ITOUCH-RMON-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
57
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
57 total| Object Name |
|---|
xRmon OBJECT IDENTIFIER .1.3.6.1.4.1.33.31 |
RFC1155-SMI Unknown .1.3.6.1.4.1.33.31 |
iTouchAlarm} TRAP-TYPE .1.3.6.1.4.1.33.31.0.1 |
xRmonMonitor OBJECT IDENTIFIER .1.3.6.1.4.1.33.31.1 |
xRmonMonitorRemoteOnce 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.ro INTEGER .1.3.6.1.4.1.33.31.1.1 |
xRmonMonitorLocalOnce 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, objects it did not
distribute to another processor.ro INTEGER .1.3.6.1.4.1.33.31.1.2 |
xRmonLogClearSet this field to 'execute' to delete all RMON log
table entries. Setting to 'ready' has no effect.rw Enumeration .1.3.6.1.4.1.33.31.1.3 |
xRmonLogTotalThis field reports the total number of RMON log
entries created since the system was initialized.
Clearing the log table does not change this value.ro Counter .1.3.6.1.4.1.33.31.1.4 |
xRmonLogLastDateTimeThe local date and time of the system at the time
an RMON log entry was last created.ro DateTime .1.3.6.1.4.1.33.31.1.5 |
xRmonTrapTypeUse this field to specify the type of SNMP trap to
generate when an alarm event occurs.
The value 'standardFormat' formats the trap as a
standard, RMON-compliant rising and falling event
trap.
The value 'iTouchFormat' formats the trap as a
DisplayString containing a human-readable summary
of the event. The text of the string is very
similar to that of the log descriptions.rw Enumeration .1.3.6.1.4.1.33.31.1.6 |
xRmonRepeaterManagementThis field enables and disables RMON monitoring of
certain repeater related variables in the chassis.
Set this field to 'enabled' to allow this slot to
activate alarms and report traps for variables from
the standard repeater MIB (snmpDot3RptrMgt
1.3.6.1.2.1.22) and the iTouch repeater MIB
(xRepeater 1.3.6.1.4.1.33.17).
When you set this field to 'disabled', alarms may
still be created for these repeater variables, but
no monitoring will take place for them. The alarm
state will be 'held' during this time.
Only one slot in a chassis may have this field set
to 'enabled' at any given time. Setting 'enabled'
in any one slot automatically sets it to 'disabled'
in every other slot. Repeater variable monitoring
in those slots will cease and the corresponding
alarm states will be 'held'.rw Enumeration .1.3.6.1.4.1.33.31.1.7 |
xRmonAlarmActivateUse this field to change the states of all completed
alarms to 'active' or 'inactive'.
Select 'activateAll' to make all completed alarms
not in the 'active' state become 'active' again.
This is useful for alarms whose error states are not
automatically cleared by the system. Alarms whose
error conditions have not cleared will remain in
their current states.
Select 'deactivateAll' to make all completed alarms
that are in the 'active' state become 'inactive'.
This is a convenient way to suppress alarm activity
while making other configuration changes without
actually deleting the alarms.
Alarms which are incomplete (e.g., 'creating' state)
are not affected by these actions.
If you want to alter the state of a single alarm,
modify the table entry for that alarm.
Selecting noAction has no effect.rw Enumeration .1.3.6.1.4.1.33.31.1.8 |
xRmonAlarmClearSet this field to 'deleteAll' to delete all alarm
table entries and their associated event entries.
Setting to 'noAction' has no effect.rw Enumeration .1.3.6.1.4.1.33.31.1.9 |
xRmonAlarmCount OBJECT IDENTIFIER .1.3.6.1.4.1.33.31.1.10 |
xRmonAlarmsIncompleteThis value represents the number of alarms that are
not completed. Completing these alarms will make
them active.ro INTEGER .1.3.6.1.4.1.33.31.1.10.1 |
xRmonAlarmsActiveThis value represents the number of alarms whose
state is 'active'. These are completed alarms
which are actively monitored.ro INTEGER .1.3.6.1.4.1.33.31.1.10.2 |
xRmonAlarmsHeldThis value represents the number of alarms whose
state is 'held'. These are completed alarms
which will not be actively monitored because the
Repeater Management feature for this processor is
currently disabled. Enabling the feature will
activate all alarms in this state.ro INTEGER .1.3.6.1.4.1.33.31.1.10.3 |
xRmonAlarmsOtherThis value represents the number of completed alarms
that are not 'active' and not 'held'. Monitoring is
not active for these alarms.ro INTEGER .1.3.6.1.4.1.33.31.1.10.4 |
xRmonAlarmInitActionUse this field to specify whether all alarms read
from the parameter file should be placed in the
'active' state or the 'inactive' state upon system
initialization.
Selecting 'activateUponInit' (the default) will
activate all alarms read from the parameter file
when the system initializes.
Selecting 'inactiveUponInit' will place all alarms
in the 'inactive' state when the system initializes.
Modifying this value does not affect the present
state of any alarm.rw Enumeration .1.3.6.1.4.1.33.31.1.11 |
xRmonMB OBJECT IDENTIFIER .1.3.6.1.4.1.33.31.2 |
xRmonMBConfig OBJECT IDENTIFIER .1.3.6.1.4.1.33.31.2.1 |
mbAlarmIndexThis 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.
Specify the index of an existing alarm to fill the
remaining fields with the corresponding settings
from that alarm. To modify the settings of a
completed alarm, set its status to underCreation.
Specify an index which does not exist to create a
new alarm. The initial settings of the remaining
fields are taken from the alarm you were previously
viewing, if any. This makes it easier to 'copy' an
alarm definition when you want to change only a few
of the settings, such as the alarm variable or keys.
Specify a value of 0 to clear the remaining fields.rw INTEGER .1.3.6.1.4.1.33.31.2.1.1 |
mbAlarmIntervalThe interval in seconds over which the variable is
sampled and compared with the rising and falling
thresholds. If the monitored variable exceeds the
limit 2^31-1 (4294967295), the alarm value field may
roll over to 0 and cause or suppress the generation
of an alarm event during that interval.
You may not modify this field once the alarm is
completed (see alarm status field).rw INTEGER .1.3.6.1.4.1.33.31.2.1.2 |
mbAlarmVariableThis value shows the SNMP object identifier of the
variable being sampled. Only variables that have an
SNMP 'SYNTAX' of INTEGER, Counter, Gauge, or
TimeTicks may be sampled.
When you specify an object identifier in this field,
the quick list, key prompt, and key value fields are
filled for you with the appropriate values. If you
specify an object not found in the quick list, that
field is set to 'unlistedAlarmVariable'. The key
values will be set to zero in this case.
If you specify an alarm variable and keys using the
quick list and key fields, an SNMP object identifier
is built for you and placed in this field.
You may not modify this field at the same time that
you modify the quick list field or either of the
key values.
You may not modify this field once the alarm is
completed (see alarm status field).rw OBJECT IDENTIFIER .1.3.6.1.4.1.33.31.2.1.3 |
mbAlarmInterpretationUse this field when you want to select an alarm
variable without specifying its entire SNMP object
identifier. First, modify this field by selecting
a variable from the list. Then, read the key prompt
fields. They will direct you to specify key values
appropriate to the selected variable. The SNMP
object identifier will be built for you when you
are done.
You may not modify this field at the same time that
you modify the object identifier field.
You may not modify this field once the alarm is
completed (see alarm status field).rw Enumeration .1.3.6.1.4.1.33.31.2.1.4 |
mbAlarmKey1MeaningThis field describes how its adjacent key value
field will be interpreted when building a complete
SNMP object identifier for the alarm variable. The
value of this field changes as you select different
items from the quick list or specify different SNMP
object identifiers.
This object has the value 'not applicable' if its key
value is not necessary or the object is unknown.ro DisplayString .1.3.6.1.4.1.33.31.2.1.5 |
mbAlarmKey1Specify a value here according the the instructions
given in its adjacent prompt field. That prompt
explains how this field will be used.
You may still modify this field even though the
prompt field indicates that it is not applicable to
the selected variable. It will be ignored.
You may not modify this field at the same time that
you modify the object identifier field.
You may not modify this field once the alarm is
completed (see alarm status field).rw INTEGER .1.3.6.1.4.1.33.31.2.1.6 |
mbAlarmKey2MeaningThis field describes how its adjacent key value
field will be interpreted when building a complete
SNMP object identifier for the alarm variable. The
value of this field changes as you select different
items from the quick list or specify different SNMP
object identifiers.
This object has the value 'not applicable' if its key
value is not necessary or the object is unknown.ro DisplayString .1.3.6.1.4.1.33.31.2.1.7 |
mbAlarmKey2Specify a value here according the the instructions
given in its adjacent prompt field. That prompt
explains how this field will be used.
In some cases, the value zero has a special meaning.
This often occurs when you are prompted to enter a
port number. Zero indicates you want each port in
the indicated slot to be monitored by this alarm.
Only one alarm will exist, but it will generate an
event each time any of the ports meets its criteria.
You may still modify this field even though the
prompt field indicates that it is not applicable to
the selected variable. It will be ignored.
You may not modify this field at the same time that
you modify the object identifier field.
You may not modify this field once the alarm is
completed (see alarm status field).rw INTEGER .1.3.6.1.4.1.33.31.2.1.8 |
mbAlarmSampleTypeUse this field to select the method of calculating
the value to be compared against the thresholds.
When you set this to 'absoluteValue', the variable
you specified is compared directly with the alarm
thresholds at the end of each monitoring interval.
When you set this to 'changeInValue', the change in
the value of the variable over the interval is
compared with the thresholds. This is useful for
detecting changes in rates of activity.
You may not modify this field once the alarm is
completed (see alarm status field).rw Enumeration .1.3.6.1.4.1.33.31.2.1.9 |
mbAlarmValueThis field shows the value of the alarm variable at
the end of the most recent monitoring interval. If
the alarm sample type is 'changeInValue', it instead
shows the change in value over that interval.
This field is zero any time the alarm is not active,
or when the alarm is a wildcard (that is, a port or
repeater number of 0 was specified for key 2 value).
The value of this field has meaning after the alarm
configuration is complete and monitoring begins.ro INTEGER .1.3.6.1.4.1.33.31.2.1.10 |
mbAlarmRisingThresholdThis is the rising threshold value for the alarm.
When the current alarm value, specified by the alarm
sample type, is greater than or equal to this
threshold, and the value at the previous sampling
interval was less than this threshold, a single
rising alarm event will be generated.
Another rising alarm event will not be generated
until the sampled value falls below the falling
threshold value.
You may not modify this field once the alarm is
completed (see alarm status field).rw INTEGER .1.3.6.1.4.1.33.31.2.1.11 |
mbAlarmFallingThresholdThis is the falling threshold value for the alarm.
When the current alarm value, specified by the alarm
sample type, is less than or equal to this
threshold, and the value at the previous sampling
interval was greater than this threshold, a single
rising alarm event will be generated.
Another rising alarm event will not be generated
until the sampled value falls below the falling
threshold value.
You may not modify this field once the alarm is
completed (see alarm status field).rw INTEGER .1.3.6.1.4.1.33.31.2.1.12 |
mbAlarmRisingEventTypeUse this field to indicate the type of notification
to make when the alarm variable exceeds its rising
threshold. The default action is to generate both
a log entry and a trap.
Set this field to noAction to suppress notification
of rising threshold events.
Set this field to logOnly to generate an RMON alarm
log entry. These log entries may be viewed through
the RMON alarm log view.
Set this field to trapOnly to generate an SNMP trap.
Refer to the RMON alarm summary to specify whether
traps are generated in standard RMON format or in
iTouch format.
Choosing logAndTrap invokes both these actions.
You may not modify this field once the alarm is
completed (see alarm status field).rw Enumeration .1.3.6.1.4.1.33.31.2.1.13 |
mbAlarmFallingEventTypeUse this field to indicate the type of notification
to make when the alarm variable exceeds its falling
threshold. The default action is to generate both
a log entry and a trap.
Set this field to noAction to suppress notification
of falling threshold events.
Set this field to logOnly to generate an RMON alarm
log entry. These log entries may be viewed through
the RMON alarm log view.
Set this field to trapOnly to generate an SNMP trap.
Refer to the RMON alarm summary to specify whether
traps are generated in standard RMON format or in
iTouch format.
Choosing logAndTrap invokes both these actions.
You may not modify this field once the alarm is
completed (see alarm status field).rw Enumeration .1.3.6.1.4.1.33.31.2.1.14 |
mbAlarmSummaryAs you make changes to the to alarm settings, this
field is filled with an easily readable summary of
the alarm parameters. This is to make it easy for
you to confirm that monitoring will behave as you
expected once the alarm status is 'active'.ro DisplayString .1.3.6.1.4.1.33.31.2.1.15 |
mbAlarmStatusDescribes 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.rw Enumeration .1.3.6.1.4.1.33.31.2.1.16 |
mbAlarmTableA list of RMON alarms. This table is indexed by
alarmIndex to provide an intuitive mapping between
alarms and descriptions. SEQUENCE OF MbAlarmEntry .1.3.6.1.4.1.33.31.2.2 |
mbAlarmEntryA description of an RMON alarm which summarizes the
actual RMON alarm and event parameters corresponding
to this entry. MbAlarmEntry .1.3.6.1.4.1.33.31.2.2.1 |
mbAlarmConditionDescribes 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. Allocate more packet buffers
or increase free 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.rw Enumeration .1.3.6.1.4.1.33.31.2.2.1.1 |
mbAlarmDescriptionAn easily-readable summary of an RMON alarm.
The general format is: '<action> when <condition>
<variable> <key2tag> <key1tag> is >= <r> or <= <f>
<interval>.'
<action> is from: 'Do nothing', 'Create log record',
'Generate trap', 'Create log and trap', or 'Various
actions', based on the alarm rising and falling
event types.
<condition> is one of 'value of' or 'change in',
according to the alarm sample type.
<variable>, if recognized, describes the quick list
selection. If unlisted, the object identifier is
substituted.
<key1tag> and <key2tag> appear only if <variable> is
recognized and represent phrases like 'slot',
'port', and 'any port'.
<r> and <f> represent the rising and falling
threshold values, respectively.
The <interval> phrase describes the units per N
seconds or the length of the sample interval in
seconds.ro DisplayString .1.3.6.1.4.1.33.31.2.2.1.2 |
mbLogTableA list of RMON logTable entries. SEQUENCE OF MbLogEntry .1.3.6.1.4.1.33.31.2.3 |
mbLogEntryA human-readable description of an RMON event. MbLogEntry .1.3.6.1.4.1.33.31.2.3.1 |
mbLogIndexAn index uniquely identifying an entry in this log
table. Each such entry describes, in human-readable
format, an RMON event occurring for an alarm. All
RMON log table entries are shown, ordered most
recent first.ro INTEGER .1.3.6.1.4.1.33.31.2.3.1.1 |
mbLogDescriptionAn easily-readable summary of an RMON log entry.
The general format is: '<time>: alarm <index>
<condition> <variable> <key2tag> <key1tag> is
<limit> <interval>.'
<time> is the date and time the entry was created.
<index> is the alarm index causing the report.
<condition> is one of 'value of <V> for' or 'change
of <V> for', according to the alarm sample type.
<V> is the actual value triggering the report.
<variable>, if recognized, describes the quick list
selection. If unlisted, the object identifier is
substituted.
<key1tag> and <key2tag> appear only if <variable> is
recognized and represent phrases like 'slot',
'port', and 'any port'.
<limit> is one of '>= <r>' or '<= <f>' where <r> and
<f> represent the rising and falling threshold
values, respectively.
The <interval> phrase describes the units per N
seconds or the length of the sample interval in
seconds.ro DisplayString .1.3.6.1.4.1.33.31.2.3.1.2 |
mbResourceTableA list of RMON resource entries. SEQUENCE OF MbResourceEntry .1.3.6.1.4.1.33.31.2.4 |
mbResourceEntryValues to control and monitor RMON resources. MbResourceEntry .1.3.6.1.4.1.33.31.2.4.1 |
mbResourceTypeIdentification of an RMON resource type. Typically
each type corresponds to an RMON table whose size is
to be controlled and monitored.ro Enumeration .1.3.6.1.4.1.33.31.2.4.1.1 |
mbResourceCurrentThe number of entries currently allocated by RMON.ro Gauge .1.3.6.1.4.1.33.31.2.4.1.2 |
mbResourceWorstThe highest number of entries ever allocated by
RMON since system initialization.ro Gauge .1.3.6.1.4.1.33.31.2.4.1.3 |
mbResourceMaximumThe desired maximum possible number of resources of
this type RMON is permitted to use at any one time.
Changes to alarm, event, and log entry resource
settings take effect immediately.
Changes to the statistics resource takes place after
the system is initialized.
For alarms and events, this value may not be set
less than the current number of entries in use.rw INTEGER .1.3.6.1.4.1.33.31.2.4.1.4 |
mbResourceOperMaximumThe actual maximum number of resources of this type
RMON will attempt to use at any one time. This is
the limit in effect for the current system.ro INTEGER .1.3.6.1.4.1.33.31.2.4.1.5 |
xRmonMapTableA list of RMON map entries. SEQUENCE OF XRmonMapEntry .1.3.6.1.4.1.33.31.3 |
xRmonMapEntryValues to create RMON statistics tables for
repeater ports. XRmonMapEntry .1.3.6.1.4.1.33.31.3.1 |
xRmonMapSlotThe slot the statistics will come from.rw INTEGER .1.3.6.1.4.1.33.31.3.1.1 |
xRmonMapPortThe port the statistics will come from.rw INTEGER .1.3.6.1.4.1.33.31.3.1.2 |
xRmonMapIfIndexThe interface index (ifIndex) corresponding to
this statistics table.ro INTEGER .1.3.6.1.4.1.33.31.3.1.3 |