jnxBgpM2CfgPeerError
jnx Bgp M2 Config Peer Error
1.3.6.1.4.1.2636.5.1.1.2.8.3.1.11
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 jnxBgpM2CfgPeerRowEntryStatus), then this instance will be set to not-activated (1). At the point that the row is activated, jnxBgpM2CfgPeerError 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 {jnxBgpM2CfgPeerLocalAddrType, jnxBgpM2CfgPeerLocalAddr, jnxBgpM2CfgPeerRemoteAddr, jnxBgpM2CfgPeerRemotePort}, 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, jnxBgpM2PeerCfgPeerEntry will be set to the row instance of the entry in the jnxBgpM2PeerTable 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 jnxBgpM2PeerTable row instance (as reflected through jnxBgpM2CfgPeerPeerEntry) associated with this row instance.
Back to BGP4-V2-MIB-JUNIPER MIB page.
IPHost Network monitor uses SNMP for monitoring health and availability of devices and applications in your network. You can send a SNMP Set to any remote device to monitor a specific SNMP object (CPU, Memory, Disk, Server Temperature, RAID failures, IO statistics, connection counts, error and much more).