# Display the BGP routing table on Switch B. Network Nexthop Metric LocalPref Weight AsPath Origin codes: i - IGP, e - EGP, ? - incomplete
Status codes: * - valid, > - best, i - internal, e. # Display the BGP routing table on Switch A. The output shows that Switch B has established an iBGP peer relationship with Switch C and an eBGP peer relationship with Switch A. # Show IP bgp peer information on Switch B. To enable Switch C to access the network 8.1.1.0/24 that is connected directly to Switch A, add network 8.1.1.0/24 to the BGP routing table of Switch A. Their loopback interfaces are not reachable to each other, so directly connected interfaces are used for establishing BGP sessions. The eBGP peers, Switch A and Switch B (usually belonging to different carriers), are located in different ASs. The output information shows that Switch C has established an iBGP peer relationship with Switch B.
Remote Address Remote-AS Local-AS State Admin Status HP Switch(bgp)# neighbor 2.2.2.2 connect-interface loopback 0 To prevent route flapping caused by port state changes, this example uses loopback interfaces to establish iBGP connections.īecause loopback interfaces are virtual interfaces, you need to use the peer connect-interface command to specify the loopback interface as the source interface for establishing BGP connections.Įnable OSPF in AS 65009 to ensure that Switch B can communicate with Switch C through loopback interfaces.