Troubleshooting Guide
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: Safety messages
- Chapter 3: New in this document
- Chapter 4: Data collection required for Technical Support cases
- Chapter 5: Troubleshooting planning fundamentals
- Chapter 6: Troubleshooting fundamentals
- Chapter 7: Troubleshooting tool fundamentals
- Chapter 8: Log and trap fundamentals
- Chapter 9: Log configuration using ACLI
- Configuring a UNIX system log and syslog host
- Configuring secure forwarding
- Installing root certificate for syslog client
- Configuring logging
- Configuring the remote host address for log transfer
- Configuring system logging to external storage
- Configuring system message control
- Extending system message control
- Viewing logs
- Configuring ACLI logging
- Chapter 10: Log configuration using EDM
- Chapter 11: SNMP trap configuration using ACLI
- Chapter 12: SNMP trap configuration using EDM
- Chapter 13: Traps reference
- Chapter 14: Hardware troubleshooting
- Chapter 15: Software troubleshooting
- Chapter 16: Software troubleshooting tool configuration using ACLI
- Using ACLI for troubleshooting
- Using software record dumps
- Using trace to diagnose problems
- Using trace to diagnose IPv6 problems
- Viewing and deleting debug files
- Configuring port mirroring
- Configuring global mirroring actions with an ACL
- Configuring ACE actions to mirror
- Clearing ARP information for an interface
- Flushing routing, MAC, and ARP tables for an interface
- Pinging an IP device
- Running a traceroute test
- Showing SNMP logs
- Using trace to examine IS-IS control packets
- Viewing the metric type of IS-IS route in TLVs – detailed
- Viewing the metric type of IS-IS route in TLVs – summarized
- Chapter 17: Software troubleshooting tool configuration using EDM
- Chapter 18: Layer 1 troubleshooting
- Chapter 19: Operations and Management
- CFM fundamentals
- CFM configuration using ACLI
- Autogenerated CFM
- Configuring explicit mode CFM
- Displaying SPBM nodal configuration
- Configuring simplified CFM SPBM
- Triggering a loopback test (LBM)
- Triggering linktrace (LTM)
- Triggering a Layer 2 ping
- Triggering a Layer 2 traceroute
- Triggering a Layer 2 tracetree
- Triggering a Layer 2 tracemroute
- Using trace CFM to diagnose problems
- Using trace SPBM to diagnose problems
- CFM configuration using EDM
- Autogenerated CFM
- Configuring explicit CFM
- Configuring Layer 2 ping
- Initiating a Layer 2 traceroute
- Viewing Layer 2 traceroute results
- Configuring Layer 2 IP ping
- Viewing Layer 2 IP Ping results
- Configuring Layer 2 IP traceroute
- Viewing Layer 2 IP traceroute results
- Triggering a loopback test
- Triggering linktrace
- Viewing linktrace results
- Configuring Layer 2 tracetree
- Viewing Layer 2 tracetree results
- Configuring Layer 2 trace multicast route on a VLAN
- Configuring Layer 2 tracemroute on a VRF
- Viewing Layer 2 trace multicast route results
- CFM configuration example
- Chapter 20: Upper layer troubleshooting
- Troubleshooting SNMP
- Troubleshooting DHCP
- Troubleshooting DHCP Relay
- Troubleshooting client connection to the DHCP server
- Troubleshooting IPv6 DHCP Relay
- IPv6 DHCP Relay switch side troubleshooting
- IPv6 DHCP Relay server side troubleshooting
- IPv6 DHCP Relay client side troubleshooting
- Enabling trace messages for IPv6 DHCP Relay
- Troubleshooting IPv6 VRRP
- VRRP transitions
- Enabling trace messages for IPv6 VRRP troubleshooting
- Risks associated with enabling trace messages
- VRRP with higher priority running as backup
- Downgrading or upgrading from releases that support different key sizes
- Troubleshooting IPv6 connectivity loss
- Troubleshooting TACACS+
- Troubleshooting RSMLT
- Chapter 21: Unicast routing troubleshooting
- Chapter 22: Multicast troubleshooting
- Chapter 23: Multicast routing troubleshooting using ACLI
- Viewing IGMP interface information
- Viewing multicast group trace information for IGMP snoop
- Viewing IGMP group information
- Showing the hardware resource usage
- Using PIM debugging commands
- Determining the protocol configured on the added VLAN
- Determining the data stream learned with IP Multicast over Fabric Connect on the VLAN
- Displaying the SPBM multicast database
- Troubleshooting IP Multicast over Fabric Connect for Layer 2 VSNs
- Troubleshooting IP Multicast over Fabric Connect for Layer 3 VSNs
- Troubleshooting IP Multicast over Fabric Connect for IP Shortcuts
- Defining the IS-IS trace flag for IP multicast
- Chapter 24: Multicast routing troubleshooting using EDM
- Viewing IGMP interface information
- Viewing IGMP snoop trace information
- Viewing IGMP group information
- Viewing multicast group sources
- Viewing multicast routes by egress VLAN
- Enabling multicast routing process statistics
- Determining the data stream learned when IP Multicast over Fabric Connect is configured on the VLAN
- Showing the SPBM multicast database
- Chapter 25: Transparent Port UNI feature troubleshooting using ACLI
- Chapter 26: Troubleshooting MACsec
- Chapter 27: Troubleshooting MACsec using EDM
- Chapter 28: Troubleshooting Fabric Attach
- Troubleshooting Fabric Attach using the ACLI
- Troubleshooting Fabric Attach using the EDM
- Fabric Attach troubleshooting example
Log file transfer
The system logs contain important information for debugging and maintaining the switch. After the
current log file reaches the configured maximum size, the system creates a new log file for logging.
The system transfers old log files to a remote host. You can configure up to 10 remote hosts, which
creates long-term backup storage of your system log files.
Of the 10 configured remote hosts, 1 is the primary host and the other 9 are redundant. Upon
initiating a transfer, system messaging attempts to use host 1 first. If host 1 is not reachable, system
messaging tries hosts 2 to 10.
If log file transfer is unsuccessful, the system keeps the old log files on internal flash. The system
attempts to transfer old log files after the new log file reaches the configured maximum size. The
system also attempts to transfer old log files periodically (once in one hundred log writes) if the disk
space on the flash is more than 75% full.
You can log system log messages to external system log hosts with both IPv4 and IPv6 addresses
with no difference in functionality or configuration.
With enhanced secure mode enabled, authorized users can use SFTP to transfer files to a remote
server with the content encrypted.
You can specify the following information to configure the transfer criteria:
• The maximum size of the log file.
• The IP address of the remote host.
• The name prefix of the log file to store on the remote host.
The system appends a suffix of .xxxxxxxx.sss to the file name. The first six characters of the
suffix contain the last three bytes of the chassis base MAC address. The next two characters
are 01. The last three characters (sss) denote the sequence number of the log file. For
example, if you configure the name prefix as mylog, a possible file name is mylog.
90000001.001.
• The user name and password, if using File Transfer Protocol (FTP) for file transfer. Use the
following commands to configure the user name and password:
boot config host user WORD<0–16>
boot config host password WORD<0–16>
Be aware of the following restrictions to transfer log files to a remote host:
• The remote host IP address must be reachable.
• If you transfer a log file from a host to the system, (for example, to display it with a show
command), rename the log file. Failure to rename the log file can cause the system to use the
recently transferred file as the current log, if the sequence number in the extension is higher
than the current log file. For example, if bf860005.002 is the current log file and you transfer
bf860005.007 to the system, the system logs future messages to the bf860005.007 file. You
can avoid this if you rename the log file to something other than the format used by system
messaging.
• If your TFTP server is a UNIX-based machine, files written to the server must already exist. For
example, you must create dummy files with the same names as your system logs. This action
is commonly performed by using the touch command (for example, touch bf860005.001).
Log and trap fundamentals
January 2017 Troubleshooting 44
Comments on this document? infodev@avaya.com










