No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CLI-based Configuration Guide - Network Management and Monitoring

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Understanding RMON and RMON2

Understanding RMON and RMON2

RMON

Before configuring RMON, you must understand concepts of four groups (statistics, history, alarm, and event) and Huawei-defined extended alarm group. Before configuring RMON2, you must understand the concepts of protocolDir and nlHost.

RMON provides packet statistics and alarm functions. The management devices use RMON to remotely monitor and manage network elements.

RMON uses statistics group and history group to provide Ethernet statistics and history statistics functions.

  • Ethernet statistics (statistics group in RMON MIB): collects basic statistics on each monitored network. The system keeps on collecting traffic statistics and distribution of each type of packets on a network segment. Additionally, the system can count the number of error packets of different types, collisions, CRC error packets, undersized (or large) packets, broadcast and multicast packets, bytes received, and packets received.
  • History statistics (history group in RMON MIB): periodically samples and records network statistics. The system can periodically collect statistics on each type of traffic, including bandwidth usage, number of error packets, and total number of packets.

RMON alarm functions include event definition function and alarm threshold setting function.

  • Event definition (event group in RMON MIB): controls the events and notifications sent from the device and provides all events related to RMON agent. When an event occurs, the system records a log or sends a trap to the NMS.

  • Alarm threshold setting (alarm group in RMON MIB): monitors the specified alarm variables (OID of an object). Based on the user-defined thresholds and sampling time, the system periodically obtains the specified alarm variables. When the alarm variables values reach or exceed the rising threshold, a rising threshold alarm event is triggered. When the alarm variables values reach or fall below the falling threshold, a falling threshold alarm event is triggered. The RMON agent records the monitored status in log or sends a trap to the NMS.

RMON standard defines multiple RMON groups. The router supports the Huawei-defined extended alarm, statistics, history, alarm, and event groups. Details about the groups are as follows:

  • Statistics group

    The statistics group keeps on collecting statistics on each type of traffic on Ethernet interfaces and records statistics results in the etherStatsTable for later retrieval. Traffic statistics include the number of network collisions, CRC error packets, undersized (or large) data packets, broadcast packets, multicast packets, received bytes, and received packets.

    After a statistics entry is created on an interface, the statistics group starts collecting statistics on the packets. The statistics are accumulated.

  • History group

    The history group periodically collects network status statistics and stores them for future use.

    The history group provides two tables:

    • historyControlTable: sets control information such as the sampling interval.

    • etherHistoryTable: stores network statistics collected by the history group and provides the network administrator with history statistics such as the traffic on a network segment, error packets, broadcast packets, bandwidth usage, and collisions.

  • Event group

    The defined events are used for the configuration options of alarm group and extended alarm group. When alarm conditions are met, an event is triggered. RMON event management is to add events to the specified rows in the event table, and the following options are supported:

    • log: only send log

    • trap: only send trap to the NMS

    • log-trap: send both log and trap

    • none: take no action

  • Alarm group

    An alarm group presets a set of thresholds for alarm variables, which can be objects in a local MIB. Based on the user-defined alarmTable, the system periodically obtains the specified alarm variables. When the alarm variables values reach or exceed the rising threshold, a rising threshold alarm event is triggered. When the alarm variables values reach or fall below the falling threshold, the system takes actions according to the action configuration.

  • Extended alarm group

    Based on RFC, the extended alarm group has the following new function: set alarm object and keepalive time using expressions. This group provides the prialarmTable. Compared with the alarm table defined in RFC, the extended alarm table has the following new options:

    • Extended alarm variable expression. It is the arithmetic expression composed of alarm variables OIDs (+, -, *, /, or brackets).

    • Descriptions of extended alarm entries

    • Sampling interval variables

    • Extended alarm types: Forever or Cycle. If Cycle is set, no alarm is generated and the entry is deleted after the specified cycle period expires.

Each entry has a lifetime. When an entry's status is not valid, the entry can exist for a certain period before it is deleted. The entry is deleted when the lifetime decreases to 0. Table 2-1 shows the capacity of each table and the maximum lifetime of an entry in each table.

Table 2-1  Lifetime of entries in each table

Table

Table Size (Bytes)

Maximum Lifetime (Seconds)

etherStatsTable

100

600

historyControlTable

100

600

alarmTable

60

6000

eventTable

60

600

logTable

600

-

prialarmTable

60

6000

NOTE:

Each entry in the historyControlTable corresponds to a maximum of 10 history records in the etherHistoryTable. When more than 10 records are generated, the old ones are overwritten.

No maximum lifetime is specified for the entries in logTable. Each event entry in logTable corresponds to up to 10 logs. When more than 10 logs are generated, the old ones are overwritten.

When an LPU is removed, the etherStatsTable and historyControlTable status is changed to invalid and the lifetime of entries in the etherStatsTable and historyControlTable is set to 1200 seconds. When the lifetime decreases to 0, the entry is deleted.

When an LPU is inserted, the corresponding entry status is changed to valid.

RMON2

Currently, the router provides two RMON2 MIB groups: protocolDir and nlHost, and the RMON agent can collect statistics on IP packets. The RMON agent supports three tables: protocolDirTable, hostTable, and hostControlTable.

The hostTable uses customized indexes to invoke the protocolDirTable and hostControlTable. The hostTable does not need to be configured when you configure RMON2 traffic statistics function. After the protocolDirTable and hostControlTable are configured, the hostTable automatically collect traffic statistics.

  • protocolDirTable

    Lists the protocols that the RMON agent can resolve and collect statistics on. Each protocol occupies a row. The protocols include network-layer, transport-layer, and upper-layer protocols.

  • hostTable

    Collects traffic statistics on each host and analyzes incoming and outgoing data packets on interfaces based on IP addresses.

  • hostControlTable

    Is classified into network-layer hostControlTable and application-layer hostControlTable. The hostControlTable defines the statistics monitoring interface and records the number of frames received by the interface but are not recorded into the nlHost table. Additionally, this table records the number of times entries are added and deleted and the maximum number of entries in nlHostTable.

Currently, the router supports only network-layer hostControlTable, so it does not control application-layer host groups. Therefore, only IP protocols can be configured in the protocolDirTable.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174072

Views: 101420

Downloads: 335

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next