All MIBs › FORCE10-BGP4-V2-MIB › f10BgpM2CfgPeerError
f10BgpM2CfgPeerError
Module: FORCE10-BGP4-V2-MIB
OID (symbolic): FORCE10-BGP4-V2-MIB::f10BgpM2CfgPeerError
OID (numeric): 1.3.6.1.4.1.6027.20.1.2.8.3.1.10
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: This value indicates the current error status of the row denoting the configured error status.
If this row is still under creation (has not been activated f10BgpM2CfgPeerRowEntryStatus), then this instance will be set to not-activated (1).
At the point that the row is activated, f10BgpM2CfgPeerError will reflect the error status of the row data itself. If there is another session already activated with the same local and remote addresses as denoted by {f10BgpM2CfgPeerLocalAddrType, f10BgpM2CfgPeerLocalAddr, f10BgpM2CfgPeerRemoteAddr}, then the value of this will be set to err-duplicate-peering-session (2).
If this row is associated with a peer session whose initialization has been attempted, the value will be set to activated (3) (and, f10BgpM2PeerCfgPeerEntry will be set to the row instance of the entry in the f10BgpM2PeerTable which reflects the state of the peering session).
Note that this object only reflects the error as a function of the attempted activation of this row as containing data for a bgp peering session. The actual state of the session at the point of any protocol exchange or session state machine initiation is reflected in the f10BgpM2PeerTable row instance (as reflected through f10BgpM2CfgPeerPeerEntry) associated with this row instance.
What is f10BgpM2CfgPeerError?
Reports this configuration row's activation status: unknown(0), notActivated(1) while the row is still being built, errDuplicatePeeringSession(2) if another active session already uses the same local/remote address pair, or activated(3) once the peering session has actually been initialized — an admin's first check when a newly-added peer refuses to come up.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6027.20.1.2.8.3.1.10 snmpwalk -v2c -c public <target> FORCE10-BGP4-V2-MIB::f10BgpM2CfgPeerError
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.6027.20.1.2.8.3.1.10.1 snmpget -v2c -c public <target> FORCE10-BGP4-V2-MIB::f10BgpM2CfgPeerError.1
Start monitoring Dell Force10 (Dell Networking OS/FTOS) switch/router (BGP4 routing) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the FORCE10-BGP4-V2-MIB::f10BgpM2CfgPeerError OID value, configure state conditions and alerts, and monitor any Dell Force10 (Dell Networking OS/FTOS) switch/router (BGP4 routing) from a single console.
OID Breakdown
Upper-level ancestors (13 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.6027 | dellNet | DELL-NETWORKING-SMI |
| 1.3.6.1.4.1.6027.20 | dellNetExperiment | DELL-NETWORKING-SMI |
| 1.3.6.1.4.1.6027.20.1 | dellNetBgpM2 | DELL-NETWORKING-BGP4-V2-MIB |
| 1.3.6.1.4.1.6027.20.1.2 | dellNetBgpM2Peer | DELL-NETWORKING-BGP4-V2-MIB |
| 1.3.6.1.4.1.6027.20.1.2.8 | dellNetBgpM2PeerConfiguration | DELL-NETWORKING-BGP4-V2-MIB |
| 1.3.6.1.4.1.6027.20.1.2.8.3 | dellNetBgpM2CfgPeerTable | DELL-NETWORKING-BGP4-V2-MIB |
| 1.3.6.1.4.1.6027.20.1.2.8.3.1 | dellNetBgpM2CfgPeerEntry | DELL-NETWORKING-BGP4-V2-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6027.20.1.2.8.3.1.10 | f10BgpM2CfgPeerError | FORCE10-BGP4-V2-MIB |