Configuring A Notification Profile - Nortel 2300 Series Configuration Manual
Wlan security switch
Hide thumbs
Also See for 2300 Series:
- Reference (622 pages) ,
- Configuration manual (39 pages) ,
- Solution manual (108 pages)
Table of Contents
Advertisement
162 Configuring SNMP
Configuring a Notification Profile
A notification profile is a named list of all the notification types that can be generated by a switch, and for each notifica-
tion type, the action to take (drop or send) when an event occurs.
A default notification profile (named default) is already configured in WSS Software. All notifications in the default
profile are dropped by default. You can configure up to 10 notification profiles.
To modify the default notification profile or create a new one, use the following command:
set snmp profile {default | profile-name} {drop | send} {notification-type | all}
To clear a notification profile, use the following command:
clear snmp profile profile-name
The profile-name can be up to 32 alphanumeric characters long, with no spaces. To modify the default notification
profile, specify default.
The notification-type can be one of the following:
•
AuthenTraps—Generated when the WSS switch's SNMP engine receives a bad community string.
•
AutoTuneRadioChannelChangeTraps—Generated when the RF Auto-Tuning feature changes the channel on a
radio.
•
AutoTuneRadioPowerChangeTraps—Generated when the RF Auto-Tuning feature changes the power setting on
a radio.
•
ClientAssociationFailureTraps—Generated when a client's attempt to associate with a radio fails.
•
ClientAuthorizationSuccessTraps—Generated when a client is successfully authorized.
•
ClientAuthenticationFailureTraps—Generated when authentication fails for a client.
•
ClientAuthorizationFailureTraps—Generated when authorization fails for a client.
•
ClientClearedTraps—Generated when a client's session is cleared.
•
ClientDeAssociationTraps—Generated when a client is dissociated from a radio.
•
ClientDot1xFailureTraps—Generated when a client experiences an 802.1X failure.
•
ClientRoamingTraps—Generated when a client roams.
•
CounterMeasureStartTraps—Generated when WSS Software begins countermeasures against a rogue access
port.
•
CounterMeasureStopTraps—Generated when WSS Software stops countermeasures against a rogue access port.
•
DAPConnectWarningTraps—generated when a Distributed AP whose fingerprint has not been configured in
WSS Software establishes a management session with the switch.
•
DeviceFailTraps—Generated when an event with an Alert severity occurs.
•
DeviceOkayTraps—Generated when a device returns to its normal state.
•
LinkDownTraps—Generated when the link is lost on a port.
•
LinkUpTraps—Generated when the link is detected on a port.
•
MichaelMICFailureTraps—Generated when two Michael message integrity code (MIC) failures occur within 60
seconds, triggering Wi-Fi Protected Access (WPA) countermeasures.
•
MobilityDomainJoinTraps—Generated when the WSS switch is initially able to contact a mobility domain seed
member, or can contact the seed member after a timeout.
320657-A
Advertisement
Table of Contents
