Using Auto-Trace To Diagnose Problems - Avaya 8800 Troubleshooting Manual

Software troubleshooting tool configuration using CLI
7 - Hardware I/F
8 - (N/A)
9 - CP Port
10 - (N/A)
11 - VLAN Manager
12 - CLI
13 - Main
14 - Phase2 IP+RIP
15 - RCC IP
16 - HTTP Server
19 - Watch Dog
Timer
20 - Topology
Discovery
21 - (N/A)
22 - (N/A)

Using auto-trace to diagnose problems

You can use auto-trace to automatically perform the trace function when a parameter reaches
a certain threshold.
For example, if the SF/CPU fluctuates and you cannot access the switch to perform a CP trace,
then use auto-trace to automatically perform this function. Auto-trace monitors CPU utilization.
When the configured utilization is reached and sustained for the configured amount of time, a
CP trace is performed and saved to the PCMCIA (or external flash on the 8895 SF/CPU).
Procedure steps
1. Configure the module and verbosity:
118 Troubleshooting
30 - P2IPX
31 - RCIPX
32 - RAR
33 - OP
34 - BOOT
35 - IOM
36 - QOS
37 - FLEXDB
38 - SMM
39 - ATM
40 - POS
41 - RADIUS
42 - SIO_COM
43 - PGM
trace auto-enable add-module <modid> <level>
For example:
Comments? infodev@avaya.com
52 - BGP 100 - MPLS
53 - EPILOGUE 101 - RCMPLS
54 - SSH 102 - ACLI
56 - HAL 103 - VRF
57 - WIND 104 - ASNA
58 - EAP 105 - MIRRORFPGA
59 - LACP 106 - MSTP
60 - PING 107 - RSTP
61 - DNS 108 - MSDP
62 - DPM 109 - TACACS+
63 - BOOTP 115 - BFD
64 - DPMMSG 116 - DHCPSNOOP
65 - FILTER 117 - DAI
66 - RCIP6 120 - ISIS
121 - SPBM
122 - CFM
123 - L2VPN
July 2013