[rbak-nsp] mBGP / non 6PE / mapped v4 address next-hop
Florian Lohoff
f at zz.de
Fri Jun 22 09:37:19 EDT 2012
Hi,
i fail to see how to configure an SE600 with mBGP announcing local routes
(pools) without them resulting in a 6PE announcement - read: ipv4 mapped
address next-hop.
All interfaces on the SE are dual stacked - we are running ISIS in single
topology as IGP - everything is happy in IGP.
router mpls
interface CORE1
interface CORE2
!
router ldp
interface CORE1
interface CORE2
!
router bgp <del>
router-id 172.30.0.9
address-family ipv4 unicast
redistribute static route-map EXPORTPOOL
address-family ipv6 unicast
redistribute static route-map EXPORTPOOL
!
peer-group IBGP internal
password encrypted <deleted>
update-source LOOPBACK0
address-family ipv4 unicast
address-family ipv6 unicast
!
neighbor 172.30.0.5 internal
peer-group IBGP
!
neighbor 172.30.0.6 internal
peer-group IBGP
The neighbor ASR9k sees the route as:
sh route ipv6 <del>:1000::/40
Fri Jun 22 13:32:34.034 UTC
Routing entry for <del>:1000::/40
Known via "bgp <del>", distance 200, metric 0, type internal
Installed Jun 22 13:18:52.313 for 00:13:41
Routing Descriptor Blocks
::ffff:172.30.0.9, from ::ffff:172.30.0.9
Nexthop in Vrf: "default", Table: "default", IPv4 Unicast, Table Id: 0xe0000000
Route metric is 0
No advertising protos.
We are dual stacked everywhere - we run MPLS mostly for L2 services.
This is 6.5.1.3p3
Flo
--
Florian Lohoff f at zz.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20120622/82502108/attachment.sig>
More information about the redback-nsp
mailing list