WESTERN-MULTIPLEX-RAD10006-MIB
File:
WESTERN-MULTIPLEX-RAD10006-MIB.mib (96628 bytes)
Imported modules
Imported symbols
Defined Values
| radio |
1.3.6.1.4.1.3727.20.20 |
| OBJECT IDENTIFIER |
|
|
|
| config |
1.3.6.1.4.1.3727.20.20.1 |
| OBJECT IDENTIFIER |
|
|
|
| cnfgT1LineCode |
1.3.6.1.4.1.3727.20.20.1.1 |
| This persistent variable contains the current
T1 line encoding/decoding method.
'B8ZS' selects the Bipolar With 8-bit Zero Substitution
encoding/decoding.
'AMI' selects Alternate Mark Inversion encoding/
decoding.
The default value for this variable is 'B8ZS'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
b8zs(1), ami(2) |
|
| cnfgT1LineBuildOut |
1.3.6.1.4.1.3727.20.20.1.2 |
| This persistent variable contains the current T1
Line Build Out configuration for the radio.
For DSX-1 applications, line lengths from 0 to 655 feet
(as measured from the DS-1 connector to the DSX-1
cross connect) are selectable. The five partition
arrangement meets ANSI T1.102-1993 requirements when
using ABAM cable.
The default value for this variable is 'lb-0-133-ft'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
lb-0-133-ft(1), lb-133-266-ft(2), lb-266-399-ft(3), lb-399-533-ft(4), lb-533-655-ft(5) |
|
| cnfgT1NearEndRadioLoopback |
1.3.6.1.4.1.3727.20.20.1.3 |
| This non-persistent variable contains the current state of
the loopback mode for the radio side of the T1 channel
of the radio.
'enabled' reconfigures the T1 data path of the radio.
The data path is set to take data received from the radio
side of the system and send it back out the transmitter of
the radio.
'disabled' turns off the T1 channel radio loopback
mode, and allows T1 data received from the radio side of
the system to be presented to its Line Interface Unit, and
T1 data received from the Line Interface Unit to be
transmitted by the radio.
The default value for this variable is disabled(2). |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
disabled(1), enabled(2) |
|
| cnfgT1FarEndRadioLoopback |
1.3.6.1.4.1.3727.20.20.1.4 |
| This non-persistent variable contains the current state of
the loopback mode for the radio side of the T1 channel
of the remote radio.
'enabled' reconfigures the T1 data path of the radio.
The data path is set to take data received from the radio
side of the system and send it back out the transmitter of
the radio.
'disabled' turns off the T1 channel radio loopback
mode, and allows T1 data received from the radio side of
the system to be presented to its Line Interface Unit, and
T1 data received from the Line Interface Unit to be
transmitted by the radio.
The default value for this variable is disabled(2). |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
disabled(1), enabled(2) |
|
| cnfgAIS |
1.3.6.1.4.1.3727.20.20.1.6 |
| This non-persistent variable contains the configuration
setting of the AIS output. It allows the SNMP user to
control AIS output.
'enabled' enables the AIS output.
'disabled' disables the AIS output.
The default value for this variable is 'disabled'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
disabled(1), enabled(2) |
|
| cnfgOrderwireAddr |
1.3.6.1.4.1.3727.20.20.1.7 |
| This persistent variable contains the current number
of the two-digit engineering orderwire (EOW) phone
number of the handset connected to the radio. The phone
number can range from 00 to 99.
When a telephone user on another radio of this radio
network dials a two digit orderwire phone number matching
this variable's value, then this radio rings its bell.
The default value for this variable is '00', which sets
the phone number of the local orderwire handset to 00. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(2) |
|
| cnfgLinkSecurityCode |
1.3.6.1.4.1.3727.20.20.1.8 |
| This persistent variable contains the current number of the
12-byte security code. It allows the SNMP user to read and set
the link security code. The link security code has to be hex
numbers (0 to f).
There is no default value for this variable. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(12) |
|
| cnfgLearningFilter |
1.3.6.1.4.1.3727.20.20.1.9 |
| This persistent variable configures the learning filter.
'disabled' turns off the learning filter.
'enabled' turns on the learning filter.
There is no default value for this variable. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
disabled(1), enabled(2) |
|
| cnfgFiberOpticInterface |
1.3.6.1.4.1.3727.20.20.1.10 |
| This persistent variable configures the fiber interface.
'disabled' turns off the fiber interface.
'enabled' turns on the fiber interface.
There is no default value for this variable. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
disabled(1), enabled(2) |
|
| cnfgEthernetDuplex |
1.3.6.1.4.1.3727.20.20.1.11 |
| This persistent variable contains the current configuration
of the ethernet communication mode.
'full-duplex' indicates ethernet communicates in full duplex mode.
'half-duplex' indicates ethernet communicates in half duplex mode.
There is no default value for this variable. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
full-duplex(1), half-duplex(2) |
|
| cnfgDataRate |
1.3.6.1.4.1.3727.20.20.1.12 |
| This persistent variable contains the current configuration
of the data rate.
'full-duplex-45-MB' indicates 45 MB data rate with full duplex
operation.
datarate2 is undefined yet.
datarate3 is undefined yet.
There is no default value for this variable. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
full-duplex-45-MB(1), datarate2(2), datarate3(3) |
|
| cnfgInterfaceType |
1.3.6.1.4.1.3727.20.20.1.13 |
| This persistent variable contains the current configuration
of interface type.
't1-100BaseT' indicates 100BaseT and a T1 channel.
't1-10BaseT' indicates 10BaseT and a T1 channel.
There is no default value for this variable. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
t1-100BaseT(1), t1-10BaseT(2) |
|
| cnfgIDUSWVersion |
1.3.6.1.4.1.3727.20.20.1.14 |
| This persistent variable contains the current number of the
4-byte IDU software Version.
There is no default value for this variable. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(4) |
|
| cnfgNMUSWVersion |
1.3.6.1.4.1.3727.20.20.1.15 |
| This persistent variable contains the current number of the
4-byte NMU software Version.
There is no default value for this variable. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(4) |
|
| perf |
1.3.6.1.4.1.3727.20.20.4 |
| OBJECT IDENTIFIER |
|
|
|
| perfCurrentBER |
1.3.6.1.4.1.3727.20.20.4.1 |
| This variable. 'perfCurrentBER' contains a calculation of
the estimated bit error rate of the aggregate data channel,
after FEC decoding. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(8) |
|
| perfCurrentRSL |
1.3.6.1.4.1.3727.20.20.4.2 |
| This variable, 'perfCurrentRSL' contains the current
received signal level, measured in dBm. The received
signal level, or RSL, is measured in the Receiver Unit,
or RCVR, of the radio. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
|
|
| perfErrorSeconds |
1.3.6.1.4.1.3727.20.20.4.3 |
| This variable. 'perfErrorSeconds' contains a count of the
number of one second periods with one or more bit errors. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
|
|
| perfSeverelyErroredSeconds |
1.3.6.1.4.1.3727.20.20.4.4 |
| This variable. 'perfSeverelyErroredSeconds' contains a count
of the number of one second periods with an error rate greater
than 10^-6 for the entire one second. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
|
|
| perfMinRSL |
1.3.6.1.4.1.3727.20.20.4.5 |
| This variable,'perfMinRSL' contains the lowest received
signal level within the measuring period. The received
signal level, or RSL, is measured in dBm, in the Receiver
Unit, or RCVR, of the radio. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
|
|
| perfMaxRSL |
1.3.6.1.4.1.3727.20.20.4.6 |
| This variable, 'perfMaxRSL' contains the highest
received signal level within the measuring period.
The received signal level, or RSL, is measured in
dBm, in the Receiver Unit, or RCVR, of the radio. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
|
|
| perfElapsedSecondsSinceReset |
1.3.6.1.4.1.3727.20.20.4.7 |
| This variable, 'perfElapsedSecondsSinceReset' contains a value
which corresponds to the total number of seconds has elapsed
since the start of the performance measurement. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
|
|
| perfHistoryReset |
1.3.6.1.4.1.3727.20.20.4.8 |
| This variable, 'perfHistoryReset' is a command to clear all the
counters in the performance table.
Setting this variable to 'history-reset' will cause all the
counters in the performance table to be cleared.
Setting this variable to 'normal' has no effect to the performance
table. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
history-reset(1), normal(2) |
|
| status |
1.3.6.1.4.1.3727.20.20.2 |
| OBJECT IDENTIFIER |
|
|
|
| statRadioLogHealth |
1.3.6.1.4.1.3727.20.20.2.1 |
| This non-persistent variable indicates the current health
status of the radio, determined by the Network
Management Unit, or NMU's system event log. This MIB
variable can be polled to provide a high-level status of
the managed radio.
This variable is identical to 'logRadioHEALTH' defined in
the 'WESTERN-MULTIPLEX-MIB'.
This variable indicates the highest severity level of
any NMU system log record that has a 'health' and 'radio'
qualifiers. Records that do not have a 'health' and a
'Radio' qualifier do not effect this variable. Records
that have been 'NORMALIZED' (see the definition in
'logRecDescription' in 'WESTERN-MULTIPLEX-MIB') do not
effect this variable.
'critical-health' is the highest severity level, followed
in decreasing order by 'major-health', 'minor-health',
'warning-health', and 'normal-health', which is the
lowest 'health' severity level.
If this variable has a value of 'normal-health', then
either there are no records that effect health and are
qualified by 'Radio' in the system log, or the only health
effecting records qualified by 'radio' have a severity
level of 'normal-health'.
There is no default value for this variable. |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal-health(1), warning-health(2), minor-health(3), major-health(4), critical-health(5) |
|
| statNMULink |
1.3.6.1.4.1.3727.20.20.2.2 |
| This non-persistent variable contains the current status
of the radio to nmu link . This MIB variable can be polled to
provide a high-level status of the radio.
'link-down' indicates that the radio to nmu link is currently
down.
'link-up' indicates that the radio to nmu link is currently up.
The default value for this variable is link-down(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
link-down(1), link-up(2) |
|
| statAlarmSummary |
1.3.6.1.4.1.3727.20.20.2.3 |
| This non-persistent variable contains the current status
of the radio. This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio currently has no alarm
condition.
'alarm_triggered' indicates that the radio currently has one or
more alarm conditions.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statT1CodeViolation |
1.3.6.1.4.1.3727.20.20.2.22 |
| This non-persistent variable contains the current status
of the radio. This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio's T1 input currently has no
code violation alarm.
'alarm_triggered' indicates that the radio's T1 input currently has an
code violation alarm.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statT1LineDriver |
1.3.6.1.4.1.3727.20.20.2.23 |
| This non-persistent variable contains the current status
of the radio. This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio's T1 line build out currently
has no alarm conditions.
'alarm_triggered' indicates that the radio currently has an T1 line
build out alarm.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statT1AIS |
1.3.6.1.4.1.3727.20.20.2.24 |
| This non-persistent variable contains the current status
of the radio. This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio currently has no AIS output.
'alarm_triggered' indicates that the radio currently is generating
'Alarm indication Signal', or marking the T1 line with all ones, on
the transmit output.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statRadioSync |
1.3.6.1.4.1.3727.20.20.2.25 |
| This non-persistent variable contains the current status
of the radio. This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio currently has no frame loss
alarm.
'alarm_triggered' indicates that the radio currently has a loss of 5
or more consecutive frames on the received aggregate data.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statBitError |
1.3.6.1.4.1.3727.20.20.2.26 |
| This non-persistent variable contains the current status
of the radio. This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio signal currently has a bit
error rate, or BER, less than 10 to minus 6.
'alarm_triggered' indicates that the radio signal currently has a
bit error rate, or BER, less than 10 to minus 6.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statFan1 |
1.3.6.1.4.1.3727.20.20.2.27 |
| This non-persistent variable contains the current status
of the radio's . This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio fan 1 unit has no alarm.
'alarm_triggered' indicates that the radio fan 1 unit is not present,
unplugged, or is not rotating.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statFan2 |
1.3.6.1.4.1.3727.20.20.2.28 |
| This non-persistent variable contains the current status
of the radio's . This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio fan 2 unit has no alarm.
'alarm_triggered' indicates that the radio fan 2 unit is not present,
unplugged, or is not rotating.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statRxSynth |
1.3.6.1.4.1.3727.20.20.2.29 |
| This non-persistent variable contains the current status
of the radio's . This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio receive signal currently
has no sync alarm.
'alarm_triggered' indicates that the radio's receiver-synthesizer
is currently in an alarm condition.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| statTxSynth |
1.3.6.1.4.1.3727.20.20.2.30 |
| This non-persistent variable contains the current status
of the radio's . This MIB variable can be polled to provide
a high-level status of the radio.
'alarm_unknown' indicates that the radio to nmu link is currently
down and the radio status cannot be determined.
'alarm_normal' indicates that the radio Transmit signal currently
has no sync alarm.
'alarm_triggered' indicates that the radio's transmitter-synthesizer
is currently in an alarm condition.
The default value for this variable is alarm_unknown(1). |
| Status: mandatory |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
alarm-unknown(1), alarm-normal(2), alarm-triggered(3) |
|
| mgmt |
1.3.6.1.4.1.3727.20.20.3 |
| OBJECT IDENTIFIER |
|
|
|
| mgmtNMULinkTrapControl |
1.3.6.1.4.1.3727.20.20.3.1 |
| This persistent variable controls whether the Agent will
attempt to send the 'nmuLinkTrap' trap whenever the
link condition between Radio and the NMU has a transition.
The 'nmuLinkTrap' trap is defined in this MIB definition file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'normal'
state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 'nmuLinkTrap'
trap, other checks described below may prohibit this trap
from transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtNMULinkSeverity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in
'westmux.mib' file) for any of these above variables for
details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtNMULinkSeverity |
1.3.6.1.4.1.3727.20.20.3.2 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the link condition between the Radio and
the NMU.
This severity level variable is associated with the
'nmuLinkTrap' trap, and a log event message that indicates
a change in the Radio's link condition to the NMU.
'critical' is the highest severity level, followed in
decreasing order by 'major', 'minor', 'warning', and
'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtNMULinkTrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtT1CodeViolationTrapControl |
1.3.6.1.4.1.3727.20.20.3.5 |
| This persistent variable controls whether the Agent will
attempt to send the 't1CvTrap' trap whenever the
Radio has a transition of the T1 Code Violation condition.
The 't1CvTrap' trap is defined in this MIB definition
file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU
will only generate a SNMP trap on the transition to the
'normal' state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 't1CvTrap' trap,
other checks described below may prohibit this trap from
transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtT1CodeViolationSeverity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in
'westmux.mib' file) for any of these above variables for
details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtT1CodeViolationSeverity |
1.3.6.1.4.1.3727.20.20.3.6 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the T1 Code Violation condition.
This severity level variable is associated with the
't1CvTrap' trap, and a log event message that
indicates a change in the Radio's T1 Code Violation
condition.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtT1CodeViolationTrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtT1LineDriverTrapControl |
1.3.6.1.4.1.3727.20.20.3.7 |
| This persistent variable controls whether the Agent will
attempt to send the 't1LoTrap' trap whenever the radio has
a transition of the T1 line build out condition.
The 't1LoTrap' trap is defined in this MIB definition file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU
will only generate a SNMP trap on the transition to the
'normal' state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 't1LoTrap' trap,
other checks described below may prohibit this trap from
transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtT1LineDriverSeverity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in
'westmux.mib' file) for any of these above variables for
details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtT1LineDriverSeverity |
1.3.6.1.4.1.3727.20.20.3.8 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the T1 line build out condition.
This severity level variable is associated with the
't1LoTrap' trap, and a log event message that indicates
a change in the Radio's T1 line build out condition.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtT1LineDriverTrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtT1AISTrapControl |
1.3.6.1.4.1.3727.20.20.3.9 |
| This persistent variable controls whether the Agent will
attempt to send the 't1AisTrap' trap whenever the radio
has a transition of its T1 AIS Output condition.
The 't1AisTrap' trap is defined in this MIB definition file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU
will only generate a SNMP trap on the transition to the
'normal' state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 't1AisTrap' trap,
other checks described below may prohibit this trap from
transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtT1AISSeverity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in
'westmux.mib' file) for any of these above variables for
details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtT1AISSeverity |
1.3.6.1.4.1.3727.20.20.3.10 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the T1 AIS Output condition.
This severity level variable is associated with the
't1AisTrap' trap, and a log event message that indicates
a change in the Radio's AIS Out condition.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtT1AISTrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtRadioSyncTrapControl |
1.3.6.1.4.1.3727.20.20.3.11 |
| This persistent variable controls whether the Agent will
attempt to send the 'radioSyncTrap' trap whenever the
Radio has a transition of the Frame Loss Alarm.
The 'radioSyncTrap' trap is defined in this MIB definition file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU
will only generate a SNMP trap on the transition to the
'normal' state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 'radioSyncTrap' trap,
other checks described below may prohibit this trap from
transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtRadioSyncSeverity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in
'westmux.mib' file) for any of these above variables for
details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtRadioSyncSeverity |
1.3.6.1.4.1.3727.20.20.3.12 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the Frame Loss alarm on the Radio.
This severity level variable is associated with the
'radioSyncTrap' trap, and a log event message that
indicates a change in the Frame Loss Alarm within
the Radio.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtRadioSynccTrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtBitErrorTrapControl |
1.3.6.1.4.1.3727.20.20.3.13 |
| This persistent variable controls whether the Agent will
attempt to send the 'berTrap' trap whenever the Radio
has a transition of the Bit Error Rate 6 (or BER6) Alarm.
The 6 refers to a bit error rate of 10 to the minus 6
(1.0 E -6).
The 'berTrap' trap is defined in this MIB definition file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'normal'
state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 'berTrap'
trap, other checks described below may prohibit this trap
from transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtBitErrorSeverity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in 'westmux.mib'
file) for any of these above variables for details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtBitErrorSeverity |
1.3.6.1.4.1.3727.20.20.3.14 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the Bit Error Rate 6 (or BER6) Alarm on the
Radio. The 6 refers to a bit error rate of 10 to the minus
6 (1.0 E -6).
This severity level variable is associated with the
'berTrap' trap, and a log event message that indicates a
change in the BER 6 Alarm within the Radio.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtBitErrorTrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtFan1TrapControl |
1.3.6.1.4.1.3727.20.20.3.15 |
| This persistent variable controls whether the Agent will
attempt to send the 'fan1Trap' trap whenever the
FAN 1 Unit has a transition of its FAN alarm.
The 'fan1Trap' trap is defined in this MIB definition
file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU
will only generate a SNMP trap on the transition to the
'normal' state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 'fan1Trap' trap,
other checks described below may prohibit this trap from
transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtFan1Severity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in
'westmux.mib' file) for any of these above variables for
details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtFan1Severity |
1.3.6.1.4.1.3727.20.20.3.16 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the FAN alarm on the FAN1 Unit.
This severity level variable is associated with the
'fan1Trap' trap, and a log event message that
indicates a change in the FAN1 alarm.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtFan1TrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtFan2TrapControl |
1.3.6.1.4.1.3727.20.20.3.17 |
| This persistent variable controls whether the Agent will
attempt to send the 'fan2Trap' trap whenever the FAN2 Unit
has a transition of its FAN alarm.
The 'fan2Trap' trap is defined in this MIB definition
file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU
will only generate a SNMP trap on the transition to the
'normal' state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 'fan2Trap'
trap, other checks described below may prohibit this trap
from transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtFan2Severity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in
'westmux.mib' file) for any of these above variables for
details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtFan2Severity |
1.3.6.1.4.1.3727.20.20.3.18 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the FAN alarm on the FAN2 Unit.
This severity level variable is associated with the
'fan2Trap' trap, and a log event message that
indicates a change in the FAN2 alarm.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtFan2TrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtRxSynthTrapControl |
1.3.6.1.4.1.3727.20.20.3.19 |
| This persistent variable controls whether the Agent will
attempt to send the 'rxSynthTrap' trap whenever the
Radio has a transition of its receiver-sythesizer alarm
condition.
The 'rxSynthTrap' trap is defined in this MIB definition file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU
will only generate a SNMP trap on the transition to the
'normal' state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 'rxSynthTrap'
trap, other checks described below may prohibit this trap
from transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmRxSynthSeverity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in
'westmux.mib' file) for any of these above variables for
details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtRxSynthSeverity |
1.3.6.1.4.1.3727.20.20.3.20 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the receiver-sythesizer alarm conditionb on
the Radio.
This severity level variable is associated with the
'rxSynthTrap' trap, and a log event message that indicates
a change in this condition within the Radio.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtRxSynthTrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtTxSynthTrapControl |
1.3.6.1.4.1.3727.20.20.3.21 |
| This persistent variable controls whether the Agent will
attempt to send the 'txSynthTrap' trap whenever the
Radio has a transition of its tansmitter-synthesizer alarm
condition.
The 'TxSynthTrap' trap is defined in this MIB definition file.
'no-trap' indicates that the NMU, should not generate any
SNMP trap on any transition. This is the default value.
'send-trap-on-alarm-transition' indicates that the NMU will
only generate a SNMP trap on the transition to the 'alarm'
state.
'send-trap-on-normal-transition' indicates that the NMU
will only generate a SNMP trap on the transition to the
'normal' state.
'send-trap-on-both-transitions' indicates that the NMU will
generate a SNMP trap on any transition.
Whenever the SNMP Agent attempts to send the 'TxSynthTrap'
trap, other checks described below may prohibit this trap
from transmission.
Whenever this variable prohibits a trap from being sent,
then 'trapFilteredSpecific' will be incremented.
This MIB variable is the first of four checks that the NMU
Agent uses to filter traps, based upon 1) a specific
enable or disable control variable; 2) 'trapControl' which
offers a gross on/off/limit control; 3) 'trapMgrTable'
with 'trapMgrControl' and 'trapMgrAddress' which filters
whether enterprise traps (such as this trap) and/or
standard (RFC 1215) traps are sent to each specific trap
manager; and 4) 'trapSeverityFilter' which filters traps
according to a controlling severity variable for the
specific trap, which in this case is described below, and
is defined as 'mgmtTxSynthSeverity'.
Whenever any of these trap filters cause a trap to be
filtered, the corresponding MIB statistic is incremented.
These statistics are 'trapFilteredSpecific',
'trapFilteredControl', 'trapFilteredManager', and
'trapFilteredSeverity'.
See the MIB descriptions (in this file, and in 'westmux.mib'
file) for any of these above variables for details. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
no-trap(1), send-trap-on-alarm-transition(2), send-trap-on-normal-transition(3), send-trap-on-both-transitions(4) |
|
| mgmtTxSynthSeverity |
1.3.6.1.4.1.3727.20.20.3.22 |
| This persistent variable indicates the desired severity
level to be associated with the log event and the SNMP
trap that record the occurance of a particular event.
In this case, the event indicates the detection of a
transition of the transmitter-synthesizer alarm condition
on the Radio.
This severity level variable is associated with the
'txSynthTrap' trap, and a log event message that
indicates a change in this condition within the Radio.
'critical' is the highest severity level, followed
in decreasing order by 'major', 'minor', 'warning',
and 'normal', which is the lowest severity level.
The default severity level is 'normal'.
This trap may also be filtered by
'mgmtTxSynthTrapControl'. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
normal(1), warning(2), minor(3), major(4), critical(5) |
|
| mgmtTrapHysteresis |
1.3.6.1.4.1.3727.20.20.3.61 |
| This persistent variable indicates the desired hysteresis
time value that allows the trap management sub-system to
generate any of the 16 SNMP Western Multiplex radio
traps.
This control, allows a radio alarm event to be NORMALIZED
within the 'mgmtTrapHysteresis' time limit. If the event
is not normalized, then the associated radio trap will be
sent if not filtered by the associate 'mgmtXXXTrapControl'
variable, or the 'mgmtXXXSeverity' variable, which also
controls the generation of this trap. In addition
trap management controls may filter this trap from being
sent.
The units are in seconds with the default value value of
120 which is the maximum allowed. The value of 0 is the
minimum, which allows the trap to be generated
immediately. The timing resolution is plus/minus 15
seconds. |
| Status: mandatory |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
0..120 |
|
| nmuLinkTrap |
1 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in the link condition between
the Radio and the NMU..
This trap may be filtered by 'mgmtNMULinkTrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the
definition of this variable above for details about this
filter, and the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap
can be used by management stations and network administrators
to detect when a trap has been lost during transmission.
The 'mgmtNMULinkSeverity' variable bound within the trap
indicates the configured severity level associated with
this event.
A value of 'LINK-UP', indicates that the link between the
Radio and NMU is not in an alarm state. A value of 'LINK-DOWN',
however, means that the link between the two entities might
be down or one side stops responding to the othe side.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtNMULinkSeverity. |
| TRAP-TYPE |
|
|
|
| t1InTrap |
2 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in Radio, T1 Input condition.
This trap may be filtered by 'mgmtT1InputTrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the
definition of this variable above for details about this
filter, and the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap
can be used by management stations and network administrators
to detect when a trap has been lost during transmission.
The 'mgmtT1InputSeverity' variable bound within the trap
indicates the configured severity level associated with
this event.
A value of 'NORMAL', indicates that the T1 Input condition
is normal. A value of 'T1IN-ALM' indicates T1 line failure
due to loss of signal.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtT1InputSeverity; |
| TRAP-TYPE |
|
|
|
| t1CvTrap |
3 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition Radio's, Code Violation condition.
This trap may be filtered by 'mgmtT1CodeViolationTrapControl',
which is a specific Trap control that can be used to spcifically
enable or disable this trap. See the definition of this variable
above for details about this filter, and the other trap filtering
mechanisms.
The 'trapSequenceNumber,' variable bound within the trap can
be used by management stations and network administrators to
detect when a trap has been lost during transmission.
The 'mgmtT1CodeViolationSeverity' variable bound within the
trap indicates the configured severity level associated with
this event.
A value of 'NORMAL', indicates that the Code Violation condition
is normal. A value of 'T1CV-ALM' indicates code violation condition
on the T1 input.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtT1CodeViolationSeverity. |
| TRAP-TYPE |
|
|
|
| t1LoTrap |
4 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in Radio, T1 line build out
condition.
This trap may be filtered by 'mgmtT1LineDriverTrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the
definition of this variable above for details about this
filter, and the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap
can be used by management stations and network administrators
to detect when a trap has been lost during transmission.
The 'mgmtT1LineDriverSeverity' variable bound within the trap
indicates the configured severity level associated with
this event.
A value of 'NORMAL', indicates that the T1 Line build out
condition is normal. A value of 'T1LO-ALM' indicates T1 line
build out has an alarm.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtT1LineDriverSeverity; |
| TRAP-TYPE |
|
|
|
| t1AisTrap |
5 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in the Radio's,T1 AIS Output condition.
This trap may be filtered by 'mgmtT1AISTrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the
definition of this variable above for details about this
filter, and the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap can
be used by management stations and network administrators to
detect when a trap has been lost during transmission.
The 'mgmtT1AISSeverity' variable bound within the trap
indicates the configured severity level associated with
this event.
A value of 'NORMAL', indicates that the T1 AIS Output condition
is normal. A value of 'T1AIS-ALM', indicates that the Radio is
generating 'Alarm Indication Signal', or marking the T1 line
with all ones, on the transmit output.When this occurs there is
an interruption in the RF signal due to 'FRAME-LOSS', 'BER-3',
or a 'DEMUX' hard alarm conditions.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtT1AISSeverity. |
| TRAP-TYPE |
|
|
|
| radioSyncTrap |
6 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in the Radio's, Frame Loss alarm.
This trap may be filtered by 'mgmtRadioSyncTrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the
definition of this variable above for details about this
filter, and the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap can
be used by management stations and network administrators to
detect when a trap has been lost during transmission.
The 'mgmtRadioSyncSeverity' variable bound within the trap indicates
the configured severity level associated with this event.
A value of 'NORMAL', indicates that Frame Loss Alarm is not
in an alarm state. A value 'RADIOSYN-ALM' indicates a loss of 5 or
more consecutive frames on the received aggregate data (input
to the demultiplexer function of the MUX).
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtRadioSyncSeverity. |
| TRAP-TYPE |
|
|
|
| berTrap |
7 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in the Radio's, Bit Error Rate 6
(or BER6) Alarm. The 6 refers to a bit error rate of 10 to
the minus 6 (1.0 E -6).
This trap may be filtered by 'mgmtBitErrorTrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the
definition of this variable above for details about this
filter, and the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap can
be used by management stations and network administrators
to detect when a trap has been lost during transmission.
The 'mgmtBitErrorSeverity' variable bound within the trap
indicates the configured severity level associated with
this event.
A value of 'NORMAL', indicates that BER is less than 10 to the
minus 6. A value of 'BER-6', indicates that the radio signal has
a bit error rate, or BER, greater than 10 to minu 6, (1.0 E -6).
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtBitErrorSeverity. |
| TRAP-TYPE |
|
|
|
| fan1Trap |
8 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in the fan1 Unit's, alarm.
This trap may be filtered by 'mgmtFan1TrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the
definition of this variable above for details about this
filter, and the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap
can be used by management stations and network
administrators to detect when a trap has been lost during
transmission.
The 'mgmtFan1Severity' variable bound within the trap
indicates the configured severity level associated with
this event.
A value of 'NORMAL', indicates that the fan1 unit has no
alarm state. A value of 'FAN1-ALM', indicates that the fan1
unit is not present, unplugged, or is not rotating.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtFan1Severity. |
| TRAP-TYPE |
|
|
|
| fan2Trap |
9 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in the fan2 Unit's, alarm.
This trap may be filtered by 'mgmtFan2TrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the
definition of this variable above for details about this
filter, and the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap
can be used by management stations and network administrators
to detect when a trap has been lost during transmission.
The 'mgmtFan2Severity' variable bound within the trap
indicates the configured severity level associated with
this event.
A value of 'NORMAL', indicates that the fan2 unit has no
alarm state. A value of 'FAN2-ALM', indicates that the fan2
unit is not present, unplugged, or is not rotating.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtFan2Severity. |
| TRAP-TYPE |
|
|
|
| rxSynthTrap |
10 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in Radio's, receiver-synthesizer
alarm condition.
This trap may be filtered by 'mgmtRxSynthTrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the definition
of this variable above for details about this filter, and
the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap
can be used by management stations and network administrators
to detect when a trap has been lost during transmission.
The 'mgmtRxSynthSeverity' variable bound within the
trap indicates the configured severity level associated
with this event.
A value of 'NORMAL', indicates that receiver-synthesizer is not
in an alarm state. A value of 'RX-SYNTH-ALM', indicates that the
receiver synthesizer has an alarm.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtRxSynthSeverity. |
| TRAP-TYPE |
|
|
|
| txSynthTrap |
11 |
| This trap is generated by the SNMP Agent when the Agent
has detected a transition in Radio's, transmitter-synthesizer
alarm condition.
This trap may be filtered by 'mgmtTxSynthTrapControl',
which is a specific Trap control that can be used to
specifically enable or disable this trap. See the definition
of this variable above for details about this filter, and
the other trap filtering mechanisms.
The 'trapSequenceNumber,' variable bound within the trap
can be used by management stations and network administrators
to detect when a trap has been lost during transmission.
The 'mgmtTxSynthSeverity' variable bound within the
trap indicates the configured severity level associated
with this event.
A value of 'NORMAL', indicates that transmitter-synthesizer is
not in an alarm state. A value of 'TX-SYNTH-ALM', indicates that
the transmitter-synthesizer has an alarm condition.
The row/column variables included in the trap are:
system.trap.trapSequenceNumber;
radio.mgmt.mgmtTxSynthSeverity. |
| TRAP-TYPE |
|
|
|