Viewing a Device's BGP Configuration

The BGP page lists the basic characteristics for routers in which Border Gateway Protocol is active. The table displays information about all known BGP4 neighbors for the current device. IPv4 and IPv6 versions of BGP are supported. If the router does not support BGP, this page will remain blank. Any neighbor interfaces that have established adjacencies with the currently selected router will appear in this table.

The BGP Neighbor Table displays the following information by default (other fields can be added to the table):

• Local Addr: Local IP address of the individual ports of the current device.

• Network View: Lists the NetMRI network view associated with the device's interface that connects to its discovered BGP neighbor. Clicking the link opens the Network View Viewer window, which lists the Associated VRFs and the Imported VRFs for the network view.

• Local Port: The Interface ID.

• Neighbor Addr: The neighboring interface running BGP4, that has established an adjacency with the listed local port.

• Neighbor Port: The neighboring port's interface ID.

• Neighbor AS: The Autonomous System (AS) to which the neighboring interface belongs.

• Neighbor Name: The name of the router host for the neighboring interface.

• RP Peer Device Type: Route Processor peer device type (if applicable), indicates the peer route processor type if line card-based forwarding table synchronization is supported. Possible values include RSP for a Cisco 7500-class router and GRP (gigabit router processor) in a Cisco 12000-class router line card.

• Connection State: Reflects the current BGP connection state of the BGP peer when the network was last polled by NetMRI. Typically, the state of a full BGP peer is Established. Seeing anything but an Established state in this field may indicate issues. Other possible states include Idle, Connect, Active, OpenSent, and OpenConfirm. BGP sessions begin in an Idle state when the device initializes the resource it needs for the upcoming session. It then transitions to state Connect while the peers establish their TCP connection for BGP. Once the TCP connection is established between the peer interfaces the routing protocol moves to the OpenSent state. If the TCP connection fails, the peers enter the Active state. OpenSent indicates that the device has received an Open message from the peer, and then determines the AS to which the neighbor belongs. OpenConfirm indicates that the device is waiting for a Keepalive response from the other end. If it gets one, the BGP connection switches to the Established state.

• Last State Change: The timestamp for the last detected occasion that the current device changed its BGP state on the current interface in the table.