IPv6 - Konfigurations-Beispiele - BGP Peering

Die ersten IPv6-Konfigs und Tests, hauptsächlich im GNS3 auf 7200er Plattform


 Topology

1. BGP-Peering with Link-Locals (GNS3)
R1
!
router bgp 65000
no synchronization
bgp log-neighbor-changes
neighbor FE80::C80F:3AFF:FEB5:1C%FastEthernet1/0 remote-as 65000
no auto-summary
!

R2
!
router bgp 65000
no synchronization
bgp log-neighbor-changes
neighbor FE80::C80E:3AFF:FEB5:1C%FastEthernet1/0 remote-as 65000
no auto-summary
!

2. BGP-Peering (GNS3,link-local, IPv4 Prefix)
R1
!
router bgp 65000
no synchronization
bgp log-neighbor-changes
network 10.0.0.1 mask 255.255.255.255
neighbor FE80::C80F:3AFF:FEB5:1C%FastEthernet1/0 remote-as 65000
no auto-summary
!
address-family ipv6
neighbor FE80::C80F:3AFF:FEB5:1C%FastEthernet1/0 activate
network 2001:1::/64
exit-address-family
!

R2
!
router bgp 65000
no synchronization
bgp log-neighbor-changes
network 10.0.0.2 mask 255.255.255.255
neighbor FE80::C80E:3AFF:FEB5:1C%FastEthernet1/0 remote-as 65000
no auto-summary
!
address-family ipv6
neighbor FE80::C80E:3AFF:FEB5:1C%FastEthernet1/0 activate
network 2001:2::/64
exit-address-family
!

Im Next-Hop-Attribute für die IPv4/10.0.0.2/32 steht eine
IPv6-Link-local-Adresse, IPv4-Next-Hop müsste mit Route-map gesetzt werden
*Aug 10 10:47:10.431: %BGP-6-NEXTHOP: Invalid next hop (254.128.0.0)
received from FE80::C80F:3AFF:FEB5:1C%FastEthernet1/0: martian next hop

IPv6-Peering-Adresse -> IPv6 Next-Hop-Adresse

IPv4-Peering-Adresse -> IPv4 Next-Hop-Adresse


3.BGP Peering (GNS3, link-local, ohne Interface-Angabe)

R1#sh run | incl neighbor
bgp log-neighbor-changes
neighbor FE80::C80F:3AFF:FEB5:1C remote-as 65000
R1#sh ip bgp su
BGP router identifier 10.0.0.1, local AS number 65000
BGP table version is 3, main routing table version 3
1 network entries using 132 bytes of memory
1 path entries using 52 bytes of memory
2/1 BGP path/bestpath attribute entries using 296 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
Bitfield cache entries: current 1 (at peak 2) using 28 bytes of memory
BGP using 508 total bytes of memory
BGP activity 3/1 prefixes, 6/4 paths, scan interval 60 secs

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
FE80::C80F:3AFF:FEB5:1C
4 65000 0 0 0 0 0 never Idle
R1#

R2#sh run | incl neighbor
bgp log-neighbor-changes
neighbor FE80::C80E:3AFF:FEB5:1C remote-as 65000
R2#sh run | incl neighbor
bgp log-neighbor-changes
neighbor FE80::C80E:3AFF:FEB5:1C remote-as 65000
R2#sh ip bgp su
BGP router identifier 10.0.0.2, local AS number 65000
BGP table version is 3, main routing table version 3
1 network entries using 132 bytes of memory
1 path entries using 52 bytes of memory
2/1 BGP path/bestpath attribute entries using 296 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
Bitfield cache entries: current 1 (at peak 2) using 28 bytes of memory
BGP using 508 total bytes of memory
BGP activity 3/1 prefixes, 3/1 paths, scan interval 60 secs

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
FE80::C80E:3AFF:FEB5:1C
4 65000 0 0 0 0 0 never Active
R2#
 
BGP-Peering kommt nicht zustande, da der Router nicht weiss über welches
Interface der BGP-Neighbor zu erreichen ist.