CISCO-VIRTUAL-NW-IF-MIB
The CISCO-VIRTUAL-NW-IF-MIB enables monitoring and management of virtual network interface states, traffic counters, and configuration parameters for Virtual Storage Area Networks (VSANs) and Virtual Local Area Networks (VLANs) on Cisco devices. It provides granular visibility into the operational status and performance metrics of virtualized network segments to facilitate troubleshooting and capacity planning.
Imported Objects
Objects
24 total| Object Name |
|---|
ciscoVirtualNwIfMIB OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290 |
RFC1155-SMI Unknown .1.3.6.1.4.1.9.9.290 |
ciscoVirtualNwIfObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.1 |
virtualNwIfConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.1.1 |
virtualNwIfTableThis table contains one entry for each local virtual
interface to a VSAN or VLAN, at most one such interface
per processor on a Supervisor or Line card managed by
the agent. Each such processor will have an entry in
the entPhysicalTable ( from ENTITY-MIB ) and will have a
unique PhysicalIndex. For e.g. if Line card has
2 processors on it then each processor will have a
entry in the entPhysicaltable and each will have
unique PhysicalIndex. It is possible that there can be
multiple VSAN's or VLAN's per processor, but the
network manager can create only one virtual interface
for a VSAN and only one for a VLAN per physical entity
i.e. per processor on the card.
Note:Processor is represented as a physical entity in
the entPhysicalTable.
Each such interface has a unique ifIndex assigned by
the agent. When requested to create an entry in this
table, the agent also creates a corresponding entry in
the ifTable of IF-MIB and also an entry in the
cieIfInterfaceTable of CISCO-IF-EXTENSION-MIB. Next,
the agent fills in the values of virtualNwIfIndex, after
which the creation of the entry in this table completes.
The ciiIPIfAddressTable of CISCO-IP-IF-MIB can be used
to configure the IP addresses. The ifTable and this
table can be used to monitor the interface.
Entries in this table are created by network managers.
But the entries can be deleted either by the network
managers or will be deleted by the agent if the
corresponding VSAN or VLAN is deleted.
An entry will be allowed to be created only if the
corresponding VSAN or VLAN has been created.
The ifType for an created interface of type 'vsan(1)'
will be 'fibreChannel(56)' and of type 'vlan(2)' would
be 'ethernetCsmacd(6)'. SEQUENCE OF VirtualNwIfEntry .1.3.6.1.4.1.9.9.290.1.1.1 |
virtualNwIfEntryEach entry provides information on a local virtual
interface for a VSAN or VLAN. VirtualNwIfEntry .1.3.6.1.4.1.9.9.290.1.1.1.1 |
virtualNwIfTypeIf the virtualNwIfType is vsan(1) and if the
corresponding virtual interface is enabled
( ifAdminStatus='up' ), then the operational state of
virtual interface will become active
( ifOperStatus='up' ) only if the VSAN state is active
and a FCID is obtained through a successful FLOGI.
Even if the desired state of the virtual interface is
enabled ( ifAdminStatus='up' ), but if the VSAN state is
non-active or FCID has not been obtained, then the
virtual interface is disabled(ifOperStatus='down').
Only when the VSAN state becomes active and an FCID is
obtained will the virtual interface be enabled
( ifOperStatus='up' ). An interface can be disabled while
its VSAN exists by setting ifAdminStatus='down'. When
an VSAN is deleted, the corresponding interface
( if created ) is also deleted.
If the virtualNwIfType is vlan(2) and if the
corresponding virtual interface is enabled
( ifAdminStatus='up' ) , then the virtual interface will
become active ( ifOperStatus='up' ) only if the VLAN
state is active. Even if the desired state of the
virtual interface is enabled(ifAdminStatus='up'), but if
the VLAN state is non-active, then the virtual interface
is disabled ( ifOperStatus='down' ) . Only when the VLAN
state becomes active will the virtual interface be
enabled ( ifOperStatus='up' ). An interface can be
disabled while its VLAN exists by setting
ifAdminStatus='down'. When an VLAN is deleted, the
corresponding interface ( if created ) is also deleted. Enumeration .1.3.6.1.4.1.9.9.290.1.1.1.1.1 |
virtualNwIfIdThe id of VSAN or VLAN, according to the value of
virtualNwIfType. Gauge .1.3.6.1.4.1.9.9.290.1.1.1.1.2 |
virtualNwIfIndexThe ifIndex of this interface. This value is
dynamically assigned by the agent. It is valid
whenever the value of the corresponding
virtualNwIfRowStatus is 'active'.
The ifType of interface of type vsan(1) will be
'fibreChannel(56)' and of type 'vlan(2)' would be
'ethernetCsmacd(6)'.ro InterfaceIndex -- Rsyntax INTEGER .1.3.6.1.4.1.9.9.290.1.1.1.1.3 |
virtualNwIfFcIdThe Fibre Channel Identifier(FC-ID) of this interface.
This object is relevant to interfaces with
'virtualNwIfType' of vsan(1) only.ro FcAddressId -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.290.1.1.1.1.4 |
virtualNwIfOperStatusCauseThe cause of current operational state of the interface.
'none(1)' - no failure.
'adminDown(2)' - 'ifAdminStatus' is down(2).
'vsanNotOperational(3) - VSAN not operational.
'noFcid(4)' - failed to get an FCID.
'kernelConfFailure(5)' - failed to configure the
network device.
The current operational state of the interface is shown
by the 'ifOperStatus' defined in rfc2863. This object
will show 'none(1)' for all the 'ifOperStatus' values
except for 'down(2)'. It will show one of the values
defined above if 'ifOperStatus' is 'down(2)'.ro Enumeration .1.3.6.1.4.1.9.9.290.1.1.1.1.5 |
virtualNwIfOperStatusCauseDescrThe description for the cause of current operational
state of the interface, shown by the object
'virtualNwIfOperStatusCause'.ro SnmpAdminString -- Rsyntax OCTET STRING .1.3.6.1.4.1.9.9.290.1.1.1.1.6 |
virtualNwIfRowStatusThe status of this conceptual row.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.9.9.290.1.1.1.1.7 |
virtualNwIfStatistics OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.1.2 |
virtualNwIfNotification OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.1.3 |
virtualNwIfNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.1.3.0 |
virtualNwIfCreateEntryNotifyThis notification is generated by the agent
whenever an virtual interface is created in the,
'virtualNwIfTable'. Note that this notification
is generated only when a new entry is added to the
table and not for any modifications to an existing
entry. TRAP-TYPE .1.3.6.1.4.1.9.9.290.1.3.0.1 |
virtualNwIfDeleteEntryNotifyThis notification is generated by the agent
whenever an virtual interface is deleted from the
'virtualNwIfTable'. TRAP-TYPE .1.3.6.1.4.1.9.9.290.1.3.0.2 |
virtualNwIfMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.2 |
virtualNwIfMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.2.1 |
virtualNwIfMIBCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.2.1.1 |
virtualNwIfMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.2.2 |
virtualNwIfGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.2.2.1 |
virtualNwIfNotificationGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.290.2.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.