Hi there, a problem encountered during the testing the BGP attributes.
Topology is as below
R4 and NE1 establishes the EBGP relationship with the loopback interface as the source. The loopback address is learned from the static route configured on the NE1 and R4.
as the screenshot above, the first static route towards to the loopback address on the R4, the nexthop is the IP address of the R4 interface.
after the EBGP neighbor relationship established, the loopback is advertised into the BGP on both routers. Then the problem comes out,
as this picture shows, the route 10.0.4.4/32 is not valid in the BGP routing table, what’s more, the next-hop of this route is itself.
@user_3534491 hello, the preference of static route is 60, which is lower than the BGP preference, so the routes in the BGP routing table would be loaded into the routing table.
@user_3534491 hello, the preference of static route is 60, which is lower than the BGP preference, so the routes in the BGP routing table would be loaded into the routing table.
well, it seems caused by the supernet, the router wouldn't advertise the supernet routes to the BGP neighbor. you might needd to enable the supernet advertise function to enable that. [router]bgp 100 [router-bgp]supernet unicast advertise enable
Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
Politically sensitive content
Content concerning pornography, gambling, and drug abuse
Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."