# RMON

### 1. Function Overview

By making settings for the RMON (Remote network MONitering) function, you can monitor and record the traffic volume and error occurrences for each interface.
Since the settings for the RMON function and the data obtained by the RMON function are held as an MIB, they can be retrieved and edited from the SNMP manager.

The RMON function of this product supports the following groups defined in RFC2819.

- Ethernet statistics group

- History group

- Alarm group

- Event group

### 2. Definition of Terms Used

RMON MIB

MIB for the RMON function, defined in RFC2819

Ethernet statistics group

MIB group defined as group 1 of the RMON MIB.
This holds a table for monitoring Ethernet statistical information.
The information in the table includes counters for the number of packets, the number of errors, etc.
The etherStatsTable is the applicable MIB for this product.

History group

MIB group defined as group 2 of the RMON MIB.
At a specified interval, it measures the same information as the Ethernet statistics group, and has a table for saving the history of this information.
The MIBs relevant for this product are the historyControlTable and the etherHistoryTable.

Alarm group

MIB group defined as group 3 of the RMON MIB.
At the specified interval, the statistical information of the Ethernet statistics group is compared with the threshold values.
If the sampled values exceed the threshold values, the event defined for the event group is generated.
The alarmTable is the applicable MIB for this product.

Event group

MIB group defined as group 9 of the RMON MIB.
This is the action taken in response when the alarm group conditions are met.
The eventTable is the applicable MIB for this product.

### 3. Function Details

The operating specifications for operation of the RMON function are shown below.

#### 3.1. Common between groups

The specifications common between groups are given below.

1. In order to enable the RMON function on this product, the system-wide RMON function must be enabled.

   - Use the rmon command to make settings.

   - This is enabled by default.

   - You can also set this by using the private MIB ysrmonSetting(1.3.6.1.4.1.1182.3.7.1).

#### 3.2. Ethernet statistics group

The operating specifications for the Ethernet statistics group are given below.

1. Make settings by using the rmon statistics command on an interface.

2. Starting at the point at which you specified the rmon statistics command, statistical information is collected, and the etherStatsTable of the RMON MIB will be available for retrieval.

3. This can be specified for a physical interface.

4. A maximum of eight rmon statistics commands can be specified for the same interface.

5. If an rmon statistics command is deleted, the collected statistical information is also deleted.

6. If an rmon statistics command is overwritten, the previously collected statistical information is deleted, and collection is started once again.

7. If the RMON function is disabled system-wide, collection of statistical information is halted.
   If the RMON function is subsequently enabled system-wide, the previously collected statistical information is deleted, and collection is started once again.

8. The supported OIDs in the Ethernet statistics group are as follows.

        rmon(1.3.6.1.2.1.16)
         +- statistics(1.3.6.1.2.1.16.1)
             +- etherStatsTable(1.3.6.1.2.1.16.1.1)
                     + etherStatsEntry(1.3.6.1.2.1.16.1.1.1) { etherStatsIndex }
                         +- etherStatsIndex(1.3.6.1.2.1.16.1.1.1.1)         (read-only)
                         +- etherStatsDataSource(1.3.6.1.2.1.16.1.1.1.2)    (read-create)
                         |Interface being monitored
                         +- etherStatsDropEvents(1.3.6.1.2.1.16.1.1.1.3)    (read-only)
                         |Number of packets dropped
                         +- etherStatsOctets(1.3.6.1.2.1.16.1.1.1.4)        (read-only)
                         |Number of octets received
                         +- etherStatsPkts(1.3.6.1.2.1.16.1.1.1.5)          (read-only)
                         |Number of packets received
                         +- etherStatsBroadcastPkts(1.3.6.1.2.1.16.1.1.1.6) (read-only)
                         |Number of broadcast packets received
                         +- etherStatsMulticastPkts(1.3.6.1.2.1.16.1.1.1.7) (read-only)
                         |Number of multicast packets received
                         +- etherStatsCRCAlignErrors(1.3.6.1.2.1.16.1.1.1.8)(read-only)
                         |Number of FCS error packets received
                         +- etherStatsUndersizePkts(1.3.6.1.2.1.16.1.1.1.9) (read-only)
                         |Number of undersize packets received (packets smaller than 64 octets)
                         +- etherStatsOversizePkts(1.3.6.1.2.1.16.1.1.1.10) (read-only)
                         |Number of oversize packets received (packets larger than 1518 octets)
                         +- etherStatsFragments(1.3.6.1.2.1.16.1.1.1.11)    (read-only)
                         |Number of fragment packets received
                         |(packets smaller than 64 octets with abnormal FCS)
                         +- etherStatsJabbers(1.3.6.1.2.1.16.1.1.1.12)      (read-only)
                         |Number of jabber packets received
                         |(packets larger than 1518 octets with abnormal FCS)
                         +- etherStatsCollisions(1.3.6.1.2.1.16.1.1.1.13)   (read-only)
                         |Number of collisions
                         +- etherStatsOwner(1.3.6.1.2.1.16.1.1.1.20)        (read-create)
                         |Name of owner
                         +- etherStatsStatus(1.3.6.1.2.1.16.1.1.1.21)       (read-create)
                               Status of statistical group

#### 3.3. History group

The operating specifications for the history group are shown below.

1. Make settings by using the rmon history command on an interface.

2. Starting at the point at which you specified the rmon history command, historical information is collected at the specified interval, and the etherHistoryTable of the RMON MIB will be available for retrieval.

3. This can be specified for a physical interface.

4. A maximum of eight rmon history commands can be specified for the same interface.

5. If an rmon history command is deleted, the collected historical information is also deleted.

6. If an rmon history command is overwritten, the previously collected historical information is deleted, and collection is started once again.

7. If the RMON function is disabled system-wide, collection of historical information is halted.
   If the RMON function is subsequently enabled system-wide, the previously collected historical information is deleted, and collection is started once again.

8. The supported OIDs in the Ethernet history group are as follows.

        rmon(1.3.6.1.2.1.16)
         +- history(1.3.6.1.2.1.16.2)
             +- historyControlTable(1.3.6.1.2.1.16.2.1)
             |+ historyControlEntry(1.3.6.1.2.1.16.2.1.1) { historyControlIndex }
             |+- historyControlIndex(1.3.6.1.2.1.16.2.1.1.1)           (read-only)
             |+- historyControlDataSource(1.3.6.1.2.1.16.2.1.1.2)      (read-create)
             ||Interface being monitored
             |+- historyControlBucketsRequested(1.3.6.1.2.1.16.2.1.1.3)(read-create)
             ||Number of history group history saves requested
             |+- historyControlBucketsGranted(1.3.6.1.2.1.16.2.1.1.4)  (read-only)
             ||Number of history group histories saved
             |+- historyControlInterval(1.3.6.1.2.1.16.2.1.1.5)        (read-create)
             ||Interval at which history group histories are saved
             |+- historyControlOwner(1.3.6.1.2.1.16.2.1.1.6)           (read-create)
             ||Name of owner
             |+- historyControlStatus(1.3.6.1.2.1.16.2.1.1.7)          (read-create)
             |History group status
             |
             +- etherHistoryTable(1.3.6.1.2.1.16.2.2)
                     + etherHistoryEntry(1.3.6.1.2.1.16.2.2.1) { etherHistoryIndex, etherHistorySampleIndex }
                         +- etherHistoryIndex(1.3.6.1.2.1.16.2.2.1.1)         (read-only)
                         +- etherHistorySampleIndex(1.3.6.1.2.1.16.2.2.1.2)   (read-only)
                         +- etherHistoryIntervalStart(1.3.6.1.2.1.16.2.2.1.3) (read-only)
                         |Interval at which history group histories are saved
                         +- etherHistoryDropEvents(1.3.6.1.2.1.16.2.2.1.4)    (read-only)
                         |Number of packets dropped
                         +- etherHistoryOctets(1.3.6.1.2.1.16.2.2.1.5)        (read-only)
                         |Number of octets received
                         +- etherHistoryPkts(1.3.6.1.2.1.16.2.2.1.6)          (read-only)
                         |Number of packets received
                         +- etherHistoryBroadcastPkts(1.3.6.1.2.1.16.2.2.1.7) (read-only)
                         |Number of broadcast packets received
                         +- etherHistoryMulticastPkts(1.3.6.1.2.1.16.2.2.1.8) (read-only)
                         |Number of multicast packets received
                         +- etherHistoryCRCAlignErrors(1.3.6.1.2.1.16.2.2.1.9)(read-only)
                         |Number of FCS error packets received
                         +- etherHistoryUndersizePkts(1.3.6.1.2.1.16.2.2.1.10)(read-only)
                         |Number of undersize packets received (packets smaller than 64 octets)
                         +- etherHistoryOversizePkts(1.3.6.1.2.1.16.2.2.1.11) (read-only)
                         |Number of oversize packets received (packets larger than 1518 octets)
                         +- etherHistoryFragments(1.3.6.1.2.1.16.2.2.1.12)    (read-only)
                         |フNumber of fragment packets received
                         |(packets smaller than 64 octets with abnormal FCS)
                         +- etherHistoryJabbers(1.3.6.1.2.1.16.2.2.1.13)      (read-only)
                         |Number of jabber packets received
                         |(packets larger than 1518 octets with abnormal FCS)
                         +- etherHistoryCollisions(1.3.6.1.2.1.16.2.2.1.14)   (read-only)
                         |Number of collisions
                         +- etherHistoryUtilization(1.3.6.1.2.1.16.2.2.1.15)  (read-only)
                               Estimated value of network usage ratio

#### 3.4. Alarm group

The operating specifications for the alarm group are shown below.

1. Use the rmon alarm command to make settings.

2. From the point that the rmon alarm command is specified, sampling occurs at the specified interval.

3. If an rmon alarm command is overwritten, the previous sampling data is deleted, and sampling is started once again.

4. If the RMON function is disabled system-wide, sampling is halted.
   If the RMON function is subsequently enabled system-wide, the previous sampling data is deleted, and sampling is started once again.

5. Only etherStatsEntry(.1.3.6.1.2.1.16.1.1.1) MIB objects that have a counter type can be specified as the object of alarm group monitoring.

6. If the Ethernet statistics group used by the rmon alarm command is deleted, the rmon alarm command is also deleted.

7. If the event group used by the rmon alarm command is deleted, the rmon alarm command is also deleted.

8. The supported OIDs in the alarm group are as follows.

        rmon(1.3.6.1.2.1.16)
         +- alarm(1.3.6.1.2.1.16.3)
             +- alarmTable(1.3.6.1.2.1.16.3.1)
                     + alarmEntry(1.3.6.1.2.1.16.3.1.1) { alarmIndex }
                         +- alarmIndex(1.3.6.1.2.1.16.3.1.1.1)              (read-only)
                         +- alarmInterval(1.3.6.1.2.1.16.3.1.1.2)           (read-create)
                         |Sampling interval
                         +- alarmVariable(1.3.6.1.2.1.16.3.1.1.3)           (read-create)
                         |MIB object to be monitored
                         +- alarmSampleType(1.3.6.1.2.1.16.3.1.1.4)         (read-create)
                         |Sampling type
                         +- alarmValue(1.3.6.1.2.1.16.3.1.1.5)              (read-only)
                         |Estimated value
                         +- alarmStartupAlarm(1.3.6.1.2.1.16.3.1.1.6)       (read-create)
                         |Threshold value used for first alarm determination
                         +- alarmRisingThreshold(1.3.6.1.2.1.16.3.1.1.7)    (read-create)
                         |Upper threshold value
                         +- alarmFallingThreshold(1.3.6.1.2.1.16.3.1.1.8)   (read-create)
                         |Lower threshold value
                         +- alarmRisingEventIndex(1.3.6.1.2.1.16.3.1.1.9)   (read-create)
                         |Event index when crossing upper limit
                         +- alarmFallingEventIndex(1.3.6.1.2.1.16.3.1.1.10) (read-create)
                         |Event index when crossing lower limit
                         +- alarmOwner(1.3.6.1.2.1.16.3.1.1.11)             (read-create)
                         |Name of owner
                         +- alarmStatus(1.3.6.1.2.1.16.3.1.1.12)            (read-create)
                               Alarm group status

Alarm detection is determined by an upper threshold value and a lower threshold value. If the threshold value is crossed, the specified event is executed.
If an alarm is detected, the alarm will not be detected again until the value crosses the opposite threshold.
The following cases are explained as examples.

- At point 1, the upper threshold value is crossed, so an alarm is detected.
  The threshold value that is used for the very first decision can be specified by STARTUP.
  In the example above, we will assume that the STARTUP value is “1” (using only the upper threshold value (risingAlarm)) or “3” (using both the upper threshold value and the lower threshold value (risingOrFallingAlarm)).

- At point 2, an alarm is not detected.

- At point 3, the upper threshold value is crossed, but since the opposite threshold was not previously crossed, an alarm is not detected.

- At point 4, the lower threshold value is crossed, and since the upper threshold was previously crossed, an alarm is detected.

- At point 5, the lower threshold value is exceeded, but since the opposite upper threshold was not previously crossed, an alarm is not detected.

- At point 6, the upper threshold value is crossed, and since the lower threshold was previously crossed, an alarm is detected.

#### 3.5. Event group

The operating specifications for the event group are shown below.

1. Use the rmon event command to make settings.

2. The following operations can be specified for the event group.

   - Record to log

   - Send SNMP trap

   - Record to log and send SNMP trap

3. If trap transmission is specified, the following SNMP commands must be set in order to transmit the SNMP trap.

   - snmp-server host

   - snmp-server enable trap rmon

4. The following operations will be carried out when specifying trap transmission.

   - SNMPv1、SNMPv2c

     - Only the traps for which the community name specified using the rmon event command, and for which the community name specified by the snmp-server host command are matching will be transmitted.

   - SNMPv3

     - Only the traps for which the community name specified using the rmon event command, and for which the user name specified by the snmp-server host command are matching will be transmitted.

5. The supported OIDs in the event group are as follows.

        rmon(1.3.6.1.2.1.16)
         +- event(1.3.6.1.2.1.16.9)
             +- eventTable(1.3.6.1.2.1.16.9.1)
                     + eventEntry(1.3.6.1.2.1.16.9.1.1) { eventIndex }
                         +- eventIndex(1.3.6.1.2.1.16.9.1.1.1)        (read-only)
                         +- eventDescription(1.3.6.1.2.1.16.9.1.1.2)  (read-create)
                         |Event description
                         +- eventType(1.3.6.1.2.1.16.9.1.1.3)         (read-create)
                         |Event type
                         +- eventCommunity(1.3.6.1.2.1.16.9.1.1.4)    (read-create)
                         |Community name
                         +- eventLastTimeSent(1.3.6.1.2.1.16.9.1.1.5) (read-only)
                         |Event execution time
                         +- eventOwner(1.3.6.1.2.1.16.9.1.1.6)        (read-create)
                         |Name of owner
                         +- eventStatus(1.3.6.1.2.1.16.9.1.1.7)       (read-create)
                               Event group status

#### 3.6. Setting by SetRequest from an SNMP manager

The same content as the commands of each group can be specified by using SetRequest from an SNMP manager.
The procedure for making settings from an SNMP manager is as follows.

As an example, we explain how to make new settings for the Ethernet statistics information (etherStatsTable) group to port1.1 using index number 1.
Similar operations can be used to make settings for a supported MIB on other groups.

1. Make SNMP settings to allow the MIB to be written.
   For details, refer to SNMP.

2. For etherStatsStatus.1, specify “2” (createRequest).
   The “.1” of etherStatsStatus.1 is the etherStatsTable index.

3. For etherStatsDataSource.1, specify ifIndex.5001 as the interface to be monitored.
   ifIndex.5001 indicates port1.1.

4. Specifying “owner” is optional, but if you do, specify the text string in etherStatsOwner.1.

5. For etherStatsStatus, specify “1” (valid).

When you perform the above steps, the following commands are specified for port1.1.
We assume that “RMON” was set as the “owner” setting.

     rmon statistics 1 owner RMON

Below we show how to disable the RMON function system-wide from the SNMP manager.

1. Make SNMP settings to allow the MIB to be written.
   For details, refer to SNMP.

2. For ysrmonSetting(1.3.6.1.4.1.1182.3.7.1), specify “2” (disabled).

When you perform the above steps, the following commands are specified.

     rmon disable

To specify enable, set ysrmonSetting(1.3.6.1.4.1.1182.3.7.1) to “1” (enabled).

### 4. Related Commands

Related commands are indicated below.
For details on the commands, refer to the Command Reference.

Operations | Operating commands
--- | ---
Enable the RMON function | rmon
Set RMON Ethernet statistics group | rmon statistics
Set RMON history group | rmon history
Set RMON event group | rmon event
Set RMON alarm group | rmon alarm
Show RMON function status | show rmon
Show RMON Ethernet statistics group status | show rmon statistics
Show RMON history group status | show rmon history
Show RMON event group status | show rmon event
Show RMON alarm group status | show rmon alarm
Clear RMON Ethernet statistics group counters | rmon clear counters

### 5. Examples of Command Execution

#### 5.1. Setting an Ethernet statistics group

Make Ethernet statistics group settings for port 1.1, and from the SNMP manager, retrieve the MIB of the Ethernet statistical information group.

■ Setting Procedure

1. Enable the Ethernet statistics group setting for port1.1.
   The index of the Ethernet statistics group is “1.”

       Yamaha(config)#interface port1.1
       Yamaha(config-if)#rmon statistics 1 (1)

   1 | Enable the Ethernet statistics group settings

2. From the SNMP manager, make SNMP settings that the MIB of the Ethernet statistics group can be retrieved.
   In this example, we use “private” access on SNMPv1 or SNMPv2c.

       Yamaha(config)#snmp-server community private rw (1)

   1 | Set the readable/writable community name as “private”.

3. From the SNMP manger, it will be possible to retrieve the etherStatsTable(.1.3.6.1.2.1.16.1.1) with the community name “private.”

#### 5.2. Setting a history group

Make settings for the history group of port1.1 and retrieve the MIB of the history group from the SNMP manager.

■ Setting Procedure

1. Enable the port1.1 history group setting.
   The index of the history group is “1.”

       Yamaha(config)#interface port1.1
       Yamaha(config-if)#rmon history 1 (1)

   1 | Enable the history group settings

2. From the SNMP manager, make SNMP settings that the MIB of the history group can be retrieved.
   In this example, we use “private” access on SNMPv1 or SNMPv2c.

       Yamaha(config)#snmp-server community private rw (1)

   1 | Set the readable/writable community name as “private”.

3. From the SNMP manger, it will be possible to retrieve the etherHistoryTable(.1.3.6.1.2.1.16.2.2) with the community name “private.”

#### 5.3. Setting an alarm event group

Use the alarm group to monitor the statistical information values of the Ethernet statistics group.
The conditions for monitoring are as follows.

- The MIB to be monitored is port1.1’s etherStatsPkts(.1.3.6.1.2.1.16.1.1.1.5).

- The sampling interval is 180 seconds.

- The sampling type is delta.

- The upper threshold value is 2000.

- The lower threshold value is 1000.

When the above monitoring conditions are matched, the following event group is executed.

- Record to log and send SNMP trap

- Community name is “RMON”

■ Setting Procedure

1. Make the required settings for SNMP trap transmission.

       Yamaha(config)#snmp-server host 192.168.100.3 traps version 2c RMON (1)
       Yamaha(config)#snmp-server enable trap rmon (2)

   1 | Set the trap destination
   2 | Enable transmission of traps for the RMON function

2. Make event group settings.
   The index of the event group is “1.”

       Yamaha(config)#rmon event 1 log-trap RMON (1)

   1 | Enable the event group settings

3. In order to set the alarm group’s monitoring target MIB object, enable the port1.1 Ethernet statistics group setting.
   The index of the Ethernet statistics group is “1.”

       Yamaha(config)#interface port1.1
       Yamaha(config-if)#rmon statistics 1 (1)

   1 | Enable the Ethernet statistics group settings

4. Set the alarm group with the listed conditions.
   The index of the alarm group is “1.”

       Yamaha(config)#rmon alarm 1 etherStatsPkts.1 interval 180 delta rising-threshold 3000 event 1 falling-threshold 2000 event 1 (1)

   1 | Enable an alarm group

### 6. Points of Caution

None

### 7. Related Documentation

- Maintenance and Operation Functions: SNMP

Search result
No more search results.
There are no topics that match your search query.