Avaya Virtual Services Platform 7000 Series Troubleshooting Manual

Hide thumbs Also See for Virtual Services Platform 7000 Series:
Table of Contents

Advertisement

Quick Links

Avaya Virtual Services Platform 7000
Series Troubleshooting
Release 10.1
NN47202-700, 01.01
March 2012

Advertisement

Table of Contents
loading

Summary of Contents for Avaya Virtual Services Platform 7000 Series

  • Page 1 Avaya Virtual Services Platform 7000 Series Troubleshooting Release 10.1 NN47202-700, 01.01 March 2012...
  • Page 2 Product provided by Avaya including the selection, arrangement and While reasonable efforts have been made to ensure that the design of the content is owned either by Avaya or its licensors and is information in this document is complete and accurate at the time of protected by copyright and other intellectual property laws including the printing, Avaya assumes no liability for any errors.
  • Page 3: Table Of Contents

    SNMP traps............................... 19 Auto Unit Replacement..........................20 Multicast behavior............................. 20 IPv6................................21 LED display............................... 21 Avaya Knowledge and Solution Engine....................21 Chapter 5: Initial troubleshooting..................Chapter 6: Emergency recovery trees................Corruption of Flash............................ 25 Corruption of flash recovery tree...................... 26 Incorrect PVID............................
  • Page 4 Returning the unit for repair......................36 Replacing a unit in the stack........................37 Removing a failed unit........................37 Verifying the new unit software version.................... 38 Obtaining the correct software version..................... 38 Placing a new unit..........................38 Connecting stacking cables......................38 Returning the unit for repair......................
  • Page 5 Checking IGMP configuration for a VLAN..................54 Viewing the IGMP unknown multicast flooding status..............55 Enabling IGMP unknown multicast flooding..................55 Chapter 11: Troubleshooting RSTP SNMP traps.............. Viewing the RSTP configuration....................... 57 Verifying RSTP traps are enabled......................57 Verifying the SNMP access configuration status..................58 Viewing the SNMP trap receiver configuration..................
  • Page 6 VSP 7000 Troubleshooting March 2012...
  • Page 7: Chapter 1: Purpose Of This Document

    The Avaya Virtual Services Platform 7000 Series Troubleshooting guide describes the diagnostic tools and utilities available with the Avaya Virtual Services Platform (VSP) 7000 Series to help you troubleshoot operational and configuration issues. This document guides you through some common problems, to achieve a first tier solution to these situations, and advises you what information to compile prior to troubleshooting or calling Avaya for help.
  • Page 8 Purpose of this document VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 9: Chapter 2: New In This Release

    Chapter 2: New in this release This troubleshooting guide is a new document for Release 10.1 of the Avaya Virtual Services Platform 7000 Series. VSP 7000 Troubleshooting March 2012...
  • Page 10 New in this release VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 11: Chapter 3: Preparing A Troubleshooting Plan

    Use the following steps to help you minimize the occurrence of circumstances that require troubleshooting and to develop a troubleshooting plan: 1. Know where to get information as you need it by reviewing the Avaya Virtual Services Platform 7000 Series Documentation Roadmap (NN47202-103) to become familiar with the documentation set.
  • Page 12 • You can speed up the process of isolating network problems by using a baseline analysis as an indicator of overall network health. A baseline view of network traffic behavior during normal operation is an important reference that you can compare to network traffic data captured while troubleshooting. VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 13: Chapter 4: Troubleshooting Tools

    Chapter 4: Troubleshooting tools This chapter describes protocols, utilities, and diagnostic tools that you can use with Avaya Virtual Services Platform 7000 Series products to help you troubleshoot operational and configuration issues. You can configure and display files, monitor and analyze traffic, capture and analyze data packets, trace data flows, view and monitor statistics, and manage event messages.
  • Page 14: Port Statistics

    MAC address A. (monitoring traffic with source OR destination MAC address You can observe and analyze packet traffic at the mirroring port using the Avaya StackProbe or equivalent. Unlike other methods that are used to analyze packet traffic, with port mirroring a copy of the packet can be captured and analyzed, so the packet traffic is uninterrupted, and packets flow normally through the mirrored port.
  • Page 15: Stack Loopback Testing

    Always perform an external loopback test using only the top FI-ports. Using the bottom FI- ports can result in a false pass. For more information about stack loopback testing, see Virtual Services Platform 7000 Series Configuration — System Monitoring (NN47202-505).
  • Page 16: System Logs

    • Configuration files are corrupted. Restored to default The following messages are loaded to the engineering log menu: • Backup configuration restored from primary configuration block • Backup configuration updated for next active configuration block VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 17: Ascii Download Log

    ASCII download log ASCII download log The ASCII download log displays informational customer messages, describing the result of the ASCII configuration file download, especially the failed commands. You can log four hundred customer messages in dynamic random-access memory (DRAM). The informational messages logged for describing the result of the ASCII configuration file download are: •...
  • Page 18: Cpu And Memory Utilization

    • show mac-address-table • show lacp aggr • show lacp port • show ipv address • show ipv interface • show system verbose VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 19: Mlt Or Dmlt

    • Avaya recommends that you use the mlt enable {1–32} command to ensure that MLT is fully functional and that all links are enabled.
  • Page 20: Auto Unit Replacement

    Important: You must enable AAUR before you can enable DAUR. DAUR is not configured separately from AAUR. For more information about AUR, AAUR, and DAUR, see Virtual Services Platform 7000 Series Getting Started (NN47202-303). Multicast behavior You can use Internet Group Management Protocol (IGMP) snooping to selectively forward multicast traffic only to ports where particular IP multicast streams are expected.
  • Page 21: Ipv6

    The Avaya Virtual Services Platform 7000 Series switches display diagnostic and operation information using light emitting diodes (LEDs). To become familiar with the interpretation of the LEDs on the VSP 7000, see Avaya Virtual Services Platform 7000 Series Installation (NN47202-300).
  • Page 22 Troubleshooting tools VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 23: Chapter 5: Initial Troubleshooting

    As part of your initial troubleshooting, Avaya recommends that you check the Knowledge and Solution Engine on the Avaya web site for known issues and solutions related to the problem you are experiencing. Information for technical support Before you contact Avaya technical support personnel, it is important that you perform the following tasks: •...
  • Page 24 Initial troubleshooting VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 25: Chapter 6: Emergency Recovery Trees

    Chapter 6: Emergency recovery trees An emergency recovery tree (ERT) is designed to quickly guide you through some common failures and solutions, by providing a quick reference for troubleshooting without procedural detail. This chapter provides emergency recovery trees (ERTs) following VSP 7000 failure symptoms: •...
  • Page 26: Corruption Of Flash Recovery Tree

    VLAN. For example, if the server VLAN is configured as a port-based VLAN, with a VLAN ID of 3, and the client port VLAN identifier (PVID) is 2, communication VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 27: Incorrect Pvid Recovery Tree

    VLAN not tagged to uplink ports between the client and the server fails. You can prevent this communication failure by setting VLAN configuration control for the switch to autoPVID. The PVID associates a switch port with a specific VLAN. For example, a switch port with a PVID of 3 assigns all untagged data frames received on that port to VLAN 3.
  • Page 28: Vlan Not Tagged To Uplink Ports Recovery Tree

    Common causes of stack failures are cabling problems between individual stack switch units, which result in communication errors between the units, or stack configuration errors. Configuration errors that can cause a stack failure include the following: VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 29: Stack Recovery Tree 1

    Stack failure • No stack switches have the base unit switch set to the On position. • Multiple stack switches have the base unit switch set to the On position. • The wrong stack switch has the base unit switch set to the On position. Stack recovery tree 1 VSP 7000 Troubleshooting March 2012...
  • Page 30 • If the Base LED condition on an individual stack switch is solid emerald, that switch is set as the stack base unit. For information about the location of the UP , DOWN, and Base LEDs on a switch , see Avaya Virtual Services Platform 7000 Series Installation (NN47202-300).
  • Page 31: Stack Recovery Tree 2

    Stack failure Stack recovery tree 2 VSP 7000 Troubleshooting March 2012...
  • Page 32: Stack Recovery Tree 3

    Emergency recovery trees Stack recovery tree 3 VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 33: Chapter 7: Troubleshooting Hardware

    Verify that the power cords and power supplies for the switch are properly installed. Ensure that the power cords are firmly seated for all power supplies. For detailed power cord and power supply information, see Avaya Virtual Services Platform 7000 Series Installation (NN47202-300).
  • Page 34: Returning The Unit For Repair

    Consider each pair of FI ports on a unit as a single connection. Each pair of FI ports requires two FI cables. Avaya recommends you to use two matched FI cables for each unit. For redundant virtual fabrics, you require one matched pair of longer FI cables to complete the loop from the bottom unit to the top unit.
  • Page 35: Checking Fiber Ports

    (FI down or FI up configuration). For detailed information about FI cable installations and FI configurations, see Avaya Virtual Services Platform 7000 Series Installation (NN47202-300). Note: You must always connect an FI-up port to an FI-down port, or an FI-down port to an FI-up port between adjacent units.
  • Page 36: Enabling The Fiber Port

    1. Inspect the SFP or SFP+ device to ensure it is fully seated in the port. 2. Inspect the fiber cable to ensure it is the correct type for a SFP or SFP+ device. For more information about SFP or SFP+ devices and cabling, see Avaya Virtual Services Platform Installation — SFP and SFP+ (NN47202–302) Confirming the cables are working Ensure that the cables connected to the port are functioning correctly.
  • Page 37: Replacing A Unit In The Stack

    Physical handling of the device and your proximity to electrical equipment can result in equipment damage or personal injury. Review and adhere to all safety instructions and literature included with device and in Avaya Virtual Services Platform 7000 Series – Regulatory Information (NN47202-100).
  • Page 38: Verifying The New Unit Software Version

    Series Getting Started (NN47202–303). Placing a new unit Place the new unit in the stack where the failed unit was connected. For more information about physically installing a switch, see Avaya Virtual Services Platform 7000 Series Installation (NN47202–300). Connecting stacking cables Reconnect the Fabric Interconnect (FI) cables to correctly stack the replacement unit.
  • Page 39: Returning The Unit For Repair

    Replacing a unit in the stack Returning the unit for repair If troubleshooting determines a failure that cannot be resolved on-site, you can return the unit to Avaya for repair. Contact Avaya for return instructions and RMA information. VSP 7000 Troubleshooting March 2012...
  • Page 40 Troubleshooting hardware VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 41: Chapter 8: Troubleshooting Sfp

    Confirming SFP device support You must confirm that the SFP or SFP+ device is supported on the switch. For detailed information about supported SFP and SFP+ devices, see Avaya Virtual Services Platform 7000 Series Installation — SFP and SFP+ (NN47202–302).
  • Page 42 Troubleshooting SFP VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 43: Chapter 9: Troubleshooting Ipv6

    Chapter 9: Troubleshooting IPv6 This chapter provides processes you can use to troubleshoot common IPv6 problems. For detailed information about configuring IPv6, see Avaya Virtual Services Platform 7000 Series Configuration Layer 2 (NN47202-502). No response to switch IPv6 address ping This section describes the troubleshooting process you can use when attempts to ping the IPv6 address of a switch from another network host fail.
  • Page 44: Verifying The Global Ipv6 Address

    2. If required, use the ipv6 default–gateway <ipv6_addr> command to configure the switch for the IPv6 default gateway. 3. You can repeat step 1 to confirm the change. VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 45: Verifying Switch Interface Ipv6 Status

    No response to switch IPv6 address ping Verifying switch interface IPv6 status Use this procedure to verify that IPv6 is enabled on interfaces for the switch that does not respond to the ping. Procedure 1. Use the show ipv6 interface command to display the IPv6 configuration for switch interfaces.
  • Page 46: Changing The Management Vlan Ipv6 Local Link Id

    1. Use the show ipv6 neighbor <ipv6_addr> command to display the IPv6 neighbor configuration. 2. Observe the State value. 3. If required, use the ipv6 neighbor <ipv6_addr> command to modify the configuration. 4. You can repeat step 1 to confirm the change. VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 47: Checking Remote Host Ipv6 Integrity

    Unable to connect through the IPv6 default gateway Checking remote host IPv6 integrity Use this procedure to check the IPv6 integrity of the remote host that does not respond to the ping. Procedure 1. Use vendor documentation to ensure the remote host is configured correctly for IPv6.
  • Page 48: Tracing The Route To The Ipv6 Default Gateway

    Procedure 1. Use the show ipv6 default-gateway command to display the IPv6 default gateway configuration for the switch. 2. Observe the command output display for inconsistencies with the IPv6 default gateway configuration. VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 49: Viewing Switch Ipv6 Default Gateway Interface Statistics

    Unable to connect to the switch with IPv6 Telnet, HTTP, or SSH Viewing switch IPv6 default gateway interface statistics Use this procedure to display and observe statistics for the communication between the switch IPv6 interface and the IPv6 default gateway. Procedure 1.
  • Page 50: Viewing Ipv6 Tcp Information

    Viewing the global IPv6 configuration Use this procedure to display and analyze the global IPv6 configuration. Procedure 1. Use the show ipv6 global command to display the global IPv6 configuration. 2. Observe and analyze the command output. VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 51: Viewing Ipv6 Udp Information

    Unable to assign an IPv6 address to an interface Viewing IPv6 UDP information Use this procedure to display and analyze IPv6 UDP configuration information. Procedure 1. Use the show ipv6 udp command to display UDP statistics. 2. Use the show ipv6 udp endpoints command to display the UDP endpoint table.
  • Page 52: Changing An Interface Ipv6 Address

    IPv6 address from the interface. 3. Use the ipv6 interface address <ipv6_addr> command to assign a new IPv6 address to the interface. 4. You can repeat step 1 to confirm the change. VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 53: Chapter 10: Troubleshooting Igmp

    This chapter provides processes you can use to troubleshoot common Internet Group Management Protocol (IGMP) problems. For detailed information about configuring IGMP, see Avaya Virtual Services Platform 7000 Series Configuration Layer 2 (NN47202-502). Unknown IGMP multicast packets flooding a network This section describes the troubleshooting process you can use to resolve the problematic flooding of a network with unknown IGMP multicast packets.
  • Page 54: Disabling Igmp Unknown Multicast Flooding

    Use this procedure to view and analyze the IGMP configuration for a specific VLAN. Procedure 1. Use the show vlan igmp {1–4094} command to display IGMP configuration information for the VLAN. 2. Observe and analyze the command output. VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 55: Viewing The Igmp Unknown Multicast Flooding Status

    Unknown IGMP multicast packets not flooding a network Viewing the IGMP unknown multicast flooding status Use this procedure to view and analyze the status of the switch configuration for flooding VLANs with IGMP unknown multicast packets. Procedure 1. Use the show vlan igmp unknown-mcast-no-flood command to display whether the switch functionality for flooding all VLANs with unknown IGMP multicast addresses is enabled or disabled.
  • Page 56 Troubleshooting IGMP VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 57: Chapter 11: Troubleshooting Rstp Snmp Traps

    This chapter describes the troubleshooting process you can use when Simple Network Management Protocol (SNMP) traps are not generated for Rapid Spanning Tree Protocol (RSTP). For detailed information about SNMP trap support, see Avaya Virtual Services Platform 7000 Series Configuration Security (NN47202-501).
  • Page 58: Verifying The Snmp Access Configuration Status

    Use this procedure to view and analyze the SNMP trap receiver configuration. Procedure 1. Use the show snmp-server host command to display the trap receiver configuration. 2. Observe and analyze the command output display. VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...
  • Page 59: Adding An Snmpv1 Trap Receiver

    Adding an SNMPv1 trap receiver Adding an SNMPv1 trap receiver Use this procedure to add an SNMPv1 trap receiver to the trap receiver table. Procedure 1. Use the snmp-server host <host-ip> v1 <community-string> command to add the trap receiver to the table. 2.
  • Page 60 Troubleshooting RSTP SNMP traps VSP 7000 Troubleshooting March 2012 Comments? infodev@avaya.com...

Table of Contents