User's Manual

Configuration Guide of XGS-5240-Series
68
{noauthnopriv | authnopriv | authpriv}}}
<user-string>
no snmp-server host { <host-ipv4-addre
ss> | <host-ipv6-address> } {v1 | v2c |
{v3 {noauthnopriv | authnopriv | authpri
v}}} <user-string>
v1/v2, this command also configures Trap
community string; for SNMP v3, this
command also configures Trap user name
and security level. The “no”
form of this
command cancels this IPv4 or IPv6 address.
snmp-server trap-source {<ipv4-addres
s> | <ipv6-address>}
no snmp-server trap-source {<ipv4-addr
ess> | <ipv6-address>}
Set the source IPv4 or IPv6 address which is
used to send trap packet, the no command
deletes the configuration.
Port mode
[no] switchport updown notification
enable
Enable/disable the function of sending the
trap message to the port of UP/DOWN event.
9. Enable/Disable RMON
Command
Explanation
Global mode
rmon enable
no rmon enable
Enable/disable RMON.
4.4.5 Typical SNMP Configuration Examples
The IP address of the NMS is 1.1.1.5; the IP address of the switch (Agent) is 1.1.1.9.
Scenario 1: The NMS network administrative software uses SNMP protocol to obtain data
from the switch.
The configuration on the switch is listed below:
Switch(config)#snmp-server enable
Switch(config)#snmp-server community rw private
Switch(config)#snmp-server community ro public
Switch(config)#snmp-server securityip 1.1.1.5
The NMS can use private as the community string to access the switch with read-write
permission, or use public as the community string to access the switch with read-only
permission.
Scenario 2: NMS will receive Trap messages from the switch (Note: NMS may have
community string verification for the Trap messages. In this scenario, the NMS uses a Trap
verification community string of usertrap).
The configuration on the switch is listed below: