No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-The Next-Hop IP Address of the Route Learned by an EBGP Peer Fails to Be Changed Through a Route-Policy

Publication Date:  2019-04-16 Views:  121 Downloads:  0

Issue Description

The next-hop IP address of the route learned by an EBGP peer fails to be changed through a route-policy delivered using the apply ip-address next-hop command.


If an EBGP peer relationship is established through physical connections, the route-policy delivered using the apply ip-address next-hop command does not take effect. That is, the next-hop IP address cannot be changed.


You can use non-direct-connect addresses to establish EBGP peer relationships. For example, use a loopback interface address to establish an EBGP peer relationship.