IPv4 and IPv6 support
The BGP implementation supports the following:
- Peering sessions between IPv4 peers
- Peering sessions between IPv6 peers
- IPv4 routing information can be carried over either IPv4 or IPv6 peering sessions
- IPv6 routing information can be carried over either IPv4 or IPv6 peering sessions
- Both IPv4 and IPv6 routing information can be carried over a single IPv4 or IPv6 peering session
IPv4 routes can be exchanged after you have enabled either of the following:
- IPv4 unicast address family for a neighbor (using protocols bgp <asn> neighbor <id> address-family ipv4-unicast)
- IPv4 unicast address family for the peer group to which the neighbor belongs (using protocols bgp <asn> peer-group <name> address-family ipv4-unicast)
IPv6 routes can be exchanged after you have enabled either of the following:
- IPv6 unicast address family for a neighbor (using protocols bgp <asn> neighbor <id> address-family ipv6-unicast)
- IPv6 unicast address family for the peer group to which the neighbor belongs (using protocols bgp <asn> peer-group <name> address-family ipv6-unicast)
The top-level address family configuration sets family-specific parameters while the neighbor-level family configuration sets support for the given family over that neighbor connection.
The following example defines IPv4 address family parameters, but does not enable any BGP neighbor connection to carry IPv4 address-family routing data.
bgp 7777 {
address-family {
ipv4-unicast {
.....
}
}
}
The following example defines two BGP neighbors, one with an IPv4 address and one with an IPv6 address, that can carry both IPv4 and IPv6 routing information. Note that IPv4 address family support is implicitly defined.
bgp 7777 {
neighbor 3ffe::c5:5 {
address-family {
ipv6-unicast {
}
}
remote-as 7777
}
neighbor 10.1.1.1 {
address-family {
ipv6-unicast {
}
}
remote-as 7777
}
}