CISCO-VIRTUAL-NW-IF-MIB: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-VIRTUAL-NW-IF-MIB
Download as:   
SNMPv2-CONF, ENTITY-MIB, SNMP-FRAMEWORK-MIB, SNMPv2-SMI, IF-MIB, CISCO-SMI, CISCO-ST-TC, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 ciscoVirtualNwIfMIB 1.3.6.1.4.1.9.9.290
The MIB module for management of virtual network interfaces to VSAN and VLAN.
         ciscoVirtualNwIfObjects 1.3.6.1.4.1.9.9.290.1
             virtualNwIfConfig 1.3.6.1.4.1.9.9.290.1.1
                 virtualNwIfTable 1.3.6.1.4.1.9.9.290.1.1.1 no-access
This 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)'.
                     virtualNwIfEntry 1.3.6.1.4.1.9.9.290.1.1.1.1 no-access
Each entry provides information on a local virtual interface for a VSAN or VLAN.
                         virtualNwIfType 1.3.6.1.4.1.9.9.290.1.1.1.1.1 integer no-access
If 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: 'vlan': 2, 'vsan': 1.
                         virtualNwIfId 1.3.6.1.4.1.9.9.290.1.1.1.1.2 unsigned32 no-access
The id of VSAN or VLAN, according to the value of virtualNwIfType.
                         virtualNwIfIndex 1.3.6.1.4.1.9.9.290.1.1.1.1.3 interfaceindex read-only
The 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)'.
                         virtualNwIfFcId 1.3.6.1.4.1.9.9.290.1.1.1.1.4 fcaddressid read-only
The Fibre Channel Identifier(FC-ID) of this interface. This object is relevant to interfaces with 'virtualNwIfType' of vsan(1) only.
                         virtualNwIfOperStatusCause 1.3.6.1.4.1.9.9.290.1.1.1.1.5 integer read-only
The 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)'. Enumeration: 'adminDown': 2, 'noFcid': 4, 'none': 1, 'kernelConfFailure': 5, 'vsanNotOperational': 3.
                         virtualNwIfOperStatusCauseDescr 1.3.6.1.4.1.9.9.290.1.1.1.1.6 snmpadminstring read-only
The description for the cause of current operational state of the interface, shown by the object 'virtualNwIfOperStatusCause'.
                         virtualNwIfRowStatus 1.3.6.1.4.1.9.9.290.1.1.1.1.7 rowstatus read-only
The status of this conceptual row.
             virtualNwIfStatistics 1.3.6.1.4.1.9.9.290.1.2
             virtualNwIfNotification 1.3.6.1.4.1.9.9.290.1.3
                 virtualNwIfNotifications 1.3.6.1.4.1.9.9.290.1.3.0
                     virtualNwIfCreateEntryNotify 1.3.6.1.4.1.9.9.290.1.3.0.1
This 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.
                     virtualNwIfDeleteEntryNotify 1.3.6.1.4.1.9.9.290.1.3.0.2
This notification is generated by the agent whenever an virtual interface is deleted from the 'virtualNwIfTable'.
         virtualNwIfMIBConformance 1.3.6.1.4.1.9.9.290.2
             virtualNwIfMIBCompliances 1.3.6.1.4.1.9.9.290.2.1
                 virtualNwIfMIBCompliance 1.3.6.1.4.1.9.9.290.2.1.1
The compliance statement for entities which implement the CISCO-VIRTUAL-NW-IF-MIB mib.
             virtualNwIfMIBGroups 1.3.6.1.4.1.9.9.290.2.2
                 virtualNwIfGroup 1.3.6.1.4.1.9.9.290.2.2.1
A collection of objects related to virtual interface parameters.
                 virtualNwIfNotificationGroup 1.3.6.1.4.1.9.9.290.2.2.2
A collection of notifications for monitoring virtual interfaces.