Troubleshooting guide

Troubleshooting

Next, record the current settings in the AOS device and verify that they match those that have been agreed

upon with the entity that controls the external AS. Table 13 on page 78 displays the key information that

should be verified and how to view the settings on the AOS device.

Figure 12 below shows sample output and where to locate some of the information for Table 13 on

page 78.

Router#show ip bgp summary

BGP router identifier 192.168.88.1, local AS number 501

0 network entries, 0 paths, and 1 BGP path attribute entries

Neighbor V AS MsgRcvd MsgSent InQ OutQ Up/Down State/PfxRcd

192.168.0.25 4 500 58 57 0 0 00:55:07 2

Remote address

Local AS

Local Router ID

Figure 12. Viewing Local ID and Local AS

When the BGP interface cannot reach the configured neighbor, the following debug messages are received

on the console:

BGP EVT 1.1.1.1[1]: IDLE->CONNECT

BGP EVT 1.1.1.1[1]: CONNET->IDLE

BGP OUT 1.1.1.1[1]: TCP error 0 connecting to peer (events:connect)

In this example, the interface is attempting to connect to a peer through the peer’s loopback IPv4 address

(1.1.1.1), which the router does not consider to be directly connected.

When configuring the BGP neighbor, it is important to

always identify it by the IPv4 address for the

connecting interface, even if the remote router uses a different router ID. For example, Figure 13 displays

information about a local router’s BGP neig

hbor. The neighbor uses the IPv4 address 192.168.5.1 for its

router ID. However, the remote IPv4 address is 192.168.0.25, and this is the IPv4 address that should be

entered when configuring the neighbor.

Table 13. Checking BGP Configuration

Key Information How to View Record the AOS Device Setting

local AS show ip bgp [summary]

local router ID show ip bgp [summary]

local router IPv4

address

show ip bgp neighbor

neighbor router ID show ip bgp neighbor

neighbor IPv4 address show ip bgp neighbor

remote AS show ip bgp neighbor