H3C Technologies H3C SecPath F1000-E - Manual (Page 148)

9
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
Sampled values of record 8 :
dropevents : 0 , octets : 1154
packets : 13 , broadcast packets : 1
multicast packets : 6 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
fragments : 0 , jabbers : 0
collisions
: 0 , utilization : 0
• Obtain the value of the MIB node directly by executing the SNMP Get operation on the NMS
through software.
Alarm Group Configuration Example
Network requirements
As shown in Figure 3 , Agent is connected to a console terminal through its console port and to an NMS
across Ethernet.
Do the following:
• Connect GigabitEthernet 0/1 to the FTP server. Gather statistics on traffic of the server on
GigabitEthernet 0/1 with the sampling interval being five seconds. When traffic is above or below
the thresholds, Agent sends the corresponding traps to the NMS.
• Execute the display rmon statistics command on Agent to display the statistics, and query the
statistics on the NMS.
Figure 3 Network diagram for RMON
Configuration procedure
# Configure the SNMP agent. (Note that parameter values configured on the agent must be the same as
the following configured on the NMS: suppose SNMPv1 is enabled on the NMS, the read community
name is public, the write community name is private, the IP address of the NMS is 1.1.1.2,
authentication protocol is MD5, authorization password is authkey, the privacy protocol is DES56,
and the privacy password is prikey.)
system-view
[Sysname] snmp-agent
[Sysname] snmp-agent community read public
[Sysname] snmp-agent community write private
[Sysname] snmp-agent sys-info version v1