80etherStatsFragments : 0 , etherStatsJabbers : 0etherStatsCRCAlignErrors : 0 , etherStatsCollisions : 0etherStatsDropEvents (insufficient resources): 0Packets received according to length:64 : 235 , 65-127 : 67 , 128-255 : 4256-511: 1 , 512-1023: 0 , 1024-1518: 0• Perform SNMP Get operation on the NMS to obtain the value of the MIB node.History group configuration exampleNetwork requirementsAs shown in Figure 30, Agent is connected to a configuration terminal through its console port and toServer through Ethernet cables.Configure the RMON history statistics table to gather incoming packet statistics for Ethernet 1/0/1 everyone minute, so the administrator can view whether traffic bursts have happened on the interface in ashort time.Figure 30 Network diagramConfiguration procedure# Configure RMON to periodically gather statistics for interface Ethernet 1/0/1. system-view[Sysname] interface ethernet 1/0/1[Sysname-Ethernet1/0/1] rmon history 1 buckets 8 interval 60 owner user1The system gathers incoming packet statistics for Ethernet 1/0/1. To view the statistics:• Execute the display command.[Sysname-Ethernet1/0/1] display rmon historyHistoryControlEntry 2 owned by null is VALIDSamples interface : Ethernet1/0/1Sampled values of record 1 :dropevents : 0 , octets : 834packets : 8 , broadcast packets : 1multicast packets : 6 , CRC alignment errors : 0undersize packets : 0 , oversize packets : 0fragments : 0 , jabbers : 0collisions : 0 , utilization : 0Sampled values of record 2 :dropevents : 0 , octets : 962
