CISCO-VDC-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-VDC-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2016-11-03

Category: Cisco Devices, Device Management

Description: Manages Virtual Device Context (VDC) creation, resource allocation, and operational state on Cisco Nexus switches.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-VDC-MIB?

CISCO-VDC-MIB is a Cisco enterprise MIB for managing Virtual Device Contexts (VDCs), a Nexus-series feature that partitions a single physical switch into multiple logical virtual switches for management separation without additional hardware. It exposes configuration and operational-state data for each VDC, including VDC identity, name, MAC address, FCoE capability, and state, as well as system-wide limits like the maximum number of VDCs allowed. Its monitoring role covers both configuration and operational hardware status: ciscoVdcState reveals whether a given virtual device context is up, down, or in a transitional/failed state, which is critical for detecting a VDC that has failed to boot or has lost high-availability synchronization. It is closely tied to Cisco Nexus platform concepts and typically used alongside standard entity/chassis MIBs describing the underlying physical hardware. It is deployed on Cisco Nexus switches configured with multiple virtual device contexts for multi-tenant or departmental separation, and administrators typically perform a CISCO-VDC-MIB download from Cisco to compile it alongside standard entity/chassis MIBs.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-VDC-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Cisco Nexus switches

Monitoring Examples

An administrator would poll ciscoVdcTable/ciscoVdcEntry, reading ciscoVdcState for each ciscoVdcId/ciscoVdcName to confirm all configured VDCs are operationally up. A VDC unexpectedly reporting a non-active ciscoVdcState would indicate a failed VDC boot, a resource allocation problem, or an HA switchover issue affecting that logical switch. Checking ciscoVdcMaxNumberVdcAllowed against the count of rows in ciscoVdcTable helps confirm the switch has capacity for additional VDCs before provisioning new ones, and ciscoVdcFcoeCapable indicates whether a given VDC supports FCoE storage traffic.

What Can Be Monitored

  • VDC operational state
  • VDC identity, name, and MAC address
  • FCoE capability per VDC
  • maximum VDCs allowed vs. configured
Imported Objects

From CISCO-SMI

ciscoMgmtOBJECT-IDENTITY

From CISCO-TC

Cisco2KVlanList

From IF-MIB

InterfaceIndex

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Gauge32
Integer32
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
MacAddress
RowStatus
StorageType
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using ciscoVdcReloadCount OID:

Select a Cisco Nexus switch (Virtual Device Contexts) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type ciscoVdcReloadCount into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This object indicates the number of times a particular VDC has been reloaded. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Gauge32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Manages Cisco Nexus Virtual Device Contexts (VDCs) which partition physical hardware into virtual switches.

Start monitoring Cisco Nexus switches (Virtual Device Contexts) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-VDC-MIB