BGP_1.3.6.1.4.1.2011.5.25.177.1.3.9 hwBgpPeerEstablished

Description

BGP/2/HWESTABLISHED:OID [oid] The BGP FSM enters the Established state. (InstanceId=[gauge], Afi=[integer], Safi=[integer], PeerType=[integer], PeerRemoteAddr=[binary], PeerLastError=[octet], PeerState=[integer])

Indicates that this trap was generated when the BGP FSM was in the Established state.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.177.1.3.9	Major	communicationsAlarm(2)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
InstanceId	Indicates the index of the instance to which the peer belongs.
Afi	Indicates the address family: 1: ipv4 2: ipv6 25: vpls 196: l2vpn
Safi	Indicates the sub-address family: 1: unicast 2: multicast 4: mpls 5: mvpn 65: vpls 66: mdt 70: evpn 128: vpn 245: tunnel-encap-ext
PeerType	Indicates the address type of the peer: 1: ipv4 2: ipv6
PeerRemoteAddr	Indicates the address of the peer.
PeerLastError	Indicates the error code of the BGP Notification when the neighbor relationship is disconnected for the last time. The value is expressed in the format of [ErrorCode][ErrorSubCode]. [ErrorCode] refers to the error code and [ErrorSubCode] refers to the error subcode. Take the integer 35 as an example, figure 3 is the error code and figure 5 is the error subcode. For detailed information about the error code, refer to BGP Error Code. If the value is 0, it indicates that no error occurs.
PeerState	Indicates the status of the BGP peer. Idle: indicates that BGP denies any request of entering. This is the initiatory status of BGP. Upon receiving a Start event, BGP initiates a TCP connection to the remote BGP peer, starts the ConnectRetry Timer with the initial value, detects a TCP connection initiated by the remote BGP peer, and changes its state to Connect. Connect: indicates that BGP performs other actions after the TCP connection is set up. If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent. If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to detect a TCP connection initiated by the remote peer, and changes its state to Active. If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value, initiates a TCP connection to the remote BGP peer, and stays in the Connect state. Active: indicates that BGP tries to set up TCP connection. This is the intermediate status of BGP. If the TCP connection succeeds, BGP stops the ConnectRetry Timer, sends an Open message to the remote peer, and changes its state to OpenSent. If the ConnectRetry Timer has expired before a TCP connection is established, BGP restarts the timer with the initial value and changes its state to Connect. If BGP initiates a TCP connection with an unknown IP address, the TCP connection fails. When this occurs, BGP restarts the ConnectRetry Timer with the initial value and stays in the Active state. OpenSent: indicates that BGP has sent one Open message to its peer and waits for the other Open message from the peer. If there are no errors in the Open message received, BGP changes its state to OpenConfirm. If there are errors in the Open message received, BGP sends a Notification message to the remote peer and changes its state to Idle. If the TCP connection fails, BGP restarts the ConnectRetry Timer with the initial value, continues to detect a TCP connection initiated by the remote peer, and changes its state to Active. OpenConfirm: indicates that BGP waits for a Notification message or a Keepalive message. If BGP receives a Notification message, or the TCP connection fails, BGP changes its state to Idle. If BGP receives a Keepalive message, BGP changes its state to Established. Established: indicates that BGP peers can exchange Update, Notification and Keepalive packets. If BGP receives an Update or a Keepalive message, its state stays in Established. If BGP receives a Notification message, BGP changes its state to Idle.

Impact on the System

The BGP neighbor relationship can be normally established.

Possible Causes

The BGP neighbor relationship was established.

Procedure

This alarm message is informational only, and no action is required.

Related Information

BGP_1.3.6.1.4.1.2011.5.25.177.1.3.10 hwBgpPeerBackwardTransition