CISCO-MODULE-VIRTUALIZATION-MIB
The CISCO-MODULE-VIRTUALIZATION-MIB enables the creation, deletion, and interface assignment of logical virtual contexts on Cisco modular hardware, allowing independent management of each partition via dedicated IP addresses and configuration scopes. This module provides SNMP access to tables governing virtual context lifecycle operations and resource allocation, facilitating the isolation of services and management planes within a single physical chassis.
Imported Objects
Objects
28 total| Object Name |
|---|
ciscoModuleVirtualizationMIBThis MIB provides a way to create virtual contexts,
and managing them. A virtual context is logical
partition of a physical device. The Virtual context
provide different type of services and can be managed
independently. Each virtual context is an independent
entity, with its own configuration and supports
almost all the options that can be configured on
stand-alone hardware. Each context can have a separate
management IP address that the user can Telnet/SSH into
and send other requests(SNMP, FTP etc).
This MIB contains tables for creating/deleting virtual
contexts and assigning interfaces and/or interface ranges
to virtual contexts. MODULE-IDENTITY .1.3.6.1.4.1.9.9.472 |
cmVirtualizationNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.472.0 |
cmVirtContextAddedThis notifications will be sent
when a virtual context is added. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.472.0.1 |
cmVirtContextRemovedThis notifications will be sent
when a virtual context is removed/deleted. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.472.0.2 |
cmVirtualizationMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.472.1 |
cmVirtualContext OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.472.1.1 |
cmVirtualContextTableThis is the virtual context table. A virtual context
can be created for a module. This table is used for
creating/deleting virtual contexts. The entries can be
created/deleted by SNMP and/or by console commands. SEQUENCE OF CmVirtualContextEntry .1.3.6.1.4.1.9.9.472.1.1.1 |
cmVirtualContextEntryAn entry in virtual context table. Each entry
provides information about a particular virtual context.
To create a virtual context, following procedure is
used:
- choose the appropriate value for entPhysicalIndex
to point to an entry(with entPhysicaClass = 'module')
in entPhysicalTable.
- specify the name of the virtual context.
- create an entry in the table by specifying
ciscoVirtualContextRowStatus value of
'createAndGo' or 'createAndWait'.
One or more virtual contexts can be created in a module.
Each of these contexts are identified by a unique name.
Resources can be assigned/mapped to each virtual context.
Configurations and Monitoring can be done each virtual
context independent of each other. Configuration changes in
one virtual context will not affect other. CmVirtualContextEntry .1.3.6.1.4.1.9.9.472.1.1.1.1 |
cmVirtContextNameThis object uniquely identifies a virtual context. SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.472.1.1.1.1.1 |
cmVirtContextDescrThis object is used for configuring
the description of virtual context.rw SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.472.1.1.1.1.2 |
cmVirtContextURLThis object is used for configuring
the URL from which virtual context
configuration will be downloaded.
The configuration contains information
on anything that is configured in a
virtual context.
Some examples of possible values for this object are:
disk://[path/]filename
ftp://[user[:password]@]server/[path/]filename
tftp://server/[path/]filename
http://server/[path/]filename
https://server/[path/]filename.
NOTE: Above list is just an example. It does not
specify/limit only these values to be supported.rw CiscoURLString (CISCO-TC) .1.3.6.1.4.1.9.9.472.1.1.1.1.3 |
cmVirtContextResourceClassThis object is used for assigning
a resource class to a context.
The resource class contains information
on the resources that are managed/applicable
to a context. The type of resources that
may be applicable are governed by the
CiscoResourceClass TEXTUAL CONVENTION.
This object value must correspond to an entry
in cmResourceClassTable.rw CiscoResourceClass (CISCO-L4L7MODULE-RESOURCE-LIMIT-MIB) .1.3.6.1.4.1.9.9.472.1.1.1.1.4 |
cmVirtContextStorageTypeThe storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row.rw StorageType (SNMPv2-TC) .1.3.6.1.4.1.9.9.472.1.1.1.1.5 |
cmVirtContextRowStatusThis object is used for creating/deleting
entries in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.472.1.1.1.1.6 |
cmVirtContextIfMapTableThis table is used for assigning interfaces
to a virtual context. This table will configure
the set of interfaces that can be used by a
virtual context. SEQUENCE OF CmVirtContextIfMapEntry .1.3.6.1.4.1.9.9.472.1.1.2 |
cmVirtContextIfMapEntryAn entry in Interface Map table.
Each entry represents the interface or
interface range that are assigned to
a virtual context. CmVirtContextIfMapEntry .1.3.6.1.4.1.9.9.472.1.1.2.1 |
cmVirtContextIfMapTypeThis object specifies the interface type
for which cmVirtContextIfMapIdHigh
and cmVirtContextIfMapIdLow are applicable. IANAifType (IANAifType-MIB) .1.3.6.1.4.1.9.9.472.1.1.2.1.1 |
cmVirtContextIfMapIdLowThis object specifies the interface that
can be assigned to a context. This object
either represents an interface or lower value
of the interface range. Unsigned32 .1.3.6.1.4.1.9.9.472.1.1.2.1.2 |
cmVirtContextIfMapIdHighThis object specifies the interface that
will be assigned to a virtual context.
The non-zero value specifies the upper value
of the interface range. This value must be
greater than the value in cmVirtContextIfMapIdLow.
The value zero specifies that value specified
in cmVirtContextIfMapIdLow is assigned.rw Unsigned32 .1.3.6.1.4.1.9.9.472.1.1.2.1.3 |
cmVirtContextIfMapStorageTypeThe storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row.rw StorageType (SNMPv2-TC) .1.3.6.1.4.1.9.9.472.1.1.2.1.4 |
cmVirtContextIfMapRowStatusThis object is used for creating/deleting
entries in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.472.1.1.2.1.5 |
cmVirtualContextNotifControl OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.472.1.2 |
cmVirtContextNotifEnableThis object is used for enabling/disabling
notifications related to virtual context.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.472.1.2.1 |
cmVirtualContextNotifObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.472.1.3 |
cmNotifVirtContextNameThis object is used in notifications only.
This object contains the virtual context name.
(i.e. value of cmVirtContextName).ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.472.1.3.1 |
cmVirtualizationMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.472.2 |
cmVirtualizationCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.472.2.1 |
cmVirtualizationGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.472.2.2 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.