Page 1: Troubleshooting Guide
AX6700S/AX6600S/AX6300S/AX3800S/AX3600S/AX2400S Troubleshooting Guide AX36S-T001-B0X Reading and storing this manual: Before you use the equipment, carefully read the manual and make sure you understand all safety precautions. After reading the guide, keep it in a convenient place for easy reference.
Page 2 Relevant products This manual applies to the models in the AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, and AX2400S series of switches. Export restrictions If you plan to export any of the models, complete the necessary procedures after checking the Foreign Exchange and Foreign Trade Act and U.S.
Page 3: History Of Amendments
History of Amendments (Edition 12) Summary of amendments Location and title Changes 1.2.2 Failure analysis for the AX3800S, A description of AX3800S series switches has been AX3600S, and AX2400S series added. 3.8.7 Communication is not possible in IPv4 This subsection was added. PIM-DM networks 3.8.8 Multicast data is forwarded twice in an IPv4 This subsection was added.
Page 4 Item Changes Problems due to the redundant configuration of This section was added. the NIF Access list logging problems This section was added. DHCP snooping problems This section was added. Detailed display contents of the "show Commands were added to the detailed description. tech-support"...
Page 5 Item Changes Procedure for handling switch faults Items for handling failures were added. Memory card problems This section was added. BSU/PSP communication failures PSP was added. In addition, items for analyzing failures were added or modified. Actions to be taken for PoE problems This subsection was added.
Page 6 Item Changes configuration of IPv6 networks functionality were added. Packet congestion in CPU processing does not This section was added. recover Detailed display contents of the "show Content displayed by the added or changed tech-support" command commands was added. (Edition 6) Summary of amendments Item Changes...
Page 7 (Edition 5) Summary of amendments Item Changes MAC-based authentication This item was added. (Edition 4) Summary of amendments Item Changes Ring Protocol This item was added. (Edition 3) Summary of amendments Item Changes Additional model A description relating to the additional model was added.
Page 9: Preface
Preface Relevant products This manual applies to the models in the AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, and AX2400S series of switches. Before you operate the equipment, carefully read the manual and make sure that you understand all instructions and cautionary notes. After reading the manual, keep it in a convenient place for easy reference.
Page 10 Reading sequence of the manuals The following shows the manuals you need to consult according to your requirements determined from the following workflow for installing, setting up, and starting regular operation of a switch. AX6700S, AX6600S, and AX6300S series switches...
Page 11 Preface AX3800S and AX3650S series switches...
Page 12 Preface AX3640S and AX3630S series switches...
Page 13 Preface AX2400S series switches...
Page 14 Preface Abbreviations used in the manual Alternating Current ACKnowledge ADSL Asymmetric Digital Subscriber Line Application Level Gateway ANSI American National Standards Institute Address Resolution Protocol Autonomous System Auxiliary Basic Control Unit Border Gateway Protocol BGP4 Border Gateway Protocol - version 4 BGP4+ Multiprotocol Extensions for Border Gateway Protocol - version 4 bit/s...
Page 15 Preface DSCP Differentiated Services Code Point Data Terminal Equipment DVMRP Distance Vector Multicast Routing Protocol E-Mail Electronic Mail Extensible Authentication Protocol EAPOL EAP Over LAN Ethernet in the First Mile End System Fan Unit Frame Check Sequence Filtering DataBase FQDN Fully Qualified Domain Name FTTH Fiber To The Home...
Page 16 Preface LLQ+3WFQ Low Latency Queueing + 3 Weighted Fair Queueing LLRLQ Low Latency Rate Limited Queueing Label Switched Path Link State PDU Label Switched Router Maintenance Association Media Access Control Memory Card Message Digest 5 Medium Dependent Interface MDI-X Medium Dependent Interface crossover Maintenance association End Point Management Information Base Maintenance domain Intermediate Point...
Page 17 Preface Protocol Data Unit PICS Protocol Implementation Conformance Statement Protocol IDentifier Protocol Independent Multicast PIM-DM Protocol Independent Multicast-Dense Mode PIM-SM Protocol Independent Multicast-Sparse Mode PIM-SSM Protocol Independent Multicast-Source Specific Multicast Power over Ethernet Primary Rate Interface Power Supply PSNP Partial Sequence Numbers PDU Packet Switching Processor Quality of Service Router Advertisement...
Page 18 10 gigabit small Form factor Pluggable Conventions: The terms "Switch" and "switch" The term Switch (upper-case "S") is an abbreviation for any or all of the following models: AX6700S series switch AX6600S series switch AX6300S series switch AX3800S series switch...
Page 19 Preface Conventions: KB, MB, GB, and TB This manual uses the following conventions: 1 KB (kilobyte) is 1,024 bytes. 1 MB (megabyte) is 1,024 bytes. 1 GB (gigabyte) is 1,024 bytes. 1 TB (terabyte) is 1,024 bytes.
Page 20 Preface...
Page 21: Table Of Contents
1.1 Overview of analyzing failures ..................2 1.2 Overview of analyzing failures of all or part of the Switch..........3 1.2.1 Failure analysis for AX6700S, AX6600S, and AX6300S series switches .... 3 1.2.2 Failure analysis for AX3800S, AX3600S, and AX2400S series switches .... 5 1.3 Overview of analyzing failures of functionality ..............
Page 22: Contents
Contents 3.6.2 IP addresses cannot be assigned by the DHCP functionality ......68 3.6.3 Dynamic DNS link does not work in the DHCP functionality ....... 74 3.7 IPv4 unicast routing communication failures ..............77 3.7.1 No RIP routing information exists ................ 77 3.7.2 No OSPF routing information exists ..............
Page 23 A. Detailed Display Contents of the "show tech-support" Command ........216 A.1 Detailed display contents of the "show tech-support" command ........216 A.1.1 AX6700S, AX6600S, and AX6300S series switches ........... 216 A.1.2 AX3800S and AX3600S series switches ............. 228 A.1.3 AX2400S series switches ..................239...
Page 24 Contents...
Page 25: Safety Information [Ax6700S]
Safety Information [AX6700S] Using AX6700S series switches correctly and safely This guide provides important information for ensuring safe use of AX6700S series switches. Please read this guide completely before using the Switch. Keep this guide handy after finishing it, so that it is available for later reference.
Page 26 Safety Information [AX6700S] using a Switch, stay alert and use common sense in addition to following all instructions.
Page 27 Safety Information [AX6700S] If anything seems wrong, immediately turn off the power. If smoke or an unusual smell is emanating from the Switch, or if liquid is spilled into the Switch or a foreign object falls into the Switch, immediately turn off Switch power as described below.
Page 28: Ground The Switch
Safety Information [AX6700S] Ground the Switch. When the Switch is connected to a 100 V AC power supply, up to 3.5 mA of leakage current flows for each switch. Always use a grounded power outlet for the switch. Using the switch without grounding could result in electric shock or failures due to electrical noise.
Page 29 Safety Information [AX6700S] Installing and carrying the switch must be performed by trained personnel or a professional carrier. The maximum weight of the switch is 82 kg. Installing and carrying the switch must be performed by trained personnel or a professional carrier. If anyone other than those mentioned above performs these tasks, the switch might fall, resulting in serious injury.
Page 30 Safety Information [AX6700S] maintenance personnel. Adding or replacing optional modules must be performed by a trained technician or maintenance personnel. Adding or replacing a power supply unit involves connecting and disconnecting the power cable. If anyone other than those mentioned above performs these tasks incorrectly, a fire, electric shock, or failure could result.
Page 31 Safety Information [AX6700S] Do not install the Switch in a dusty or humid location. Do not install the Switch in a dusty or humid location. Doing so could result in fire or electric shock. Condensation might form on the surfaces and the inside of the Switch if it is moved from a cold location to a warm location.
Page 32 Safety Information [AX6700S] cause injury. A DC power supply unit weighs 5.6 kg and is 163 mm long. When removing a power supply unit from a Switch, hold the power supply unit tightly. Pulling a power supply unit carelessly from a Switch might cause the power supply unit to fall, resulting in injury.
Page 33: Lithium Battery
Safety Information [AX6700S] Do not touch the SFP-T during operation and just after operation stops. During operation (when a link is established), the temperature of the SFP-T can rise to 65 °C. Do not touch the device while it is operating or just after it stops. Doing so could result in burns.
Page 34 Do not attach any labels to a transceiver. A label attached to the transceiver indicates that the transceiver is a standard product from ALAXALA or another manufacturer. However, such labels are attached where they do not interfere with heat dissipation from the transceiver or the mechanism that prevents the transceiver from coming loose from the cage.
Page 35 Safety Information [AX6700S] When carrying or packing a Switch and its optional modules, wear a wrist strap to protect against static electricity. Be sure to wear an antistatic wrist strap. If you handle the Switch without wearing an antistatic wrist strap, the Switch might be damaged by static electricity.
Page 36 Safety Information [AX6700S] Adjust the orientation of the TV or radio antenna. Use separate outlets. Do not place a Switch where it will be exposed to hydrogen sulfide or salt. Placing a Switch in an area where sulfides are present, such as a hot-springs area, or in an area with salty air, such as along a coast, could shorten the life of the Switch.
Page 37: Safety Information [Ax6600S]
Safety Information [AX6600S] Using AX6600S series switches correctly and safely This guide provides important information for ensuring safe use of AX6600S series switches. Please read this guide completely before using the Switch. Keep this guide handy after finishing it, so that it is available for later reference. Operate the Switch according to the instructions and procedures provided in this guide.
Page 38 Safety Information [AX6600S] using a Switch, stay alert and use common sense in addition to following all instructions. xviii...
Page 39 Safety Information [AX6600S] If anything seems wrong, immediately turn off the power. If smoke or an unusual smell is emanating from the Switch, or if liquid is spilled into the Switch or a foreign object falls into the Switch, immediately turn off Switch power as described below.
Page 40 Safety Information [AX6600S] Ground the Switch. Each Switch has at most 3.5 mA of leakage current. When the Switch is connected to an AC power supply unit, always use a grounded power outlet. Using the Switch without grounding could result in electric shock or failures due to electrical noise. When the Switch is connected to a DC power supply unit, always connect the ground terminal for proper grounding.
Page 41 Safety Information [AX6600S] Handle power cables carefully. Do not place anything heavy on a power cable. Do not pull, bend, or process a cable. Doing so could damage the cable, resulting in fire or electric shock. If the power cable is covered by a carpet, it is easy to forget that the cable is there and to place something heavy on it.
Page 42 Safety Information [AX6600S] with a fragile tip, or anything that might become caught in the Switch, such as a pin or paper clip. When pressing the button on the front panel of the control and switching unit, do not use anything with a fragile tip, or anything that might become caught in the Switch, such as a pin or paper clip.
Page 43 Safety Information [AX6600S] Do not install the Switch in a dusty or humid location. Do not install the Switch in a dusty or humid location. Doing so could result in fire or electric shock. Condensation might form on the surfaces and the inside of the Switch if it is moved from a cold location to a warm location.
Page 44 Safety Information [AX6600S] Do not allow hair or objects near the ventilation slots. Cooling fan units are mounted in the Switch. Do not allow anything near the ventilation slots. Doing so causes heat to accumulate inside the Switch and could cause a failure.
Page 45 Safety Information [AX6600S] Handle the power cable carefully. Do not place the power cable near a heat-generating apparatus. The heat could melt the cable coating, resulting in fire or electric shock. When connecting or disconnecting the power cable from the outlet, always hold the plug, not the cable itself.
Page 46 Safety Information [AX6600S] injury or a fire. Do not remove the battery from the Switch, disassemble it, heat it to 100°C or higher, incinerate it, or immerse it in water. Cleaning Remove dust on and around the Switch regularly. In addition to causing the Switch to stop, accumulated dust could result in a fire or electric shock.
Page 47 Do not attach any labels to a transceiver. A label attached to the transceiver indicates that the transceiver is a standard product from ALAXALA or another manufacturer. However, such labels are attached where they do not interfere with heat dissipation from the transceiver or the mechanism that prevents the transceiver from coming loose from the cage.
Page 48 Safety Information [AX6600S] When carrying or packing a Switch and its optional modules, wear a wrist strap to protect against static electricity. Be sure to wear an antistatic wrist strap. If you handle the Switch without wearing an antistatic wrist strap, the Switch might be damaged by static electricity. When removing optional modules, attach blank panels.
Page 49 Safety Information [AX6600S] Adjust the orientation of the TV or radio antenna. Use separate outlets. Do not place a Switch where it will be exposed to hydrogen sulfide or salt. Placing a Switch in an area where sulfides are present, such as a hot-springs area, or in an area with salty air, such as along a coast, could shorten the life of the Switch.
Page 50 Safety Information [AX6600S]...
Page 51: Safety Information [Ax6300S]
Safety Information [AX6300S] Using AX6300S series switches correctly and safely This guide provides important information for ensuring safe use of AX6300S series switches. Please read this guide completely before using the Switch. Keep this guide handy after finishing it, so that it is available for later reference. Operate the Switch according to the instructions and procedures provided in this guide.
Page 52 Safety Information [AX6300S] using a Switch, stay alert and use common sense in addition to following all instructions. xxxii...
Page 53 Safety Information [AX6300S] If anything seems wrong, immediately turn off the power. If smoke or an unusual smell is emanating from the Switch, or if liquid is spilled into the Switch or a foreign object falls into the Switch, immediately turn off Switch power as described below.
Page 54 Safety Information [AX6300S] Ground the Switch. Each Switch has at most 3.5 mA of leakage current. When the Switch is connected to an AC power supply unit, always use a grounded power outlet. Using the Switch without grounding could result in electric shock or failures due to electrical noise. When the Switch is connected to a DC power supply unit, always connect the ground terminal for proper grounding.
Page 55 Safety Information [AX6300S] Note that the following label is attached to the Switch. Handle power cables carefully. Do not place anything heavy on a power cable. Do not pull, bend, or process a cable. Doing so could damage the cable, resulting in fire or electric shock. If the power cable is covered by a carpet, it is easy to forget that the cable is there and to place something heavy on it.
Page 56 Safety Information [AX6300S] When pressing the button of the management and switching unit, do not use anything with a fragile tip, or anything that might become caught in the Switch, such as a pin or paper clip. When pressing the button on the front panel of the management and switching unit, do not use anything with a fragile tip, or anything that might become caught in the Switch, such as a pin or paper clip.
Page 57 Safety Information [AX6300S] Do not install the Switch in a dusty or humid location. Do not install the Switch in a dusty or humid location. Doing so could result in fire or electric shock. Condensation might form on the surfaces and the inside of the Switch if it is moved from a cold location to a warm location.
Page 58 Safety Information [AX6300S] Do not allow hair or objects near the ventilation slots. Cooling fan units are mounted in the Switch. Do not allow anything near the ventilation slots. Doing so causes heat to accumulate inside the Switch and could cause a failure.
Page 59 Safety Information [AX6300S] Handle the power cable carefully. Do not place the power cable near a heat-generating apparatus. The heat could melt the cable coating, resulting in fire or electric shock. When connecting or disconnecting the power cable from the outlet, always hold the plug, not the cable itself.
Page 60 Safety Information [AX6300S] Lithium battery The Switch has a lithium battery for the real-time clock. Incorrect handling of the lithium battery could cause the battery to heat up, explode, or catch fire, resulting in injury or a fire. Do not remove the battery from the Switch, disassemble it, heat it to 100°C or higher, incinerate it, or immerse it in water.
Page 61 Do not attach any labels to a transceiver. A label attached to the transceiver indicates that the transceiver is a standard product from ALAXALA or another manufacturer. However, such labels are attached where they do not interfere with heat dissipation from the transceiver or the mechanism that prevents the transceiver from coming loose from the cage.
Page 62 Safety Information [AX6300S] When carrying or packing a Switch and its optional modules, wear a wrist strap to protect against static electricity. Be sure to wear an antistatic wrist strap. If you handle the Switch without wearing an antistatic wrist strap, the Switch might be damaged by static electricity. When removing optional modules, attach blank panels.
Page 63 Safety Information [AX6300S] Do not use a TV or a radio near a Switch. Do not use a TV or a radio near a Switch. Placing a Switch near a TV or a radio could affect both devices. If you hear noise on the TV or radio, do the following: Place the Switch as far away as possible from the TV or radio.
Page 64 Safety Information [AX6300S] xliv...
Page 65: Safety Information [Ax3800S] [Ax3600S] [Ax2400S]
Safety Information [AX3800S] [AX3600S] [AX2400S] Using AX3800S, AX3600S, and AX2400S series switches correctly and safely This guide provides important information for ensuring safe use of AX3800S, AX3600S, and AX2400S series switches. Please read this guide completely before using the Switch. Keep this guide handy after finishing it, so that it is available for later reference.
Page 66 Safety Information [AX3800S] [AX3600S] [AX2400S] If anything seems wrong, immediately turn off the power. If smoke or an unusual smell is emanating from the Switch, or if liquid is spilled into the Switch or a foreign object falls into the Switch, immediately turn off Switch power as described below.
Page 67 Safety Information [AX3800S] [AX3600S] [AX2400S] with a liquid, such as a vase or a flowerpot, on the Switch. Liquid or metallic objects falling into the Switch could result in fire or electric shock. Use the Switch only with the indicated power supply. Do not use the Switch at any voltage other than the indicated voltage.
Page 68 Safety Information [AX3800S] [AX3600S] [AX2400S] Handle power cables carefully. Do not place anything heavy on a power cable. Do not pull, bend, or process a cable. Doing so could damage the cable, resulting in fire or electric shock. If the power cable is covered by a carpet, it is easy to forget that the cable is there and to place something heavy on it.
Page 69 Safety Information [AX3800S] [AX3600S] [AX2400S] Do not place the Switch in an unstable location. When installing the Switch on a table, position the Switch horizontally on a worktable strong enough to bear the weight of the Switch. Placing the Switch in an unstable location, such as on an unsteady or tilting surface, might cause the Switch to fall, resulting in injury.
Page 70 Safety Information [AX3800S] [AX3600S] [AX2400S] resulting in fire or electric shock. If you must stack multiple Switches during transport, use appropriate packaging. Failure to do so might cause the Switches to become deformed or damaged, resulting in a fire or electric shock. Handle the power cable carefully.
Page 71 Safety Information [AX3800S] [AX3600S] [AX2400S] eye. Never look directly into the optical transceiver. Do not touch the SFP-T and SFP-T(T) during operation and just after operation stops. During operation (when a link is established), the temperature of the SFP-T and SFP-T(T) can rise to 65°C.
Page 72 Safety Information [AX3800S] [AX3600S] [AX2400S] Install a fan unit for the slot of a redundant power model (AX3630S and AX3640S) with no power supply unit. Install a fan unit for the slot of a redundant power model (AX3630S and AX3640S) with no power supply unit.
Page 73 Safety Information [AX3800S] [AX3600S] [AX2400S] Do not place a Switch in a high-temperature location. Do not place a Switch in direct sunlight or near a heater or other heat-generating apparatus. Do not use a TV or a radio near a Switch. Do not use a TV or a radio near a Switch.
Page 74 Do not attach any labels to a transceiver or a direct attach cable connector. A label attached to the transceiver or direct attach cable connector indicates that the transceiver or direct attach cable connector is a standard product from ALAXALA or another manufacturer. However, such labels are attached where they do not...
Page 75 Safety Information [AX3800S] [AX3600S] [AX2400S] Make sure that you use a valid combination for the direct attach cable and the Switch. The following Switches support SFPP-CU1M/3M/5M. Use the transceivers only with the indicated Switches. Not doing so could result in a Switch malfunction. AX3650S-24T6XW (Supported ports: 25 to 30) AX3650S-20S6XW (Supported ports: 25 to 30) AX3650S-48T4XW (Supported ports: 49 to 52)
Page 76 Safety Information [AX3800S] [AX3600S] [AX2400S] Before cleaning, make sure that the tip of the optical connector cleaner is clean and free of defects, such as lint, dirt, or other foreign substances. Using a cleaner with a defective tip might damage the ferrule tip. Do not apply excessive pressure when cleaning.
Page 77: Overview
Overview This chapter provides an overview of failure analysis. 1.1 Overview of analyzing failures 1.2 Overview of analyzing failures of all or part of the Switch 1.3 Overview of analyzing failures of functionality...
Page 78: Overview Of Analyzing Failures
1 Overview 1.1 Overview of analyzing failures Use this manual when there is a problem in an AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, or AX2400S series switch. When failure analysis requires looking at the actual Switch, do the analysis according to 1.2 Overview of analyzing failures of all or part of the Switch.
Page 79: Overview Of Analyzing Failures Of All Or Part Of The Switch
2.1 Troubleshooting faults for AX6700S, AX6600S, and AX6300S series switches to troubleshoot the failure. The status of a switch is shown in the basic control unit (BCU) for AX6700S series switches, in the control and switching unit (CSU) for AX6600S series switches, and in the management and switching unit (MSU) for AX6300S series switches.
Page 80 #6: This LED is always off for the MSU (for AX6300S series switches) and for the BCU with a software version earlier than 11.1 (for AX6700S series switches). #7: This LED only shows the power mode of an active BCU or CSU.
Page 81: Failure Analysis For Ax3800S, Ax3600S, And Ax2400S Series Switches
1 Overview Figure 1-1 Example layout of the front panel 1.2.2 Failure analysis for AX3800S, AX3600S, and AX2400S series switches If a failure occurs during operation and the actual switch can be looked at, take appropriate action as described in 2.2 Troubleshooting faults for AX3800S, AX3600S, and AX2400S series switches to troubleshoot the failure.
Page 82 1 Overview Figure 1-2 Example layout of the front panel...
Page 83 1 Overview Table 1-2 LED indications, buttons, and connectors Name Type Status Description brightness LED: Power supply status Green Regular Power is on. Green Blinking Regular Sleep state green Power is off or the power supply failed. LED: Status of the switch Green Regular Available for operation...
Page 84 1 Overview Name Type Status Description brightness CONSO RS-232C port to Connector CONSOLE port connect a console terminal LINK LED: Operating status of Green Regular Link established, 100 Green or the SFP slot Ethernet Mbps, full duplex orange port Blinking Regular 1,000 Mbps green...
Page 85 1 Overview Name Type Status Description brightness LED: Blinking A frame is being sent or Regular Green green received Not used 1-24 LED: Operating status of Green Regular Link established, 100 Green or 10/100/1000BASE-T Mbps, full duplex orange Ethernet ports Blinking Regular A link is established...
Page 86 1 Overview Name Type Status Description brightness LED: Operating status of A link has been LINK Green Regular Green or the SFP+ slot established. orange Ethernet port Orange Regular Line failure detection Link failure or block when the green ST1 LED is on LED: Blinking...
Page 87 1 Overview #1: The LED blinks green at long intervals (turns on for 0.5 seconds and off for 5 seconds). #2: This applies when the device is in the power saving brightness mode. #3: This applies when the device is in the power saving brightness mode or in the LED off mode.
Page 88: Overview Of Analyzing Failures Of Functionality
1 Overview 1.3 Overview of analyzing failures of functionality The following table provides an overview of analyzing functional failures on the Switch. Because communication failures in a lower layer might cause communication failures in an upper layer, check the items applicable to lower layers. Table 1-3 Status of functional failures and where to find information Category Sub-category...
Page 89 1 Overview Category Sub-category Reference Layer 2 network VLAN failure 3.5.1 Layer 2 communication by VLANs is communication failures not possible Spanning tree failure 3.5.2 Failures occurring when the spanning tree functionality is used Ring Protocol failure 3.5.3 Failures occurring when the Ring Protocol functionality is used IGMP snooping not possible 3.5.4 Multicast forwarding by IGMP...
Page 90 1 Overview Category Sub-category Reference IPv6 network Communication not possible 3.9.1 Communication is not possible or is communication failures disconnected DHCP relay problems 3.9.2 IPv6 DHCP relay communication problems DHCP server problems 3.9.3 Troubleshooting IPv6 DHCP server problems IPv6 unicast routing No RIPng information 3.10.1 RIPng routing information cannot be communication failures...
Page 91 1 Overview Category Sub-category Reference IPv6 VRRP failures 3.13.3 Communication is not possible with the VRRP configuration of IPv6 networks Uplink redundancy 3.13.4 Communication is not possible with functionality failures uplink redundancy SNMP communication The MIB cannot be obtained. 3.14.1 MIBs cannot be obtained from the failures SNMP manager Traps cannot be received.
Page 92 1 Overview Category Sub-category Reference DHCP snooping problems 3.26 DHCP snooping problems Communication failures The MAC address table entries 4.1 MAC address table resource shortage caused by resource exceed the device capacity. shortage The VLAN identification table 4.2 When a VLAN identification table entries exceed the device resource shortage occurs capacity.
Page 93: Troubleshooting Switch Failures
Troubleshooting Switch Failures This chapter describes how to take actions when a failure occurs on a Switch. 2.1 Troubleshooting faults for AX6700S, AX6600S, and AX6300S series switches 2.2 Troubleshooting faults for AX3800S, AX3600S, and AX2400S series switches...
Page 94: Troubleshooting Faults For Ax6700S, Ax6600S, And Ax6300S Series Switches
2 Troubleshooting Switch Failures 2.1 Troubleshooting faults for AX6700S, AX6600S, and AX6300S series switches 2.1.1 Procedure for handling switch faults Use the procedure described below if a failure occurs on a Switch. Table 2-1 Troubleshooting Switch failures Problem Action Smoke emanates from the switch.
Page 95 2 Troubleshooting Switch Failures Problem Action The STATUS LED of the BCU, CSU, or Check the single or redundant configuration of the MSU is lit in red, the other LEDs are all off, BCU, CSU, or MSU modules. and no message is displayed on the (1) When a single configuration is used, follow steps system operation panel.
Page 96: Replacing The Switch And Optional Modules
2 Troubleshooting Switch Failures Point to be checked Action The power supply unit is not firmly installed Perform the following procedure: and is unstable. Turn the power switch off. If you are using a DC power supply unit, turn off the circuit breaker at the distribution board.
Page 97: Troubleshooting Faults For Ax3800S, Ax3600S, And Ax2400S Series Switches
2 Troubleshooting Switch Failures 2.2 Troubleshooting faults for AX3800S, AX3600S, and AX2400S series switches 2.2.1 Procedure for handling switch faults Use the procedure described below if a failure occurs on a Switch. Table 2-3 Troubleshooting switch failures Problem Action Smoke emanates from the switch. Immediately take the following actions: An abnormal odor emanates from Turn off the switch.
Page 98 2 Troubleshooting Switch Failures Problem Action The red ST1 LED of the switch is on. A fault has occurred on the switch, or the power to the switch is turned on after a long period (more than one month) of being in a non-powered state.
Page 99: Isolating The Cause Of External Power Unit Failures
2 Troubleshooting Switch Failures Problem Action The measured input power supply is outside Ask the person responsible for the facility where the the following range: switch is housed to take action regarding the input power supply. For 100 V AC: 90 to 127 V AC For 200 V AC: 180 to 254 V AC For −48 V DC: −40.5 to −57 V DC Note: Take this action only if the input power...
Page 100: Replacing The Switch And Optional Modules
2 Troubleshooting Switch Failures Table 2-7 Isolating the cause of power supply module failures Problem Action The power switch of the power supply Set the power switch of the power supply module to ON. module is off. The power cable of the power supply Set the power switch of the power supply module to module is not correctly connected to the OFF.
Page 101: Troubleshooting Functional Failures During Operation
Troubleshooting Functional Failures During Operation This chapter describes what actions to take when a problem occurs, such as when a Switch does not operate correctly or cannot communicate. 3.1 Problems related to login passwords 3.2 Memory card problems 3.3 Operation terminal problems 3.4 Network interface communication failures 3.5 Layer 2 network communication failures 3.6 IPv4 network communication failures...
Page 102: Problems Related To Login Passwords
3 Troubleshooting Functional Failures During Operation 3.1 Problems related to login passwords 3.1.1 Forgotten login user password If a user forgets his or her login user password and is unable to log in to the Switch, do the following: If another user can log in: Ask the user who can log in to execute the command in administrator password...
Page 103: Memory Card Problems
After replacing the memory card, execute the command again. If replacing the memory card does not resolve the problem, the memory card slot might have failed. For AX6700S, AX6600S, or AX6300S series switches: Replace the BCU, CSU, or MSU. For AX3800S, AX3600S, or AX2400S series switches: Replace the Switch.
Page 104 After replacing the memory card, execute the command again. If replacing the memory card does not resolve the problem, the memory card slot might have failed. For AX6700S, AX6600S, or AX6300S series switches: Replace the BCU, CSU, or MSU. For AX3800S, AX3600S, or AX2400S series switches:...
Page 105: Operation Terminal Problems
3 Troubleshooting Functional Failures During Operation 3.3 Operation terminal problems 3.3.1 Information cannot be entered from the console or does not appear correctly If a problem occurs during a connection to the console, check the problem and take action according to Table 3-3 Problems occurring during connection to the console and action to take.
Page 106 3 Troubleshooting Functional Failures During Operation Problem Items to check Login is not possible. Make sure that the login prompt is displayed on the screen. If it is not, the Switch is starting up. Wait a while. Use the aaa authentication login console configuration commands to make sure authentication login that the RADIUS or TACACS+ authentication is not set.
Page 107: Login From A Remote Terminal Is Not Possible
3 Troubleshooting Functional Failures During Operation 3.3.2 Login from a remote terminal is not possible If a problem occurs during connection to a remote terminal, check the status according to the following table. Table 3-5 Problems occurring during connection to a remote terminal and action to take Problem Action Remote connection is not...
Page 108: Login Authentication Using Radius/Tacacs+ Is Not Possible
3 Troubleshooting Functional Failures During Operation 3.3.3 Login authentication using RADIUS/TACACS+ is not possible If a login cannot be authenticated by using RADIUS or TACACS+, check the following: Communication with the RADIUS or TACACS+ server Use the command to check if a connection from the Switch to the RADIUS or ping TACACS+ server has been established.
Page 109: Command Authorization Using Radius/Tacacs+ And Local Is Not Possible
3 Troubleshooting Functional Failures During Operation 3.3.4 Command authorization using RADIUS/TACACS+ and local is not possible After RADIUS, TACACS+, or local authentication is successful and you log in to the Switch, if command authorization fails or if a command cannot be executed due to an authorization error, check the following: Checking with the command...
Page 110: Network Interface Communication Failures
3.4.1 Ethernet port cannot be connected If it is possible that the Ethernet port caused the communication failure, do the following: For AX6700S, AX6600S, or AX6300S series switches: Check the NIF status, port status, and port statistics in this order.
Page 111 3 Troubleshooting Functional Failures During Operation NIF status Cause Action is set Make sure that the NIF board to use is implemented, and disable no power enable by a configuration use the configuration command to put the power enable command. target NIF into active status.
Page 112 3 Troubleshooting Functional Failures During Operation Port state Cause Action The port is in inactive status If the port is deactivated by the standby link inactive due to one of the following functionality of the link aggregation, this is normal reasons: operating status.
Page 113: Bsu/Psp Communication Failures
3 Troubleshooting Functional Failures During Operation (3) Checking statistics You can use the command to check the number of sent and show port statistics received packets and the number of discarded send and receive packets for all ports on the Switch.
Page 114 3 Troubleshooting Functional Failures During Operation Operating Cause Action status of the BSU/PSP The configuration contains a setting Correctly set the flow distribution pattern for fault that cannot be used. the filtering and QoS functionality by using the configuration command. fldm prefer Correctly set the distribution pattern of the maximum number of entries per switch by...
Page 115: Actions To Be Taken For 10Base-T/100Base-Tx/1000Base-T Problems
3 Troubleshooting Functional Failures During Operation 3.4.3 Actions to be taken for 10BASE-T/100BASE-TX/1000BASE-T problems If a 10BASE-T/100BASE-TX/1000BASE-T problem occurs, use the following procedure to isolate the failure: Checking the log For details about the log, see the manual Message Log Reference. Isolating the cause of the problem according to the failure analysis method Isolate the cause of the problem according to the failure analysis method described in the following table.
Page 116 3 Troubleshooting Functional Failures During Operation Items to check Cause Action Use the Line quality is degraded. Check whether the cable types are correct. For show the types, see the Hardware Instruction interfaces command to display Manual. the failure statistics for the receiving side, and check whether there are counts for the...
Page 117 3 Troubleshooting Functional Failures During Operation Items to check Cause Action Execute the The cable is not Check whether the cable types are correct. For show compatible. the types, see the Hardware Instruction interfaces command and check Manual. the line type and line speed in the detail information displayed for the target port.
Page 118: Actions To Be Taken For 100Base-Fx/1000Base-X Problems
3 Troubleshooting Functional Failures During Operation 3.4.4 Actions to be taken for 100BASE-FX/1000BASE-X problems If a 100BASE-FX/1000BASE-X problem occurs, use the procedure below to isolate the failure. Checking the log For details about the log, see the manual Message Log Reference. Isolating the cause of the problem according to the failure analysis method Isolate the cause of the problem according to the failure analysis method described in the following table.
Page 119 3 Troubleshooting Functional Failures During Operation Items to check Cause Action Use the Line quality on Check the type of the optical fiber. For the mode, see the show command the receiving interfaces Hardware Instruction Manual. to display the failure side is statistics for the receiving degraded.
Page 120 3 Troubleshooting Functional Failures During Operation Items to check Cause Action If a single-core optical If 1000BASE-BX is used, one side must use a U-type fiber cable such as combination of transceiver and the other side must use a D-type 1000BASE-BX is used, transceiver.
Page 121: Actions To Be Taken For 10Gbase-R Problems
If there is a count, see the Cause and Action columns. For AX6700S, AX6600S, or AX6300S series switches: Signal detect errors LOS of sync HI_BER For AX3800S, AX3600S,...
Page 122 3 Troubleshooting Functional Failures During Operation Items to check Cause Action Use the Line quality on Check the type of the optical fiber. For the types, see the show command the receiving interfaces Hardware Instruction Manual. to display the failure side is statistics for the receiving degraded.
Page 123 3 Troubleshooting Functional Failures During Operation Items to check Cause Action For AX6700S, AX6600S, Line quality on Check the type of the optical fiber. For the types, see the or AX6300S series the sending Hardware Instruction Manual. switches, use the...
Page 124: Actions To Be Taken For Poe Problems
3 Troubleshooting Functional Failures During Operation 3.4.6 Actions to be taken for PoE problems If a problem such as a disabled power supply unit occurs when PoE is used, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 125: Communication Failures When Link Aggregation Is Used
3 Troubleshooting Functional Failures During Operation 3.4.7 Communication failures when link aggregation is used If communication is not possible or if degraded operation is in effect when link aggregation is used, isolate the cause of the problem according to the failure analysis method in the following table.
Page 126 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Partner System ID Unmatch The Partner System ID received from the partner port is different from the Partner System ID of the group, and degradation has occurred. To avoid the degradation, check the operating status of the remote device and also check the wiring.
Page 127: Layer 2 Network Communication Failures
3 Troubleshooting Functional Failures During Operation 3.5 Layer 2 network communication failures 3.5.1 Layer 2 communication by VLANs is not possible If Layer 2 communication is not possible when VLANs are used, isolate the cause of the problem according to the failure analysis method described in the table below. (1) Checking the VLAN status Execute the command or the...
Page 128 3 Troubleshooting Functional Failures During Operation 0012.e200.0001 (static) 0012.e200.00:02 (static) 0012.e200.0003 (static) 0012.e200.00:04 (dot1x) Execute the command and make sure the MAC address set for show vlan mac-vlan a VLAN by using the Layer 2 authentication functionality has not been set for another VLAN in the configuration.
Page 129 Also check whether a threshold that is too low is set for the storm control functionality. (b) Checking the MAC address learning limitation For AX6700S, AX6600S, and AX6300S series switches, execute the show command with the...
Page 130: Failures Occurring When The Spanning Tree Functionality Is Used
3 Troubleshooting Functional Failures During Operation The MAC address learning limit value has been reached, and MAC address learning has been stopped. Received frames that contain an unlearned sender MAC address are discarded without the MAC address being learned. However, frames from a VLAN for which MAC address learning is suppressed are flooded.
Page 131 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Execute the If the port status and port role for the spanning tree are the same show command for the as those defined in the network configuration, go to No. 4. spanning-tree spanning tree that caused the failure, and then check the port...
Page 132: Failures Occurring When The Ring Protocol Functionality Is Used
(for example, an incorrect combination of the attribute and ring port for the operating mode of the Switch). If there is no conflict in the configuration, for AX6700S, AX6600S, or AX6300S series switches, go to No. 2. For AX3800S, AX3600S, or AX2400S series switches,...
Page 133 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Use the If the message show logging The MAC address entry can't be registered command to check whether is not displayed, go to No. 3. at hardware tables. entries are properly registered in the MAC address table as the If the message...
Page 134 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Check the filtering and QoS The control frames used for the Ring Protocol might have been control configurations. discarded by filtering or QoS control. See 3.24.1 Checking the filtering and QoS control configuration information and check for a problem.
Page 135: Multicast Forwarding By Igmp Snooping Is Not Possible
3 Troubleshooting Functional Failures During Operation 3.5.4 Multicast forwarding by IGMP snooping is not possible If multicast forwarding is not possible when IGMP snooping is used, use the following analysis flowchart to determine the problem and isolate the cause. Figure 3-4 Analysis flowchart...
Page 136 3 Troubleshooting Functional Failures During Operation Table 3-16 Failure analysis method for multicast forwarding Items to check and Action commands Use the Check the following: show logging command and check Check whether log information about a physical fault has been whether a failure has recorded.
Page 137 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Use the Check the following: show igmp-snooping To check whether the IGMP querier that monitors the group members command to check the exists, make sure one of the following messages is displayed. IGMP snooping configuration.
Page 138: Multicast Forwarding By Mld Snooping Is Not Possible
3 Troubleshooting Functional Failures During Operation 3.5.5 Multicast forwarding by MLD snooping is not possible If multicast forwarding is impossible when MLD snooping is used, use the following analysis flowchart to determine the problem and isolate the cause. Figure 3-5 Analysis flowchart...
Page 139 3 Troubleshooting Functional Failures During Operation Table 3-17 Failure analysis method for multicast forwarding Items to check and Action commands Use the Check the following: show logging command and check whether a Check whether log information about a physical fault has been failure has occurred.
Page 140 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Use the Check the following: show mld-snooping command to check the MLD To check whether the MLD querier that monitors the group snooping configuration. members exists, make sure one of the following messages is displayed.
Page 141: Ipv4 Network Communication Failures
3 Troubleshooting Functional Failures During Operation 3.6 IPv4 network communication failures 3.6.1 Communication is not possible or is disconnected There are three probable causes of problems that occur during communication on an IPv4 network employing a Switch: A configuration related to IP communication is changed. The network configuration is changed.
Page 142 Down For AX6700S, AX6600S, and AX6300S series switches, if the target interface working as a VRF interface is not displayed, see (9) Checking the optional license OP-NPAR. If the status of the target interface is , see 3.4 Network interface communication...
Page 143 Execute the command to check the route information obtained by the show ip route Switch. For AX6700S, AX6600S, and AX6300S series switches, check whether packets are discarded at the null interface. If is displayed for the sending interface that null0 caused the communication failure in the route information, packets are discarded at the null interface.
Page 144: Ip Addresses Cannot Be Assigned By The Dhcp Functionality
3 Troubleshooting Functional Failures During Operation If the route information obtained by the Switch contains route information about the interface that caused the communication failure, the interface might have a problem with the functionality shown below. That functionality must be checked. DHCP and BOOTP functionality See (7) Checking the DHCP and BOOTP configuration information.
Page 145 For cause 2, check the differences in the network configuration before and after the change to uncover any cause that could disable communication. In this section, ALAXALA Networks Corporation considers a case to which the cause 1 or 3 applies, assuming that you have checked the client settings (such as network card settings and cable connections).
Page 146 3 Troubleshooting Functional Failures During Operation (b) Identifying the range for a failure (from the Switch) If a failure has not occurred on the Switch, a failure might have occurred somewhere on the route between the Switch and the remote device. To identify the range for a failure in order to determine the fault location on the route, do the following: Log in to the Switch.
Page 147 3 Troubleshooting Functional Failures During Operation device has a problem. To carry out the check, do the following: Log in to the Switch. Use the command to check the route information obtained by the show ip route Switch. If the route information obtained by the Switch does not contain the route information about the interface that caused the communication failure or contains an incorrect address of the interface's next hop, see 3.7 IPv4 unicast routing communication failures.
Page 148 3 Troubleshooting Functional Failures During Operation (2) Communication problems on the DHCP server There are three probable causes for problems such as disabled address distribution to clients that might occur during communication with the DHCP server: A configuration is set incorrectly. The network configuration is changed.
Page 149 3 Troubleshooting Functional Failures During Operation If DHCP snooping is used, packets might have been discarded by DHCP snooping. Check whether the setting conditions for DHCP snooping in the configuration are correct. For details about the procedure, see 3.26 DHCP snooping problems. (b) Checking the log messages and interface One probable cause of disabled assignment of IP addresses to clients is that communication between the client and the server has been disabled.
Page 150: Dynamic Dns Link Does Not Work In The Dhcp Functionality
3 Troubleshooting Functional Failures During Operation 3.6.3 Dynamic DNS link does not work in the DHCP functionality (1) Communication problems on the DHCP server There are three probable causes for communication problems on a DHCP server: A configuration is set incorrectly. The network configuration is changed.
Page 151 3 Troubleshooting Functional Failures During Operation reverse lookups are set. Make sure that DNS updating is set (see the manual Configuration Command Reference). This setting is required to enable DNS updating because DNS updating is disabled by default. Make sure that the domain name used by the client is consistent with the domain name registered in the DNS server.
Page 152 3 Troubleshooting Functional Failures During Operation and that bandwidth monitoring, drop control, or the shaper is used appropriately in the system configuration. For details about the procedure, see 3.24.1 Checking the filtering and QoS control configuration information. In addition, if DHCP snooping is used, packets might have been discarded by a terminal filter.
Page 153: Ipv4 Unicast Routing Communication Failures
3 Troubleshooting Functional Failures During Operation 3.7 IPv4 unicast routing communication failures 3.7.1 No RIP routing information exists If RIP routing information cannot be found in the routing information obtained by the Switch, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 154 3 Troubleshooting Functional Failures During Operation Table 3-19 Failure analysis method for OSPF Items to check and commands Action Display the OSPF interface status. If the interface status is P, go to No. 3. P to show ip ospf interface <IP Address>...
Page 155: No Bgp4 Routing Information Exists
3 Troubleshooting Functional Failures During Operation 3.7.3 No BGP4 routing information exists If BGP4 routing information cannot be found in the routing information obtained by the Switch, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 156: Ipv4 Routing Information Cannot Be Found In Vrf
3 Troubleshooting Functional Failures During Operation 3.7.4 IPv4 routing information cannot be found in VRF If the routing information of each protocol cannot be found in the routing information obtained by the Switch, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 157: Communication Failures In The Ipv4 Multicast Routing Functionality
For AX6700S, AX6600S, or AX6300S series If a protocol other than PIM-SM is specified for the switches, make sure that the multicast protocol multicast protocol, modify the configuration.
Page 158 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure that PIM-SM is running on one or more If PIM-SM is not running, check and modify the interfaces. configuration so that PIM-SM runs on at least one of the interfaces.
Page 159 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure that the rendezvous point has been If the rendezvous point has not been determined, determined. check whether the unicast route to the rendezvous point exists. If the unicast route does show ip pim rp-mapping not exist, see 3.7 IPv4 unicast routing communication failures.
Page 160 3 Troubleshooting Functional Failures During Operation (3) Items to check for the rendezvous point router The following table shows the items to check when the Switch is used as a rendezvous point router in an IPv4 PIM-SM network configuration. Table 3-24 Items to check for the rendezvous point router Items to check and commands Action Make sure the Switch is a rendezvous point...
Page 161: Multicast Data Is Forwarded Twice In The Ipv4 Pim-Sm Network
3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether IGMP snooping is set for the If IGMP snooping is set, check the following: interface on which the static group participation Check whether the multicast router port for functionality is used.
Page 162: Communication Is Not Possible On The Ipv4 Pim-Ssm Networks
3 Troubleshooting Functional Failures During Operation Table 3-27 Items to check when data continues to be forwarded twice Items to check and commands Action Check the PIM neighboring information of the If neighboring routers are not displayed, check interface belonging to the network with multiple the following: routers.
Page 163 3 Troubleshooting Functional Failures During Operation Items to check and commands Action For AX6700S, AX6600S, or AX6300S series If a protocol other than PIM-SM is specified for the switches, make sure that the multicast protocol multicast protocol, modify the configuration.
Page 164 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether the number of the multicast routing If a warning is displayed, check whether an information entries or multicast forwarding entries unexpected multicast routing information entry or exceeds its upper limit.
Page 165 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether any anomaly has been detected Make sure that no warning information is on any interface. displayed for Notice. If warning information is displayed, check the show ip igmp interface following: L: More participation requests than the expected maximum number have occurred.
Page 166: Multicast Data Is Forwarded Twice In The Ipv4 Pim-Ssm Network
For AX6700S, AX6600S, or AX6300S series If a protocol other than PIM-SM is specified for the switches, make sure that the multicast protocol multicast protocol, modify the configuration.
Page 167: Problems That Occur During Ipv4 Multicast Communication In The Extranet
3 Troubleshooting Functional Failures During Operation Items to check and commands Action If multiple VRFs are used, check whether a global If a global network or specific VRF occupies more network or specific VRF occupies an multicast forwarding entries than expected in the unexpectedly large number of multicast network design, check whether any unexpected forwarding entries.
Page 168: Communication Is Not Possible On The Ipv4 Pim-Dm Networks
3 Troubleshooting Functional Failures During Operation Items to check and commands Action If the PIM-SM VRF gateway is used, make sure If the destination VRF does not exist in the that the destination VRF is displayed for the downstream interface for the (*,G) entry of the downstream interface for the (*,G) entry upstream VRF, make sure that the destination VRF generated in the upstream VRF.
Page 169 3 Troubleshooting Functional Failures During Operation Table 3-34 Items checked in common Items to check and commands Action Make sure that the setting for using the multicast If the setting for using the multicast functionality functionality (ip multicast routing) exists in does not exist, modify the configuration.
Page 170 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether multicast routing information If multicast routing information does not exist, exists. check the downstream router settings. show ip mroute (2) Items to check for last-hop-router The following table shows the items to check when the Switch is used as in an IPv4 PIM-DM network configuration.
Page 171: Multicast Data Is Forwarded Twice In The Ipv4 Pim-Dm Network
3 Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure that PIM-DM is running on the interface If PIM-DM is not running, check and modify the connected to the multicast sender. configuration so that PIM-DM runs on the interface.
Page 172: Ipv6 Network Communication Failures
3 Troubleshooting Functional Failures During Operation 3.9 IPv6 network communication failures 3.9.1 Communication is not possible or is disconnected There are three probable causes of problems that occur during communication on an IPv6 network employing a Switch: A configuration related to IPv6 communication is changed. The network configuration is changed.
Page 173 Up or Down. For AX6700S, AX6600S, and AX6300S series switches, if the target interface working as a VRF interface is not displayed, see (9) Checking the optional license OP-NPAR.
Page 174 Execute the command to check the route information obtained by show ipv6 route the Switch. For AX6700S, AX6600S, and AX6300S series switches, check whether packets are discarded at the null interface. If is displayed for the sending interface that null0 caused the communication failure in the route information, packets are discarded at the null interface.
Page 175: Ipv6 Dhcp Relay Communication Problems
3 Troubleshooting Functional Failures During Operation RA functionality See (8) Checking the RA configuration information. (7) Checking the filtering and QoS control configuration information Certain packets might have been discarded either by filtering or by bandwidth monitoring, drop control, or the QoS control shaper. Make sure that the setting conditions for filtering and QoS control in the configuration are correct, and that bandwidth monitoring, drop control, or the shaper is used appropriately in the system configuration.
Page 176 For cause 2, check the differences in the network configuration before and after the change to uncover any cause that could disable communication. In this subsection, ALAXALA Networks Corporation considers a case to which the cause 1 or 3 applies, assuming that you have checked the client settings. This is a case when, for...
Page 177 3 Troubleshooting Functional Failures During Operation devices up to the remote device, beginning with the device closest to the Switch. If the execution result of the command indicates that the failure occurred ping ipv6 on the neighboring device, see (3) Checking the NDP resolution information with a neighboring device.
Page 178: Troubleshooting Ipv6 Dhcp Server Problems
3 Troubleshooting Functional Failures During Operation (6) Checking the IPv6 DHCP relay configuration information If many of the prefixes or addresses to be leased are left on the IPv6 DHCP server, it can be assumed that the prefixes or addresses cannot be assigned to clients due to incorrect configuration settings for the IPv6 DHCP relay.
Page 179 3 Troubleshooting Functional Failures During Operation Figure 3-15 Failure analysis procedure on the IPv6 DHCP server (a) Checking the log and interface Probable causes of disabled communication are a failure (or damage) of the NIM or interface and a failure of a neighboring device. Check the log displayed by the Switch or use the command to check whether the interface status is show ipv6 interface...
Page 180 3 Troubleshooting Functional Failures During Operation the prefixes available for assignment by the IPv6 DHCP server. For details about the check procedure, see the Configuration Guide. If it is found that the remainder of the prefixes is zero, increase the total number of prefixes available for assignment. Note that the upper limit of the number of prefixes available for assignment is 1,024.
Page 181 3 Troubleshooting Functional Failures During Operation 3ffe:aaaa:1234::/48 05/04/01 11:29:00 Automatic 00:01:00:01:55:55:55:55:00:11:22:33:44:55 > If the same DUIDs are displayed multiple times as shown in the underlined lines, the relevant client might have incorrectly received prefix information. Check the prefix value assigned to each client. Establishing correspondences between the assigned prefixes and clients If you cannot find a client with duplicate prefixes in the result of the show ipv6 dhcp...
Page 182 3 Troubleshooting Functional Failures During Operation Table 3-38 Isolating the cause of a failure related to the route information setting for prefix assignment targets Conditions Causes Does the binding information exist? for clients Not applicable. The status is active. Cause 2 Cause 2 Causes 1 and 2 The route information for prefix assignment targets is not always retained, as shown in the...
Page 183 3 Troubleshooting Functional Failures During Operation 3ffe:aaaa:1234::/48 osaka Static <Active Gateway Dhcp> > (b) Setting the route information again Consider the case where the automatic route setting functionality is used for assigning prefixes from the IPv6 DHCP server on the Switch to assignment targets. In this case, if an event has cleared the route information due to a failure, the prefixes must be assigned again.
Page 184: Ipv6 Unicast Routing Communication Failures
3 Troubleshooting Functional Failures During Operation 3.10 IPv6 unicast routing communication failures 3.10.1 RIPng routing information cannot be found If RIPng routing information cannot be found in the routing information obtained by the Switch, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 185: Ospfv3 Routing Information Cannot Be Found
3 Troubleshooting Functional Failures During Operation 3.10.2 OSPFv3 routing information cannot be found If OSPFv3 routing information cannot be found in the routing information obtained by the Switch, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 186: No Bgp4+ Routing Information Exists
3 Troubleshooting Functional Failures During Operation 3.10.3 No BGP4+ routing information exists If BGP4+ routing information cannot be found in the routing information obtained by the Switch, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 187: No Ipv6 Routing Information Exists In The Vrf
3 Troubleshooting Functional Failures During Operation 3.10.4 No IPv6 routing information exists in the VRF If routing information for each protocol cannot be found in the routing information obtained by the Switch, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 188: Communication Failures In The Ipv6 Multicast Routing Functionality
3 Troubleshooting Functional Failures During Operation 3.11 Communication failures in the IPv6 multicast routing functionality This section describes actions to be taken when an IPv6 multicast communication failure occurs on the Switch. 3.11.1 Communication is not possible on the IPv6 PIM-SM networks If multicast forwarding is not possible in an IPv6 PIM-SM network configuration, isolate the cause of the problem according to the failure analysis method described below.
Page 189 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure that PIM is running on one or more If PIM is not running, check and modify the interfaces. configuration so that PIM runs on at least one of the interfaces.
Page 190 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure that the rendezvous point group If the forwarding target group address is not addresses contain the forwarding target group contained, check the rendezvous point router address. settings.
Page 191 3 Troubleshooting Functional Failures During Operation (3) Items to check for the rendezvous point router The following table shows the items to check when the Switch is used as a rendezvous point router in an IPv6 PIM-SM network configuration. Table 3-46 Items to check for the rendezvous point router Items to check and commands Action Make sure the Switch is a rendezvous point...
Page 192: Multicast Data Is Forwarded Twice In The Ipv6 Pim-Sm Network
3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether MLD snooping is set for the If MLD snooping is set, check the following: interface on which the static group participation Check whether the multicast router port for functionality is used.
Page 193: Communication Is Not Possible On The Ipv6 Pim-Ssm Networks
3 Troubleshooting Functional Failures During Operation Table 3-49 Items to check when data continues to be forwarded twice Items to check and commands Action Check the PIM neighboring information of the If neighboring routers are not displayed, check interface belonging to the network with multiple the following: routers.
Page 194 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure that the address setting for the If the address setting for the loopback interface loopback interface exists in the configuration. does not exist in the configuration, modify the configuration.
Page 195 3 Troubleshooting Functional Failures During Operation (2) Items to check for last-hop-router The following table shows the items to check when the Switch is used as in an IPv6 PIM-SSM network configuration. last-hop-router Table 3-51 Items to check for last-hop-router Items to check and commands Action If the mode of the multicast receivers is MLDv1 or...
Page 196: Multicast Data Is Forwarded Twice In The Ipv6 Pim-Ssm Network
3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether any anomaly has been detected Make sure that no warning information is on any interface. displayed for Notice. If warning information is displayed, check the show ipv6 mld interface following: L: More participation requests than the expected maximum number have occurred.
Page 197: Ipv6 Multicast Communication Problems In Vrf
3 Troubleshooting Functional Failures During Operation Table 3-53 Items to check when data continues to be forwarded twice Items to check and commands Action Check the PIM neighboring information of the If neighboring routers are not displayed, check interface belonging to the network with multiple the following: routers.
Page 198: Ipv6 Multicast Communication Problems In An Extranet
3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check each VRF configuration by using the Specify the target VRF for each command to check the check items in 3.11.1 Communication is not information of the VRF. For details about specifying VRF, see the manual Operation Command Reference.
Page 199: Layer 2 Authentication Communication Failures
3 Troubleshooting Functional Failures During Operation 3.12 Layer 2 authentication communication failures 3.12.1 Communication failures occurring when IEEE 802.1X is used If authentication is not possible when IEEE 802.1X is used, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-56 Authentication failure analysis method for IEEE 802.1X Items to check and Action...
Page 200 MAC address table for the hardware failed. See the appropriate part in the manual Message Log Reference, and take the action described in Action. For AX6700S, AX6600S, and AX6300S series switches, see 4.1.2 Actions to be taken when a MAC address table resource shortage occurs.
Page 201 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Failed to assign VLAN. (Reason: Tunnel-Medium-Type Attribute is not IEEE802(6) ) displayed, dynamic allocation has failed. This is because the value of the attribute is not IEEE802(6) Tunnel-Medium-Type or because the value of the attribute is Tunnel-Medium-Type...
Page 202: Communication Failures Occurring When Web Authentication Is Used
If the login page or logout page is not displayed in fixed or dynamic VLAN mode, check and modify the following settings: AX6700S, AX6600S, and AX6300S series switches: Make sure that a Web authentication IP address has been set with the web-authentication ip address configuration command.
Page 203 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Make sure that the Web server Execute the following command to check whether the Web is running. server is running. If the Web server is running, go to No. 4. Command: # ps -auwx | grep httpd Check procedure:...
Page 204 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Use the If the value displayed for under show TxTotal [RADIUS frames] is 0, check whether the web-authentication aaa authentication command to statistics web-authentication default group radius check the communication status configuration commands have been radius-server host with the RADIUS server.
Page 205 (by executing the web-authentication system-auth-control command). System switching occurs on AX6700S series switches (BCU), AX6600S series switches (CSU), or AX6300S series switches (MSU). restart web-authentication web-server command is used to restart the Web server.
Page 206 Configuration for fixed VLAN mode: web-authentication ip address web-authentication port web-authentication static-vlan max-user web-authentication web-port For AX6700S, AX6600S, and AX6300S series switches, make sure also the following commands have been set. authentication ip access-group web-authentication redirect-vlan web-authentication redirect-mode For AX3800S, AX3600S, and AX2400S series switches, make sure also the following commands have been set.
Page 207 3 Troubleshooting Functional Failures During Operation Items to check Items to check Check the filtering For dynamic VLAN mode, when the filtering is used for an L3 switch, configuration. make sure that the filters are correctly set between the following VLANs: From the VLAN used for authentication to the post-authentication VLAN: A filter is set to disable all IP...
Page 208: Communication Failures Occurring When Mac-Based Authentication Is Used
3 Troubleshooting Functional Failures During Operation Items to check Items to check command has been set. 3.12.3 Communication failures occurring when MAC-based authentication is used If a failure occurs when MAC-based authentication is used, isolate the cause of the problem according to the failure analysis method described in Table 3-61 Failure analysis method for MAC-based authentication.
Page 209 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Check whether the MAC If the MAC address is not registered as the user ID of the address and password are RADIUS server, register the MAC address on the RADIUS registered on the RADIUS server.
Page 210 3 Troubleshooting Functional Failures During Operation Table 3-62 Checking the configuration of MAC-based authentication Items to check Items to check Check the MAC-based authentication Make sure the following configuration commands have configuration settings. been set correctly. aaa accounting mac-authentication default start-stop group radius aaa authentication mac-authentication default group radius mac-authentication password...
Page 211: Communication Failures Occurring When An Authentication Vlan Is Used
3 Troubleshooting Functional Failures During Operation 3.12.4 Communication failures occurring when an authentication VLAN is used If a failure occurs when an authentication VLAN is used, isolate the cause of the problem according to the following table. Table 3-64 Failure analysis method for the authentication VLAN Items to check and commands Action Execute the...
Page 212 L2MAC manager program. For other cases, go to No. 9. Execute the For AX6700S, AX6600S, or AX6300S series show fense logging command, and make sure switches, if The registration of the MAC communication with the authentication is output in the log of the address failed.
Page 213 3 Troubleshooting Functional Failures During Operation Items to check Items to check Check the DHCP relay agent Make sure that the DHCP relay agents are correctly set configuration. between the following VLANs: Between the VLAN used for authentication and the VLAN for the authentication server Between the authenticated VLAN and the VLAN for the authentication server...
Page 214: Communication Failures In The High-Reliability Functionality
3 Troubleshooting Functional Failures During Operation 3.13 Communication failures in the high-reliability functionality 3.13.1 GSRP communication failures If communication is not possible in a GSRP configuration, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-66 Communication failure analysis method for a GSRP configuration Items to check and commands Action...
Page 215 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Use the command with If the method for flushing the MAC address table is show gsrp GSRP parameter to check the and is not suitable for the current GSRP configuration, port Reset method (GSRP, Reset, or No) for...
Page 216 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Use the If the delay time (port-up-delay) is and you want to show gsrp detail infinity include the number of up ports Ports) in the number of active show gsrp port <GSRP-ID>...
Page 217: Communication Is Not Possible With The Vrrp Configuration Of Ipv4 Networks
For the virtual routers of the Switch For AX6700S, AX6600S, or AX6300S series switches: and remote devices that make up a If multiple virtual routers are master routers, go to No. 4.
Page 218 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Execute the If VLANs and VRIDs for the primary virtual router are different show vrrpstatus command with the among devices that make up the virtual routers, multiple routers detail parameter, and check whether will be master routers.
Page 219 3 Troubleshooting Functional Failures During Operation Items to check and commands Action increases in the statistics, check whether the authentication password setting exists in the Switch and remote device. You might find that the following is registered in the reference log: Virtual router <VRID>...
Page 220: Communication Is Not Possible With The Vrrp Configuration Of Ipv6 Networks
3 Troubleshooting Functional Failures During Operation Items to check and commands Action Execute the If the status of the virtual router is Initial, check the following: show vrrpstatus command with the detail If the current priority is not zero, resolve the cause of parameter, and make sure that the disabling the virtual router that is displayed for Admin...
Page 221 Items to check and commands Action For the virtual routers of the Switch For AX6700S, AX6600S, or AX6300S series switches: and remote devices that make up a If multiple virtual routers are master routers, go to No. 4. virtual router, check whether only...
Page 222 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Execute the You might find that the following is registered in the reference show vrrpstatus command with the log: statistics Virtual router <VRID> <Interface Name> parameter, and check the reception received VRRP packet for which the status of ADVERTISEMENT advertisement interval is different than the...
Page 223 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Execute the For the physical port to which a remote device that makes up the show interfaces command and check the statistics same virtual router is connected, you might find that the Input for the physical port to which a values are large and the line load is high.
Page 224: Communication Is Not Possible With Uplink Redundancy
3 Troubleshooting Functional Failures During Operation 3.13.4 Communication is not possible with uplink redundancy If communication is not possible in an uplink redundancy configuration, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-71 Failure analysis method for uplink redundancy Items to check and commands Action...
Page 225: Snmp Communication Failures
3 Troubleshooting Functional Failures During Operation 3.14 SNMP communication failures 3.14.1 MIBs cannot be obtained from the SNMP manager Make sure the configuration has been set correctly. When using SNMPv1 or SNMPv2C Execute the configuration command, and check whether the IP show access-list address of the SNMP manager has been set in the access list in the configuration.
Page 226 3 Troubleshooting Functional Failures During Operation When using SNMPv3 Execute the configuration command, and check whether the show snmp-server information about SNMP and traps has been set correctly in the configuration of the Switch. If the information has not been set correctly, execute the following configuration commands to set the information about SNMP and traps.
Page 227: Troubleshooting The Sflow Statistics (Flow Statistics) Functionality
3 Troubleshooting Functional Failures During Operation 3.15 Troubleshooting the sFlow statistics (flow statistics) functionality The following figure shows the workflow for troubleshooting the sFlow statistics functionality on the Switch. Figure 3-19 Workflow for troubleshooting the sFlow statistics functionality 3.15.1 sFlow packets cannot be sent to the collector (1) Checking the route to the collector See 3.6.1 Communication is not possible or is disconnected and 3.9.1 Communication is not possible or is disconnected, and make sure that the network is correctly connected to...
Page 228 3 Troubleshooting Functional Failures During Operation Collector IP address: 192.168.4.203 UDP:65535 Source IP address: 130.130.130.1 Send FlowSample UDP packets : 12077 Send failed packets: Send CounterSample UDP packets: Send failed packets: > Note: Make sure that the underlined values increase. (3) Checking the configuration Check the following in the active configuration: Make sure that the IP address and UDP port number of the collector to which sFlow...
Page 229: Flow Samples Cannot Be Sent To The Collector
3 Troubleshooting Functional Failures During Operation (config)# Make sure that filter has not been set for the physical port at which the flow statistics are recorded. For details about the procedure, see 3.24.1 Checking the filtering and QoS control configuration information. If the sender (agent) IP address of an sFlow packet has been set by using the sflow command, make sure that the IP address has been assigned to the port of...
Page 230: Counter Samples Cannot Be Sent To The Collector
3 Troubleshooting Functional Failures During Operation Figure 3-27 Example of the port status > show interfaces gigabitethernet 1/5 Date 2006/10/24 17:19:34 UTC NIF1: active 48-port 10BASE-T/100BASE-TX/1000BASE-T retry:0 Average:150Mbps/24Gbps Peak:200Mbps at 15:44:37 Port5: active up 100BASE-TX full(auto) 0012.e220.ec31 Time-since-last-status-change:1:47:47 Bandwidth:10000kbps Average out:5Mbps Average in:5Mbps Peak out:5Mbps at 15:44:36 Peak in:5Mbps at 15:44:18...
Page 231: Communication Failures In The Neighboring Device Management Functionality
3 Troubleshooting Functional Failures During Operation 3.16 Communication failures in the neighboring device management functionality 3.16.1 Neighboring device information cannot be obtained by the LLDP functionality If neighboring device information cannot be obtained correctly by using the LLDP functionality, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 232: Neighboring Device Information Cannot Be Obtained By The Oadp Functionality
3 Troubleshooting Functional Failures During Operation 3.16.2 Neighboring device information cannot be obtained by the OADP functionality If neighboring device information cannot be obtained correctly by using the OADP functionality, isolate the cause of the problem according to the failure analysis method described in the following table.
Page 233 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Execute the command, If the information is not displayed, check No. 1 through No. 6 on show oadp and check the neighboring device the neighboring device. If the neighboring device also does not information for the port to which the display the neighboring device information for the target port, the neighboring device is connected.
Page 234: Ntp Communication Failures
3 Troubleshooting Functional Failures During Operation 3.17 NTP communication failures 3.17.1 The Switch cannot be synchronized by using NTP If the system clock cannot be synchronized by NTP, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-74 NTP failure analysis method Items to check and commands Action...
Page 235: Communication Failures In The Ieee 802.3Ah/Udld Functionality
3 Troubleshooting Functional Failures During Operation 3.18 Communication failures in the IEEE 802.3ah/UDLD functionality 3.18.1 Port is in inactivate status by the IEEE 802.3ah/UDLD functionality If the IEEE 802.3ah/UDLD functionality has deactivated a port, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-75 Failure analysis method when the IEEE 802.3ah/UDLD functionality is used Items to check and commands Action...
Page 236 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check the cable connection. The cable might be defective. Replace the cable used for the target port. Note: IEEE 802.3ah/OAM: An OAM protocol defined in IEEE 802.3ah IEEE 802.3ah/UDLD: Unidirectional link failure detection functionality specific for a Switch that uses IEEE 802.3ah/OAM...
Page 237: Problems Due To The Redundant Configuration Of The Bcu, Csu, Or Msu
3 Troubleshooting Functional Failures During Operation 3.19 Problems due to the redundant configuration of the BCU, CSU, or MSU 3.19.1 Active-standby switchover is not possible If switching between the active and standby systems is not possible, check the problem and take action according to the following table. Table 3-76 Problems occurring during switchover of the active system and action to take Cause of the problem in Items to check...
Page 238: Problems Due To The Redundant Configuration Of The Bsu
3 Troubleshooting Functional Failures During Operation 3.20 Problems due to the redundant configuration of the BSU 3.20.1 BSU switchover is not possible If the active and standby BSUs cannot be switched in a redundant BSU configuration, perform the check procedure described below. Checking the log For details about the log, see the manual Message Log Reference.
Page 239 3 Troubleshooting Functional Failures During Operation Operating status Cause Action of BSU units Different types of BSU units are Implement only one type of BSU board. implemented. A BSU not supported in this Check the type of the BSU board and the software version is implemented.
Page 240: Problems Due To The Redundant Configuration Of The Nif
3 Troubleshooting Functional Failures During Operation 3.21 Problems due to the redundant configuration of the NIF 3.21.1 The standby NIF cannot be switched to the active system If a failure occurs on the active NIF in a redundant NIF configuration but the standby NIF cannot be switched to the active system, isolate the cause of the problem according to the following table.
Page 241: Power Saving-Related Problems
3 Troubleshooting Functional Failures During Operation 3.22 Power saving-related problems 3.22.1 Scheduling is disabled If scheduling is disabled, perform the check procedure described below. Execute the command to check whether the show power-control schedule displayed schedule contains the current time, and isolate the cause of the problem according to the following table.
Page 242: Packet Congestion In Cpu Processing Does Not Recover
3 Troubleshooting Functional Failures During Operation 3.23 Packet congestion in CPU processing does not recover This section describes how to take actions if packet congestion in CPU processing is not cleared up. Packet congestion in CPU processing occurs due to the overflow of the input queue when the CPU receives a large number of packets to be processed in software.
Page 243 Revise the network configuration. If there is no problem in the network configuration, check the settings of the terminal that has the source address. Collect analysis information. Send the collected information to the support division. For AX6700S series switches: Execute the show command and tech-support...
Page 244: Communication Failures In Filtering And Qos Configurations
(3) Checking whether packets have been discarded by drop control and the QoS control legacy shaper For AX6700S, AX6600S, and AX6300S series switches: Log in to the Switch. Execute the command with the...
Page 245 Check whether drop control and the legacy shaper are being used appropriately in the system configuration. (4) Checking whether packets have been discarded by drop control and the QoS control hierarchical shaper For AX6700S, AX6600S, and AX6300S series switches: Log in to the Switch. Execute the command with the...
Page 246: Access List Logging Problems
If the settings are not correct, modify the configuration. If the settings are correct, go to No. 5. Collect analysis information. Send the collected information to the support division. For AX6700S series switches: Execute the command, show tech-support dump command, and...
Page 247: Dhcp Snooping Problems
3 Troubleshooting Functional Failures During Operation 3.26 DHCP snooping problems 3.26.1 Problems related to DHCP If DHCP cannot assign IP addresses in a DHCP snooping configuration, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-83 Failure analysis method when DHCP cannot assign IP addresses in a DHCP snooping configuration Items to check...
Page 248 3 Troubleshooting Functional Failures During Operation Items to check Action If packets via DHCP relay are forwarded, Packets forwarded via DHCP relay are discarded make sure that the because the client hardware address and the source no ip dhcp snooping configuration MAC address in the packets are different.
Page 249: Problems Related To Saving The Binding Database
3 Troubleshooting Functional Failures During Operation 3.26.2 Problems related to saving the binding database If binding information cannot be inherited at a device restart, probable causes are problems related to saving the binding database. Isolate the cause of the problem according to the failure analysis method described in the following table.
Page 250: Problems Related To Arp
3 Troubleshooting Functional Failures During Operation 3.26.3 Problems related to ARP If ARP packets are discarded, IPv4 communication is not possible. A probable cause of ARP packets being discarded is dynamic ARP inspection. Isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-85 Failure analysis method for problems caused by dynamic ARP inspection Items to check Action...
Page 251 3 Troubleshooting Functional Failures During Operation Items to check Action Execute the If the binding information is not present and the target show ip dhcp snooping command, and make sure that the device has a fixed IP address, set the binding ip source binding information is present for the device...
Page 252 3 Troubleshooting Functional Failures During Operation...
Page 253: Troubleshooting Communication Failures Due To A Resource Shortage
Troubleshooting Communication Failures Due to a Resource Shortage This chapter describes communication failures due to a resource shortage in AX6700S, AX6600S, and AX6300S series switches. 4.1 MAC address table resource shortage 4.2 When a VLAN identification table resource shortage occurs...
Page 254: Mac Address Table Resource Shortage
4 Troubleshooting Communication Failures Due to a Resource Shortage 4.1 MAC address table resource shortage 4.1.1 Checking the MAC address table resource usage The Switch outputs operation log messages when the MAC address table entries reach 80% and 100% of the device capacity. The table below lists the operation log message to be output.
Page 255 4 Troubleshooting Communication Failures Due to a Resource Shortage Trigger Log message IGMP snooping registration IGMP snooping: The number of the IGMP snooping entry exceeded the capacity of this system. MLD snooping registration MLD snooping: The number of the MLD snooping entry exceeded the capacity of this system.
Page 256 4 Troubleshooting Communication Failures Due to a Resource Shortage Entry to be deleted Procedure MAC address for Ring Protocol Execute the configuration command to disable disable the Ring Protocol. Execute any of the following configuration commands to clear the configuration. no axrp no axrp vlan-mapping no axrp-ring-port...
Page 257: When A Vlan Identification Table Resource Shortage Occurs
4 Troubleshooting Communication Failures Due to a Resource Shortage 4.2 When a VLAN identification table resource shortage occurs 4.2.1 Checking the VLAN identification table resource usage The Switch outputs an operation log message when the VLAN identification table entries reach 80% of the device capacity. The table below lists the operation log message to be output.
Page 258 4 Troubleshooting Communication Failures Due to a Resource Shortage Trigger Log message Configuring a MAC VLAN static entry The MAC-VLAN MAC Address entry can't be registered at hardware tables. IEEE 802.1X (VLAN-based authentication The 802.1X Supplicant MAC address of [dynamic]) MAC VLAN can't be registered at hardware tables.
Page 259 4 Troubleshooting Communication Failures Due to a Resource Shortage Table 4-6 How to delete VLAN identification table entries Entry to be deleted Procedure Tag translation Execute the no switchport vlan mapping enable configuration no switchport vlan mapping commands. Protocol VLAN Execute the configuration no switchport protocol...
Page 260: When A Resource Shortage Occurs In Shared Memory
4 Troubleshooting Communication Failures Due to a Resource Shortage 4.3 When a resource shortage occurs in shared memory 4.3.1 Checking the resource usage of shared memory You can check the usage of shared memory installed on a Switch by using the show system command.
Page 261: Obtaining Failure Information
Obtaining Failure Information This chapter mainly describes how to obtain failure information. 5.1 Collecting maintenance information 5.2 Transferring maintenance information files 5.3 Collecting information and transferring files by using the "show tech-support" command 5.4 Collecting information and transferring files by using the "ftp" command on a remote terminal 5.5 Writing data to a memory card...
Page 262: Collecting Maintenance Information
You can also use operation commands to capture dump information. 5.1.1 Maintenance information (1) Maintenance information for AX6700S, AX6600S, and AX6300S series switches The following table lists the maintenance information for AX6700S, AX6600S, and AX6300S series switches. Table 5-1 Maintenance information (AX6700S, AX6600S, and AX6300S) Item...
Page 263 5 Obtaining Failure Information Item Path and file name Remarks PSP dump in the system in which /usr/var/hardware/psp**.cmd information file the command is executed created when the (For versions prior to Version 10.5: /dump0/psp**.cmd dump psp the system in which the command is executed) command is if the specified PSP is CSU1/MSU1, or if the...
Page 264: Collecting Failure Information By Using The "Dump" Command
5.1.2 Collecting failure information by using the "dump" command In the AX6700S, AX6600S, and AX6300S series, you can use operation commands to capture memory dump information of the board or other components of the switch. The dump procedures are described below.
Page 265 5 Obtaining Failure Information Dump command accept. > 11/01 17:43:42 E3 BSU BSU:1 25070700 1681:000000000000 BSU online dump command executed. After the above log information is displayed, execute the following command. dump > dump bsu 2 Dump command accept. > 11/01 18:10:42 E3 BSU BSU:2 25070700 1681:000000000000 BSU online dump command executed.
Page 266 /usr/var/hardware /dump0 in which the commands were executed. You need to delete the memory dump files after capturing the memory dumps. In the AX6700S series: In the active BCU, execute the command for all the BSUs that are dump bsu installed.
Page 267 5 Obtaining Failure Information 11/01 18:15:42 E3 NIF NIF:1 25000700 1240:000000000000 NIF online dump command executed. After the above log information is displayed, log in to the standby BCU, and then execute the following command. dump SBY:> dump bsu 1 Dump command accept.
Page 268 5 Obtaining Failure Information 11/01 18:20:42 E3 CSU 25070700 2301:000000000000 PSP online dump command executed. In the AX6300S series: In the active system, execute the command for the PSP in the active dump psp system. In the active system, execute the command for the port that has dump nif failed.
Page 269 5 Obtaining Failure Information (3) Capturing a memory dump when a communication failure occurs after a switchover of the BSU systems When a communication failure occurs after a BSU switchover, execute all of the following commands to capture memory dumps. The captured memory dump files are stored in (for versions prior to Version 10.5, in ) in the system in which /usr/var/hardware...
Page 270: Transferring Maintenance Information Files
5 Obtaining Failure Information 5.2 Transferring maintenance information files This section describes how to transfer files that contain log or dump information. command available for the Switch allows you to transfer files containing maintenance information to a remote terminal or remote host. AX3800S, AX3600S, and AX2400S series switches also have the ability to transfer files to a console by using the command.
Page 271 5 Obtaining Failure Information (2) Transferring log information to a remote terminal Figure 5-2 Transferring log information to a remote terminal > show logging > log.txt > show logging reference > log_ref.txt > ftp 192.168.0.1 <---1 Connected to 192.168.0.1. 220 FTP server (Version 6.00LS) ready. Name (192.168.0.1:staff1): staff1 331 Password required for staff1.
Page 272: Transferring Files Using The "Zmodem" Command
5 Obtaining Failure Information (3) Transferring an error save information file to a remote terminal Figure 5-3 Transferring an error save information file to a remote terminal > cd /usr/var/core/ > ls <---1 nimd.core nodeInit.core > ftp 192.168.0.1 <---2 Connected to 192.168.0.1. 220 FTP server (Version 6.00LS) ready.
Page 273 5 Obtaining Failure Information (1) Transferring a dump file to a console Figure 5-4 Transferring a dump file to a console > cd <---1 <dump file directory> > zmodem put <---2 <dump file name> > Specify the source directory. Transfer the dump file. (2) Transferring log information to a console Figure 5-5 Transferring a log file to a console >...
Page 274: Collecting Information And Transferring Files By Using The "Show Tech-Support" Command
(1) Collecting information and transferring files by using the "show tech-support" command (AX6700S, AX6600S, and AX6300S series switches) Figure 5-7 Transferring maintenance information files to a remote terminal (AX6700S, AX6600S, and AX6300S series switches) > show tech-support ftp <---1...
Page 275 5 Obtaining Failure Information (2) Collecting information and transferring files by using the "show tech-support" command (AX3800S, AX3600S, and AX2400S series switches) Figure 5-8 Transferring maintenance information files to a remote terminal (AX3800S, AX3600S, and AX2400S series switches) > show tech-support ftp <---1 Specify Host Name of FTP Server.
Page 276: Collecting Information And Transferring Files By Using The "Ftp" Command On A Remote Terminal
5 Obtaining Failure Information 5.4 Collecting information and transferring files by using the "ftp" command on a remote terminal You can use the command on a remote terminal or remote server to connect to the Switch and to obtain failure or maintenance information by specifying a file name. (1) Collecting "show tech-support"...
Page 277 5 Obtaining Failure Information Figure 5-9 Obtaining the "show tech-support" unicast information <---1 client-host> ftp 192.168.0.60 Connected to 192.168.0.60. 220 192.168.0.60 FTP server (NetBSD-ftpd) ready. Name (192.168.0.60:staff1): staff1 331 Password required for staff1. Password: 230 User staff1 logged in. Remote system type is UNIX. Using binary mode to transfer files.
Page 278 5 Obtaining Failure Information Figure 5-10 Obtaining dump files from a remote terminal client-host> ftp 192.168.0.60 <---1 Connected to 192.168.0.60. 220 192.168.0.60 FTP server (NetBSD-ftpd) ready. Name (192.168.0.60:staff1): staff1 331 Password required for staff1. Password: 230 User staff1 logged in. Remote system type is UNIX.
Page 279: Writing Data To A Memory Card
5 Obtaining Failure Information 5.5 Writing data to a memory card Failure and maintenance information can be written to a memory card. Note, however, that memory cards have a capacity limit. 5.5.1 Writing data to a memory card by using an operation terminal This section describes how to write the Switch information to a memory card by using an operation terminal.
Page 280 5 Obtaining Failure Information...
Page 281: Line Testing
Line Testing 6.1 Testing a line...
Page 282: Testing A Line
What loops back Fault location to be identified frames Internal Switch AX6700S, AX6600S, and AX6300S series switches loopback test NIF (except for the RJ45 connector and transceiver) AX3800S, AX3600S, and AX2400S series switches Switch (except for the RJ45 connector and transceiver)
Page 283: Loop Connector Loopback Test
6 Line Testing Figure 6-2 Example of an internal loopback test > inactivate gigabitethernet 1/1 > test interfaces gigabitethernet 1/1 internal interval 2 pattern 4 > no test interfaces gigabitethernet 1/1 Date 2006/03/10 00:20:21 UTC Interface type :100BASE-TX Test count Send-OK Send-NG Receive-OK...
Page 284 6 Line Testing using a crimping tool. Figure 6-3 Overview of a 10BASE-T/100BASE-TX loop connector (3) 10BASE-T/100BASE-TX/1000BASE-T loop connector Create two 6-to-7-cm long twisted pair cables before you start the procedure. Figure 6-4 Twisted pair cable As shown in the following figure, insert the cables into the connector and crimp them by using a crimping tool.
Page 285: Device Restart
Device Restart This chapter mainly describes how to restart the device. 7.1 Restarting the device...
Page 286: Restarting The Device
For details on the syntax and parameters of the command, see the manual Operation Command Reference. AX6700S, AX6600S, and AX6300S series switches As an example, the following steps describe how to select parameters for the reload command. In this example, you choose to restart the standby system and capture the CPU memory dump of the BCU, CSU, or MSU by interacting with the confirmation messages.
Page 287 7 Device Restart According to the figure above, you do not use any parameters. Step 3 In the last step, specify the system you want to restart or stop. Figure 7-3 Selection of the system or systems to be stopped In step 3, you choose to restart the standby system.
Page 288 7 Device Restart AX3800S, AX3600S, and AX2400S series switches As an example, the following steps describe how to select parameters for the reload command. In this example, you choose to restart the device and capture the CPU memory dump by interacting with the confirmation messages. Step 1 Choose whether you want to restart or stop the device.
Page 289 7 Device Restart Figure 7-7 Confirmation messages for CPU memory dump capturing...
Page 290 7 Device Restart...
Page 291: Appendix
Appendix A Detailed Display Contents of the "show tech-support" Command...
Page 292: Detailed Display Contents Of The "Show Tech-Support" Command
A.1.1 AX6700S, AX6600S, and AX6300S series switches The following table lists the commands, the information that they display, and parameter information for AX6700S, AX6600S, and AX6300S series switches. Table A-1 Command details (AX6700S, AX6600S, and AX6300S series switches) Command (displayed) Description...
Page 293 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Internal information of the kernel and daemons (for Version 10.5 /standby/var/log/messages and later) Kernel internal statistics /usr/local/diag/statShow Operating time information (for /usr/local/diag/pk_tmrd Version 11.2 and later) File descriptor information fstat Internal device-related information /usr/local/diag/rtsystat...
Page 294 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description active system Chronological log information for show logging standby the standby system Reference log information for the show logging reference standby standby system Operating information of the NTP show ntp associations server Login-related information...
Page 295 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Log information created when software is updated (for Version /standby/usr/var/pplog/pp 11.1 and later) update.log Log information created when software is updated (for Version /standby/usr/var/pplog/pp update2.log 11.1 and later) Authentication trace information tail -n 30 /var/log/authlog...
Page 296 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Configuration for operation show running-config Link aggregation details show channel-group detail Spanning tree details show spanning-tree detail Details for all GSRPs show gsrp all Ring Protocol details show axrp detail IEEE 802.3ah/OAM functionality show efmoam detail configuration information and port...
Page 297 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Statistics on the hierarchical show shaper shaper functionality (for Version 10.7.A and later) Statistics on filtering show access-filter Access list logging statistics show access-log Internal trace for the access list access-log trace logging program Log information for the access list...
Page 298 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Route-related information in the show netstat routing-table kernel (unicast) numeric Route-related information in the show netstat multicast kernel (multicast) numeric IPv4 multicast statistics (for show ip multicast Version 10.5 and later) statistics IPv6 multicast statistics (for show ipv6 multicast...
Page 299 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description IPv6 PIM BSR information show ipv6 pim bsr IPv6 PIM rendezvous point show ipv6 pim rp-mapping information IPv6 multicast route information show ipv6 mroute IPv6 multicast forwarding entries show ipv6 mcache VRRP virtual router status and show vrrpstatus detail...
Page 300: Dynamic Arp Inspection Statistics Y (For Version 11.4 And Later)
A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description DHCP snooping statistics (for show ip dhcp snooping Version 11.4 and later) statistics Dynamic ARP inspection statistics show ip arp inspection (for Version 11.4 and later) statistics DHCP snooping log information show ip dhcp snooping (for Version 11.4 and later) logging info...
Page 301 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Number of routes advertised to show ip bgp BGP4 peers advertised-routes summary Number of For Version show ip vrf all routes learned 11.0 and later for each VRF and prior to Version 11.2 For Version...
Page 302: Display Of Registrations And N Changes In The Internal Web Authentication Db
A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description BGP4+ peering information show ipv6 bgp neighbor detail Packets that caused the show ipv6 bgp notification-factor disconnection of BGP4+ connections Number of routes received from show ipv6 bgp received-routes summary BGP4+ peers Number of routes advertised to...
Page 303 (for Version 11.4 and later) Average bandwidth used by show engine-traffic packet-transfer buses (per minute) statistics detail minutes (for Version 11.4 and later) For AX6700S series switches, the pktbusdisp display of the combination of packet-transfer buses and port numbers (for Version 10.7 and later)
Page 304: Ax3800S And Ax3600S Series Switches
A Detailed Display Contents of the "show tech-support" Command A.1.2 AX3800S and AX3600S series switches The following table lists the commands, the information that they display, and parameter information for AX3800S and AX3600S series switches. Table A-2 Command details (AX3800S and AX3600S series switches) Command (displayed) Description Software version and hardware...
Page 305 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Dump file information ls -lTiR /dump0 Hardware dump file information (for ls -lTiR Version 10.5 and later) /usr/var/hardware file information ls -lTiR /usr/var/core core file information ls -lTiR /config config Memory file system information (for ls -lTiR /var...
Page 306 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Internal trace information of the kernel cat /var/log/fixsb.log (for Version 10.5 and later) Log information created when software is updated (for Version 11.1 /usr/var/pplog/ppupdate .log and later) Log information created when software is updated (for Version 11.1 /usr/var/pplog/ppupdate and later)
Page 307 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Detailed statistics for ports show interfaces nif XXX_NIF line XXX_LINE debug PoE information show power inline Configuration for operation show running-config Link aggregation details show channel-group detail Spanning tree details show spanning-tree detail Details for all GSRPs...
Page 308 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Log information for L2 loop detection show loop-detection (for Version 10.7 and later) logging Link aggregation statistics show channel-group statistics LACP statistics for link aggregation show channel-group statistics lacp Spanning tree statistics show spanning-tree statistics...
Page 309: Show Mld-Snooping
A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description IGMP snooping group information show igmp-snooping group IGMP snooping statistics show igmp-snooping statistics MLD snooping information show mld-snooping MLD snooping group information show mld-snooping group MLD snooping statistics show mld-snooping statistics Route-related information in the kernel...
Page 310 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Number of entries used for IPv6 show ipv6 multicast multicast routing (for AX3800S series resources switches Version 11.6 and later or for AX3650S series switches Version 11.5 and later) Information on interfaces with MLD show ipv6 mld interface enabled...
Page 311: Show Ip Dhcp Snooping Statistics
A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Information on conflicted IP addresses show ip dhcp conflict detected by a DHCP server IPv6 DHCP server statistics show ipv6 dhcp server statistics IPv6 DHCP relay statistics (for Version show ipv6 dhcp traffic 11.4 and later) DHCP snooping statistics (for Version...
Page 312 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description BGP4 peering information show ip bgp neighbor detail Messages that caused the show ip bgp disconnection of BGP4 connections notification-factor Number of routes received from BGP4 show ip bgp peers received-routes summary Number of routes advertised to BGP4...
Page 313: Show Web-Authentication User Edit
A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Number of LS-Databases for OSPFv3 show ipv6 ospf database database-summary BGP4+ peering information show ipv6 bgp neighbor detail Packets that caused the show ipv6 bgp disconnection of BGP4+ connections notification-factor Number of routes received from show ipv6 bgp...
Page 314: Show Mac-Authentication
A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Display of MAC-based authentication show mac-authentication settings (for Version 10.6 and later) Display of MAC-based authentication show mac-authentication statistics (for Version 10.6 and later) statistics Display of registrations and changes show mac-authentication in the internal MAC-based mac-address edit...
Page 315: Ax2400S Series Switches
A Detailed Display Contents of the "show tech-support" Command A.1.3 AX2400S series switches The following table lists the commands, the information that they display, and parameter information for AX2400S series switches. Table A-3 Command details (AX2400S series switches) Command (displayed) Description Software version and hardware show version...
Page 316 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Dump file information ls -lTiR /dump0 Hardware dump file information (for ls -lTiR /usr/var/hardware Version 10.5 and later) file information ls -lTiR /usr/var/core core file information ls -lTiR /config config Memory file system information (for ls -lTiR /var...
Page 317: And Later)
A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Internal trace information of the cat /var/log/fixsb.log kernel (for Version 10.5 and later) Log information created when software is updated (for Version /usr/var/pplog/ppupdate.l 11.1 and later) Log information created when software is updated (for Version /usr/var/pplog/ppupdate2.
Page 318 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Detailed statistics for ports show interfaces nif XXX_NIF line XXX_LINE debug Configuration for operation show running-config Link aggregation details show channel-group detail Spanning tree details show spanning-tree detail Details for all GSRPs show gsrp all Ring Protocol details...
Page 319 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description LACP statistics for link aggregation show channel-group statistics lacp Spanning tree statistics show spanning-tree statistics VLAN details show vlan detail MAC VLAN information show vlan mac-vlan Statistics on all For versions show qos queueing queues...
Page 320: Display Of Registrations And N
A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description MLD snooping information show mld-snooping MLD snooping group information show mld-snooping group MLD snooping statistics show mld-snooping statistics DHCP snooping statistics (for show ip dhcp snooping statistics Version 11.4 and later) Dynamic ARP inspection statistics show ip arp inspection statistics...
Page 321 A Detailed Display Contents of the "show tech-support" Command Command (displayed) Description Display of MAC-based show mac-authentication authentication settings (for Version 10.6 and later) Display of MAC-based show mac-authentication authentication statistics (for statistics Version 10.6 and later) Display of registrations and show mac-authentication changes in the internal MAC-based mac-address edit...
Page 322 A Detailed Display Contents of the "show tech-support" Command...
Page 323: Index
Index series switches troubleshooting, 21 faults for AX6700S, AX6600S, and AX6300S access list logging series switches problems, 170 troubleshooting, 18 analyzing failures filtering overview, 2 communication failures, 168 analyzing failures of all or part of the Switch ftp command overview, 3...
Page 324 AX3800S, AX3600S, and redundant configurations of BSUs, 162 AX2400S series switches, 21 redundant configurations of NIFs, 164 faults for AX6700S, AX6600S, and AX6300S series switches, 18 functional failures during operation, 25 sFlow statistics (flow statistics) functionality, QoS configurations...

This manual is also suitable for:

Ax6300s Ax2400s Ax6600s Ax3800s Ax3600s

Alaxala AX6700S Troubleshooting Manual

Table of Contents

History of Amendments

Preface

Contents

Safety Information [AX6700S]

Safety Information [AX6600S]

Safety Information [AX6300S]

Safety Information [AX3800S] [AX3600S] [AX2400S]

1 Overview

2 Troubleshooting Switch Failures

3 Troubleshooting Functional Failures During Operation

4 Troubleshooting Communication Failures Due to a Resource Shortage

5 Obtaining Failure Information

6 Line Testing

7 Device Restart

Appendix

Detailed Display Contents of the "Show Tech-Support" Command

Display of Registrations and N/Authentication Db

Quick Links

Troubleshooting Guide

Chapters

Troubleshooting

Related Manuals for Alaxala AX6700S

Summary of Contents for Alaxala AX6700S

This manual is also suitable for:

Table of Contents