BAY-STACK-SFF-MIB

Monitored by Observium
        Avaya SFF MIB
        
Copyright 2012 Avaya, Inc.
All rights reserved.
This Avaya SNMP Management Information Base
Specification embodies Avaya's confidential and
proprietary intellectual property. Avaya retains
all title and ownership in the Specification, including any
revisions.
        
This Specification is supplied 'AS IS,' and Avaya
makes no warranty, either express or implied, as to the use,
operation, condition, or performance of the Specification.
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Sensors
Explore Observium network monitoring
Source file
BAY-STACK-SFF-MIB
Last revised
Identity
bayStackDdiSfpMib
Base OID
1.3.6.1.4.1.45.5.29
Imported Objects
IF-MIB InterfaceIndex
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page)
SYNOPTICS-ROOT-MIB bayStackMibs
Net-SNMP examples using the nortel 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 'BAY-STACK-SFF-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'BAY-STACK-SFF-MIB::bayStackDdiSfpMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'BAY-STACK-SFF-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'BAY-STACK-SFF-MIB::bayStackDdiSfpMib'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (33)
5 directly used by Observium
.1.3.6.1.4.1.45.5.29
.1.3.6.1.4.1.45.5.29.0
.1.3.6.1.4.1.45.5.29.1
.1.3.6.1.4.1.45.5.29.1.2
.1.3.6.1.4.1.45.5.29.1.2.1
.1.3.6.1.4.1.45.5.29.1.2.1.1
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.10
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.11
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.12
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.13
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.14
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.15
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.16
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.17
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.18
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.19
Enumeration
.1.3.6.1.4.1.45.5.29.1.2.1.2
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.20
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.21
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.22
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.23
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.24
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.25
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.26
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.27
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.28
Enumeration
.1.3.6.1.4.1.45.5.29.1.2.1.3
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.4
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.5
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.6
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.7
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.8
Integer32
.1.3.6.1.4.1.45.5.29.1.2.1.9
Dependencies (7) 3 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
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. IANAifType-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMPv2-MIBrfc
  6. IF-MIBrfc
  7. SYNOPTICS-ROOT-MIBnortel
  8. BAY-STACK-SFF-MIBnortelselected
Notifications / Traps (15)
NameOIDDescription
.1.3.6.1.4.1.45.5.29.0.1
This notification is generated when a transceiver's temperature reaches an alarm level.
.1.3.6.1.4.1.45.5.29.0.10
This notification is generated when a transceiver's transmit power reaches an alarm level.
.1.3.6.1.4.1.45.5.29.0.11
This notification is generated when a transceiver's transmit power reaches a warning level.
.1.3.6.1.4.1.45.5.29.0.12
This notification is generated when a transceiver's transmit power reaches normal operating level.
The notification is triggered after the transceiver's transmit power has reached a warning or alarm
level and then returns to normal level.
.1.3.6.1.4.1.45.5.29.0.13
This notification is generated when a transceiver's receive power reaches an alarm level.
.1.3.6.1.4.1.45.5.29.0.14
This notification is generated when a transceiver's receive power reaches a warning level.
.1.3.6.1.4.1.45.5.29.0.15
This notification is generated when a transceiver's receive power reaches normal operating level.
The notification is triggered after the transceiver's receive power has reached a warning or alarm
level and then returns to normal level.
.1.3.6.1.4.1.45.5.29.0.2
This notification is generated when a transceiver's temperature reaches a warning level.
.1.3.6.1.4.1.45.5.29.0.3
This notification is generated when a transceiver's temperature reaches normal operating level.
The notification is triggered after the transceiver's temperature has reached a warning or alarm
level and then returns to normal level.
.1.3.6.1.4.1.45.5.29.0.4
This notification is generated when a transceiver's voltage reaches an alarm level.
.1.3.6.1.4.1.45.5.29.0.5
This notification is generated when a transceiver's voltage reaches a warning level.
.1.3.6.1.4.1.45.5.29.0.6
This notification is generated when a transceiver's voltage reaches normal operating level.
The notification is triggered after the transceiver's voltage has reached a warning or alarm
level and then returns to normal level.
.1.3.6.1.4.1.45.5.29.0.7
This notification is generated when a transceiver's bias reaches an alarm level.
.1.3.6.1.4.1.45.5.29.0.8
This notification is generated when a transceiver's bias reaches a warning level.
.1.3.6.1.4.1.45.5.29.0.9
This notification is generated when a transceiver's bias reaches normal operating level.
The notification is triggered after the transceiver's bias has reached a warning or alarm
level and then returns to normal level.