Peer Statistics The routing tables managed by a BGP implementation are adjusted continually to reflect changes in the network, such as links breaking and being restored or routers going down and coming back up. In the network as a whole it is normal for these changes to happen almost continuously, but for any particular router or link changes are supposed to be relatively infrequent. Therefore AppDirector users need to monitor the BGP statistics from the Peer table. To access the Peer Table statistics 1. From the Router menu select BGP Route Injection > Statistics. The Statistics pane displays. 2. Select the Peer IP Address. The BGP Peer Table Statistics Update pane displays. 3. Set the parameters. Parameter Description Peer IP Address IP address of the remote peer. Admin Status Lets administrators enable or disable the peer. Connection State Idle — The Peer is stopped. Connect — AppDirector initiated a TCP connection to remote peer. Active — Peer is waiting during a connect retry interval, after failing to establish TCP connection to a remote peer. In this state, AppDirector also listens on port 179 for potential incoming connections from the remote peer. OpenSent — A TCP connection is established with the remote peer. AppDirector sent a BGP OPEN message to the remote peer and expects to receive an OPEN message from it. OpenConfirm — AppDirector received an OPEN message from the remote peer. AppDirector responds with a KEEPALIVE message and expects a KEEPALIVE message from the remote peer. Established — BGP connection is established with remote peer. AppDirector can exchange UPDATE messages with it. Remote AS Remote autonomous system number. Peer Identifier IP address identifies remote peer for current BGP connection. Local Address AppDirector IP interface address used as source IP address for BGP connection. Local Port TCP source port number used by AppDirector for BGP connection to remote peer. In/Out Updates The number of BGP UPDATE messages transmitted on this connection. This object should be initialized to zero (0) when the connection is established. In/Out Total Messages The total number of messages received from/transmitted to the remote peer on this connection. This should be initialized to zero when the connection is established. Last Error The last error code and subcode seen by this peer on this connection. If no error has occurred, this field is zero. Otherwise, the first byte of this two byte OCTET STRING contains the error code, and the second byte contains the subcode. FSM Established Transitions The total number of times the BGP FSM transitioned into the established state. FSM Established Time This timer indicates how long (in seconds) this peer has been in the established state or how long since this peer was last in the established state. It is set to zero when a new peer is configured or the router is booted. Connect Retry Interval (sec) Interval in which AppDirector tries to re-establish BGP connection with remote peer after TCP failure event. Hold Time (sec) Defines hold time offered by AppDirector during a BGP connection establishment. During this time, a peer must receive a keepalive or an update message from the remote peer to consider the BGP connection active. Zero (0) indicates that keepalive messages is not sent by AppDirector and AppDirector does not expect keepalive messages from the remote peer. Keep Alive Time (sec) Time interval used by AppDirector for sending keepalive messages to the remote peer. Zero (0) indicates that keep alive messages are not sent. Hold Time Configured Time interval in seconds for the Hold Time configured for this BGP speaker with this peer. This value is placed in an OPEN message sent to this peer by this BGP speaker, and is compared with the Hold Time field in an OPEN message received from the peer when determining the Hold Time (bgpPeerHoldTime) with the peer. This value must not be less than three seconds if it is not zero (0) in which case the Hold Time is NOT to be established with the peer. The suggested value for this timer is 90 seconds Keep Alive Configured Time interval in seconds for the KeepAlive timer configured for this BGP speaker with this peer. The value of this object only determines the KEEPALIVE messages' frequency relative to the value specified in bgpPeerHoldTimeConfigured; the actual time interval for the KEEPALIVE messages is indicated by bgpPeerKeepAlive. A reasonable maximum value for this timer would be configured to be one third of that of bgpPeerHoldTimeConfigured. If the value of this object is zero (0), no periodical KEEPALIVE messages are sent to the peer after the BGP connection has been established. The suggested value for this timer is 30 seconds. In Update Elapsed Time (sec.) Elapsed time in seconds since the last BGP UPDATE message was received from the peer. Each time bgpPeerInUpdates is incremented, the value of this object is set to zero (0) 4. Click Set.