...
For BGP unnumbered, the next-hop address for each prefix is an IPv6 link-local address, which is assigned automatically to each interface. Using the IPv6 link-local address as a next-hop instead of an IPv4 unicast address, BGP unnumbered saves you from having to configure IPv4 addresses on each interface.
NOTEs:
|
Configuration Example
Networking Requirements
Figure 1. BGP Unnumbered Configuration Example
As shown in Figure 1, Switch A and Switch B are BGP peers. An EBGP connection is established between Switch A and Switch B. To save IP addresses, BGP unnumbered can be configured between Switch A and Switch B. In this example, routed interfaces are configured for the use of BGP unnumbered interface.
The only difference between a BGP unnumbered configuration and the BGP numbered configuration is that the BGP neighbor is specified as an interface instead of an IP address. The interface between the two peers does not need to have an IP address configured on each side.
NOTE: The ebgp-requires-policy function needs to be disabled in EBGP, but not in IBGP. |
Procedure
Switch A
Step 1 Enable te-1/1/1 as a routed interface and configure the interface name as r1.
...
Code Block |
---|
admin@SwitchA# set protocols bgp local-as 65001
admin@SwitchA# set protocols bgp router-id 49.49.49.49
admin@SwitchA# set protocols bgp interface r1 remote-as 65002
admin@SwitchA# set protocols bgp interface r1 ipv6-unicast activate true
admin@SwitchA# set protocols bgp interface r1 capability extended-nexthop
admin@SwitchA# set protocols bgp ebgp-requires-policy false |
...
Code Block |
---|
admin@SwitchB# set protocols bgp local-as 65002
admin@SwitchB# set protocols bgp router-id 45.45.45.45
admin@SwitchB# set protocols bgp interface r1 remote-as 65001
admin@SwitchB# set protocols bgp interface r1 ipv6-unicast activate true
admin@SwitchB# set protocols bgp interface r1 capability extended-nexthop
admin@SwitchB# set protocols bgp ebgp-requires-policy false |
...