CISCO-IPSEC-SIGNALING-MIB
The CISCO-IPSEC-SIGNALING-MIB monitors generic IPsec and FC-SP control protocol activity (such as IKE and KINK) on Cisco hardware to track control tunnel states, peer associations, and signaling failures. It provides real-time statistics and historical data for Phase 1 and Phase 2 tunnel establishment, along with specific counters for detecting security violations and protocol errors across multiple signaling implementations.
Imported Objects
Objects
126 total| Object Name |
|---|
ciscoIPsecSignalingMIB MODULE-IDENTITY .1.3.6.1.4.1.9.9.438 |
ciscoIPsecSigMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.438.0 |
ciscoIpsSgTunnelStart NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.438.0.1 |
ciscoIpsSgTunnelStop NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.438.0.2 |
ciscoIpsSgSysFailure NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.438.0.3 |
ciscoIpsSgCertCrlFailure NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.438.0.4 |
ciscoIPsecSigMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.438.1 |
cisgIpsSgCurrentActivity OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.438.1.1 |
cisgIpsSgGlobalStatsTable SEQUENCE OF CisgIpsSgGlobalStatsEntry .1.3.6.1.4.1.9.9.438.1.1.1 |
cisgIpsSgGlobalStatsEntry CisgIpsSgGlobalStatsEntry .1.3.6.1.4.1.9.9.438.1.1.1.1 |
cisgIpsSgProtocol CIPsecControlProtocol (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.1.1.1 |
cisgIpsSgGlobalActiveTunnelsro Gauge32 .1.3.6.1.4.1.9.9.438.1.1.1.1.2 |
cisgIpsSgGlobalPreviousTunnelsro Counter64 UNITS "SAs" .1.3.6.1.4.1.9.9.438.1.1.1.1.3 |
cisgIpsSgGlobalInOctetsro Counter64 UNITS "Octets" .1.3.6.1.4.1.9.9.438.1.1.1.1.4 |
cisgIpsSgGlobalInPktsro Counter64 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.1.1.1.5 |
cisgIpsSgGlobalInDropPktsro Counter64 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.1.1.1.6 |
cisgIpsSgGlobalInNotifysro Counter64 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.1.1.7 |
cisgIpsSgGlobalInP2SaDelReqsro Counter64 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.1.1.8 |
cisgIpsSgGlobalOutOctetsro Counter64 UNITS "Octets" .1.3.6.1.4.1.9.9.438.1.1.1.1.9 |
cisgIpsSgGlobalOutPktsro Counter64 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.1.1.1.10 |
cisgIpsSgGlobalOutDropPktsro Counter64 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.1.1.1.11 |
cisgIpsSgGlobalOutNotifysro Counter64 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.1.1.12 |
cisgIpsSgGlobalOutP2SaDelReqsro Counter64 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.1.1.13 |
cisgIpsSgGlobalInitTunnelsro Counter64 UNITS "SAs" .1.3.6.1.4.1.9.9.438.1.1.1.1.14 |
cisgIpsSgGlobalInitTunnelFailsro Counter64 UNITS "SAs" .1.3.6.1.4.1.9.9.438.1.1.1.1.15 |
cisgIpsSgGlobalRespTunnelsro Counter64 UNITS "SAs" .1.3.6.1.4.1.9.9.438.1.1.1.1.16 |
cisgIpsSgGlobalRespTunnelFailsro Counter64 UNITS "SAs" .1.3.6.1.4.1.9.9.438.1.1.1.1.17 |
cisgIpsSgGlobalSysCapFailsro Counter64 UNITS "Failures" .1.3.6.1.4.1.9.9.438.1.1.1.1.18 |
cisgIpsSgGlobalAuthFailsro Counter64 UNITS "Failures" .1.3.6.1.4.1.9.9.438.1.1.1.1.19 |
cisgIpsSgGlobalDecryptFailsro Counter64 UNITS "Failures" .1.3.6.1.4.1.9.9.438.1.1.1.1.20 |
cisgIpsSgGlobalHashValidFailsro Counter64 UNITS "Failures" .1.3.6.1.4.1.9.9.438.1.1.1.1.21 |
cisgIpsSgGlobalBadTunnelRefsro Counter64 UNITS "Failures" .1.3.6.1.4.1.9.9.438.1.1.1.1.22 |
cisgIpsSgGlobalInP1SaDelReqsro Counter64 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.1.1.23 |
cisgIpsSgGlobalOutP1SaDelReqsro Counter64 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.1.1.24 |
cisgIpsSgTunnelTable SEQUENCE OF CisgIpsSgTunnelEntry .1.3.6.1.4.1.9.9.438.1.1.2 |
cisgIpsSgTunnelEntry CisgIpsSgTunnelEntry .1.3.6.1.4.1.9.9.438.1.1.2.1 |
cisgIpsSgTunIndex CIPsecPhase1TunnelIndex (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.1 |
cisgIpsSgTunLocalTypero CIPsecPhase1PeerIdentityType (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.2 |
cisgIpsSgTunLocalValuero SnmpAdminString .1.3.6.1.4.1.9.9.438.1.1.2.1.3 |
cisgIpsSgTunLocalAddressTypero CIPsecPhase1PeerIdentityType (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.4 |
cisgIpsSgTunLocalAddressro SnmpAdminString .1.3.6.1.4.1.9.9.438.1.1.2.1.5 |
cisgIpsSgTunLocalNamero SnmpAdminString .1.3.6.1.4.1.9.9.438.1.1.2.1.6 |
cisgIpsSgTunRemoteTypero CIPsecPhase1PeerIdentityType (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.7 |
cisgIpsSgTunRemoteValuero SnmpAdminString .1.3.6.1.4.1.9.9.438.1.1.2.1.8 |
cisgIpsSgTunRemoteAddressTypero CIPsecPhase1PeerIdentityType (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.9 |
cisgIpsSgTunRemoteAddressro SnmpAdminString .1.3.6.1.4.1.9.9.438.1.1.2.1.10 |
cisgIpsSgTunRemoteNamero SnmpAdminString .1.3.6.1.4.1.9.9.438.1.1.2.1.11 |
cisgIpsSgTunEncryptAlgoro CIPsecEncryptAlgorithm (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.12 |
cisgIpsSgTunEncryptKeySizero CIPsecEncryptionKeySize UNITS "Bits" .1.3.6.1.4.1.9.9.438.1.1.2.1.13 |
cisgIpsSgTunHashAlgoro CIPsecIkeHashAlgorithm (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.14 |
cisgIpsSgTunAuthMethodro CIPsecIkeAuthMethod (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.15 |
cisgIpsSgTunLifeTimero Unsigned32 .1.3.6.1.4.1.9.9.438.1.1.2.1.16 |
cisgIpsSgTunActiveTimero TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.17 |
cisgIpsSgTunInOctetsro Counter32 UNITS "Octets" .1.3.6.1.4.1.9.9.438.1.1.2.1.18 |
cisgIpsSgTunInPktsro Counter32 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.1.2.1.19 |
cisgIpsSgTunInDropPktsro Counter32 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.1.2.1.20 |
cisgIpsSgTunInNotifysro Counter32 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.2.1.21 |
cisgIpsSgTunOutOctetsro Counter32 UNITS "Octets" .1.3.6.1.4.1.9.9.438.1.1.2.1.22 |
cisgIpsSgTunOutPktsro Counter32 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.1.2.1.23 |
cisgIpsSgTunOutDropPktsro Counter32 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.1.2.1.24 |
cisgIpsSgTunOutNotifysro Counter32 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.2.1.25 |
cisgIpsSgTunOutP2SaDelReqsro Counter32 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.1.2.1.26 |
cisgIpsSgTunStatusro CIPsecTunnelStatus (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.1.2.1.27 |
cisgIpsSgTunActionrw Enumeration .1.3.6.1.4.1.9.9.438.1.1.2.1.28 |
cisgIpsSgPeerAssociations OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.438.1.2 |
cisgIpsSgHistory OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.438.1.3 |
cisgIpsSgHistGlobal OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.438.1.3.1 |
cisgIpsSgHistGlobalCntl OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.438.1.3.1.1 |
cisgIpsSgHistTableSizerw Unsigned32 .1.3.6.1.4.1.9.9.438.1.3.1.1.1 |
cisgIpsSgTunnelHistTable SEQUENCE OF CisgIpsSgTunnelHistEntry .1.3.6.1.4.1.9.9.438.1.3.2 |
cisgIpsSgTunnelHistEntry CisgIpsSgTunnelHistEntry .1.3.6.1.4.1.9.9.438.1.3.2.1 |
cisgIpsSgTunHistIndex Unsigned32 .1.3.6.1.4.1.9.9.438.1.3.2.1.1 |
cisgIpsSgTunHistTermReasonro Enumeration .1.3.6.1.4.1.9.9.438.1.3.2.1.2 |
cisgIpsSgTunHistActiveIndexro CIPsecPhase1TunnelIndex (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.3 |
cisgIpsSgTunHistPeerLocalTypero CIPsecPhase1PeerIdentityType (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.4 |
cisgIpsSgTunHistPeerLocalValuero SnmpAdminString .1.3.6.1.4.1.9.9.438.1.3.2.1.5 |
cisgIpsSgTunHistPeerIntIndexro Unsigned32 .1.3.6.1.4.1.9.9.438.1.3.2.1.6 |
cisgIpsSgTunHistPeerRemoteTypero CIPsecPhase1PeerIdentityType (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.7 |
cisgIpsSgTunHistPeerRemoteValuero SnmpAdminString .1.3.6.1.4.1.9.9.438.1.3.2.1.8 |
cisgIpsSgTunHistLocalAddrTypero CIPsecPhase1PeerIdentityType (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.9 |
cisgIpsSgTunHistLocalAddrro SnmpAdminString .1.3.6.1.4.1.9.9.438.1.3.2.1.10 |
cisgIpsSgTunHistLocalNamero SnmpAdminString .1.3.6.1.4.1.9.9.438.1.3.2.1.11 |
cisgIpsSgTunHistRemoteAddrTypero CIPsecPhase1PeerIdentityType (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.12 |
cisgIpsSgTunHistRemoteAddrro SnmpAdminString .1.3.6.1.4.1.9.9.438.1.3.2.1.13 |
cisgIpsSgTunHistRemoteNamero SnmpAdminString .1.3.6.1.4.1.9.9.438.1.3.2.1.14 |
cisgIpsSgTunHistEncryptAlgoro CIPsecEncryptAlgorithm (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.15 |
cisgIpsSgTunHistEncryptKeySizero CIPsecEncryptionKeySize UNITS "Bits" .1.3.6.1.4.1.9.9.438.1.3.2.1.16 |
cisgIpsSgTunHistHashAlgoro CIPsecIkeHashAlgorithm (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.17 |
cisgIpsSgTunHistAuthMethodro CIPsecIkeAuthMethod (CISCO-IPSEC-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.18 |
cisgIpsSgTunHistLifeTimero Unsigned32 .1.3.6.1.4.1.9.9.438.1.3.2.1.19 |
cisgIpsSgTunHistStartTimero TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.20 |
cisgIpsSgTunHistActiveTimero TimeInterval (SNMPv2-TC) .1.3.6.1.4.1.9.9.438.1.3.2.1.21 |
cisgIpsSgTunHistInOctetsro Counter64 UNITS "Octets" .1.3.6.1.4.1.9.9.438.1.3.2.1.22 |
cisgIpsSgTunHistInPktsro Counter64 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.3.2.1.23 |
cisgIpsSgTunHistInDropPktsro Counter64 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.3.2.1.24 |
cisgIpsSgTunHistInNotifysro Counter64 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.3.2.1.25 |
cisgIpsSgTunHistInP2SaDelReqsro Counter64 UNITS "Notification Payloads" .1.3.6.1.4.1.9.9.438.1.3.2.1.26 |
cisgIpsSgTunHistOutOctetsro Counter64 UNITS "Octets" .1.3.6.1.4.1.9.9.438.1.3.2.1.27 |
cisgIpsSgTunHistOutPktsro Counter64 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.3.2.1.28 |
cisgIpsSgTunHistOutDropPktsro Counter64 UNITS "Packets" .1.3.6.1.4.1.9.9.438.1.3.2.1.29 |
CISCO-IPSEC-SIGNALING-MIB Technical Reference Overview
The CISCO-IPSEC-SIGNALING-MIB SNMP MIB module published by Cisco defines 126 managed OID objects, including 99 scalar/column metrics, 4 SNMP tables, and 4 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.438. Key tabular structures include cisgIpsSgGlobalStatsTable, cisgIpsSgTunnelTable, cisgIpsSgTunnelHistTable, cisgIpsSgFailTable. Monitored SNMP traps/notifications include ciscoIpsSgTunnelStart, ciscoIpsSgTunnelStop, ciscoIpsSgSysFailure, ciscoIpsSgCertCrlFailure.
Key OID Definitions in CISCO-IPSEC-SIGNALING-MIB
.1.3.6.1.4.1.9.9.438This MIB Module models status, performance and failures of a protocol with the generic characteristics of signalling protocols used with IPsec and FC-SP protocols. Examples of such protocols include IKE, KINK, etc. This MIB views the common attributes of such protocols. Signaling protocols are also referred in this document as 'Control Protocols', since they perform session control. This MIB is an attempt to capture the generic aspects of the signaling activity. The protocol-specific aspects of a signaling protocol still need to be captured in a protocol-specific MIB (e.g., CISCO-IKE-FLOW-MIB, etc.). Acronyms The following acronyms are used in this document: IPsec: Secure IP Protocol VPN: Virtual Private Network ISAKMP: Internet Security Association and Key Exchange Protocol IKE: Internet Key Exchange Protocol SA: Security Association (ref: rfc2408). Phase 1 Tunnel: An ISAKMP SA can be regarded as representing a flow of ISAKMP/IKE traffic. Hence an ISAKMP is referred to as a 'Phase 1 Tunnel' in this document. Control Tunnel: Another term for a Phase 1 Tunnel. Phase 2 Tunnel: An instance of a non-ISAKMP SA bundle in which all the SA share the same proxy identifiers (IDii,IDir) protect the same stream of application traffic. Such an SA bundle is termed a 'Phase 2 Tunnel'. Note that a Phase 2 tunnel may comprise different SA bundles and different number of SA bundles at different times (due to key refresh). History of the MIB A precursor to this MIB was the IPsec Flow Monitor MIB, which combined the objects pertaining to IKE and IPsec (Phase-2) into a single MIB module. Furthermore, the MIB supported only one signaling protocol, IKEv1, in addition to manual keying. The MIB was written by Tivoli and implemented in IBM Nways routers in 1999. During late 1999, Cisco adopted the MIB and together with Tivoli publised the IPsec Flow Monitor MIB in IETF IPsec WG in draft-ietf-ipsec-flow-monitoring-mib-00.txt. In 2000, the MIB was Cisco-ized and implemented as CISCO-IPSEC-FLOW-MONITOR-MIB in IOS and VPN3000 platforms. With the evolution of IKEv2, the MIB was modified and presented to the IPsec WG again in May 2003 in draft-ietf-ipsec-flow-monitoring-mib-02.txt. With the emergence to multiple signaling protocols, it has further evolved to define separate set of MIB modules to instrument IPsec signaling alone. Thus, this MIB module is now the generic IPsec signaling MIB. Overview of MIB The MIB contains major groups of objects which are used to manage the generic aspects of IPsec signaling. These groups include a global statistics, control tunnel table, Peer association group, control tunnel history group, signaling failure group and notification group. The global statistics, tunnel table and peer association groups aid in the real-time monitoring of IPsec signaling activity. The History group is to aid applications that do trending analysis. The Failure group is to enable an operator to do troubleshooting and debugging. Further, counters are supported to aid detection of potential security violations. The notifications are modeled as generic IPsec control notifications and are parameterized by the identity of the specific signaling protocol which caused the notification to be issued.
.1.3.6.1.4.1.9.9.438.1.1.1This Signaling Protocol global statistics table. There is one row in the following table for each signaling protocol implemented by the managed entity. There is no row corresponding to the instance 'cpNone'. If the managed entity implements more than one signaling protocol, the aggregate statistics across all the supported signaling protocols must be computed by the network management station manually; in other words, there is no conceptual row in this table corresponding to 'all signaling protocols'.
.1.3.6.1.4.1.9.9.438.1.1.2This table lists active Phase-1 control tunnels. There is one entry in this table for each active Control Tunnel.
.1.3.6.1.4.1.9.9.438.1.3.2The control tunnel History Table. This table lists all instances of control tunnels that were successfully established but which are no longer in operation. An entry transitions to this table from the active tunnel table ('cisgIpsSgTunnelTable') into this table after it expires, is aborted or terminated. This table is conceptually a sliding window in which only the last 'N' entries are maintained, where 'N' is the value of the object 'cisgIpsSgHistTableSize'. If the value of 'cisgIpsSgHistTableSize' is 0, archiving of entries in this table is disabled.
.1.3.6.1.4.1.9.9.438.1.4.2This is the control tunnel Table and is implemented as a sliding window in which only the last 'N' entries are maintained. The maximum number of entries is specified by the object 'cisgIpsSgFailTableSize'. The failure records are catalogued under each signaling protocol type; that is, the first index of this table is the signaling protocol identifier ('cisgIpsSgProtocol'). The second index ('cisgIpsSgFailIndex') identifies the failure record uniquely in the subcategory. Should a failure be identified before the signaling protocol itself has been identified by the managed entity, the failure record will be classified under 'cpUnknown'.
.1.3.6.1.4.1.9.9.438.0.1This notification is generated when an control tunnel becomes active.
.1.3.6.1.4.1.9.9.438.0.2This notification is generated when an control tunnel becomes inactive.
.1.3.6.1.4.1.9.9.438.0.3This notification is generated when the processing for an control Tunnel experiences an system capacity error.
.1.3.6.1.4.1.9.9.438.0.4This notification is generated when the processing for an control Tunnel experiences a Certificate or a Certificate validation (CRL or OCSP) related error.
.1.3.6.1.4.1.9.9.438.1.3.1.1.1The window size of the control tunnel History Tables. The control tunnel history table is implemented as a sliding window in which at most the last 'cisgIpsSgHistTableSize' entries are maintained. This object is, hence, used to control the size of the tunnel history table. An implementation may choose suitable values for this element based on the available resources. If an SNMP SET request specifies a value outside this window for this element, in appropriate SNMP error code should be returned. Setting this value to zero is equivalent to deleting all conceptual rows in the archiving table ('cisgIpsSgTunnelHistTable') and disabling the archiving of entries in the tables.
.1.3.6.1.4.1.9.9.438.1.4.1.1.1The window size of the Internet Key Exchange Failure Tables. The Failure Table is implemented as a sliding window in which only the last 'cisgIpsSgFailTableSize' entries are maintained. This object is used specify the number of entries which will be maintained in the control tunnel Failure Table. An implementation may choose suitable minimum and maximum values for this element based on the local policy and available resources. If an SNMP SET request specifies a value outside this window for this element, an appropriate SNMP error code must be returned. Setting this value to zero is equivalent to deleting all conceptual rows in the archiving tables ('cisgIpsSgFailTable') and disabling the archiving of entries in this table.
.1.3.6.1.4.1.9.9.438.1.5.1This object acts as the knob that controls the the administrative state of sending any notification defined in this MIB module. That is, a particular notification 'foo' defined in this MIB module is enabled if and only if the expression cisgIpsSgNotifCntlAllNotifs && cisgIpsSgNotifCntl<foo> evaluates to 'true'.
.1.3.6.1.4.1.9.9.438.1.5.2This object defines the administrative state of sending the Control Tunnel Start notification. If the value of this object is 'true', the issuing of the notification 'cisgIpsSgTunnelStart' is enabled.
.1.3.6.1.4.1.9.9.438.1.5.3This object defines the administrative state of sending the Control Tunnel Stop notification. If the value of this object is 'true', the issuing of the notification 'cisgIpsSgTunnelStop' is enabled.
.1.3.6.1.4.1.9.9.438.1.5.4This object defines the administrative state of sending the System Failure notification. If the value of this object is 'true', the issuing of the notification 'ciscoIpsSgSysFailure' is enabled.
.1.3.6.1.4.1.9.9.438.1.5.5This object defines the administrative state of sending the Certificate/CRL Failure notification. If the value of this object is 'true', the issuing of the notification 'ciscoIpsSgCertCrlFailure' is enabled.
.1.3.6.1.4.1.9.9.438.1.1.1.1Each entry contains the global statistics pertaining to a specific signaling protocol.
.1.3.6.1.4.1.9.9.438.1.1.1.1.1The identity of the signaling protocol used by the control tunnel corresponding to this conceptual row.
.1.3.6.1.4.1.9.9.438.1.1.1.1.2The number of currently active Phase-1 control tunnels.
.1.3.6.1.4.1.9.9.438.1.1.1.1.3High capacity counter to accumulate the total number of Phase-1 control tunnels that are no longer active.
.1.3.6.1.4.1.9.9.438.1.1.1.1.4The total number of octets received by all currently and previously active Phase-1 Control Tunnels.
.1.3.6.1.4.1.9.9.438.1.1.1.1.5The total number of packets received by all currently and previously active Phase-1 Control Tunnels.
.1.3.6.1.4.1.9.9.438.1.1.1.1.6The total number of packets which were dropped during receive processing by all currently and previously active Phase-1 Control Tunnels.
.1.3.6.1.4.1.9.9.438.1.1.1.1.7The total number of notification payloads received by all currently and previously active Phase-1 Control Tunnels.
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.
The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.
The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.
SNMP MIB module
The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.
The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.