Page 1: Troubleshooting Guide
AX6700S/AX6600S/AX6300S/AX3800S/AX3600S/AX2400S Troubleshooting Guide AX36S-T001X-E0...
Page 2: Export Restrictions
Export restrictions In the event that any or all ALAXALA products (including technologies, programs and services) described or contained herein are controlled under any of applicable export control laws and regulations (including the Foreign Exchange and Foreign Trade Law of Japan and United States export control laws and regulations), such products shall not be exported without obtaining the required export licenses from the authorities concerned in accordance with the above laws.
Page 3 History of Amendments [Edition 14] Summary of amendments Item Changes Failure analysis for the AX3800S, AX3600S, and • A description of AX3830S-44X4QW was added. AX2400S series Loop connector specifications • A description of 40GBASE-SR4 loop connector specifications was added. [Edition 13] Summary of amendments Item Changes...
Page 4 Item Changes Communication is not possible or is disconnected • The description was changed in accordance with the addition of VRF support in AX3600S and AX2400 series switches. Creating loop connectors • This subsection was added. Detailed display contents of the "show tech-support" •...
Page 5 [Edition 8] Summary of amendments Item Changes Addition of series • A description relating to the addition of AX6600S series switches was added. Procedure for handling switch faults • Items for handling failures were added. Memory card problems • This section was added. •...
Page 6 Item Changes Detailed display contents of the "show tech-support" • Content displayed by the added or changed commands was command added. [Edition 6] Summary of amendments Item Changes Information cannot be entered from the console or • The item "After line disconnection, reconnection is not does not appear correctly possible."...
Page 7 [Edition 3] Summary of amendments Item Changes Additional model • A description relating to the additional model was added. Web Authentication • This item was added. sFlow statistics • This item was added. IEEE 802.3ah/UDLD functionality • This item was added. [Edition 2] Summary of amendments Item...
Page 9: Intended Readers
This manual is intended for system administrators who configure and operate a network system that uses AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, and AX2400S series switches. Readers must have an understanding of the following: • The basics of network system management Manual URL You can view this manual on our website at: http://www.alaxala.com/en/...
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 AX3800S and AX3650S series switches...
Page 12 AX3640S and AX3630S series switches...
Page 13 AX2400S series switches...
Page 14 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 IPv6 Internet Protocol version 6 IPV6CP IP Version 6 Control Protocol Internetwork Packet Exchange International Organization for Standardization Internet Service Provider Internal Spanning Tree L2LD Layer 2 Loop Detection Local Area Network Link Control Protocol Light Emitting Diode Logical Link Control LLDP Link Layer Discovery Protocol LLPQ...
Page 16 Router Advertisement RADIUS Remote Authentication Dial In User Service Remote Defect Indication REJect Request For Comments Rate Guaranteed Queueing Routing Information Protocol RIPng Routing Information Protocol next generation RMON Remote Network Monitoring MIB Reverse Path Forwarding ReQuest RSTP Rapid Spanning Tree Protocol Source Address Secure Digital Synchronous Digital Hierarchy...
Page 17 current vendor, or a switch from another vendor. The context decides the meaning. Conventions: KB, MB, GB, and TB This manual uses the following conventions: 1 KB (kilobyte) is 1024 bytes, 1 MB (megabyte) is 1024 bytes, 1 GB (gigabyte) is 1024 bytes, 1 TB (terabyte) is 1024 bytes.
Page 19: Table Of Contents
Contents Preface Safety Information [AX6700S] Safety Information [AX6600S] xxvii Safety Information [AX6300S] xxxix Safety Information [AX3800S] [AX3600S] [AX2400S] 1. Overview 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 ..............10 2.
Page 20 3.5.6 Actions to be taken for PoE problems ............... 43 3.5.7 Communication failures when link aggregation is used ..........44 3.6 Layer 2 network communication failures ................46 3.6.1 Layer 2 communication by VLANs is not possible ........... 46 3.6.2 Failures occurring when the Spanning Tree functionality is used ......49 3.6.3 Failures occurring when the Ring Protocol functionality is used ......
Page 21 3.16.1 sFlow packets cannot be sent to the collector ............138 3.16.2 Flow samples cannot be sent to the collector ............140 3.16.3 Counter samples cannot be sent to the collector ............141 3.17 Communication failures in the neighboring device management functionality ....142 3.17.1 Neighboring device information cannot be obtained by the LLDP functionality ..142 3.17.2 Neighboring device information cannot be obtained by the OADP functionality .142 3.18 NTP communication failures .....................144...
Page 22 5.4 Collecting information and transferring files by using the "ftp" command on a remote terminal ............................190 5.5 Writing data to a memory card .................... 193 5.5.1 Writing data to a memory card by using an operation terminal ......193 6.
Page 23: 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 24: Ground The Switch
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 25 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. Using the switch without grounding could result in electric shock or failures due to electrical noise.
Page 26 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 27 When pressing the button of the basic control 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 basic control 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 28 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 29 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. The following label is attached to a DC power supply unit. Do not touch the inside of the Switch with your hands.
Page 30: Lithium Battery
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 31 • 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 32 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 33 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. Use care when handling an air duster.
Page 34 xxvi...
Page 35: 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. •...
Page 36 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 37 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. Using the Switch without grounding could result in electric shock or failures due to electrical noise.
Page 38 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 39 When pressing the button 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. • 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 40: The Switch
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 41 not allow hair or other objects near the ventilation slots. They might be sucked into the Switch, resulting in injury. When moving the Switch, do not hold the handle of an optional module. • When moving the Switch, do not hold the handle of a fan unit or power supply unit. The handle might come off, resulting in the device falling and possibly causing injury.
Page 42 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. Pulling the cable itself might cause the wires to break. Do not touch the Switch directly if you have a metal allergy. •...
Page 43 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. xxxv...
Page 44 • 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 45 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 46 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. Use care when handling an air duster.
Page 47: 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. •...
Page 48 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 49 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. Using the Switch without grounding could result in electric shock or failures due to electrical noise.
Page 50 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 51 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 52 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 53 not allow hair or other objects near the ventilation slots. They might be sucked into the Switch, resulting in injury. When moving the Switch, do not hold the handle of an optional module. • When moving the Switch, do not hold the handle of a fan unit or power supply unit. The handle might come off, resulting in the device falling and possibly causing injury.
Page 54 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. Pulling the cable itself might cause the wires to break. Do not touch the Switch directly if you have a metal allergy. •...
Page 55 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. xlvii...
Page 56 • 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 57 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 58 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. 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. •...
Page 59: Safety Information [Ax3800S] [Ax3600S] [Ax2400S] Li
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. •...
Page 60 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 61 Use the Switch only with the indicated power supply. • Do not use the Switch at any voltage other than the indicated voltage. Doing so could result in fire or electric shock. Ensure that the capacity for incoming current to the distribution board is greater than the operating current of the circuit breaker.
Page 62 due to the high output power of EPU-B. 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 63 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 64 • 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. • Do not place the power cable near a heat-generating apparatus. The heat could melt the cable coating, resulting in fire or electric shock.
Page 65 Do not touch the Switch directly if you have a metal allergy. • The Switch is coated with zinc, nickel, gold, and other elements. Do not touch the Switch directly if you have an allergic reaction to these metallic elements. Doing so might cause eczema or skin irritation.
Page 66 • Condensation might form on the surfaces and the inside of the Switch if it is moved from a cold location to a warm location. Using the Switch in this condition could result in fire or electric shock. After moving the Switch between two locations with a large temperature variation, let the Switch stand a few hours before using it.
Page 67 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. Placing a Switch near a TV or a radio could affect both devices.
Page 68 • 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 interfere with...
Page 69 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) •...
Page 70 air duster could cause the ferrule tip to become dirty. • Keep the nozzle or container of the air duster from coming into contact with the ferrule tip. Contact could result in a malfunction. Use care when handling an optical connector cleaner. •...
Page 71: Overview
Chapter 1. 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 72: 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 73: 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 74 #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 75: Failure Analysis For Ax3800S, Ax3600S, And Ax2400S Series Switches
1. Overview 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 76 1. Overview Table 1-2: LED indications, buttons, and connectors Name Type Status Description brightnes LED: Green Power supply status Green Regular Power is on. Blinking Regular Sleep state green Power is off or the power supply failed. LED: Green Status of the switch Green Regular Available for operation...
Page 77 1. Overview Name Type Status Description brightnes Connector Memory card slot Memory card slot LED: Green Memory card status Regular The memory card is being accessed. (Do not remove the memory card.) The memory card is idle. (Memory cards can be inserted or removed.) CONSOLE Connector...
Page 78 1. Overview Name Type Status Description brightnes 1-24 LED: Green Operating status of 10/ Green Regular Link established, 100 Mbit/ or orange 100/1000BASE-T , full duplex Ethernet ports Blinking Regular A link is established and green frames are being sent or received, 1000 Mbit/s Orange Regular...
Page 79 1. Overview Name Type Status Description brightnes LINK LED: Green Operating status of 10/ Green Regular A link has been established. or orange 100/1000BASE-T Ethernet ports Orange Regular Line failure detection Link failure or block when the green ST1 LED is on LED: Green Blinking Regular...
Page 80: 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 81 1. Overview Category Sub-category Reference Spanning tree failure 3.6.2 Failures occurring when the Spanning Tree functionality is used Ring Protocol failure 3.6.3 Failures occurring when the Ring Protocol functionality is used IGMP snooping not possible 3.6.4 Multicast forwarding by IGMP snooping is not possible MLD snooping not possible 3.6.5 Multicast forwarding by MLD snooping is...
Page 82 1. Overview Category Sub-category Reference No OSPFv3 information 3.11.2 OSPFv3 routing information cannot be found No BGP4+ information 3.11.3 No BGP4+ routing information exists No VRF information 3.11.4 No IPv6 routing information exists in the Communication failures in the Communication not possible in the 3.12.1 Communication is not possible on the IPv6 multicast routing PIM-SM network...
Page 83 1. Overview Category Sub-category Reference Neighboring device 3.17.1 Neighboring device information cannot information cannot be be obtained by the LLDP functionality obtained by the LLDP functionality Neighboring device 3.17.2 Neighboring device information cannot information cannot be be obtained by the OADP functionality obtained by the OADP functionality NTP communication failures...
Page 85: Troubleshooting Switch Failures
Chapter 2. 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 86: 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. Immediately take the following actions: •...
Page 87 2. Troubleshooting Switch Failures Problem Action The STATUS LED of the BCU, CSU, or MSU 1. Check the single or redundant configuration of the BCU, is lit in red, the other LEDs are all off, and no CSU, or MSU modules. message is displayed on the system operation (1) When a single configuration is used, follow steps 3 panel.
Page 88: 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. 1. Turn the power switch off. 2. If you are using a DC power supply unit, turn off the circuit breaker at the distribution board.
Page 89: 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: •...
Page 90: Isolating The Cause Of External Redundant Power Unit Failures
2. Troubleshooting Switch Failures Problem Action • The red ST1 LED of the switch blinks. A problem has occurred on the switch or line. • The LINK LED (10GBASE-R or 1. For a redundant power model, check the status of the power 1000BASE-X port) and the 1-48 LED supply unit and fan unit.
Page 91: Replacing The Switch And Optional Modules
2. Troubleshooting Switch Failures Table 2-5: Isolating the cause of external redundant power unit failures Problem Action The POWER LED of the EPU is lit in green. Identify the power supply module that is not operating properly by checking the LEDs of the power supply modules mounted on the EPU.
Page 93: Troubleshooting Functional Failures During Operation
Chapter 3. 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 Stack configuration problems 3.5 Network interface communication failures...
Page 94: 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 mode to reset password...
Page 95: Memory Card Problems
3. Troubleshooting Functional Failures During Operation 3.2 Memory card problems 3.2.1 The "show system" or "show mc" command displays "MC : --------" If the command displays , check the problem and take show system show mc MC : -------- action according to the following table. Table 3-1: Action to take when "MC : --------"...
Page 96: 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. If a problem occurs during connection to the modem, check the problem and take action according to Table 3-4: Problems occurring during connection to the modem and action to take.
Page 97: Login From A Remote Terminal Is Not Possible
3. Troubleshooting Functional Failures During Operation Problem Items to check When the communication Despite changing the communication speed of the communication software after speed of the communication login, correct display is not possible. Restore the original communication speed software is changed after of the communication software.
Page 98: Returning To Administrator Mode From Configuration Command Mode Is Not Possible
3. Troubleshooting Functional Failures During Operation Table 3-5: Problems occurring during connection to a remote terminal and action to take Problem Action Remote connection is not Perform the following procedure: possible. 1. Use the command from a PC or workstation to make sure that a route ping for remote connection has been established.
Page 99: Login Authentication Using Radius/Tacacs+ Is Not Possible
3. Troubleshooting Functional Failures During Operation Use the command to forcibly log out the target user. killuser Specify the login number you checked in step 1, to the parameter. login no. Execution example (config)# $killuser 1 (2) When connected to a remote terminal Temporarily shut down the remote terminal, and then re-connect it.
Page 100: Command Authorization Using Radius/Tacacs+ And Local Is Not Possible
3. Troubleshooting Functional Failures During Operation Default restart Push and hold the RESET button for at least five seconds. Take care when performing a default restart. A startup due to the default restart does not perform authentication by password, authentication when changing to administrator mode ( command), or command authorization.
Page 101: Stack Configuration Problems
3. Troubleshooting Functional Failures During Operation 3.4 Stack configuration problems 3.4.1 Stack configuration is not possible If you cannot configure a stack successfully, check the following in order: the state of member switches, the optional license information, and the state of the stack port. Checking the log For details about the log, see the manual Message and Log Reference.
Page 102: Stack Configuration Cannot Be Edited
3. Troubleshooting Functional Failures During Operation 3.4.2 Stack configuration cannot be edited If you can make a stack configuration but cannot edit the configuration, check the software information. Execute on the master switch to check the software remote command all show version information of all member switches in the stack configuration.
Page 103: Network Interface Communication Failures
3. Troubleshooting Functional Failures During Operation 3.5 Network interface communication failures 3.5.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 104 3. Troubleshooting Functional Failures During Operation For details about the log, see the manual Message and Log Reference. Isolating the cause of the problem by checking the port status Use the command to check the port status, and isolate the cause of the show interfaces problem according to the following table.
Page 105: Bsu/Psp Communication Failures
3. Troubleshooting Functional Failures During Operation Port status Cause Action configuration Make sure the cable is connected to the target port, and set disable shutdown command is set. configuration command to activate the locked no shutdown target port. (3) Checking statistics You can use the command to check the number of sent and received show port statistics...
Page 106: Actions To Be Taken For 10Base-T/100Base-Tx/1000Base-T Problems
3. Troubleshooting Functional Failures During Operation Operating status Cause Action of the BSU/PSP Correctly set the distribution pattern of the maximum number of entries per switch by using the configuration fwdm prefer command. A failure has occurred on the target Based on the log entry for the target BSU/ BSU/PSP.
Page 107 3. Troubleshooting Functional Failures During Operation Table 3-10: Failure analysis method for 10BASE-T/100BASE-TX/1000BASE-T problems Items to check Cause Action Use the Line quality is Check whether the cable types are correct. For the types, see the show command degraded. Hardware Instruction Manual. interfaces to display the failure statistics, and check...
Page 108: Actions To Be Taken For 100Base-Fx/1000Base-X Problems
3. Troubleshooting Functional Failures During Operation Items to check Cause Action Perform a line test on the Switch and make sure that the functionality of the receiving side has no problem. Check the results of the command, and take the no test interfaces action described in Action.
Page 109 3. Troubleshooting Functional Failures During Operation Checking the log For details about the log, see the manual Message and 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 110 3. Troubleshooting Functional Failures During Operation Items to check Cause Action Check the cable length. For the cable length, see the Hardware Instruction Manual. Check whether the cables are connected correctly (for example, check for incomplete insertion). Make sure that the end sections of the cables are clean.
Page 111: Actions To Be Taken For 10Gbase-R/40Gbase-R Problems
3. Troubleshooting Functional Failures During Operation Items to check Cause Action Use the Packets Adjust the jumbo frame settings to those on the remote device. show command to exceeding the interfaces display the failure maximum statistics, and check allowed frame whether there is a count for length are the following item for the...
Page 112 3. Troubleshooting Functional Failures During Operation Items to check Cause Action Check whether the cables are connected correctly (for example, check for incomplete insertion). Make sure that the end sections of the cables are clean. If they are dirty, clean them.
Page 113: Actions To Be Taken For Poe Problems
3. Troubleshooting Functional Failures During Operation Items to check Cause Action For AX6700S, AX6600S, or Line quality on Check the type of the optical fiber. For the types, see the AX6300S series switches, the sending side Hardware Instruction Manual. use the is degraded.
Page 114: Communication Failures When Link Aggregation Is Used
3. Troubleshooting Functional Failures During Operation Table 3-13: Communication failure analysis method when PoE is used Items to check and commands Action Use the • When is displayed for show power inline PoEStatus command to check the information Power is not being supplied. Go to No. 2. displayed for for the target PoEStatus...
Page 115 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • Port Down The status of the port is link down. For details, see 3.5 Network interface communication failures. • Port Speed Unmatch The line speed of the port is different from that of the other ports in the channel group, and degradation has occurred.
Page 116: Layer 2 Network Communication Failures
3. Troubleshooting Functional Failures During Operation 3.6 Layer 2 network communication failures 3.6.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 117 3. Troubleshooting Functional Failures During Operation Execute the command and make sure the MAC address set for a VLAN show vlan mac-vlan by using the Layer 2 authentication functionality has not been set for another VLAN in the configuration. In the example below, the MAC address indicated with an asterisk ( ) is disabled because the address has also been set in the configuration.
Page 118 3. Troubleshooting Functional Failures During Operation port for the transfer. When Snoop is displayed for Type: See 3.6.4 Multicast forwarding by IGMP snooping is not possible and 3.6.5 Multicast forwarding by MLD snooping is not possible. When Dot1x is displayed for Type: See 3.13.1 Communication failures occurring when IEEE 802.1X is used.
Page 119: Failures Occurring When The Spanning Tree Functionality Is Used
3. Troubleshooting Functional Failures During Operation in the configuration are correct, and that bandwidth monitoring, drop control, or the shaper is used appropriately in the system configuration. For details about the procedure, see 3.25.1 Checking the filters and QoS configuration information. 3.6.2 Failures occurring when the Spanning Tree functionality is used If Layer 2 communication fails or the operating status of the Spanning Tree Protocol does not conform to the network configuration when the Spanning Tree functionality is used, use the...
Page 120: Failures Occurring When The Ring Protocol Functionality Is Used
3. Troubleshooting Functional Failures During Operation Items to check and commands Action Execute the Make sure the root bridge identifier and sending bridge identifier for the show spanning-tree command with the parameter received BPDUs are the same as those defined in the network detail for the Spanning Tree Protocol that configuration.
Page 121 3. Troubleshooting Functional Failures During Operation Table 3-16: Failure analysis method for the Ring Protocol Items to check and Action commands Use the command to is displayed for , go to No. 3. show axrp enable Oper State check the operating status of the If a hyphen ( ) is displayed for , required items for using the...
Page 122: Multicast Forwarding By Igmp Snooping Is Not Possible
3. Troubleshooting Functional Failures During Operation Items to check and Action commands Use the If there is no anomaly in the states of the VLAN and its ports, go to No. 9. show vlan detail command to check the state of the Also, go to No.
Page 123 3. Troubleshooting Functional Failures During Operation Figure 3-4: Analysis flowchart Table 3-17: Failure analysis method for multicast forwarding Items to check and commands Action Use the command Check the following: show logging and check whether a failure has • Check whether log information about a physical fault has been recorded. occurred.
Page 124 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure the settings for using Check the following: IPv4 multicast are correct. • For AX3800S or AX3600S series switches, check whether the setting of configuration command is applied. swrt_multicast_table If the configuration command is correctly...
Page 125: Multicast Forwarding By Mld Snooping Is Not Possible
3. Troubleshooting Functional Failures During Operation Items to check and commands Action Use the Check the following: show igmp-snooping command to check the IGMP • To check whether the IGMP querier that monitors the group members snooping configuration. exists, make sure one of the following messages is displayed. (1) If the IGMP querier exists, the IP address of the IGMP querier is displayed: IGMP querying system: 192.168.11.20*...
Page 126 3. Troubleshooting Functional Failures During Operation Figure 3-5: Analysis flowchart Table 3-18: Failure analysis method for multicast forwarding Items to check and commands Action Use the command Check the following: show logging and check whether a failure has • Check whether log information about a physical fault has been recorded. occurred.
Page 127 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure the settings for using Check the following: IPv6 multicast are correct. • For AX3800S or AX3600S series switches, check whether the setting of configuration command is applied. swrt_multicast_table If the configuration command is correctly...
Page 128 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Use the Check the following: show mld-snooping command to check the MLD • To check whether the MLD querier that monitors the group members snooping configuration. exists, make sure one of the following messages is displayed. (1) If the MLD querier exists, the IP address of the MLD querier is displayed: MLD querying system: fe80::200:87ff:fe10:1959*...
Page 129: Ipv4 Network Communication Failures
3. Troubleshooting Functional Failures During Operation 3.7 IPv4 network communication failures 3.7.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 130 3. Troubleshooting Functional Failures During Operation Figure 3-6: Failure analysis procedure when IPv4 communication is not possible (1) Checking the log One probable cause of disabled communication is a line failure (or damage). To display the messages that indicate a hardware failure, carry out the procedure below. You can find these messages in the log displayed by the Switch.
Page 131 3. Troubleshooting Functional Failures During Operation If a log entry was not displayed for the date and time when communication was disabled, see (2) Checking the interface status. (2) Checking the interface status Even when the Switch hardware is operating normally, a fault could have occurred on the hardware of a neighboring device connected to the Switch.
Page 132 3. Troubleshooting Functional Failures During Operation device is impossible, the address might not have been resolved by ARP. To check the status of address resolution between the Switch and the neighboring device, do the following: Log in to the Switch. Use the command to check the status of address resolution (whether ARP entry show ip arp...
Page 133: Ip Addresses Cannot Be Assigned By The Dhcp Functionality
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 134 3. Troubleshooting Functional Failures During Operation Figure 3-7: Failure analysis procedure on DHCP and BOOTP relays (a) Checking the log 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. Check the log displayed by the Switch or use command to check whether the interface status is .
Page 135 3. Troubleshooting Functional Failures During Operation Log in to the Switch. Use the command to check the communication with the two remote devices that are ping unable to communicate. For details about examples of using the command and how to ping interpret the execution result, see the Configuration Guide.
Page 136 3. Troubleshooting Functional Failures During Operation If the routing information obtained by the Switch does not contain the routing information about the interface that caused the communication failure or contains an incorrect address of the interface's next hop, see 3.8 IPv4 unicast routing communication failures. If the routing information obtained by the Switch contains routing information about the interface that caused the communication failure, the interface might have a problem with the functionality shown below.
Page 137 3. Troubleshooting Functional Failures During Operation The network configuration is changed. The DHCP server fails. First, check for cause 1. Described below are likely examples of incorrect configuration. For cause 2, check the differences in the network configuration before and after the change to uncover any cause that could disable communication.
Page 138 3. Troubleshooting Functional Failures During Operation Check the settings of the device used as the DHCP relay agent. If the Switch is used as the relay agent, see (1) Communication problems on DHCP and BOOTP relays. 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.
Page 139: Dynamic Dns Link Does Not Work In The Dhcp Functionality
3. Troubleshooting Functional Failures During Operation 3.7.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 140 3. Troubleshooting Functional Failures During Operation Make sure that the key information and the authentication key specified on the DNS server are consistent with the key information included in the DHCP server configuration (see the manual Configuration Command Reference). Make sure that the zone information specified on the DNS server is consistent with the zone information included in the DHCP server configuration (see the manual Configuration Command Reference).
Page 141 3. Troubleshooting Functional Failures During Operation (f) Checking the filters and QoS configuration information Only certain packets might have been discarded by filtering, or packets might have been discarded by bandwidth monitoring, drop control, or the QoS control shaper. On the Switch and the relay device between the DNS server and the DHCP server, make sure that the setting conditions for filters 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 142: Ipv4 Unicast Routing Communication Failures
3. Troubleshooting Functional Failures During Operation 3.8 IPv4 unicast routing communication failures 3.8.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 143: No Bgp4 Routing Information Exists
3. Troubleshooting Functional Failures During Operation Items to check and commands Action If the status of every neighboring router is , go to No. 5. Full Check whether the OSPF setting in the If the configuration is correct, go to No. 5. configuration is correct.
Page 144: Ipv4 Routing Information Cannot Be Found In Vrf
3. Troubleshooting Functional Failures During Operation Items to check and commands Action If the configuration is not correct, modify the configuration. For details about the procedure for checking the filter configuration information, see 3.25.1 Checking the filters and QoS configuration information.
Page 145: Communication Failures In The Ipv4 Multicast Routing Functionality
3. Troubleshooting Functional Failures During Operation 3.9 Communication failures in the IPv4 multicast routing functionality This section describes actions to be taken when an IPv4 multicast communication failure occurs on the Switch. 3.9.1 Communication is not possible on the IPv4 PIM-SM networks If multicast forwarding is not possible in an IPv4 PIM-SM network configuration, isolate the cause of the problem according to the failure analysis method described below.
Page 146 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 147: Network Configuration
3. Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure that multicast forwarding entries exist. If multicast forwarding entries do not exist, make sure that multicast data has reached the upstream port. If show ip mcache multicast data has not reached the upstream port, check the settings of the multicast sender or upstream router.
Page 148 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Make sure the Switch is the rendezvous point for the If the Switch is not the rendezvous point, check the forwarding target group address. priorities of other rendezvous point candidates. A smaller value represents a higher priority.
Page 149: Multicast Data Is Forwarded Twice In The Ipv4 Pim-Sm Network
3. Troubleshooting Functional Failures During Operation Table 3-27: Items to check for first-hop-router Items to check and commands Action Make sure that the Switch is directly connected to the If the Switch is not connected directly, check the multicast sender. network configuration.
Page 150 3. Troubleshooting Functional Failures During Operation Notes: • : The router that is connected directly to the multicast sender first-hop-router • : The router that is connected directly to the multicast receivers last-hop-router (1) Items checked in common The following table shows the items checked in common for all the Switches in an IPv4 PIM-SSM network configuration.
Page 151 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check the configuration to make sure that the If the PIM-SSM group addresses do not contain the PIM-SSM group addresses contain the forwarding forwarding target group address, modify the target group address.
Page 152: Multicast Data Is Forwarded Twice In The Ipv4 Pim-Ssm Network
3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether any anomaly has been detected on any Make sure that no warning information is displayed for interface. Notice If warning information is displayed, check the show ip igmp interface following: •...
Page 153: Ipv4 Multicast Communication Problems In Vrf
3. Troubleshooting Functional Failures During Operation Table 3-32: 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 the interface belonging to the network with multiple following: routers.
Page 154: Problems That Occur During Ipv4 Multicast Communication In The Extranet
3. Troubleshooting Functional Failures During Operation 3.9.6 Problems that occur during IPv4 multicast communication in the extranet To resolve problems on IPv4 multicast communication in an extranet, first, try to use the check items described in 3.9.5 IPv4 multicast communication problems in VRF and make sure that multicast communication is possible in each VRF.
Page 155 3. Troubleshooting Functional Failures During Operation Figure 3-12: Example of an IPv4 PIM-DM network Notes: • : The router that is connected directly to the multicast sender first-hop-router • : The router that is connected directly to the multicast receivers last-hop-router (1) Items checked in common The following table shows the items checked in common for all the Switches in an IPv4 PIM-DM...
Page 156 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check the PIM neighboring information. If neighboring routers are not displayed, check the following: show ip pim neighbor • Use the command to show ip pim interface make sure that PIM is running on the interface connected with the neighboring routers.
Page 157: Multicast Data Is Forwarded Twice In The Ipv4 Pim-Dm Network
3. Troubleshooting Functional Failures During Operation IPv4 PIM-DM network configuration. Table 3-37: Items to check for first-hop-router Items to check and commands Action Make sure that the Switch is directly connected to the If the Switch is not connected directly, check the multicast sender.
Page 158: Ipv6 Network Communication Failures
3. Troubleshooting Functional Failures During Operation 3.10 IPv6 network communication failures 3.10.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 159 3. Troubleshooting Functional Failures During Operation For details about the contents of the log, see the manual Message and Log Reference. Log in to the Switch. Use the command to display the log. show logging Each entry in the log indicates the date and time that a failure occurred. Check whether a log entry was displayed for the date and time when communication was disabled.
Page 160 3. Troubleshooting Functional Failures During Operation If communication with the remote device cannot be verified by using the ping ipv6 functionality, use the command to check communication with each of the devices ping ipv6 up to the remote device, beginning with the device closest to the customer's terminal. If you are able to determine the range for the failure by using the functionality and ping ipv6...
Page 161: Ipv6 Dhcp Relay Communication Problems
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 example, after...
Page 162 3. Troubleshooting Functional Failures During Operation Figure 3-14: Failure analysis procedure on IPv6 DHCP relays (1) Checking the log and interface One probable cause of disabled assignment of prefixes or addresses to clients is that communication between the client and the server has been disabled. Check the log displayed by the Switch or use the command to check whether the interface status is show ipv6 interface...
Page 163 3. Troubleshooting Functional Failures During Operation Log in to the Switch. Use the command to check the status of address resolution (whether show ipv6 neighbors NDP entry information exists) between the Switch and the neighboring device. If the address with the neighboring device has been resolved (NDP entry information exists), see (4) Checking the unicast routing information.
Page 164: Troubleshooting Ipv6 Dhcp Server Problems
3. Troubleshooting Functional Failures During Operation prefix or address to the target client is set by the configuration ipv6 dhcp relay destination command. Check whether the value specified for the hop-limit ipv6 dhcp relay hop-limit configuration command is equal to or larger than an appropriate hop value for the client. 3.10.3 Troubleshooting IPv6 DHCP server problems (1) The configuration distribution fails There are five probable causes of a service operation failure that occurs when you use the prefix...
Page 165 3. Troubleshooting Functional Failures During Operation (b) Checking the status of the IPv6 DHCP server on the Switch Checking whether the IPv6 DHCP server service is running Use the command to check whether information can be show ipv6 dhcp server statistics obtained from the IPv6 DHCP server daemon.
Page 166 3. Troubleshooting Functional Failures During Operation (config)# (d) Duplicate assignment to a client Checking the binding information Use the command with the parameter to check whether show ipv6 dhcp binding detail multiple prefixes have been distributed to a single DUID. The following shows an example. [Execution result] >...
Page 167 3. Troubleshooting Functional Failures During Operation The configuration has been set but not distributed. An operation or event has occurred that affects functions related to the automatic routing information setting. To isolate the cause of the problem, first, execute the command to display the show ipv6 route -s routing information.
Page 168 3. Troubleshooting Functional Failures During Operation Destination Next Hop Interface Metric Protocol 3ffe:1234:5678::/48 tokyo Static <Active Gateway Dhcp> 3ffe:aaaa:1234::/48 osaka Static <Active Gateway Dhcp> > (b) Setting the routing information again Consider the case where the automatic route setting functionality is used for distributing prefixes from the IPv6 DHCP server on the Switch to assignment targets.
Page 169: Ipv6 Unicast Routing Communication Failures
3. Troubleshooting Functional Failures During Operation 3.11 IPv6 unicast routing communication failures 3.11.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 170: No Bgp4+ Routing Information Exists
3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check the status of every neighboring If the status of any neighboring router is other than , go to No. Full router from the information in Neighbor List If the status of every neighboring router is , go to No.
Page 171: No Ipv6 Routing Information Exists In The Vrf
3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether the route is filtered in the Check whether the neighboring router is advertising the BGP4+ configuration. route. If the configuration is not correct, modify the configuration. For details about the procedure for checking the filter configuration information, see 3.25.1 Checking the filters and QoS configuration information.
Page 172: Communication Failures In The Ipv6 Multicast Routing Functionality
3. Troubleshooting Functional Failures During Operation 3.12 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.12.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 173 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check whether MLD snooping is set for the interface If MLD snooping is set, check the following: on which PIM runs. • Check whether the multicast router port for MLD snooping is set for the port connected to the show mld-snooping neighboring router.
Page 174 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 175 3. Troubleshooting Functional Failures During Operation (4) Items to check for last-hop-router The following table shows the items to check when the Switch is used as in an last-hop-router IPv6 PIM-SM network configuration. Table 3-48: Items to check for last-hop-router Items to check and commands Action Make sure that MLD is running on the interface...
Page 176: 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 multicast routing information exists. If multicast routing information does not exist, make sure that the multicast data source address is the show ipv6 mroute network address of the interface directly connected to the multicast sender.
Page 177 3. Troubleshooting Functional Failures During Operation network configuration. Table 3-51: 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 does functionality ( ) exists in the not exist, modify the configuration.
Page 178 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 last-hop-router IPv6 PIM-SSM network configuration. Table 3-52: Items to check for last-hop-router Items to check and commands Action If the mode of the multicast receivers is MLDv1 or...
Page 179: 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 on any Make sure that no warning information is displayed for interface. Notice If warning information is displayed, check the show ipv6 mld interface following: •...
Page 180: Ipv6 Multicast Communication Problems In Vrf
3. Troubleshooting Functional Failures During Operation Table 3-54: 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 the interface belonging to the network with multiple following: routers.
Page 181 3. Troubleshooting Functional Failures During Operation multicast communication is possible in each VRF. After that, check the following. Table 3-56: Items to check for an extranet Items to check and commands Action Make sure that the unicast route from the destination If it is not the case, check the settings of the unicast VRF to the source address is the expected VRF or extranet.
Page 182: Layer 2 Authentication Communication Failures
3. Troubleshooting Functional Failures During Operation 3.13 Layer 2 authentication communication failures 3.13.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-57: Authentication failure analysis method for IEEE 802.1X Items to check and commands Action...
Page 183 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • If Execute the is displayed, authentication failed show dot1x logging New Supplicant Auth Fail. command, and check whether for either of the following reasons. Check for problems. authentication failed.
Page 184 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • If Execute the show dot1x logging Failed to assign VLAN.(Reason: No Tunnel-Type command, and check whether dynamic is displayed, dynamic allocation has failed because the Attribute) allocation in VLAN-based attribute is not set for the attribute of the Tunnel-Type...
Page 185: Communication Failures Occurring When Web Authentication Is Used
3. Troubleshooting Functional Failures During Operation failures. Table 3-58: Communication failure analysis method for IEEE 802.1X Items to check and commands Action Make sure that VLANs with a VLAN-based Communication is possible only for VLANs with a authentication (static) setting and VLANs with VLAN-based authentication (static) setting.
Page 186 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • Execute the following command to check whether the Web Make sure that the Web server is running. server is running. If the Web server is running, go to No. 4. Command: # ps -auwx | grep httpd Check procedure:...
Page 187 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • If the value displayed for Use the under show web-authentication TxTotal [RADIUS command to check the , check whether the statistics frames] aaa authentication communication status with the RADIUS web-authentication default group radius server.
Page 188 (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 189 3. Troubleshooting Functional Failures During Operation Table 3-60: Checking the configuration of Web authentication Items to check Action Check the Web authentication configuration Make sure the following configuration commands have been settings. set correctly. Common configuration: • aaa accounting web-authentication default start-stop group radius •...
Page 190: Communication Failures Occurring When Mac-Based Authentication Is Used
3. Troubleshooting Functional Failures During Operation Items to check Action Check the configuration of the access filter for For fixed or dynamic VLAN mode, make sure the filter authentication. conditions required for communication from unauthenticated terminals to destinations outside the Switch have been set correctly by using the authentication ip access-group configuration commands.
Page 191 3. Troubleshooting Functional Failures During Operation Table 3-62: Failure analysis method for MAC-based authentication Items to check and commands Action Check whether communication with the • If authentication in local authentication method is not terminal is possible. possible, go to No. 2. •...
Page 192 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • If an unauthenticated terminal sends certain types of Check the setting of the authentication IPv4 access list. packets to destinations outside the Switch, make sure an authentication IPv4 access list is set. When both a standard access list and an authentication IPv4 access list are set, make sure the filter conditions in the authentication IPv4 access list are also set in the...
Page 193: Communication Failures Occurring When An Authentication Vlan Is Used
3. Troubleshooting Functional Failures During Operation Items to check Action Check the configuration of the access filter for Make sure the filter conditions required for communication authentication. from unauthenticated terminals to destinations outside the Switch have been set correctly by using the authentication ip access-group ip access-list extended...
Page 194 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • If VAA NAME is not set (i.e., Execute the command to is displayed), the show fense server fense check the operating status of the authentication command is not set in the configuration. Set the vaa-name VLAN.
Page 195 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • If the Execute the command, command shows that show vlan mac-vlan show vlan mac-vlan and make sure authenticated MAC addresses authenticated MAC addresses have been registered, have been registered for the MAC VLAN authentication of those MAC addresses cannot be enabled.
Page 196 3. Troubleshooting Functional Failures During Operation Items to check Action Check the filtering configuration. Make sure that the filters are correctly set between the following VLANs: • Between the VLAN used for authentication and the authenticated VLAN: A filter is set to disable all IP communication.
Page 197: Communication Failures In The High-Reliability Functionality
3. Troubleshooting Functional Failures During Operation 3.14 Communication failures in the high-reliability functionality 3.14.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-67: Communication failure analysis method for a GSRP configuration Items to check and commands Action...
Page 198 3. Troubleshooting Functional Failures During Operation Table 3-68: Failure analysis method when state switching fails in a GSRP configuration Items to check and commands Action Use the command to check If the state of one of them is and the state of the other is other show gsrp Master the status of the VLAN group in which...
Page 199: Communication Is Not Possible With The Vrrp Configuration Of Ipv4 Networks
3. Troubleshooting Functional Failures During Operation Items to check and commands Action See 3.25.1 Checking the filters and QoS configuration information, and check whether there is any cause of GSRP Advertise frames being discarded by filtering, or by bandwidth monitoring, drop control, or the QoS control shaper.
Page 200 3. Troubleshooting Functional Failures During Operation Items to check and commands Action If VLANs and VRIDs for the primary virtual router are the same among devices that make up the virtual routers, go to No. 6. Note that items No. 6 onward must be applied to the primary virtual router.
Page 201: Communication Is Not Possible With The Vrrp Configuration Of Ipv6 Networks
3. Troubleshooting Functional Failures During Operation Items to check and commands Action If ADVERTISEMENT packets are received correctly, check the remote device. If ADVERTISEMENT packets are not received, go to No. 8. Execute the For the physical port to which a remote device that makes up the same show interfaces command and check the statistics for virtual router is connected, you might find that the...
Page 202 3. Troubleshooting Functional Failures During Operation Table 3-71: Failure analysis method for VRRP Items to check and commands Action On the Switch and remote devices that For devices that make up a virtual router, if only one device is the master make up a virtual router, check the router and the others are the backup routers, check the following: status of the virtual router, and check...
Page 203 3. Troubleshooting Functional Failures During Operation Items to check and commands Action • You might find that the following is registered in the reference log: Execute the show vrrpstatus command with the <VRID> <Interface Name> statistics Virtual router received VRRP parameter, and check the reception packet for which the advertisement interval is status of ADVERTISEMENT packets.
Page 204: Communication Is Not Possible With Uplink Redundancy
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 same show interfaces command and check the statistics for virtual router is connected, you might find that the Input rate the physical port to which a remote values are large and the line load is high.
Page 205 3. Troubleshooting Functional Failures During Operation Table 3-72: Failure analysis method for uplink redundancy Items to check and commands Action Execute the If neither the primary port nor the secondary port is , check show Forwarding command, the following: switchport-backup and make sure that the states of the •...
Page 206: Snmp Communication Failures
3. Troubleshooting Functional Failures During Operation 3.15 SNMP communication failures 3.15.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 address of show access-list the SNMP manager has been set in the access list in the configuration.
Page 207 3. Troubleshooting Functional Failures During Operation When using SNMPv3 Execute the configuration command, and check whether the information show snmp-server 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 208: Troubleshooting The Sflow Statistics (Flow Statistics) Functionality
3. Troubleshooting Functional Failures During Operation 3.16 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.16.1 sFlow packets cannot be sent to the collector (1) Checking the route to the collector See 3.7.1 Communication is not possible or is disconnected and 3.10.1 Communication is not possible or is disconnected, and make sure that the network is correctly connected to the collector.
Page 209 3. Troubleshooting Functional Failures During Operation 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 packets are sent have been set correctly in the configuration.
Page 210: Flow Samples Cannot Be Sent To The Collector
3. Troubleshooting Functional Failures During Operation switchport mode access sflow forward ingress <-- sflow forward must be set. (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.25.1 Checking the filters and QoS configuration information.
Page 211: Counter Samples Cannot Be Sent To The Collector
3. Troubleshooting Functional Failures During Operation (1) Checking whether packets are forwarded Execute the command, and check whether packets are forwarded. show interfaces 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...
Page 212: Communication Failures In The Neighboring Device Management Functionality
3. Troubleshooting Functional Failures During Operation 3.17 Communication failures in the neighboring device management functionality 3.17.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 213 3. Troubleshooting Functional Failures During Operation Table 3-74: Failure analysis method when the OADP functionality is used Items to check and commands Action Execute the command and is displayed for , go to No. 2. show oadp Enabled Status check the operating status of the OADP functionality.
Page 214: Ntp Communication Failures
3. Troubleshooting Functional Failures During Operation 3.18 NTP communication failures 3.18.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-75: NTP failure analysis method Items to check and commands Action...
Page 215: Communication Failures In The Ieee 802.3Ah/Udld Functionality
3. Troubleshooting Functional Failures During Operation 3.19 Communication failures in the IEEE 802.3ah/UDLD functionality 3.19.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.
Page 216: Problems Due To The Redundant Configuration Of The Bcu, Csu, Or Msu
3. Troubleshooting Functional Failures During Operation 3.20 Problems due to the redundant configuration of the BCU, CSU, or MSU 3.20.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.
Page 217: Problems Due To The Redundant Configuration Of The Bsu
3. Troubleshooting Functional Failures During Operation 3.21 Problems due to the redundant configuration of the BSU 3.21.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 and Log Reference.
Page 218 3. Troubleshooting Functional Failures During Operation Operating Cause Action status of BSU units The target BSU is not implemented. Make sure that as many BSU boards as the notconnect number of active and standby BSUs (or the number of active BSUs only, if standby BSUs are not required) are implemented.
Page 219: Problems Due To The Redundant Configuration Of The Nif
3. Troubleshooting Functional Failures During Operation 3.22 Problems due to the redundant configuration of the NIF 3.22.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 220: Power Saving-Related Problems
3. Troubleshooting Functional Failures During Operation 3.23 Power saving-related problems 3.23.1 Scheduling is disabled If scheduling is disabled, perform the check procedure described below. Execute the command to check whether the displayed show power-control schedule schedule contains the current time, and isolate the cause of the problem according to the following table.
Page 221: Packet Congestion In Cpu Processing Does Not Recover
3. Troubleshooting Functional Failures During Operation 3.24 Packet congestion in CPU processing does not recover This section describes how to take actions if packet congestion in CPU processing is not cleared 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 222 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 tech-support command and command dump bsu twice in this order.
Page 223: Communication Failures In Filters And Qos Configurations
3. Troubleshooting Functional Failures During Operation 3.25 Communication failures in filters and QoS configurations 3.25.1 Checking the filters and QoS configuration information If a communication problem occurs on a network employing the Switch, it is possible that certain packets might have been discarded either by filtering or by bandwidth monitoring, drop control, or the QoS control shaper.
Page 224 3. Troubleshooting Functional Failures During Operation statistics item displayed for the port input and output queues of the input discard_pkt and output interfaces used for communication. Execute the command with the parameter, and check show qos queueing distribution statistics item displayed for the distribution input and output queues for discard_pkt the input or output interface used for communication.
Page 225: 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 226: Dhcp Snooping Problems
3. Troubleshooting Functional Failures During Operation 3.27 DHCP snooping problems 3.27.1 Problems related to DHCP If DHCP cannot distribute 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-84: Failure analysis method when DHCP cannot distribute IP addresses in a DHCP snooping configuration Items to check...
Page 227: Problems Related To Saving The Binding Database
3. Troubleshooting Functional Failures During Operation Items to check Action Make sure the DHCP server is connected to a DHCP server response packets from an untrusted port are trusted port. discarded. If the target DHCP server is an authorized one, set the configuration command for the dhcp snooping trust port to which the DHCP server is connected.
Page 228: Problems Related To Arp
3. Troubleshooting Functional Failures During Operation Items to check Action Make sure that the lease time of the IP addresses If the lease time is shorter, the lease of the IP addresses distributed to the DHCP clients is longer than the might expire before the binding database is completely read wait time for saving the database.
Page 229 3. Troubleshooting Functional Failures During Operation Items to check Action If there is no problem, go to No. 2. Check whether the is set, packets from devices not in the ip verify source ip verify source configuration command is set for the target port. binding information are discarded.
Page 230: Policy-Based Routing Problems
3. Troubleshooting Functional Failures During Operation 3.28 Policy-based routing problems 3.28.1 Actions to take when packets are not forwarded in policy-based routing If packets are not forwarded to the specified route when a policy-based routing group is used, resolve the problem as shown in the following table. Table 3-88: Action to take when packets are not forwarded in policy-based routing for AX6700S, AX6600S, or AX6300S Items to check and commands...
Page 231 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check the path switch-back operation setting of If the setting is , path switch-back operations are not policy-based routing performed, and thus the path is not being re-selected. Execute the command to re-select •...
Page 232: Actions To Be Taken When The Tracking Functionality Of Policy-Based Routing Is In An Unexpected Track State
3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check the operating status of path switching in is displayed for only, the packets might have End Time policy-based routing been discarded because the group is in the process of starting.
Page 233 3. Troubleshooting Functional Failures During Operation target. Due to network congestion, communication with the polling monitoring track target is unstable. To investigate the cause of the current unexpected track state, you must follow the methods of analysis shown in the following table to determine the cause. Table 3-90: Action to take when the track state is unexpected for AX6700S, AX6600S, or AX6300S Items to check and commands...
Page 234 3. Troubleshooting Functional Failures During Operation Items to check and commands Action If the track operating status is , the track is stopped Init because it is immediately after startup. Wait until the startup waiting time elapses. If the track operates, yet the track type is ICMP, go to No. 2. Check whether IPv4 communication can be made If the ping destination address and responding address are with track target...
Page 235: Policy-Based Switching Problems
3. Troubleshooting Functional Failures During Operation 3.29 Policy-based switching problems 3.29.1 Actions to be taken when packets are not forwarded in policy-based switching When you are using a policy-based switching group, if packets are not forwarded to the specified route, resolve the problem as shown in the following table. Table 3-92: Action to take when packets are not forwarded in policy-based switching Items to check and commands Action...
Page 236 3. Troubleshooting Functional Failures During Operation Items to check and commands Action Check the path switch-back operation settings for If the setting is , path switch-back operations are not policy-based switching performed, and thus the path is not being re-selected. Execute the command to •...
Page 237: Troubleshooting Communication Failures Due To A Resource Shortage
Chapter 4. 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 4.3 When a resource shortage occurs in shared memory...
Page 238: 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 capacity limit. The table below lists the operation log message to be output. Table 4-1: Operation log message that indicates resource usage Trigger Operation log message...
Page 239 4. Troubleshooting Communication Failures Due to a Resource Shortage Trigger Log message Web authentication (fixed VLAN mode) The login failed because of hardware restriction. Note: This log message is displayed when the show command is executed. web-authentication logging MAC-based authentication The login failed because of hardware restriction.
Page 240 4. Troubleshooting Communication Failures Due to a Resource Shortage Entry to be deleted Procedure IGMP/MLD snooping Execute the clear igmp-snooping all clear commands. mld-snooping all Web Authentication Execute the clear web-authentication auth-state command to cancel authentication. MAC-based authentication Execute the clear mac-authentication auth-state command to cancel authentication.
Page 241: 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 capacity limit.
Page 242 4. Troubleshooting Communication Failures Due to a Resource Shortage Trigger Loge message • Authentication VLAN The registration of the MAC address failed. Note: This log message is displayed when the show fense logging command is executed. Web authentication (dynamic VLAN mode) •...
Page 243: 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 245: Obtaining Failure Information
Chapter 5. 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 246: Collecting Maintenance Information
5. Obtaining Failure Information 5.1 Collecting maintenance information When a fault occurs with the switch during operation, log and dump information is automatically collected. 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.
Page 247 5. Obtaining Failure Information Item Path and file name Remarks Dump information *** in the system that failed /usr/var/hardware/nif file created when the (For versions prior to Version 10.5: *** in the /dump0/nif NIF fails active system) **: NIF number of the NIF that failed ***: Serial number assigned since the first dump data was collected.
Page 248: Collecting Failure Information By Using The "Dump" Command
) in the system in which the commands were executed. You need to delete /dump0 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 installed.
Page 249 ) in the system in which the commands hardware /dump0 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 installed. dump bsu In the active BCU, execute the command for all the ports that have failed.
Page 250 5. Obtaining Failure Information of NIF number 1 when the BSUs are installed on the BSU numbers 1 and 2 in a redundant BCU environment. Log in to the active BCU, and then execute the command. dump > dump bsu 1 Dump command accept.
Page 251 5. Obtaining Failure Information 11/01 18:18:42 E3 CSU 25070700 2301:000000000000 PSP online dump command executed. After the above log information is displayed, log in to the standby system, and then execute the following command. dump SBY:> dump psp Dump command accept. SBY:>...
Page 252 5. Obtaining Failure Information In the active BCU, execute the command for all the ports that have failed. dump nif Example: The following procedure shows an example in which communication fails on port number 1 of NIF number 1 when the BSUs are installed on the BSU numbers 1 and 2. Log in to the active BCU, and then execute the command.
Page 253: 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 254 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 255: Transferring Files Using The "Zmodem" Command
5. Obtaining Failure Information 200 EPRT command successful. 150 Opening BINARY mode data connection for 'nimd.core'. 100% |**********************************************************************| 272 KB 1.12 MB/s 00:00 ETA 226 Transfer complete. 278528 bytes sent in 00:00 (884.85 KB/s) local: nodeInit.core remote: nodeInit.core 200 EPRT command successful. 150 Opening BINARY mode data connection for 'nodeInit.core'.
Page 256 5. Obtaining Failure Information > cd /usr/var/core/ > ls <---1 interfaceControl.core nodeInit.core > zmodem put interfaceControl.core <---2 > zmodem put nodeInit.core > Make sure that the error save information file exists. If the file does not exist, exit the procedure without doing anything. Transfer the log file.
Page 257: Collecting Information And Transferring Files By Using The "Show Tech-Support" Command
5. Obtaining Failure Information 5.3 Collecting information and transferring files by using the "show tech-support" command You can use the command to collect information when a failure has occurred show tech-support in a batch operation. You can also specify the parameter for this command to transfer the collected information to a remote terminal or remote host.
Page 258 5. Obtaining Failure Information ..............................................Operation normal end. > Execute the command. Specify the remote host name. Specify a user name. Enter the password. Specify the destination directory. Specify a file name. Choose to collect dump files from the standby system. (2) Collecting information and transferring files by using the "show tech-support"...
Page 259 5. Obtaining Failure Information Specify the destination directory. Specify a file name. (3) Use the "remote command" command to use the "show tech-support" command to collect information (at the time of stack configuration)remote command Figure 5-9: Collection of member switch (switch number 2) maintenance information by the master switch (at the time of stack configuration) >...
Page 260: 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. In a stack configuration, you can connect to the master switch by using the command.
Page 261 5. Obtaining Failure Information Figure 5-11: Obtaining the "show tech-support" unicast information 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. Using binary mode to transfer files.
Page 262 5. Obtaining Failure Information 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. ftp> binary <---2 200 Type set to I. ftp>...
Page 263: 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 265: Line Testing
Chapter 6. Line Testing 6.1 Testing a line...
Page 266: Testing A Line
6. Line Testing 6.1 Testing a line In line tests, what loops back test frames varies depending on the test type. The following figure shows what loops back the test frames for various line test types. Note that line testing for stack configuration is not supported. Figure 6-1: What loops back the test frames for various line test types Table 6-1: Test types and fault locations to be identified Test type...
Page 267: Loop Connector Loopback Test
6. Line Testing Date 2006/03/10 00:20:21 UTC Interface type :100BASE-TX Test count Send-OK Send-NG Receive-OK Receive-NG Data compare error Out underrun Out buffer hunt error Out line error In CRC error In frame alignment In monitor time out In line error H/W error :none >...
Page 268 6. Line Testing 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. Figure 6-5: 10BASE-T/100BASE-TX/1000BASE-T loop connector specification Note that the 1000BASE-T loop connector above is only supported for loop operation for the Switch.
Page 269: Device Restart
Chapter 7. Device Restart This chapter mainly describes how to restart the device. 7.1 Restarting the device...
Page 270: Restarting The Device
7. Device Restart 7.1 Restarting the device 7.1.1 Device restart You can use the command to restart the device. Log data is stored when the device restarts. reload For details on the syntax and parameters of the command, see the manual Operation Command Reference.
Page 271 7. Device Restart In step 2, you will be asked whether you want to capture the CPU memory dump. According to the figure above, you do not use any parameters. Step3 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 272 7. Device Restart Figure 7-4: Confirmation messages for CPU memory dump capturing 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.
Page 273 7. Device Restart In this step, choose whether you capture the dump. Figure 7-6: Selection of the CPU memory dump type In step 2, you will be asked whether you want to capture the CPU memory dump. According to the figure above, you do not use any parameters. Combining the parameters selected in steps 1 and 2 results in the command .
Page 274 7. Device Restart Figure 7-7: Confirmation messages for CPU memory dump capturing...
Page 275: Appendix
Appendix A. Detailed Display Contents of the "show tech-support" Command...
Page 276: A Detailed Display Contents Of The "Show Tech-Support" Command
A. Detailed Display Contents of the "show tech-support" Command A. Detailed Display Contents of the "show tech-support" Command A.1 Detailed display contents of the "show tech-support" command The following tables list descriptions of the content that is displayed when protocol parameters are used with the command.
Page 277 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie 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 Path distribution-related information /usr/local/diag/rtastat Layer 4-related statistics show netstat all-protocol-address numeric Layer 3-related statistics...
Page 278 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Console terminal information stty -a -f /dev/tty00 CLI trace information 1 cat /var/log/clitrace1 CLI trace information 2 cat /var/log/clitrace2 Operation command trace cat /var/log/mmitrace information (for Version 10.5 and later)
Page 279 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Configuration command trace cat /var/tmp/gen/trace/ information 3 (for Version 10.7 and mng_sub.trc later) Configuration command trace tail -n 400 /var/tmp/gen/ information 4 (for Version 10.7 and trace/api.trc later) Configuration command trace...
Page 280 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie 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...
Page 281 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Authentication status information on show dot1x detail IEEE 802.X authentication IGMP snooping information show igmp-snooping IGMP snooping group information show igmp-snooping group IGMP snooping statistics show igmp-snooping statistics...
Page 282 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Information on interfaces with IPv6 show ipv6 pim interface PIM enabled (detail) IPv6 PIM neighbor information show ipv6 pim neighbor (detail) IPv6 PIM BSR information show ipv6 pim bsr IPv6 PIM rendezvous point show ipv6 pim rp-mapping...
Page 283 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Dynamic ARP inspection statistics show ip arp inspection (for Version 11.4 and later) statistics DHCP snooping log information (for show ip dhcp snooping logging Version 11.4 and later) info DHCP snooping event information...
Page 284 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Operating status of restart routers that show graceful-restart perform graceful restarts in the unicast unicast routing protocol (for Version 10.3 and later) Interface information on the Switch show ipv6 interface recognized by the unicast routing...
Page 285 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Display of entries registered in the show web-authentication user internal Web authentication DB (for commit Version 10.3 and later) Display of Web authentication show web-authentication statistics (for Version 10.3 and later) statistics...
Page 286 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) NIF HDC information (for Version nifhdcinfo 10.7 and later)
Page 287 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie CPU utilization show cpu days hours minutes seconds Memory usage of the device show memory summary Kernel event information /sbin/dmesg Kernel event information (for Version cat /var/run/dmesg.boot 10.5 and later) Internal information of the kernel and...
Page 288 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Login session information show session Terminal information /usr/sbin/pstat -t Console terminal information stty -a -f /dev/tty00 CLI information file list (for versions ls -lTiR /var/tmp/mmi* earlier than Version 10.1.A) CLI trace information 1...
Page 289 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Kernel interface information show netstat interface VLAN information list show vlan list Port information show port Port statistics show port statistics Protocol information for ports show port protocol Transceiver details for ports show port transceiver debug...
Page 290 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Statistics on L2 loop detection (for show loop-detection Version 10.7 and later) statistics Log information for L2 loop show loop-detection logging detection (for Version 10.7 and later) Link aggregation statistics show channel-group statistics...
Page 291 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Authentication status information on show dot1x detail IEEE 802.X authentication IGMP snooping information show igmp-snooping IGMP snooping group information show igmp-snooping group IGMP snooping statistics show igmp-snooping statistics...
Page 292 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Information on interfaces with MLD show ipv6 mld interface enabled Information on groups managed by show ipv6 mld group Information on interfaces with IPv6 show ipv6 pim interface PIM enabled (detail)
Page 293 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie DHCP snooping log information (for show ip dhcp snooping logging Version 11.4 and later) info DHCP snooping event information dhsn debug (for Version 11.4 and later) Number of For versions show ip route summary...
Page 294 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Number of For versions show ipv6 route summary active and prior to Version inactive routes 10.6 maintained by For Version 10.6 the unicast and later routing program Number of routes advertised by...
Page 295 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Display of authenticated-user show web-authentication information (account information) login (for Version 10.3 and later) Display of operation logs for Web show web-authentication authentication (for Version 10.3 and logging later)
Page 296 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Detailed information of tracking show track-object detail functionality for policy-based routing (For AX3800S Version 11.9 and later. Also for AX3650S and AX3640S Version 11.7 and later.) Trace information of tracking /usr/local/bin/trackobj -t |...
Page 297 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Kernel event information /sbin/dmesg Kernel event information (for Version cat /var/run/dmesg.boot 10.5 and later) Internal information of the kernel and cat /var/log/messages daemons Kernel internal statistics /usr/local/diag/statShow...
Page 298 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie CLI information file list (for versions ls -lTiR /var/tmp/mmi* earlier than Version 10.1.A) CLI trace information 1 cat /var/log/clitrace1 CLI trace information 2 cat /var/log/clitrace2 Operation command trace cat /var/log/mmitrace...
Page 299 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Port statistics show port statistics Protocol information for ports show port protocol Transceiver details for ports show port transceiver debug Detailed statistics for ports show interfaces nif XXX_NIF line XXX_LINE debug Configuration for operation...
Page 300 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie 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 prior to Version...
Page 301 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie DHCP snooping log information (for show ip dhcp snooping logging Version 11.4 and later) info DHCP snooping event information dhsn debug (for Version 11.4 and later) Display of registrations and changes show web-authentication user in the internal Web authentication DB...
Page 302 A. Detailed Display Contents of the "show tech-support" Command Command (displayed) Description unic mult laye para icas cifie Display of operation logs for show mac-authentication MAC-based authentication (for logging Version 10.6 and later) Schedule information of power show power-control schedule saving functionality (for Version 11.4 and later) Display of SW subunit logs (for...
Page 303: Index
Index Symbols communication failures in the neighboring device management functionality 142 "MC not found." is displayed when the memory card is communication failures occurring when an authentication accessed 25 VLAN is used 123 communication failures occurring when IEEE 802.1X is used 112 actions to be taken for 100BASE-FX/1000BASE-X communication failures occurring when MAC-based...
Page 304 Index faults for AX6700S, AX6600S, and AX6300S series switches 16 neighboring device information cannot be obtained by the flow samples cannot be sent to the collector 140 LLDP functionality 142 forgotten login user password 24 neighboring device information cannot be obtained by the forgotten password for administrator mode 24 OADP functionality 142 nework interface communication failures 33...
Page 305 Index the Switch cannot be synchronized by using NTP 144 transferring files using the ftp command 183 transferring files using the zmodem command 185 transferring maintenance information files 183 traps cannot be received by the SNMP manager 136 troubleshooting IPv6 DHCP server problems 94 troubleshooting Switch failures 15 troubleshooting the sFlow statistics (flow statistics) functionality 138...

This manual is also suitable for:

Ax3600s series Ax6600s series Ax2400s series Ax6300s series Ax3800s series

Alaxala AX6700S series Troubleshooting Manual

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

Quick Links

Troubleshooting Guide

Troubleshooting

Related Manuals for Alaxala AX6700S series

Summary of Contents for Alaxala AX6700S series

This manual is also suitable for:

Table of Contents