CISCO-FCTRACEROUTE-MIB

        The MIB module for the management of the
Fibre Channel Trace Route functionality.
    
Source file
CISCO-FCTRACEROUTE-MIB
Last revised
Identity
ciscoFcTraceRouteMIB
Base OID
1.3.6.1.4.1.9.9.296
Imported Objects
CISCO-FCPING-MIB FcStartOper
CISCO-SMI ciscoMgmt
CISCO-ST-TC FcAddress FcAddressType FcNameId VsanIndex
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 RowStatus 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-FCTRACEROUTE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-FCTRACEROUTE-MIB::ciscoFcTraceRouteMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-FCTRACEROUTE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-FCTRACEROUTE-MIB::ciscoFcTraceRouteMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (27)
.1.3.6.1.4.1.9.9.296
.1.3.6.1.4.1.9.9.296.1
.1.3.6.1.4.1.9.9.296.1.1
.1.3.6.1.4.1.9.9.296.1.1.1
.1.3.6.1.4.1.9.9.296.1.1.1.1
Unsigned32
.1.3.6.1.4.1.9.9.296.1.1.1.1.1
.1.3.6.1.4.1.9.9.296.1.1.1.1.10
.1.3.6.1.4.1.9.9.296.1.1.1.1.2
.1.3.6.1.4.1.9.9.296.1.1.1.1.3
.1.3.6.1.4.1.9.9.296.1.1.1.1.4
secondsUnsigned32
.1.3.6.1.4.1.9.9.296.1.1.1.1.5
.1.3.6.1.4.1.9.9.296.1.1.1.1.6
Enumeration
.1.3.6.1.4.1.9.9.296.1.1.1.1.7
millisecondsUnsigned32
.1.3.6.1.4.1.9.9.296.1.1.1.1.8
.1.3.6.1.4.1.9.9.296.1.1.1.1.9
.1.3.6.1.4.1.9.9.296.1.2
.1.3.6.1.4.1.9.9.296.1.2.1
.1.3.6.1.4.1.9.9.296.1.2.1.1
Unsigned32
.1.3.6.1.4.1.9.9.296.1.2.1.1.1
.1.3.6.1.4.1.9.9.296.1.2.1.1.2
.1.3.6.1.4.1.9.9.296.1.2.1.1.3
Unsigned32
.1.3.6.1.4.1.9.9.296.1.2.1.1.4
.1.3.6.1.4.1.9.9.296.1.3
.1.3.6.1.4.1.9.9.296.1.3.0
.1.3.6.1.4.1.9.9.296.2
.1.3.6.1.4.1.9.9.296.2.1
.1.3.6.1.4.1.9.9.296.2.2
Dependencies (6) 6 direct 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-ST-TCcisco
  5. SNMPv2-CONFrfc
  6. CISCO-FCPING-MIBcisco
  7. CISCO-FCTRACEROUTE-MIBciscoselected
Conformance Groups (3)
A collection of objects for configuring
Fibre Channel Trace route functionality.
.1.3.6.1.4.1.9.9.296.2.2.1
A collection of objects for displaying
Fibre Channel Trace route results.
.1.3.6.1.4.1.9.9.296.2.2.2
A collection of notification(s) for
monitoring Fibre Channel Trace route
test completion.
.1.3.6.1.4.1.9.9.296.2.2.3
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.296.2.1.1
The compliance statement for entities which
implement the Fibre Channel Trace Route
functionality.
Required groups
Object refinements
ObjectAccessSyntaxDescription
fcTraceRouteRowStatus readwrite
active(1), createAndGo(4), destroy(6)
Only three values 'createAndGo', 'destroy' and
'active' out of the six enumerated values need to be
supported.
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.9.296.1.3.0.1
This notification is generated whenever a
trace route test is completed and the
corresponding instance of
fcTraceRouteTrapOnCompletion is set to 'true'.

The agent is encouraged to append, at the end
of this notification's varbindlist, one varbind
for each hop of the traced route. Each such
appended varbind would contain an instance of
fcTraceRouteHopsHopAddr object. If the number of
varbinds required would cause the notification
to approach it's maximum size, the number of
instances of fcTraceRouteHopsHopAddr will be
truncated suitably.