Hey Richard,
The then next-hop x.x.x.x should work as long as the next-hop is valid
'in the routing table'.
mind showing your config?
Thanks
Payam
Richard Zheng wrote:
Hi Joseph,
rtr C belongs to the customer. It only talks bgp with rtr A.
The issue is that redistribution from bgp to ospf on rtrA. It should set the
forwarding address to rtr C's ip. I tried to use 'then next-hop w.x.y.z',
but no effect.
Thanks,
Richard
On Mon, Jun 13, 2011 at 2:39 AM, Joseph Soricelli <j...@proteus.net> wrote:
Richard-
IIRC, in the "customer-A" term configuring "then next-hop w.x.y.z" with rtr
C's loopback address should set the forwarding address to rtr C.
Assuming that rtr C is running OSPF, is there a particular reason that rtr
C can't redist its own routes into OSPF?
-joe
Joseph Soricelli
JNCIE #14/ CCIE #4803
703-980-3999
j...@proteus.net
Twitter - @proteusnetworks
On Jun 13, 2011, at 6:42 AM, Richard Zheng wrote:
Hi,
We have the following setup. RTR A speaks multihop BGP with CPE router C.
Router B is in the middle, and doesn't speak bgp. We redistribute BGP
routes
on rtr A into OSPF. There is a filter to only allow specific routes
learned
from rtr C. However OSPF external route redistributed at rtr A has a
forward
address 0.0.0.0. So rtr B still sends traffic to A, which causes a loop.
How do I let rtr B know to send traffic to rtr C for routes learned from
rtr
C?
---------- -------------- -----------
| BGP rtr A | ============ | no-BGP rtr B | ============ | CPE BGP C |
---------- -------------- -----------
The router filter is
term customer-A {
from {
protocol bgp;
route-filter x.y.z.0/24 exact;
}
then accept;
}
term reject-others {
then reject;
}
The ospf external route on rtr B is like this,
Type-5 AS External Link States
Routing Bit Set on this LSA
LS age: 89
Options: (No TOS-capability, DC)
LS Type: AS External Link
Link State ID: x.y.z.0 (External Network Number )
Advertising Router: a.b.c.c (which is rtr-A's loopback)
LS Seq Number: 80000001
Checksum: 0xD32E
Length: 36
Network Mask: /24
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 0
Forward Address: 0.0.0.0
External Route Tag: 0
Thanks,
Richard
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
