1-11 display rmon statistics GigabitEthernet 2/0/1EtherStatsEntry 1 owned by user1-rmon is VALID.Interface : GigabitEthernet2/0/1etherStatsOctets : 57329 , etherStatsPkts : 455etherStatsBroadcastPkts : 53 , etherStatsMulticastPkts : 353etherStatsUndersizePkts : 0 , etherStatsOversizePkts : 0etherStatsFragments : 0 , etherStatsJabbers : 0etherStatsCRCAlignErrors : 0 , etherStatsCollisions : 0etherStatsDropEvents (insufficient resources): 0Packets received according to length:64 : 7 , 65-127 : 413 , 128-255 : 35256-511: 0 , 512-1023: 0 , 1024-1518: 0After completing the configuration, you may query alarm events on the NMS. On the monitored device,alarm event messages are displayed when events occur. The following is a sample output:[Sysname]#Aug 27 16:31:34:12 2005 Sysname RMON/2/ALARMFALL:Trap 1.3.6.1.2.1.16.0.2 Alarm table 1monitors 1.3.6.1.2.1.16.1.1.1.4.1 with sample type 2,has sampled alarm value 0 less than(or=) 50.Private Alarm Group Configuration ExampleNetwork requirementsAs shown in Figure 1-4, monitor the utilization rate of interface GigabitEthernet 2/0/1 when it is receivingpackets. When the utilization rate is higher than 80%, the system logs the event locally and sends a trapto the NMS; when the utilization rate is lower than 5%, the system only logs the event locally.Figure 1-4 Network diagram for RMONConfiguration procedure# Configure the SNMP parameters. (Note that, parameter values configured on the agent must be thesame with the following configured on the NMS: suppose SNMPv3 is enabled on the NMS, the username is v3user, the IP address of the NMS is 1.1.1.2, authentication protocol is MD5, authorizationpassword is authkey, the privacy protocol is DES56, and the privacy password is prikey.) system-view[Sysname] snmp-agent[Sysname] snmp-agent sys-info version v3[Sysname] snmp-agent group v3 v3group[Sysname] snmp-agent usm-user v3 v3user v3group authentication-mode md5 authkey privacy-modedes56 prikey
