AX6700S/AX6600S/AX6300S/AX3800S/AX3600S/AX2400S Troubleshooting Guide AX36S-T001X-E0
Relevant products This manual applies to the models in the AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, and AX2400S series of switches.
History of Amendments [Edition 14] Summary of amendments Item Changes Failure analysis for the AX3800S, AX3600S, and AX2400S series • A description of AX3830S-44X4QW was added. Loop connector specifications • A description of 40GBASE-SR4 loop connector specifications was added. [Edition 13] Summary of amendments Item Changes Returning to administrator mode from configuration command mode is not possible • This subsection was added. Stack configuration problems • This subsection was added.
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" command • Commands were added to the detailed description. [Edition 10] Summary of amendments Item Changes IPv4 network communication failures • Actions to be taken when using DHCP snooping were added.
[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. BSU/PSP communication failures • PSP was added. In addition, items for analyzing failures were added or modified. Actions to be taken for PoE problems • This subsection was added.
Item Detailed display contents of the "show tech-support" command Changes • Content displayed by the added or changed commands was added. [Edition 6] Summary of amendments Item Changes Information cannot be entered from the console or does not appear correctly • The item "After line disconnection, reconnection is not possible." for problems occurring during connection to a modem was added.
[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 Changes Additional model • A description relating to the additional model was added. Authentication VLAN • This item was added. SNMPv3 • This item was added.
Preface Relevant products This manual applies to the models in the AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, and AX2400S series of switches. Before you operate the equipment, carefully read the manual and make sure that you understand all instructions and cautionary notes. After reading the manual, keep it in a convenient place for easy reference. Corrections to the manual Corrections to this manual are contained in the Manual Corrections.
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.
AX3800S and AX3650S series switches iii
AX3640S and AX3630S series switches iv
AX2400S series switches v
Abbreviations used in the manual AC ACK ADSL ALG ANSI ARP AS AUX BCU BGP BGP4 BGP4+ bit/s BPDU BRI BSU CC CDP CFM CIDR CIR CIST CLNP CLNS CONS CRC CSMA/CD CSNP CST CSU DA DC DCE DHCP DIS DNS DR DSAP DSCP DTE DVMRP E-Mail EAP EAPOL EFM ES FAN FCS FDB FQDN FTTH GBIC GSRP HMAC IANA ICMP ICMPv6 ID IEC IEEE IETF IGMP IP IPCP IPv4 vi Alternating Current ACKnowledge Asymmetric Digital Subscriber Line Application Level Gateway American National Standards Institute Address Resolution Protocol Autonomous System Aux
IPv6 IPV6CP IPX ISO ISP IST L2LD LAN LCP LED LLC LLDP LLPQ LLQ+3WFQ LLRLQ LSP LSP LSR MA MAC MC MD5 MDI MDI-X MEP MIB MIP MRU MSTI MSTP MSU MTU NAK NAS NAT NCP NDP NET NIF NLA ID NPDU NSAP NSSA NTP OADP OAM OSPF OUI packet/s PAD PAE PC PCI PDU PICS PID PIM PIM-DM PIM-SM PIM-SSM PoE PRI PS PSNP PSP QoS QSFP+ Internet Protocol version 6 IP Version 6 Control Protocol Internetwork Packet Exchange International Organization for Standardization Internet Service Provider Internal Spanning Tree Layer 2 Loop Detect
RA RADIUS RDI REJ RFC RGQ RIP RIPng RMON RPF RQ RSTP SA SD SDH SDU SEL SFD SFP SFP+ SMTP SNAP SNMP SNP SNPA SOP SPF SSAP STP TA TACACS+ TCP/IP TLA ID TLV TOS TPID TTL UDLD UDP UPC UPC-RED uRPF VAA VLAN VPN VRF VRRP WAN WDM WFQ WGQ WRED WS WWW XFP Router Advertisement Remote Authentication Dial In User Service Remote Defect Indication REJect Request For Comments Rate Guaranteed Queueing Routing Information Protocol Routing Information Protocol next generation Remote Network Monitoring MIB Reverse Path Forwa
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 10242 bytes, 1 GB (gigabyte) is 10243 bytes, 1 TB (terabyte) is 10244 bytes.
Contents Preface i Safety Information [AX6700S] xv Safety Information [AX6600S] xxvii Safety Information [AX6300S] xxxix Safety Information [AX3800S] [AX3600S] [AX2400S] li 1. Overview 1 1.1 Overview of analyzing failures ................................................................................................2 1.2 Overview of analyzing failures of all or part of the Switch ....................................................3 1.2.
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.
3.17 3.18 3.19 3.20 3.21 3.22 3.23 3.24 3.25 3.26 3.27 3.28 3.29 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 Communication failures in the neighboring device management functionality ................142 3.17.
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. Line Testing 195 6.
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. • Operate the Switch according to the instructions and procedures provided in this guide. • Heed all warnings and cautions on the Switch in this guide.
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. Continuing operation could result in fire or electric shock. • If the Switch has an AC power supply unit, turn off the Switch, and then unplug the power cable.
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.
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. • Use the supplied or a designated power cable. Using another cable could result in fire or electric shock. In addition, do not use the supplied cable with other devices.
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. Doing so could result in fire or electric shock. Disconnect the power cable before adding or replacing a power supply unit.
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. 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.
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. • Do not carelessly put your hands inside the Switch. The frame and components might cause injury. Be careful of heat when removing a basic control unit or network interface unit.
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. • When you remove the SFP-T, use the following procedure. Failure to do so could result in burns. 1. To remove the device when the Switch is turned on, execute the inactivate command, and then wait five minutes before removing the device.
Do not turn off the power during a software update (while the ppupdate command is executing). • The Switch automatically restarts after the ppupdate command is executed. Do not turn off the power while the switch is restarting (wait until the STATUS LED of the basic control unit changes from blinking green to solid green). Turning off the power could result in a switch fault. Handle memory cards carefully. • When inserting a memory card, do not push the card too strongly or flick it with your finger.
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. • When removing optional modules, attach blank panels. If you use the Switch without attaching a blank panel, airflow through the Switch cannot be maintained.
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. • Use an air duster specially designed for cleaning optical connectors. Using another type of air duster could cause the ferrule tip to become dirty.
xxvi
Safety Information [AX6600S] Using AX6600S series switches correctly and safely • This guide provides important information for ensuring safe use of AX6600S series switches. Please read this guide completely before using the Switch. • Keep this guide handy after finishing it, so that it is available for later reference. • Operate the Switch according to the instructions and procedures provided in this guide. • Heed all warnings and cautions on the Switch in this guide.
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. Continuing operation could result in fire or electric shock. • If the Switch has an AC power supply unit, turn off the Switch, and then unplug the power cable.
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. Connecting and disconnecting a DC power cable must be performed by a trained technician or maintenance personnel.
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. • Use the supplied or a designated power cable. Using another cable could result in fire or electric shock. In addition, do not use the supplied cable with other devices.
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. Doing so could result in fire or electric shock. Disconnect the power cable before adding or replacing a power supply unit.
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. 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.
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. Moreover, the fan unit or power supply unit might become damaged, resulting in a fire or electric shock. When moving a Switch, unplug all cables.
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. • 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.
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.
Do not turn off the power during a software update (while the ppupdate command is executing). • The Switch automatically restarts after the ppupdate command is executed. Do not turn off the power while the Switch is restarting (wait until the STATUS LED of the control and switching unit changes from blinking green to solid green). Turning off the power could result in a switch fault. Handle memory cards carefully.
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. • When removing optional modules, attach blank panels. If you use the Switch without attaching a blank panel, airflow through the Switch cannot be maintained.
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. • Use an air duster specially designed for cleaning optical connectors. Using another type of air duster could cause the ferrule tip to become dirty.
Safety Information [AX6300S] Using AX6300S series switches correctly and safely • This guide provides important information for ensuring safe use of AX6300S series switches. Please read this guide completely before using the Switch. • Keep this guide handy after finishing it, so that it is available for later reference. • Operate the Switch according to the instructions and procedures provided in this guide. • Heed all warnings and cautions on the Switch in this guide.
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. Continuing operation could result in fire or electric shock. • If the Switch has an AC power supply unit, turn off the Switch, and then unplug the power cable.
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. Connecting and disconnecting a DC power cable must be performed by a trained technician or maintenance personnel.
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. • Use the supplied or a designated power cable. Using another cable could result in fire or electric shock. In addition, do not use the supplied cable with other devices.
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. Doing so could result in fire or electric shock.
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. 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.
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. Moreover, the fan unit or power supply unit might become damaged, resulting in a fire or electric shock. When moving a Switch, unplug all cables.
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. • 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.
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.
Do not turn off the power during a software update (while the ppupdate command is executing). • The Switch automatically restarts after the ppupdate command is executed. Do not turn off the power while the Switch is restarting (wait until the STATUS LED of the management and switching unit changes from blinking green to solid green). Turning off the power could result in a switch fault. Handle memory cards carefully.
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. • When removing optional modules, attach blank panels. If you use the Switch without attaching a blank panel, airflow through the Switch cannot be maintained.
both devices. If you hear noise on the TV or radio, do the following: 1. Place the Switch as far away as possible from the TV or radio. 2. Adjust the orientation of the TV or radio antenna. 3. Use separate outlets. Do not place a Switch where it will be exposed to hydrogen sulfide or salt. • Placing a Switch in an area where sulfides are present, such as a hot-springs area, or in an area with salty air, such as along a coast, could shorten the life of the Switch. Use care when handling an air duster.
Safety Information [AX3800S] [AX3600S] [AX2400S] Using AX3800S, AX3600S, and AX2400S series switches correctly and safely • This guide provides important information for ensuring safe use of AX3800S, AX3600S, and AX2400S series switches. Please read this guide completely before using the Switch. • Keep this guide handy after finishing it, so that it is available for later reference. • Operate the Switch according to the instructions and procedures provided in this guide.
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. Continuing operation could result in fire or electric shock.
Use the Switch only with the indicated power supply. • Do not use the Switch at any voltage other than the indicated voltage. 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. • Ensure that the capacity for incoming current to the distribution board is greater than the operating current of the circuit breaker.
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. • Use the supplied or a designated power cable. Using another cable could result in fire or electric shock.
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. • When mounting the Switch in a rack, make sure that the Switch is stable. If the Switch is unstable, it might fall, resulting in injury. Do not open the Switch cover.
• 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. • When connecting or disconnecting the AC power cable from the outlet, always hold the plug, not the cable itself.
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. Avoid looking directly at laser beams. • The Switch uses laser beams that are colorless and transparent, and invisible to the eye. Never look directly into the optical transceiver.
• 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. Do not touch the inside of the Switch with your hands. • Do not carelessly put your hands inside the Switch. The frame and components might cause injury.
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. If you hear noise on the TV or radio, do the following: 1. Place the Switch as far away as possible from the TV or radio. 2. Adjust the orientation of the TV or radio antenna. 3. Use separate outlets.
• Replacing a fan unit of a redundant power model AX3830S Turn off the power before installing or removing a power supply module. • Before installing or removing a power supply module, turn off its power. Installing or removing the module with the power supply module turned on causes a (switch) failure. The following label is attached to the EPU. Turn off the power of the power supply modules before turning on the main power switch of an EPU.
Make sure that you use a valid combination for the direct attach cable and the Switch. The following Switches support SFPP-CU1M/3M/5M. Use the transceivers only with the indicated Switches. Not doing so could result in a Switch malfunction. • AX3650S-24T6XW (Supported ports: 25 to 30) • AX3650S-20S6XW (Supported ports: 25 to 30) • AX3650S-48T4XW (Supported ports: 49 to 52) • AX3830S-44XW (Supported ports: 1 to 44) • AX3830S-44X4QW (Supported ports: 1 to 44) The following Switch supports QSFP-CU35C/1M/3M/5M.
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. • Always use a dedicated optical connector cleaner. If you use another type of cleaner, the ferrule tip might become dirty.
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.
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. When failure analysis requires logging in to the Switch, do the analysis according to 1.3 Overview of analyzing failures of functionality.
1. Overview 1.2 Overview of analyzing failures of all or part of the Switch 1.2.1 Failure analysis for AX6700S, AX6600S, and AX6300S series switches If a failure occurs during operation and the actual switch can be looked at, take appropriate action as described in 2.1 Troubleshooting faults for AX6700S, AX6600S, and AX6300S series switches to troubleshoot the failure.
1. Overview No . Name Type Status Description 8 SYSTEM1 LED: Green, orange, or red Status of the switch Green: The switch is available for operation. Orange: A partial switch fault has been detected. Red: A switch fault has been detected.
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. For a description of the LEDs on the switch, see the examples shown in Figure 1-2: Example layout of the front panel and Table 1-2: LED indications, buttons, and connectors.
1. Overview Table 1-2: LED indications, buttons, and connectors No . 1 2 Name PWR ST1 Type LED: Green LED: Green or red Status Power supply status Status of the switch LED brightnes s Description Green Regular Power is on. Blinking green#1 Regular Sleep state Off -- Power is off or the power supply failed.
1. Overview No . Name Type Status LED brightnes s Description 4 MC Connector Memory card slot -- -- Memory card slot 5 ACC LED: Green Memory card status ON Regular The memory card is being accessed. (Do not remove the memory card.) Low#3 Off -- The memory card is idle. (Memory cards can be inserted or removed.
1. Overview No .
1. Overview No . 24 Name LINK Type LED: Green or orange Status Operating status of 10/ 100/1000BASE-T Ethernet ports LED brightnes s Green Regular Description A link has been established.
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.
1. Overview Category IPv4 network communication failures IPv4 unicast routing communication failures Communication failures in the IPv4 multicast routing functionality IPv6 network communication failures IPv6 unicast routing communication failures 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.
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 VRF Communication not possible in the PIM-SM network 3.12.1 Communication is not possible on the IPv6 PIM-SM networks Data is forwarded twice in a PIM-SM network 3.12.
1. Overview Category Sub-category Reference Neighboring device information cannot be obtained by the LLDP functionality -- 3.17.1 Neighboring device information cannot be obtained by the LLDP functionality Neighboring device information cannot be obtained by the OADP functionality -- 3.17.2 Neighboring device information cannot be obtained by the OADP functionality NTP communication failures -- 3.18.1 The Switch cannot be synchronized by using NTP Failures when the IEEE 802.
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 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 No. 1 Problem • Smoke emanates from the switch. • An abnormal odor emanates from the switch. • An abnormal sound emanates from the switch. Action Immediately take the following actions: 1. Turn off the switch. 2.
2. Troubleshooting Switch Failures No. 6 Problem Action The STATUS LED of the BCU, CSU, or MSU is lit in red, the other LEDs are all off, and no message is displayed on the system operation panel. 1. Check the single or redundant configuration of the BCU, CSU, or MSU modules. (1) When a single configuration is used, follow steps 3 onwards shown below. (2) When a redundant configuration is used, follow steps 2 onwards shown below. 2. Check the status of the active and standby BCU, CSU, or MSU modules.
2. Troubleshooting Switch Failures No. Point to be checked Action 3 The power supply unit is not firmly installed and is unstable. Perform the following procedure: 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. 3. When a cable latch is used to fix the power cable in position, remove the cable latch from the cable. 4. Disconnect the power cable. 5.
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 No. 1 Problem • Smoke emanates from the switch. • An abnormal odor emanates from the switch. • An abnormal sound emanates from the switch. Action Immediately take the following actions: 1. Turn off the switch. 2.
2. Troubleshooting Switch Failures No. 5 Problem Action • The red ST1 LED of the switch blinks. • The LINK LED (10GBASE-R or 1000BASE-X port) and the 1-48 LED (10/100/1000BASE-T port) of ports on the switch are lit in orange or off. A problem has occurred on the switch or line. 1. For a redundant power model, check the status of the power supply unit and fan unit. If a fault is found, replace the applicable unit. - If the ALM LED of the fan unit is lit in red, replace the fan unit.
2. Troubleshooting Switch Failures Table 2-5: Isolating the cause of external redundant power unit failures No. Problem Action 1 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.
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 3.6 Layer 2 network communication failures 3.7 IPv4 network communication failures 3.8 IPv4 unicast routing communication failures 3.
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 password command in administrator mode to reset the forgotten login user password. Alternatively, ask the user to use the clear password command to delete the password.
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 show system or show mc command displays MC : --------, check the problem and take action according to the following table. Table 3-1: Action to take when "MC : --------" is displayed No. Items to check and commands Action 1 Check the ACC LED. If the ACC LED is green, another process might be accessing the memory card.
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.
3. Troubleshooting Functional Failures During Operation No. Problem Items to check 6 When the communication speed of the communication software is changed after login, unexpected characters are displayed and no commands can be entered. Despite changing the communication speed of the communication software after login, correct display is not possible. Restore the original communication speed of the communication software.
3. Troubleshooting Functional Failures During Operation Table 3-5: Problems occurring during connection to a remote terminal and action to take No. Problem Action 1 Remote connection is not possible. Perform the following procedure: 1. Use the ping command from a PC or workstation to make sure that a route for remote connection has been established. 2.
3. Troubleshooting Functional Failures During Operation 2. Use the killuser command to forcibly log out the target user. Specify the login number you checked in step 1, to the login no. parameter. Execution example (config)# $killuser 1 (2) When connected to a remote terminal Temporarily shut down the remote terminal, and then re-connect it.
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 (enable command), or command authorization. The specified password takes effect after the Switch restarts. 3.3.
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. 1. Checking the log For details about the log, see the manual Message and Log Reference. 2.
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 remote command all show version on the master switch to check the software information of all member switches in the stack configuration.
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. • For AX3800S, AX3600S, or AX2400S series switches: Check the port status and port statistics in this order. (1) Checking the status of the NIF 1.
3. Troubleshooting Functional Failures During Operation For details about the log, see the manual Message and Log Reference. 2. Isolating the cause of the problem by checking the port status Use the show interfaces command to check the port status, and isolate the cause of the problem according to the following table. Table 3-8: Checking the port status and action to take No. Port status Cause 1 active up The target port is operating normally.
3. Troubleshooting Functional Failures During Operation No. 7 Port status disable or locked Cause Action The shutdown configuration command is set. Make sure the cable is connected to the target port, and set the no shutdown configuration command to activate the target port. (3) Checking statistics You can use the show port statistics command to check the number of sent and received packets and the number of discarded send and receive packets for all ports on the Switch.
3. Troubleshooting Functional Failures During Operation No. Operating status of the BSU/PSP Cause 6 Action Correctly set the distribution pattern of the maximum number of entries per switch by using the fwdm prefer configuration command. 7 A failure has occurred on the target BSU/PSP. Based on the log entry for the target BSU/ PSP displayed by the show logging command, see the manual Message and Log Reference and take the action described in Action. The inactivate bsu command is set.
3. Troubleshooting Functional Failures During Operation Table 3-10: Failure analysis method for 10BASE-T/100BASE-TX/1000BASE-T problems No. 1 Items to check Use the show interfaces command to display the failure statistics, and check whether there is a count for the following item for the target port. If there is a count, see the Cause and Action columns. • Link down Cause Line quality is degraded. Action Check whether the cable types are correct. For the types, see the Hardware Instruction Manual.
3. Troubleshooting Functional Failures During Operation No. 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 no test interfaces command, and take the action described in Action. For the test types to be specified, see 6.1 Testing a line. 3 Use the show interfaces command The pin mapping of the cable is not correct. Modify the pin mapping correctly.
3. Troubleshooting Functional Failures During Operation 1. Checking the log For details about the log, see the manual Message and Log Reference. 2. 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. Table 3-11: Failure analysis method for 100BASE-FX/1000BASE-X problems No.
3. Troubleshooting Functional Failures During Operation No. 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. If they are dirty, clean them. Check whether the transceiver is connected correctly.
3. Troubleshooting Functional Failures During Operation No. 6 Items to check Use the show interfaces command to display the failure statistics, and check whether there is a count for the following item for the target port. If there is a count, see the Cause and Action columns. • Long frames 7 Use the show qos queueing command to check whether there is a count for the following item. If there is a count, see the Cause and Action columns.
3. Troubleshooting Functional Failures During Operation No. 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. Check whether the transceiver is connected correctly. Adjust the transceiver to comply with the segment standard of the remote device. Check whether the optical level is correct.
3. Troubleshooting Functional Failures During Operation No. 3 Items to check Cause For AX6700S, AX6600S, or AX6300S series switches, use the show interfaces command to display the failure statistics, and check whether there is a count for the following item for the target port. If there is a count, see the Cause and Action columns. • RF Line quality on the sending side is degraded. Action Check the type of the optical fiber. For the types, see the Hardware Instruction Manual.
3. Troubleshooting Functional Failures During Operation Table 3-13: Communication failure analysis method when PoE is used No. 1 Items to check and commands Use the show power inline command to check the information displayed for PoEStatus for the target port. Action • When off is displayed for PoEStatus: Power is not being supplied. Go to No. 2. • When denied is displayed for PoEStatus: The supplied power is insufficient for the entire switch. Go to No. 3.
3. Troubleshooting Functional Failures During Operation No. 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. To avoid the degradation, specify the same speed for all ports in the channel group. • Duplex Half The mode is Half and degradation has occurred.
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 show vlan command or the show vlan command with the detail parameter to check the status of the VLAN.
3. Troubleshooting Functional Failures During Operation Execute the show vlan mac-vlan command and make sure the MAC address set for a 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. # show vlan mac-vlan : VLAN ID:500 MAC Counts:4 0012.e200.aa01 (static) 0012.e200.
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. When Wa is displayed for Type: See 3.13.2 Communication failures occurring when Web authentication is used. When Macauth is displayed for Type: See 3.13.
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.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 5 Execute the show spanning-tree command with the detail parameter for the Spanning Tree Protocol that caused the failure, and then check the bridge identifier for the received BPDUs. Make sure the root bridge identifier and sending bridge identifier for the received BPDUs are the same as those defined in the network configuration.
3. Troubleshooting Functional Failures During Operation Table 3-16: Failure analysis method for the Ring Protocol No. 1 Items to check and commands Use the show axrp command to check the operating status of the Ring Protocol. Action If enable is displayed for Oper State, go to No. 3. If a hyphen (-) is displayed for Oper State, required items for using the Ring Protocol have not been configured. Check the configuration. If disable is displayed for Oper State, the Ring Protocol is disabled.
3. Troubleshooting Functional Failures During Operation No. 8 Items to check and commands Action Use the show vlan detail command to check the state of the VLAN used for the Ring Protocol and the VLAN port states. If there is no anomaly in the states of the VLAN and its ports, go to No. 9. Also, go to No. 10 for the configuration in which a Spanning Tree Protocol or GSRP is used together with the Ring Protocol, and go to No.
3. Troubleshooting Functional Failures During Operation Figure 3-4: Analysis flowchart Table 3-17: Failure analysis method for multicast forwarding No. Items to check and commands Action 1 Use the show logging command and check whether a failure has occurred. Check the following: • Check whether log information about a physical fault has been recorded. 2 Make sure filters and QoS control are configured correctly.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands 3 Make sure the settings for using IPv4 multicast are correct. Action Check the following: • For AX3800S or AX3600S series switches, check whether the setting of the swrt_multicast_table configuration command is applied. If the swrt_multicast_table configuration command is correctly set, On is displayed for Current selected swrt_multicast_table: when the show system command is executed.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands 4 Use the show igmp-snooping command to check the IGMP snooping configuration. Action Check the following: • To check whether the IGMP querier that monitors the group members 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.
3. Troubleshooting Functional Failures During Operation Figure 3-5: Analysis flowchart Table 3-18: Failure analysis method for multicast forwarding No. Items to check and commands 1 Use the show logging command and check whether a failure has occurred. Check the following: • Check whether log information about a physical fault has been recorded. 2 Make sure filters and QoS control are configured correctly.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands 3 Make sure the settings for using IPv6 multicast are correct. Action Check the following: • For AX3800S or AX3600S series switches, check whether the setting of the swrt_multicast_table configuration command is applied. If the swrt_multicast_table configuration command is correctly set, On is displayed for Current selected swrt_multicast_table: when the show system command is executed.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands 4 Use the show mld-snooping command to check the MLD snooping configuration. Action Check the following: • To check whether the MLD querier that monitors the group members exists, make sure one of the following messages is displayed.
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: 1. A configuration related to IP communication is changed. 2. The network configuration is changed. 3. A network device fails.
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. For details about the contents of the log, see the manual Message and Log Reference. 60 1. Log in to the Switch. 2.
3. Troubleshooting Functional Failures During Operation 5. 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. To check the status of the interface between the Switch and the neighboring device, do the following: 1. Log in to the Switch. 2.
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: 1. Log in to the Switch. 2. Use the show ip arp command to check the status of address resolution (whether ARP entry information exists) between the Switch and the neighboring device. 3.
3. Troubleshooting Functional Failures During Operation configuration. For details about the procedure, see 3.25.1 Checking the filters and QoS configuration information. In addition, if DHCP snooping is used, packets might have been discarded by a terminal filter. Check whether the setting conditions for DHCP snooping in the configuration are correct. For details about the procedure, see 3.27 DHCP snooping problems.
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 the show ip interface command to check whether the interface status is Up or Down. For details about the procedure, see 3.7.
3. Troubleshooting Functional Failures During Operation 1. Log in to the Switch. 2. Use the ping command to check the communication with the two remote devices that are unable to communicate. For details about examples of using the ping command and how to interpret the execution result, see the Configuration Guide. 3.
3. Troubleshooting Functional Failures During Operation 3. 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. 4.
3. Troubleshooting Functional Failures During Operation 2. The network configuration is changed. 3. 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. You might have checked the client and server settings (such as network card settings and cable connections) and concluded that cause 3 applies.
3. Troubleshooting Functional Failures During Operation 4. 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. 5. If DHCP snooping is used, packets might have been discarded by DHCP snooping. Check whether the setting conditions for DHCP snooping in the configuration are correct. For details about the procedure, see 3.27 DHCP snooping problems.
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: 1. A configuration is set incorrectly. 2. The network configuration is changed. 3. The DHCP server fails. First, check for cause 1. Described below are likely examples of incorrect configuration.
3. Troubleshooting Functional Failures During Operation 2. 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). 3. 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).
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.
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.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action If the status of every neighboring router is Full, go to No. 5. 4 Check whether the OSPF setting in the configuration is correct. If the configuration is correct, go to No. 5. If the configuration is not correct, modify the configuration. 5 Check the route that has learned the OSPF route. show ip route all-routes If the route is InActive, go to No. 6.
3. Troubleshooting Functional Failures During Operation No. 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. 3.8.
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.
3. Troubleshooting Functional Failures During Operation No. 3 Items to check and commands Make sure that PIM-SM is running on one or more interfaces. show ip pim interface 4 Check whether IGMP snooping is set for the interface on which PIM runs. show igmp-snooping 5 Make sure that the configuration does not contain filtering or other settings that suppress forwarding of protocol packets and multicast packets on the interface on which PIM and IGMP run.
3. Troubleshooting Functional Failures During Operation No. 13 Items to check and commands Make sure that multicast forwarding entries exist. show ip mcache 14 Make sure that multicast routing information exists. show ip mroute 15 Check whether the number of the multicast routing information entries or multicast forwarding entries exceeds its upper limit.
3. Troubleshooting Functional Failures During Operation No. 2 Items to check and commands Make sure the Switch is the rendezvous point for the forwarding target group address. show ip pim rp-hash Action If the Switch is not the rendezvous point, check the priorities of other rendezvous point candidates. A smaller value represents a higher priority. If the priority of another rendezvous point candidate is higher than that of the Switch, the Switch does not work as the rendezvous point.
3. Troubleshooting Functional Failures During Operation Table 3-27: Items to check for first-hop-router No. Items to check and commands Action 1 Make sure that the Switch is directly connected to the multicast sender. If the Switch is not connected directly, check the network configuration. 2 Make sure that PIM-SM or IGMP is running on the interface connected to the multicast sender. If PIM-SM or IGMP is not running, check and modify the configuration so that PIM-SM or IGMP runs on the interface.
3. Troubleshooting Functional Failures During Operation Notes: • first-hop-router: The router that is connected directly to the multicast sender • last-hop-router: The router that is connected directly to the multicast receivers (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. Table 3-29: Items checked in common No.
3. Troubleshooting Functional Failures During Operation No. 9 Items to check and commands Check the configuration to make sure that the PIM-SSM group addresses contain the forwarding target group address. Action If the PIM-SSM group addresses do not contain the forwarding target group address, modify the configuration. show running-config 10 Check whether multicast routing information exists.
3. Troubleshooting Functional Failures During Operation No. 7 Items to check and commands Action Check whether any anomaly has been detected on any interface. Make sure that no warning information is displayed for Notice. If warning information is displayed, check the following: • L: More participation requests than the expected maximum number have occurred. Check the number of connected users. • Q: The IGMP version is different from that on the neighboring router. Use the same IGMP version.
3. Troubleshooting Functional Failures During Operation Table 3-32: Items to check when data continues to be forwarded twice No. 1 Items to check and commands Check the PIM neighboring information of the interface belonging to the network with multiple routers. show ip pim neighbor Action If neighboring routers are not displayed, check the following: • Use the show ip pim command with the interface parameter to make sure that PIM-SM is running on the interface connected with the neighboring routers.
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. After that, check the following. Table 3-34: Items to check for an extranet No.
3. Troubleshooting Functional Failures During Operation Figure 3-12: Example of an IPv4 PIM-DM network Notes: • first-hop-router: The router that is connected directly to the multicast sender • last-hop-router: The router that is connected directly to the multicast receivers (1) Items checked in common The following table shows the items checked in common for all the Switches in an IPv4 PIM-DM network configuration. Table 3-35: Items checked in common No.
3. Troubleshooting Functional Failures During Operation No. 6 Items to check and commands Check the PIM neighboring information. show ip pim neighbor 7 Check whether the unicast route to the multicast data sender exists. Action If neighboring routers are not displayed, check the following: • Use the show ip pim interface command to make sure that PIM is running on the interface connected with the neighboring routers. • Check the settings of the neighboring routers.
3. Troubleshooting Functional Failures During Operation IPv4 PIM-DM network configuration. Table 3-37: Items to check for first-hop-router No. Items to check and commands Action 1 Make sure that the Switch is directly connected to the multicast sender. If the Switch is not connected directly, check the network configuration. 2 Make sure that PIM-DM is running on the interface connected to the multicast sender.
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: 1. A configuration related to IPv6 communication is changed. 2. The network configuration is changed. 3. A network device fails.
3. Troubleshooting Functional Failures During Operation For details about the contents of the log, see the manual Message and Log Reference. 1. Log in to the Switch. 2. Use the show logging command to display the log. 3. 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. 4.
3. Troubleshooting Functional Failures During Operation 3. If communication with the remote device cannot be verified by using the ping ipv6 functionality, use the ping ipv6 command to check communication with each of the devices up to the remote device, beginning with the device closest to the customer's terminal. 4.
3. Troubleshooting Functional Failures During Operation possible, address information might not be correctly distributed by RA. Therefore, check whether the RA functionality is correctly set in the configuration. To carry out the check, do the following: 1. Log in to the Switch. 2. Execute the show ipv6 routers command to check the RA information for the Switch. 3. If the IPv6 address information has been correctly distributed, the interface might have a problem with the functionality shown below.
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 show ipv6 interface command to check whether the interface status is Up or Down. For details about the procedure, see 3.10.
3. Troubleshooting Functional Failures During Operation 1. Log in to the Switch. 2. Use the show ipv6 neighbors command to check the status of address resolution (whether NDP entry information exists) between the Switch and the neighboring device. 3. If the address with the neighboring device has been resolved (NDP entry information exists), see (4) Checking the unicast routing information. 4.
3. Troubleshooting Functional Failures During Operation prefix or address to the target client is set by the ipv6 dhcp relay destination configuration command. 4. Check whether the hop-limit value specified for the ipv6 dhcp relay hop-limit configuration command is equal to or larger than an appropriate hop value for the client. 3.10.
3. Troubleshooting Functional Failures During Operation (b) Checking the status of the IPv6 DHCP server on the Switch 1. Checking whether the IPv6 DHCP server service is running Use the show ipv6 dhcp server statistics command to check whether information can be obtained from the IPv6 DHCP server daemon. If the following result is displayed by executing the show ipv6 dhcp server statistics command, use the service ipv6 dhcp configuration command to configure the IPv6 DHCP server functionality again.
3. Troubleshooting Functional Failures During Operation ! (config)# (d) Duplicate assignment to a client 1. Checking the binding information Use the show ipv6 dhcp binding command with the detail parameter to check whether multiple prefixes have been distributed to a single DUID. The following shows an example.
3. Troubleshooting Functional Failures During Operation 1. The configuration has been set but not distributed. 2. 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 show ipv6 route -s command to display the routing information. Next, execute the show ipv6 dhcp server binding command to display the information of the distributed prefixes.
3. Troubleshooting Functional Failures During Operation Destination 3ffe:1234:5678::/48 Next Hop ::1 Dhcp> ::1 Dhcp> Interface tokyo Metric 0/0 osaka 0/0 Protocol Static Age 45m Static 23m (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.
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.
3. Troubleshooting Functional Failures During Operation No. 3 Items to check and commands Action Check the status of every neighboring router from the information in Neighbor List. If the status of any neighboring router is other than Full, go to No. 4. If the status of every neighboring router is Full, go to No. 5. 4 Check whether the OSPFv3 setting in the configuration is correct. If the configuration is correct, go to No. 5. If the configuration is not correct, modify the configuration.
3. Troubleshooting Functional Failures During Operation No. 5 Items to check and commands Check whether the route is filtered in the configuration. Action Check whether the neighboring router is advertising the BGP4+ 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. 3.11.
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.
3. Troubleshooting Functional Failures During Operation No. 4 Items to check and commands Action Check whether MLD snooping is set for the interface on which PIM runs. If MLD snooping is set, check the following: • Check whether the multicast router port for MLD snooping is set for the port connected to the neighboring router. • See 3.6.5 Multicast forwarding by MLD snooping is not possible.
3. Troubleshooting Functional Failures During Operation No. 15 Items to check and commands Check whether the number of the multicast routing information entries or multicast forwarding entries exceeds its upper limit. For the multicast routing information: show ipv6 mroute For the multicast forwarding entries: Action If a warning is displayed, check whether an unexpected multicast routing information entry or unexpected multicast forwarding entry has been created.
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 last-hop-router in an IPv6 PIM-SM network configuration. Table 3-48: Items to check for last-hop-router No. 1 Items to check and commands Make sure that MLD is running on the interface connected to the multicast receivers. Action If MLD is not running, check and modify the configuration so that MLD runs on the interface.
3. Troubleshooting Functional Failures During Operation No. 3 Items to check and commands Check whether multicast routing information exists. show ipv6 mroute Action If multicast routing information does not exist, make sure that the multicast data source address is the network address of the interface directly connected to the multicast sender. 3.12.
3. Troubleshooting Functional Failures During Operation network configuration. Table 3-51: Items checked in common No. 1 Items to check and commands Action Make sure that the setting for using the multicast functionality (ipv6 multicast routing) exists in the configuration. If the setting for using the multicast functionality does not exist, modify the configuration. show running-config 2 Make sure that the address setting for the loopback interface exists in the configuration.
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 last-hop-router in an IPv6 PIM-SSM network configuration. Table 3-52: Items to check for last-hop-router No. 1 Items to check and commands If the mode of the multicast receivers is MLDv1 or MLDv2 (EXCLUDE mode), make sure that ipv6 mld ssm-map enable is set in the configuration.
3. Troubleshooting Functional Failures During Operation No. 9 Items to check and commands Action Check whether any anomaly has been detected on any interface. Make sure that no warning information is displayed for Notice. If warning information is displayed, check the following: • L: More participation requests than the expected maximum number have occurred. Check the number of connected users. • Q: The MLD version is different from that on the neighboring router. Use the same MLD version.
3. Troubleshooting Functional Failures During Operation Table 3-54: Items to check when data continues to be forwarded twice No. 1 Items to check and commands Action If neighboring routers are not displayed, check the following: • Use the show ipv6 pim command with the interface parameter to make sure that PIM is running on the interface connected with the neighboring routers. • Make sure that the configuration does not contain filtering or other settings that suppress forwarding of protocol packets.
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 No. 1 Items to check and commands Make sure that the unicast route from the destination VRF to the source address is the expected VRF or global network. Action If it is not the case, check the settings of the unicast extranet.
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 No.
3. Troubleshooting Functional Failures During Operation No. 6 Items to check and commands Execute the show dot1x logging command, and check whether authentication failed. Action • If New Supplicant Auth Fail. is displayed, authentication failed for either of the following reasons. Check for problems. The user ID or password has not been registered on the authentication server. The user ID or password is entered incorrectly.
3. Troubleshooting Functional Failures During Operation No. 7 Items to check and commands Action Execute the show dot1x logging command, and check whether dynamic allocation in VLAN-based authentication (dynamic) failed. • If Failed to assign VLAN.(Reason: No Tunnel-Type Attribute) is displayed, dynamic allocation has failed because the Tunnel-Type attribute is not set for the RADIUS attribute of the RADIUS frame. Add the Tunnel-Type attribute in the RADIUS attribute setting of the RADIUS server.
3. Troubleshooting Functional Failures During Operation failures. Table 3-58: Communication failure analysis method for IEEE 802.1X No. Items to check and commands Action 1 Make sure that VLANs with a VLAN-based authentication (static) setting and VLANs with another setting are not set simultaneously for the trunk port. Communication is possible only for VLANs with a VLAN-based authentication (static) setting.
3. Troubleshooting Functional Failures During Operation No. 3 Items to check and commands Make sure that the Web server is running. Action • Execute the following command to check whether the Web server is running. If the Web server is running, go to No. 4. Command: # ps -auwx | grep httpd Check procedure: If /usr/local/sbin/httpd is displayed in the result of the ps command, the Web server is running. • If the Web server is not running, check the web-authentication web-port configuration command.
3. Troubleshooting Functional Failures During Operation No. 7 Items to check and commands Use the show web-authentication statistics command to check the communication status with the RADIUS server. Action • If the value displayed for TxTotal under [RADIUS frames] is 0, check whether the aaa authentication web-authentication default group radius and radius-server host configuration commands have been set correctly.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 13 Check whether authentication fails on the connected terminal. • If a terminal subject to authentication cannot be authenticated at all, use the restart web-authentication web-server command to restart the Web server. • If authentication still fails after the Web server restarts, execute the restart vlan mac-manager command.
3. Troubleshooting Functional Failures During Operation Table 3-60: Checking the configuration of Web authentication No. 1 Items to check Check the Web authentication configuration settings. Action Make sure the following configuration commands have been set correctly.
3. Troubleshooting Functional Failures During Operation No. Items to check Action 5 Check the configuration of the access filter for authentication. For fixed or dynamic VLAN mode, make sure the filter conditions required for communication from unauthenticated terminals to destinations outside the Switch have been set correctly by using the authentication ip access-group and ip access-list extended configuration commands. 6 Check the ARP relay configuration.
3. Troubleshooting Functional Failures During Operation Table 3-62: Failure analysis method for MAC-based authentication No. Items to check and commands Action 1 Check whether communication with the terminal is possible. • If authentication in local authentication method is not possible, go to No. 2. • If authentication in RADIUS authentication method is not possible, go to No. 3. • For other cases, go to No. 5.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 5 Check the setting of the authentication IPv4 access list. • If an unauthenticated terminal sends certain types of 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 standard access list.
3. Troubleshooting Functional Failures During Operation No. 2 Items to check Action Check the configuration of the access filter for authentication. Make sure the filter conditions required for communication from unauthenticated terminals to destinations outside the Switch have been set correctly by using the authentication ip access-group and ip access-list extended configuration commands. Check the following for the accounting of MAC-based authentication.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 3 Execute the show fense server command to check the operating status of the authentication VLAN. • If VAA NAME is not set (i.e., - is displayed), the fense vaa-name command is not set in the configuration. Set the fense vaa-name command in the configuration. • If disable is displayed for Status of VAA IDs, the authentication VLAN is not operating. Check the configuration. • For other cases, go to No. 4.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 8 Execute the show vlan mac-vlan command, and make sure authenticated MAC addresses have been registered for the MAC VLAN functionality. • If the show vlan mac-vlan command shows that authenticated MAC addresses have been registered, authentication of those MAC addresses cannot be enabled. Delete the registered MAC addresses.
3. Troubleshooting Functional Failures During Operation No. 4 126 Items to check Check the filtering configuration. Action 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. • Between the VLAN used for authentication and the VLAN for the authentication server: A filter is set to forward only HTTP, DHCP, and ICMP communication.
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 No.
3. Troubleshooting Functional Failures During Operation Table 3-68: Failure analysis method when state switching fails in a GSRP configuration No. 1 Items to check and commands Use the show gsrp command to check the status of the VLAN group in which intended switching between master and backup states does not occur. Action If the state of one of them is Master and the state of the other is other than Master, go to No. 2.
3. Troubleshooting Functional Failures During Operation No. 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. 3.14.
3. Troubleshooting Functional Failures During Operation No. 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. 6 Check communication between routers that make up the virtual router by using the ping command with actual IPv4 addresses.
3. Troubleshooting Functional Failures During Operation No. 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. 8 Execute the show interfaces command and check the statistics for the physical port to which a remote device that makes up the same virtual router is connected. Also, execute the show cpu command to check the CPU usage.
3. Troubleshooting Functional Failures During Operation Table 3-71: Failure analysis method for VRRP No. 1 Items to check and commands Action On the Switch and remote devices that make up a virtual router, check the status of the virtual router, and check whether only one device is the master router and the others are backup routers.
3. Troubleshooting Functional Failures During Operation No. 7 Items to check and commands Action Execute the show vrrpstatus command with the statistics parameter, and check the reception status of ADVERTISEMENT packets. • You might find that the following is registered in the reference log: Virtual router of received VRRP packet for which the advertisement interval is different than the one configured for local virtual router.
3. Troubleshooting Functional Failures During Operation No. 8 Items to check and commands Action Execute the show interfaces command and check the statistics for the physical port to which a remote device that makes up the same virtual router is connected. Also, execute the show cpu command to check the CPU usage.
3. Troubleshooting Functional Failures During Operation Table 3-72: Failure analysis method for uplink redundancy No. 1 Items to check and commands Execute the show switchport-backup command, and make sure that the states of the primary and secondary ports are Forwarding or Blocking correctly. Action If neither the primary port nor the secondary port is Forwarding, check the following: • If both of them are Blocking, active port locking might be enabled.
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 show access-list configuration command, and check whether the IP address of the SNMP manager has been set in the access list in the configuration.
3. Troubleshooting Functional Failures During Operation When using SNMPv3 Execute the show snmp-server configuration command, and check whether the information about SNMP and traps has been set correctly in the configuration of the Switch. If the information has not been set correctly, execute the following configuration commands to set the information about SNMP and traps.
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.
3. Troubleshooting Functional Failures During Operation Send CounterSample UDP packets: 621 Send failed packets: 0 > 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. Figure 3-21: Configuration example 1 (config)# show sflow sflow destination 192.1.1.1 6455 correctly.
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.
3. Troubleshooting Functional Failures During Operation (1) Checking whether packets are forwarded Execute the show interfaces command, and check whether packets are forwarded. Figure 3-27: Example of the port status > show interfaces gigabitethernet 1/5 Date 2006/10/24 17:19:34 UTC NIF1: active 48-port 10BASE-T/100BASE-TX/1000BASE-T retry:0 Average:150Mbps/24Gbps Peak:200Mbps at 15:44:37 Port5: active up 100BASE-TX full(auto) 0012.e220.
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. Table 3-73: Failure analysis method when the LLDP functionality is used No.
3. Troubleshooting Functional Failures During Operation Table 3-74: Failure analysis method when the OADP functionality is used No. 1 Items to check and commands Execute the show oadp command and check the operating status of the OADP functionality. Action If Enabled is displayed for Status, go to No. 2. If the displayed status is Disabled, the OADP functionality has been disabled. Enable the OADP functionality. 2 Execute the show oadp command and check the port information.
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 No. 1 Items to check and commands Action Use the show clock command to make sure the time zone is set.
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. Table 3-76: Failure analysis method when the IEEE 802.3ah/UDLD functionality is used No.
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. Table 3-77: Problems occurring during switchover of the active system and action to take No. Cause of the problem in switching 1 The standby system is not running.
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. 1. Checking the log For details about the log, see the manual Message and Log Reference. 2.
3. Troubleshooting Functional Failures During Operation No. Operating status of BSU units Cause Action 4 notconnect The target BSU is not implemented. Make sure that as many BSU boards as the number of active and standby BSUs (or the number of active BSUs only, if standby BSUs are not required) are implemented. If the required number of boards is already implemented, no action is required. If not implemented, implement as many BSU boards as required.
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. Table 3-79: Failure analysis method when the standby NIF cannot be switched to the active system No.
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. 1. Execute the show power-control schedule command to check whether the displayed schedule contains the current time, and isolate the cause of the problem according to the following table. Table 3-81: Scheduling problems occurring when the power saving functionality is used and action to take No.
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 up. Packet congestion in CPU processing occurs due to the overflow of the input queue when the CPU receives a large number of packets to be processed in software.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action If the packet type is arp, a large number of ARP packets have been received. In this case, an L2 loop configuration might be used. Revise the network configuration. If there is no problem in the network configuration, check the settings of the terminal that has the source address. 4 Collect analysis information.
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.
3. Troubleshooting Functional Failures During Operation discard_pkt statistics item displayed for the port input and output queues of the input and output interfaces used for communication. 3. Execute the show qos queueing command with the distribution parameter, and check the discard_pkt statistics item displayed for the distribution input and output queues for the input or output interface used for communication. 4.
3. Troubleshooting Functional Failures During Operation 3.26 Access list logging problems 3.26.1 Actions to be taken when access list logs are not output If an access list log cannot be output when access list logging is used, take the following action. Table 3-83: Action to take when access list logs are not output No. 1 Items to check and commands Action Check the log output status of access list logging.
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 No.
3. Troubleshooting Functional Failures During Operation No. Items to check Action 8 Make sure the DHCP server is connected to a trusted port. DHCP server response packets from an untrusted port are discarded. If the target DHCP server is an authorized one, set the ip dhcp snooping trust configuration command for the port to which the DHCP server is connected. Note that if the DHCP server on the Switch is used, the port can be an untrusted port.
3. Troubleshooting Functional Failures During Operation No. 5 Items to check Action Make sure that the lease time of the IP addresses distributed to the DHCP clients is longer than the wait time for saving the database. If the lease time is shorter, the lease of the IP addresses might expire before the binding database is completely read in. Use the ip dhcp snooping database write-delay configuration command to shorten the wait time for saving the database on the Switch.
3. Troubleshooting Functional Failures During Operation No. Items to check Action If there is no problem, go to No. 2. 2 Check whether the ip verify source configuration command is set for the target port. If ip verify source is set, packets from devices not in the binding information are discarded. If there is no problem, go to No. 3. If ip verify source is not set, go to No. 4.
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 No.
3. Troubleshooting Functional Failures During Operation No. 6 Items to check and commands Check the path switch-back operation setting of policy-based routing • Execute the show ip cache policy command, and check the Recover item. Action If the setting is Off, path switch-back operations are not performed, and thus the path is not being re-selected. Execute the reset policy-list command to re-select the path. If the setting is On, go to No. 7.
3. Troubleshooting Functional Failures During Operation No. 3 Items to check and commands Action Check the operating status of path switching in policy-based routing • Check the Start Time and End Time values of the Policy Base Routing Default Init Interval of the show ip cache policy command. If - is displayed for End Time only, the packets might have been discarded because the group is in the process of starting. Wait until startup finishes.
3. Troubleshooting Functional Failures During Operation target. 3. 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 No.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action If the track operating status is Init, the track is stopped 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. 2 Check whether IPv4 communication can be made with track target For the destination address, source address, and next hop, use the same values as for the track settings. • Execute the ping command.
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 No.
3. Troubleshooting Functional Failures During Operation No. 6 Items to check and commands Check the path switch-back operation settings for policy-based switching • Execute the show cache policy-switch command, and check the Recover item. Action If the setting is Off, path switch-back operations are not performed, and thus the path is not being re-selected. Execute the reset policy-switch-list command to re-select the path. If the setting is On, go to No. 7.
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.
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 No.
4. Troubleshooting Communication Failures Due to a Resource Shortage No. Trigger Log message 9 Web authentication (fixed VLAN mode) The login failed because of hardware restriction. Note: This log message is displayed when the show web-authentication logging command is executed. 10 MAC-based authentication The login failed because of hardware restriction. Note: This log message is displayed when the show mac-authentication logging command is executed.
4. Troubleshooting Communication Failures Due to a Resource Shortage No. 5 Entry to be deleted IGMP/MLD snooping Procedure Execute the clear igmp-snooping all and clear mld-snooping all commands.#1 6 Web Authentication Execute the clear web-authentication auth-state command to cancel authentication.#1 7 MAC-based authentication Execute the clear mac-authentication auth-state command to cancel authentication.
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. The table below lists the operation log message to be output. Table 4-4: Operation log message that indicates resource usage No.
4. Troubleshooting Communication Failures Due to a Resource Shortage No. Trigger 5 Authentication VLAN 6 Web authentication (dynamic VLAN mode) Loge message • The registration of the MAC address failed. Note: This log message is displayed when the show fense logging command is executed. • The login failed because of hardware restriction. Note: This log message is displayed when the show web-authentication logging command is executed.
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.
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. 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.
5. Obtaining Failure Information Item Path and file name Remarks Dump information file created when the NIF fails /usr/var/hardware/nif**.*** in the system that failed (For versions prior to Version 10.5: /dump0/nif**.*** in the active system) **: NIF number of the NIF that failed ***: Serial number assigned since the first dump data was collected. Up to two files, the oldest and the latest files, are stored.
5. Obtaining Failure Information Item Path and file name Remarks Information when the configuration file encounters an error In administrator mode, execute the following commands to copy two files to the home directory. Then transfer these files. • Use binary mode to transfer these files with the ftp command. • Delete the source files after the transfer is completed. cp /config/system.cnf system.cnf cp /config/system.txt system.
5. Obtaining Failure Information 1. In the active system, execute the dump psp command for the PSP in the active system. 2. In the active system, execute the dump nif command for the port that has failed. Example: The following procedure shows an example in which communication fails on port number 1 of NIF number 1. 1. Log in to the active system, and then execute the dump command. > dump psp Dump command accept. > 11/01 17:43:42 E3 CSU 25070700 2301:000000000000 PSP online dump command executed. 2.
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. 1. Log in to the active BCU, and then execute the dump command. > dump bsu 1 Dump command accept. > 11/01 17:43:42 E3 BSU BSU:1 25070700 1681:000000000000 BSU online dump command executed. 2. After the above log information is displayed, execute the following dump command. > dump bsu 2 Dump command accept.
5. Obtaining Failure Information 11/01 18:18:42 E3 CSU 25070700 2301:000000000000 PSP online dump command executed. 4. After the above log information is displayed, log in to the standby system, and then execute the following dump command. SBY:> dump psp Dump command accept. SBY:> 11/01 18:20:42 E3 CSU 25070700 2301:000000000000 PSP online dump command executed. In the AX6300S series: 1. In the active system, execute the dump psp command for the PSP in the active system. 2.
5. Obtaining Failure Information 2. In the active BCU, execute the dump nif command for all the ports that have failed. 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. 1. Log in to the active BCU, and then execute the dump command. > dump bsu 1 Dump command accept. > 11/01 17:43:42 E3 BSU BSU:1 25070700 1681:000000000000 BSU online dump command executed. 2.
5. Obtaining Failure Information 5.2 Transferring maintenance information files This section describes how to transfer files that contain log or dump information. The ftp 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 zmodem command.
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. Password: 230 User staff1 logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> ascii <---2 200 Type set to A.
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'. 100% |**********************************************************************| 1476 KB 1.
5. Obtaining Failure Information > cd /usr/var/core/ > ls interfaceControl.core nodeInit.core > zmodem put interfaceControl.core > zmodem put nodeInit.core > 1. <---1 <---2 Make sure that the error save information file exists. If the file does not exist, exit the procedure without doing anything. 2. 186 Transfer the log file.
5. Obtaining Failure Information 5.3 Collecting information and transferring files by using the "show tech-support" command You can use the show tech-support command to collect information when a failure has occurred in a batch operation. You can also specify the ftp parameter for this command to transfer the collected information to a remote terminal or remote host.
5. Obtaining Failure Information ............................................................................... ........... ............................................................................... ........................................................ Operation normal end. > 1. Execute the command. 2. Specify the remote host name. 3. Specify a user name. 4. Enter the password. 5. Specify the destination directory. 6. Specify a file name. 7.
5. Obtaining Failure Information 5. Specify the destination directory. 6. 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) > remote command 2 show tech-support > support.txt <---1 Executing. ......................................................
5. Obtaining Failure Information 5.4 Collecting information and transferring files by using the "ftp" command on a remote terminal You can use the ftp 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 ftp command. You cannot connect to member switches other than the master switch by using the ftp command.
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. ftp> get .show-tech-unicast show-tech-uni.txt <---2 local: show-tech-uni.txt remote: .show-tech-uni.
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> get .dump dump.tgz <---3 local: dump.tgz remote: .dump 150 Opening BINARY mode data connection for '/etc/ftpdump'. 226 Transfer complete. 2411332 bytes received in 5.78 seconds (407.
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. Figure 5-13: Writing information to a memory card Insert a memory card into the Switch to which information is to be written.
Chapter 6. Line Testing 6.
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.
6. Line Testing Date 2006/03/10 00:20:21 UTC Interface type :100BASE-TX Test count :30 Send-OK :30 Receive-OK :30 Data compare error :0 Out buffer hunt error :0 In CRC error :0 In monitor time out :0 H/W error :none > activate gigabitethernet 1/1 Send-NG Receive-NG Out underrun Out line error In frame alignment In line error :0 :0 :0 :0 :0 :0 After the test is completed, check the following: If both Send-NG and Receive-NG are 0, the line test has successfully completed.
6. Line Testing Figure 6-4: Twisted pair cable 2. 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. (Loop operation by the 1000BASE-T connector is a non-standard, proprietary action.) (3) 40GBASE-SR4 loop connector Use a loop connector as specified below.
Chapter 7. Device Restart This chapter mainly describes how to restart the device. 7.
7. Device Restart 7.1 Restarting the device 7.1.1 Device restart You can use the reload command to restart the device. Log data is stored when the device restarts. For details on the syntax and parameters of the command, see the manual Operation Command Reference. AX6700S, AX6600S, and AX6300S series switches As an example, the following steps describe how to select parameters for the reload command.
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. According to the figure above, the standby parameter is used. Combining the parameters selected in steps 1 through 3 results in the command reload standby.
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. Step1 Choose whether you want to restart or stop the device. Figure 7-5: Selecting to restart or stop the device In step 1, you restart the device.
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 reload. When you enter this command, the dump capture confirmation messages are displayed as follows: 1. Dump information extracted?(y/n):_ 2.
7.
Appendix A.
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 show tech-support command. For details on the displayed information, see the manual Operation Command Reference.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 15 /usr/local/diag/pk_tmrd Operating time information (for Version 11.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 41 stty -a -f /dev/tty00 Console terminal information Y Y Y Y 42 cat /var/log/clitrace1 CLI trace information 1 Y Y Y Y 43 cat /var/log/clitrace2 CLI trace information 2 Y Y Y Y 44 cat /var/log/mmitrace Operation command trace information (for Version 10.5 and later) Y Y Y Y 45 cat /var/log/kern.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 61 cat /var/tmp/gen/trace/ mng_sub.trc Configuration command trace information 3 (for Version 10.7 and later) Y Y Y Y 62 tail -n 400 /var/tmp/gen/ trace/api.trc Configuration command trace information 4 (for Version 10.7 and later) Y Y Y Y 63 tail -n 400 /var/tmp/gen/ trace/ctl.
A. Detailed Display Contents of the "show tech-support" Command No.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 106 show dot1x detail Authentication status information on IEEE 802.
A. Detailed Display Contents of the "show tech-support" Command No.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 149 show ip arp inspection statistics Dynamic ARP inspection statistics (for Version 11.4 and later) Y Y Y Y 150 show ip dhcp snooping logging info DHCP snooping log information (for Version 11.4 and later) N N N Y 151 dhsn debug DHCP snooping event information (for Version 11.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 167 show graceful-restart unicast Operating status of restart routers that perform graceful restarts in the unicast routing protocol (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 185 show web-authentication user commit Display of entries registered in the internal Web authentication DB (for Version 10.3 and later) N N N Y 186 show web-authentication statistics Display of Web authentication statistics (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 200 show engine-traffic statistics detail minutes Average bandwidth used by packet-transfer buses (per minute) (for Version 11.4 and later) Y Y Y Y 201 pktbusdisp For AX6700S series switches, the display of the combination of packet-transfer buses and port numbers (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 7 show cpu days hours minutes seconds CPU utilization Y Y Y Y 8 show memory summary Memory usage of the device Y Y Y Y 9 /sbin/dmesg Kernel event information Y Y Y Y 10 cat /var/run/dmesg.boot Kernel event information (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 32 show session Login session information Y Y Y Y 33 /usr/sbin/pstat -t Terminal information Y Y Y Y 34 stty -a -f /dev/tty00 Console terminal information Y Y Y Y 35 ls -lTiR /var/tmp/mmi* CLI information file list (for versions earlier than Version 10.1.
A. Detailed Display Contents of the "show tech-support" Command No.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 75 show loop-detection statistics Statistics on L2 loop detection (for Version 10.7 and later) N N N Y 76 show loop-detection logging Log information for L2 loop detection (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 95 show dot1x detail Authentication status information on IEEE 802.
A. Detailed Display Contents of the "show tech-support" Command No.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 137 show ip dhcp snooping logging info DHCP snooping log information (for Version 11.4 and later) N N N Y 138 dhsn debug DHCP snooping event information (for Version 11.4 and later) N N N Y 139 show ip route summary Number of active and inactive routes maintained by routing protocols For versions prior to Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. 155 Command (displayed) show ipv6 route summary Description Number of active and inactive routes maintained by the unicast routing program No para met er spe cifie d unic ast mult icas t laye r-2 For versions prior to Version 10.6 N Y N N For Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 173 show web-authentication login Display of authenticated-user information (account information) (for Version 10.3 and later) N N N Y 174 show web-authentication logging Display of operation logs for Web authentication (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 189 show track-object detail Detailed information of tracking functionality for policy-based routing (For AX3800S Version 11.9 and later. Also for AX3650S and AX3640S Version 11.7 and later.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 9 /sbin/dmesg Kernel event information Y Y Y Y 10 cat /var/run/dmesg.boot Kernel event information (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 35 ls -lTiR /var/tmp/mmi* CLI information file list (for versions earlier than Version 10.1.A) Y Y Y Y 36 cat /var/log/clitrace1 CLI trace information 1 Y Y Y Y 37 cat /var/log/clitrace2 CLI trace information 2 Y Y Y Y 38 cat /var/log/mmitrace Operation command trace information (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 77 show spanning-tree statistics Spanning tree statistics N N N Y 78 show vlan detail VLAN details N Y Y Y 79 show vlan mac-vlan MAC VLAN information N N N Y 80 show qos queueing Statistics on all queues For versions prior to Version 10.6 N Y Y Y For Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 100 show ip dhcp snooping logging info DHCP snooping log information (for Version 11.4 and later) N N N Y 101 dhsn debug DHCP snooping event information (for Version 11.4 and later) N N N Y 102 show web-authentication user edit Display of registrations and changes in the internal Web authentication DB (for Version 10.
A. Detailed Display Contents of the "show tech-support" Command No. Command (displayed) Description No para met er spe cifie d unic ast mult icas t laye r-2 116 show mac-authentication logging Display of operation logs for MAC-based authentication (for Version 10.6 and later) N N N Y 117 show power-control schedule Schedule information of power saving functionality (for Version 11.4 and later) Y Y Y Y 118 swdev logging Display of SW subunit logs (for Version 11.1.
Index Symbols "MC not found.
Index faults for AX6700S, AX6600S, and AX6300S series switches 16 flow samples cannot be sent to the collector 140 forgotten login user password 24 forgotten password for administrator mode 24 G GSRP communication failures 127 I information cannot be entered from the console or does not appear correctly 26 internal loopback test 196 IP addresses cannot be assigned by the DHCP functionality 63 IPv4 multicast communication problems in VRF 83 IPv4 network communication failures 59 IPv4 routing information c
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 W when a resource shortage occurs in shared memory 173 when a VLAN identification table resource shortage occur
