![HP ProCurve 1600M Management And Configuration Manual Download Page 623](http://html.mh-extra.com/html/hp/procurve-1600m/procurve-1600m_management-and-configuration-manual_155305623.webp)
Troubleshooting
Debug and Syslog Messaging Operation
Syslog Operation
Syslog is a client-server logging tool that allows a client switch to send event
notification messages to a networked device operating with Syslog server
software. Messages sent to a Syslog server can be stored to a file for later
debugging analysis. Use of Syslog requires that you set up a Syslog server
application on a networked host accessible to the switch. (Refer to the
documentation for the Syslog server application you select.) Except as
described below, you must use the
debug
command to specify the message
types the switch sends to the configured Syslog server(s).
Syntax:
[no] logging <
syslog-ip-addr >
Enables or disables Syslog messaging to the specified IP
address. You can configure up to six addresses. If you config
ure an address when none are already configured, this com
mand enables destination logging (Syslog) and the Event
debug type. Thus, at a minimum, the switch begins sending
Event Log messages to the configured Syslog server(s). The
ACL, IP-OSPF, and/or IP-RIP message types will also be sent
to the Syslog server(s) if they are currently enabled debug types.
(Refer to
.)
no logging
removes all currently configured Syslog logging
destinations from the switch.
no logging <
syslog-ip-address
>
removes only the specified Syslog
logging destination from the switch.
If you use the “
no
” form of the command to delete the only
remaining logging address, debug destination logging is dis
abled on the switch, but the Event debug type is not changed
from its current setting.
To block messages to the configured Syslog server(s) from any
currently enabled debug type, use
no debug <
debug-type
>
. (Refer
.)
To disable Syslog logging on the switch without deleting the
server addresses, use
no debug destination logging
. Note that,
unlike the case where there are no Syslog servers configured,
if one or more Syslog servers are already configured, but Syslog
messaging is disabled, adding a new server address to those
already configured does not re-enable Syslog messaging. In
this case, you must use
debug destination logging
to re-enable
Syslog messaging.
C-39
Summary of Contents for ProCurve 1600M
Page 1: ...Management and Configuration Guide 8200zl ProCurve Switches K 12 XX www procurve com ...
Page 2: ......
Page 3: ...ProCurve Series 8200zl Switches September 2007 K 12 xx Management and Configuration Guide ...
Page 68: ...Using the Menu Interface Where To Go From Here 3 16 ...
Page 110: ...Using the ProCurve Web Browser Interface Status Reporting Features 5 26 ...
Page 152: ...Switch Memory and Configuration Multiple Configuration Files 6 42 ...
Page 220: ...Time Protocols SNTP Messages in the Event Log 9 28 ...
Page 252: ...Port Status and Configuration Uni Directional Link Detection UDLD 10 32 ...
Page 282: ...Power Over Ethernet PoE Operation PoE Operating Notes 11 30 ...
Page 472: ...Redundancy Switch 8212zl Event Log Messages 15 48 ...
Page 584: ...Monitoring and Analyzing Switch Operation Locating a Device B 74 ...
Page 652: ...Troubleshooting Restoring a Flash Image C 68 ...
Page 660: ...MAC Address Management Viewing the MAC Addresses of Connected Devices D 8 ...
Page 666: ...Monitoring Resources When Insufficient Resources Are Available E 6 ...
Page 670: ...Daylight Savings Time on ProCurve Switches F 4 ...
Page 688: ...18 Index ...
Page 689: ......