- 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
Configuring for Network Management Applications
LLDP (Link-Layer Discovery Protocol)
— Continued—
Type/Value Pairs (
CA-TYPE and CA-VALUE): This is a
series of data pairs, each composed of a location data
“type” specifier and the corresponding location data
for that type. That is, the first value in a pair is
expected to be the civic address “type” number (
CA-
TYPE
), and the second value in a pair is expected to
be the corresponding civic address data (
CA-VALUE).
For example, if the CA-TYPE for “city name” is “3”, then
the type/value pair to define the city of Paris is “
3
Paris
”. Multiple type/value pairs can be entered in any
order, although it is recommended that multiple
pairs be entered in ascending order of the
CA-
TYPE
.When an emergency call is placed from a
properly configured class 3 endpoint device to an
appropriate PSAP, the country code, device type, and
type/value pairs configured on the switch port are
included in the transmission. The “type” specifiers
are used by the PSAP to identify and organize the
location data components in an understandable
format for response personnel to interpret. A civic-
addr command requires a minimum of one type/
value pair, but typically includes multiple type/value
pairs as needed to configure a complete set of data
describing a given location.
CA-TYPE: This is the first
entry in a type/value pair, and is a number defining
the type of data contained in the second entry in the
type/value pair (
CA-VALUE). Some examples of CA-TYPE
specifiers include:
•3 = city
• 6 = street (name)
• 25 = building name
(Range: 0 - 255)
For a sample listing of
CA-TYPE specifiers, refer to table
13-4 on page 13-66.
CA-VALUE: This is the second entry in a type/value
pair, and is an alphanumeric string containing
the location information corresponding to the
immediately preceding
CA-TYPE entry. Strings
are delimited by either blank spaces, single
quotes (‘ ... ‘), or double quotes (“ ... “). Each string
should represent a specific data type in a set of
unique type/value pairs comprising the
description of a location, and each string must
be preceded by a CA-TYPE number identifying the
type of data in the string.
13-64