Table of Contents

1 SNMP Configuration· 1-1

SNMP Overview· 1-1

SNMP Mechanism·· 1-1

SNMP Protocol Version· 1-2

MIB Overview· 1-2

SNMP Configuration· 1-3

Configuring SNMP Logging· 1-5

Introduction to SNMP Logging· 1-5

Enabling SNMP Logging· 1-5

SNMP Trap Configuration· 1-6

Enabling the Trap Function· 1-6

Configuring Trap Parameters· 1-7

Displaying and Maintaining SNMP· 1-8

SNMP Configuration Example (SNMPv2c) 1-8

SNMP Logging Configuration Example· 1-10

2 MIB Style Configuration· 2-1

Setting the MIB Style· 2-1

Displaying and Maintaining MIB· 2-1

3 RMON Configuration· 3-1

RMON Overview· 3-1

Introduction· 3-1

Working Mechanism·· 3-1

RMON Groups· 3-2

Configuring RMON· 3-3

Configuration Prerequisites· 3-3

Configuration Procedure· 3-3

Displaying and Maintaining RMON· 3-5

RMON Configuration Example· 3-5

 

 

When configuring SNMP, go to these sections for information you are interested in:

l          SNMP Overview

l          SNMP Configuration

l          Configuring SNMP Logging

l          SNMP Trap Configuration

l          Displaying and Maintaining SNMP

l          SNMP Configuration Example (SNMPv2c)

l          SNMP Logging Configuration Example

SNMP Overview

Simple Network Management Protocol (SNMP) offers a framework to monitor network devices through TCP/IP protocol suite. It provides a set of basic operations in monitoring and maintaining the Internet and has the following characteristics:

l          Automatic network management: SNMP enables network administrators to search and modify information, find and diagnose network problems, plan for network growth, and generate reports on network nodes.

l          SNMP shields the physical differences between various devices and thus realizes automatic management of products from different manufacturers. Offering only the basic set of functions, SNMP makes the management tasks independent of both the physical features of the managed devices and the underlying networking technology. Thus, SNMP achieves effective management of devices from different manufacturers, especially in small, high-speed and low cost network environments.

SNMP Mechanism

An SNMP enabled network comprises a Network Management Station (NMS) and an agent.

l          An NMS is a station that runs the SNMP client software. It offers a user friendly interface, making it easier for network administrators to perform most network management tasks.

l          An agent is a program on the device. It receives and handles requests sent from the NMS. Only under certain circumstances, such as interface state change, will the agent inform the NMS.

An NMS manages an SNMP enabled network, whereas agents are the managed network device. They exchange management information through the SNMP protocol.

SNMP provides the following four basic operations:

l          Get operation: The NMS gets the value of one or more objects of the agent through this operation.

l          Set operation: The NMS can reconfigure the value of one or more objects in the agent MIB (Management Information Base) by means of this operation.

l          Trap operation: The agent sends traps to the NMS through this operation.

l          Inform operation: The NMS sends traps to other NMSs through this operation.

SNMP Protocol Version

Currently, SNMP agents support SNMPv3 and are compatible with SNMPv1 and SNMPv2c.

l          SNMPv1 uses community name for authentication, which defines the relationship between an SNMP NMS and an SNMP agent. SNMP packets with community names that did not pass the authentication on the device will simply be discarded. A community name performs a similar role as a key word and can be used to regulate access from NMS to agent.

l          SNMPv2c uses community name for authentication. Compatible with SNMPv1, it extends the functions of SNMPv1. SNMPv2c provides more operation modes such as GetBulk and InformRequest; it supports more data types such as Counter64; and it provides various error codes, thus being able to distinguish errors in more detail.

l          SNMPv3 offers an authentication that is implemented with a User-Based Security Model (USM). You can set the authentication and privacy functions. The former is used to authenticate the validity of the sending end of the authentication packets, preventing access of illegal users; the latter is used to encrypt packets between the NMS and agent, preventing the packets from being intercepted. USM ensures a more secure communication between SNMP NMS and SNMP agent by authentication with privacy, authentication without privacy, or no authentication no privacy.

Successful interaction between NMS and agent requires consistency of SNMP versions configured on them. You can configure multiple SNMP versions for an agent to interact with different NMSs.

MIB Overview

Any managed resource can be identified as an object, which is known as the managed object. Management Information Base (MIB) is a collection of all the managed objects. It defines a set of characteristics associated with the managed objects, such as the object identifier (OID), access right and data type of the objects. Each agent has its own MIB. NMS can read or write the managed objects in the MIB. The relationship between an NMS, agent and MIB is shown in Figure 1-1.

Figure 1-1 Relationship between NMS, agent and MIB

 

MIB stores data using a tree structure. The node of the tree is the managed object and can be uniquely identified by a path starting from the root node. As illustrated in the following figure, the managed object B can be uniquely identified by a string of numbers {1.2.1.1}. This string of numbers is the OID of the managed object B.

Figure 1-2 MIB tree

 

SNMP Configuration

As configurations for SNMPv3 differ substantially from those of SNMPv1 and SNMPv2c, their SNMP functionalities is introduced separately below.

Follow these steps to configure SNMPv3:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enable SNMP agent	snmp-agent	Optional Disabled by default You can enable SNMP agent through this command or any commands that begin with snmp-agent.
Configure SNMP agent system information	snmp-agent sys-info { contact sys-contact | location sys-location | version { all | { v1 | v2c | v3 }* } }	Optional The defaults are as follows: Hangzhou H3C Technologies Co., Ltd. for contact, Hangzhou China for location, and SNMP v3 for the version.
Configure an SNMP agent group	snmp-agent group v3 group-name [ authentication | privacy ] [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] [ acl acl-number ]	Required
Convert the user-defined plain text password to a cipher text password	snmp-agent calculate-password plain-password mode { 3desmd5 | 3dessha | md5 | sha } { local-engineid | specified-engineid engineid }	Optional
Add a new user to an SNMP agent group	snmp-agent usm-user v3 user-name group-name [ [ cipher ] authentication-mode { md5 | sha } auth-password [ privacy-mode { 3des | aes128 | des56 } priv-password ] ] [ acl acl-number ]	Required If the cipher keyword is specified, the arguments auth-password and priv-password are considered as cipher text password.
Configure the maximum size of an SNMP packet that can be received or sent by an SNMP agent	snmp-agent packet max-size byte-count	Optional 1,500 bytes by default
Configure the engine ID for a local SNMP agent	snmp-agent local-engineid engineid	Optional Company ID and device ID by default
Create or update the MIB view content for an SNMP agent	snmp-agent mib-view { excluded | included } view-name oid-tree [ mask mask-value ]	Optional MIB view name is ViewDefault and OID is 1 by default.

 

Follow these steps to configure SNMPv1 and SNMPv2c:

To do…			Use the command…	Remarks
Enter system view			system-view	—
Enable SNMP agent			snmp-agent	Optional Disabled by default You can enable SNMP agent through this command or any commands that begin with snmp-agent.
Configure SNMP agent system information			snmp-agent sys-info { contact sys-contact | location sys-location | version { { v1 | v2c | v3 }* | all } }	Required The defaults are as follows: Hangzhou H3C Technologies Co., Ltd. for contact, Hangzhou China for location and SNMP v3 for the version.
Configure SNMP NMS access right	Configure directly	Create an SNMP community	snmp-agent community { read | write } community-name [ acl acl-number | mib-view view-name ]*	Use either approach. Both commands can be used to configure SNMP NMS access rights. The second command was introduced to be compatible with SNMPv3. The community name configured on NMS should be consistent with the username configured on the agent.
	Configure indirectly	Configure an SNMP group	snmp-agent group { v1 | v2c } group-name [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] [ acl acl-number ]
		Add a new user to an SNMP group	snmp-agent usm-user { v1 | v2c } user-name group-name [ acl acl-number ]
Configure the maximum size of an SNMP packet that can be received or sent by an SNMP agent			snmp-agent packet max-size byte-count	Optional 1500 bytes by default
Configure the engine ID for a local SNMP agent			snmp-agent local-engineid engineid	Optional Company ID and device ID by default
Create or update MIB view content for an SNMP agent			snmp-agent mib-view { excluded | included } view-name oid-tree [ mask mask-value ]	Optional ViewDefault by default

 

 

Configuring SNMP Logging

Introduction to SNMP Logging

SNMP logs the GET and SET operations that the NMS performs on the SNMP agent. When the GET operation is performed, the agent logs the IP address of the NMS, node name of the GET operation and OID of the node. When the SET operation is performed, the agent logs the IP address of the NMS, node name of the SET operation, OID of the node, the value set and the error code and error index of the SET response. These logs will be sent to the information center, and the level of them is informational, that is, they are taken as the system prompt information. With parameters for the information center set, the output rules for SNMP logs are decided (that is, whether the logs are permitted to output and the output destinations).

SNMP logs GET request, SET request and SET response, but does not log GET response.

Enabling SNMP Logging

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enable SNMP logging	snmp-agent log { all | get-operation | set-operation }	Required Disabled by default.
Configure SNMP log output rules	info-center source { module-name | default } channel { channel-number | channel-name } [ debug { level severity | state state } * | log { level severity | state state } * | trap { level severity | state state } * ] *	Optional By default, SNMP logs are output to loghost and logfile only. To output SNMP logs to other destinations such as console or monitor terminal, you need to set the output destinations with this command.

 

 

SNMP Trap Configuration

Enabling the Trap Function

The SNMP agent sends traps to the NMS to inform the NMS of critical and important events (such as reboot of a managed device). Two types of traps are available: generic traps and self-defined traps. Generic traps supported on the device include: authentication, coldstart, linkdown, linkup and warmstart. The others are self-defined traps, which are generated by different modules. As traps that occupy large device memory affect device performance, it is recommended not to enable the trap function for all the modules but for the specific modules as needed.

With the trap function enabled on a module, the traps generated by the module will be sent to the information center. The information center has seven information output destinations. By default, traps of all modules are allowed to be output to the console, monitor terminal (monitor), loghost, and logfile; traps of all modules and with level equal to or higher than warnings are allowed to be output to the trapbuffer and SNMP module (snmpagent); and traps cannot be sent to the logbuffer. You can set parameters for the information center based on the levels of the traps generated by each module, and thus decide the output rules of traps (that is, whether traps are allowed to be output and the output destinations). For the configuration of the information center, refer to Information Center Configuration in the System Volume.

Follow these steps to enable the trap function:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enable the trap function globally	snmp-agent trap enable [ configuration | flash | standard [ authentication | coldstart | linkdown | linkup | warmstart ] * | system ]	Optional By default, the trap function is enabled.
Enter interface view	interface interface-type interface-number	—
Enable the trap function of interface state changes	enable snmp trap updown	Optional Enabled by default.

 

 

Configuring Trap Parameters

Configuration prerequisites

To send traps to the NMS, you need to prepare the following:

l          Basic SNMP configurations have been completed. These configurations include version configuration: community name is needed when SNMPv1 and v2c are adopted; username and MIB view are needed if SNMPv3 is adopted.

l          A connection has bee established between the device and the NMS, and they can operate each other.

Configuration procedure

After traps are sent to the SNMP module, the SNMP module saves the traps in the trap queue. You can set the size of the queue and the holding time of the traps in the queue, and you can also send the traps to the specified destination host (usually the NMS).

Follow these steps to configure trap parameters:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Configure target host attribute for traps	snmp-agent target-host trap address udp-domain  ip-address [ udp-port port-number ] params securityname security-string [ v1 | v2c | v3 [ authentication | privacy ] ]	Optional To send the traps to the NMS, this command is required, and you must specify ip-address as the IP address of the NMS.
Configure the source address for traps	snmp-agent trap source interface-type interface-number	Optional
Extend the standard linkUp/linkDown traps defined in RFC	snmp-agent trap if-mib link extended	Optional Standard linkUp/linkDown traps defined in RFC are used by default.
Configure the size of the trap sending queue	snmp-agent trap queue-size size	Optional 100 by default
Configure the holding time of the traps in the queue	snmp-agent trap life seconds	Optional 120 seconds by default

 

 

Displaying and Maintaining SNMP

To do…	Use the command…	Remarks
Display SNMP-agent system information, including the contact, location, and version of the SNMP	display snmp-agent sys-info [ contact | location | version ]*	Available in any view
Display SNMP agent statistics	display snmp-agent statistics
Display the SNMP agent engine ID	display snmp-agent local-engineid
Display SNMP agent group information	display snmp-agent group [ group-name ]
Display basic information of the trap queue	display snmp-agent trap queue
Display the modules that can send traps and whether their trap sending is enabled or not	display snmp-agent trap-list
Display SNMP v3 agent user information	display snmp-agent usm-user [ engineid engineid | username user-name | group group-name ] *
Display SNMP v1 or v2c agent community information	display snmp-agent community [ read | write ]
Display MIB view information for an SNMP agent	display snmp-agent mib-view [ exclude | include | viewname view-name ]

 

SNMP Configuration Example (SNMPv2c)

Network requirements

l          The NMS connects to the agent, a switch, through an Ethernet.

l          The IP address of the NMS is 1.1.1.2/24.

l          The IP address of the VLAN interface on the switch is 1.1.1.1/24.

l          The NMS monitors and manages the agent using SNMPv2c. The agent reports errors or faults to the NMS.

Figure 1-3 Network diagram for SNMP

 

Configuration procedure

1)        Configuring the SNMP agent

# Configure the SNMP basic information, including version and community name.

<Sysname> system-view

[Sysname] snmp-agent sys-info version v2c

[Sysname] snmp-agent community read public

[Sysname] snmp-agent community write private

# Configure VLAN-interface 2 (with the IP address of 1.1.1.1/24). Add the port GigabitEthernet 1/1/1 to VLAN 2.

[Sysname] vlan 2

[Sysname-vlan2] port GigabitEthernet 1/1/1

[Sysname-Vlan2] quit

[Sysname] interface vlan-interface 2

[Sysname-Vlan-interface2] ip address 1.1.1.1 255.255.255.0

[Sysname-Vlan-interface2] quit

# Configure the contact person and physical location information of the switch.

[Sysname] snmp-agent sys-info contact Mr.Wang-Tel:3306

[Sysname] snmp-agent sys-info location telephone-closet,3rd-floor

# Enable the sending of traps to the NMS with an IP address of 1.1.1.2/24, using public as the community name.

[Sysname] snmp-agent trap enable

[Sysname] snmp-agent target-host trap address udp-domain 1.1.1.2 udp-port 5000 params securityname public

2)        Configuring the SNMP NMS

With SNMPv2c, the user needs to specify the read only community, the read and write community, the timeout time, and number of retries. The user can inquire and configure the device through the NMS.

 

 

SNMP Logging Configuration Example

Network requirements

l          The NMS and the agent are connected through an Ethernet

l          The IP address of the NMS is 1.1.1.2/24

l          The IP address of the VLAN interface on the agent is 1.1.1.1/24

l          Configure community name, access right and SNMP version on the agent

Figure 1-4 Network diagram for SNMP logging

 

Configuration procedure

 

 

# Enable logging display on the terminal. (This function is enabled by default, so that you can omit this configuration).

<Sysname> terminal monitor

<Sysname> terminal logging

# Enable the information center to output the system information with the severity level equal to or higher than informational to the console port.

<Sysname> system-view

[Sysname] info-center source snmp channel console log level informational

# Enable SNMP logging on the agent to log the GET and SET operations of the NMS.

[Sysname] snmp-agent log get-operation

[Sysname] snmp-agent log set-operation

l          The following log information is displayed on the terminal when the NMS performs the GET operation to the agent.

%Jan 1 02:49:40:566 2006 Sysname SNMP/6/GET:

seqNO = <10> srcIP = <1.1.1.2> op = <get> node = <sysName(1.3.6.1.2.1.1.5.0)> value=<>

l          The following log information is displayed on the terminal when the NMS performs the SET operation to the agent.

%Jan 1 02:59:42:576 2006 Sysname SNMP/6/SET:

seqNO = <11> srcIP = <1.1.1.2> op = <set> errorIndex = <0> errorStatus =<noError> node = <sysName(1.3.6.1.2.1.1.5.0)> value = <Sysname>

Table 1-1 Description on the output field of SNMP log

Field	Description
Jan 1 02:49:40:566 2006	The time when SNMP log is generated
seqNO	Sequence number of the SNMP log ()
srcIP	IP address of NMS
op	SNMP operation type (GET or SET)
node	Node name of the SNMP operations and OID of the instance
erroIndex	Error index, with 0 meaning no error
errorstatus	Error status, with noError meaning no error
value	Value set when the SET operation is performed (This field is null, meaning the value obtained with the GET operation is not logged.) When the value is a string of characters and the string contains characters not in the range of ASCII 0 to 127 or invisible characters, the string is displayed in hexadecimal. For example, value = <81-43>[hex]

 

H3C private MIB involves two styles, H3C compatible MIB and H3C new MIB. In the H3C compatible MIB style, the device sysOID is under the H3C’s enterprise ID 25506, and the private MIB is under the enterprise ID 2011. In the H3C new MIB style, both the device sysOID and the private MIB are under the H3C’s enterprise ID 25506. These two styles of MIBs implement the same management function except for their root nodes. A device is shipped with MIB loaded and the MIB style may vary depending on the device. To implement NMS’s flexible management of the device, the device allows you to configure MIB style, that is, you can switch between the two styles of MIBs. However, you need to ensure that the MIB style of the device is the same as that of the NMS.

Setting the MIB Style

Follow these steps to set the MIB style:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Set the MIB style of the device	mib-style [ new | compatible ]	Optional new by default

 

 

Displaying and Maintaining MIB

To do…	Use the command…	Remarks
Display the MIB style	display mib-style	Available in any view

When configuring RMON, go to these sections for information you are interested in:

l          RMON Overview

l          Configuring RMON

l          Displaying and Maintaining RMON

l          RMON Configuration Example

RMON Overview

This section covers these topics:

l          Introduction

l          RMON Groups

Introduction

Remote Monitoring (RMON) is implemented based on the Simple Network Management Protocol (SNMP) and is fully compatible with the existing SNMP framework without the need of any modification on SNMP.

RMON provides an efficient means of monitoring subnets and allows SNMP to monitor remote network devices in a more proactive and effective way. It reduces traffic between network management station (NMS) and agent, facilitating large network management.

RMON comprises two parts: NMSs and agents running on network devices.

l          Each RMON NMS administers the agents within its administrative domain.

l          An RMON agent resides on a network monitor or a network probe. It monitors and collects statistics on traffic over the network segments connected to its interfaces, such as the total number of packets passed through a network segment over a specified period, or the total number of good packets sent to a host.

Working Mechanism

RMON allows multiple monitors. A monitor provides two ways of data gathering:

l          Using RMON probes. NMSs can obtain management information from RMON probes directly and control network resources. In this approach, RMON NMSs can obtain all RMON MIB information.

l          Embedding RMON agents in network devices such as routers, switches, and hubs to provide the RMON probe function. RMON NMSs exchange data with RMON agents using basic SNMP commands to gather network management information, which, due to system resources limitation, may not cover all MIB information but four groups of information, alarm, event, history, and statistics, in most cases.

The device adopts the second way. By using RMON agents on network monitors, an NMS can obtain information about traffic size, error statistics, and performance statistics for network management.

RMON Groups

Among the ten RMON groups defined by RMON specifications (RFC 1757), the device supports the event group, alarm group, history group and statistics group. Besides, H3C also defines and implements the private alarm group, which enhances the functions of the alarm group. This section describes the five kinds of groups in general.

Event group

The event group defines event indexes and controls the generation and notifications of the events triggered by the alarms defined in the alarm group and the private alarm group. The events can be handled in one of the following ways:

l          Logging event related information in the event log table

l          Sending traps to NMSs

l          Logging event information in the event log table and sending traps to NMSs

l          No action

Alarm group

The RMON alarm group monitors specified alarm variables, such as statistics on a port. If the sampled value of the monitored variable is bigger than or equal to the upper threshold, an upper event is triggered; if the sampled value of the monitored variable is lower than or equal to the lower threshold, a lower event is triggered. The event is then handled as defined in the event group.

The following is how the system handles entries in the RMON alarm table:

1)        Samples the alarm variables at the specified interval.

2)        Compares the sampled values with the predefined threshold and triggers events if all triggering conditions are met.

 

 

Private alarm group

The private alarm group calculates the sampled values of alarm variables and compares the result with the defined threshold, thereby realizing a more comprehensive alarming function.

System handles the prialarm alarm table entry (as defined by the user) in the following ways:

l          Periodically samples the prialarm alarm variables defined in the prialarm formula.

l          Calculates the sampled values based on the prialarm formula.

l          Compares the result with the defined threshold and generates an appropriate event.

 

 

History group

The history group periodically collects statistics on data at interfaces and saves the statistics in the history record table for query convenience. The statistics data includes bandwidth utilization, number of error packets, and total number of packets.

Once you successfully create a history entry in the specified interface, the history group starts to periodically collect statistics on packet at the specified interface. Each statistical value is a cumulative sum of packets sent/received on the interface during a sampling period.

Ethernet statistics group

The statistics group monitors port utilization. It provides statistics about network collisions, CRC alignment errors, undersize/oversize packets, broadcasts, multicasts, bytes received, packets received, and so on.

After the creation of a statistics entry on an interface, the statistics group starts to collect traffic statistics on the current interface. The result of the statistics is a cumulative sum.

Configuring RMON

Configuration Prerequisites

Before configuring RMON, configure the SNMP agent as described in SNMP Configuration in the System Volume.

Configuration Procedure

Follow these steps to configure RMON:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Create an event entry in the event table	rmon event entry-number [ description string ] { log | log-trap log-trapcommunity | none | trap trap-community } [ owner text ]	Optional
Enter Ethernet interface view	interface interface-type interface-number	—
Create an entry in the history table	rmon history entry-number buckets number interval sampling-interval [ owner text ]	Optional
Create an entry in the statistics table	rmon statistics entry-number [ owner text ]	Optional
Exit Ethernet interface view	quit	—
Create an entry in the alarm table	rmon alarm entry-number alarm-variable sampling-interval { absolute | delta } rising-threshold threshold-value1 event-entry1 falling-threshold threshold-value2 event-entry2 [ owner text ]	Optional
Create an entry in the private alarm table	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 ]	Optional

 

 

Table 3-1 Restrictions on the configuration of RMON

Entry	Parameters to be compared	Maximum number of entries that can be created
Event	Event description (description string), event type (log, trap, logtrap or none) and community name (trap-community or log-trapcommunity)	60
History	Sampling interval (interval sampling-interval)	100
Statistics	Only one statistics entry can be created on an interface.	100
Alarm	Alarm variable (alarm-variable), sampling interval (sampling-interval), sampling type (absolute or delta), rising threshold (threshold-value1) and falling threshold (threshold-value2)	60
Prialarm	Alarm variable formula (alarm-variable), sampling interval (sampling-interval), sampling type (absolute, changeratio or delta), rising threshold (threshold-value1) and falling threshold (threshold-value2)	50

 

Displaying and Maintaining RMON

To do…	Use the command…	Remarks
Display RMON statistics	display rmon statistics [ interface-type interface-number ]	Available in any view
Display the RMON history control entry and history sampling information	display rmon history [ interface-type interface-number ]	Available in any view
Display RMON alarm configuration information	display rmon alarm [ entry-number ]	Available in any view
Display RMON prialarm configuration information	display rmon prialarm [ entry-number ]	Available in any view
Display RMON events configuration information	display rmon event [ entry-number ]	Available in any view
Display log information for the specified or all event entries.	display rmon eventlog [ entry-number ]	Available in any view

 

RMON Configuration Example

Network requirements

Agent is connected to a configuration terminal through its console port and to a remote NMS across the Internet.

Create an entry in the RMON Ethernet statistics table to gather statistics on GigabitEthernet 1/1/1, and enable logging after received bytes exceed the specified threshold.

Figure 3-1 Network diagram for RMON

 

Configuration procedure

# Configure RMON to gather statistics for interface GigabitEthernet 1/1/1.

<Sysname> system-view

[Sysname] interface GigabitEthernet 1/1/1

[Sysname-GigabitEthernet1/1/1] rmon statistics 1 owner user1-rmon

[Sysname-GigabitEthernet1/1/1] quit

# Display RMON statistics for interface GigabitEthernet 1/1/1.

<Sysname> display rmon statistics GigabitEthernet 1/1/1

Statistics entry 1 owned by user1-rmon is VALID.

  Interface : GigabitEthernet1/1/1<ifIndex.3>

  etherStatsOctets         : 21657     , etherStatsPkts          : 307

  etherStatsBroadcastPkts  : 56        , etherStatsMulticastPkts : 34

  etherStatsUndersizePkts  : 0         , etherStatsOversizePkts  : 0

  etherStatsFragments      : 0         , etherStatsJabbers       : 0

  etherStatsCRCAlignErrors : 0         , etherStatsCollisions    : 0

  etherStatsDropEvents (insufficient resources): 0

  Packets received according to length:

  64     : 235       ,  65-127  : 67        ,  128-255  : 4

  256-511: 1         ,  512-1023: 0         ,  1024-1518: 0

# Create an event to start logging after the event is triggered.

<Sysname> system-view

[Sysname] rmon event 1 log owner 1-rmon

# Configure an alarm group to sample received bytes on GigabitEthernet 1/1/1. When the received bytes exceed the upper or below the lower limit, logging is enabled.

[Sysname] rmon alarm 1 1.3.6.1.2.1.16.1.1.1.4.1 10 delta rising-threshold 1000 1 falling-threshold 100 1 owner 1-rmon

[Sysname] display rmon alarm 1

Alarm table 1 owned by 1-rmon is VALID.

  Samples type          : delta

  Variable formula      : 1.3.6.1.2.1.16.1.1.1.4.1<etherStatsOctets.1>

  Sampling interval     : 10(sec)

  Rising threshold      : 1000(linked with event 1)

  Falling threshold     : 100(linked with event 1)

  When startup enables  : risingOrFallingAlarm

  Latest value          : 2552