2-4z The rmon alarm and rmon prialarm commands take effect on existing nodes only.z For each port, only one RMON statistics entry can be created. That is, if an RMON statistics entry isalready created for a given port, you will fail to create another statistics entry with a different indexfor the same port.Displaying RMONTo do… Use the command… RemarksDisplay RMON statistics display rmon statistics [ interface-typeinterface-number | unit unit-number ]Display RMON historyinformationdisplay rmon history [ interface-typeinterface-number | unit unit-number ]Display RMON alarminformation display rmon alarm [ entry-number ]Display extended RMON alarminformationdisplay rmon prialarm[ prialarm-entry-number ]Display RMON events display rmon event [ event-entry ]Display RMON event logs display rmon eventlog [ event-entry ]Available inany view.RMON Configuration ExampleNetwork requirementsz The switch to be tested is connected to a remote NMS through the Internet. Ensure that the SNMPagents are correctly configured before performing RMON configuration.z Create an entry in the extended alarm table to monitor the information of statistics on the Ethernetport, if the change rate of which exceeds the set threshold, the alarm events will be triggered.Network diagramFigure 2-1 Network diagram for RMON configurationConfiguration procedures# Add the statistics entry numbered 1 to take statistics on GigabitEthernet 1/0/1. system-view[Sysname] interface GigabitEthernet 1/0/1[Sysname-GigabitEthernet1/0/1] rmon statistics 1