Filter
Top Products
20
Figure 3-12: The Stack member list Web page
3.10 SNMP
The management switch provides Simple Network Management Protocol (SNMP) over the UDP/IP
transport protocol as defined in RFC 1517 for network management applications. The screen in Figure
3-13 appears.
To control the access of the system, a list of community entries is defined. Each community entry
consists of a community string and its access privilege. The Access privilege is either “Read Only” or
“Read-Write”. Only SNMP messages with correct community string and allowable operation are re-
sponded by the system. The community list is configurable by all management operations. Only SNMP
community with “Read-Write” can view the whole list and make modifications. A “Read Only” com-
munity can only see its own community entry.
!
NOTE
In a stack environment, for master switch to know which s
witch you want to view and set by
SNMP, either the switches’ IP or community
name must be different. Thus, if you have
stacked several switches by single IP, their community name must be different.
Trap messages are generated to report system events spontaneously as defined in RFC 1215. The
system can generate traps defined in the MIB it supports.
A list of “Trap Receivers” is defined in management as the target of each trap message. A Trap Re-
ceiver is a network node that deserves the trap message sent by management switch. A Trap
Receiver entry contains the IP address of the node and a community string that is included in the trap
message. When an event arises that requires a trap message to be sent, it is sent to every node listed
in the Trap Receiver.
!
NOTE
If you are configuring slave switch’s SNMP settings, please reboot the switch
after making
any configuration.