Injecting Information Statically into BGP
- Tracy Yang (Unlicensed)
Listing prefixes with the network command has the same drawbacks as the dynamic redistribution. If a route that is listed with the network command goes down, BGP will send an update; if the route comes back, BGP will send another update. If this behavior continues, the IGP instability will translate into BGP instabilities. The only way around this is to use a combination of statically defined prefixes in conjunction with the network command. This will ensure that the prefixes will always remain in the IP routing tables and will always be advertised.
Configuration Command References:
admin@XorPlus# set protocols bgp network6 <IPV6-Network>
Note: This command is to advertise a special IPV6 Network statically.
Figure 1-12
Step 1: Switch A Switch B enable ospfv3
Switch A:
admin@XorPlus# set protocols ospf6 instance-id 1 admin@XorPlus# set protocols ospf6 router-id 1.1.1.1 admin@XorPlus# set protocols ospf6 area 0.0.0.0 interface vlan500 vif vlan500 address 5005::2
Switch B:
admin@XorPlus# set protocols ospf6 instance-id 1 admin@XorPlus# set protocols ospf6 router-id 9.9.9.9 admin@XorPlus# set protocols ospf6 area 0.0.0.0 interface vlan500 vif vlan500 address 5005::1
Step 2: Check ospfv3 neighbor status on Switch B
Note: OSPFv3 have been established.
admin@XorPlus# run show ospf6 neighbor Address Interface State Router ID Pri Dead --------------------------------------- --------------------- -------- --------------- ----- ---- fe80::200:5ff:fe6c:f993 vlan500/vlan500 Full 1.1.1.1 0 37
Step 3: Switch A propagate two ospfv3 route to Switch B. Then, check ospf route table on SwitchB
Note: Two ospfv3 route entries, 8888::/64 8888:0:0:1::/64, can be seen.
admin@XorPlus# run show route table ipv6 unicast ospf 8888::/64 [ospf(110)/1] > to fe80::200:5ff:fe6c:f993 via vlan500/vlan500 8888:0:0:1::/64 [ospf(110)/1] > to fe80::200:5ff:fe6c:f993 via vlan500/vlan500 admin@XorPlus# run show route forward-route ipv6 all Destination NetMask NextHopMac Port --------------------------------------- --------------------------------------- ----------------- --------- 3003:: ffff:ffff:ffff:ffff:: C8:0A:A9:AE:0A:66 connected 5005:: ffff:ffff:ffff:ffff:: C8:0A:A9:AE:0A:66 connected 4001:: ffff:ffff:ffff:ffff:: 04:7D:7B:62:93:FF te-1/1/46 2001:: ffff:ffff:ffff:ffff:: C8:0A:A9:AE:0A:66 connected 8888:: ffff:ffff:ffff:ffff:: 00:00:05:6C:F9:93 te-1/1/44 8888:0:0:1:: ffff:ffff:ffff:ffff:: 00:00:05:6C:F9:93 te-1/1/44
Step 4: Switch B Switch C Enable EBGP. Switch B Switch D Enable EBGP.
Switch B:
admin@XorPlus# set protocols bgp bgp-id 9.9.9.9 admin@XorPlus# set protocols bgp local-as "9" admin@XorPlus# set protocols bgp peer 3003::1 local-ip "3003::2" admin@XorPlus# set protocols bgp peer 3003::1 as "6" admin@XorPlus# set protocols bgp peer 3003::1 ipv6-unicast true
Switch C:
admin@XorPlus# set protocols bgp bgp-id 6.6.6.6 admin@XorPlus# set protocols bgp local-as "6" admin@XorPlus# set protocols bgp peer 3003::2 local-ip "3003::1" admin@XorPlus# set protocols bgp peer 3003::2 as "9" admin@XorPlus# set protocols bgp peer 3003::2 ipv6-unicast true
Step 5: Check BGP peer status on Switch B
Note: BGP peer is established.
Switch B:
admin@XorPlus# run show bgp peers detail 3003::1 Peer 1: local 3003::2/179 remote 3003::1/41512 Peer ID: 6.6.6.6 Peer State: ESTABLISHED Admin State: START Negotiated BGP Version: 4 Peer AS Number: 6 Updates Received: 0, Updates Sent: 5 Messages Received: 56, Messages Sent: 62 Time since last received update: n/a Number of transitions to ESTABLISHED: 5 Time since last entering ESTABLISHED state: 1426 seconds Retry Interval: 120 seconds Hold Time: 90 seconds, Keep Alive Time: 30 seconds Configured Hold Time: 90 seconds, Configured Keep Alive Time: 30 seconds Minimum AS Origination Interval: 0 seconds Minimum Route Advertisement Interval: 0 seconds
Step 6: Check BPG route table on Switch B Switch C Switch D. They should all be NULL.
Switch B:
admin@XorPlus# run show bgp routes ipv6 Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ---------------------------- ------------------------ --------------- ------------
Switch C:
admin@XorPlus# run show bgp routes ipv6 Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ---------------------------- ------------------------ --------------- ------------
Step 7: Injecting a special network into BGP via “Network” command
Note: We inject network 8888::/64 into BGP via network command, and the network 8888::/64 is reachable, as the entry 8888::/64 is in ospfv3 route table.
admin@XorPlus# set protocols bgp network6 8888::/64
Step 8: Check BGP route table on Switch B Switch C
Switch B:
admin@XorPlus# run show bgp routes ipv6 Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ---------------------------- ------------------------ --------------- ------------ *> 8888::/64 :: 0.0.0.0 i
Switch C:
admin@XorPlus# run show bgp routes ipv6 Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ---------------------------- ------------------------ --------------- ------------ *> 8888::/64 3003::2 9.9.9.9 9 i
Step 9: Switch A withdrawn the route entry 8888::/64
Since the network 8888::/64 is not reachable, the network will not install into the BGP route table.
Switch B ospfv3 route table:
admin@XorPlus# run show route table ipv6 unicast ospf admin@XorPlus#
Switch B BGP route table:
admin@XorPlus# run show bgp routes ipv6 Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ---------------------------- ------------------------ --------------- ------------ admin@XorPlus#
Copyright © 2025 Pica8 Inc. All Rights Reserved.