
Troubleshooting
Debug/Syslog Operation
b. Re-enter the
logging
command in Step “a” to configure additional
Syslog servers. You can configure up to a total of six servers. (When
multiple server IP addresses are configured, the switch sends the
debug message types that you configure in Step 3 to all IP addresses.)
2. To use a CLI session on a destination device for debug messaging:
a. Set up a serial, Telnet, or SSH connection to access the switch’s CLI.
b. Enter the
debug destination session
command at the manager level.
3. Enable the types of debug messages to be sent to configured Syslog
servers and/or the current session device by entering the
debug
<
debug-
type
>
command:
ProCurve# debug <all|arp-protect|event|ip
[bgp|forwarding|packet|rip|routemap]|ipv6|lldp>
Repeat this step if necessary to enable multiple debug message types.
By default, Event Log messages are sent to configured debug destination
devices. To block Event Log messages from being sent, enter the
no debug
event
command.
4. If necessary, enable a subset of Event Log messages to be sent to config
ured Syslog servers by specifying a severity level and/or system module
using the following commands
ProCurve(config)# logging severity
< debug | major | error | warning | info >
ProCurve(config)# logging system-module
<
system-module
>
To display a list of valid values for each command, enter
logging severity
or
logging system-module
followed by
?
or pressing the
Tab
key.
The severity levels in order from the highest to lowest severity are: major,
error, warning, info, debug. For a list of valid values for the
logging system-
module
<
system-module
>
command
,
refer to Table C-1 on page C-25
.
5. If you configure system-module and/or severity-level values to filter Event
Log messages, when you finish troubleshooting, you may want to reset
these values to their default settings so that the switch sends all Event Log
messages to configured debug destinations (Syslog servers and/or CLI
session).
To remove a configured setting and restore the default values that send
all Event Log messages, enter one or both of the following commands:
ProCurve(config)# no logging severity
< debug | major | error | warning | info>
ProCurve(config)# no logging system-module
<
system-module
>
C-40
Содержание ProCurve 6120G/XG
Страница 1: ...ProCurve Series 6120 Switches Management and Configuration Guide November 2010 Version Z 14 22 ...
Страница 2: ......
Страница 3: ...HP ProCurve 6120G XG Switch 6120XG Switch November 2010 Z 14 22 Management and Configuration Guide ...
Страница 24: ...xxii ...
Страница 40: ...Getting Started To Set Up and Install the Switch in Your Network 1 10 ...
Страница 54: ...Selecting a Management Interface Advantages of Using ProCurve Manager or ProCurve Manager Plus 2 14 ...
Страница 70: ...Using the Menu Interface Where To Go From Here 3 16 ...
Страница 92: ...Using the ProCurve Web Browser Interface Contents Setting Fault Detection Policy 5 25 5 2 ...
Страница 160: ...Switch Memory and Configuration Automatic Configuration Update with DHCP Option 66 6 44 ...
Страница 288: ...Port Status and Configuration Uplink Failure Detection 10 42 ...
Страница 318: ...Port Trunking Outbound Traffic Distribution Across Trunked Links 11 30 ...
Страница 470: ...File Transfers Copying Diagnostic Data to a Remote Host USB Device PC or UNIX Workstation A 34 ...
Страница 487: ...Monitoring and Analyzing Switch Operation Status and Counters Data B 17 ...
Страница 518: ...Monitoring and Analyzing Switch Operation Traffic Mirroring B 48 ...
Страница 612: ...MAC Address Management Viewing the MAC Addresses of Connected Devices D 8 ...
Страница 616: ...Monitoring Resources When Insufficient Resources Are Available E 4 ...
Страница 620: ...Daylight Savings Time on ProCurve Switches F 4 ...
Страница 638: ...Network Out of Band Management OOBM Tasks G 18 ...
Страница 659: ...download to primary or secondary flash A 21 using to download switch software A 19 Index 19 ...
Страница 660: ...20 Index ...
Страница 661: ......