The following information is available from Router

A problem was reported that the 10.10.10.0 /24 prefix was not injected into the local BGP table on
RouterA. The following information is available from RouterA.
router bgp 65001
network 10.0.0.0
neighbor 172.16.1.1 remote-as 65002
no auto-summary
show ip route
o 10.10.10.0 /24 [110/11] via 192.168.1.1 2d00h, Ethernet0/0
Why is this prefix not in the local BGP table?

A problem was reported that the 10.10.10.0 /24 prefix was not injected into the local BGP table on
RouterA. The following information is available from RouterA.
router bgp 65001
network 10.0.0.0
neighbor 172.16.1.1 remote-as 65002
no auto-summary
show ip route
o 10.10.10.0 /24 [110/11] via 192.168.1.1 2d00h, Ethernet0/0
Why is this prefix not in the local BGP table?

A.
This route is not a BGP learned route.

B.
The network command is wrong.

C.
The 172.16.1.1 neighbor is down.

D.
The prefix 10.10.10.0 /24 is not a ‘connected’ route.

Explanation:
Network command is wrong because to advertise any network through bgp, the prefix and network
mask must be exact as per the IP routing table. So to advertise this ospf route of 10.10.10.0/24,
the network command in bgp should be : network 10.10.10.0 mask 255.255.255.0



Leave a Reply 0

Your email address will not be published. Required fields are marked *