Once an alarm is 'completed', monitoring for that
variable may be distributed within an enclosure to
another processor. Factors affecting this decision
include variable type, slot number, and processor
type. Furthermore, alarms which have identical
parameters (variable, interval, thresholds, etc.)
are viewed by the monitoring processor as a single
'object' to monitor.
Alarm variables falling into this category are a
subset of the repeater MIB and iTouch repeater MIB
objects.
This field represents the number of 'objects' this
system CPU is monitoring on behalf of alarms which
were distributed to it by a management processor.
Parsed from file it-rmon-mib.mib.txt
Company: None
Module: ITOUCH-RMON-MIB
Once an alarm is 'completed', monitoring for that
variable may be distributed within an enclosure to
another processor. Factors affecting this decision
include variable type, slot number, and processor
type. Furthermore, alarms which have identical
parameters (variable, interval, thresholds, etc.)
are viewed by the monitoring processor as a single
'object' to monitor.
Alarm variables falling into this category are a
subset of the repeater MIB and iTouch repeater MIB
objects.
This field represents the number of 'objects' this
system CPU is monitoring on behalf of alarms which
were distributed to it by a management processor.
Parsed from file ITOUCHHUB.mib
Module: ITOUCHHUB
xRmonMonitorRemote OBJECT-TYPE SYNTAX INTEGER (0..65535) ACCESS read-only STATUS mandatory DESCRIPTION " Once an alarm is 'completed', monitoring for that variable may be distributed within an enclosure to another processor. Factors affecting this decision include variable type, slot number, and processor type. Furthermore, alarms which have identical parameters (variable, interval, thresholds, etc.) are viewed by the monitoring processor as a single 'object' to monitor. Alarm variables falling into this category are a subset of the repeater MIB and iTouch repeater MIB objects. This field represents the number of 'objects' this system CPU is monitoring on behalf of alarms which were distributed to it by a management processor." ::= { xRmonMonitor 1 }
Vendor: MRV Communications, In-Reach Product Division
Module: ITOUCH-RMON-MIB
[Automatically extracted from oidview.com]
xRmonMonitorRemote OBJECT-TYPE SYNTAX INTEGER (0..65535) ACCESS read-only STATUS mandatory DESCRIPTION " Once an alarm is 'completed', monitoring for that variable may be distributed within an enclosure to another processor. Factors affecting this decision include variable type, slot number, and processor type. Furthermore, alarms which have identical parameters (variable, interval, thresholds, etc.) are viewed by the monitoring processor as a single 'object' to monitor. Alarm variables falling into this category are a subset of the repeater MIB and iTouch repeater MIB objects. This field represents the number of 'objects' this system CPU is monitoring on behalf of alarms which were distributed to it by a management processor." ::= { xRmonMonitor 1 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.33.31.1.1.0 | xRmonMonitorRemote | 0 | 0 | None |
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.33.31.1.2 | xRmonMonitorLocal | 1 | 1 | Once an alarm is 'completed', monitoring for that variable may be distributed within an enclosure to another processor. Factors … |
1.3.6.1.4.1.33.31.1.3 | xRmonLogClear | 1 | 1 | Set this field to 'execute' to delete all RMON log table entries. Setting to 'ready' has no effect. |
1.3.6.1.4.1.33.31.1.4 | xRmonLogTotal | 1 | 1 | This field reports the total number of RMON log entries created since the system was initialized. Clearing the log table does not… |
1.3.6.1.4.1.33.31.1.5 | xRmonLogLastDateTime | 1 | 1 | The local date and time of the system at the time an RMON log entry was last created. |
1.3.6.1.4.1.33.31.1.6 | xRmonTrapType | 1 | 1 | Use this field to specify the type of SNMP trap to generate when an alarm event occurs. The value 'standardFormat' formats the tr… |
1.3.6.1.4.1.33.31.1.7 | xRmonRepeaterManagement | 1 | 1 | This field enables and disables RMON monitoring of certain repeater related variables in the chassis. Set this field to 'enabled'… |
1.3.6.1.4.1.33.31.1.8 | xRmonAlarmActivate | 1 | 1 | Use this field to change the states of all completed alarms to 'active' or 'inactive'. Select 'activateAll' to make all completed… |
1.3.6.1.4.1.33.31.1.9 | xRmonAlarmClear | 1 | 1 | Set this field to 'deleteAll' to delete all alarm table entries and their associated event entries. Setting to 'noAction' has no … |
1.3.6.1.4.1.33.31.1.10 | xRmonAlarmCount | 4 | 8 | None |
1.3.6.1.4.1.33.31.1.11 | xRmonAlarmInitAction | 1 | 1 | Use this field to specify whether all alarms read from the parameter file should be placed in the 'active' state or the 'inactive… |