|
Object and OID |
Access |
Description |
|---|---|---|
|
extremeBgp4V2PeerTable 1.3.6.1.4.1.1916.1.51.1.2 |
None |
This entity contains information of the BGP4 peer table. |
|
extremeBgp4V2PeerEntry 1.3.6.1.4.1.1916.1.51.1.2.1 |
None |
An entry containing information about the BGP4 peer. |
|
extremeBgp4V2PeerInstance 1.3.6.1.4.1.1916.1.51.1.2.1.1 |
None |
The Routing Instance Index. Some BGP implementations permit the creation of multiple instances of a BGP routing process. An example includes routers running BGP/MPLS IP Virtual Private Networks Implementations that do not support multiple routing instances should return 1 for this object. |
|
extremeBgp4V2PeerLocalAddrType 1.3.6.1.4.1.1916.1.51.1.2.1.2 |
Read-Only |
The address family of the local end of the peering session. The possible values are:
|
|
extremeBgp4V2PeerLocalAddr 1.3.6.1.4.1.1916.1.51.1.2.1.3 |
Read-Only |
The local IPv6 address of this entry's BGP connection |
|
extremeBgp4V2PeerRemoteAddrType 1.3.6.1.4.1.1916.1.51.1.2.1.4 |
None |
The address family of the remote end of the peering session. The possible values are:
|
|
extremeBgp4V2PeerRemoteAddr 1.3.6.1.4.1.1916.1.51.1.2.1.5 |
None |
The remote IPV6 address of this entry's BGP peer. |
|
extremeBgp4V2PeerLocalPort 1.3.6.1.4.1.1916.1.51.1.2.1.6 |
Read-Only |
The local port for the TCP connection between the BGP peers. |
|
extremeBgp4V2PeerLocalAs 1.3.6.1.4.1.1916.1.51.1.2.1.7 |
Read-Only |
Some implementations of BGP can represent themselves as multiple ASes. This is the AS that this peering session is representing itself as to the remote peer. |
|
extremeBgp4V2PeerLocalIdentifier 1.3.6.1.4.1.1916.1.51.1.2.1.8 |
Read-Only |
The BGP Identifier of the local system for this peering session. It is REQUIRED that all extremeBgp4V2PeerLocalIdentifier values for the same extremeBgp4V2PeerInstance be identical. This is the Router ID. |
|
extremeBgp4V2PeerRemotePort 1.3.6.1.4.1.1916.1.51.1.2.1.9 |
Read-Only |
The remote port for the TCP connection between the BGP peers. Note that the objects extremeBgp4V2PeerLocalAddr, extremeBgp4V2PeerLocalPort, extremeBgp4V2PeerRemoteAddr, and extremeBgp4V2PeerRemotePort provide the appropriate reference to the standard MIB TCP connection table, or even the IPv6 TCP MIB as in RFC 4022. |
|
extremeBgp4V2PeerRemoteAs 1.3.6.1.4.1.1916.1.51.1.2.1.10 |
Read-Only |
The remote autonomous system number received in the BGP OPEN message. |
|
extremeBgp4V2PeerRemoteIdentifier 1.3.6.1.4.1.1916.1.51.1.2.1.11 |
Read-Only |
The BGP Identifier of this entry's remote BGP peer. This entry should be 0:0:0:0:0:0:0:0 unless the extremeBgp4V2PeerState is in the openconfirm or the established state. |
|
extremeBgp4V2PeerAdminStatus 1.3.6.1.4.1.1916.1.51.1.2.1.12 |
Read-Only |
Whether the BGP FSM for this remote peer is halted or running. The BGP FSM for a remote peer is halted after processing a Stop event. Similarly, it is in the running state after a Start event. The extremeBgp4V2PeerState will generally be in the idle state when the FSM is halted, although some extensions such as Graceful Restart will leave the peer in the Idle state but with the FSM running. The supported values are:
|
|
extremeBgp4V2PeerState 1.3.6.1.4.1.1916.1.51.1.2.1.13 |
Read-Only |
The BGP peer connection state. |
|
extremeBgp4V2PeerDescription 1.3.6.1.4.1.1916.1.51.1.2.1.14 |
Read-Only |
A user configured description identifying this peer. When this object is not an empty string, this object SHOULD contain a description that is unique within a given BGP instance for this peer. |