Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
Sending Event Log Messages as Traps
Use the following options to send Event Log messages as traps.
Table 13-2. Options for Sending Event Log Messages as Traps
Event Level Description
None (default) Send no log messages.
All Send all log messages.
Not INFO Send the log messages that are not information-only.
Critical Send critical-level log messages.
Debug Reserved for ProCurve-internal use.
For example, to configure a trap receiver in a community named "red-team"
with an IP address of 10.28.227.130 to receive only "critical" log messages:
ProCurve(config)# snmp-server trap-receiver
red-team 10.28.227.130 critical
Notes To replace one community name with another for the same IP address, you
must use no snmp-server host < community-name> < ip-address > to delete the
unwanted community name. Otherwise, adding a new community name with
an IP address already in use with another community name simply creates
two allowable community name entries for the same management station.
If you do not specify the event level ([<none | all | non-info | critical | debug>])
then the switch does not send event log messages as traps. "Well-Known" traps
and threshold traps (if configured) will still be sent.
Using the CLI To Enable Authentication Traps
Note For this feature to operate, one or more trap receivers must be configured on
the switch. See “Configuring Trap Receivers” on page 13-21.
13-24
To Next Page
Loading...
Need help?
General