Dynamic Acquisition with MBGP
Problem
You appetite to use MBGP to backpack IPv6 acquisition advice amid free systems.
Solution
MBGP readily carries IPv6 unicast acquisition advice amid IPv6 BGP peers:
Router1#configure terminal
Enter agreement commands, one per line. End with CNTL/Z.
Router1(config)#router bgp 65520
Router1(config-router)#no bgp absence ipv4-unicast
Router1(config-router)#neighbor AAAA:5::2 remote-as 65522
Router1(config-router)#neighbor AAAA:5::AA9 remote-as 65521
Router1(config-router)#address-family ipv6
Router1(config-router-af)#neighbor AAAA:5::2 activate
Router1(config-router-af)#neighbor AAAA:5::AA9 activate
Router1(config-router-af)#network AAAA:2222::2/64
Router1(config-router-af)#no synchronization
Router1(config-router-af)#exit-address-family
Router1(config-router)#exit
Router1(config)#end
Router1#
And you can alike run a aggregate of IPv4 and IPv6 BGP on the aforementioned router:
Router9#configure terminal
Enter agreement commands, one per line. End with CNTL/Z.
Router9(config)#router bgp 65521
Router9(config-router)#no bgp absence ipv4-unicast
Router9(config-router)#neighbor AAAA:5::1 remote-as 65520
Router9(config-router)#neighbor 192.168.1.103 remote-as 65525
Router9(config-router)#address-family ipv4
Router9(config-router-af)#redistribute connected
Router9(config-router-af)#neighbor 192.168.1.103 activate
Router9(config-router-af)#no auto-summary
Router9(config-router-af)#no synchronization
Router9(config-router-af)#exit-address-family
Router9(config-router)#address-family ipv6
Router9(config-router-af)#neighbor AAAA:5::1 activate
Router9(config-router-af)#network AAAA:FE::1/64
Router9(config-router-af)#network AAAA:BBBB::1/64
Router9(config-router-af)#no synchronization
Router9(config-router-af)#exit-address-family
Router9(config-router)#exit
Router9(config)#end
Router9#
Discussion
The aboriginal archetype shows how to configure a router to run BGP amid IPv6 peers:
Router1(config)#router bgp 65520
Router1(config-router)#no bgp absence ipv4-unicast
Router1(config-router)#neighbor AAAA:5::2 remote-as 65522
The analytical command actuality is the no bgp absence ipv4-unicast line. By default, BGP will alone administer IPv4 prefixes to its neighbors. However, back you attenuate the absence ipv4-unicast command, you can alpha to administer IPv6 acquisition advice as well.
We agenda in casual that you can configure IPv4 neighbors to canyon IPv6 acquisition information, but this bound becomes actual complicated because the next-hop advice is in the amiss protocol. For this reason, we acerb acclaim application IPv6 acquaintance addresses back casual IPv6 acquisition prefixes with MBGP.
The abutting footfall is to configure one or added acquaintance statements and to actuate them in the address-family ipv6 agreement block. This way the router knows what sorts of Arrangement Layer Reachability Advice (NLRI) to canyon to this neighbor. You additionally configure any arrangement commands in the address-family agreement area:
Router1(config)#router bgp 65520
Router1(config-router)#neighbor AAAA:5::2 remote-as 65522
Router1(config-router)#address-family ipv6
Router1(config-router-af)#neighbor AAAA:5::2 activate
Router1(config-router-af)#network AAAA:2222::2/64
Router1(config-router-af)#no synchronization
Note that we accept included the no synchronization command actuality for the aforementioned affidavit that we included it in abounding of the BGP examples in Chapter 9. By default, BGP wants to ensure that all acquisition is constant aural the Free System. So it wants to see that any prefixes that it distributes application iBGP are additionally present in the IGP for the AS. In this example, however, we are not redistributing acquisition advice amid BGP and the IGP. In fact, we're not alike active an IGP. Please accredit to Chapter 9 for a added abundant altercation of this command.
In the additional archetype in the Solution area of this recipe, we accept configured both IPv4 and IPv6 BGP neighbors:
Router9#configure terminal
Enter agreement commands, one per line. End with CNTL/Z.
Router9(config)#router bgp 65521
Router9(config-router)#no bgp absence ipv4-unicast
Router9(config-router)#neighbor AAAA:5::1 remote-as 65520
Router9(config-router)#neighbor 192.168.1.103 remote-as 65525
Then we accept included address-family agreement both IPv4 and IPv6 unicast avenue prefixes:
Router9(config-router)#address-family ipv4
Router9(config-router-af)#redistribute connected
Router9(config-router-af)#neighbor 192.168.1.103 activate
Router9(config-router-af)#no auto-summary
Router9(config-router-af)#no synchronization
Router9(config-router-af)#exit-address-family
Router9(config-router)#address-family ipv6
Router9(config-router-af)#neighbor AAAA:5::1 activate
Router9(config-router-af)#network AAAA:FE::1/64
Router9(config-router-af)#network AAAA:BBBB::1/64
Router9(config-router-af)#no synchronization
Router9(config-router-af)#exit-address-family
This agency that this router is active BGP for both IPv4 and IPv6 simultaneously. Agenda that back you do this, the ASN for both protocols is the same.
The commands to attending at IPv6 BGP advice are hardly altered that we ahead saw for IPv4 BGP. You can see the cachet of the acquaintance routers with the appearance bgp arbitrary command:
Router9#show bgp summary
BGP router identifier 172.16.1.1, bounded AS cardinal 65521
BGP table adaptation is 19, capital acquisition table adaptation 19
6 arrangement entries application 798 bytes of memory
6 aisle entries application 432 bytes of memory
4 BGP aisle aspect entries application 240 bytes of memory
2 BGP AS-PATH entries application 48 bytes of memory
0 BGP route-map accumulation entries application 0 bytes of memory
0 BGP filter-list accumulation entries application 0 bytes of memory
BGP application 1518 absolute bytes of memory
BGP action 58/50 prefixes, 112/104 paths, browse breach 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
AAAA:5::1 4 65520 168 147 19 0 0 01:44:39 4
Router9#
You still use the appearance ip bgp arbitrary command to see the authentic IPv4 BGP peers:
Router9#show ip bgp summary
BGP router identifier 172.16.1.1, bounded AS cardinal 65521
BGP table adaptation is 12, capital acquisition table adaptation 12
5 arrangement entries application 505 bytes of memory
6 aisle entries application 288 bytes of memory
5 BGP aisle aspect entries application 300 bytes of memory
3 BGP AS-PATH entries application 72 bytes of memory
0 BGP route-map accumulation entries application 0 bytes of memory
0 BGP filter-list accumulation entries application 0 bytes of memory
BGP application 1165 absolute bytes of memory
BGP action 61/50 prefixes, 116/104 paths, browse breach 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
192.168.1.103 4 65525 83 83 12 0 0 00:01:43 4
Router9#
To attending at the BGP table, which contains all BGP acquisition prefixes, you use the appearance bgp command:
Router9#show bgp
BGP table adaptation is 19, bounded router ID is 172.16.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Arrangement Abutting Hop Metric LocPrf Weight Path
*> AAAA:99::A:0/112 AAAA:5::2 0 65520 65522 65523 i
*> AAAA:99::B:0/112 AAAA:5::2 0 65520 65522 65523 i
*> AAAA:99::C:0/112 AAAA:5::2 0 65520 65522 65523 i
*> AAAA:FE::1/64 :: 0 32768 i
*> AAAA:2222::/64 AAAA:5::1 0 0 65520 i
*> AAAA:BBBB::/64 :: 0 32768 i
Router9#
And you can verify that these IPv6 prefixes accept been alien into the acquisition table with the command appearance ipv6 avenue bgp:
Router9#show ipv6 avenue bgp
IPv6 Acquisition Table - 20 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
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
B AAAA:99::A:0/112 [20/0]
via AAAA:5::2
B AAAA:99::B:0/112 [20/0]
via AAAA:5::2
B AAAA:99::C:0/112 [20/0]
via AAAA:5::2
B AAAA:2222::/64 [20/0]
via FE80::20E:D7FF:FED6:4D80, Ethernet0
Router9#
See Also