Standard view Table view

CISCO-NPORT-VIRTUALIZATION-MIB

        The MIB module for the management of N_port
Virtualization or NPV within the framework of Cisco's 
N_port virtualization (NPV) Architecture.
        
N_Port virtualization reduces the number of Fibre 
Channel domain IDs in SANs. Switches operating in the 
NPV mode do not join a fabric; rather, they pass traffic 
between NPV core switch links and end-devices, which 
eliminates the domain IDs for these edge switches.
        
Glossary of terms Used in this MIB:
----------------------------------
        
SAN                - Storage Area Network
        
VSAN               - Virtual Storage Area Network,
                     Similar to a VLAN.
        
NPV                - N Port Virtualization, a technique
                     using which the number of domain IDs
                     in fibre channel fabric can be reduced,
                     leading to easier management. 
                     When operating in this mode, a fibre 
                     channel switch (typically, 
                     a fabric/blade switch)
                     acts as a HBA with respect to the 
                     fibre channel fabric and as a switch 
                     with respect to the connected devices.
        
NPV Device         - A fibre channel switch working in NPV
                     special mode.
        
NPV Core Switch    - A fibre channel edge switch connected to 
                     one or more NPV devices.
        
Server             - Host connected to the NPV device.
                     Typically, a Blade Server connected to 
                     Blade switch in NPV mode in a Blade 
                     Chassis.
        
Server Interface   - Interface on the NPV Device that connects
                     to end devices(hosts/disks). Also, known
                     as F-port, as it operates in F port mode.
        
External Interface - Interface on the NPV Device that 
                     connects to the NPV Core Switch.
                     Also known as NP-port as it operates
                     in NP port mode.
        
Traffic Map        - Traffic map is a way to restrict traffic 
                     flow from an interface to only a set of 
                     interfaces. In NPV device, traffic map
                     can be used to present a server interface
                     to the fibre channel fabric only through
                     one of the valid external interfaces
                     specified in the set of interfaces.
Source file
CISCO-NPORT-VIRTUALIZATION-MIB
Last revised
Identity
ciscoNportVirtualizationMIB
Base OID
1.3.6.1.4.1.9.9.660
Imported Objects
CISCO-IF-EXTENSION-MIB InterfaceIndexList
CISCO-SMI ciscoMgmt
IF-MIB InterfaceIndex
SNMPv2-CONF MODULE-COMPLIANCE OBJECT-GROUP
SNMPv2-SMI MODULE-IDENTITY OBJECT-TYPE
SNMPv2-TC RowStatus StorageType TimeStamp TruthValue
Net-SNMP examples using the cisco 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 'CISCO-NPORT-VIRTUALIZATION-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-NPORT-VIRTUALIZATION-MIB::ciscoNportVirtualizationMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-NPORT-VIRTUALIZATION-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-NPORT-VIRTUALIZATION-MIB::ciscoNportVirtualizationMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (17)
ciscoNportVirtualizationMIB
.1.3.6.1.4.1.9.9.660
ciscoNportVirtualizationMIBNotifs
.1.3.6.1.4.1.9.9.660.0
ciscoNportVirtualizationMIBObjects
.1.3.6.1.4.1.9.9.660.1
cnpvConfiguration
.1.3.6.1.4.1.9.9.660.1.1
cnpvGlobal
.1.3.6.1.4.1.9.9.660.1.1.1
cnpvTrafficAutoLoadbalance r/w
SNMPv2-TCTruthValue
 .1.3.6.1.4.1.9.9.660.1.1.1.1
cnpvTrafficMap
.1.3.6.1.4.1.9.9.660.1.1.2
cnpvTrafficMapTable
.1.3.6.1.4.1.9.9.660.1.1.2.1
cnpvTrafficMapEntry
cnpvTrafficMapFromIfIndex
 .1.3.6.1.4.1.9.9.660.1.1.2.1.1
cnpvTrafficMapFromIfIndex
IF-MIBInterfaceIndex
 .1.3.6.1.4.1.9.9.660.1.1.2.1.1.1
cnpvTrafficMapToIfIndexList r/w
OctetString
 .1.3.6.1.4.1.9.9.660.1.1.2.1.1.2
cnpvTrafficMapLastChange
SNMPv2-TCTimeStamp
 .1.3.6.1.4.1.9.9.660.1.1.2.1.1.3
cnpvTrafficMapStorageType r/w
SNMPv2-TCStorageType
 .1.3.6.1.4.1.9.9.660.1.1.2.1.1.4
cnpvTrafficMapRowStatus r/w
SNMPv2-TCRowStatus
 .1.3.6.1.4.1.9.9.660.1.1.2.1.1.5
ciscoNportVirtualizationMIBConform
.1.3.6.1.4.1.9.9.660.2
ciscoNportVirtualizationMIBCompliances
.1.3.6.1.4.1.9.9.660.2.1
ciscoNportVirtualizationMIBGroups
.1.3.6.1.4.1.9.9.660.2.2
Dependencies (13) 6 direct · 7 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. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. CISCO-TCcisco
  5. IANA-ENTITY-MIBrfc
  6. SNMPv2-CONFrfc
  7. SNMP-FRAMEWORK-MIBrfc
  8. UUID-TC-MIBrfc
  9. ENTITY-MIBrfc
  10. IANAifType-MIBrfc
  11. SNMPv2-MIBrfc
  12. IF-MIBrfc
  13. CISCO-IF-EXTENSION-MIBcisco
  14. CISCO-NPORT-VIRTUALIZATION-MIBciscoselected
Conformance Groups (1)
cnpvTrafficMapGroup
cnpvTrafficAutoLoadbalance cnpvTrafficMapToIfIndexList cnpvTrafficMapStorageType cnpvTrafficMapRowStatus cnpvTrafficMapLastChange
A collection of objects for displaying and configuring
NPV.
 .1.3.6.1.4.1.9.9.660.2.2.1
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.660.2.1.1
The compliance statement for entities which
implement the NPV feature.
Required groups
mandatory cnpvTrafficMapGroup
Object refinements
ObjectAccessSyntaxDescription
cnpvTrafficMapRowStatus readonly
SNMPv2-TCRowStatus
active(1), createAndGo(4), destroy(6)
Only three values 'createAndGo', 'destroy' and
'active' out of the six enumerated values need to be
supported.
cnpvTrafficAutoLoadbalance readonly
Write access is not required.
cnpvTrafficMapToIfIndexList readonly
Write access is not required.
cnpvTrafficMapStorageType readonly
Write access is not required.