CISCO-FDMI-MIB
Fabric Device Management Interface (FDMI) MIB. This MIB
module defines objects for managing the devices such as
HBA (Host Bus Adapter). It provides device information
which have registered with an FC fabric using FDMI.
For more information on FDMI, refer to Fibre Channel
Generic Services-4 Section 6.7 : Fabric Device
Management Interface.
- Source file
CISCO-FDMI-MIB- Last revised
- Identity
ciscoFdmiMIB- Base OID
1.3.6.1.4.1.9.9.373
Imported Objects
| CISCO-SMI | ciscoMgmt |
| CISCO-ST-TC | FcNameId |
| CISCO-VSAN-MIB | notifyVsanIndex vsanIndex |
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | TEXTUAL-CONVENTION (no object page) 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-FDMI-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-FDMI-MIB::ciscoFdmiMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-FDMI-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-FDMI-MIB::ciscoFdmiMIB'
Objects (37)
Showing 37 of 37 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.373 |
||
.1.3.6.1.4.1.9.9.373.0 |
||
.1.3.6.1.4.1.9.9.373.1 |
||
.1.3.6.1.4.1.9.9.373.1.1 |
||
.1.3.6.1.4.1.9.9.373.1.1.1 |
||
.1.3.6.1.4.1.9.9.373.1.2 |
||
.1.3.6.1.4.1.9.9.373.1.2.1 |
||
.1.3.6.1.4.1.9.9.373.1.2.1.1 |
||
.1.3.6.1.4.1.9.9.373.1.2.1.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.10 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.11 |
|
|
32-bit wordsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.12 |
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.2 |
||
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.3 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.4 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.5 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.6 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.7 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.8 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.1.1.9 |
|
.1.3.6.1.4.1.9.9.373.1.2.2 |
||
.1.3.6.1.4.1.9.9.373.1.2.2.1 |
||
.1.3.6.1.4.1.9.9.373.1.2.2.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.2.1.2 |
|
.1.3.6.1.4.1.9.9.373.1.2.2.1.3 |
||
.1.3.6.1.4.1.9.9.373.1.2.2.1.4 |
||
.1.3.6.1.4.1.9.9.373.1.2.2.1.5 |
||
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.2.1.6 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.373.1.2.2.1.7 |
|
.1.3.6.1.4.1.9.9.373.1.2.3 |
||
.1.3.6.1.4.1.9.9.373.1.2.4 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.373.1.2.5 |
|
.1.3.6.1.4.1.9.9.373.1.2.6 |
||
.1.3.6.1.4.1.9.9.373.1.3 |
||
.1.3.6.1.4.1.9.9.373.2 |
||
.1.3.6.1.4.1.9.9.373.2.1 |
||
.1.3.6.1.4.1.9.9.373.2.2 |
Dependencies (11) 7 direct · 4 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
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- CISCO-ST-TCcisco
- CISCO-TCcisco
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- CISCO-VSAN-MIBcisco
- CISCO-FDMI-MIBciscoselected
Type Definitions (2)
| Enumeration |
invalidCommandCode(1)unableToPerformCmdReq(2)invalidSize(3) |
|
| Enumeration |
noAdditionalExpl(1)hbaAlreadyRegistered(2)attrForSpecifiedHbaNotReg(3)hbaAttrMultiAttribSameType(4)invalidHbaAttrBlockLen(5)reqdHbaAttrNotPresent(6)origPortNotInRegPortList(7)hbaIdNotInRegPortList(8)portAttrNotRegistered(9)portNotRegistered(10)portAttrMultiAttrSameType(11)invalidPortAttrBlockLen(12)none(13) |
Conformance Groups (4)
|
A collection of objects for configuring FDMI.
|
.1.3.6.1.4.1.9.9.373.2.2.1
|
|
|
cfdmiHbaInfoNodeName cfdmiHbaInfoMfg cfdmiHbaInfoSn cfdmiHbaInfoModel cfdmiHbaInfoModelDescr cfdmiHbaInfoHwVer cfdmiHbaInfoDriverVer cfdmiHbaInfoOptROMVer cfdmiHbaInfoFwVer cfdmiHbaInfoOSInfo cfdmiHbaInfoMaxCTPayload cfdmiRejectReasonCode cfdmiRejectReasonCodeExpl cfdmiNotifyRegOperType cfdmiNotifyHBAPortId
A collection of objects for HBA Information.
|
.1.3.6.1.4.1.9.9.373.2.2.2
|
|
|
cfdmiHbaPortSupportedFC4Type cfdmiHbaPortSupportedSpeed cfdmiHbaPortCurrentSpeed cfdmiHbaPortMaxFrameSize cfdmiHbaPortOsDevName cfdmiHbaPortHostName
A collection of objects for HBA port information.
|
.1.3.6.1.4.1.9.9.373.2.2.3
|
|
|
A collection of notifications for managing FDMI.
|
.1.3.6.1.4.1.9.9.373.2.2.4
|
Compliance Statements (1)
OID
.1.3.6.1.4.1.9.9.373.2.1.1The compliance statement for entities which
implement the CISCO-FDMI-MIB.
implement the CISCO-FDMI-MIB.
Required groups
| mandatory | cfdmiConfigGroup | |
| mandatory | cfdmiHbaInformationGroup | |
| mandatory | cfdmiHbaPortInformationGroup | |
| mandatory | cfdmiNotificationGroup |
Notifications / Traps (1)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.9.9.373.0.1 |
This notification is generated by the FDMI
whenever it rejects a registration request. The FDMI should update the 'cfdmiRejectReasonCode' and 'cfdmiRejectReasonCodeExpl' objects with the corresponding reason code and reason code explanation before sending the notification. These two objects are also included along with the notification to provide the reason for the reject. |