Using Trace To Diagnose Problems - Avaya 8800 Troubleshooting Manual

Procedure steps
To dump hardware record information, enter the following command:
dump ar <octapid> <vlan|ip_subnet|mac_vlan|mac|arp|ip|ipx|
ipmc|ip_filter|protocol|sys_rec|all> <verbosity>
For example, dump all hardware records from OctaPID 0 slot 1 port 1 with a verbosity
level of 3:
dump ar 0 all 3
Variable definitions
Use the information in the following table to help you use the dump command.
<opid>
<vlan|ip_subnet|
mac_vlan|mac|arp|ip|
ipx|ipmc|ip_filter|
protocol|sys_rec|all>
<verbosity>

Using trace to diagnose problems

Use trace to observe the status of a software module at a given time.
For example, if a CPU utilization issue is observed (generally a sustained spike above 90%)
perform a trace of the control plane (CP) activity.
Prerequisites
Caution:
Risk of traffic loss
Troubleshooting
Variable
Specifies the OctaPID assignment from 1 to 64.
Specifies a record type in the AR table.
Specifies the verbosity from 0 to 3. Higher numbers
specify more verbosity.
General troubleshooting
Value
July 2013 115