Page 1
9304m
9308m
9315m
9408sl
ProCurve Routing Switches
Software versions 07.8.00a (9300 series)
and 01.0.02 (9408sl)
Diagnostic Guide
www.procurve.com
Page 2
Page 3
Diagnostic Guide
for
ProCurve 9300/9400 Series
Routing Switches
Software versions 07.8.00a (9300 Series)
and 01.0.02 (9408sl)
Page 4
©
Copyright 2000, 2003, 2005 Hewlett-Packard
Development Company, L.P. The information
contained herein is subject to change without
notice.
Publication number
5990-6032
June 2005
Applicable Products
ProCurve 9304M (J4139A)
ProCurve 9308M (J4138A)
ProCurve 9315M (J4874A)
ProCurve 9408sl (J8680A)
Trademark Credits
®
Microsoft
, Windows®, and Windows NT® are US
registered trademarks of Microsoft Corporation.
Disclaimer
The information contained in this document is
subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO
WARRANTY OF ANY KIND WITH REGARD TO
THIS MATERIAL, INCLUDING BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. Hewlett-Packard shall
not be liable for errors contained herein or for
incidental or consequential damages in connection
with the furnishing, performance or use of this
material.
The only warranties for HP products and services
are set forth in the express warranty statements
accompanying such products and services. Nothing
herein should be construed as constituting an
additional warranty. HP shall not be liable for
technical or editorial errors or omissions contained
herein.
Hewlett-Packard assumes no responsibility for the
use or reliability of its software on equipment that is
not furnished by Hewlett-Packard.
A copy of the specific warranty terms applicable to
your HP product and replacement parts can be
obtained from your HP Sales and Service Office or
authorized dealer.
Warranty
See the Customer Support/Warranty booklet
included with the product.
A copy of the specific warranty terms applicable to
your Hewlett-Packard products and replacement
parts can be obtained from your HP Sales and
Service Office or authorized dealer.
Safety Considerations
Prior to the installation and use of this product,
review all safety markings and instructions.
Instruction Manual Symbol.
If the product is marked with the above symbol, refer
to the product manual to protect the product from
damage.
WARNING Denotes a hazard that can cause injury.
CAUTION Denotes a hazard that can damage
equipment or data.
Do not proceed beyond a WARNING or CAUTION
notice until you have understood the hazard and
have taken appropriate precautions.
Use of control, adjustments or performance
procedures other than those specified herein may
result in hazardous radiation exposure.
Grounding
This product provides a protective earthing terminal.
There must be an uninterrupted safety earth ground
from the main power source to the product’s input
wiring terminals, power cord or supplied power cord
set. Whenever it is likely that the protection has
been impaired, disconnect the power cord until the
ground has been restored.
If your LAN covers an area served by more than one
power distribution system, be sure their safety
grounds are securely interconnected.
LAN cables may occasionally be subject to
hazardous transient voltages (such as lightning or
disturbances in the electrical utilities power grid).
Handle exposed metal components of the network
with caution.
For more safety information, see the Installation and
Basic Configuration Guide for ProCurve 9300 Series
Routing Switches and the Quick Start Guide for your
HP 9300M Routing Switch product.
Servicing
There are no user-serviceable parts inside the userinstallable modules comprising the product. Any
servicing, adjustment, maintenance or repair must
be performed only by service-trained personnel.
June 2005 ii
Page 5
Contents
Chapter 1
Getting Started ........................................................................................ 1-1
Introduction ...............................................................................................................................................1-1
Software Versions Covered ......................................................................................................................1-1
Audience ...................................................................................................................................................1-1
Conventions ..............................................................................................................................................1-1
Terminology ..............................................................................................................................................1-2
Support and Warranty Information ...........................................................................................................1-2
Related Publications .................................................................................................................................1-2
Chapter 2
Using Diagnostic Commands ................................................................ 2-1
Using an ACL to Filter Debug Output .......................................................................................................2-2
Chapter 3
HP Diagnostic Command Reference..................................................... 3-1
About the Diagnostic Commands .............................................................................................................3-1
D
IAGNOSTIC COMMANDS
Diagnostic Commands – Syntax Descriptions ..........................................................................................3-5
.....................................................................................................................3-1
Chapter 4
Using the Backplane Debugging Commands ...................................... 4-1
Chapter 5
Changing CAM Partitions....................................................................... 5-1
CAM Overview ..........................................................................................................................................5-1
CAM P
CAM P
CAM P
ARTITIONING ON STANDARD MODULES
ARTITIONING ON ENHANCED PERFORMANCE MODULES
ARTITIONING ON
10 G
IGABIT ETHERNET MODULES
.......................................................................................5-2
.....................................................................5-2
...............................................................5-2
June 2005 iii
Page 6
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Using the CLI to Configure CAM Partitioning ...........................................................................................5-2
Displaying CAM Partitioning Information ..................................................................................................5-4
Configuring CAM Aggregation ..................................................................................................................5-7
CAM S
UPPORT FOR DIRECTLY CONNECTED ROUTES
............................................................................5-7
June 2005 iv
Page 7
Organization of Product Documentation
NOTE: HP periodically updates the ProCurve 9300/9400 Series Routing Switch documentation. For the latest
version of any of these publications, visit the ProCurve website at:
http://www.procurve.com
Click on Technical Support, then Product manuals.
NOTE: All manuals listed below are available on the ProCurve website, and also on the Documentation CD
shipped with your HP product.
Installation and Basic Configuration Guide for ProCurve 9300 Series Routing Switches
This is an electronic (PDF) guide containing product safety and EMC regulatory statements as well as installation
and basic configuration information, and software and hardware specifications.
Topics Specific to the 9300 Series Routing Switches
• Product mounting instructions
• Module installation
• Basic access and connectivity configuration (passwords, IP addresses)
• Redundant management module commands and file systems
• Cooling system commands and information
• Basic software feature configuration (SNMP, clock, mirror/monitor ports)
• Configuring for these features:
• Uni-Directional Link Detection (UDLD)
• Metro Ring Protocol (MRP)
• Virtual Switch Redundancy Protocol (VSRP)
• GVRP (dynamic VLANs)
• Software update instructions
• Hardware specs
• Software specs (e.g. RFC support, IEEE compliance)
June 2005 vii
Page 8
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Information on Configuring Features for 9300 Series and 9408sl Routing Switches
• Port settings
• VLANS
• Trunks
• Spanning Tree Protocol
• Syslog
Quick Start Guide for ProCurve 9300 Series Routing Switches
This is a printed guide you can use as an easy reference to the installation and product safety information needed
for out-of-box setup, plus the general product safety and EMC regulatory statements of which you should be aware
when installing and using a Routing Switch.
Installation and Basic Configuration Guide for the ProCurve 9408sl Routing Switch
This is a printed guide that describes the ProCurve 9408sl and provides procedures for installing modules and AC
power supplies into the ProCurve 9408sl, cabling the 10-Gigabit Ethernet interface ports, and performing a basic
configuration of the software.
Topics Specific to the 9408sl Routing Switch
• Product overview and architecture
• Product mounting instructions
• Module installation
• Basic access and connectivity configuration (passwords, IP addresses)
• Management Module redundancy and file systems
• Interacting with the cooling system, switch fabric module, and interface modules
• Basic software feature configuration (SNMP, clock, mirror/monitor ports)
• Hardware maintenance instructions
• Software update instructions
• Hardware specs
• Safety and regulatory statements
• Software specs (e.g. RFC support, IEEE compliance)
Advanced Configuration and Management Guide for ProCurve 9300/9400 Series Routing Switches
This is an electronic (PDF) guide that contains advanced configuration information for routing protocols and
Quality of Service (QoS). In addition, appendixes in this guide contain reference information for network
monitoring, policies, and filters.
Information on Configuring Features
• Quality of Service (QoS)
• Access Control Lists (ACLs)
• Rate limiting
• IPv4 routing
• RIP
• IP Multicast
• OSPF
• BGP4
• Multi-protocol BGP (MBGP)
• Network Address Translation (NAT)
viii June 2005
Page 9
Organization of Product Documentation
• VRRP and VRRPE (VRRP extended)
• IPX routing
• AppleTalk routing
• Route health injection
• RMON, NetFlow, and sFlow monitoring
IPv6 Configuration Guide for the ProCurve 9408sl Routing Switch
This is an electronic (PDF) guide that describes the IPv6 software and features. It provides conceptual information
about IPv6 addressing and explains how to configure basic IPv6 connectivity and the IPv6 routing protocols. The
software procedures explain how to perform tasks using the CLI.
Command Line Interface Reference for ProCurve 9300/9400 Series Routing Switches
This is an electronic (PDF) guide that provides a dictionary of CLI commands and syntax.
Security Guide for ProCurve 9300/9400 Series Routing Switches
This is an electronic (PDF) guide that provides procedures for securing management access to HP devices and for
protecting against Denial of Service (DoS) attacks.
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
This is an electronic (PDF) guide that describes the diagnostic commands available on HP devices. The software
procedures show how to perform tasks using the Command Line Interface (CLI).
Removing and Installing XENPAK Optics
This is a printed instruction sheet describing the correct preparation and procedure for removing and installing
XENPAK optics on the 10-Gigabit Ethernet modules.
Read Me First
The "Read Me First" document, printed on bright yellow paper, is included with every chassis and module. It
contains an overview of software release information, a brief "Getting Started" section, an included parts list,
troubleshooting tips, operating notes, and other information that is not included elsewhere in the product
documentation. It also includes:
• software update instructions
• operating notes for this release
Release Notes
These documents describe features and other information that becomes available between revisions of the main
product guides. New releases of such documents will be available on HP's ProCurve website. To register to
receive email notice from HP when a new software release is available, visit:
http://www.procurve.com
In the "My Procurve" box on the right, click on "Register".
Product Documentation CD: A Tool for Finding Specific Information and/or Printing Selected Pages
This CD is shipped with your ProCurve Routing Switch product and provides the following:
• A README file describing the CD contents and use, including easy instructions on how to search the book
files for specific information
• A Contents file to give you easy access to the documentation on the CD
• Separate PDF files of the individual chapters and appendixes in the major guides, enabling you to easily print
individual chapters, appendixes, and selected pages
• Single PDF files for each of the major guides, enabling you to use the Adobe® Acrobat® Reader to easily
search for detailed information
• Additional files. These may include such items as additional Read Me files and release notes.
June 2005 ix
Page 10
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
June 2005 x
Page 11
Introduction
This guide describes diagnostic commands for the following:
• ProCurve Routing Switch 9315M
• ProCurve Routing Switch 9308M
• ProCurve Routing Switch 9304M
• ProCurve Routing Switch 9408sl
Chapter 1
Getting Started
Software Versions Covered
This edition describes software release 07.8.00a for the following ProCurve products:
• 9304M
• 9308M
• 9315M
This edition also describes software release 01.0.02 for the ProCurve 9408sl Routing Switch.
NOTE: The software release for the 9408sl is 02.1.00. See the Release Notes for the most current information,
which supercedes the information in this guide.
Audience
This manual is designed for system administrators with a working knowledge of Layer 2 and Layer 3 switching and
routing.
If you are using a ProCurve Routing Switch, you should be familiar with the following protocols if applicable to your
network—IP, RIP, OSPF, BGP4, IGMP, PIM, DVMRP, IPX, AppleTalk, and VRRP.
Conventions
This guide uses the following typographical conventions:
Italic highlights the title of another publication and occasionally emphasizes a word or phrase.
June 2005 1 - 1
Page 12
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Bold highlights a CLI command.
Bold Italic highlights a term that is being defined.
Underline
Capitals highlights field names and buttons that appear in the Web management interface.
NOTE: A note emphasizes an important fact or calls your attention to a dependency.
WAR NING: A warning calls your attention to a possible hazard that can cause injury or death.
CAUTION: A caution calls your attention to either a possible hazard that can damage equipment or an action
that can produce an operating problem or other unwanted results.
highlights a link on the Web management interface.
Terminology
The following table defines basic product terms used in this guide.
Term
chassis
or
Chassis device
EP
and
Standard
Routing Switch
or
router
Switch
ProCurveRS#
Definition
A Routing Switch that accepts optional modules or power supplies. The
ProCurve 9304M, 9308M, 9315M, and 9408sl Routing Switches are Chassis
devices.
9300 Series Chassis devices can be EP or Standard devices, depending on
whether the management module is an EP or Standard module.
A Layer 2 and Layer 3 device that switches and routes network traffic. The
term router is sometimes used in this document in descriptions of a Routing
Switch’s Layer 3 routing protocol features.
A Layer 2 device that switches network traffic.
An example Command Line Interface (CLI) prompt. Actual prompts show
the product number for the device, such as HP9304#.
Support and Warranty Information
Refer to Support is as Close as the World Wide Web, which was shipped with your ProCurve Routing Switch.
Related Publications
Refer to the “Organization of Product Documentation” on page vii for a list of publications for your ProCurve
Routing Switch.
1 - 2 June 2005
Page 13
Chapter 2
Using Diagnostic Commands
The HP diagnostic commands are tools that you can use to gather information about HP devices. The diagnostic
commands start with de, debug, mm, phy, and ptrace.
de Displays information about CPU buffer allocations.
debug Reports debugging information that you can use to resolve configuration problems.
mm Displays the contents of a specified address on every module. (Available on Chassis devices only)
phy Displays information about PHY (hardware) registers for a specified port.
ptrace Displays information on the console when a specified kind of packet is transmitted or received.
In addition, the show ip bgp debug command reports information about resource allocation and errors in a BGP
configuration.
These commands are available in Privileged EXEC mode on the Command Line Interface (CLI) only. You cannot
use them in the device’s Web management interface. For complete syntax information for the diagnostic
commands, see the next chapter, “HP Diagnostic Command Reference” on page 3-1.
Many of the diagnostic commands are meant to be used in conjunction with calls to HP technical support. If you
report a problem, the support engineer may ask you to execute one or more of the diagnostic commands
described in this guide. Some of the diagnostic commands report information about internal hardware settings
and registers that is relevant primarily to HP engineering staff. Consequently, this information is not described in
detail here.
The following table lists some of the tasks you can perform using the diagnostic commands:
Task
Tracing packets ptrace
Displaying AppleTalk information debug appletalk
Displaying BGP information
Relevant Commands
ptrace appletalk
debug ip bgp
show ip bgp debug
Displaying IPv6 information
Displaying OSPF packet information
June 2005 2 - 1
debug ipv6
debug ip ospf packet
Page 14
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Task
Displaying VRRP packet information
Displaying BPDU packet information
Recovering a frozen console
Displaying CPU buffer information
Reading hardware registers
Relevant Commands
debug ip vrrp packet
debug spanning
dm uart
de
debug serial state
phy
Using an ACL to Filter Debug Output
You can use an ACL to filter output from debug commands. For example, you can set up an ACL that permits
packets from an IP address, then apply that ACL to a debug command. When you start the debug command,
only messages related to that IP address are displayed in the output for that command.
The following example limits output from the debug ip tcp packet command to only messages related to incoming
packets from 10.10.10.10.
First, set up an ACL to permit packets from host 10.10.10.10. For example:
ProCurveRS(config)# access-list 100 permit ip host 10.10.10.10 any
Then apply this ACL to the debug ip tcp command. You can specify no more than one ACL per protocol.
ProCurveRS# debug ip tcp acl 100
Syntax: debug ip <protocol> acl <acl-id>
Then enter the debug ip tcp packet command to start generating debug output.
ProCurveRS# debug ip tcp packet
Syntax: [no] debug ip tcp packet
Only messages related to packets inbound from 10.10.10.10 are displayed in the output for the debug ip tcp
packet command. To display messages related to outbound packets sent to 10.10.10.10, add another entry to the
ACL, specifying 10.10.10.10 as the destination host. For example:
ProCurveRS(config)# access-list 100 permit ip any host 10.10.10.10
The show debug command displays ACLs applied to debug commands. For example:
ProCurveRS# show debug
Debug message destination: Console
TCP:
TCP: packet debugging is on
TCP: Display is bound to ACL 100
Syntax: show debug
2 - 2 June 2005
Page 15
Chapter 3
HP Diagnostic Command Reference
This chapter lists and provides syntax and examples for the CLI de, debug, mm, phy, and ptrace commands.
About the Diagnostic Commands
You can enter the diagnostic commands at the Privileged EXEC CLI level. The following tables list the diagnostic
commands and contains page references to descriptions of each command.
Diagnostic Commands
Unless otherwise noted, the following diagnostic commands are supported on Routing Switches that support IPv6
de 3-5
debug all 3-6
debug appletalk 3-6
debug destination 3-6
debug gvrp packets 3-7
debug ip arp 3-7
debug ip bgp <address> updates 3-8
debug ip bgp dampening 3-8
debug ip bgp events 3-9
debug ip bgp in 3-9
debug ip bgp keepalives 3-10
debug ip bgp out 3-10
debug ip bgp updates 3-10
debug ip dvmrp detail 3-11
.
debug ip dvmrp in 3-11
debug ip dvmrp out 3-11
June 2005 3 - 1
Page 16
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
debug ip dvmrp pruning 3-12
debug ip icmp events 3-12
debug ip icmp packets 3-12
debug ip igmp 3-13
debug ip msdp alarms 3-13
debug ip msdp events 3-13
debug ip msdp message 3-14
debug ip nat icmp 3-14
debug ip nat udp 3-14
debug ip nat tcp 3-15
debug ip nat transdata 3-15
debug ip ospf adj 3-15
debug ip ospf events 3-16
debug ip ospf flood 3-16
debug ip ospf lsa-generation 3-16
debug ip ospf packet 3-17
debug ip ospf retransmission 3-18
debug ip ospf spf 3-18
debug ip pim <address> 3-19
debug ip pim events 3-19
debug ip rip 3-20
debug ip rip database 3-20
debug ip rip events 3-21
debug ip rip trigger 3-22
debug ip ssh 3-22
debug ip tcp <address> 3-23
debug ip tcp driver 3-23
debug ip tcp memory 3-24
debug ip tcp packet 3-24
debug ip tcp sack 3-25
debug ip tcp transactions 3-25
debug ip udp 3-26
debug ip vrrp events 3-26
debug ip vrrp packet 3-26
3 - 2 June 2005
Page 17
HP Diagnostic Command Reference
debug ipv6 address 3-27
debug ipv6 cache 3-28
debug ipv6 icmp 3-28
debug ipv6 nd 3-28
debug ipv6 ospf ism 3-29
debug ipv6 ospf ism-events 3-29
debug ipv6 ospf ism-status 3-29
debug ipv6 ospf lsa 3-30
debug ipv6 ospf lsa-flooding 3-30
debug ipv6 ospf lsa-generation 3-31
debug ipv6 ospf lsa-install 3-31
debug ipv6 ospf lsa-maxage 3-32
debug ipv6 ospf lsa-refresh 3-32
debug ipv6 ospf nsm 3-33
debug ipv6 ospf nsm-events 3-34
debug ipv6 ospf nsm-status 3-34
debug ipv6 ospf packet 3-35
debug ipv6 ospf packet-dd 3-35
debug ipv6 ospf packet-hello 3-36
debug ipv6 ospf packet-lsa-ack 3-36
debug ipv6 ospf packet-lsa-req 3-37
debug ipv6 ospf packet-lsa-update 3-38
debug ipv6 ospf route 3-38
debug ipv6 ospf route-calc-external 3-39
debug ipv6 ospf route-calc-inter-area 3-40
debug ipv6 ospf route-calc-intra-area 3-40
debug ipv6 ospf route-calc-spf 3-41
debug ipv6 ospf route-calc-transit 3-41
debug ipv6 ospf route-install 3-41
debug ipv6 packet 3-42
debug ipv6 ra 3-42
debug ipv6 rip events 3-43
debug ipv6 rip receive 3-43
debug ipv6 rip transmit 3-43
June 2005 3 - 3
Page 18
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
debug ipv6 routing 3-44
debug spanning 3-44
ipv6 debug route-table disable-cache
ipv6 debug route-table main
ipv6 debug route-table rip
mm 3-45
phy 3-46
ptrace aaa 3-48
ptrace appletalk aarp 3-48
ptrace appletalk aep 3-48
ptrace appletalk nbp 3-49
ptrace appletalk none 3-49
ptrace appletalk rtmp 3-49
ptrace appletalk states 3-49
ptrace appletalk zip 3-50
ptrace arp 3-50
ptrace bootp 3-50
ptrace dvmrp graft 3-50
3-45
3-45
3-45
ptrace dvmrp graft-ack 3-50
ptrace dvmrp mcache 3-50
ptrace dvmrp message 3-51
ptrace dvmrp none 3-51
ptrace dvmrp probe 3-51
ptrace dvmrp prune 3-51
ptrace dvmrp route-table 3-51
ptrace icmp 3-52
ptrace igmp 3-52
ptrace ip 3-52
ptrace none 3-52
ptrace ospf 3-52
ptrace pim fcache 3-52
ptrace pim mcache 3-53
ptrace pim message 3-53
ptrace pim none 3-53
3 - 4 June 2005
Page 19
HP Diagnostic Command Reference
ptrace ppp 3-53
ptrace rarp 3-53
ptrace rip 3-54
ptrace snmp 3-54
ptrace switch none 3-54
ptrace switch stp 3-54
ptrace tcp 3-54
ptrace telnet 3-54
ptrace term 3-55
ptrace tftp 3-55
ptrace udp 3-55
show ip bgp debug 3-55
show debug 3-57
Diagnostic Commands – Syntax Descriptions
The following commands are available at the Privileged EXEC level of the CLI for HP devices, except where noted.
de
Displays information about CPU buffer allocations.
EXAMPLE:
ProCurveRS# de
GADDR = 043a1588 TOT_IN = 260 TOT_OUT = 259
CPU_R = 85 GET_B = 175
SNOOP_M = 175 SNOOP = 28
FREE_B = 56 FREE_B_M = 0
Dram buf = 63 No-bufs = 0
The following table describes the output from the de command:
Table 3.1: Output from the de command
This Field...
GADDR
TOT_IN
Displays...
Address of g_sw_sys
Total number of CPU buffer allocations.
TOT_OUT
CPU_R
GET_B
SNOOP
June 2005 3 - 5
Total number of CPU buffer deallocations.
CPU read queue buffers.
CPU buffers allocated by BM_GET_BUFFER.
Number of snoop operations.
Page 20
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Table 3.1: Output from the de command (Continued)
This Field... Displays...
SNOOP_M Number of management snoop operations.
FREE_B Number of buffers freed using BM_FREE_BUFFER or BM_FREE_BUFFER_MGMT.
FREE_B_M Additional counter indicating number of buffers freed using just
BM_FREE_BUFFER_MGMT.
Dram buf Amount of available packet processing memory. This number should always be close to
64.
No-bufs Number of times the CPU was unsuccessful in obtaining packet processing memory. This
number should be 0 under normal operation.
Syntax: de
Possible values: N/A
Default value: N/A
debug all
Activates all debugging functions on the device. The no form of the command deactivates all debugging functions.
NOTE: Activating all debugging functions can generate a lot of output and greatly slow the operation of the
device.
EXAMPLE:
ProCurveRS# debug all
Syntax: [no] debug all
Possible values: N/A
Default value: N/A
debug appletalk
Displays the number of timer events dropped and insufficient zone allocations in an Appletalk configuration.
EXAMPLE:
ProCurveRS# debug appletalk
Timer event Dropped: 0
Insufficient zone allocation: 0
Syntax: [no] debug appletalk
Possible values: N/A
Default value: N/A
debug destination
Specifies a destination for debugging output. You can send debugging output to the console, Syslog buffer, a
Telnet session, or an SSH session.
EXAMPLE:
ProCurveRS# debug destination ssh 1
Syntax: debug destination console | logging | telnet <num> | ssh <num>
Possible values: Specify one of the following destinations:
console Directs debugging output to the system console.
3 - 6 June 2005
Page 21
HP Diagnostic Command Reference
logging Directs debugging output to the Syslog buffer and also to the Syslog server, if configured.
telnet <num> Directs debugging output to the specified Telnet session.
ssh <num> Directs debugging output to the specified SSH session.
Default value: By default, debugging output is sent to the Console.
debug gvrp packets
Displays GVRP information.
EXAMPLE:
ProCurveRS# debug gvrp packets
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug gvrp packets command.
GVRP: Port 2/1 RCV
GVRP: 0x2095ced4: 01 80 c2 00 00 21 00 e0 52 ab 87 40 00 28 42 42
GVRP: 0x2095cee4: 03 00 01 01 04 02 03 e9 04 01 03 eb 04 01 03 ec
GVRP: 0x2095cef4: 04 01 03 ef 04 01 03 f1 04 01 05 dd 04 01 09 cb
GVRP: 0x2095cf04: 04 01 0f a1 00 00
GVRP: Port 2/1 TX
GVRP: 0x207651b8: 01 80 c2 00 00 21 00 04 80 2c 0e 20 00 3a 42 42
GVRP: 0x207651c8: 03 00 01 01 02 00 04 05 03 e9 04 05 03 eb 04 05
GVRP: 0x207651d8: 03 ec 04 05 03 ef 04 05 03 f1 04 05 05 dd 04 05
GVRP: 0x207651e8: 09 cb 04 05 0f a1 04 02 00 02 04 01 00 07 04 01
GVRP: 0x207651f8: 00 09 04 01 00 0b 00 00
GVRP: Port 2/1 TX
GVRP: 0x207651b8: 01 80 c2 00 00 21 00 04 80 2c 0e 20 00 18 42 42
GVRP: 0x207651c8: 03 00 01 01 04 02 00 02 04 01 00 07 04 01 00 09
GVRP: 0x207651d8: 04 01 00 0b 00 00
Syntax: [no] debug gvrp packets
Possible values: N/A
Default value: N/A
debug ip arp
Displays information about ARP messages sent and received by the device.
EXAMPLE:
ProCurveRS# debug ip arp
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug arp command.
[A] [B] [C] [D] [E]
IP ARP: rcvd 192.168.4.56 000034ab67bd , 192.168.4.32 00cdfeba23ab 9
IP ARP: sent 192.168.4.32 000034ab67bd , 192.168.4.4 00cdfeba23ab 9
June 2005 3 - 7
Page 22
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Table 3.2 describes the contents of debug ip arp messages. The letters in brackets do not appear in the actual
output.
Table 3.2: Output from the debug ip arp command
This Field...
rcvd or sent
[A] 192.168.4.56
[B] 000034ab67bd
[C] 192.168.4.32
[D] 00cdfeba23ab
[E] 9
Syntax: [no] debug ip arp
Possible values: N/A
Default value: N/A
debug ip bgp <address> updates
Displays BGP update information for a specific neighbor.
EXAMPLE:
ProCurveRS# debug ip bgp 1.1.1.192 updates
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip bgp <address> updates command.
Displays...
Indicates whether the packet was sent or received.
Source IP address.
Source MAC address.
Destination IP address.
Destination MAC address.
Por t number.
BGP: 1.1.1.192 rcvd UPDATE about 1.1.1.0/24 -- withdrawn
BGP: 1.1.1.192 rcvd UPDATE 5.5.5.0/24
BGP: 1.1.1.192 rcvd UPDATE about 5.5.5.0/24 -- withdrawn
Syntax: [no] debug ip bgp <ip-addr> updates
Possible values: Valid IP address
Default value: N/A
debug ip bgp dampening
Displays BGP dampening information
EXAMPLE:
ProCurveRS# debug ip bgp dampening
3 - 8 June 2005
Page 23
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip bgp dampening command.
BGP: (1.1.1.1) dampening - route down 3.3.3.0/24
Old Dampening: state was <*>, reuse_list_index=38, penalty=929, time=48,
flaps=1
New state <h>, penalty=1893, reuse_list_index=43, offset=44
BGP: (1.1.1.1) Dampening - Route 3.3.3.0/24 up
State was <h>, penalty=1893, time=390, flaps=2
New state <*> penalty=1396, reuse_list_index=82, curr_offset=83
BGP: (1.1.1.100) Free Dampening 3.3.3.0/24
Total number of IP routes: 1
Start index: 1 B:BGP D:Connected R:RIP S:Static O:OSPF *:Candidate default
Destination NetMask Gateway Port Cost Type
1
Syntax: [no] debug ip bgp dampening
Possible values: N/A
Default value: N/A
1.1.1.0 255.255.255.0 0.0.0.0 1 1 D
debug ip bgp events
Displays messages when BGP-related events occur. BGP-related events include starting or stopping a peer and
opening or closing a BGP TCP connection.
EXAMPLE:
ProCurveRS# debug ip bgp events
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip bgp events command.
BGP: 3.3.3.1 start peer
BGP: 3.3.3.1 stop peer
BGP: 3.3.3.1 BGP-TCP Connection opened
BGP: 3.3.3.1 TCP_OPEN done
BGP: 3.3.3.1 keep alive timer expired
Syntax: [no] debug ip bgp events
Possible values: N/A
Default value: N/A
debug ip bgp in
Displays BGP inbound information.
EXAMPLE:
ProCurveRS# debug ip bgp in
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip bgp in command.
BGP: rcvd message KEEPALIVE_MESSAGE from peer 1.1.1.100, length (incl. header) 19
BGP: rcvd message UPDATE from peer 1.1.1.100, length (incl. header) 27
BGP: rcvd message OPEN_MESSAGE from peer 1.1.1.100, length (incl. header) 29
Syntax: [no] debug ip bgp in
June 2005 3 - 9
Page 24
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Possible values: N/A
Default value: N/A
debug ip bgp keepalives
Displays BGP keepalive information
EXAMPLE:
ProCurveRS# debug ip bgp keepalives
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip bgp keepalives command.
BGP: send keepalives to peer 3.3.3.100
Syntax: [no] debug ip bgp keepalives
Possible values: N/A
Default value: N/A
debug ip bgp out
Displays BGP outbound information.
EXAMPLE:
ProCurveRS# debug ip bgp out
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip bgp out command.
BGP: send UPDATE message to peer 1.1.1.100, length (incl. header) 19
BGP: send KEEPALIVE_MESSAGE message to peer 1.1.1.100, length (incl. header) 19
BGP: send OPEN_MESSAGE message to peer 1.1.1.100, length (incl. header) 19
Syntax: [no] debug ip bgp out
Possible values: N/A
Default value: N/A
debug ip bgp updates
Displays BGP update information for all neighbors or those specified in an IP prefix list.
EXAMPLE:
ProCurveRS# debug ip bgp updates
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip bgp updates command.
BGP: 3.3.3.100 rcvd UPDATE 4.4.4.0/24
BGP: 3.3.3.100 rcvd UPDATE about 4.4.4.0/24 -- withdrawn
Syntax: [no] debug ip bgp updates [<prefix-list>]
Possible values: The <prefix-list> parameter specifies an IP prefix list. Only the routes permitted by the prefix list
are displayed.
Default value: N/A
3 - 10 June 2005
Page 25
HP Diagnostic Command Reference
debug ip dvmrp detail
Displays detailed messages about DVMRP events, including sending reports, updating the forwarding table, and
inserting table entries.
EXAMPLE:
ProCurveRS# debug ip dvmrp detail
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip dvmrp detail command.
DVMRP: send report DVMRP report to 224.0.0.4
DVMRP: send report DVMRP report to 2.2.2.1
DVMRP: updating fwd table due to a child is deleted
DVMRP: updating fwd table due to a entry is deleted
DVMRP: updating fwd table due to adding entry
DVMRP: insert entry source 1.1.1.0 group 239.255.162.2
Syntax: [no] debug ip dvmrp detail
Possible values: N/A
Default value: N/A
debug ip dvmrp in
Displays messages related to inbound DVMRP information.
EXAMPLE:
ProCurveRS# debug ip dvmrp in
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip dvmrp in command.
DVMRP: accept report. src ip 2.2.2.1 dest ip 224.0.0.4 group 0.6.5.3 port 7
DVMRP: accept probe. src ip 2.2.2.1 dest ip 224.0.0.4 group 0.6.5.3 port 7
DVMRP: accept prune. src ip 2.2.2.1 dest ip 2.2.2.100 group 0.6.5.3 port 7
Syntax: [no] debug ip dvmrp in
Possible values: N/A
debug ip dvmrp out
Displays messages related to outbound DVMRP information.
EXAMPLE:
ProCurveRS# debug ip dvmrp out
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip dvmrp out command.
DVMRP: send report. src ip 2.2.2.1 dest ip 224.0.0.4
DVMRP: send probe. src 2.2.2.1 dest 2.2.2.100 port 7
Syntax: [no] debug ip dvmrp out
Possible values: N/A
June 2005 3 - 11
Page 26
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
debug ip dvmrp pruning
Displays DVMRP pruning information.
EXAMPLE:
ProCurveRS# debug ip dvmrp pruning
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip dvmrp pruning command.
DVMRP: delete entry 00000003 idx 273
DVMRP: delete all entries for source 1.1.1.0
DVMRP: update fwd table by adding group 239.255.162.1 router 3.3.3.100 interface 9
DVMRP: update fwd table by adding group 239.255.162.2 router 3.3.3.100 interface 9
DVMRP: update fwd table by deleting group 239.255.162.1 router 3.3.3.100 interface 9
DVMRP: dvmrp delete prune state: Int6 Index 255 Prune Index 3
Syntax: [no] debug ip dvmrp pruning
Possible values: N/A
Default value: N/A
debug ip icmp events
Displays messages when ICMP events, including sending and receiving ICMP echo requests, occur.
EXAMPLE:
ProCurveRS# debug ip icmp events
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip icmp events command.
ICMP: rcvd echo request packet of length 40 from 1.1.1.2
ICMP: send echo request packet of length 60 to 1.1.1.2
Syntax: [no] debug ip icmp events
Possible values: N/A
Default value: N/A
debug ip icmp packets
Displays information related to ICMP packets sent or received on the device.
EXAMPLE:
ProCurveRS# debug ip icmp packets
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip icmp packets command.
ICMP:dst (1.2.3.4), src (0.0.0.0) echo request type
Syntax: [no] debug ip icmp packets
Possible values: N/A
Default value: N/A
3 - 12 June 2005
Page 27
HP Diagnostic Command Reference
debug ip igmp
Displays IGMP related information.
EXAMPLE:
ProCurveRS# debug ip igmp
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip igmp command.
IGMP: send message to 1.1.1.1 port ethernet 1 type 17 size 28
IGMP: send query to all port. type 17 port ethernet 7 ver 2
IGMP: rcvd v2 membership report from 1.1.1.2 group address 239.255.162.1 port ethernet
1 size 8
IGMP: rcvd membership query from 2.2.2.100 group address 0.0.0.0 port ethernet 7 size 8
IGMP: rcvd pim from 2.2.2.100 group address 16.0.0.0 port ethernet 7 size 12
debug ip msdp alarms
Displays information about MSDP alarms.
EXAMPLE:
ProCurveRS# debug ip msdp alarms
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip msdp alarms command.
MSDP: S=xxxxxxx P=0 Initiate Transport Connection to MSDP peer
Syntax: [no] debug ip msdp alarms
Possible values: N/A
Default value: N/A
debug ip msdp events
Displays messages when significant MSDP events occur.
EXAMPLE:
ProCurveRS# debug ip msdp events
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip msdp events command.
MSDP: 172.16.2.4: Closing session
MSDP: 172.16.2.4: Peer back to IDLE state
MSDP: (172.16.2.4) START peer
MSDP: 172.16.2.4: Closing session
MSDP: 172.16.2.4: Peer back to IDLE state
MSDP: Originating SA
MSDP: (172.16.2.4) START peer
MSDP: 172.16.2.4: TCP Connection to Remote Peer is Open
MSDP: 172.16.2.4: MSDP-TCP Connection opened
MSDP: 172.16.2.4: TCP_OPEN DONE, State 4
MSDP: Remote Peer closed TCP connection
Syntax: [no] debug ip msdp events
Possible values: N/A
Default value: N/A
June 2005 3 - 13
Page 28
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
debug ip msdp message
Displays information when MSDP messages are sent or received on the device.
EXAMPLE:
ProCurveRS# debug ip msdp message
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip msdp message command.
MSDP: 172.16.2.4: send keepalive message
MSDP: 172.16.2.4: TLV 4 Send Message to peer. length=3
MSDP: P=0 MSDP Header Rcvd: Len=3 Type=4
MSDP: 172.16.2.4: KEEP_ALIVE Received Type 00000004 State=4 Length=3
MSDP: 172.16.2.4: send keepalive message
MSDP: 172.16.2.4: TLV 4 Send Message to peer. length=3
MSDP: P=0 MSDP Header Rcvd: Len=3 Type=4
MSDP: 172.16.2.4: KEEP_ALIVE Received Type 00000004 State=4 Length=3
Syntax: [no] debug ip msdp message
Possible values: N/A
Default value: N/A
debug ip nat icmp
Displays information about ICMP packets whose source or destination matches a specified IP address.
EXAMPLE:
ProCurveRS# debug ip nat icmp 10.10.100.18
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip nat icmp command.
NAT: icmp src 10.10.100.18 => trans 192.168.2.79 dst 204.71.202.127
NAT: 192.168.2.79 204.71.202.127 ID 35768 len 60 txfid 13 icmp (8/0/512/519)
NAT: 204.71.202.127 10.10.100.18 ID 11554 len 60 txfid 15 icmp (0/0/512/519)
Syntax: [no] debug ip nat icmp <ip-addr>
Possible values: A valid IP address. An IP address of 0.0.0.0 matches any ICMP packet.
Default value: N/A
debug ip nat udp
Displays information about UDP packets whose source or destination matches a specified IP address.
EXAMPLE:
ProCurveRS# debug ip nat udp 10.10.100.18
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip nat udp command.
NAT: udp src 10.10.100.18:1561 => trans 192.168.2.79:65286 dst 192.168.3.11:53
NAT: 192.168.2.79:65286 192.168.3.11:53 ID 35512 len 58 txfid 13
NAT: 192.168.3.11:53 10.10.100.18:1560 ID 8453 len 346 txfid 15
Syntax: [no] debug ip nat udp <ip-addr>
Possible values: A valid IP address. An IP address of 0.0.0.0 matches any UDP packet.
3 - 14 June 2005
Page 29
HP Diagnostic Command Reference
Default value: N/A
debug ip nat tcp
Displays information about TCP packets whose source or destination matches a specified IP address.
EXAMPLE:
ProCurveRS# debug ip nat tcp 10.10.100.18
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip nat tcp command.
NAT: tcp src 10.10.100.18:1473 => trans 192.168.2.78:8016 dst 192.168.2.158:53
NAT: 192.168.2.78:8016 192.168.2.158:53 flags S ID 57970 len 44 txfid 13
NAT: 192.168.2.158:53 10.10.100.18:1473 flags S A ID 22762 len 44 txfid 15
NAT: 192.168.2.78:8016 192.168.2.158:53 flags A ID 58226 len 40 txfid 13
NAT: 192.168.2.78:8016 192.168.2.158:53 flags A ID 58482 len 77 txfid 13
NAT: 192.168.2.158:53 10.10.100.18:1473 flags A ID 23018 len 42 txfid 15
NAT: 192.168.2.78:8016 192.168.2.158:53 flags A ID 58738 len 40 txfid 13
NAT: 192.168.2.158:53 10.10.100.18:1473 flags A ID 23274 len 131 txfid 15
NAT: 192.168.2.78:8016 192.168.2.158:53 flags FA ID 58994 len 40 txfid 13
NAT: 192.168.2.158:53 10.10.100.18:1473 flags A ID 23530 len 40 txfid 15
NAT: 192.168.2.158:53 10.10.100.18:1473 flags FA ID 23786 len 40 txfid 15
NAT: 192.168.2.78:8016 192.168.2.158:53 flags A ID 59250 len 40 txfid 13
Syntax: [no] debug ip nat tcp <ip-addr>
Possible values: A valid IP address. An IP address of 0.0.0.0 matches any TCP packet.
Default value: N/A
debug ip nat transdata
Displays information about network translation requests and responses.
EXAMPLE:
ProCurveRS# debug ip nat transdata
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip nat transdata command.
NAT: icmp src 10.10.100.18:2048 => trans 192.168.2.79 dst 204.71.202.127
NAT: udp src 10.10.100.18:1561 => trans 192.168.2.79:65286 dst 192.168.3.11:53
NAT: tcp src 10.10.100.18:1473 => trans 192.168.2.78:8016 dst 192.168.2.158:53
Syntax: [no] debug ip nat transdata
Possible values: N/A
Default value: N/A
debug ip ospf adj
Displays information related to OSPF adjacency events. Adjacency events include adding or removing an
interface, receiving hello messages from an adjacency, and broadcasting hello messages to an adjacency.
EXAMPLE:
ProCurveRS# debug ip ospf adj
June 2005 3 - 15
Page 30
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip ospf adj command.
OSPF: 1.1.1.100 is added to interface neighbor list
OSPF: 4.4.4.101 is removed from interface neighbor list
OSPF: rvcd hello from 207.95.6.146 area 1 from 207.9
OSPF: broadcast hello to area 1 of all neighbors of 207.95.6.52
Syntax: [no] debug ip ospf adj
Possible values: N/A
Default value: N/A
debug ip ospf events
Displays messages when significant OSPF events occur. These events include backup designated router (BDR)
election, designated router (DR) election, and receiving and sending database description (DBD) packets.
EXAMPLE:
ProCurveRS# debug ip ospf events
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip ospf events command.
OSPF: DR/BDR election for 1.1.1.1 on ve 2
OSPF: elect BDR(backup designated router): Router ID 1.1.1.10 IP interface 1.1.1.10
OSPF: elect DR(designated router): Router ID 1.1.1.1, IP interface 1.1.1.1
OSPF: rcvd DBD from 1.1.1.1 on ve 2 flag 0x0 len 32 mtu 1500
OSPF: send DBD to 1.1.1.1 on ve 2 flag 0x0 len 232
Syntax: [no] debug ip ospf events
Possible values: N/A
Default value: N/A
debug ip ospf flood
Displays OSPF link state advertisement (LSA) flooding information.
EXAMPLE:
ProCurveRS# debug ip ospf flood
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip ospf flood command.
OSPF: flooding 1 advertisement out interface 207.95.6.52
OSPF: attempting to flood rcvd LSA area = 00000001 interface type = 1
OSPF: flood advertisement throughout the entire autonomous system
Syntax: [no] debug ip ospf flood
Possible values: N/A
Default value: N/A
debug ip ospf lsa-generation
Displays information related to OSPF link state advertisements (LSAs).
3 - 16 June 2005
Page 31
HP Diagnostic Command Reference
EXAMPLE:
ProCurveRS# ip ospf lsa-generation
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip ospf lsa-generation command.
OSPF: rcvd LSA type = 5, router ID 207.95.6.0 seq_num = 80000058
OSPF: ospf ls acknowledgement packet received!
OSPF: processing advertisement
Syntax: [no] debug ip ospf lsa-generation
Possible values: N/A
Default value: N/A
debug ip ospf packet
Displays information about OSPF packets sent and received on the device
EXAMPLE:
ProCurveRS# debug ip ospf packet
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip ospf packet command.
OSPF: rcvd. v:2 t:1 l:48 rid:207.95.6.146
aid:207.95.6.146 chk:00007920 aut:0 auk:00000000 00000000
OSPF: send v:2 t:1 l:48 rid:1.1.1.1
aid:1.1.1.1 chk:0000F630 aut:0 auk:00000000 00000000
Table 3.3 describes the contents of debug ip ospf packet messages.
Table 3.3: Output from the debug ip ospf packet command
This Field...
rcvd. or send
v:
t:
l:
rid:
Displays...
Indicates whether the packet was sent or received.
OSPF version.
OSPF packet type. Possible packet types are:
1 – Hello
2 – Data description
3 – Link state request
4 – Link state update
5 – Link state acknowledgment
OSPF packet length in bytes.
OSPF router ID.
aid:
chk:
June 2005 3 - 17
OSPF area ID.
OSPF checksum.
Page 32
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Table 3.3: Output from the debug ip ospf packet command (Continued)
This Field... Displays...
aut: OSPF authentication type. Possible authentication types are:
0 – No authentication
1 – Simple password
2 – MD5
auk: OSPF authentication key.
Syntax: [no] debug ip ospf packet
Possible values: N/A
Default value: N/A
debug ip ospf retransmission
Displays OSPF retransmission related events.
EXAMPLE:
ProCurveRS# debug ip ospf retransmission
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip ospf retransmission command.
OSPF: examine each neighbor and add advertisement to the retransmission list if
necessary
OSPF: remove current database copy from all neighbors retransmission lists
Syntax: [no] debug ip ospf retransmission
Possible values: N/A
Default value: N/A
debug ip ospf spf
Displays information about shortest path first (SPF) or Dijkstra algorithm related OSPF events. This command
lists new routing table entries when they are added, as well as the updated routing table.
EXAMPLE:
ProCurveRS# debug ip ospf spf
3 - 18 June 2005
Page 33
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip ospf spf command.
OSPF: Running dijksttra for area 1
OSPF: Adding routing table entry for transit network 207.95.6.146
OSPF: adding stub networks for area 1
OSPF: New routing table:
OSPF: ---Entry #1
OSPF: destination 1.1.1.0, mask 255.255.255.0, type 0
OSPF: area 0.0.0.1 path cost 1, type 0
OSPF: next hop router 15.212.4.123, outgoing interface loopback 22
OSPF: advertising router 1.1.1.1
OSPF: ---Entry #2
OSPF: destination 4.4.4.0, mask 255.255.255.0, type 0
OSPF: area 0.0.0.1 path cost 1, type 0
OSPF: next hop router 16.148.4.123, outgoing interface loopback 22
OSPF: advertising router 1.1.1.1
(remaining routing table entries omitted)
Syntax: [no] debug ip ospf spf
Possible values: N/A
Default value: N/A
debug ip pim <address>
Displays information about PIM related traffic. Messages are displayed when hello, join, graft, and prune
messages are sent or received.
EXAMPLE:
ProCurveRS# debug ip pim 239.255.162.6
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip pim <address> command.
PIM: send prune e7, source 1.1.1.2 group 239.255.162.6 nbr 2.2.2.1
PIM: rcvd prune e7, Source 1.1.1.2 group 239.255.162.6
PIM: send graft e7, source 1.1.1.2 group 239.255.162.6 nbr 2.2.2.1
PIM: rcvd graft e7, source 3.3.3.1 group 239.255.162.6
Syntax: [no] debug ip pim [<ip-addr>]
Possible values: Valid PIM group address.
Default value: N/A
debug ip pim events
Displays messages when PIM events, including deleting and adding group entries, occur.
EXAMPLE:
ProCurveRS# debug ip pim events
June 2005 3 - 19
Page 34
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip pim events command.
PIM: BEGIN Periodic join-prune msgs
PIM: END Periodic join-prune msgs
PIM: delete group 239.255.162.2
PIM: Begin sending Join/Prune msg to e7
PIM: delete group entry 239.255.162.2 port ethernet 1
Syntax: [no] debug ip pim events
Possible values: N/A
Default value: N/A
debug ip rip
Displays information about RIP routing transactions.
EXAMPLE:
ProCurveRS# debug ip rip
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip rip command.
RIP: sending updates(periodic) to 1.1.1.255 via ethernet 7 (1.1.1.100)
RIP: sending updates(triggered) to 1.1.1.255 via ethernet 7 (1.1.1.100)
RIP: rcvd updates from 1.1.1.100 on ethernet 7
Syntax: [no] debug ip rip
Possible values: N/A
Default value: N/A
debug ip rip database
Displays information about routes imported from other routing protocols, such as OSPF and BGP.
EXAMPLE:
ProCurveRS# debug ip rip database
3 - 20 June 2005
Page 35
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip rip database command.
RIP: process response packet
header: type:RESPONSE PACKET, version:1
RIP: remove imported route
Network Address NetMask Gateway Port Cost Type
7.7.7.0 255.255.255.0 *2.2.2.100 v3 2 O
7.7.7.0 255.255.255.0 3.3.3.100 v4 2 O
RIP: add imported OSPF route
Total number of IP routes: 14
Start index: 1 B:BGP D:Connected R:RIP S:Static O:OSPF *:Candidate default
Destination NetMask Gateway Port Cost Type
1 1.0.0.0 255.0.0.0 207.95.6.146 v8 0 B
2 1.1.1.0 255.255.255.0 0.0.0.0 v2 1 D
3 2.0.0.0 255.0.0.0 1.1.1.100 v2 2 R
4 2.2.2.0 255.255.255.0 0.0.0.0 v3 1 D
5 3.0.0.0 255.0.0.0 1.1.1.100 v2 2 R
6 3.3.3.0 255.255.255.0 0.0.0.0 v4 1 D
7 4.0.0.0 255.0.0.0 207.95.6.146 v8 0 B
8 4.4.4.0 255.255.255.0 0.0.0.0 9 1 D
9 6.0.0.0 255.0.0.0 1.1.1.100 v2 2 R
10 6.6.6.0 255.255.255.0 *2.2.2.100 v3 2 O
6.6.6.0 255.255.255.0
11 7.0.0.0 255.0.0.0
12 7.7.7.0 255.255.255.0
7.7.7.0 255.255.255.0
13 192.192.192.0 255.255.255.0
14 207.95.6.0 255.255.255.0
3.3.3.100 v4 2 O
1.1.1.100 v2 2 R
*2.2.2.100 v3 2 O
3.3.3.100 v4 2 O
207.95.6.146 v8 20 O
0.0.0.0 v8 1 D
Syntax: [no] debug ip rip database
Possible values: N/A
Default value: N/A
debug ip rip events
Displays information about RIP events, including aged-out routes and replies sent to other routers.
EXAMPLE:
ProCurveRS# debug ip rip events
June 2005 3 - 21
Page 36
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip rip events command.
RIP: route to 6.0.0.0 via next hop 1.1.1.100 aged out
RIP: send all routes reply to 1.1.1.100
RIP: received response from 1.1.1.100: 164 bytes
route entry: family:2, target:6.0.0.0, metric:1
route entry: family:2, target:207.95.6.0, metric:1
RIP: New routing table
Total number of IP routes: 6
Start index: 1 B:BGP D:Connected R:RIP S:Static O:OSPF *:Candidate default
1
Destination
1.0.0.0
NetMask
255.0.0.0
Gateway
207.95.6.146
Port
v8
Cost
0
2 1.1.1.0 255.255.255.0 0.0.0.0 v2 1 D
3 2.0.0.0 255.0.0.0 207.95.6.146 v8 0 B
4 2.2.2.0 255.255.255.0 0.0.0.0 v3 1 D
5 3.0.0.0 255.0.0.0 1.1.1.100 v2 2 R
6 3.3.3.0 255.255.255.0 0.0.0.0 v4 1 D
Syntax: [no] debug ip rip events
Possible values: N/A
Default value: N/A
Type
B
debug ip rip trigger
Displays information about RIP events triggered by adding or deleting a route.
EXAMPLE:
ProCurveRS# debug ip rip trigger
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip rip trigger command.
RIP: adding route to target:3.0.0.0 via gateway:1.1.1.9, metric: 2, port: 8, bits: 8
RIP: deleting route to target:3.0.0.0 via gateway:1.1.1.9
RIP: build route header: type:RESPONSE PACKET, version:1
RIP: build route entry: family:2, target:207.95.6.0, metric:1
RIP: periodic update sent on port 18
Syntax: [no] debug ip rip trigger
Possible values: N/A
Default value: N/A
debug ip ssh
Displays the status of SSH session negotiation.
EXAMPLE:
ProCurveRS# debug ip ssh
3 - 22 June 2005
Page 37
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip ssh command.
SSH: Server successfully sent to client its version number
SSH: Server received client's version number
SSH: client's version number SSH-1.5
SSH: Server version number matches client's version number
SSH: Server sent its host and server public keys to the client
SSH: Server received session key from the client
SSH: Server received client's name
SSH: Server authenticated the client with password
SSH: Client requested compression
SSH: Secure Shell is established!
Syntax: [no] debug ip ssh
Possible values: N/A
Default value: N/A
debug ip tcp <address>
Displays information about TCP packets from a specified IP address.
EXAMPLE:
ProCurveRS# debug ip tcp 192.168.9.210
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip tcp
<address>
command.
TCP: rcvd packet (len=20) 192.168.9.210:3669 -> 192.168.9.2:23
packet:syn:0,ack:1,rst:0,fin:1,hlen:5,chksum:00006fdf,seqn:2423494362,ackn:211
TCP: sent packet (len=40) 192.168.9.2:23 -> 192.168.9.210:3669
packet: syn:0,ack:0,rst:1,fin:0,hlen:5,chksum:0000b93d,seqn:21521,ackn:0
TCP: sent packet 192.168.9.2:23 -> 192.168.9.210:3669
packet: syn:0,ack:0,rst:1,fin:0,hlen:5,chksum:0000b93d,seqn:21521,ackn:0
Syntax: [no] debug ip tcp <address>
Possible values: IP address
Default value: N/A
debug ip tcp driver
Displays information about TCP driver related events, such as opening, closing, and aborting a TCP connection,
or discarding TCP packets.
EXAMPLE:
ProCurveRS# debug ip tcp driver
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip tcp driver command.
TCP: aborting connection 1.1.1.1:23 -> 1.1.1.2:2559
TCP: closing connection 1.1.1.1:23 -> 1.1.1.2:2559
TCP: opening connection 207.95.6.52:3456 -> 207.95.6.146:23
Syntax: [no] debug ip tcp driver
June 2005 3 - 23
Page 38
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Possible values: N/A
Default value: N/A
debug ip tcp memory
The debug ip tcp memory command causes messages to be displayed when memory is allocated or deallocated
to the internal TCP buffers.
EXAMPLE:
ProCurveRS# debug ip tcp memory
For example, when a user establishes a Telnet session with the device, an then terminates it, messages such as
the following appear at the destination specified for debugging output. You can turn off these messages with the
no debug ip tcp memory command.
TCP TCB ALLOCATED 210de822
TCP SEND BUFFER ALLOCATED 2111ec80
TCP SEND QUEUE BUFFER ALLOCATED 210d88dc
TCP SEND BUFFER ALLOCATED 2113695c
TCP SEND QUEUE BUFFER ALLOCATED 210d9714
TCP SEND BUFFER ALLOCATED 2111f838
TCP SEND QUEUE BUFFER ALLOCATED 210d894c
TCP SEND BUFFER ALLOCATED 21117174
TCP SEND QUEUE BUFFER ALLOCATED 210d8444
TCP SEND BUFFER ALLOCATED 210f4aac
TCP SEND QUEUE BUFFER ALLOCATED 210d6fb4
TCP SEND BUFFER ALLOCATED 210f5088
TCP SEND QUEUE BUFFER ALLOCATED 210d6fec
TCP SEND BUFFER FREED 2111ec80
TCP QUEUE BUFFER FREED 210d6fec
TCP RECEIVE QUEUE BUFFER ALLOCATED 210d6fec
TCP RECEIVE BUFFER ALLOCATED 21151530
TCP RECEIVE BUFFER FREED 21151530
TCP QUEUE BUFFER FREED 210d6fec
TCP RECEIVE QUEUE BUFFER ALLOCATED 210d6fec
TCP RECEIVE BUFFER ALLOCATED 21151530
TCP RECEIVE BUFFER FREED 21151530
TCP QUEUE BUFFER FREED 210d6fec
TCP TCB FREED 210de822
Syntax: [no] debug ip tcp memory
NOTE: Output from this command appears only on the console or syslog. The output is suppressed when sent
to a Telnet or SSH session.
Possible values: N/A
Default value: N/A
debug ip tcp packet
Displays information about received and sent TCP packets.
EXAMPLE:
ProCurveRS# debug ip tcp packet
3 - 24 June 2005
Page 39
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip tcp packet command.
TCP: rcvd packet (len=20) 1.1.1.2:2526 -> 1.1.1.1:23
packet:syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:0000c34e,seqn:55807198,ackn:548539276
TCP: sent packet (len=20) 207.95.6.52:8104 -> 207.95.6.146:179
packet:syn:0,ack:1,rst:0,fin:0,hlen:5,chksum:00008b4a,seqn:36182260,ackn:2027586739
Syntax: [no] debug ip tcp packet
Possible values: N/A
Default value: N/A
debug ip tcp sack
Displays information about TCP Selective-ACK packets.
EXAMPLE:
ProCurveRS# debug ip tcp sack
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip tcp sack command.
TCP: process ACK, tcp state tcp_syn_recd
TCP: nothing to ACK, sequence number 21521, tcp is in sequence
TCP: process ACK, tcp state tcp_close_wait
Syntax: [no] debug ip tcp sack
Possible values: N/A
Default value: N/A
debug ip tcp transactions
Displays information about TCP transactions, including state changes and packet retransmissions.
EXAMPLE:
ProCurveRS# debug ip tcp transactions
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip tcp transactions command.
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change LISTEN -> SYN-RECEIVED
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change SYN-RECEIVED -> ESTABLISHED
TCP: retransmitted segment
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change ESTABLISHED -> FIN-WAIT-1
TCP: retransmitted segment
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change FIN-WAIT-1 -> FIN-WAIT-2
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change FIN-WAIT-2 -> TIME-WAIT
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change TIME-WAIT -> CLOSED
Syntax: [no] debug ip tcp transactions
Possible values: N/A
Default value: N/A
June 2005 3 - 25
Page 40
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
debug ip udp
Displays information about UDP packets.
EXAMPLE:
ProCurveRS# debug ip udp
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip udp command.
UDP: sent src 1.1.168.192(port 161) -> dest 181.1.168.192(port 162), length:71
UDP: rcvd src 234.1.168.192(port 138) -> dest 255.1.168.192(port 138), length:209
Syntax: [no] debug ip udp
Possible values: N/A
Default value: N/A
debug ip vrrp events
Displays information about VRRP events, such as when a backup router transitions to a master, a router
transitions to a backup router, a VRID is deleted, or a VRRP packet is dropped.
EXAMPLE:
ProCurveRS# debug ip vrrp events
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip vrrp events command.
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change LISTEN -> SYN-RECEIVED
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change SYN-RECEIVED -> ESTABLISHED
TCP: retransmitted segment
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change ESTABLISHED -> FIN-WAIT-1
TCP: retransmitted segment
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change FIN-WAIT-1 -> FIN-WAIT-2
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change FIN-WAIT-2 -> TIME-WAIT
TCP: 1.1.1.1:23 -> 1.1.1.2:2537: state change TIME-WAIT -> CLOSED
Syntax: [no] debug ip vrrp events
Possible values: N/A
Default value: N/A
debug ip vrrp packet
Displays information about VRRP packets and the IP addresses of backup routers.
EXAMPLE:
ProCurveRS# debug ip vrrp packet
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ip vrrp events command.
VRRP: rcvd ver:2 type:1 vrid:1 pri:255 #ip:1 aut:0 adv:1 chk:56825
Num of ip addr 1
1.1.1.1 from sender 1.1.1.1
VRRP: send advertise! ver:2 type:1 vrid:1 pri:255 #ip:1 aut:0 adv:1 chk:56825
Num of ip addr 1
1.1.1.1
3 - 26 June 2005
Page 41
Table 3.4 describes the contents of debug ip vrrp packet messages.
Table 3.4: Output from the debug ip vrrp packet command
HP Diagnostic Command Reference
This Field...
rcvd. or send
ver:
type:
vrid:
pri:
#ip:
aut:
adv:
chk:
Num of ip addr
Syntax: [no] debug ip vrrp packet
Displays...
Indicates whether the packet was sent or received.
VRRP version; RFC 2338 defines version 2.
VRRP packet type. Possible packet types are:
1 Advertisement
Virtual Router Identifier.
Priority of the VRRP router.
The number of IP addresses contained in this VRRP advertisement.
VRRP authentication type. Possible authentication types are:
0 No authentication
1 Simple text password
2 IP Authentication Header
VRRP checksum.
Possible values: N/A
Default value: N/A
debug ipv6 address
Displays information about packets with a source or destination address that matches the specified IPv6 address.
Entering the debug ipv6 address command also enables the debugging of IPv6 packets. For more information
about debugging IPv6 packets, see “debug ipv6 packet” on page 3-42.
EXAMPLE:
ProCurveRS# debug ipv6 address 3000:1::2
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 address command.
IPv6_TX: 3000:1::2 => 3000:1::6 (00e0.52da.c347)
NextHeader:58, size:32 (72), vlan:1, Port: 136 (136)
Syntax: [no] debug ipv6 address <ipv6-address>
Possible values: A valid IPv6 address.
Default value: N/A
June 2005 3 - 27
Page 42
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
debug ipv6 cache
Displays information when an IPv6 cache entry is added, deleted, or updated. The IPv6 cache contains an IPv6
host table that has indices to the next hop gateway and the router interface on which the route was learned.
EXAMPLE:
ProCurveRS debug ipv6 cache
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 cache command.
IPv6RT0: Deleted cache for fe80::204:80ff:fe2c:c048 on port 3/9 Local
IPv6RT0: Deleted cache for 3000:1::2 on port 3/9 Local
IPv6RT0: update cache entries for parent route 3000:1::/6 route 3000:1::/64
IPv6RT0: Added cache for 3000:1::2 on port 3/9 Local
IPv6RT0: Added cache for fe80::204:80ff:fe2c:c048 on port 3/9 Local
Syntax: [no] debug ipv6 cache
Possible values: N/A
Default value: N/A
debug ipv6 icmp
Displays information when an HP device that supports IPv6 receives and transmits ICMP request, response, error,
and redirect packets.
EXAMPLE:
ProCurveRS debug ipv6 icmp
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 icmp command.
ICMPv6:Sending Echo Request to 3000:1::6, length 24
ICMPv6:Received Echo Reply from 3000:1::6, length 24
Syntax: [no] debug ipv6 icmp
Possible values: N/A
Default value: N/A
debug ipv6 nd
Displays information when an HP device that supports IPv6 sends and receives neighbor solicitation and
advertisement messages, which verify the existence of a new neighbor or an existing neighbor that has become
unreachable.
EXAMPLE:
ProCurveRS debug ipv6 nd
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 nd command.
ICMPv6-ND: STALE->DELAY: 3000:1::6 on 3/9
ICMPv6-ND: Received NS for 3000:1::2 on 3/9 from 3000:1::6
ICMPv6-ND: Sending NA for 3000:1::2 on 3/9
Syntax: [no] debug ipv6 nd
3 - 28 June 2005
Page 43
HP Diagnostic Command Reference
Possible values: N/A
Default value: N/A
debug ipv6 ospf ism
Displays comprehensive information about the status changes of OSPF version 3 interfaces. The debug ipv6
ospf ism-status command displays status change messages only. For more information, see “debug ipv6 ospf
ism-status” on page 3-29.
EXAMPLE:
ProCurveRS debug ipv6 ospf ism
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf ism command.
OSPFv3 ISM[137]: InterfaceUp
OSPFv3 ISM[137]: Status change Down -> Waiting (Priority > 0)
OSPFv3 ISM[137]: BackupSeen
OSPFv3 ISM[137]: Status change Waiting -> BDR (BackupSeen:DR Election)
OSPFv3 ISM[137]: {dr:0.0.0.0,bdr:0.0.0.0} -> {dr:2.2.2.2,bdr:1.2.3.4}
Syntax: [no] debug ipv6 ospf ism
Possible values: N/A
Default value: N/A
debug ipv6 ospf ism-events
Displays information when an event related to an OSPF version 3 interface, for example, an interface coming up,
occurs.
EXAMPLE:
ProCurveRS debug ipv6 ospf ism-events
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf ism-events command.
OSPFv3 ISM[137]: InterfaceUp
OSPFv3 ISM[137]: BackupSeen goes up
Syntax: [no] debug ipv6 ospf ism-events
Possible values: N/A
Default value: N/A
debug ipv6 ospf ism-status
Displays status change messages only related to OSPF version 3 interfaces. The debug ipv6 ospf ism command
displays more comprehensive information about OSPF version 3 interface status changes. For more information,
see
“debug ipv6 ospf ism” on page 3-29.
EXAMPLE:
ProCurveRS debug ipv6 ospf ism-status
June 2005 3 - 29
Page 44
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf ism-status command.
OSPFv3 ISM[137]: Status change Down -> Waiting (Priority > 0)
OSPFv3 ISM[137]: Status change Waiting -> BDR (Backup Seen:DR Election)
OSPFv3 ISM[137]: {dr:0.0.0.0,bdr:0.0.0.0} -> {dr:2.2.2.2,bdr:1.2.3.4}
Syntax: [no] debug ipv6 ospf ism-status
Possible values: N/A
Default value: N/A
debug ipv6 ospf lsa
Displays information when an OSPF version 3 router generates link-state advertisements (LSAs).
EXAMPLE:
ProCurveRS debug ipv6 ospf lsa
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf lsa command.
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Checking Interface 137
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Interface 137 is down
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): No prefix to advertise for Area
0.0.0.0
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): Area 0.0.0.0
ospf1(config-ospf6-router)#OSPFv3 ISM[137]: Status change Down -> Waiting
(Priority > 0)
LSA: Update Router-LSA for area 0.0.0.0
OSPFV3 LSA: Create LSA Type :Router Id: 0 Advrouter: 1.2.3.4
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Checking Interface 137
OSPFv3 LSA Update Intra-Area-Prefix(Stub): include 3000:1::2/64
OSPFV3 LSA: Create LSA Type :IntraPrefix Id: 0 Advrouter: 1.2.3.4
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): Area 0.0.0.0
OSPFv3 :LSA Update Link: Interface 137
OSPFV3 LSA: Create LSA Type :Link Id: 137 Advrouter: 1.2.3.4
OSPF6: Inter Area LSA not generated, route is in same area.
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Checking Interface 137
OSPFv3 LSA Update Intra-Area-Prefix(Stub): include 3000:1::2/64
OSPFV3 LSA: Create LSA Type :IntraPrefix Id: 0 Advrouter: 1.2.3.4
OSPFv3 LSA: Turnover type:IntraPrefix Lsa Id:0.0.0.0 AdvRouter:1.2.3.4: conten ts
not changed
OSPFV3 LSA: Delete LSA Type :IntraPrefix Id: 0.0.0.0 Advrouter: 1.2.3.4
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): Area 0.0.0.0
Syntax: [no] debug ipv6 ospf lsa
Possible values: N/A
Default value: N/A
debug ipv6 ospf lsa-flooding
Displays information when an OSPF version 3 router floods LSAs to neighboring routers to update them about its
interfaces.
EXAMPLE:
ProCurveRS debug ipv6 ospf lsa-flooding
3 - 30 June 2005
Page 45
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf lsa-flooding command.
OSPFV3:LSA: schedule flooding 2.2.2.2
OSPFV3:LSA: schedule flooding 2.2.2.2
OSPFV3:LSA: schedule flooding 2.2.2.2
OSPFV3:LSA: schedule flooding 2.2.2.2
Syntax: [no] debug ipv6 ospf lsa-flooding
Possible values: N/A
Default value: N/A
debug ipv6 ospf lsa-generation
Displays information when an OSPF version 3 router creates or deletes LSAs from its link state database.
EXAMPLE:
ProCurveRS debug ipv6 ospf lsa-generation
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf lsa-generation command.
OSPFV3 LSA: Create LSA Type :Router Id: 0 Advrouter:1.2.3.4
OSPFV3 LSA: Create LSA Type :IntraPrefix Id: 0 Advrouter: 1.2.3.4
OSPFV3 LSA: Create LSA Type :Link Id: 137 Advrouter: 1.2.3.4
OSPFV3 LSA: Create LSA Type :Router Id: 0 Advrouter: 1.2.3.4
OSPFV3 LSA: Delete LSA Type :Router Id: 0.0.0.0 Advrouter: 1.2.3.4
OSPFV3 LSA: Create LSA Header Type :Router Id: 0 Advrouter: 1.2.3.4
OSPFV3 LSA: Create LSA Header Type :Router Id: 0 Advrouter: 2.2.2.2
OSPFV3 LSA: Create LSA Header Type :IntraPrefix Id: 0 Advrouter: 2.2.2.2
OSPFV3 LSA: Create LSA Header Type :Link Id: 136 Advrouter: 2.2.2.2
OSPFV3 LSA: Create LSA Header Type :Link Id: 137 Advrouter: 1.2.3.4
OSPFV3 LSA: Delete LSA HEADER Type :Link Id: 0.0.0.137 Advrouter: 1.2.3.4
OSPFV3 LSA: Create LSA Type :Router Id: 0 Advrouter: 1.2.3.4
OSPFV3 LSA: Delete LSA HEADER Type :Router Id: 0.0.0.0 Advrouter: 1.2.3.4
OSPFV3 LSA: Delete LSA Type :Router Id: 0.0.0.0 Advrouter: 1.2.3.4
OSPFV3 LSA: Delete LSA Type :Router Id: 0.0.0.0 Advrouter: 1.2.3.4
OSPFV3 LSA: Create LSA Type :Router Id: 0 Advrouter: 2.2.2.2
OSPFV3 LSA: Delete LSA HEADER Type :Router Id: 0.0.0.0 Advrouter: 2.2.2.2
OSPFV3 LSA: Create LSA Type :IntraPrefix Id: 0 Advrouter: 2.2.2.2
OSPFV3 LSA: Delete LSA HEADER Type :IntraPrefix Id: 0.0.0.0 Advrouter: 2.2.2.2
OSPFV3 LSA: Create LSA Type :Link Id: 136 Advrouter: 2.2.2.2
Syntax: [no] debug ipv6 ospf lsa-generation
Possible values: N/A
Default value: N/A
debug ipv6 ospf lsa-install
Displays information when an OSPF version 3 router installs a new LSA in its link state database.
EXAMPLE:
ProCurveRS debug ipv6 ospf lsa-install
June 2005 3 - 31
Page 46
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf lsa-install command.
OSPFv3 LSA: Turnover type:IntraPrefix Lsa Id:0.0.0.0 AdvRouter:1.2.3.4: contents
not changed
OSPFv3 LSA: Turnover type:Router Lsa Id:0.0.0.0 AdvRouter:1.2.3.4: contents not
changed
OSPFv3 LSA: Turnover type:Router Lsa Id:0.0.0.0 AdvRouter:1.2.3.4: contents not
changed
OSPFv3 LSA: Turnover type:Router Lsa Id:0.0.0.0 AdvRouter:1.2.3.4: contents
changed
OSPFv3 LSA: Turnover type:IntraPrefix Lsa Id:0.0.0.0 AdvRouter:2.2.2.2: conten ts
changed
OSPFv3 LSA: Turnover type:Router Lsa Id:0.0.0.0 AdvRouter:2.2.2.2: contents
changed
Syntax: [no] debug ipv6 ospf lsa-install
Possible values: N/A
Default value: N/A
debug ipv6 ospf lsa-maxage
Displays information when an OSPF version 3 router removes an LSA from its link state database because the
router has not received any updates about the LSA in a specified amount of time.
EXAMPLE:
ProCurveRS debug ipv6 ospf lsa-maxage
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf lsa-maxage command.
OSPFv3 LSA: Premature aging: Type: IntraPrefix, ID : 0, AdvRouter 1.2.3.4
OSPFv3 LSA: Premature aging: Type: IntraPrefix, ID : 0, AdvRouter 1.2.3.4
OSPFv3 LSA: remove MaxAge LSA:IntraPrefix Lsa Id:0.0.0.0 AdvRouter:1.2.3.4:
OSPFv3 LSA: remove MaxAge LSA:IntraPrefix Lsa Id:0.0.0.0 AdvRouter:2.2.2.2:
Syntax: [no] debug ipv6 ospf lsa-maxage
Possible values: N/A
Default value: N/A
debug ipv6 ospf lsa-refresh
Displays information when a link state database is refreshed with updated information about an existing LSA.
EXAMPLE:
ProCurveRS debug ipv6 ospf lsa-refresh
3 - 32 June 2005
Page 47
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf lsa-refresh command.
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Checking Interface 137
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Interface 137 is down
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): No prefix to advertise for Area
0.0.0.0
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): Area 0.0.0.0
ospf1(config-ospf6-router)#LSA: Update Router-LSA for area 0.0.0.0
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Checking Interface 137
OSPFv3 LSA Update Intra-Area-Prefix(Stub): include 3000:1::2/64
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): Area 0.0.0.0
OSPFv3 :LSA Update Link: Interface 137
LSA: Update Router-LSA for area 0.0.0.0
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Checking Interface 137
OSPFv3 LSA Update Intra-Area-Prefix(Stub): include 3000:1::2/64
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): Area 0.0.0.0
OSPFV3: LSA[2.2.2.2]: request 1.2.3.40 (newer)
OSPFV3 LSA[2.2.2.2]: request Type =8193 ADvRtr =2.2.2.2 ID=0
OSPFV3 LSA[2.2.2.2]: request Type =8201 ADvRtr =2.2.2.2 ID=0
OSPFV3 LSA[2.2.2.2]: request Type =8 ADvRtr =2.2.2.2 ID=136
OSPFv3 : LSA[575305040]: delayed ack
LSA: Update Router-LSA for area 0.0.0.0
OSPFv3 : LSA[575305040]: delayed ack
OSPFv3 : LSA[575305040]: delayed ack
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Checking Interface 137
OSPFv3 LSA Update Intra-Area-Prefix(Stub): Interface 137 is not stub
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): No prefix to advertise for Area
0.0.0.0
OSPFv3 :LSA Update Intra-Area-Prefix(Stub): Area 0.0.0.0
LSA: Update Router-LSA for area 0.0.0.0
OSPFv3 : LSA[575305040]: delayed ack
OSPFv3:LSA[2.2.2.2]: direct ack
OSPFv3 : LSA[575305040]: delayed ack
OSPFv3:LSA[2.2.2.2]: direct ack
OSPFv3:LSA[2.2.2.2]: direct ack
OSPFv3:LSA[2.2.2.2]: direct ack
OSPFv3 : LSA[575305040]: delayed ack
Syntax: [no] debug ipv6 ospf lsa-refresh
Possible values: N/A
Default value: N/A
debug ipv6 ospf nsm
Displays comprehensive information about the status changes of OSPF version 3 neighbors. The debug ipv6
ospf nsm-status command displays status change messages only. For more information, see “debug ipv6 ospf
ism-status” on page 3-29.
EXAMPLE:
ProCurveRS debug ipv6 ospf nsm
June 2005 3 - 33
Page 48
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf nsm command.
OSPFv3 NSM[2.2.2.2]: HelloReceived
OSPFv3 NSM[2.2.2.2]: Status change [Down]->[Init](HelloReceived)
OSPFv3 NSM[2.2.2.2]: 2Way-Received
OSPFv3 NSM[2.2.2.2]: Status change [Init]->[2-way](No Need Adjacency)
OSPFv3 NSM[2.2.2.2]: AdjOK?
OSPFv3 NSM[2.2.2.2]: Status change [2-way]->[ExStart](Need Adjacency)
OSPFv3 NSM[2.2.2.2]: NegotiationDone
OSPFv3 NSM[2.2.2.2]: Status change [ExStart]->[ExChange](NegotiationDone)
OSPFv3 NSM[2.2.2.2]: ExchangeDone
OSPFv3 NSM[2.2.2.2]: Status change [ExChange]->[Loading](Requestlist Not Empty)
OSPFv3 NSM[2.2.2.2]: LoadingDone
OSPFv3 NSM[2.2.2.2]: Status change [Loading]->[Full](LoadingDone)
Syntax: [no] debug ipv6 ospf nsm
Possible values: N/A
Default value: N/A
debug ipv6 ospf nsm-events
Displays information when an event related to an OSPF version 3 neighbor, for example, the discovery of a new
neighbor, occurs.
EXAMPLE:
ProCurveRS debug ipv6 ospf nsm-events
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf nsm-events command.
OSPFv3 NSM[2.2.2.2]: HelloReceived
OSPFv3 NSM[2.2.2.2]: 2Way-Received
OSPFv3 NSM[2.2.2.2]: AdjOK?
OSPFv3 NSM[2.2.2.2]: NegotiationDone
OSPFv3 NSM[2.2.2.2]: ExchangeDone
OSPFv3 NSM[2.2.2.2]: LoadingDone
Syntax: [no] debug ipv6 ospf nsm-events
Possible values: N/A
Default value: N/A
debug ipv6 ospf nsm-status
Displays status change messages only related to OSPF version 3 neighbors. The debug ipv6 ospf nsm
command displays more comprehensive information about OSPF version 3 neighbor status changes. For more
information, see “debug ipv6 ospf nsm” on page 3-33.
EXAMPLE:
ProCurveRS debug ipv6 ospf nsm-status
3 - 34 June 2005
Page 49
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf nsm-status command.
OSPFv3 NSM[2.2.2.2]: Status change [Down]->[Init](HelloReceived)
OSPFv3 NSM[2.2.2.2]: Status change [Init]->[2-way](No Need Adjacency)
OSPFv3 NSM[2.2.2.2]: Status change [2-way]->[ExStart](Need Adjacency)
OSPFv3 NSM[2.2.2.2]: Status change [ExStart]->[ExChange](NegotiationDone)
OSPFv3 NSM[2.2.2.2]: Status change [ExChange]->[Loading](Requestlist Not Empty)
OSPFv3 NSM[2.2.2.2]: Status change [Loading]->[Full](LoadingDone)
Syntax: [no] debug ipv6 ospf nsm-status
Possible values: N/A
Default value: N/A
debug ipv6 ospf packet
Displays information about OSPF version 3 packets sent and received on an HP device that supports IPv6.
EXAMPLE:
ProCurveRS debug ipv6 ospf packet
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf packet command.
OSPFv3: Snd Hello on ethe 3/9(fe80::204:80ff:fe2c:c048->ff02::5)
RtrID:1.2.3.4 DR:0.0.0.0 BDR:0.0.0.0
OSPFv3: Rcv Hello on ethe 3/9(fe80::2e0:52ff:feda:c347->ff02::5)
RtrID:2.2.2.2 DR:2.2.2.2 BDR:1.2.3.4
OSPFv3: NBR 2.2.2.2 declares 2.2.2.2 as DR
OSPFv3: NBR 2.2.2.2 declare 1.2.3.4 as BDR
OSPFv3: Rcv DbDesc on ethe 3/9(fe80::2e0:52ff:feda:c347->
fe80::204:80ff:fe2c:c048)
Syntax: [no] debug ipv6 ospf packet
Possible values: N/A
Default value: N/A
debug ipv6 ospf packet-dd
Displays information when an HP device that supports IPv6 sends or receives OSPF version 3 data description
packets.
EXAMPLE:
ProCurveRS debug ipv6 ospf packet-dd
June 2005 3 - 35
Page 50
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf packet-dd command.
OSPFV3: set dbdesc seqnum 0000ec4a for 2.2.2.2OSPFv3: Snd DbDesc on ethe 3
/9(fe80::204:80ff:fe2c:c048->fe80::2e0:52ff:feda:c347)
OSPFv3: Rcv DbDesc on ethe 3/9(fe80::2e0:52ff:feda:c347->fe80::204:80ff:fe2c:c048)
OSPFv3: Snd DbDesc on ethe 3/9(fe80::204:80ff:fe2c:c048->fe80::2e0:52ff:feda:c347)
Type:2001, LSID:00000000 Adv:1.2.3.4 SEQ:8000001c AGE:4
Type:2001, LSID:00000000 Adv:2.2.2.2 SEQ:80000025 AGE:3551
Type:2002, LSID:00000088 Adv:2.2.2.2 SEQ:80000001 AGE:3555
Type:2009, LSID:00000000 Adv:1.2.3.4 SEQ:80000007 AGE:4
Type:2009, LSID:000002a8 Adv:2.2.2.2 SEQ:80000001 AGE:3555
Type:0008, LSID:00000089 Adv:1.2.3.4 SEQ:80000003 AGE:35
OSPFv3: Rcv DbDesc on ethe 3/9(fe80::2e0:52ff:feda:c347->fe80::204:80ff:fe2c:c048)
Type:2001, LSID:00000000 Adv:2.2.2.2 SEQ:80000002 AGE:1
Type:2009, LSID:00000000 Adv:2.2.2.2 SEQ:80000003 AGE:1
Type:0008, LSID:00000088 Adv:2.2.2.2 SEQ:80000003 AGE:32
OSPFv3: Snd DbDesc on ethe 3/9(fe80::204:80ff:fe2c:c048->fe80::2e0:52ff:feda:c347)
Syntax: [no] debug ipv6 ospf packet-dd
Possible values: N/A
Default value: N/A
debug ipv6 ospf packet-hello
Displays information when an HP device that supports IPv6 sends or receives OSPF version 3 hello packets.
EXAMPLE:
ProCurveRS debug ipv6 ospf packet-hello
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf packet-hello command.
OSPFv3: Snd Hello on ethe 3/9(fe80::204:80ff:fe2c:c048->ff02::5)
RtrID:1.2.3.4 DR:2.2.2.2 BDR:1.2.3.4
OSPFv3: Rcv Hello on ethe 3/9(fe80::2e0:52ff:feda:c347->ff02::5)
RtrID:2.2.2.2 DR:2.2.2.2 BDR:1.2.3.4
Syntax: [no] debug ipv6 ospf packet-hello
Possible values: N/A
Default value: N/A
debug ipv6 ospf packet-lsa-ack
Displays information when an HP device that supports IPv6 sends or receives OSPF version 3 LSA ack packets.
EXAMPLE:
ProCurveRS debug ipv6 ospf packet-lsa-ack
3 - 36 June 2005
Page 51
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf packet-lsa-ack command.
OSPFv3: Snd LSAck on ethe 3/9(fe80::204:80ff:fe2c:c048->fe80::2e0:52ff:feda:c347)
Type:2009, LSID:00000000 Adv:2.2.2.2 SEQ:80000001 AGE:3600
OSPFv3: Rcv LSAck on ethe 3/9(fe80::2e0:52ff:feda:c347->fe80::204:80ff:fe2c:c048)
Type:2009, LSID:00000000 Adv:1.2.3.4 SEQ:80000001 AGE:3600
OSPFv3: Rcv LSAck on ethe 3/9(fe80::2e0:52ff:feda:c347->ff02::5)
Type:2001, LSID:00000000 Adv:1.2.3.4 SEQ:8000001e AGE:4
Type:0008, LSID:00000089 Adv:1.2.3.4 SEQ:80000004 AGE:4
OSPFv3: Snd LSAck on ethe 3/9(fe80::204:80ff:fe2c:c048->ff02::5)
Type:0008, LSID:00000088 Adv:2.2.2.2 SEQ:80000003 AGE:248
Type:2002, LSID:00000088 Adv:2.2.2.2 SEQ:80000003 AGE:5
Type:2009, LSID:000002a8 Adv:2.2.2.2 SEQ:80000003 AGE:5
Type:2009, LSID:00000000 Adv:2.2.2.2 SEQ:80000001 AGE:3600
Type:2001, LSID:00000000 Adv:2.2.2.2 SEQ:8000002a AGE:4
OSPFv3: Rcv LSAck on ethe 3/9(fe80::2e0:52ff:feda:c347->fe80::204:80ff:fe2c:c048)
Type:2001, LSID:00000000 Adv:1.2.3.4 SEQ:8000001f AGE:1
OSPFv3: Rcv LSAck on ethe 3/9(fe80::2e0:52ff:feda:c347->ff02::5)
Type:2001, LSID:00000000 Adv:1.2.3.4 SEQ:8000001f AGE:4
Type:2001, LSID:00000000 Adv:1.2.3.4 SEQ:8000001f AGE:4
OSPFv3: Snd LSAck on ethe 3/9(fe80::204:80ff:fe2c:c048->ff02::5)
Type:2001, LSID:00000000 Adv:2.2.2.2 SEQ:8000002b AGE:5
Syntax: [no] debug ipv6 ospf packet-lsa-ack
Possible values: N/A
Default value: N/A
debug ipv6 ospf packet-lsa-req
Displays information when an HP device that supports IPv6 sends or receives OSPF version 3 LSA request
packets.
EXAMPLE:
ProCurveRS debug ipv6 ospf packet-lsa-req
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf packet-lsa-req command.
OSPFv3: Rcv LSReq on ethe 3/9(fe80::2e0:52ff:feda:c347->fe80::204:80ff:fe2c:c048)
Type:2009, LSID:00000000 Adv-Router:1.2.3.4
OSPFv3: Snd LSReq on ethe 3/9(fe80::204:80ff:fe2c:c048->fe80::2e0:52ff:feda:c347)
Type:2001, LSID:00000000 Adv-Router:1.2.3.4
Type:2001, LSID:00000000 Adv-Router:2.2.2.2
Type:2009, LSID:00000000 Adv-Router:2.2.2.2
Type:0008, LSID:00000088 Adv-Router:2.2.2.2
Type:0008, LSID:00000089 Adv-Router:1.2.3.4
Syntax: [no] debug ipv6 ospf packet-lsa-req
Possible values: N/A
Default value: N/A
June 2005 3 - 37
Page 52
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
debug ipv6 ospf packet-lsa-update
Displays information when an HP device that supports IPv6 sends or receives OSPF version 3 LSA update
packets.
EXAMPLE:
ProCurveRS debug ipv6 ospf packet-lsa-update
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf packet-lsa-update command.
OSPFv3: Snd LSUpdate on ethe 3/9(fe80::204:80ff:fe2c:
c048>fe80::2e0:52ff:feda:c347)
Type:2009, LSID:00000000 Adv:1.2.3.4 SEQ:80000001 AGE:1
OSPFv3: Rcv LSUpdate on ethe 3/9(fe80::2e0:52ff:feda:c347->fe80::204:80ff:fe2c:
c048)
Type:2001, LSID:00000000 Adv:1.2.3.4 SEQ:80000021 AGE:77
Type:2001, LSID:00000000 Adv:2.2.2.2 SEQ:80000030 AGE:1
Type:2009, LSID:00000000 Adv:2.2.2.2 SEQ:80000001 AGE:1
Type:0008, LSID:00000088 Adv:2.2.2.2 SEQ:80000003 AGE:854
Type:0008, LSID:00000089 Adv:1.2.3.4 SEQ:80000005 AGE:82
OSPFv3: Snd LSUpdate on ethe 3/9(fe80::204:80ff:fe2c:c048->ff02::5)
Type:2001, LSID:00000000 Adv:1.2.3.4 SEQ:80000022 AGE:1
Type:0008, LSID:00000089 Adv:1.2.3.4 SEQ:80000006 AGE:1
OSPFv3: Rcv LSUpdate on ethe 3/9(fe80::2e0:52ff:feda:c347->ff02::5)
Type:2002, LSID:00000088 Adv:2.2.2.2 SEQ:80000002 AGE:1
Type:2009, LSID:000002a8 Adv:2.2.2.2 SEQ:80000002 AGE:1
OSPFv3: Snd LSUpdate on ethe 3/9(fe80::204:80ff:fe2c:c048->ff02::5)
Type:2001, LSID:00000000 Adv:1.2.3.4 SEQ:80000023 AGE:1
OSPFv3: Rcv LSUpdate on ethe 3/9(fe80::2e0:52ff:feda:c347->ff02::5)
Type:2009, LSID:00000000 Adv:2.2.2.2 SEQ:80000001 AGE:3600
Type:2009, LSID:00000000 Adv:2.2.2.2 SEQ:80000001 AGE:3600
Type:2001, LSID:00000000 Adv:2.2.2.2 SEQ:80000031 AGE:1
OSPFv3: Snd LSUpdate on ethe 3/9(fe80::204:80ff:fe2c:c048->ff02::5)
Type:2009, LSID:00000000 Adv:1.2.3.4 SEQ:80000001 AGE:3600
Type:2009, LSID:00000000 Adv:1.2.3.4 SEQ:80000001 AGE:3600
OSPFv3: Rcv LSUpdate on ethe 3/9(fe80::2e0:52ff:feda:c347->ff02::5)
Type:2001, LSID:00000000 Adv:2.2.2.2 SEQ:80000032 AGE:1
Syntax: [no] debug ipv6 ospf packet-lsa-update
Possible values: N/A
Default value: N/A
debug ipv6 ospf route
Displays information about routes calculated by a OSPF version 3 router. The router calculates the following route
types: external, inter-area, intra-area, Shortest Path First (SPF), and transit.
EXAMPLE:
ProCurveRS debug ipv6 ospf route
3 - 38 June 2005
Page 53
HP Diagnostic Command Reference
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf route command.
OSPFv3:Route calculation started at 69351
OSPFv3 SPF: Calculation for area 0.0.0.0
OSPFv3 SPF: installing vertex 1.2.3.4
OSPFv3 SPF: 2.2.2.2:136 is the first hop
OSPFv3 SPF : 2.2.2.2:136 nexthop :: ifindex 137
OSPFv3 SPF: Examining Vertex: 2.2.2.2:136
OSPFv3 SPF: new node added to candidate list: 2.2.2.2:136
OSPFv3 SPF: installing vertex 2.2.2.2:136
OSPFv3 ROUTE: route created: 2.2.2.2:136
OSPFv3 SPF : 2.2.2.2:0 nexthop fe80::2e0:52ff:feda:c347 ifindex 137
OSPFv3 SPF: Examining Vertex: 2.2.2.2:0
OSPFv3 SPF: new node added to candidate list: 2.2.2.2:0
OSPFv3 SPF: Ignore link description to myself
OSPFv3 SPF: installing vertex 2.2.2.2:0
OSPFv3 ROUTE: route created: 2.2.2.2:0
OSPFv3 SPF: 2.2.2.2:136 inherits 2.2.2.2:0's nexthop_list
OSPFv3 SPF: Examining Vertex: 2.2.2.2:136
OSPFv3 SPF: already in SPF tree: 2.2.2.2:136
OSPFv3 SPF: Calculation for area 0.0.0.0 done
OSPFv3: Calculating Intra Area routes for area 0.0.0.0
OSPFv3:INTRA AREA ROUTE: Calculating Intra Area Stub Routes
OSPFv3:INTRA AREA ROUTE: Can't find Prefix LSA for id 0.0.0.0 AdvRouter 1.2.3.4
OSPFv3 :INTRA AREA ROUTE: Can't find Prefix LSA for id 0.0.0.0 AdvRouter 2.2.2.2
OSPFv3 :INTRA AREA ROUTE: found Prefix LSA type : IntraPrefix : for Id 0.0.0.136
Advrouter 2.2.2.2
OSPFv3 :INTRA AREA ROUTE: Intra Area route install 3000:1::/64 cost 1
OSPFv3 ROUTE: route changed, new route preferred: 3000:1::/64
OSPFv3: Intra area route calculation finished at 69352
OSPFv3:Inter Area Prefix route calculation finished at 69353
OSPFv3:Inter Area Router route calculation finished at 69354
OSPFv3 : TRANSIT ROUTE: Discarding routes with nexthop unresolved
OSPFv3:Transit route calculation finished at 69355
OSPFv3:External route calculation finished at 69356
OSPFv3: Generating events due to routing table changes.
ROUTE: Validate routing table
OSPFv3 : Validating route 3000:1::/64
OSPFv3 : Route 3000:1::/64 updated in RIB
OSPFv3: Route calculation finished at 69357
Syntax: [no] debug ipv6 ospf route
Possible values: N/A
Default value: N/A
debug ipv6 ospf route-calc-external
Displays information about external routes calculated by an OSPF version 3 router.
EXAMPLE:
ProCurveRS debug ipv6 ospf route-calc-external
June 2005 3 - 39
Page 54
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf route-calc-external command.
OSPFV3 :EXTERNAL ROUTE INCREMENTAL: Calculating route from external LSA (Id =2,
Advrtr = 1.2.3.4
OSPFV3 :EXTERNAL ROUTE INCREMENTAL: External LSA is self originated
Syntax: [no] debug ipv6 ospf route-calc-external
Possible values: N/A
Default value: N/A
debug ipv6 ospf route-calc-inter-area
Displays information about inter-area routes calculated by an OSPF version 3 router.
EXAMPLE:
ProCurveRS debug ipv6 ospf route-calc-inter-area
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf route-calc-inter-area command.
OSPFV3 :INTER AREA ROUTE: Inter Area Prefix LSA(I D= 1) is Self-originated:
Syntax: [no] debug ipv6 ospf route-calc-inter-area
Possible values: N/A
Default value: N/A
debug ipv6 ospf route-calc-intra-area
Displays information about intra-area routes calculated by an OSPF version 3 router.
EXAMPLE:
ProCurveRS debug ipv6 ospf route-calc-intra-area
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf route-calc-intra-area command.
OSPFv3: Calculating Intra Area routes for area 0.0.0.0
OSPFv3:INTRA AREA ROUTE: Calculating Intra Area Stub Routes
OSPFv3:INTRA AREA ROUTE: Can't find Prefix LSA for id 0.0.0.0 AdvRouter 3.3.3.3
OSPFv3 :INTRA AREA ROUTE: Can't find Prefix LSA for id 0.0.0.0 AdvRouter 2.2.2.2
OSPFv3 :INTRA AREA ROUTE: found Prefix LSA type : IntraPrefix : for Id 0.0.0.137
Advrouter 3.3.3.3
OSPFv3 :INTRA AREA ROUTE: Intra Area route install 3000:1::/64 cost 1
OSPFv3: Calculating Intra Area routes for area 0.0.0.1
OSPFv3:INTRA AREA ROUTE: Calculating Intra Area Stub Routes
OSPFv3 :INTRA AREA ROUTE: found Prefix LSA type : IntraPrefix : for Id 0.0.0.0 A
dvrouter 3.3.3.3
OSPFv3:INTRA AREA ROUTE: Intra Area route install 3000:2::/64 cost 0
Syntax: [no] debug ipv6 ospf route-calc-intra-area
Possible values: N/A
Default value: N/A
3 - 40 June 2005
Page 55
HP Diagnostic Command Reference
debug ipv6 ospf route-calc-spf
Displays information about SPF routes calculated by an OSPF version 3 router.
EXAMPLE:
ProCurveRS debug ipv6 ospf route-calc-spf
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf route-calc-spf command.
OSPFv3 SPF: Calculation for area 0.0.0.0
OSPFv3 SPF: installing vertex 1.2.3.4
OSPFv3 SPF: 2.2.2.2:136 is the first hop
OSPFv3 SPF : 2.2.2.2:136 nexthop :: ifindex 137
OSPFv3 SPF: Examining Vertex: 2.2.2.2:136
OSPFv3 SPF: new node added to candidate list: 2.2.2.2:136
OSPFv3 SPF: installing vertex 2.2.2.2:136
OSPFv3 SPF : 2.2.2.2:0 nexthop fe80::2e0:52ff:feda:c347 ifindex 137
OSPFv3 SPF: Examining Vertex: 2.2.2.2:0
OSPFv3 SPF: new node added to candidate list: 2.2.2.2:0
OSPFv3 SPF: Ignore link description to myself
OSPFv3 SPF: installing vertex 2.2.2.2:0
OSPFv3 SPF: 2.2.2.2:136 inherits 2.2.2.2:0's nexthop_list
OSPFv3 SPF: Examining Vertex: 2.2.2.2:136
OSPFv3 SPF: already in SPF tree: 2.2.2.2:136
OSPFv3 SPF: Calculation for area 0.0.0.0 done
OSPFv3 SPF: Calculation for area 0.0.0.1
OSPFv3 SPF: installing vertex 1.2.3.4
OSPFv3 SPF: Calculation for area 0.0.0.1 done
Syntax: [no] debug ipv6 ospf route-calc-spf
Possible values: N/A
Default value: N/A
debug ipv6 ospf route-calc-transit
Displays information about transit routes calculated by an OSPF version 3 router.
EXAMPLE:
ProCurveRS debug ipv6 ospf route-calc-transit
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf route-calc-transit command.
OSPFv3 : TRANSIT ROUTE: Discarding routes with nexthop unresolved
Syntax: [no] debug ipv6 ospf route-calc-transit
Possible values: N/A
Default value: N/A
debug ipv6 ospf route-install
Displays information about routes added or removed from the OSPF version 3 route table.
EXAMPLE:
ProCurveRS debug ipv6 ospf route-install
June 2005 3 - 41
Page 56
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ospf route-install command.
OSPFv3 ROUTE: route created: 3000:2::/64
ROUTE: Validate routing table
OSPFv3 : Validating route 3000:1::/64
OSPFv3 : Validating route 3000:2::/64
OSPFv3 : Route 3000:2::/64 added to RIB
Syntax: [no] debug ipv6 ospf route-install
Possible values: N/A
Default value: N/A
debug ipv6 packet
Displays basic header and port information for IPv6 packets transmitted and received by an HP device that
supports IPv6.
EXAMPLE:
ProCurveRS debug ipv6 packet
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 packet command.
IPv6_TX: 3000:1::2 => 3000:1::6 (00e0.52da.c347)
NextHeader:58, size:32 (72), vlan:1, Port: 136 (136)
Syntax: [no] debug ipv6 packet
Possible values: N/A
Default value: N/A
debug ipv6 ra
Displays information when an HP device that supports IPv6 sends and receives router solicitation and
advertisement messages, which verify the existence of a new router or an existing router that has become
unreachable.
EXAMPLE:
ProCurveRS debug ipv6 ra
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ra command.
Periodical RA advertisement (200 seconds by default)
ICMPv6-RA: Sent RA to ff02::1 on port 3/9
ICMPv6-RA: prefix 3000:1::/64, lifetime 2592000/604800, onlink, autoconfig
ICMPv6-RA: Received RA from fe80::2e0:52ff:feda:c347 on port 3/9
Syntax: [no] debug ipv6 ra
Possible values: N/A
Default value: N/A
3 - 42 June 2005
Page 57
HP Diagnostic Command Reference
debug ipv6 rip events
Displays information when RIP events, such as adding or removing RIP interfaces or routes, changing the setting
of RIP timers, and detecting activity on a RIP port, occur.
EXAMPLE:
ProCurveRS debug ipv6 rip events
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 ra command.
RIPng: Removing local connected route 3000:1::2/64 on interface 3/9
RIPng: garbage prefix 3000:1::/64 timer 16, metric 0, tag 0
from :: on interface Ethernet 3/9
RIPng: stop running on interface 3/9
RIPng: Removing local connected route 3000:1::2/64 on interface 3/9
Syntax: [no] debug ipv6 rip events
Possible values: N/A
Default value: N/A
debug ipv6 rip receive
Displays information about all RIP packets received by an HP device that supports IPv6 or only those RIP packets
received by a specified port or tunnel on the HP device.
EXAMPLE:
ProCurveRS debug ipv6 rip receive ethernet 3
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 rip receive command.
RIPng: received packet from fe80::2e0:52ff:feda:c347 port 521 on interface 3
command response version 1 packet size 24
prefix 3000:1::/64 metric 1 tag 0
Syntax: [no] debug ipv6 rip receive ethernet <port-number> | tunnel <number> | ve <number>
Possible values: Ethernet port number, tunnel number, or virtual Ethernet (ve) number.
Default value: N/A
debug ipv6 rip transmit
Displays information about all RIP packets sent by an HP device that supports IPv6 or only those RIP packets sent
by a specified port or tunnel on the HP device.
EXAMPLE:
ProCurveRS debug ipv6 rip transmit ethernet 3
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 rip transmit command.
RIPng: Sending update on interface 3/9
src fe80::204:80ff:fe2c:c048, port 521
dest ff02::9 (3/9), port 521
command response version 1 packet size 24
prefix 3000:1::/64 metric 1 tag 0
Syntax: [no] debug ipv6 rip transmit ethernet <port-number> | tunnel <number> | ve <number>
June 2005 3 - 43
Page 58
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Possible values: Ethernet port number, tunnel number, or virtual Ethernet (ve) number.
Default value: N/A
debug ipv6 routing
Displays information when entries in the IPv6 route table are added, removed, and changed.
EXAMPLE:
ProCurveRS debug ipv6 routing
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug ipv6 routing command.
IPv6RT0: Remove 3000:1::/64 (connected) from rib
IPv6RT0: un-install (connected)
IPv6RT0: Add 3000:1::/64 (connected) to rib
IPv6RT0: install (connected
Syntax: [no] debug ipv6 routing
Possible values: N/A
Default value: N/A
debug spanning
Displays information about BPDU packets.
EXAMPLE:
ProCurveRS# debug spanning
After you enter this command, messages such as the following appear at the destination specified for debugging
output. You can turn off these messages with the no debug spanning command.
ST: Port 2/1
[A] [B][C][D] [E] [F]
0000 00 00 00 800000e052c37d40 00000000
[G] [H][I] [J] [K] [L] [M]
800000e052c37d40 20 40 0000 0014 0002 000f
Table 3.5 describes the contents of debug spanning message. Note that the letters in brackets do not appear in
the output.
Table 3.5: Output from the debug spanning command
This Field...
ST:
Displays...
Indicates that this is a spanning tree packet
Port 2/1
[A] 0000
[B] 00
3 - 44 June 2005
Interface receiving the packet
Indicates that this is an IEEE BDPU packet.
Version number.
Page 59
HP Diagnostic Command Reference
Table 3.5: Output from the debug spanning command (Continued)
This Field...
[C] 00
[D] 00
[E] 800000e052c37d40
[F] 00000000
[G] 800000e052c37d40
[H] 20
[I] 40
[J] 0000
[K] 0014
[L] 0002
[M] 000f
Displays...
Command mode. This can be one of the following:
00 Config BPDU
80 Topology Change Notification BPDU
Acknowledgement of topology change. This can be one of the following:
00 No change
80 Change notification
Root ID.
Root path cost.
Bridge ID.
Port priority.
Por t number.
Message age in 1/256 seconds.
Maximum age in 1/256 seconds.
Hello time in 1/256 seconds.
Forward delay in 1/256 seconds.
Syntax: [no] debug spanning
Possible values: N/A
Default value: N/A
ipv6 debug route-table disable-cache
This command is for HP internal use only.
ipv6 debug route-table main
This command is for HP internal use only.
ipv6 debug route-table rip
This command is for HP internal use only.
mm
Displays the contents of a specified address on every module.
EXAMPLE:
ProCurveRS# mm 0190044c
(4)0190044c: 0000 0000 0000 0000 0000 0000 0000 0000
(4)0190045c: 0000 0000 0000 0000 0000 0000 0000 0000
(4)0190046c: 0000 0000 0000 0000 0000 0000 0000 0000
(4)0190047c: 0000 0000 0000 0000 0000 0000 0000 0000
1e90044c: 0000044c 00000450 00000454 00000458
1e90045c: 0000045c 00000460 00000464 00000468
1e90046c: 0000046c 00000470 00000474 00000478
1e90047c: 0000047c 00000480 00000484 00000488
June 2005 3 - 45
Page 60
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Syntax: mm <address> [<length>]
Possible values: <length> can be up to 0x40 bytes.
Default value: If you do not specify the <length> parameter, 0x40 bytes are displayed.
phy
Displays information about PHY registers for a specified port. This command can be useful for resolving problems
with NIC adapters that have linking problems
3 - 46 June 2005
Page 61
HP Diagnostic Command Reference
EXAMPLE:
.
ProCurveRS# phy 4/11
BCR reg 0, val = 1100
BSR reg 1, val = 7809
ID1 reg 2, val = 7810
ID2 reg 3, val = 0043
ANA reg 4, val = 01e1
ANLPA reg 5, val = 0000
ANE reg 6, val = 0000
MR reg 16, val = 0c00
IER reg 17, val = 0000
ISR reg 18, val = 4000
CR reg 19, val = 0000
CSR reg 20, val = 048b
/* Register 1: Basic Status Register (PHY_BSR_R) */
#define BSR_100BASE_T4 0x8000
#define BSR_100BASE_TX_FD
#define BSR_100BASE_TX_HD
#define BSR_10BASE_T_FD
#define BSR_10BASE_T_HD
#define BSR_AUTO_NEGO_DONE
#define BSR_REMOTE_FAULT
#define BSR_AUTO_NEGO_ABL
#define BSR_LINK_UP
0x4000
0x2000
0x1000
0x0800
0x0020
0x0010
0x0008
0x0004
/* Register 4: Auto-Negotiation Advertisement (PHY_ANA_R) */
#define ANA_NEXT_PAGE 0x8000
#define ANA_REMOTE_FAULT
#define ANA_100BASE_T4
#define ANA_100BASE_TX_FD
#define ANA_100BASE_TX
#define ANA_10BASE_T_FD
#define ANA_10BASE_T
#define ANA_SELECTOR_FIELD
0x2000
0x0200
0x0100
0x0080
0x0040
0x0020
0x001F
/* Register 5: Auto-Negotiation Link Partner Ability (PHY_ANLPA_R) */
#define ANL_NEXT_PAGE 0x8000
#define ANL_ACK 0x4000
#define ANL_REMOTE_FAULT 0x2000
#define ANL_100BASE_T4 0x0200
#define ANL_100BASE_TX_FD 0x0100
#define ANL_100BASE_TX 0x0080
#define ANL_10BASE_T_FD 0x0040
#define ANL_10BASE_T 0x0020
#define ANL_SELECTOR_FIELD 0x001F
#define BPC_OP_100B_FD 0x0018
#define BPC_OP_ISOLATE 0x001C
#define BPC_MLT3_DISAB 0x0002
#define BPC_SCRAMB_DISAB 0x0001
June 2005 3 - 47
Page 62
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
/* Register 31: BASE-TX PHY Control (PHY_BPC_R) */
#define BPC_DISABLE_REC 0x2000
#define BPC_AUTO_NEG_CPL 0x1000
#define BPC_COMPENSAT_MASK 0x0C00
#define BPC_NO_COMPENSAT 0
#define BPC_HALF_COMPENSAT 0x0400
#define BPC_FULL_COMPENSAT 0x0800
#define BPC_AUTO_COMPENSAT 0x0C00
#define BPC_RLBEN 0x0200
#define BPC_DCREN 0x0100
#define BPC_NRZIEN 0x0080
#define BPC_4B5BEN 0x0040
#define BPC_TX_ISOLATE 0x0020
#define BPC_OPMODE_MASK 0x001C
#define BPC_OP_STILL_NEG 0x0000
#define BPC_OP_10B_HD 0x0004
#define BPC_OP_100B_HD 0x0008
#define BPC_OP_100B_T4 0x0010
#define BPC_OP_10B_FD 0x0014
#define BPC_OP_100B_FD 0x0018
#define BPC_OP_ISOLATE 0x001C
#define BPC_MLT3_DISAB 0x0002
#define BPC_SCRAMB_DISAB 0x0001
Syntax: phy <slot/port>
Possible values: <slot/port> must be a valid port on the device.
Default value: N/A
ptrace aaa
Toggles tracing for AAA packets.
EXAMPLE:
ProCurveRS# ptrace aaa
Syntax: ptrace aaa
Possible values: N/A
Default value: N/A
ptrace appletalk aarp
Toggles tracing for Appletalk Address Resolution Protocol (AARP) packets. When you enable this function, each
time an AARP packet is encountered, a message appears on the console indicating whether the packet was
transmitted or received, the port on which it was transmitted or received, and the data field of the packet.
EXAMPLE:
ProCurveRS# ptrace appletalk aarp
Syntax: ptrace appletalk aarp
Possible values: N/A
Default value: N/A
ptrace appletalk aep
Toggles tracing for Appletalk Echo Protocol (AEP) packets. When you enable this function, each time an AEP
packet is encountered, a message appears on the console indicating whether the packet was transmitted or
received, the port on which it was transmitted or received, and the contents of the packet’s Datagram Delivery
Protocol (DDP) header.
3 - 48 June 2005
Page 63
HP Diagnostic Command Reference
EXAMPLE:
ProCurveRS# ptrace appletalk aep
Syntax: ptrace appletalk aep
Possible values: N/A
Default value: N/A
ptrace appletalk nbp
Toggles tracing for Appletalk Name Binding Protocol (NBP) packets. When you enable this function, each time an
NBP packet is encountered, a message appears on the console indicating whether the packet was transmitted or
received, the port on which it was transmitted or received, and the contents of the packet’s DDP header.
EXAMPLE:
ProCurveRS# ptrace appletalk nbp
Syntax: ptrace appletalk nbp
Possible values: N/A
Default value: N/A
ptrace appletalk none
Disables tracing for all Appletalk packets.
EXAMPLE:
ProCurveRS# ptrace appletalk none
Syntax: ptrace appletalk none
Possible values: N/A
Default value: N/A
ptrace appletalk rtmp
Toggles tracing for Appletalk Routing Table Maintenance Protocol (RTMP) packets. When you enable this function,
each time an RTMP packet is encountered, a message appears on the console indicating whether the packet was
transmitted or received, the port on which it was transmitted or received, and the contents of the packet’s DDP
header.
EXAMPLE:
ProCurveRS# ptrace appletalk rtmp
Syntax: ptrace appletalk rtmp
Possible values: N/A
Default value: N/A
ptrace appletalk states
Toggles tracing for Appletalk state transition packets.
EXAMPLE:
ProCurveRS# ptrace appletalk states
Syntax: ptrace appletalk states
Possible values: N/A
Default value: N/A
June 2005 3 - 49
Page 64
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
ptrace appletalk zip
Toggles tracing for Appletalk Zone Information Protocol (ZIP) packets. When you enable this function, each time a
ZIP packet is encountered, a message appears on the console indicating whether the packet was transmitted or
received, the port on which it was transmitted or received, and the contents of the packet’s DDP header.
EXAMPLE:
ProCurveRS# ptrace appletalk zip
Syntax: ptrace appletalk zip
Possible values: N/A
Default value: N/A
ptrace arp
Toggles tracing for ARP packets.
EXAMPLE:
ProCurveRS# ptrace arp
Syntax: ptrace arp
Possible values: N/A
Default value: N/A
ptrace bootp
Toggles tracing for BOOTP packets.
EXAMPLE:
ProCurveRS# ptrace bootp
Syntax: ptrace bootp
Possible values: N/A
Default value: N/A
ptrace dvmrp graft
Toggles tracing for DVMRP graft packets.
EXAMPLE:
ProCurveRS# ptrace dvmrp graft
Syntax: ptrace dvmrp graft
Possible values: N/A
Default value: N/A
ptrace dvmrp graft-ack
Toggles tracing for DVMRP graft-ack packets.
EXAMPLE:
ProCurveRS# ptrace dvmrp graft-ack
Syntax: ptrace dvmrp graft-ack
Possible values: N/A
Default value: N/A
ptrace dvmrp mcache
Toggles tracing for DVMRP mcache packets.
3 - 50 June 2005
Page 65
EXAMPLE:
ProCurveRS# ptrace dvmrp mcache
Syntax: ptrace dvmrp mcache
Possible values: N/A
Default value: N/A
ptrace dvmrp message
Toggles tracing for DVMRP message packets.
EXAMPLE:
ProCurveRS# ptrace dvmrp message
Syntax: ptrace dvmrp message
Possible values: N/A
Default value: N/A
ptrace dvmrp none
Disables tracing for DVMRP packets.
EXAMPLE:
ProCurveRS# ptrace dvmrp none
HP Diagnostic Command Reference
Syntax: ptrace dvmrp none
Possible values: N/A
Default value: N/A
ptrace dvmrp probe
Toggles tracing for DVMRP probe packets.
EXAMPLE:
ProCurveRS# ptrace dvmrp probe
Syntax: ptrace dvmrp probe
Possible values: N/A
Default value: N/A
ptrace dvmrp prune
Toggles tracing for DVMRP prune packets.
EXAMPLE:
ProCurveRS# ptrace dvmrp prune
Syntax: ptrace dvmrp prune
Possible values: N/A
Default value: N/A
ptrace dvmrp route-table
Toggles tracing for DVMRP route-table packets.
EXAMPLE:
ProCurveRS# ptrace dvmrp route-table
Syntax: ptrace dvmrp route-table
Possible values: N/A
June 2005 3 - 51
Page 66
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Default value: N/A
ptrace icmp
Toggles tracing for ICMP packets.
EXAMPLE:
ProCurveRS# ptrace icmp
Syntax: ptrace icmp
Possible values: N/A
Default value: N/A
ptrace igmp
Toggles tracing for IGMP packets.
EXAMPLE:
ProCurveRS# ptrace igmp
Syntax: ptrace igmp
Possible values: N/A
Default value: N/A
ptrace ip
Toggles tracing for IP packets.
EXAMPLE:
ProCurveRS# ptrace ip
Syntax: ptrace ip
Possible values: N/A
Default value: N/A
ptrace none
Disables all packet tracing.
EXAMPLE:
ProCurveRS# ptrace none
Syntax: ptrace ip
Possible values: N/A
Default value: N/A
ptrace ospf
Toggles tracing for OSPF packets.
EXAMPLE:
ProCurveRS# ptrace ospf
Syntax: ptrace ospf
Possible values: N/A
Default value: N/A
ptrace pim fcache
Toggles tracing for PIM fcache packets.
3 - 52 June 2005
Page 67
EXAMPLE:
ProCurveRS# ptrace pim fcache
Syntax: ptrace pim fcache
Possible values: N/A
Default value: N/A
ptrace pim mcache
Toggles tracing for PIM mcache packets.
EXAMPLE:
ProCurveRS# ptrace pim mcache
Syntax: ptrace pim mcache
Possible values: N/A
Default value: N/A
ptrace pim message
Toggles tracing for PIM message packets.
EXAMPLE:
ProCurveRS# ptrace pim message
HP Diagnostic Command Reference
Syntax: ptrace pim message
Possible values: N/A
Default value: N/A
ptrace pim none
Disables tracing for PIM packets.
EXAMPLE:
ProCurveRS# ptrace pim none
Syntax: ptrace pim none
Possible values: N/A
Default value: N/A
ptrace ppp
Toggles tracing for PPP packets.
EXAMPLE:
ProCurveRS# ptrace ppp
Syntax: ptrace ppp
Possible values: N/A
Default value: N/A
ptrace rarp
Toggles tracing for RARP packets.
EXAMPLE:
ProCurveRS# ptrace rarp
Syntax: ptrace rarp
Possible values: N/A
June 2005 3 - 53
Page 68
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Default value: N/A
ptrace rip
Toggles tracing for RIP packets.
EXAMPLE:
ProCurveRS# ptrace rip
Syntax: ptrace rip
Possible values: N/A
Default value: N/A
ptrace snmp
Toggles tracing for SNMP packets.
EXAMPLE:
ProCurveRS# ptrace snmp
Syntax: ptrace snmp
Possible values: N/A
Default value: N/A
ptrace switch none
Disables packet tracing started with the ptrace switch stp command.
EXAMPLE:
ProCurveRS# ptrace switch none
Syntax: ptrace switch none
Possible values: N/A
Default value: N/A
ptrace switch stp
Toggles tracing for STP packets.
EXAMPLE:
ProCurveRS# ptrace switch stp
Syntax: ptrace switch stp
Possible values: N/A
Default value: N/A
ptrace tcp
Toggles tracing for TCP packets.
EXAMPLE:
ProCurveRS# ptrace tcp
Syntax: ptrace tcp
Possible values: N/A
Default value: N/A
ptrace telnet
Toggles tracing for Telnet packets.
3 - 54 June 2005
Page 69
EXAMPLE:
ProCurveRS# ptrace telnet
Syntax: ptrace telnet
Possible values: N/A
Default value: N/A
ptrace term
Sends packet tracing output to the current terminal.
EXAMPLE:
ProCurveRS# ptrace term
debug output is now sent to this terminal
Syntax: ptrace term
Possible values: N/A
Default value: Packet tracing output is sent to the console by default.
ptrace tftp
Toggles tracing for TFTP packets.
EXAMPLE:
ProCurveRS# ptrace tftp
Syntax: ptrace tftp
Possible values: N/A
HP Diagnostic Command Reference
Default value: N/A
ptrace udp
Toggles tracing for UDP packets.
EXAMPLE:
ProCurveRS# ptrace udp
Syntax: ptrace udp
Possible values: N/A
Default value: N/A
show ip bgp debug
Displays BGP debugging information for the router.
June 2005 3 - 55
Page 70
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
EXAMPLE:
ProCurveRS# show ip bgp debug
BGP4 Debug Information
Pid SBlock TBlocks UBlocks FBlocks EBlocks SAddress CAddress
0 16 10000 26 9973 0 04e6c16a 04e6c372
1 32 10000 9240 758 0 04e9cec2 04ebd0be
2 64 10000 41 9958 0 04ef4d1a 04ef504a
3 150 200 2 197 0 04f9ad72 04f9ae0c
4 22 67000 64404 2596 0 04fa25da 05030d1e
5 30 144000 131768 12228 0 0514baa2 0537b84e
6 74 67000 65886 1113 0 055f6fba 059d3c52
7 72 10000 9309 689 0 05af2de2 05b90822
Total Memory Use for Route and Attributes Tables : 13894800
Memory Block Not Available Count : 0
Maximum Number of Attribute Entries Supported : 10000
Maximum Number of Routes Supported : 67000
Maximum Number of Peers Supported : 3
BGP Route Table Full Count : 0
Bad Memory Pool ID Count : 0
Bad Memory Address Count : 0
debug ip bgp errors
debug ip bgp event
debug ip bgp state
The following table describes the output from the show ip bgp debug command:
Table 3.6: Output from the show ip bgp debug command
Statistic
Pid
SBlock
TBlocks
UBlocks
FBlocks
EBlocks
SAddress
CAddress
Total Memory Use for Route and Attributes
Ta bl e s
Memory Block Not Available Count Number of times that a memory block was not available.
Maximum Number of Attribute Entries Number of attribute entries the router’s memory can hold. An
Supported attribute entry is a set of route attributes that are associated
Description
Memory pool ID 0 – 7
Size of the memory blocks in the memory pool.
Total number of blocks in the memory pool.
Number of used blocks in the memory pool.
Number of free blocks in the memory pool.
Number of error blocks
Starting address of the memory pool.
Ending address of the memory pool.
Amount of memory available for the BGP4 route and
attributes tables.
with one or more routes.
Maximum Number of Routes Supported
3 - 56 June 2005
Number of BGP4 routes the router’s memory can hold.
Page 71
HP Diagnostic Command Reference
Table 3.6: Output from the show ip bgp debug command (Continued)
Statistic
Maximum Number of Peers Supported Number of BGP4 peers the router can have.
BGP Route Table Full Count How many times a route could not be added to the BGP route
Bad Memory Pool ID Count
Bad Memory Address Count
debug ip bgp errors
debug ip bgp event
debug ip bgp state
Syntax: show ip bgp debug
Possible values: N/A
Default value: N/A
Description
table because the route table was full.
Number of times a memory pool was reported as bad. If
there is a non-zero value in this field, contact HP technical
support.
Number of times a memory address was reported as bad. If
there is a non-zero value in this field, contact HP technical
support.
The debug ip bgp options that are currently in effect.
show debug
Lists the debugging options currently in effect on the device.
June 2005 3 - 57
Page 72
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
EXAMPLE:
ProCurveRS# debug all
ProCurveRS# show debug
Debug message destination: Console
IP Routing:
BGP:
bgp debugging is on
BGP:
neighbor 0.0.0.0 debugging is on
BGP:
dampening debugging is on
BGP:
events debugging is on
BGP:
inbound information debugging is on
BGP:
keepalives debugging is on
BGP:
outbound information debugging is on
BGP:
updates debugging is on
OSPF:
OSPF:
OSPF:
OSPF:
OSPF:
OSPF:
OSPF:
OSPF:
OSPF:
VRRP:
VRRP:
IP Multicast:
DVMRP:
DVMRP:
DVMRP:
VRRP:
VRRP:
IGMP:
Generic IP:
IGMP:
ICMP:
ICMP:
adjacency events debugging is on
database timer debugging is on
events debugging is on
flooding debugging is on
lsa generation debugging is on
packet debugging is on
retransmission debugging is on
spf debugging is on
tree debugging is on
RIP:
rip debugging is on
RIP:
database debugging is on
RIP:
events debugging is on
RIP:
trigger debugging is on
events debugging is on
packet debugging is on
dvmrp debugging is on
detail debugging is on
pruning debugging is on
PIM:
pim debugging is on
PIM:
events debugging is on
PIM:
group 0.0.0.0 debugging is on
events debugging is on
packet debugging is on
IGMP debugging is on
TCP:
driver debugging is on
TCP:
intercept debugging is on
TCP:
packet debugging is on
TCP:
rcmd debugging is on
TCP:
sack debugging is on
TCP:
transactions debugging is on
UDP:
debugging is on
IGMP debugging is on
events debugging is on
packets debugging is on
Syntax: show debug
Possible values: N/A
Default value: N/A
3 - 58 June 2005
Page 73
Chapter 4
Using the Backplane Debugging Commands
For debugging purposes, you can monitor information about the backplane hardware on a Chassis device. When
the backplane debugging feature is enabled, every 30 seconds the device checks the following counters: SMC
DMA Drop counters (DMADrop), SMC Backplane Drop counters (BPDrop), BM Free Queue Depth counters
(FreeDepth), and BM Write Sequence Drop counters (WriteDrop). The device generates a Syslog message when
any of the following conditions are true:
• DMADrop count is non-zero
• BPDrop count is non-zero
• WriteDrop count is greater than or equal to 1,500 increments per 30 seconds
• If the queue depth indicated by the FreeDepth counters is 120 less than the management module’s
approximate maximum free queue depth for 3 consecutive measurements.
• On T-Flow Redundant Management Module, the maximum free queue depth is approximately 4000.
• On Management 4 modules, the maximum free queue depth is approximately 3960.
• On Management 1 and Management 2, the maximum free queue depth is approximately 890.
To enable the backplane debugging feature, enter the following command:
ProCurveRS# debug hw
Syntax: [no] debug hw
To disable the backplane debugging feature, enter one of the following commands:
ProCurveRS# no debug hw
or
ProCurveRS# undebug hw
Syntax: undebug hw
Entering the no debug hw or undebug hw commands stops the backplane debugging feature, but does not clear
the WriteDrop counters (the other counters are cleared once they are read). To clear the WriteDrop counters, you
can either reboot the device, or enter the following command:
ProCurveRS# clear hw writedrop
Syntax: clear hw writedrop
June 2005 4 - 1
Page 74
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Table 4.1 describes the Syslog messages that can appear when the backplane debugging feature is enabled.
Table 4.1: Syslog messages generated by the backplane debugging feature
Message Level Message Explanation
Alert Slot <num> SMC <num> Drop counter is
<num>
Alert Slot <num> BP <num> Drop counter is
<num>
When the backplane debugging feature is
enabled, the first time the SMC DMA Drop
(DMADrop) counter is non-zero, the device
generates a Syslog message and an SNMP
trap.
When the first Syslog message indicating a
non-zero DMADrop count is generated, the
device starts a five-minute timer. After five
minutes, the device generates a Syslog
message if the DMADrop count is non-zero
at least once during this five-minute period.
Slot <num> is the slot number that contains
the module.
SMC <num> indicates the Strip Memory
Controller (SMC) ASIC.
Drop counter is <num> indicates the total
number of SMC DMA drops during the fiveminute period.
When the backplane debugging feature is
enabled, the first time the SMC Backplane
Drop (BPDrop) counter is non-zero, the
device generates a Syslog message and an
SNMP trap.
When the first Syslog message indicating a
non-zero BPDrop count is generated, the
device starts a five-minute timer. After five
minutes, the device generates a Syslog
message if the BPDrop count is non-zero at
least once during this five-minute period.
Slot <num> is the slot number that contains
the module.
BP <num> is the current value of the BPDrop
counter.
Drop counter is <num> indicates the total
number of SMC backplane drops during the
five-minute period.
4 - 2 June 2005
Page 75
Using the Backplane Debugging Commands
Table 4.1: Syslog messages generated by the backplane debugging feature
Message Level Message Explanation
Warning Slot <num> <module> Free Queue
decreases less than the desirable values 3
consecutive times.
Informational Slot <num> Write Sequence Drop <num>
within 30 seconds
The module’s BM Free Queue Depth
(FreeDepth) has been recorded at 120 less
than the maximum for the module for three
consecutive measurements.
• On Management V modules, the
maximum free queue depth is
approximately 4000.
• On Management IV modules, the
maximum free queue depth is
approximately 3960.
• On Management 1 and Management 2,
the maximum free queue depth is
approximately 890.
Slot <num> <module> is the slot number that
contains the module and the kind of module.
The BM Write Sequence Drop (WriteDrop)
counter is greater or equal to 1,500
increments per 30 seconds.
Slot <num> is the slot number that contains
the module.
Write Sequence Drop <num> is the current
value of the WriteDrop counter.
To display the status of the backplane counters, enter the following command:
ProCurveRS# show backplane
_____________________________________________________________
Slot Mod FreeQ DMADrop BPDrop WriteDrop Last
------------------------------------------------------------3 BxGMR4 3988 0 0 252 D:0 H:0 M:20S:5
4 B24E 900 0 0 0 NEVER
Syntax: show backplane
The show backplane command displays the status of the backplane counters since the last boot (for the
WriteDrop counters, either the last boot or the last time the counters were cleared with the clear hw writedrop
command).
This Field... Displays...
Slot The slot number for the module.
Mod The module type.
FreeQ The module’s BM free queue depth counter.
DMADrop The sum of the module’s four SMC DMA drop counters.
Table 4.2 describes the output from the show backplane command.
Table 4.2: Output from the show backplane command
June 2005 4 - 3
Page 76
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Table 4.2: Output from the show backplane command (Continued)
This Field...
BPDrop
WriteDrop
Last
Displays...
The sum of the module’s four SMC backplane drop counters.
The module’s BM write sequence drop counter.
The last time an event was recorded. If any SMC DMA drops or SMC backplane drops
have occurred, the time of the last drop is displayed. If there have been no SMC DMA
drops or SMC backplane drops, the time of the BM write sequence drop is displayed.
If there have been no drops at all, then NEVER is displayed.
4 - 4 June 2005
Page 77
Chapter 5
Changing CAM Partitions
You can adjust the percentage of a module’s CAM that can store Layer 2, Layer 3, or Layer 4 entries. In releases
prior to 07.6.01b, CAM partitioning was not configurable. Starting in release 07.6.01b, you can specify the
percentage of CAM assigned to each of the CAM entry types, both on a global and per-module basis. After you
reboot the HP device, the user-specified CAM partitions take effect.
This chapter is divided into the following sections:
• “CAM Overview” on page 5-1 below
• “Using the CLI to Configure CAM Partitioning” on page 5-2
• “Displaying CAM Partitioning Information” on page 5-4
CAM Overview
Content Addressable Memory (CAM) is a component of HP modules that facilitates hardware forwarding. As
packets flow through the HP device from a given source to a given destination, the management processor
records forwarding information about the flow in CAM entries. A CAM entry generally contains next-hop
information, such as the outgoing port, the MAC address of the next-hop router, VLAN tag, and so on. Once the
HP device has this information in its CAM, packets with the same source and destination can be forwarded by
hardware without the aid of the management processor, speeding up forwarding time.
CAM entries can contain Layer 2, Layer 3, or Layer 4 information. Each type of CAM entry has its own format.
Layer 2 CAM entries contain destination MAC information; Layer 3 CAM entries contain destination IP information;
Layer 4 CAM entries contain destination IP, destination TCP/UDP port, source IP, and source TCP/UDP port
information. Layer 2 entries also deal with 802.1p (priority), and VLAN information.
When the HP device is initialized, the software partitions the available CAM into segments for Layer 2, Layer 3, or
Layer 4 information. The percentage of CAM devoted to each type of CAM entry depends on the software image
running on the device. For example, Routing Switch software may assign a percentage of CAM to Layer 3 and a
percentage to Layer 2/4.
On 9300 series routers, the CAM lookup mechanism involves longest prefix match with up to three levels of
overlapping prefixes. The Layer 3 CAM partition on these devices is divided into three levels of “supernet” host
routes, designated Level1, Level2, and Level3. For Layer 3 IP network routes, Level1 routes precede Level2
routes, and Level2 routes precede Level3 routes. For example, given three routes to program into the CAM,
110.23.24.0/24, 110.23.0.0/16 and 110.0.0.0/8, the device programs 110.23.24.0/24 in Level1, 110.23.0.0/16 in
Level2, and 110.0.0.0/8 in Level3.
The Layer 4 CAM partition is divided into four pools, designated Pool0, Pool1, Pool2, and Pool3. Pools 1 – 3 store
Layer 4 session CAM entries. When no match for an IP packet is found in Pools 1 – 3, an entry for the packet is
made in Pool0. IP packets with CAM entries in Pool0 are sent to the CPU. By default, entries for all packet types
June 2005 5 - 1
Page 78
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
except TCP are programmed into Pool0. When strict ACL TCP mode is enabled (with the ip strict-acl-tcp
command) TCP packets are also programmed into Pool0.
CAM partitioning also depends on the device type and module used: 9300 series devices have different amounts
of CAM available, and Standard (non-EP), Enhanced Performance, and 10 Gigabit Ethernet modules use different
CAM partitioning mechanisms. The following sections list the CAM entry size, amount of CAM, and default CAM
partition size for each of these modules for software images.
CAM Partitioning on Standard Modules
In the Standard architecture, all CAM entries are 64-bits wide, regardless of type.
9300 series Gigabit modules have 1 Mbit of CAM for each set of four ports, for a total of 2 Mbits. 10/100-T
modules have 1 Mbit of CAM for all 24 ports.
For router software images, the default CAM partition is 50 percent Layer 2 entries and 50 percent Layer 3 entries.
In unicast high-performance mode (the default for release 7.5.04 and above) the CAM partition is 75 percent Layer
3 entries and 25 percent Layer 2 entries. On Standard modules, Layer 4 CAM entries are part of the Layer 2
partition.
CAM Partitioning on Enhanced Performance Modules
On EP modules, CAM entries can be 64 bits (for Layer 2 entries) 64 bits (for Layer 3 entries), or 128 bits (for Layer
4 entries). Each 64-bit Layer 3 CAM entry contains two 32-bit IP route entries.
EP module ports are managed by two kinds of custom ASICs:
• Integrated Gigabit Controllers (IGCs) – Ethernet packet controllers for Gigabit ports. Each Gigabit Ethernet
module contains two IGCs.
• Integrated Packet Controllers (IPCs) – Ethernet packet controllers for 10/100 ports. Each 10/100 Ethernet
module contains two IPCs.
Each IGC or IPC has its own CAM space. An IPC or IGC has 2 Mbits for 9300 series modules. An 8-port Gigabit
module has 4 Mbits of CAM and a 16-port Gigabit module has 8 Mbits.
For router software images, the default CAM partition is 50 percent Layer 3 entries, 25 percent Layer 2 entries,
and 25 percent Layer 4 entries. Note that these percentages refer to the amount of CAM space allotted to each
type of CAM entry, not to the actual number of CAM entries, since on EP modules CAM entries of different types
can be different sizes.
CAM Partitioning on 10 Gigabit Ethernet Modules
As with other EP modules, CAM entries on 10 Gigabit Ethernet modules are 64 bits (for Layer 2 entries) 64 bits
(for Layer 3 entries), or 128 bits (for Layer 4 entries). Unlike the other EP modules, 10 Gigabit Ethernet modules
have two CAM banks of 4 Mbits each. One CAM bank is used for Layer 2 destination address entries and Layer 3
entries, and the other CAM bank is used for Layer 2 source address entries and Layer 4 entries.
The amount of CAM space allotted to Layer 2 source address entries must be equal to the amount allotted to
Layer 2 destination address entries. Consequently, if you increase the amount of Layer 2 CAM space, it will
reduce the amount of CAM space for both Layer 3 and Layer 4 entries.
For router software images, one bank of CAM is divided into 25 percent Layer 2 destination address entries and
75 percent Layer 3 entries. The other CAM bank is divided into 25 percent Layer 2 source address entries and 75
percent Layer 4 entries.
Using the CLI to Configure CAM Partitioning
You can configure CAM partitioning on a global or per-module basis. On a Routing Switch image, you can specify
percentages for Layer 2, Layer 3, and Layer 4 CAM entries.
5 - 2 June 2005
Page 79
Changing CAM Partitions
For example, the following command specifies CAM percentages to be applied to all the modules on a ProCurve
Routing Switch running a router image.
l
ProCurveRS(config)# cam-partition
Slot 1 (DMA 0) CAM Partition:
Standard Module, Total Size 1Mbits
L2 232.530029Mbits 88789.002929%, L3 0.75Mbits 75%, L4 232.655029Mbits 88801
.502929%
L3 = 12288 (level2 = 2048, level3 = 2048), Pool0 = 2048, Pool1 = 2048, Pool2
= 544488408, Pool3 = 0
Slot 1 (DMA 2) CAM Partition:
Standard Module, Total Size 1Mbits
L2 232.530029Mbits 88789.002929%, L3 0.75Mbits 75%, L4 232.655029Mbits 88801
.502929%
L3 = 12288 (level2 = 2048, level3 = 2048), Pool0 = 2048, Pool1 = 2048, Pool2
= 544488408, Pool3 = 0
Cold start required. Please write memory and then reload or power cycle.
Syntax: cam-partition l2 <percent> l3 <percent> l4 <percent>
On devices running a router image, you cannot set CAM to zero percent (0%). Also, the minimum value for Layer
4 CAM is one-fourth or 25% of the total CAM.
When you enter the cam-partition command, the HP device attempts to partition the available CAM into the
percentages you specify. Due to internal hardware restrictions, the resulting CAM partitions may not exactly
match the percentages you specify. The device attempts to come as close as possible to match the user-specified
partitions. The new CAM partitioning takes effect after you enter the write memory command and restart the HP
device.
2 0 l3 100 l4 0
The percentages you specify must add up to 100 percent. When you are globally setting CAM partitions on 10
Gigabit Ethernet Modules, the percentage assigned to Layer 3 must equal the percentage assigned to Layer 4.
To specify CAM partitions on an individual module, enter commands such as the following:
ProCurveRS(config)# hw-module 3
ProCurveRS(config-module-3/8)# cam-part l2 10 l3 70 l4 20
Slot 3 (DMA 8) CAM Partition:
Standard Module, Total Size 1Mbits
L2 232.530029Mbits 88789.002929%, L3 0.75Mbits 75%, L4 232.655029Mbits 88801
.502929%
L3 = 12288 (level2 = 2048, level3 = 2048), Pool0 = 2048, Pool1 = 2048, Pool2
= 544488408, Pool3 = 0
Cold start required. Please write memory and then reload or power cycle.
Syntax: hw-module <module>
June 2005 5 - 3
Page 80
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
Displaying CAM Partitioning Information
CAM is shared among multiple DMAs on an HP module. The CAM is accessible by one of the DMAs, called a
master DMA. The show version command displays which DMAs are master DMAs. For example:
HP9304# show version
SW: Version 07.6.04T53 Hewlett-Packard Company
Compiled on Jun 27 2003 at 23:32:30 labeled as H2R07604
(2870842 bytes) from Primary h2r07604.bin
J4139A HP ProCurve Routing Switch 9304M
HW: ProCurve HP9304 Routing Switch, SYSIF version 21, Serial #: Non-exist
==========================================================================
SL 1: J4889A EP 48 port 10/100-TX telco Module, SYSIF 2
Serial #: SA29020286
4096 KB BRAM, EP ASIC IPC version 43, BIA version 89
8192 KB PRAM and 2M-Bit*1 CAM for IPC 0, version 1843
8192 KB PRAM and 2M-Bit*1 CAM for IPC 1, version 1843
==========================================================================
SL 2: J4885A EP 8 port mini-GBIC Management Module, SYSIF 2 (Mini GBIC), M4, ACTIVE
Serial #: CH21028091
4096 KB BRAM, EP ASIC IGC version 47, BIA version 89
32768 KB PRAM and 2M-Bit*1 CAM for IGC 4, version 0447
32768 KB PRAM and 2M-Bit*1 CAM for IGC 5, version 0447
==========================================================================
SL 3: J4891A 2 Port 10Gig 10km Module, SYSIF 2
Serial #: SA18030021
32768 KB BRAM, XPP version 58, XTM version 59
4096 KB PRAM(4096K+0K) and 65536*1 CAM entries for DMA 8, version 0158
4096 KB PRAM(4096K+0K) and 65536*1 CAM entries for DMA 9, version 0158
==========================================================================
SL 4: J4885A EP 8 port mini-GBIC Management Module, SYSIF 2 (Mini GBIC), M4, STANDBY
Serial #: US90020086
4096 KB BRAM, EP ASIC IGC version 49, BIA version 89
32768 KB PRAM and 2M-Bit*1 CAM for IGC 12, version 0449
32768 KB PRAM and 2M-Bit*1 CAM for IGC 13, version 0449
==========================================================================
Active management module:
466 MHz Power PC processor 750 (version 8/8302) 66 MHz bus
512 KB boot flash memory
16384 KB code flash memory
256 KB SRAM
512 MB DRAM
Standby management module:
466 MHz Power PC processor 750 (version 8/8302) 66 MHz bus
512 KB boot flash memory
16384 KB code flash memory
256 KB SRAM
512 MB DRAM
The system uptime is 2 days 1 hours 26 minutes 21 seconds
The system : started=cold start
5 - 4 June 2005
Page 81
Changing CAM Partitions
Syntax: show version
In the example at the beginning of this section, on the module in slot 1, DMAs 0 and 1 are master DMAs, and on
the module in slot 3, DMA 8 is a master DMA. You can display CAM partitioning information for each master DMA.
For example:
ProCurveRS# show cam-partition brief
==== SLOT 1 CAM PARTITION ====
DMA: 0 (0x00)
Number of CAM devices per DMA: 8
Number of hw entries per CAM: 0x00800
Total size of CAM = 1Mbits
complete CAM index range per DMA:
(sw) 1 - 16383 (1 - 0x03fff), total entries: 16383 (0x03fff)
(hw) 0 - 16383 (0 - 0x03fff), total entries: 16384 (0x04000)
Percentage of CAM hardware entries for each partition:
Level3 l3 = 2047 (0.124938Mbits) (12.493896%)
Level3 l3 = 2048 (0.125Mbits) (12.5%)
Level3 l3 = 8192 (0.5Mbits) (50%)
Level4 = 4096 (0.25Mbits) (25%)
DMA: 2 (0x02)
Number of CAM devices per DMA: 8
Number of hw entries per CAM: 0x00800
Total size of CAM = 1Mbits
complete CAM index range per DMA:
(sw) 1 - 16383 (1 - 0x03fff), total entries: 16383 (0x03fff)
(hw) 0 - 16383 (0 - 0x03fff), total entries: 16384 (0x04000)
Percentage of CAM hardware entries for each partition:
Level3 l3 = 2047 (0.124938Mbits) (12.493896%)
Level3 l3 = 2048 (0.125Mbits) (12.5%)
Level3 l3 = 8192 (0.5Mbits) (50%)
Level4 = 4096 (0.25Mbits) (25%)
Syntax: show cam-partition brief
June 2005 5 - 5
Page 82
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
To display the index range for each kind of CAM entry, enter the following command:
ProCurveRS# show cam-partition detail
==== SLOT 1 CAM PARTITION ====
DMA: 0 (0x00)
Number of CAM devices per DMA: 8
Number of hw entries per CAM: 0x00800
Total size of CAM = 1Mbits
complete CAM index range per DMA:
(sw) 1 - 16383 (1 - 0x03fff), total entries: 16383 (0x03fff)
(hw) 0 - 16383 (0 - 0x03fff), total entries: 16384 (0x04000)
Percentage of CAM hardware entries for each partition:
Level3 l3 = 2047 (0.124938Mbits) (12.493896%)
Level3 l3 = 2048 (0.125Mbits) (12.5%)
Level3 l3 = 8192 (0.5Mbits) (50%)
Level4 = 4096 (0.25Mbits) (25%)
L3 level 3 index range:
(sw) 1 - 2047 (0x00001 - 0x007ff), free 2047 (0x007ff)
(hw) 1 - 2047 (0x00001 - 0x007ff)
L3 level 2 index range:
(sw) 2048 - 4095 (0x00800 - 0x00fff), free 2048 (0x00800)
(hw) 2048 - 4095 (0x00800 - 0x00fff)
L3 index range:
(sw) 4096 - 12287 (0x01000 - 0x02fff), free 8189 (0x01ffd)
(hw) 4096 - 12287 (0x01000 - 0x02fff)
L4 pool 0 index range:
(sw) 12288 - 14335 (0x03000 - 0x037ff), free 2044 (0x007fc)
(hw) 12288 - 14335 (0x03000 - 0x037ff)
L2/L4 pool 1 index range:
(sw) 14336 - 16383 (0x03800 - 0x03fff), free 2047 (0x007ff)
(hw) 14336 - 16383 (0x03800 - 0x03fff)
Syntax: show cam-partition detail
To display CAM partitioning information for a specified module, enter a command such as the following:
ProCurveRS# show cam-partition module 3 brief
==== SLOT 3 CAM PARTITION ====
DMA: 8 (0x08)
Number of CAM devices per DMA: 8
Number of hw entries per CAM: 0x00800
Total size of CAM = 0.9375Mbits
complete CAM index range per DMA:
(sw) 1 - 15359 (1 - 0x03bff), total entries: 15359 (0x03bff)
(hw) 0 - 15359 (0 - 0x03bff), total entries: 15360 (0x03c00)
Percentage of CAM hardware entries for each partition:
Level3 l3 = 2047 (0.124938Mbits) (13.326822%)
Level3 l3 = 2048 (0.125Mbits) (13.333333%)
Level3 l3 = 8192 (0.5Mbits) (53.333333%)
Level4 = 3072 (0.1875Mbits) (20%)
Syntax: show cam-partition module <module> brief | detail
5 - 6 June 2005
Page 83
Changing CAM Partitions
Configuring CAM Aggregation
The following sections describe features that allow you to modify the way the HP device manages the CAM:
• Programming directly connected routes into CAM as network routes
• CAM aggregation for supernet routes
NOTE: These features apply to HP devices running Enterprise software release 07.8.00 or higher.
CAM Support for Directly Connected Routes
By default, for supernet routes of directly connected routes, the HP device creates 32-bit host CAM entries for
traffic using these routes. If a network has traffic destined to a large number of different hosts, creating the 32-bit
supernet routes can consume a large portion of CAM space.
To configure the device to program directly connected routes as supernet routes in CAM, enter the following
command:
ProCurveRS(config)# ip supernet connected
Syntax: [no] ip supernet connected
This feature takes effect immediately after you enter the ip supernet connected command. CAM entries that
have already been programmed are not affected, however; consequently, you may want to save the configuration
and restart the HP device after enabling the feature.
The following is an example of how this feature works. In the example, 20.20.20.0/24 is a locally connected subnet. Two static routes, 20.0.0.0/8 and 20.20.0.0/16 are configured. Traffic is sent to host 20.1.1.1 using the first
parent route.
Without the ip supernet connected command configured, the following 32-bit host CAM entries are created:
ProCurveRS# show cam ip 3/1
Slot Index IP_Address MAC Age VLAN Out Port
3 4097 20.1.1.1/32 00e0.52da.c347 1 1 ether 3/9
3 4099 20.20.20.10/32 0050.da27.62cb 1 1 ether 3/1
With the ip supernet connected command configured, the following network CAM entries are created:
ProCurveRS# show cam ip 3/1
Slot Index IP_Address MAC Age VLAN Out Port
3 1 20.0.0.0/8 00e0.52da.c347 0 1 ether 3/9
3 2048 20.20.0.0/16 00e0.52da.c347 dis 1 ether 3/9
3 4096 20.20.20.0/24 0000.0000.0000 1 N/A FID unused
Note that in the second CAM entry displayed (20.20.0.0/16), the age is shown as disabled. This is because this
CAM entry is created when its parent is created, but since the entry is never used, it would normally be timed out
eventually. However, since its parent is still in the CAM, it should not be timed out. Instead, aging for the CAM
entry is disabled.
For the third CAM entry, created for the locally connected route (20.20.20.0/24), the outgoing interface is shown as
"FID unused". This indicates that packets using this route are forwarded by the CPU.
In addition, if a host CAM entry for the supernet route had already existed prior to when the ip supernet
connected command was configured, it is not removed by enabling this feature. In the example above, if a host
entry for 20.20.20.10/32 had already existed, enabling this feature does not remove this entry. When the CAM
entry ages out, traffic for this destination would be forwarded using the network CAM entries.
June 2005 5 - 7
Page 84
Diagnostic Guide for ProCurve 9300/9400 Series Routing Switches
5 - 8 June 2005
Page 85
Backcover
Page 86
Technical information in this document is subject
to change without notice.
© Copyright 2000, 2005 Hewlett-Packard
Development Company, L.P. All rights reserved.
Reproduction, adaptation, or translation without
prior written permission is prohibited except as
allowed under the copyright laws.
June 2005
Manual Part Number
5990-6032
Loading...