Symbol Technologies WS 2000 - Manual (Page 74)

System Administration
Trap Trap Name Generates a Trap when…
Category
MU Traps MU associated An MU becomes associated with one of
the switch’s Wireless Local Area
Networks (WLANs).
MU unassociated An MU becomes unassociated with (or
gets dropped from) one of the switch’s
WLANs.
MU denied
association Check this box to generate a trap when
an MU cannot associate with the switch-
managed network. A denial of service can
result from an absent or incorrectly
specified MAC address on a WLAN
Security screen.
AP Traps AP adopted Any of the switch’s Wireless Local Area
Networks (WLANs) adopts an AP.
AP unadopted Any of the switch’s WLANs unadopts (or
drops) an AP.
AP denied adoption Check this box to generate a trap when
any of the switch’s WLANs deny the
adoption of an AP.
4. Click the OK button when done setting traps in a subwindow.
5. Click the Apply button to save the trap settings.
6. It is necessary to tell the switch where to send the notifications. Set the trap
configuration (directions found in one of the following two sections) to indicate where
to send the notifications.
Setting the Trap Configuration for SNMP v1/v2c
To set the trap notification destination for the SNMP v1/v2c servers, add one or more
entries to SNMP v1/v2c Trap Configuration table.
1. Click the Add button to add a new entry to the table.
2. Specify a Destination IP addresses for the systems that will receive notification when
an SNMP trap is generated.
3. Specify a destination User Datagram Protocol (UDP) port for receiving the traps that
are sent by SNMP agents.
UDP offers direct connection for sending and receiving datagrams over an IP network.
4. Specify a Community name that matches one of the community names added on the
SNMP Access screen.
5. Select the appropriate SNMP Version (v1 or v2) from the pull-down list for this
particular SNMP server.
6. Click the Apply button to save the entries.
Copyright © 2004 Symbol Technologies, Inc. All Rights Reserved 74
WS 2000 Wireless Switch: 1.0 Date of last Revision: March 2004