This document is the SNMP MIB module to manage and provision the
hardware components of the Nokia 7x50 device.
Copyright 2003-2015 Nokia. All rights reserved.
Reproduction of this document is authorized on the condition that
the foregoing copyright notice is included.
This SNMP MIB module (Specification) embodies Nokia's
proprietary intellectual property. Nokia retains
all title and ownership in the Specification, including any
revisions.
Nokia grants all interested parties a non-exclusive
license to use and distribute an unmodified copy of this
Specification in connection with management of Nokia
products, and without fee, provided this copyright notice and
license appear on all copies.
This Specification is supplied 'as is', and Nokia
makes no warranty, either express or implied, as to the use,
operation, condition, or performance of the Specification.
Generated when a SFP is installed in a MDA that supports
synchronous ethernet operation.
aluEqPortRS232Alarm
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.1
Generated when a RS232 interface alarm condition is detected.
It is generated only when the type of alarm being raised is enabled
in aluRS232ReportAlarm.
aluEqPortDataAlarmClear
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.10
Generated when a Data interface alarm condition is cleared.
It is generated only when the type of alarm being cleared is enabled
in aluDataReportAlarm.
aluDataLoopbackStarted
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.11
The aluDataLoopbackStarted notification is generated when a
loopback is provisioned on a Data port.
aluDataLoopbackStopped
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.12
The aluDataLoopbackStopped notification is generated when a
loopback is removed on a Data port. The value of
aluDataLoopback specifies the type of loopback that was
configured and has now been removed.
aluExtPethPsePortStatusChange
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.13
Generated when there is a change in Power Classification,
Detection Status, Fault Reason, or Oper Status on a power ethernet port.
aluSerialMddbSquelchStatusChanged
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.14
The aluSerialMddbSquelchStatusChanged notification is generated when the
Squelch Status of a scada bridge is changed. The value of
aluSerialMddbSquelchStatus indicates the new squelch status detected.
aluSerialMddbSquelchResetIssued
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.15
The aluSerialMddbSquelchResetIssued notification is generated when user
reset the squelch of the scada bridge. The value of
aluSerialMddbSquelchStatus indicates the existing squelch status.
aluGnssPortStatusChange
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.16
The aluGnssPortStatusChange notification is generated when
there is a change in the status of the GNSS receiver. This
notification
is a point-in-time status change event.
[CAUSE] This notification may be triggered for a variety of reasons
including (but not limited to):
1) The antenna is experiencing fault issues
2) The number of visible satellites is too low
[EFFECT] The GNSS receiver is not able to provide a sync-worthy clock
signal.
[RECOVERY] If the customer is expecting the GNSS receiver to be
locked,
the customer will need to determine the root cause (for example,
insufficient visible satellites) and resolve the issue (for example,
ensure aluGnssPortElevationMaskAngle is set accordingly).
aluPcmSquelchStatusChanged
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.17
The aluPcmSquelchStatusChanged notification is generated when the
Squelch Status of a scada bridge is changed. The value of
aluPcmSquelchStatus indicates the new squelch status detected.
aluPcmSquelchResetIssued
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.18
The aluPcmSquelchResetIssued notification is generated when user
reset the squelch of the scada bridge. The value of
aluPcmSquelchStatus indicates the existing squelch status.
aluRS232ControlLeadsSignalChange
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.19
The aluRS232ControlLeadsSignalChange notification is generated when
there is a change in the status of a Serial control lead signal. This
notification is a point-in-time status change event.
[CAUSE] This notification may be triggered for a variety of reasons.
One example is that the far-end equipment has been disconnected.
[EFFECT] Alert user of transitions.
[RECOVERY] Determine root cause and resolve accordingly.
aluEqPortRS232AlarmClear
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.2
Generated when a RS232 interface alarm condition is cleared.
It is generated only when the type of alarm being cleared is enabled
in aluRS232ReportAlarm.
aluRS232SquelchStatusChange
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.20
The aluRS232SquelchStatusChange notification is generated when
there is a change in the status of squelch on the respective channel.
This notification is a point-in-time status change event.
[CAUSE] This notification may be triggered for the following reasons:
1) A continuous stream of data is being received for a specified
period of time, aluRS232SocketSquelchDelay.
2) The continuous stream of data is no longer being received for a
specified period of time, aluRS232SocketUnsquelchDelay.
[EFFECT] Incoming data will be suppressed or unsuppressed accordingly.
[RECOVERY] Determine root cause of far-end sending continuous data
and resolve accordingly.
aluRS232SquelchResetIssued
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.21
The aluRS232SquelchResetIssued notification is generated when the
user triggers a manual reset of squelch via
aluRS232SocketSquelchReset. The value of aluRS232SocketSquelchStatus
indicates the existing squelch status.
aluRS232ClockSyncStateChange
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.22
The aluRS232ClockSyncStateChange notification is generated when the
aluRS232ClockSyncState changes for an RS232 interface.
aluExtDS0ChanGrpLoopbackStarted
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.23
The aluExtDS0ChanGrpLoopbackStarted notification is generated when a
loopback is provisioned on a DS0 channel group.
aluExtDS0ChanGrpLoopbackStopped
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.24
The aluExtDS0ChanGrpLoopbackStopped notification is generated when a
loopback is removed on a DS0 channel group. The value of
aluExtDS0ChanGroupLoopback specifies the type of loopback that was
configured and has now been removed.
aluRS232LoopbackStarted
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.3
The aluRS232LoopbackStarted notification is generated when a
loopback is provisioned on a RS-232/V.35/X.21/RS-530 port.
aluRS232LoopbackStopped
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.4
The aluRS232LoopbackStopped notification is generated when a
loopback is removed on a RS-232/V.35/X.21/RS-530 port. The value of
aluRS232Loopback specifies the type of loopback that was
configured and has now been removed.
aluVoiceLoopbackStarted
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.5
The aluVoiceLoopbackStarted notification is generated when a
loopback is provisioned on a voice port.
aluVoiceLoopbackStopped
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.6
The aluVoiceLoopbackStopped notification is generated when a
loopback is removed on a voice port. The value of
aluVoiceLoopback specifies the type of loopback that was
configured and has now been removed.
aluGponPortInbandAlarm
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.7
Generated when an alarm condition is detected on the inband signaling
mechanism between the ONT and SAR
aluGponPortInbandAlarmClear
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.8
Generated when an alarm condition is cleared on the inband signaling
mechanism between the ONT and SAR
aluEqPortDataAlarm
.1.3.6.1.4.1.6527.6.1.2.3.2.2.0.9
Generated when a Data interface alarm condition is detected.
It is generated only when the type of alarm being raised is enabled
in aluDataReportAlarm.
AluDataReportStatus
aluPortMIBModule 
aluPortDiscardStatsTable 
aluPortDiscardsStatsEntry 
aluPortInL2AddrProtoDiscards 
aluLsrIpLoadBalBtmOfStk 
aluPortEtherSfpESyncCompatibility