CISCO-VIRTUAL-NW-IF-MIB

File: CISCO-VIRTUAL-NW-IF-MIB.mib (13635 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF SNMPv2-TC
SNMP-FRAMEWORK-MIB IF-MIB CISCO-SMI
ENTITY-MIB CISCO-ST-TC

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
Unsigned32 MODULE-COMPLIANCE OBJECT-GROUP
NOTIFICATION-GROUP RowStatus SnmpAdminString
InterfaceIndex ifName ciscoMgmt
entPhysicalIndex FcAddressId

Defined Types

VirtualNwIfEntry  
SEQUENCE    
  virtualNwIfType INTEGER
  virtualNwIfId Unsigned32
  virtualNwIfIndex InterfaceIndex
  virtualNwIfFcId FcAddressId
  virtualNwIfOperStatusCause INTEGER
  virtualNwIfOperStatusCauseDescr SnmpAdminString
  virtualNwIfRowStatus RowStatus

Defined Values

ciscoVirtualNwIfMIB 1.3.6.1.4.1.9.9.290
The MIB module for management of virtual network interfaces to VSAN and VLAN.
MODULE-IDENTITY    

ciscoVirtualNwIfObjects 1.3.6.1.4.1.9.9.290.1
OBJECT IDENTIFIER    

virtualNwIfMIBConformance 1.3.6.1.4.1.9.9.290.2
OBJECT IDENTIFIER    

virtualNwIfConfig 1.3.6.1.4.1.9.9.290.1.1
OBJECT IDENTIFIER    

virtualNwIfStatistics 1.3.6.1.4.1.9.9.290.1.2
OBJECT IDENTIFIER    

virtualNwIfNotification 1.3.6.1.4.1.9.9.290.1.3
OBJECT IDENTIFIER    

virtualNwIfNotifications 1.3.6.1.4.1.9.9.290.1.3.0
OBJECT IDENTIFIER    

virtualNwIfTable 1.3.6.1.4.1.9.9.290.1.1.1
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)'.
OBJECT-TYPE    
  SEQUENCE OF  
    VirtualNwIfEntry

virtualNwIfEntry 1.3.6.1.4.1.9.9.290.1.1.1.1
Each entry provides information on a local virtual interface for a VSAN or VLAN.
OBJECT-TYPE    
  VirtualNwIfEntry  

virtualNwIfType 1.3.6.1.4.1.9.9.290.1.1.1.1.1
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.
OBJECT-TYPE    
  INTEGER vsan(1), vlan(2)  

virtualNwIfId 1.3.6.1.4.1.9.9.290.1.1.1.1.2
The id of VSAN or VLAN, according to the value of virtualNwIfType.
OBJECT-TYPE    
  Unsigned32  

virtualNwIfIndex 1.3.6.1.4.1.9.9.290.1.1.1.1.3
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)'.
OBJECT-TYPE    
  InterfaceIndex  

virtualNwIfFcId 1.3.6.1.4.1.9.9.290.1.1.1.1.4
The Fibre Channel Identifier(FC-ID) of this interface. This object is relevant to interfaces with 'virtualNwIfType' of vsan(1) only.
OBJECT-TYPE    
  FcAddressId  

virtualNwIfOperStatusCause 1.3.6.1.4.1.9.9.290.1.1.1.1.5
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)'.
OBJECT-TYPE    
  INTEGER none(1), adminDown(2), vsanNotOperational(3), noFcid(4), kernelConfFailure(5)  

virtualNwIfOperStatusCauseDescr 1.3.6.1.4.1.9.9.290.1.1.1.1.6
The description for the cause of current operational state of the interface, shown by the object 'virtualNwIfOperStatusCause'.
OBJECT-TYPE    
  SnmpAdminString  

virtualNwIfRowStatus 1.3.6.1.4.1.9.9.290.1.1.1.1.7
The status of this conceptual row.
OBJECT-TYPE    
  RowStatus  

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.
NOTIFICATION-TYPE    

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'.
NOTIFICATION-TYPE    

virtualNwIfMIBCompliances 1.3.6.1.4.1.9.9.290.2.1
OBJECT IDENTIFIER    

virtualNwIfMIBGroups 1.3.6.1.4.1.9.9.290.2.2
OBJECT IDENTIFIER    

virtualNwIfMIBCompliance 1.3.6.1.4.1.9.9.290.2.1.1
Only three values 'createAndGo', 'destroy' and 'active' out of the six enumerated values need to be supported.
MODULE-COMPLIANCE    
  virtualNwIfRowStatus INTEGER active(1), createAndGo(4), destroy(6)

virtualNwIfGroup 1.3.6.1.4.1.9.9.290.2.2.1
A collection of objects related to virtual interface parameters.
OBJECT-GROUP    

virtualNwIfNotificationGroup 1.3.6.1.4.1.9.9.290.2.2.2
A collection of notifications for monitoring virtual interfaces.
NOTIFICATION-GROUP