- 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
DNS Resolver
Operating Notes
■ Configuring another IP address for a priority that has already been
assigned to an IP address is not allowed. To replace one IP address at a
given priority level with another address having the same priority, you
must first use the no form of the command to remove the unwanted
address. Also, only one instance of a given server address is allowed in
the server list. Attempting to enter a duplicate of an existing entry at a
different priority level is not allowed. To change the priority of an existing
server address, use the no form of the command to remove the entry, then
re-enter the address with the new priority.
■ To change the position of an address already configured with priority x,
you must first use no ip dns server-address priority x < ip-addr > to remove
the address from the configuration, then use ip dns server-address priority
< ip-addr > to reconfigure the address with the new priority. Also, if the
priority to which you want to move an address is already used in the
configuration for another address, you must first use the no form of the
command to remove the current address from the target priority.
■ The DNS server(s) and domain configured on the switch must be
accessible to the switch, but it is not necessary for any intermediate
devices between the switch and the DNS server to be configured to
support DNS operation.
■ When multiple DNS servers are configured on the switch, they can
reside in the same domain or different domains.
■ A DNS configuration must include the IP address for a DNS server
that is able to resolve host names for the desired domain. If a DNS
server has limited knowledge of other domains, then its ability to
resolve DNS-compatible command requests is also limited.
■ If the DNS configuration includes a DNS server IP address but does
not also include a domain suffix, then any DNS-compatible
commands should include the target host’s fully qualified domain
name. Refer to Figure C-27 on page C-72.
■ Switch-Initiated DNS packets go out through the VLAN having the
best route to the DNS server, even if a Management VLAN has been
configured.
■ The DNS server address must be manually input. It is not automati-
cally determined via DHCP.
C-78