CISCO-VIRTUAL-INTERFACE-MIB
The CISCO-VIRTUAL-INTERFACE-MIB enables programmatic creation, deletion, and binding of Cisco virtual interfaces and Virtual Interface Groups to physical ports or EtherChannels. It provides management access to the `cvifGroupTable` for systems supporting interface grouping and exposes operational status for virtual interfaces bound to underlying physical or logical transport layers.
Imported Objects
Objects
27 total| Object Name |
|---|
ciscoVirtualInterfaceMIBThe MIB module for creation and deletion of Virtual Interfaces
and Virtual Interface Groups. In addition to this MIB,
interface mib (rfc2863) will also contain entries for virtual
interfaces.
There are two ways virtual interfaces can be created and bound
to an interface. The MIB Object cvifGroupsSupported indicates
if a particular system supports the Virtual Interface Group
concept.
If Virtual Interface Groups are supported, then a virtual
interface is always created/deleted in conjunction with its
associated Virtual Interface Group. The Virtual Interface
Group, which may be associated to multiple virtual interfaces,
is then bound to a physical interface or another virtual
interface like an EtherChannel.
If Virtual Interface Groups are not supported, then a virtual
interface is created/deleted independently. And each virtual
interface is bound to a physical interface or another virtual
interface like an EtherChannel.
In order for a virtual interface to become operational, it must
be directly or indirectly (via its Virtual Interface Group)
bound to a physical interface or possibly to another virtual
interface such as an EtherChannel.
The cvifGroupTable is only used if the MIB object
cvifGroupsSupported indicates Virtual Interface Groups are
supported. MODULE-IDENTITY .1.3.6.1.4.1.9.9.648 |
ciscoVirtualInterfaceMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.648.1 |
cvifGlobals OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.648.1.1 |
cvifGroupsSupportedThis is a boolean that indicates whether Virtual Interface
Groups are supported (and enabled). Note that many agents are
unlikely to support write-access for this object. If there are
entries in the cvifGroupTable when this value is being set to
false, the set will fail.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.648.1.1.1 |
cvifConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.648.1.2 |
cvifGroupTableThis table facilitates the creation and deletion of a Virtual
Interface Group. Entries in this table exist only if
cvifGroupsSupported is 'true'. A Virtual Interface Group is a
collection of virtual interfaces on an adapter in a server. The
virtual interfaces within a Virtual Interface Group do not need
to all have the same ifType. SEQUENCE OF CvifGroupEntry .1.3.6.1.4.1.9.9.648.1.2.1 |
cvifGroupEntryThere is one entry in this table for each created
Virtual Interface Group. CvifGroupEntry .1.3.6.1.4.1.9.9.648.1.2.1.1 |
cvifGroupIndexAn index that uniquely identifies an entry in the
cvifGroupTable table. Unsigned32 (1..1024 ) .1.3.6.1.4.1.9.9.648.1.2.1.1.1 |
cvifGroupIfIndexThe ifIndex of this Virtual Interface Group.ro InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.648.1.2.1.1.2 |
cvifGroupBindingIfIndexThe ifIndex of the physical interface or another virtual
interface like an Etherchannel bound to this Virtual Interface
Group. The binding can happen at Virtual Interface Group
creation time or at a later time. In order for Virtual Interface
Group to become operational, binding to a physical interface or
a virtual interface like an Etherchannel is mandatory. When the
virtual interface group is not bound to an interface, this field
has a value of zero.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.9.648.1.2.1.1.3 |
cvifGroupMemberListThe list of Virtual interfaces in the Virtual Interface Group.ro PortMemberList (CISCO-ST-TC) .1.3.6.1.4.1.9.9.648.1.2.1.1.4 |
cvifGroupCreationTimeThe timestamp of this entry's creation time.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.648.1.2.1.1.5 |
cvifGroupFailureCauseThe cause of failure for the last bind operation. This object
will be zero length if and only if the bind is successful. After
a successful bind operation, the value of cvifGroupOperState is
set to 'up'.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.648.1.2.1.1.6 |
cvifGroupOperStateOperational state of the Virtual Interface Group.ro Enumeration .1.3.6.1.4.1.9.9.648.1.2.1.1.7 |
cvifGroupRowStatusThe status of this conceptual row. The RowStatus becomes active
on successful creation of a Virtual Interface Group. It is not
necessary for the cvifGroupBindingIfIndex to be set at the time
of creation.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.648.1.2.1.1.8 |
cvifTableThis table facilitates the creation and deletion of virtual
interfaces. Virtual interfaces may or may not be associated
with a Virtual Interface Group according to the value of
cvifGroupsSupported. In order for a virtual interface to become
operational, it must be directly bound to a physical interface
or another virtual interface like an EtherChannel or indirectly
bound via its Virtual Interface Group. At creation time, the
cvifType must be identified. SEQUENCE OF CvifEntry .1.3.6.1.4.1.9.9.648.1.2.2 |
cvifEntryThere is one entry in this table for each created virtual
Interface CvifEntry .1.3.6.1.4.1.9.9.648.1.2.2.1 |
cvifIndexWhen Virtual Interface Groups (as indicated by the
cvifGroupsSupported MIB object) are supported, this is the
Virtual Interface Group index. Otherwise, this index identifies
the virtual interface. Unsigned32 (1..1024 ) .1.3.6.1.4.1.9.9.648.1.2.2.1.1 |
cvifTypeThe type of virtual interface desired by the network manager.
If and when a row is created in this table by using a SetRequest
to cvifRowStatus, the corresponding ifTable row will be created
by the agent with its ifType as specified by this object.
Note that agents are unlikely to support more than a few values
for this object, e.g., 'ethernetCsmacd(6)' and
'fibreChannel(56)'. IANAifType (IANAifType-MIB) .1.3.6.1.4.1.9.9.648.1.2.2.1.2 |
cvifIfIndexThe ifIndex of this virtual interface.ro InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.648.1.2.2.1.3 |
cvifCreationTimeThe timestamp of this entry's creation time.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.648.1.2.2.1.4 |
cvifBindingIfIndexThis field is supported only when Virtual Interface Groups are
not supported, as indicated by the cvifGroupsSupported MIB
object. It identifies the ifIndex of the interface that this
virtual interface is bound to. In order for a virtual interface
to become operational, in the absence of Virtual Interface
Groups, binding to an interface is mandatory. When the virtual
interface is not bound to an interface, this field has a
value of zero.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.9.648.1.2.2.1.5 |
cvifFailureCauseThis field is supported only when Virtual Interface Groups are
not supported, as indicated by the cvifGroupsSupported MIB
object. The cause of failure for the last bind operation. This
object will be zero length if and only if the bind is
successful.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.648.1.2.2.1.6 |
cvifRowStatusThe status of this conceptual row. The RowStatus becomes active
on successful creation of a virtual interface. If Virtual
Interface Groups are not supported, as indicated by the
cvifGroupsSupported MIB object, the virtual interface must be
bound to a physical interface or another virtual interface like
an Etherchannel before it can become operational.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.648.1.2.2.1.7 |
ciscoVirtualInterfaceMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.648.2 |
cvifMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.648.2.1 |
cvifMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.648.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.