- Table of Contents
-
- H3C S9500 Command Manual-Release2132[V2.03]-08 System Volume
- 00-1Cover
- 01-GR Commands
- 02-VRRP Commands
- 03-HA Commands
- 04-Device Management Commands
- 05-NQA Commands
- 06-NetStream Commands
- 07-NTP Commands
- 08-RMON Commands
- 09-SNMP Commands
- 10-File System Management Commands
- 11-System Maintaining and Debugging Commands
- 12-Basic System Configuration Commands
- 13-Information Center Commands
- 14-User Interface Commands
- 15-MAC Address Table Management Commands
- 16-PoE Commands
- 17-Clock Monitoring Commands
- Related Documents
-
Title | Size | Download |
---|---|---|
08-RMON Commands | 79.51 KB |
Chapter 1 RMON Configuration Commands
1.1 RMON Configuration Commands
1.1.1 debugging rmon
Syntax
debugging rmon
undo debugging rmon
View
User view
Default Level
1: Monitor level
Parameters
None
Description
Use the debugging rmon command to enable RMON debugging.
Use the undo debugging rmon command to disable RMON debugging.
By default, RMON debugging is disabled.
Table 1-1 debugging rmon command output description
Field |
Description |
GETVALUEINFO |
Debugging information about the Get operation |
PARAERR |
Debugging information about the parameter errors |
MEMOERR |
Debugging information about the memory distribution failure |
CMOERR |
Debugging information about the invalid CMO |
CMSGERR |
Debugging information about the invalid messages |
CMDCBREGFAIL |
Debugging information about the command line registration errors |
APPMSGFAIL |
Debugging information about the adding message failures |
TIMERINFO |
Debugging information about the timer errors |
TABLEINFO |
Debugging information about the table operation failures |
GLOBALERRINFO |
Global debugging information |
BUILDINFO |
BuildRun debugging information |
INLEGALENTEY |
Debugging information about the illegal instances |
RPCTIMEOUT |
Debugging information about the RPC scheduling failures |
GETINVALIDIFINDEX |
Debugging information about the invalid interface indexes |
DEBUGINFO |
Other debugging information |
RMON_Alarm_Counter: ulSampleCount is number |
Alarm group sample counts |
RMON for hot gets invalid ifIndex. ifIndex= number |
RMON gets invalid ifIndex of the card inserted. |
Examples
# Enable debugging for the information center and RMON. Configure a valid event group and a valid alarm group, and the system will output debugging information to the terminal about the alarm group sample counts.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging rmon
<Sysname> system-view
[Sysname] rmon event 1 log owner test
[Sysname] rmon alarm 1 1.3.6.1.2.1.6.3.0 5 absolute rising-threshold 100 1 falling-threshold 20 1
[Sysname]
*Oct 16 13:56:30:20 2006 Sysname RMON/7/GETVALUEINFO:RMON_Alarm_Counter: ulSampleCount is 1
// Sampling count for the current alarm group is once.
# Enable debugging for the information center and RMON. The current system already has 100 history groups. If you continue to configure history groups, the system will output debugging information to the terminal that the history control table is full.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging rmon
<Sysname> system-view
[Sysname] interface ethennet 3/1/2
[Sysname-Ethennet3/1/2] rmon history 101 buckets 10 interval 10
There are too many table entries. No more can be added.
*Oct 16 14:16:41:50 2006 Sysname RMON/7/TABLEINFO:HistoryControl table is full.
[Sysname-Ethennet3/1/2]
// Currently, the history control table is full.
# Enable debugging for the information center and RMON. Configure a private alarm group using a nonexistent MIB variable, and system will output debugging information to the terminal that the private alarm group configuration failed.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging rmon
<Sysname>system-view
[Sysname] rmon prialarm 1 100/(1.3.6.1.2.1.4.2.0-255) test 10 absolute rising-threshold 10 1 falling-threshold 20 1 entrytype forever
Failure! Wrong private alarm variable formula.
*Oct 16 14:18:51:40 2006 SYSNAME RMON/7/INLEGALENTEY:Private alarm table's variable formula error!
// Error in the private alarm variable formula.
# Enable debugging for the information center and RMON. Configure a private alarm group whose rising threshold is smaller than the falling threshold, and the system will output debugging information to the terminal that the private alarm group configuration failed.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging rmon
<Sysname> system-view
[Sysname] rmon prialarm 1 100/50 test 10 absolute rising-threshold 10 1 falling-threshold 200 1 entrytype forever
Failure! Set operation parameter error.
*Oct 16 14:26:07:47 2006 SYSNAME RMON/7/INLEGALENTEY:Rising threshold little than falling threshold!
// The rising threshold of the private alarm group is smaller than the falling threshold of the group.
1.1.2 display rmon alarm
Syntax
display rmon alarm [ entry-number ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Index of an RMON alarm entry, in the range 1 to 65535. If no entry is specified, the configuration of all alarm entries is displayed.
Description
Use the display rmon alarm command to display the configuration of the specified or all RMON alarm entries.
Related commands: rmon alarm.
Examples
# Display the configuration of all RMON alarm table entries.
Alarm table 1 owned by user1 is VALID.
Samples type : absolute
Variable formula : 1.3.6.1.2.1.16.1.1.1.4.1 <etherStatsOctets.1>
Sampling interval : 10(sec)
Rising threshold : 50(linked with event 1)
Falling threshold : 5(linked with event 2)
When startup enables : risingOrFallingAlarm
Latest value : 0
Table 1-2 display rmon alarm command output description
Field |
Description |
Alarm table |
Alarm entry index, 1 in this example |
owned by |
Owner of the entry, user1 in this example |
VALID |
Status of the entry identified by the index (VALID means the entry is valid, and UNDERCREATION means invalid. You can use the display rmon command to view the invalid entry, while you cannot view the corresponding rmon commands with the display current-configuration and display this commands.) |
Samples type |
The sampling type (absolute in this example) |
Variable formula |
Formula for the sampling value |
Sampling interval |
Sampling interval |
Rising threshold |
Alarm rising threshold (When the sampling value is bigger than or equal to this threshold, a rising alarm is triggered.) |
Falling threshold |
Alarm falling threshold (When the sampling value is smaller than or equal to this threshold, a falling alarm is triggered.) |
When startup enables |
How can an alarm be triggered |
Latest value |
The last sampled value |
1.1.3 display rmon event
Syntax
display rmon event [ entry-number ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Index of an RMON event entry, in the range 1 to 65535.
Description
Use the display rmon event command to display the configuration of the specified or all RMON event entries.
Displayed information includes event index, event owner, event description, action triggered by the event (such as sending log or trap messages), and last time the event occurred (the elapsed time since system initialization/startup) in seconds.
If no entry is specified, the configuration of all event entries is displayed.
Related commands: rmon event.
Examples
# Display the configuration of RMON event table.
<Sysname> display rmon event
Event table 1 owned by user1 is VALID.
Description: null.
Will cause log-trap when triggered, last triggered at 0days 00h:02m:27s.
Table 1-3 display rmon event command output description
Field |
Description |
Event table |
Event entry number |
owned by |
Owner of the entry |
VALID |
Status of the entry identified by the index (VALID means the entry is valid, and UNDERCREATION means invalid. You can use the display rmon command to view the invalid entry, while you cannot view the corresponding rmon commands with the display current-configuration and display this commands.) |
Description |
Description for the event |
cause log-trap when triggered |
The event will trigger logging and trapping. |
last triggered at |
Last time the event was triggered |
1.1.4 display rmon eventlog
Syntax
display rmon eventlog [ entry-number ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Index of an event entry, in the range 1 to 65535.
Description
Use the display rmon eventlog command to display log information for the specified or all event entries.
If you use the rmon event command to specify that the action of an entry includes logging, then when this event is triggered, the event log is retained in the RMON log list. You can use the display rmon eventlog command to display detailed log information including event index, current event state, time the event was logged (the elapsed time in seconds since system initialization/startup), and event description.
If no entry number is specified, the log information for all event entries is displayed.
Examples
# Display the RMON log information for event entry 1.
<Sysname> display rmon eventlog 1
Event table 1 owned by user1 is VALID.
Generates eventLog 1.1 at 0days 00h:01m:39s.
Description: The 1.3.6.1.2.1.16.1.1.1.4.1 defined in alarm table 1,
less than(or =) 100 with alarm value 0. Alarm sample type is absolute.
Generates eventLog 1.2 at 0days 00h:02m:27s.
Description: The alarm formula defined in private alarm table 1,
less than(or =) 100 with alarm value 0. Alarm sample type is absolute.
Table 1-4 display rmon eventlog command output description
Field |
Description |
Event table |
Event index |
owned by |
Owner of the entry |
VALID |
Status of the entry identified by the index (VALID means the entry is valid, and UNDERCREATION means invalid. You can use the display rmon command to view the invalid entry, while you cannot view the corresponding rmon commands with the display current-configuration and display this commands.) |
Generates eventLog at |
Time the log was created |
Description |
Log description |
1.1.5 display rmon history
Syntax
display rmon history [ interface-type interface-number ]
View
Any view
Default Level
1: Monitor level
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Description
Use the display rmon history command to display RMON history control entry and last history sampling information, including bandwidth utilization, number of bad packets, and total packet number.
Related commands: rmon history.
Examples
# Display RMON history control entries and history sample information for interface Ethernet 2/1/1.
<Sysname> display rmon history ethernet 2/1/1
History control entry 1 owned by user1 is VALID
Samples interface : Ethernet2/1/1<ifEntry.642>
Sampling interval : 10(sec) with 10 buckets max
Latest sampled values :
Dropevents :0 , octets :0
packets :0 , broadcast packets :0
multicast packets :0 , CRC alignment errors :0
undersize packets :0 , oversize packets :0
fragments :0 , jabbers :0
collisions :0 , utilization :0
Table 1-5 display rmon history command output description
Field |
Description |
History control entry |
Index of the history control entry for the interface, 1 in this example |
owned by |
Owner of the entry |
VALID |
Status of the entry identified by the index (VALID means the entry is valid, and UNDERCREATION means invalid. You can use the display rmon command to view the invalid entry, while you cannot view the corresponding rmon commands with the display current-configuration and display this commands.) |
Samples Interface |
The sampled interface |
Sampling interval |
Sampling interval |
buckets max |
Maximum number of records that can be stored in the history control table. |
Latest sampled values |
The latest sampled values |
Dropevents |
Dropped packets during the sampling period |
octets |
Number of octets received during the sampling period |
packets |
Number of packets received during the sampling period |
broadcastpackets |
Number of broadcasts received during the sampling period |
multicastpackets |
Number of multicasts received during the sampling period |
CRC alignment errors |
Number of packets received with CRC alignment errors during the sampling period |
undersize packets |
Number of undersize packets received during the sampling period |
oversize packets |
Number of oversize packets received during the sampling period |
fragments |
Number of fragments received during the sampling period |
jabbers |
Number of jabbers received during the sampling period |
collisions |
Number of colliding packets received during the sampling period |
utilization |
Bandwidth utilization during the sampling period |
& Note:
Currently, the S9500 series switches do not support statistics on jabbers.
1.1.6 display rmon prialarm
Syntax
display rmon prialarm [ entry-number ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Private alarm entry index, in the range 1 to 65535. If no entry is specified, the configuration of all private alarm entries is displayed.
Description
Use the display rmon prialarm command to display the configuration of the specified or all private alarm entries.
Related commands: rmon prialarm.
Examples
# Display the configuration of all private alarm entries.
<Sysname> display rmon prialarm
Prialarm table 5 owned by user1 is UNDERCREATION.
Samples type : changeratio
Variable formula : ((.1.3.6.1.2.1.16.1.1.1.5.1-.1.3.6.1.2.1.16.1.1.1.6.1)*100/.1.3.6.1.2.1.16.1.1.1.5.1)
Description : ifUtilization.GigabitEthernet2/1/1
Sampling interval : 10(sec)
Rising threshold : 892340484(linked with event 1)
Falling threshold : 889783312(linked with event 2)
When startup enables : risingOrFallingAlarm
This entry will exist : forever
Latest value : 0
Table 1-6 display rmon prialarm command output description
Field |
Description |
Prialarm table |
Index of the prialarm table |
owned by |
Owner of the entry, user1 in this example |
VALID |
Status of the entry identified by the index (VALID means the entry is valid, and UNDERCREATION means invalid. You can use the display rmon command to view the invalid entry, while you cannot view the corresponding rmon commands with the display current-configuration and display this commands.) |
Samples type |
Samples type |
Variable formula |
Variable formula |
Sampling interval |
Sampling interval |
Rising threshold |
Alarm rising threshold. An alarm event is triggered when the sampled value is greater than or equal to this threshold. |
Falling threshold |
Alarm falling threshold. An alarm event is triggered when the sampled value is less than or equal to this threshold. |
linked with event |
Event index associated with the prialarm |
When startup enables |
How can an alarm be triggered |
This entry will exist |
The lifetime of the entry, which can be forever or span the specified period |
Latest value |
The last sampled value |
1.1.7 display rmon statistics
Syntax
display rmon statistics [ interface-type interface-number ]
View
Any view
Default Level
1: Monitor level
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Description
Use the display rmon statistics command to display RMON statistics.
The displayed statistics include statistics about network collisions, CRC alignment errors, undersize/oversize packets, broadcasts, multicasts, bytes received, packets received, and so on.
Related commands: rmon statistics.
& Note:
Currently, the S9500 series switches do not support statistics about oversize frames and bytes received.
Examples
# Display RMON statistics for interface GigabitEthernet 4/2/2.
<Sysname> display rmon statistics GigabitEthernet 4/2/2
Statistics entry 1 owned by user1-rmon is VALID.
Interface : GigabitEthernet4/2/2<ifIndex.157>
etherStatsOctets : 0 , etherStatsPkts : 0
etherStatsBroadcastPkts : 0 , etherStatsMulticastPkts : 0
etherStatsUndersizePkts : 0 , etherStatsOversizePkts : 0
etherStatsFragments : 0 , etherStatsJabbers : 0
etherStatsCRCAlignErrors : 0 , etherStatsCollisions : 0
etherStatsDropEvents (insufficient resources): 0
Packets received according to length:
64 : 0 , 65-127 : 0 , 128-255 : 0
256-511: 0 , 512-1023: 0 , 1024-1518: 0
Table 1-7 display rmon statistics command output description
Field |
Description |
Statistics entry |
Statistics table entry index |
VALID |
Status of the entry identified by the index (VALID means the entry is valid, and UNDERCREATION means invalid. You can use the display rmon command to view the invalid entry, while you cannot view the corresponding rmon commands with the display current-configuration and display this commands.) |
Interface |
Interface on which statistics are gathered |
etherStatsOctets |
Number of octets received by the interface during the statistical period |
etherStatsPkts |
Number of packets received by the interface during the statistical period |
etherStatsBroadcastPkts |
Number of broadcast packets received by the interface during the statistical period |
etherStatsMulticastPkts |
Number of multicast packets received by the interface during the statistical period |
etherStatsUndersizePkts |
Number of undersize packets received by the interface during the statistical period |
etherStatsOversizePkts |
Number of oversize packets received by the interface during the statistical period |
etherStatsFragments |
Number of undersize packets with CRC errors received by the interface during the statistical period |
etherStatsJabbers |
Number of oversize packets with CRC errors received by the interface during the statistical period |
etherStatsCRCAlignErrors |
Number of packets with CRC errors received on the interface during the statistical period |
etherStatsCollisions |
Number of collisions received on the interface during the statistical period |
etherStatsDropEvents |
Total number of drop events received on the interface during the statistical period |
Packets received according to length: |
Statistics of packets received according to length during the statistical period |
& Note:
Currently, the S9500 series switches do not support statistics on etherStatsJabbers.
1.1.8 rmon alarm
Syntax
rmon alarm entry-number alarm-variable sampling-interval { absolute | delta } rising-threshold threshold-value1 event-entry1 falling-threshold threshold-value2 event-entry2 [ owner text ]
undo rmon alarm entry-number
View
System view
Default Level
2: System level
Parameters
entry-number: Alarm entry index, in the range 1 to 65535.
alarm-variable: Alarm variable, a string of 1 to 256 characters, in dotted object identifier (OID) format, such as 1.3.6.1.2.1.2.1.10.1 (or ifInOctets.1). Only variables that can be parsed into INTEGER (INTEGER, Counter, Gauge, or Time Ticks) in the ASN.1 can be used for the alarm-variable argument.
sampling-interval: Sampling interval, in the range 5 to 65535 seconds.
absolute: Sets the sampling type to absolute.
delta: Sets the sampling type to delta.
threshold-value1: Rising threshold, in the range –2147483648 to +2147483647.
event-entry1: Index of the event triggered when the rising threshold is reached. It ranges from 0 to 65535.
threshold-value2: Falling threshold, in the range –2147483648 to +2147483647.
event-entry2: Index of the event triggered when the falling threshold is reached. It ranges from 1 to 65535.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon alarm command to create an entry in the RMON alarm table.
Use the undo rmon alarm command to remove a specified entry from the RMON alarm table.
This command defines alarms. The generation and notification of an alarm however, is controlled by the event entry associated with it.
The following is how the system handles alarm entries:
1) Samples the alarm variables at the specified interval.
2) Compares the sampled values with the predefined threshold and does the following:
l If the rising threshold is reached, triggers the event specified by the event-entry1 argument.
l If the falling threshold is reached, triggers the event specified by the event-entry2 argument.
& Note:
l Before creating an alarm entry, define the events to be referenced in the event table with the rmon event command.
l Rising threshold alarm and falling threshold alarm are alternate. That is, if a rising/falling threshold alarm occurs, next alarm must be a falling/rising threshold alarm.
l When you create an entry, if the values of the specified alarm variable (alarm-variable), sampling interval (sampling-interval), sampling type (absolute or delta), rising threshold (threshold-value1) and falling threshold (threshold-value2) are identical to those of the existing alarm entry, the system considers their configurations the same and the creation fails.
l You can create up to 60 alarm entries.
Examples
# Add entry 1 in the alarm table and sample the node 1.3.6.1.2.1.16.1.1.1.4.1 at a sampling interval of 10 seconds in absolute sampling type. Generate event 1 when the sampled value is greater than or equal to the rising threshold of 50, and event 2 when the sampled value is lower than or equal to the falling threshold of 5. Set the owner of the entry to user1.
<Sysname> system-view
[Sysname] rmon event 1 log
[Sysname] rmon event 2 none
[Sysname] interface Gigabitethernet 2/1/1
[Sysname-GigabitEthernet2/1/1] rmon statistics 1
[Sysname-GigabitEthernet2/1/1] quit
[Sysname] rmon alarm 1 1.3.6.1.2.1.16.1.1.1.4.1 10 absolute rising_threshold 50 1 falling_threshold 5 2 owner user1
# Remove the alarm table entry with the index of 15.
<Sysname> system-view
[Sysname] undo rmon alarm 15
1.1.9 rmon event
Syntax
rmon event entry-number [ description string ] { log | trap trap-community | log-trap log-trapcommunity | none } [ owner text ]
undo rmon event entry-number
View
System view
Default Level
2: System level
Parameters
entry-number: Event entry index, in the range 1 to 65535.
description string: Event description, a string of 1 to 127 characters.
log: Logs the event when it occurs.
trap: Sends a trap when the event occurs.
trap-community: Network management station community to which traps are sent, a string of 1 to 127 characters.
log-trap: Performs both logging and trap sending when the event occurs.
log-trapcommunity: Community name of the network management station that receives trap messages, a string of 1 to 127 characters.
none: Performs no action when the event occurs.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon event command to create an entry in the RMON event table.
Use the undo rmon event command to remove the specified entry from the RMON event table.
When an event is triggered by its associated alarm in the alarm table, the event group allows you to log it, send a trap, do both, or do neither at all. This helps control the generation and notification of events.
& Note:
l When you create an entry, if the values of the specified event description (description string), event type (log, trap, logtrap or none), and community name (trap-community or log-trapcommunity) are identical to those of the existing event entry, the system considers their configurations the same and the creation fails.
l You can create up to 60 alarm entries.
Examples
# Create event 10 in the RMON event table.
<Sysname> system-view
[Sysname] rmon event 10 log owner user1
1.1.10 rmon history
Syntax
rmon history entry-number buckets number interval sampling-interval [ owner text ]
undo rmon history entry-number
View
Ethernet interface view
Default Level
2: System level
Parameters
entry-number: History control entry index, in the range 1 to 65535.
buckets number: History table size for the entry, in the range 1 to 65535. An S9500 series switch supports 10 buckets only.
interval sampling-interval: Sampling interval, in the range 5 to 3600 seconds.
owner text-string: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon history command to create an entry in the RMON history control table.
Use the undo rmon history command to remove a specified entry from the RMON history control table.
This command enables RMON to periodically sample and save for an interface data such as bandwidth utilization, errors, and total number of packets for later retrieval.
& Note:
l When you create an entry, if the value of the specified sampling interval (interval sampling-interval) is identical to that of the existing history entry, the system considers their configurations the same and the creation fails.
l You can create up to 100 alarm entries.
Related commands: display rmon history.
Examples
# Create RMON history control entry 1 for interface Ethernet 2/1/1, the index is 1, table size is 10, and sampling interval is 5 seconds.
<Sysname> system-view
[Sysname] interface ethernet 2/1/1
[Sysname-Ethernet2/1/1] rmon history 1 buckets 10 interval 5 owner user1
# Remove history control entry 15.
<Sysname> system-view
[Sysname] interface ethernet 2/1/1
[Sysname-Ethernet2/1/1] undo rmon history 15
1.1.11 rmon prialarm
Syntax
rmon prialarm entry-number prialarm-formula prialarm-des sampling-interval { absolute | changeratio | delta } rising_threshold threshold-value1 event-entry1 falling_threshold threshold-value2 event-entry2 entrytype { forever | cycle cycle-period } [ owner text ]
undo rmon prialarm entry-number
View
System view
Default Level
2: System level
Parameters
entry-number: Index of a private alarm entry, in the range 1 to 65535.
prialarm-formula: Private alarm variable formula, a string of 1 to 256 characters. The variables in the formula must be represented in OID format that starts with a point “.”, the formula (.1.3.6.1.2.1.2.1.10.1)*8 for example. You may perform the basic operations of addition, subtraction, multiplication, and division on these variables. The operations should yield a long integer. To prevent errors, make sure that the result of each calculating step falls into the value range for long integers.
prialarm-des: Private alarm entry description, a string of 1 to 127 characters.
sampling-interval: Sampling interval, in the range 10 to 65,535 seconds.
absolute | changeratio | delta : Sets the sampling type to absolute, delta, or change ratio.
threshold-value1: Rising threshold, in the range –2147483648 to +2147483647.
event-entry1: Index of the event triggered when the rising threshold is reached. It ranges from 0 to 65535.
threshold-value2: Falling threshold, in the range –2147483648 to +2147483647.
event-entry2: Index of the event triggered when the falling threshold is reached. It ranges from 0 to 65535.
forever: Indicates that the lifetime of the private alarm entry is infinite.
cycle cycle-period: Sets the lifetime period of the private alarm entry, in the range 0 to 2147483647 seconds.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon prialarm command to create an entry in the private alarm table of RMON.
Use the undo rmon prialarm command to remove a private alarm entry from the private alarm table of RMON.
The following is how the system handles private alarm entries:
1) Samples the private alarm variables in the private alarm formula at the specified sampling interval.
2) Performs calculation on the sampled values with the formula.
3) Compares the calculation result with the predefined thresholds and does the following:
l If the rising threshold is reached, triggers the event specified by the event-entry1 argument.
l If the falling threshold is reached, triggers the event specified by the event-entry2 argument.
& Note:
l Before creating a private alarm entry, define the events to be referenced in the event table with the rmon event command.
l When you create an entry, if the values of the specified alarm variable formula (prialarm-formula), sampling type (absolute changeratio or delta), rising threshold (threshold-value1) and falling threshold (threshold-value2) are identical to those of the existing alarm entry, the system considers their configurations the same and the creation fails.
l You can create up to 50 pri-alarm entries.
l For private alarms, the rising threshold alarm and falling threshold alarm are alternate.
Examples
# Create entry 5 in the private alarm table. Calculate the private alarm variables with the (1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1) formula and sample the corresponding variables at intervals of 10 seconds to get the percentage of broadcasts received on GigabitEthernet 1/1/5 in the total packets. When this ratio reaches or is bigger than the rising threshold of 50, trigger event 1; when this ratio reaches or drops under the falling threshold, trigger event 2. Set the lifetime of the entry to forever and owner to user1.
<Sysname> system-view
[Sysname] rmon event 1 log
[Sysname] rmon event 2 none
[Sysname] interface Gigabitethernet 1/1/5
[Sysname-Gigabitethernet1/1/5] rmon statistics 1
[Sysname-Gigabitethernet1/1/5] quit
[Sysname] rmon prialarm 5 (.1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1) packet.Gigabitethernet1/1/5 10 absolute rising-threshold 50 1 falling-threshold 5 2 entrytype forever owner user1
# Remove private alarm entry 10.
<Sysname> system-view
[Sysname] undo rmon prialarm 10
1.1.12 rmon statistics
Syntax
rmon statistics entry-number [ owner text ]
undo rmon statistics entry-number
View
Ethernet interface view
Default Level
2: System level
Parameters
entry-number: Index of statistics entry, in the range 1 to 65535.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon statistics command to create an entry in the RMON statistics table.
Use the undo rmon statistics command to remove a specified entry from the RMON statistics table.
The RMON statistics group collects information on how a monitored port is being used and records errors. Statistics include number of collisions, CRC alignment errors, number of undersize or oversize packets, number of broadcasts, number of multicasts, number of bytes received, number of packets received.
To display information for the RMON statistics table, use the display rmon statistics command.
& Note:
l Currently, the S9500 series switches do not support statistics on oversize frames and bytes received.
l Only one statistics entry can be created on one interface.
l You can create up to 100 statistics entries.
Examples
# Create an entry in the RMON statistics table for interface Ethernet 2/1/1. The index of the entry is 20.
<Sysname> system-view
[Sysname] interface ethernet 2/1/1
[Sysname-Ethernet2/1/1] rmon statistics 20 owner user1