
15
7. XSNet 2800 SNMP management by traps and/or polling
Introduction
To prepare the XSNet 2800 switch for SNMP management, the database documenting the 2800’s variables
amenable to readout and/or modification must be registered with the program; such SNMP MIB documents are
available from our web site.
The System Information pane (on the SNMP HTML page, see figure 14) shows the network/device data
specifically made available to the SNMP manager for making the device, its location and service manager(s)
traceable.
You will always need to set the
community strings
(names) in the Communities pane to conform to those
configured in the SNMP manager. Often, these are ‘public’, mainly used for the read and trap communities, and
‘private’ or ‘netman’, for read-write operations. The manager software may offer additional choices.
Traps
Traps generated by the XSNet 2800 SW can be caught by any SNMP manager. Traps can be generated by
configuring an alarm level A-N on the Alarm settings page for the available events or variables to be monitored
using the SNMP manager program.
In the Traps pane (figure 14), at least the following information must be entered:
-
the SNMP version used
-
the IP address associated with the manager program, and the destination port (162 is a sensible default).
If desired, an alternative destination IP can be added. It is also possible to add an authentication trap to be able to
catch attempts at access using the wrong community string.
Figure 14. 2800 SW SNMP settings