IPI-VRF-MIB

        The MIB module for provisioning and managing network
virtualization features. 
        
A VRF-Lite enabled device implements VRFs and does not require
MPLS for end to end communication. Instead of using MPLS
labels, VRF-Lite uses the interfaces to distinguish routes for
different VPNs. VRF-Lite forms virtual packet-forwarding tables
by associating one or more interfaces with each VRF, and
interfaces cannot belong to more than one VRF at any time.
        
VRF-Lite is an IP based hop-by-hop virtualization mechanism and
it involves complex configuration of every hop in the network.
vNET, virtual network, is also an IP based hop-by-hop mechanism
that can provide end-to-end virtualization of the network. vNET
greatly reduces the complexity in VRF-Lite deployment.
        
This MIB module will allow the user to perform the following
        
  * Create and monitor VRFs
  * Group VRFs to create VRF List
  * Associate/Dis-associate interface to/from a VRF
    
Source file
IPI-VRF-MIB
Last revised
Identity
ipiVrfMIB
Base OID
1.3.6.1.4.1.6926.2.35
Imported Objects
IF-MIB InterfaceIndex
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI enterprises MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus StorageType
Net-SNMP examples using the mrv MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'IPI-VRF-MIB' -M '/opt/observium/mibs/mrv:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IPI-VRF-MIB::ipiVrfMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'IPI-VRF-MIB' -M '/opt/observium/mibs/mrv:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'IPI-VRF-MIB::ipiVrfMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (24)
.1.3.6.1.4.1.6926
.1.3.6.1.4.1.6926.2
.1.3.6.1.4.1.6926.2.35
.1.3.6.1.4.1.6926.2.35.0
.1.3.6.1.4.1.6926.2.35.1
.1.3.6.1.4.1.6926.2.35.1.1
.1.3.6.1.4.1.6926.2.35.1.1.1
.1.3.6.1.4.1.6926.2.35.1.1.1.1
Unsigned32
.1.3.6.1.4.1.6926.2.35.1.1.1.1.1
OctetString
.1.3.6.1.4.1.6926.2.35.1.1.1.1.2
Enumeration
.1.3.6.1.4.1.6926.2.35.1.1.1.1.3
Bits
.1.3.6.1.4.1.6926.2.35.1.1.1.1.4
.1.3.6.1.4.1.6926.2.35.1.1.1.1.5
.1.3.6.1.4.1.6926.2.35.1.1.1.1.6
.1.3.6.1.4.1.6926.2.35.1.2
.1.3.6.1.4.1.6926.2.35.1.2.1
.1.3.6.1.4.1.6926.2.35.1.2.1.1
Integer32
.1.3.6.1.4.1.6926.2.35.1.2.1.1.1
OctetString
.1.3.6.1.4.1.6926.2.35.1.2.1.1.2
.1.3.6.1.4.1.6926.2.35.1.2.1.1.3
.1.3.6.1.4.1.6926.2.35.1.2.1.1.4
.1.3.6.1.4.1.6926.2.35.2
.1.3.6.1.4.1.6926.2.35.2.1
.1.3.6.1.4.1.6926.2.35.2.2
Dependencies (7) 5 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. IANAifType-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMPv2-MIBrfc
  6. IF-MIBrfc
  7. SNMP-FRAMEWORK-MIBrfc
  8. IPI-VRF-MIBmrvselected
Conformance Groups (2)
Collection of objects needed for VRF and VRF-Lite management.
.1.3.6.1.4.1.6926.2.35.2.1.1
Collection of VRF notifications.
.1.3.6.1.4.1.6926.2.35.2.1.2
Compliance Statements (1)

OID .1.3.6.1.4.1.6926.2.35.2.2.1
The compliance statement for SNMP Agents which
implement this MIB.
Required groups
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.6926.2.35.0.1
This notification is generated when:
a. The ifOperStatus of an interface associated with a VRF
changes to the up(1) state.
b. When an interface with ifOperStatus = up(1) is
associated with a VRF.

The interface is identified by ipiVrfInterfaceIndex and the VRF is identified by ipiVrfName varbinds respectively.
.1.3.6.1.4.1.6926.2.35.0.2
This notification is generated when:
a. The ifOperStatus of an interface associated with a VRF
changes to the down(2) state.
b. When an interface with ifOperStatus = up(1) state is
disassociated with a VRF.

The interface is identified by ipiVrfInterfaceIndex and the VRF is identified by ipiVrfName varbinds respectively.

If all the interfaces associated with the VRF are in down(2)
state or if there are no more interfaces associated with the
VRF, then the ipiVrfOperStatus will have a value of down(2).