BGP Peer Table. This table contains information about the connections for BGP peers.
The indexes of the table are hwBgpPeerInstanceId, hwBgpPeerAddrFamilyAfi, hwBgpPeerAddrFamilySafi, hwBgpPeerType, hwBgpPeerIPAddr.
|
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
|---|---|---|---|---|---|
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.1 |
hwBgpPeerNegotiatedVersion |
Unsigned32 |
read-only |
The version negotiated with the remote BGP peer. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.2 |
hwBgpPeerRemoteAs |
Unsigned32 |
read-only |
The AS number of the remote BGP peer. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.4 |
hwBgpPeerRemoteAddr |
OCTET STRING{(0,255)} |
read-only |
The IP address of the remote BGP peer. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.5 |
hwBgpPeerState |
INTEGER{idle(1),connect(2),active(3),opensent(4),openconfirm(5),established(6)} |
read-only |
The status of the remote BGP peer, including: 1: Idle(1) 2: Connect(2) 3: Active(3) 4: Opensent(4) 5: Openconfirm(5) 6: Established(6) |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.6 |
hwBgpPeerFsmEstablishedCounter |
Unsigned32 |
read-write |
The Counter That Records the Times the Remote BGP Peer Is Correctly Connected The counter is increased by one if the remote BGP peer is correctly connected once. The counter could be set to zero. |
The actually supported access is read-only. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.7 |
hwBgpPeerFsmEstablishedTime |
Gauge32 |
read-only |
The counter that records the times the remote BGP peer is correctly connected. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.8 |
hwBgpPeerGRStatus |
INTEGER{peerNotBeingHelped(1),peerRestarting(2),peerFinishRestart(3),peerHelping(4)} |
accessible-for-notify |
Graceful restart status of the BGP peer, including: 1: peerNotBeingHelped, indicating that the BGP peer will not be helped during restarting. 2: peerRestarting, indicating that the BGP peer is detected restarting. 3: peerFinishRestart, indicating that the BGP peer finishes the latest GR. 4: peerHelping, indicating that the BGP peer is helping the local end to perform GR. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.9 |
hwBgpPeerLastError |
OCTET STRING |
read-only |
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. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.10 |
hwBgpPeerUnAvaiReason |
Unsigned32 |
read-only |
Bgp peer down reason including: 1: Configuration lead peer down(1) 2: Receive notification(2) 3: Receive error packet(3) 4: Hold timer expire(4) 5: Remote peer not reachable(5) 6: Direct connect-interface down(6) 7: Route limit(7) |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.11 |
hwBgpPeerAdminStatus |
INTEGER{stop(1),start(2)} |
read-only |
The desired state of the BGP connection. A transition from 'stop' to 'start' will cause the BGP Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication. |
This object is implemented as defined in the corresponding MIB files. |
|
1.3.6.1.4.1.2011.5.25.177.1.1.2.1.12 |
hwBgpPeerDescription |
OCTET STRING{(0,255)} |
accessible-for-notify |
The description of the BGP peer. |
This object is implemented as defined in the corresponding MIB files. |