Remote Network Monitoring (RMON) History Entry Configuration on 200/300 Series Managed Switches

Objective

RMON allows the exchange of monitoring-data between devices on a network. You can create a RMON history entry for an interface to gather information about network traffic within that interface. This article explains how to configure a RMON history entry 200/300 Series Managed Switches.

Applicable Devices

• SF/SG 200 and SF/SG 300 Series Managed Switches

Software Version

• 1.3.0.62

Display RMON History

Step 1. Log in to the web configuration utility and choose Status and Statistics > RMON > History. The History page opens:

Step 2. Click Add to configure a new entry in the control table. The Add RMON History window appears.

Note: The New History Entry displays the number of the new history table entry.

Step 4. Click the radio button of one of the available options in the Source Interface to choose the interface from which the RMON information is taken. The options are:

• Port — This option lets you choose a specific port from the Port drop-down-list.

• LAG — This option lets you choose a specific Link Aggregation Group (LAG) from the LAG drop-down list. A LAG combines individual interfaces into a single logical link, which provides an aggregate bandwidth of up to eight physical links.

Step 5. Enter the number of samples to store in the Max No. of Samples to Keep field.

Step 6. Enter the interval time the samples are collected from the interface in the Sampling Interval field.

Step 7. Enter the name of the user that requested RMON information in the Owner field.

Step 8. Click Apply to save your configuration.

Step 9. (Optional) To edit an entry in the History Control Table, check the check box of the entry you wish to edit and click Edit.

Step 10. (Optional) To delete an entry in the History Control Table, check the check box of the entry you wish to delete and click Delete. 

History Table

 Step 1. Click History Table to see the information obtained from the RMON history entry for the specific interface. The History Table opens:

Step 2. Check the Filter check box and choose from the History No. equals to drop-down list the entry you wish to obtain RMON information from.

Step 3. Click Go.

Step 4. (Optional) To start a new search, click Clear Filter.

The history Table display the next RMON information for the chose RMON history entry:

• History Entry No. — The number of the current RMON history entry.

• Owner — The owner name.

• Sample No. — The sample number of the current RMON history entry.

• Drop Events — The number of dropped packets for each sample of the current RMON history entry.

• Bytes Received — The number of octets received for each sample of the current RMON history entry.

• Packets Received — The number of packets received for each sample of the current RMON history entry.

• Broadcast Packets — The number of broadcast packets used for each sample of the current RMON history entry.

• Multicast Packets — The number of multicast packets used for each sample of the current RMON history entry.

• CRC Align Errors — The number of Cyclic Redundancy Check errors and Align errors occurred for each sample of the current RMON history table.

• Undersize Packets — The number of packets with less than 64 octets received for each sample of the current RMON history table.

• Oversize Packets — The number of packets with more than 2000 octets received for each sample of the current RMON history table.

• Fragments — The number of packets with less than 64 octets received without framing bits and with Frame Check Sequence (FCS) octets for each sample of the current RMON history table.

• Jabbers — The number of packets received with more than 2000 octets without frame bits and with FCS octets with either a bad FCS with an integral number of octets, or FCS octets with a bad FCS with a non-integral octet number

• Collisions — The number of collisions received for each sample of the current RMON history table.

• Utilization — The percentage of the current traffic compared to the maximum traffic the interface can support.

Revision History

Revision	Publish Date	Comments
1.0	10-Dec-2018	Initial Release