s******v
发帖数: 4495 | 1 configuration is simple. but why 2.2.2.2 要enabled在ipv4 AF? 看了C的网站都是
这样，而且如果拿掉2.2.2.2 under ipv4, the ipv6 prefix is not accepted as
valid.
router bgp 1
nei 1:1:1::2 remote 100 # CE
nei 2.2.2.2 remote 1 # RR
nei 2.2.2.2 upd loop0
!
add ipv4
redis conn
nei 2.2.2.2 act # RR enabled on ipv4，必须的，可是为什么？
!
add ipv6
redis conn
nei 2.2.2.2 act # RR enabled ipv6 with label
nei 2.2.2.2 send-label
nei 1:1:1::2 act | s*****g
发帖数: 1055 | 2 Don't you need IPv4 connectivity between iBGP peers (whether you use RR or
not is irreverent) ? 6PE will need MPLS transport LSP for iBGP peer IPv4
address. | s******v
发帖数: 4495 | 3 but ipv4 connectivity with label is carried by IGP.
when I did show ip bgp
PE1#sh ip bgp 44.100.100.2
BGP routing table entry for 44.100.100.2/32, version 5
Paths: (1 available, best #1, table default, RIB-failure(17))
Not advertised to any peer
Refresh Epoch 1
Local
44.100.100.2 (metric 2) from 44.100.100.2 (44.100.100.22)
Origin incomplete, metric 0, localpref 100, valid, internal, best
rx pathid: 0, tx pathid: 0x0
this ipv4 prefix is even marked as RIB failure which means it was ignored
since the IGP route has higher admin value.
【在 s*****g 的大作中提到】
: Don't you need IPv4 connectivity between iBGP peers (whether you use RR or
: not is irreverent) ? 6PE will need MPLS transport LSP for iBGP peer IPv4
: address.
| z**r
发帖数: 17771 | 4 6pe 里所有的p router都是ipv4，ipv6的扩展都得借助ipv4才行
【在 s******v 的大作中提到】
: but ipv4 connectivity with label is carried by IGP.
: when I did show ip bgp
: PE1#sh ip bgp 44.100.100.2
: BGP routing table entry for 44.100.100.2/32, version 5
: Paths: (1 available, best #1, table default, RIB-failure(17))
: Not advertised to any peer
: Refresh Epoch 1
: Local
: 44.100.100.2 (metric 2) from 44.100.100.2 (44.100.100.22)
: Origin incomplete, metric 0, localpref 100, valid, internal, best
| s*****g
发帖数: 1055 | 5 Sorry, I mis-understood you ...
I don't think you need to activate IPv4 neighbor under ipv4 unicast address
family if you are not exchanging IPv4 unicast routes. So even ipv4 neighbor
is not activated under ipv4 unicast address family, 6PE will still work, if
not, it must be something else.
【在 s******v 的大作中提到】
: but ipv4 connectivity with label is carried by IGP.
: when I did show ip bgp
: PE1#sh ip bgp 44.100.100.2
: BGP routing table entry for 44.100.100.2/32, version 5
: Paths: (1 available, best #1, table default, RIB-failure(17))
: Not advertised to any peer
: Refresh Epoch 1
: Local
: 44.100.100.2 (metric 2) from 44.100.100.2 (44.100.100.22)
: Origin incomplete, metric 0, localpref 100, valid, internal, best
| s******v
发帖数: 4495 | 6 我的理解和你一样，所以看到sample cfg里面有ipv4 AF，很不解，而且试验了一下，
没有ipv4 AF不行，如果拿掉了"nei x.x.x.x act" under ipv4 AF, ipv6 pfx is not
imported.
怪了。
address
neighbor
if
【在 s*****g 的大作中提到】
: Sorry, I mis-understood you ...
: I don't think you need to activate IPv4 neighbor under ipv4 unicast address
: family if you are not exchanging IPv4 unicast routes. So even ipv4 neighbor
: is not activated under ipv4 unicast address family, 6PE will still work, if
: not, it must be something else.
| s******v
发帖数: 4495 | 7 如果是NH的话，在ipv6 pfx, NH = ::FFFF:x.x.x.x，这个解析应该是从IGP(ospf in
my case)得到啊。
可是为啥要在BGP里面的IPV4 AF里面，“nei x.x.x.x act"
【在 z**r 的大作中提到】
: 6pe 里所有的p router都是ipv4，ipv6的扩展都得借助ipv4才行
| s*****g
发帖数: 1055 | 8 How can that be possible? let's lab it up with dynamip.
not
【在 s******v 的大作中提到】
: 我的理解和你一样，所以看到sample cfg里面有ipv4 AF，很不解，而且试验了一下，
: 没有ipv4 AF不行，如果拿掉了"nei x.x.x.x act" under ipv4 AF, ipv6 pfx is not
: imported.
: 怪了。
:
: address
: neighbor
: if
| s*****g
发帖数: 1055 | 9 Here we go, simple 2 router setup,
R1#sh run | sec bgp
router bgp 1
bgp log-neighbor-changes
neighbor 2.2.2.2 remote-as 1
neighbor 2.2.2.2 update-source Loopback0
!
address-family ipv4
no neighbor 2.2.2.2 activate <== IPv4 neighbor not activated
no auto-summary
no synchronization
exit-address-family
!
address-family ipv6
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 send-label
redistribute connected
no synchronization
exit-address-family
R1#sh ipv6 route
IPv6 Routing Table - 3 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route, M - MIPv6
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
D - EIGRP, EX - EIGRP external
LC 2001::1/128 [0/0]
via ::, Loopback1
B 2001::2/128 [200/0]
via ::FFFF:2.2.2.2, IPv6-mpls
L FF00::/8 [0/0]
via ::, Null0
【在 s*****g 的大作中提到】
: How can that be possible? let's lab it up with dynamip.
:
: not
| z**r
发帖数: 17771 | 10 NH应该是far end PE loopback，这个肯定是从IGP得到，同时也应该在LFIB里，你不激
活ipv4 neighbor，同时看一下show mpls for？
刚才俺也做了个实验，果然不需要在add ipv4下激活ipv4 neighbor，只需要在add
ipv6下激活ipv4 neighbor就可以送ipv6扩展了。
R1----R2----R3----R4
R1 and R4 are dual stack, R2 and R3 are IPv4 only, LDP enabled on all
interface
相关配置如下
!
!
!
ip cef
no ip domain lookup
ipv6 unicast-routing
ipv6 cef
!
!
interface Loopback0
ip address 10.1.1.1 255.255.255.255
!
interface Loopback1
no ip address
ipv6 address 2001::1/128
!
interface Ethernet0/0
no ip address
!
interface Ethernet0/1
ip address 10.1.12.1 255.255.255.0
mpls ip
!
interface Ethernet0/2
no ip address
shutdown
!
interface Ethernet0/3
no ip address
shutdown
!
router ospf 1234
log-adjacency-changes
passive-interface Loopback0
network 10.1.0.0 0.0.255.255 area 0
!
router bgp 1
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 10.1.4.4 remote-as 1
neighbor 10.1.4.4 update-source Loopback0
!
address-family ipv4
no synchronization
no auto-summary
exit-address-family
!
address-family ipv6
redistribute connected
no synchronization
neighbor 10.1.4.4 activate
neighbor 10.1.4.4 send-label
exit-address-family
!
!
!
!
!
R1#sh ipv6 ro
IPv6 Routing Table - default - 3 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, HA - Home Agent, MR - Mobile Router, R - RIP
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
D - EIGRP, EX - EIGRP external, ND - Neighbor Discovery
LC 2001::1/128 [0/0]
via Loopback1, receive
B 2001::4/128 [200/0]
via 10.1.4.4%default, indirectly connected
L FF00::/8 [0/0]
via Null0, receive
R1#trace 2001::4
Type escape sequence to abort.
Tracing the route to 2001::4
1 ::FFFF:10.1.12.2 [MPLS: Labels 18/21 Exp 0] 4 msec 0 msec 0 msec
2 ::FFFF:10.1.23.3 [MPLS: Labels 18/21 Exp 0] 0 msec 4 msec 0 msec
3 2001::4 0 msec 0 msec 0 msec
R1#show mpl for
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
16 Pop Label 10.1.2.2/32 0 Et0/1 10.1.12.2
17 17 10.1.3.3/32 0 Et0/1 10.1.12.2
18 18 10.1.4.4/32 0 Et0/1 10.1.12.2
19 Pop Label 10.1.23.0/24 0 Et0/1 10.1.12.2
20 19 10.1.34.0/24 0 Et0/1 10.1.12.2
21 Pop Label 2001::1/128 4808 aggregate
R1#
【在 s******v 的大作中提到】
: 如果是NH的话，在ipv6 pfx, NH = ::FFFF:x.x.x.x，这个解析应该是从IGP(ospf in
: my case)得到啊。
: 可是为啥要在BGP里面的IPV4 AF里面，“nei x.x.x.x act"
| | | s******v
发帖数: 4495 | 11 多谢！我在看一眼我的cfg，可能有问题，要不然就是bug了。
【在 s*****g 的大作中提到】
: Here we go, simple 2 router setup,
: R1#sh run | sec bgp
: router bgp 1
: bgp log-neighbor-changes
: neighbor 2.2.2.2 remote-as 1
: neighbor 2.2.2.2 update-source Loopback0
: !
: address-family ipv4
: no neighbor 2.2.2.2 activate <== IPv4 neighbor not activated
: no auto-summary
| s*****g
发帖数: 1055 | 12 Heheh, it is such a shame we have to lab it to verify a basic concept.
【在 z**r 的大作中提到】
: NH应该是far end PE loopback，这个肯定是从IGP得到，同时也应该在LFIB里，你不激
: 活ipv4 neighbor，同时看一下show mpls for？
: 刚才俺也做了个实验，果然不需要在add ipv4下激活ipv4 neighbor，只需要在add
: ipv6下激活ipv4 neighbor就可以送ipv6扩展了。
: R1----R2----R3----R4
: R1 and R4 are dual stack, R2 and R3 are IPv4 only, LDP enabled on all
: interface
: 相关配置如下
: !
: !
| z**r
发帖数: 17771 | 13 agreed. luckily my customers don't know this, lol
【在 s*****g 的大作中提到】
: Heheh, it is such a shame we have to lab it to verify a basic concept.
| s******v
发帖数: 4495 | 14 you guys are right. so sorry for that. this time, my cfg works well. | z**r
发帖数: 17771 | 15 no worries, thanks for bringing this up so we can have a chance to refresh
6pe, lol. BTW, what was the issue?
【在 s******v 的大作中提到】
: you guys are right. so sorry for that. this time, my cfg works well.
| j*a
发帖数: 14423 | 16 没看懂你的问题
【在 s******v 的大作中提到】
: configuration is simple. but why 2.2.2.2 要enabled在ipv4 AF? 看了C的网站都是
: 这样，而且如果拿掉2.2.2.2 under ipv4, the ipv6 prefix is not accepted as
: valid.
: router bgp 1
: nei 1:1:1::2 remote 100 # CE
: nei 2.2.2.2 remote 1 # RR
: nei 2.2.2.2 upd loop0
: !
: add ipv4
: redis conn
| s******v
发帖数: 4495 | 17 把cfg抹了，重新cfg一遍就好了:-)
可能有个typo，当时没注意到。要不然就是我用的是新release，不是很稳定。
【在 z**r 的大作中提到】
: no worries, thanks for bringing this up so we can have a chance to refresh
: 6pe, lol. BTW, what was the issue?
| z**r
发帖数: 17771 | 18 多好的troubleshooting机会，可惜了，呵呵
【在 s******v 的大作中提到】
: 把cfg抹了，重新cfg一遍就好了:-)
: 可能有个typo，当时没注意到。要不然就是我用的是新release，不是很稳定。
|
|
