BGP

Based on the topology, configure BGP neighbor between R1-R2 and R1-ISP A:

- For iBGP configuration, if the local-address id not specified, the system uses the interface address of
the egress interface used to reach the referenced peer address.
 Based on the above topology, configure and apply policy to enable next-hop self option on router
R1 (so that R1 advertise eBGP routes to R2 with its loopback-ip as next hop):

- The inset illustrates a sample policy used to alter the next-hop value. The illustrated policy matches
on all BGP routes received from R1s EBGP peer and changes the next-hop address for those routes
to the IP address used for the IBGP peering session (R1s loopback address). This policy is applied as
an export policy to the internal BGP group.

- We recommend that you always apply the next-hop self policy as an export policy to the internal
peers or to the BGP group to which those peers belong. Improper application of a next-hop self policy
can cause suboptimal routing or result in hidden routes.

- When defining a next-hop self policy, ensure that you do not include the accept action in conjunction
with the next-hop action. Using the accept action in conjunction with the next-hop action effectively
matches all routes, BGP and otherwise, and advertises those routes to the configured IBGP peers.

Display BGP summary information:

# show bgp summary

Display BGP neighbor, BGP group information:

# show bgp neighbor
# show bgp group

Display only BGP routes from the routing table:

# show route protocol bgp

Display BGP hidden routes:

# show route hidden
- When a router receives a BGP update, the router checks whether the next-hop address is reachable.
If the next-hop is not reachable, the route is NOT considered on BGP best route selection process and
that routes are placed into the routing table as hidden routes.

- A BGP route might be hidden for various reasons such as import policy filtering, the next hop is
unreachable, or route damping.

Display all the BGP routes received from a particular neighbor (routes that are filtered by the import-
policy will not be displayed):

# show route receive-protocol bgp <neighbor-id>

- You can add the hidden command option to display routes that are hidden because of an import
Policy.

Display all the BGP routes advertised to a particular neighbor:

# show route advertising-protocol bgp <neighbor-id>