- Hewlett-Packard Switch User Manual
Table Of Contents
- HP ProCurve 2520 Switches Management and Configuration Guide
- Front Cover
- Title Page
- Copyright, Notices, & Publication Data
- Contents
- Feature Index
- 1.Getting Started
- 2.Selecting a Management Interface
- 3.Using the Menu Interface
- 4.Using the Command Line Interface (CLI)
- 5.Using the ProCurve Web Browser Interface
- 6.Switch Memory and Configuration
- 7.Interface Access and System Information
- 8.Configuring IP Addressing
- 9.Time Protocols
- 10.Port Status and Configuration
- Contents
- Overview
- Viewing Port Status and Configuring Port Parameters
- Menu: Port Status and Configuration
- CLI: Viewing Port Status and Configuring Port Parameters
- Customizing the Show Interfaces Command
- Viewing Port Utilization Statistics
- Viewing Transceiver Status
- Enabling or Disabling Ports and Configuring Port Mode
- Enabling or Disabling Flow Control
- Configuring a Broadcast Limit on the Switch
- Configuring ProCurve Auto-MDIX
- Web: Viewing Port Status and Configuring Port Parameters
- Using Friendly (Optional) Port Names
- 11.Power Over Ethernet (PoE) Operation
- 12.Port Trunking
- Contents
- Overview
- Port Trunk Features and Operation
- Trunk Configuration Methods
- Menu: Viewing and Configuring a Static Trunk Group
- CLI: Viewing and Configuring Port Trunk Groups
- Web: Viewing Existing Port Trunk Groups
- Trunk Group Operation Using LACP
- Trunk Group Operation Using the “Trunk” Option
- How the Switch Lists Trunk Data
- Outbound Traffic Distribution Across Trunked Links
- 13.Configuring for Network Management Applications
- Contents
- Using SNMP Tools To Manage the Switch
- LLDP (Link-Layer Discovery Protocol)
- Terminology
- General LLDP Operation
- Packet Boundaries in a Network Topology
- Configuration Options
- Options for Reading LLDP Information Collected by the Switch
- LLDP and LLDP-MED Standards Compatibility
- LLDP Operating Rules
- Configuring LLDP Operation
- LLDP-MED (Media-Endpoint-Discovery)
- Displaying Advertisement Data
- LLDP Operating Notes
- LLDP and CDP Data Management
- A.File Transfers
- B.Monitoring and Analyzing Switch Operation
- Contents
- Overview
- Status and Counters Data
- Menu Access To Status and Counters
- General System Information
- Task Monitor—Collecting Processor Data
- Switch Management Address Information
- Port Status
- Viewing Port and Trunk Group Statistics and Flow Control Status
- Viewing the Switch’s MAC Address Tables
- Spanning Tree Protocol (MSTP) Information
- Internet Group Management Protocol (IGMP) Status
- VLAN Information
- Web Browser Interface Status Information
- Interface Monitoring Features
- Locating a Device
- C.Troubleshooting
- Contents
- Overview
- Troubleshooting Approaches
- Browser or Telnet Access Problems
- Unusual Network Activity
- General Problems
- 802.1Q Prioritization Problems
- IGMP-Related Problems
- LACP-Related Problems
- Port-Based Access Control (802.1X)-Related Problems
- QoS-Related Problems
- Radius-Related Problems
- Spanning-Tree Protocol (MSTP) and Fast-Uplink Problems
- SSH-Related Problems
- TACACS-Related Problems
- TimeP, SNTP, or Gateway Problems
- VLAN-Related Problems
- Fan Failure
- Using the Event Log for Troubleshooting Switch Problems
- Debug/Syslog Operation
- Debug/Syslog Messaging
- Debug/Syslog Destination Devices
- Debug/Syslog Configuration Commands
- Configuring Debug/Syslog Operation
- Debug Command
- Logging Command
- Adding a Description for a Syslog Server
- Adding a Priority Description
- Configuring the Severity Level for Event Log Messages Sent to a Syslog Server
- Operating Notes for Debug and Syslog
- Diagnostic Tools
- Viewing Switch Configuration and Operation
- Restoring the Factory-Default Configuration
- Restoring a Flash Image
- DNS Resolver
- D.MAC Address Management
- E.Daylight Savings Time on ProCurve Switches
- F.Power-Saving Features
- Index
- Notices & Publication Data
Troubleshooting
Debug/Syslog Operation
Logging Command
At the global configuration level, the logging command allows you to enable
debug logging on specified Syslog servers and select a subset of Event Log
messages to send for debugging purposes according to:
■ Severity level
■ System module
By specifying both a severity level and system module, you can use both
configured settings to filter the Event Log messages you want to use to
troubleshoot switch or network error conditions.
Caution After you configure a Syslog server and a severity level and/or system module
to filter the Event Log messages that are sent, if you save these settings to the
startup configuration file by entering the write memory command, these debug
and logging settings are automatically re-activated after a switch reboot or
power recycle. The debug settings and destinations configured in your
previous troubleshooting session will then be applied to the current session,
which may not be desirable.
After a reboot, messages remain in the Event Log and are not deleted.
However, after a power recycle, all Event Log messages are deleted.
If you configure a severity level and/or system module to temporarily filter
Event Log messages, be sure to reset the values to their default settings by
entering the no form of the following commands to ensure that Event Log
messages of all severity levels and from all system modules are sent to
configured Syslog servers:
ProCurve(config)# no logging severity < debug | major | error | warning | info>
ProCurve(config)# no logging system-module < system-module >
Configuring a Syslog Server
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.
To use the Syslog feature, you must install and configure a Syslog server
application on a networked host accessible to the switch. Refer to the docu-
mentation for the Syslog server application for instructions.
To configure a Syslog server, use the logging < syslog-ip-addr > command as
described below.
C-41