Troubleshooting Guide

Table Of Contents
Switch:1#trace shutdown
Switch:1#clear trace
Removed 5 files.
Variable definitions
Use the data in the following table to use the trace ipv6 command.
Table 27: Variable definitions
Variable Value
base <disable|enable> <all|debug|error|
icmp|info|ipclient|nbr|pkt|warn>
Enables or disables a specific trace category for IPv6 base.
forwarding <disable|enable> <all|debug|
error|info|pkt|warn>
Enables or disables a specific trace category for IPv6 forwarding.
nd <disable|enable> <all|debug|error|
info|nbr|pkt|redirect|warn>
Enables or disables a specific trace category for IPv6 neighbor
discovery.
ospf <disable|enable> <adj|all|config|
error|import|info|lsa|pkt|spf|warn>
Enables or disables a specific trace category for IPv6 OSPF.
rtm <disable|enable> <all|change-list|
debug|error|fib|info|redist|update|warn>
Enables or disables a specific trace category for IPv6 routing
table manager.
transport <disable|enable> <all|
common|tcp|udp>
Enables or disables a specific trace category for IPv6 transport.
Viewing and deleting debug files
Use this procedure to view and delete debug files.
Delete debug files to free space in the intflash, which has 2 GB of space. Avaya recommends you
delete these files to ensure enough space exists in intflash. New debug files do not overwrite old
debug files. You must remove the file; otherwise, enough free space may not exist in the intflash to
store the core dump if the switch fails or enough space may not exist for you to transfer a new
release to the intflash of the switch to upgrade your switch.
The debug-file remove command can delete the following types of files:
core
archive
PMEM
dmalloc
flrec
Viewing and deleting debug files
January 2017 Troubleshooting 105
Comments on this document? infodev@avaya.com