Describes the current operational state of the
alarm and allows you to make limited changes in
the state of the alarm for purposes of managing
its state.
You may set this field to one of: underCreation,
active, inactive, and delete. All other values
report current status.
underCreation: Alarm configuration is incomplete.
You may modify alarm parameters. No monitoring
is taking place for the alarm. An alarm is saved
in a parameter file after configuration complete.
Select this state before changing a previously
completed alarm.
active: Alarm configuration is complete and active
monitoring of the alarm variable is in progress.
Select this state to complete an alarm or to begin
active monitioring of the alarm variable.
inactive: No monitoring of the alarm variable is
actively taking place. Select this state when you
want to temporarily suppress monitoring for the
alarm. Select 'active' to begin monitoring again.
delete: Select this state when you want to delete
this alarm and all log entries associated with it.
held: Active monitoring of the alarm variable is not
taking place because this system does not have RMON
Repeater Management set to 'enabled'. Once you do
this, alarm monitoring begins automatically.
noHubCard: The target slot does not contain a
management card or repeater I/O card capable of
monitoring. Monitoring will begin automatically
once the target slot is loaded with a supported
configuration.
oldFirmware: The I/O card in the target slot does
not contain monitoring firmware. Monitoring will
begin automatically once that card has been loaded
with current scm firmware.
slotTimeout: The target slot did not respond to
attempts to activate the alarm. May happen if the
management card in the target slot does not contain
monitoring software. Monitoring begins automatically
once the target slot has been repaired or loaded
with current software.
slotFailed: Active monitoring of the alarm
variable stopped because the target slot was not
operating properly. Monitoring automatically
resumes once the target slot has recovered.
monitorStopped: Active monitoring of the alarm
variable stopped due to some error. This can
occur if the variable no longer exists because a
related configuration change has made it invalid.
Correct the condition and re-activate the alarm.
unknownVariable: The alarm variable specified by the
object ID is not recognized in the currently running
system. Correct the entry.
keysMissing: One or more required key values are not
specified in the alarm variable object ID. Correct
the entry.
noResources: Not enough system resources exist to
activate this alarm. Reduce the use of packet buffers
or available memory and re-activate the alarm.
loading: The alarm is being read from a parameter
file and will soon be activated. This condition
is transient.
activating: Monitoring of the alarm variable will
begin soon. This condition is transient.
deactivating: Monitoring of the alarm variable will
stop soon. This condition is transient.
unsupported: Monitoring for the alarm variable is
not supported by the target slot. Monitoring will
begin once that card is loaded with current scm
firmware or software.
unknownAlarm: Monitoring stopped because the target
slot reset. Monitoring will continue shortly.
inconsistency: Internal system error.
invalidFlags: Internal system error.
invalidSlot: Alarm specified for a slot which does
not exist in the chassis. Modify and re-activate.
inaccessible: Monitoring of the alarm variable could
not begin. This can occur if the key values are
invalid for the variable. Correct and re-activate
the alarm.
otherError: An unspecified error has occurred.
Parsed from file it-rmon-mib.mib.txt
Company: None
Module: ITOUCH-RMON-MIB
Describes the current operational state of the
alarm and allows you to make limited changes in
the state of the alarm for purposes of managing
its state.
You may set this field to one of: underCreation,
active, inactive, and delete. All other values
report current status.
underCreation: Alarm configuration is incomplete.
You may modify alarm parameters. No monitoring
is taking place for the alarm. An alarm is saved
in a parameter file after configuration complete.
Select this state before changing a previously
completed alarm.
active: Alarm configuration is complete and active
monitoring of the alarm variable is in progress.
Select this state to complete an alarm or to begin
active monitioring of the alarm variable.
inactive: No monitoring of the alarm variable is
actively taking place. Select this state when you
want to temporarily suppress monitoring for the
alarm. Select 'active' to begin monitoring again.
delete: Select this state when you want to delete
this alarm and all log entries associated with it.
held: Active monitoring of the alarm variable is not
taking place because this system does not have RMON
Repeater Management set to 'enabled'. Once you do
this, alarm monitoring begins automatically.
noHubCard: The target slot does not contain a
management card or repeater I/O card capable of
monitoring. Monitoring will begin automatically
once the target slot is loaded with a supported
configuration.
oldFirmware: The I/O card in the target slot does
not contain monitoring firmware. Monitoring will
begin automatically once that card has been loaded
with current scm firmware.
slotTimeout: The target slot did not respond to
attempts to activate the alarm. May happen if the
management card in the target slot does not contain
monitoring software. Monitoring begins automatically
once the target slot has been repaired or loaded
with current software.
slotFailed: Active monitoring of the alarm
variable stopped because the target slot was not
operating properly. Monitoring automatically
resumes once the target slot has recovered.
monitorStopped: Active monitoring of the alarm
variable stopped due to some error. This can
occur if the variable no longer exists because a
related configuration change has made it invalid.
Correct the condition and re-activate the alarm.
unknownVariable: The alarm variable specified by the
object ID is not recognized in the currently running
system. Correct the entry.
keysMissing: One or more required key values are not
specified in the alarm variable object ID. Correct
the entry.
noResources: Not enough system resources exist to
activate this alarm. Reduce the use of packet buffers
or available memory and re-activate the alarm.
loading: The alarm is being read from a parameter
file and will soon be activated. This condition
is transient.
activating: Monitoring of the alarm variable will
begin soon. This condition is transient.
deactivating: Monitoring of the alarm variable will
stop soon. This condition is transient.
unsupported: Monitoring for the alarm variable is
not supported by the target slot. Monitoring will
begin once that card is loaded with current scm
firmware or software.
unknownAlarm: Monitoring stopped because the target
slot reset. Monitoring will continue shortly.
inconsistency: Internal system error.
invalidFlags: Internal system error.
invalidSlot: Alarm specified for a slot which does
not exist in the chassis. Modify and re-activate.
inaccessible: Monitoring of the alarm variable could
not begin. This can occur if the key values are
invalid for the variable. Correct and re-activate
the alarm.
otherError: An unspecified error has occurred.
Parsed from file ITOUCHHUB.mib
Module: ITOUCHHUB
mbAlarmStatus OBJECT-TYPE SYNTAX INTEGER { underCreation(1), active(2), inactive(3), delete(4), held(5), noHubCard(6), oldFirmware(7), slotTimeout(8), slotFailed(9), monitorStopped(10), unknownVariable(11), keysMissing(12), noResources(13), loading(14), activating(15), deactivating(16), unsupported(17), unknownAlarm(18), inconsistency(19), invalidFlags(20), invalidSlot(21), inaccessible(22), otherError(23) } ACCESS read-write STATUS mandatory DESCRIPTION " Describes the current operational state of the alarm and allows you to make limited changes in the state of the alarm for purposes of managing its state. You may set this field to one of: underCreation, active, inactive, and delete. All other values report current status. underCreation: Alarm configuration is incomplete. You may modify alarm parameters. No monitoring is taking place for the alarm. An alarm is saved in a parameter file after configuration complete. Select this state before changing a previously completed alarm. active: Alarm configuration is complete and active monitoring of the alarm variable is in progress. Select this state to complete an alarm or to begin active monitioring of the alarm variable. inactive: No monitoring of the alarm variable is actively taking place. Select this state when you want to temporarily suppress monitoring for the alarm. Select 'active' to begin monitoring again. delete: Select this state when you want to delete this alarm and all log entries associated with it. held: Active monitoring of the alarm variable is not taking place because this system does not have RMON Repeater Management set to 'enabled'. Once you do this, alarm monitoring begins automatically. noHubCard: The target slot does not contain a management card or repeater I/O card capable of monitoring. Monitoring will begin automatically once the target slot is loaded with a supported configuration. oldFirmware: The I/O card in the target slot does not contain monitoring firmware. Monitoring will begin automatically once that card has been loaded with current scm firmware. slotTimeout: The target slot did not respond to attempts to activate the alarm. May happen if the management card in the target slot does not contain monitoring software. Monitoring begins automatically once the target slot has been repaired or loaded with current software. slotFailed: Active monitoring of the alarm variable stopped because the target slot was not operating properly. Monitoring automatically resumes once the target slot has recovered. monitorStopped: Active monitoring of the alarm variable stopped due to some error. This can occur if the variable no longer exists because a related configuration change has made it invalid. Correct the condition and re-activate the alarm. unknownVariable: The alarm variable specified by the object ID is not recognized in the currently running system. Correct the entry. keysMissing: One or more required key values are not specified in the alarm variable object ID. Correct the entry. noResources: Not enough system resources exist to activate this alarm. Reduce the use of packet buffers or available memory and re-activate the alarm. loading: The alarm is being read from a parameter file and will soon be activated. This condition is transient. activating: Monitoring of the alarm variable will begin soon. This condition is transient. deactivating: Monitoring of the alarm variable will stop soon. This condition is transient. unsupported: Monitoring for the alarm variable is not supported by the target slot. Monitoring will begin once that card is loaded with current scm firmware or software. unknownAlarm: Monitoring stopped because the target slot reset. Monitoring will continue shortly. inconsistency: Internal system error. invalidFlags: Internal system error. invalidSlot: Alarm specified for a slot which does not exist in the chassis. Modify and re-activate. inaccessible: Monitoring of the alarm variable could not begin. This can occur if the key values are invalid for the variable. Correct and re-activate the alarm. otherError: An unspecified error has occurred." ::= { xRmonMBConfig 16 }
Vendor: MRV Communications, In-Reach Product Division
Module: ITOUCH-RMON-MIB
[Automatically extracted from oidview.com]
mbAlarmStatus OBJECT-TYPE SYNTAX INTEGER { underCreation(1), active(2), inactive(3), delete(4), held(5), noHubCard(6), oldFirmware(7), slotTimeout(8), slotFailed(9), monitorStopped(10), unknownVariable(11), keysMissing(12), noResources(13), loading(14), activating(15), deactivating(16), unsupported(17), unknownAlarm(18), inconsistency(19), invalidFlags(20), invalidSlot(21), inaccessible(22), otherError(23) } ACCESS read-write STATUS mandatory DESCRIPTION " Describes the current operational state of the alarm and allows you to make limited changes in the state of the alarm for purposes of managing its state. You may set this field to one of: underCreation, active, inactive, and delete. All other values report current status. underCreation: Alarm configuration is incomplete. You may modify alarm parameters. No monitoring is taking place for the alarm. An alarm is saved in a parameter file after configuration complete. Select this state before changing a previously completed alarm. active: Alarm configuration is complete and active monitoring of the alarm variable is in progress. Select this state to complete an alarm or to begin active monitioring of the alarm variable. inactive: No monitoring of the alarm variable is actively taking place. Select this state when you want to temporarily suppress monitoring for the alarm. Select 'active' to begin monitoring again. delete: Select this state when you want to delete this alarm and all log entries associated with it. held: Active monitoring of the alarm variable is not taking place because this system does not have RMON Repeater Management set to 'enabled'. Once you do this, alarm monitoring begins automatically. noHubCard: The target slot does not contain a management card or repeater I/O card capable of monitoring. Monitoring will begin automatically once the target slot is loaded with a supported configuration. oldFirmware: The I/O card in the target slot does not contain monitoring firmware. Monitoring will begin automatically once that card has been loaded with current scm firmware. slotTimeout: The target slot did not respond to attempts to activate the alarm. May happen if the management card in the target slot does not contain monitoring software. Monitoring begins automatically once the target slot has been repaired or loaded with current software. slotFailed: Active monitoring of the alarm variable stopped because the target slot was not operating properly. Monitoring automatically resumes once the target slot has recovered. monitorStopped: Active monitoring of the alarm variable stopped due to some error. This can occur if the variable no longer exists because a related configuration change has made it invalid. Correct the condition and re-activate the alarm. unknownVariable: The alarm variable specified by the object ID is not recognized in the currently running system. Correct the entry. keysMissing: One or more required key values are not specified in the alarm variable object ID. Correct the entry. noResources: Not enough system resources exist to activate this alarm. Reduce the use of packet buffers or available memory and re-activate the alarm. loading: The alarm is being read from a parameter file and will soon be activated. This condition is transient. activating: Monitoring of the alarm variable will begin soon. This condition is transient. deactivating: Monitoring of the alarm variable will stop soon. This condition is transient. unsupported: Monitoring for the alarm variable is not supported by the target slot. Monitoring will begin once that card is loaded with current scm firmware or software. unknownAlarm: Monitoring stopped because the target slot reset. Monitoring will continue shortly. inconsistency: Internal system error. invalidFlags: Internal system error. invalidSlot: Alarm specified for a slot which does not exist in the chassis. Modify and re-activate. inaccessible: Monitoring of the alarm variable could not begin. This can occur if the key values are invalid for the variable. Correct and re-activate the alarm. otherError: An unspecified error has occurred." ::= { xRmonMBConfig 16 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.33.31.2.1.16.0 | mbAlarmStatus | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.33.31.2.1.1 | mbAlarmIndex | 1 | 1 | This field can be either the index of an existing alarm (as seen in the alarm summary view) or a new number to create a new alarm… |
| 1.3.6.1.4.1.33.31.2.1.2 | mbAlarmInterval | 1 | 1 | The interval in seconds over which the variable is sampled and compared with the rising and falling thresholds. If the monitored… |
| 1.3.6.1.4.1.33.31.2.1.3 | mbAlarmVariable | 1 | 1 | This value shows the SNMP object identifier of the variable being sampled. Only variables that have an SNMP 'SYNTAX' of INTEGER,… |
| 1.3.6.1.4.1.33.31.2.1.4 | mbAlarmInterpretation | 1 | 1 | Use this field when you want to select an alarm variable without specifying its entire SNMP object identifier. First, modify thi… |
| 1.3.6.1.4.1.33.31.2.1.5 | mbAlarmKey1Meaning | 1 | 1 | This field describes how its adjacent key value field will be interpreted when building a complete SNMP object identifier for the… |
| 1.3.6.1.4.1.33.31.2.1.6 | mbAlarmKey1 | 1 | 1 | Specify a value here according the the instructions given in its adjacent prompt field. That prompt explains how this field will… |
| 1.3.6.1.4.1.33.31.2.1.7 | mbAlarmKey2Meaning | 1 | 1 | This field describes how its adjacent key value field will be interpreted when building a complete SNMP object identifier for the… |
| 1.3.6.1.4.1.33.31.2.1.8 | mbAlarmKey2 | 1 | 1 | Specify a value here according the the instructions given in its adjacent prompt field. That prompt explains how this field will… |
| 1.3.6.1.4.1.33.31.2.1.9 | mbAlarmSampleType | 1 | 1 | Use this field to select the method of calculating the value to be compared against the thresholds. When you set this to 'absolut… |
| 1.3.6.1.4.1.33.31.2.1.10 | mbAlarmValue | 1 | 1 | This field shows the value of the alarm variable at the end of the most recent monitoring interval. If the alarm sample type is … |
| 1.3.6.1.4.1.33.31.2.1.11 | mbAlarmRisingThreshold | 1 | 1 | This is the rising threshold value for the alarm. When the current alarm value, specified by the alarm sample type, is greater th… |
| 1.3.6.1.4.1.33.31.2.1.12 | mbAlarmFallingThreshold | 1 | 1 | This is the falling threshold value for the alarm. When the current alarm value, specified by the alarm sample type, is less than… |
| 1.3.6.1.4.1.33.31.2.1.13 | mbAlarmRisingEventType | 1 | 1 | Use this field to indicate the type of notification to make when the alarm variable exceeds its rising threshold. The default ac… |
| 1.3.6.1.4.1.33.31.2.1.14 | mbAlarmFallingEventType | 1 | 1 | Use this field to indicate the type of notification to make when the alarm variable exceeds its falling threshold. The default a… |
| 1.3.6.1.4.1.33.31.2.1.15 | mbAlarmSummary | 1 | 1 | As you make changes to the to alarm settings, this field is filled with an easily readable summary of the alarm parameters. This… |