Cisco MDS 9000 Family MIB Quick Reference (OL-18087-01, February 2009)

Send documentation comments to [e-mail]
48
Cisco MDS 9000 Family MIB Quick Reference
OL-18087-01, Cisco MDS NX-OS Release 4.x
Cisco-Specific MIBs Supported in the Cisco MDS 9000 Family
As with any services important the user requires that provides some level of fault tolerance in a graceful
manner. SME provides fault tolerance by allowing encryption nodes to be grouped into a cluster. Nodes
in the same cluster immediately take over the work of a failed node so that the user does not experience
service disruption.
CISCO-SMI
This file gives the Structure of Management Information (SMI) for the Cisco enterprise. A subset of the
SMI follows.
ciscoProducts
ciscoProducts is the root object identifier from which sysObjectID values are assigned. Actual values are
defined in CISCO-PRODUCTS-MIB.
ciscoAgentCapability
ciscoAgentCapability provides a root object identifier from which AGENT-CAPABILITIES values may
be assigned.
ciscoMgmt
ciscoMgmt is the main subtler for new MIB development.
ciscoExperiment
ciscoExperiment provides a root object identifier from which experimental MIBs may be temporarily
based. MIBs are typically based here if they fall in one of two categories:
• Cisco versions of IETF Internet Drafts that have not been assigned a permanent object identifier by
the IANA.
• Cisco work-in-process MIBs that have not been assigned a permanent object identifier by Cisco,
typically because the MIB or technology is experimental.
CISCO-SNMP-VACM-EXT-MIB
This MIB extends the SNMP-VACM-MIB to allow each combination of a securityModel and a
securityName to be mapped into additional groupNames. The groups identified by these mappings are
in addition to those identified by the vacmGroupName of the vacmSecurityToGroupTable.
CISCO-SSM-PROV-MIB
This MIB provisions features for SSMs. Currently, an SSM has eight data path processors (DPPs), each
of which corresponds to four of the 32 ports on the SSM. Each DPP can run a feature independent of the
other DPPs. Because the concept of a DPP is transparent to the network manager, groups of ports are
used to configure different features. A start port and an end port are specified to identify a DPP and
provision a feature.