Home/Catalog/CISCO-IPSEC-FLOW-MONITOR-MIB

CISCO-IPSEC-FLOW-MONITOR-MIB

AI MIB Summary

The CISCO-IPSEC-FLOW-MONITOR-MIB monitors IPSec Virtual Private Network Security Associations, IKE negotiation phases (Main and Quick Mode), and tunnel states to provide granular visibility into protocol-level metrics for troubleshooting and intrusion detection. It exposes counters and status objects across six functional groups to track Phase 1 and Phase 2 tunnel establishment, historical trends, and failure events on Cisco routers and security appliances.

This is a MIB Module for monitoring the structures in IPSec-based Virtual Private Networks. The MIB has been designed to be adopted as an IETF standard. Hence Cisco-specific features of IPSec protocol are excluded from this MIB. 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 MM: Main Mode - the process of setting up a Phase 1 SA to secure the exchanges required to setup Phase 2 SAs QM: Quick Mode - the process of setting up Phase 2 Security Associations using a Phase 1 SA. Overview of IPsec MIB The MIB contains six major groups of objects which are used to manage the IPSec Protocol. These groups include a Levels Group, a Phase-1 Group, a Phase-2 Group, a History Group, a Failure Group and a TRAP Control Group. The following table illustrates the structure of the IPSec MIB. The Phase 1 group models objects pertaining to IKE negotiations and tunnels. The Phase 2 group models objects pertaining to IPSec data tunnels. The History group is to aid applications that do trending analysis. The Failure group is to enable an operator to do troubleshooting and debugging of the VPN Router. Further, counters are supported to aid Intrusion Detection. In addition to the five major MIB Groups, there are a number of Notifications. The following table illustrates the name and description of the IPSec TRAPs. For a detailed discussion, please refer to the IETF draft draft-ietf-ipsec-flow-monitoring-mib-00.txt.
Main OID:
ciscoIpSecFlowMonitorMIB.1.3.6.1.4.1.9.9.171
425
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

425 total
Object Name
ciscoIpSecFlowMonitorMIB
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.171
cipSecMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.171.1
cipSecLevels
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.171.1.1
cipSecMibLevelro
Integer32
.1.3.6.1.4.1.9.9.171.1.1.1
cipSecPhaseOne
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.171.1.2
cikeGlobalStats
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.171.1.2.1
cikeGlobalActiveTunnelsro
Gauge32
.1.3.6.1.4.1.9.9.171.1.2.1.1
cikeGlobalPreviousTunnelsro
Counter32 UNITS "SAs"
.1.3.6.1.4.1.9.9.171.1.2.1.2
cikeGlobalInOctetsro
Counter32 UNITS "Octets"
.1.3.6.1.4.1.9.9.171.1.2.1.3
cikeGlobalInPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.1.4
cikeGlobalInDropPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.1.5
cikeGlobalInNotifysro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.6
cikeGlobalInP2Exchgsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.7
cikeGlobalInP2ExchgInvalidsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.8
cikeGlobalInP2ExchgRejectsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.9
cikeGlobalInP2SaDelRequestsro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.10
cikeGlobalOutOctetsro
Counter32 UNITS "Octets"
.1.3.6.1.4.1.9.9.171.1.2.1.11
cikeGlobalOutPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.1.12
cikeGlobalOutDropPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.1.13
cikeGlobalOutNotifysro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.14
cikeGlobalOutP2Exchgsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.15
cikeGlobalOutP2ExchgInvalidsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.16
cikeGlobalOutP2ExchgRejectsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.17
cikeGlobalOutP2SaDelRequestsro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.1.18
cikeGlobalInitTunnelsro
Counter32 UNITS "SAs"
.1.3.6.1.4.1.9.9.171.1.2.1.19
cikeGlobalInitTunnelFailsro
Counter32 UNITS "SAs"
.1.3.6.1.4.1.9.9.171.1.2.1.20
cikeGlobalRespTunnelFailsro
Counter32 UNITS "SAs"
.1.3.6.1.4.1.9.9.171.1.2.1.21
cikeGlobalSysCapFailsro
Counter32 UNITS "Failures"
.1.3.6.1.4.1.9.9.171.1.2.1.22
cikeGlobalAuthFailsro
Counter32 UNITS "Failures"
.1.3.6.1.4.1.9.9.171.1.2.1.23
cikeGlobalDecryptFailsro
Counter32 UNITS "Failures"
.1.3.6.1.4.1.9.9.171.1.2.1.24
cikeGlobalHashValidFailsro
Counter32 UNITS "Failures"
.1.3.6.1.4.1.9.9.171.1.2.1.25
cikeGlobalNoSaFailsro
Counter32 UNITS "Failures"
.1.3.6.1.4.1.9.9.171.1.2.1.26
cikePeerTable
SEQUENCE OF CikePeerEntry
.1.3.6.1.4.1.9.9.171.1.2.2
cikePeerEntry
CikePeerEntry
.1.3.6.1.4.1.9.9.171.1.2.2.1
cikePeerLocalType
IkePeerType
.1.3.6.1.4.1.9.9.171.1.2.2.1.1
cikePeerLocalValue
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.2.1.2
cikePeerRemoteType
IkePeerType
.1.3.6.1.4.1.9.9.171.1.2.2.1.3
cikePeerRemoteValue
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.2.1.4
cikePeerIntIndex
Integer32
.1.3.6.1.4.1.9.9.171.1.2.2.1.5
cikePeerLocalAddrro
IPSIpAddress
.1.3.6.1.4.1.9.9.171.1.2.2.1.6
cikePeerRemoteAddrro
IPSIpAddress
.1.3.6.1.4.1.9.9.171.1.2.2.1.7
cikePeerActiveTimero
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.2.1.8
cikePeerActiveTunnelIndexro
Integer32
.1.3.6.1.4.1.9.9.171.1.2.2.1.9
cikeTunnelTable
SEQUENCE OF CikeTunnelEntry
.1.3.6.1.4.1.9.9.171.1.2.3
cikeTunnelEntry
CikeTunnelEntry
.1.3.6.1.4.1.9.9.171.1.2.3.1
cikeTunIndex
Integer32
.1.3.6.1.4.1.9.9.171.1.2.3.1.1
cikeTunLocalTypero
IkePeerType
.1.3.6.1.4.1.9.9.171.1.2.3.1.2
cikeTunLocalValuero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.3.1.3
cikeTunLocalAddrro
IPSIpAddress
.1.3.6.1.4.1.9.9.171.1.2.3.1.4
cikeTunLocalNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.3.1.5
cikeTunRemoteTypero
IkePeerType
.1.3.6.1.4.1.9.9.171.1.2.3.1.6
cikeTunRemoteValuero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.3.1.7
cikeTunRemoteAddrro
IPSIpAddress
.1.3.6.1.4.1.9.9.171.1.2.3.1.8
cikeTunRemoteNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.3.1.9
cikeTunNegoModero
IkeNegoMode
.1.3.6.1.4.1.9.9.171.1.2.3.1.10
cikeTunDiffHellmanGrpro
DiffHellmanGrp
.1.3.6.1.4.1.9.9.171.1.2.3.1.11
cikeTunEncryptAlgoro
EncryptAlgo
.1.3.6.1.4.1.9.9.171.1.2.3.1.12
cikeTunHashAlgoro
IkeHashAlgo
.1.3.6.1.4.1.9.9.171.1.2.3.1.13
cikeTunAuthMethodro
IkeAuthMethod
.1.3.6.1.4.1.9.9.171.1.2.3.1.14
cikeTunLifeTimero
Integer32
.1.3.6.1.4.1.9.9.171.1.2.3.1.15
cikeTunActiveTimero
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.3.1.16
cikeTunSaRefreshThresholdro
Integer32
.1.3.6.1.4.1.9.9.171.1.2.3.1.17
cikeTunTotalRefreshesro
Counter32 UNITS "QM Exchanges"
.1.3.6.1.4.1.9.9.171.1.2.3.1.18
cikeTunInOctetsro
Counter32 UNITS "Octets"
.1.3.6.1.4.1.9.9.171.1.2.3.1.19
cikeTunInPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.3.1.20
cikeTunInDropPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.3.1.21
cikeTunInNotifysro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.22
cikeTunInP2Exchgsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.23
cikeTunInP2ExchgInvalidsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.24
cikeTunInP2ExchgRejectsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.25
cikeTunInP2SaDelRequestsro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.26
cikeTunOutOctetsro
Counter32 UNITS "Octets"
.1.3.6.1.4.1.9.9.171.1.2.3.1.27
cikeTunOutPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.3.1.28
cikeTunOutDropPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.3.1.29
cikeTunOutNotifysro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.30
cikeTunOutP2Exchgsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.31
cikeTunOutP2ExchgInvalidsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.32
cikeTunOutP2ExchgRejectsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.33
cikeTunOutP2SaDelRequestsro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.3.1.34
cikeTunStatusrw
TunnelStatus
.1.3.6.1.4.1.9.9.171.1.2.3.1.35
cikePeerCorrTable
SEQUENCE OF CikePeerCorrEntry
.1.3.6.1.4.1.9.9.171.1.2.4
cikePeerCorrEntry
CikePeerCorrEntry
.1.3.6.1.4.1.9.9.171.1.2.4.1
cikePeerCorrLocalType
IkePeerType
.1.3.6.1.4.1.9.9.171.1.2.4.1.1
cikePeerCorrLocalValue
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.4.1.2
cikePeerCorrRemoteType
IkePeerType
.1.3.6.1.4.1.9.9.171.1.2.4.1.3
cikePeerCorrRemoteValue
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.9.9.171.1.2.4.1.4
cikePeerCorrIntIndex
Integer32
.1.3.6.1.4.1.9.9.171.1.2.4.1.5
cikePeerCorrSeqNum
Integer32
.1.3.6.1.4.1.9.9.171.1.2.4.1.6
cikePeerCorrIpSecTunIndexro
Integer32
.1.3.6.1.4.1.9.9.171.1.2.4.1.7
cikePhase1GWStatsTable
SEQUENCE OF CikePhase1GWStatsEntry
.1.3.6.1.4.1.9.9.171.1.2.5
cikePhase1GWStatsEntry
CikePhase1GWStatsEntry
.1.3.6.1.4.1.9.9.171.1.2.5.1
cikePhase1GWActiveTunnelsro
Gauge32
.1.3.6.1.4.1.9.9.171.1.2.5.1.1
cikePhase1GWPreviousTunnelsro
Counter32 UNITS "SAs"
.1.3.6.1.4.1.9.9.171.1.2.5.1.2
cikePhase1GWInOctetsro
Counter32 UNITS "Octets"
.1.3.6.1.4.1.9.9.171.1.2.5.1.3
cikePhase1GWInPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.5.1.4
cikePhase1GWInDropPktsro
Counter32 UNITS "Packets"
.1.3.6.1.4.1.9.9.171.1.2.5.1.5
cikePhase1GWInNotifysro
Counter32 UNITS "Notification Payloads"
.1.3.6.1.4.1.9.9.171.1.2.5.1.6
cikePhase1GWInP2Exchgsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.5.1.7
cikePhase1GWInP2ExchgInvalidsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.5.1.8
cikePhase1GWInP2ExchgRejectsro
Counter32 UNITS "SA Payloads"
.1.3.6.1.4.1.9.9.171.1.2.5.1.9
Showing 100 of 425 OID objects

CISCO-IPSEC-FLOW-MONITOR-MIB Technical Reference Overview

The CISCO-IPSEC-FLOW-MONITOR-MIB SNMP MIB module published by Cisco defines 425 managed OID objects, including 363 scalar/column metrics, 13 SNMP tables, and 13 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.171. Key tabular structures include cikePeerTable, cikeTunnelTable, cikePeerCorrTable, cikePhase1GWStatsTable, cipSecTunnelTable, cipSecEndPtTable. Monitored SNMP traps/notifications include cikeTunnelStart, cikeTunnelStop, cikeSysFailure, cikeCertCrlFailure, cikeProtocolFailure, cikeNoSa.

Key OID Definitions in CISCO-IPSEC-FLOW-MONITOR-MIB

ciscoIpSecFlowMonitorMIBMODULE-IDENTITYnot-accessible
.1.3.6.1.4.1.9.9.171

This is a MIB Module for monitoring the structures in IPSec-based Virtual Private Networks. The MIB has been designed to be adopted as an IETF standard. Hence Cisco-specific features of IPSec protocol are excluded from this MIB. 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 MM: Main Mode - the process of setting up a Phase 1 SA to secure the exchanges required to setup Phase 2 SAs QM: Quick Mode - the process of setting up Phase 2 Security Associations using a Phase 1 SA. Overview of IPsec MIB The MIB contains six major groups of objects which are used to manage the IPSec Protocol. These groups include a Levels Group, a Phase-1 Group, a Phase-2 Group, a History Group, a Failure Group and a TRAP Control Group. The following table illustrates the structure of the IPSec MIB. The Phase 1 group models objects pertaining to IKE negotiations and tunnels. The Phase 2 group models objects pertaining to IPSec data tunnels. The History group is to aid applications that do trending analysis. The Failure group is to enable an operator to do troubleshooting and debugging of the VPN Router. Further, counters are supported to aid Intrusion Detection. In addition to the five major MIB Groups, there are a number of Notifications. The following table illustrates the name and description of the IPSec TRAPs. For a detailed discussion, please refer to the IETF draft draft-ietf-ipsec-flow-monitoring-mib-00.txt.

cikePeerTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.2.2

The IPsec Phase-1 Internet Key Exchange Peer Table. There is one entry in this table for each IPsec Phase-1 IKE peer association which is currently associated with an active IPsec Phase-1 Tunnel. The IPsec Phase-1 IKE Tunnel associated with this IPsec Phase-1 IKE peer association may or may not be currently active.

cikeTunnelTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.2.3

The IPsec Phase-1 Internet Key Exchange Tunnel Table. There is one entry in this table for each active IPsec Phase-1 IKE Tunnel.

cikePeerCorrTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.2.4

The IPsec Phase-1 Internet Key Exchange Peer Association to IPsec Phase-2 Tunnel Correlation Table. There is one entry in this table for each active IPsec Phase-2 Tunnel.

cikePhase1GWStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.2.5

Phase-1 IKE stats information is included in this table. Each entry is related to a specific gateway which is identified by 'cmgwIndex'.

cipSecTunnelTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.3.2

The IPsec Phase-2 Tunnel Table. There is one entry in this table for each active IPsec Phase-2 Tunnel.

cipSecEndPtTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.3.3

The IPsec Phase-2 Tunnel Endpoint Table. This table contains an entry for each active endpoint associated with an IPsec Phase-2 Tunnel.

cipSecSpiTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.3.4

The IPsec Phase-2 Security Protection Index Table. This table contains an entry for each active and expiring security association.

cipSecPhase2GWStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.3.5

Phase-2 IPsec stats information is included in this table. Each entry is related to a specific gateway which is identified by 'cmgwIndex'

cikeTunnelHistTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.4.2.1

The IPsec Phase-1 Internet Key Exchange Tunnel History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

cipSecTunnelHistTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.4.3.1

The IPsec Phase-2 Tunnel History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

cipSecEndPtHistTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.4.3.2

The IPsec Phase-2 Tunnel Endpoint History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

cikeFailTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.5.2.1

The IPsec Phase-1 Failure Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecFailTableSize object.

cipSecFailTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.171.1.5.3.1

The IPsec Phase-2 Failure Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecFailTableSize object.

cikeTunnelStartNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.1

This notification is generated when an IPsec Phase-1 IKE Tunnel becomes active.

cikeTunnelStopNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.2

This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive.

cikeSysFailureNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.3

This notification is generated when the processing for an IPsec Phase-1 IKE Tunnel experiences an internal or system capacity error.

cikeCertCrlFailureNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.4

This notification is generated when the processing for an IPsec Phase-1 IKE Tunnel experiences a Certificate or a Certificate Revoke List (CRL) related error.

cikeProtocolFailureNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.5

This notification is generated when the processing for an IPsec Phase-1 IKE Tunnel experiences a protocol related error.

cikeNoSaNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.6

This notification is generated when the processing for an IPsec Phase-1 IKE Tunnel experiences a non-existent security association error.

cipSecTunnelStartNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.7

This notification is generated when an IPsec Phase-2 Tunnel becomes active.

cipSecTunnelStopNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.8

This notification is generated when an IPsec Phase-2 Tunnel becomes inactive.

cipSecSysFailureNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.9

This notification is generated when the processing for an IPsec Phase-2 Tunnel experiences an internal or system capacity error.

cipSecSetUpFailureNOTIFICATION-TYPEnot-accessible
.1.3.6.1.4.1.9.9.171.2.0.10

This notification is generated when the setup for an IPsec Phase-2 Tunnel fails.

More MIBs from Cisco

Browse all CiscoMIBs →
CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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.

1401 objects→
CISCO-UNIFIED-COMPUTING-STORAGE-MIB

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.

1295 objects→
CISCO-UNIFIED-COMPUTING-VNIC-MIB

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.

1161 objects→
CERENT-GENERIC-MIB

SNMP MIB module

984 objects→
CISCO-UNIFIED-COMPUTING-BIOS-MIB

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.

937 objects→
CISCO-UNIFIED-COMPUTING-ETHER-MIB

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.

920 objects→