MIBs Depot

CISCO-VIRTUAL-NW-IF-MIB

Registered at
1.3.6.1.4.1.9.9.290
Last updated
2002-10-02 00:00
Organization
Cisco Systems Inc.
Revisions
2002-10-02 00:00
Namespace
cisco
Source file
CISCO-VIRTUAL-NW-IF-MIB
Digest
sha256:28f76705aa703f61c4894f76abb218b82112084b384e205e9b70025a63fed853

Description

The MIB module for management of virtual network interfaces to VSAN and VLAN.

Contact

Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553 -NETS E-mail: cs-san@cisco.com

Imports

FromSymbols
CISCO-SMIciscoMgmt
CISCO-ST-TCFcAddressId
ENTITY-MIBentPhysicalIndex
IF-MIBInterfaceIndex, ifName
SNMP-FRAMEWORK-MIBSnmpAdminString
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMIMODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso
SNMPv2-TCDisplayString, RowStatus, TEXTUAL-CONVENTION

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

CISCO-SMI
CISCO-ST-TC
CISCO-VIRTUAL-NW-IF-MIB
ENTITY-MIB
IANA-ENTITY-MIB
IANAifType-MIB
IF-MIB
SNMP-FRAMEWORK-MIB
SNMPv2-CONF
SNMPv2-MIB
SNMPv2-SMI
SNMPv2-TC
UUID-TC-MIB

Objects

NameOIDSyntaxAccessStatus
ciscoVirtualNwIfObjects
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.290.1
virtualNwIfConfig
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.290.1.1
virtualNwIfTable
OBJECT-TYPE
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)'.
1.3.6.1.4.1.9.9.290.1.1.1not-accessiblecurrent
virtualNwIfEntry
OBJECT-TYPE
Each entry provides information on a local virtual interface for a VSAN or VLAN.
1.3.6.1.4.1.9.9.290.1.1.1.1not-accessiblecurrent
virtualNwIfType
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.290.1.1.1.1.1INTEGER {vsan(1), vlan(2)}not-accessiblecurrent
virtualNwIfId
OBJECT-TYPE
The id of VSAN or VLAN, according to the value of virtualNwIfType.
1.3.6.1.4.1.9.9.290.1.1.1.1.2Unsigned32not-accessiblecurrent
virtualNwIfIndex
OBJECT-TYPE
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)'.
1.3.6.1.4.1.9.9.290.1.1.1.1.3InterfaceIndexread-onlycurrent
virtualNwIfFcId
OBJECT-TYPE
The Fibre Channel Identifier(FC-ID) of this interface. This object is relevant to interfaces with 'virtualNwIfType' of vsan(1) only.
1.3.6.1.4.1.9.9.290.1.1.1.1.4FcAddressIdread-onlycurrent
virtualNwIfOperStatusCause
OBJECT-TYPE
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)'.
1.3.6.1.4.1.9.9.290.1.1.1.1.5INTEGER {none(1), adminDown(2), vsanNotOperational(3), noFcid(4), kernelConfFailure(5)}read-onlycurrent
virtualNwIfOperStatusCauseDescr
OBJECT-TYPE
The description for the cause of current operational state of the interface, shown by the object 'virtualNwIfOperStatusCause'.
1.3.6.1.4.1.9.9.290.1.1.1.1.6SnmpAdminStringread-onlycurrent
virtualNwIfRowStatus
OBJECT-TYPE
The status of this conceptual row.
1.3.6.1.4.1.9.9.290.1.1.1.1.7RowStatusread-createcurrent
virtualNwIfStatistics
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.290.1.2
virtualNwIfNotification
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.290.1.3
virtualNwIfNotifications
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.290.1.3.0
virtualNwIfMIBConformance
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.290.2
virtualNwIfMIBCompliances
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.290.2.1
virtualNwIfMIBGroups
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.290.2.2

Notifications

NameOIDStatus
virtualNwIfCreateEntryNotify
NOTIFICATION-TYPE
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.
1.3.6.1.4.1.9.9.290.1.3.0.1current
virtualNwIfDeleteEntryNotify
NOTIFICATION-TYPE
This notification is generated by the agent whenever an virtual interface is deleted from the 'virtualNwIfTable'.
1.3.6.1.4.1.9.9.290.1.3.0.2current

Conformance

NameOIDStatus
virtualNwIfMIBCompliance
MODULE-COMPLIANCE
The compliance statement for entities which implement the CISCO-VIRTUAL-NW-IF-MIB mib.
1.3.6.1.4.1.9.9.290.2.1.1current
virtualNwIfGroup
OBJECT-GROUP
A collection of objects related to virtual interface parameters.
1.3.6.1.4.1.9.9.290.2.2.1current
virtualNwIfNotificationGroup
NOTIFICATION-GROUP
A collection of notifications for monitoring virtual interfaces.
1.3.6.1.4.1.9.9.290.2.2.2current