Table of Contents

Advertisement

Quick Links

AX2500S
Troubleshooting Guide
AX25S-T001X-60

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the AX25S-T001X-60 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Alaxala AX25S-T001X-60

  • Page 1 AX2500S Troubleshooting Guide AX25S-T001X-60...
  • Page 2 This manual applies to the models of the AX2500S series of switches. Export restrictions In the event that any or all ALAXALA products (including technologies, programs and services) described or contained herein are controlled under any of applicable export control laws and regulations (including the Foreign...
  • Page 3 History of Amendments (Edition 7) Summary of amendments Location and title Changes  3.11 Troubleshooting the sFlow This subsection was added. statistics (flow statistics) functionality  Appendix A. Detailed Display Commands were added to the Displayed information. Contents of the show tech-support Command In addition to the above changes, minor editorial corrections were made.
  • Page 4 (Edition 4) Summary of amendments Location and title Changes  A description of AX2530S-24T4X/AX2530S-48T2X switches was added. In addition to the above changes, minor editorial corrections were made. (Edition 3) Summary of amendments Location and title Changes  SNMP communication failures A description of SNMPv3 was added.
  • Page 5 Location and title Changes  Actions to be taken for 10GBASE-R This subsection was added. problems [24S4X]  Actions to be taken for direct attach This subsection was added. cable problems [24S4X]  Problems related to the support This subsection was added. regarding long life solutions ...
  • Page 7: Preface

    This manual is intended for system administrators who wish to configure and operate a network system that uses the Switch. Readers must have an understanding of the following:  The basics of network system management Manual URL You can view this manual on our website at: http://www.alaxala.com/en/...
  • Page 8 Preface 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 an AX2500S series switch. Abbreviations used in the manual Alternating Current ACKnowledge ADSL...
  • Page 9 Preface BPDU Bridge Protocol Data Unit Basic Rate Interface Continuity Check Cisco Discovery Protocol Connectivity Fault Management CIDR Classless Inter-Domain Routing Committed Information Rate CIST Common and Internal Spanning Tree CLNP ConnectionLess Network Protocol CLNS ConnectionLess Network System CONS Connection Oriented Network System Cyclic Redundancy Check CSMA/CD Carrier Sense Multiple Access with Collision Detection...
  • Page 10 Preface IPCP IP Control Protocol IPv4 Internet Protocol version 4 IPv6 Internet Protocol version 6 IPV6CP IP Version 6 Control Protocol Internetwork Packet Exchange International Organization for Standardization Internet Service Provider Internal Spanning Tree L2LD Layer 2 Loop Detection Local Area Network Link Control Protocol Light Emitting Diode Logical Link Control...
  • Page 11 Preface Port Access Entity Personal Computer Protocol Control Information Protocol Data Unit PICS Protocol Implementation Conformance Statement Protocol IDentifier Protocol Independent Multicast PIM-DM Protocol Independent Multicast-Dense Mode PIM-SM Protocol Independent Multicast-Sparse Mode PIM-SSM Protocol Independent Multicast-Source Specific Multicast Power over Ethernet Primary Rate Interface Power Supply PSNP...
  • Page 12 Preface Type Of Service TPID Tag Protocol Identifier Time To Live UDLD Uni-Directional Link Detection User Datagram Protocol Uplink Redundant Usage Parameter Control UPC-RED Usage Parameter Control - Random Early Detection VLAN Access Agent VLAN Virtual LAN VRRP Virtual Router Redundancy Protocol Wide Area Network Wavelength Division Multiplexing Weighted Fair Queueing...
  • Page 13 Safety Information Using AX2500S series switches properly and safely  This guide provides important information for ensuring safe use of AX2500S series switch. Please read this manual completely before using the Switch.  Keep this manual handy after reading it, so that it is available for later reference. ...
  • Page 14 Safety Information If anything seems wrong, immediately turn off the power.  If smoke or an unusual smell is emanating from the Switch, or if liquid is spilled into the Switch or a foreign object falls into the Switch, immediately turn off Switch power as described below.
  • Page 15 Safety Information 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. If it is not, the circuit breaker might not operate properly in the event of a failure, which could result in a fire.
  • Page 16 Safety Information Do not remove the Switch cover.  Do not remove the Switch cover. Doing so could result in electric shock. The following label is attached to a Switch. Safety-4...
  • Page 17 Safety Information Do not place the Switch in a place where it is unstable.  If placing the Switch on a desk, lay it on its side on a workbench capable of withstanding the weight of the Switch. If, for example, you place the Switch on a shaky table or a tilted surface, the Switch might fall and possibly injure someone.
  • Page 18 Safety Information 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.
  • Page 19 Safety Information Do not touch the SFP-T during operation and just after operation stops.  During operation (when a link is established), the temperature of the SFP-T can rise to 65ºC. Do not touch the device while it is operating or just after it stops. Doing so could result in burns.
  • Page 20 Safety Information Attach a blank panel to a slot in which a power supply module for an EPU is not installed.  Be sure to attach a blank panel to any slots for which a power supply module for an EPU is not installed.
  • Page 21 Safety Information Ensure adequate heat dissipation from the Switch by not stacking devices.  Heat dissipates from the top panels of the AX2530S-24T (fanless) model and AX2530S-48T (semi-fanless) model. To ensure adequate heat dissipation, do not stack another device on top of or below the Switch. Doing so could result in Switch malfunction.
  • Page 22 Safety Information 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.
  • Page 23  A label attached to the transceiver or direct attach cable connector indicates that the transceiver or direct attach cable connector is a standard product from ALAXALA or another manufacturer. However, such labels are attached where they do not interfere...
  • Page 24 Safety Information 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.  Keep the nozzle or container of the air duster from coming into contact with the ferrule tip.
  • Page 25: Table Of Contents

    Contents Preface ..............................I Safety Information ..........................1 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.3 Overview of analyzing failures of functionality ..............5 2.
  • Page 26 Contents 3.9 Communication failures in the high-reliability functionality based on a redundant configuration ............................71 3.9.1 Communication failures occurring when uplink redundancy is used ....71 3.9.2 Communication failures occurring when SML is used [OS-L2A] ......72 3.10 SNMP communication failures ..................74 3.10.1 MIBs cannot be obtained from the SNMP manager ..........
  • Page 27: Safety Information

    Overview This chapter provides an overview of failure analysis. 1.1 Overview of analyzing failures 1.2 Overview of analyzing failures of all or part of the Switch 1.3 Overview of analyzing failures of functionality...
  • Page 28: Overview Of Analyzing Failures

    1 Overview 1.1 Overview of analyzing failures Use this manual when there is a problem in an AX2500S 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.
  • Page 29: Overview Of Analyzing Failures Of All Or Part Of The Switch

    1 Overview 1.2 Overview of analyzing failures of all or part of the Switch If a failure occurs during operation and the actual Switch can be looked at, take appropriate action as described in 2.1 Procedure for handling Switch failures to troubleshoot the failure. For a description of the LEDs on the Switch, see the example of the AX2530S-24T switch shown in the following figure and Table 1-1 LED indications, buttons, and connectors.
  • Page 30 1 Overview Name Type Description Details Ethernet port. LED: Blinking green: A frame is being transmitted. Green 1-24 LED: Indicates the Lit in green: A link is established. Green or operating status of Blinking green: A link is established and frames are orange being sent or received 10/100/1000BASE-...
  • Page 31: Overview Of Analyzing Failures Of Functionality

    1 Overview 1.3 Overview of analyzing failures of functionality The following table provides an overview of analyzing functional failures on a Switch. Table 1-2 Status of functional failures and where to find information Category Sub-category Reference Forgotten login password Forgotten login user password 3.1.1 Forgotten login user password 3.1.2 Forgotten device administrator password...
  • Page 32 1 Overview Category Sub-category Reference Directly attached cable 3.4.5 Actions to be taken for direct attach communication failure cable problems [10G models] Link aggregation failure 3.4.6 Communication failures when link aggregation is used Layer 2 network VLAN failure 3.5.1 Layer 2 communication by VLANs is not communication failures possible Spanning Tree failure...
  • Page 33 1 Overview Category Sub-category Reference Traps cannot be received. 3.10.2 Traps cannot be received by the SNMP manager SNMPv3 cannot be used. 3.10.3 When SNMPv3 cannot be used sFlow statistics failures sFlow packets cannot be sent. 3.11.1 sFlow packets cannot be sent to the collector Flow samples cannot be sent.
  • Page 34 1 Overview...
  • Page 35: Troubleshooting Switch Failures

    Troubleshooting Switch Failures This chapter describes how to take actions when a failure occurs on a Switch. 2.1 Procedure for handling Switch faults...
  • Page 36: Procedure For Handling Switch Faults

    2 Troubleshooting Switch Failures 2.1 Procedure for handling Switch faults 2.1.1 Procedure for handling Switch faults Use the procedure described below if a failure occurs on a Switch. Table 2-1 Troubleshooting Switch failures Problem Action  Smoke emanates from the Switch. Immediately take the following actions: ...
  • Page 37 2 Troubleshooting Switch Failures Problem Action failure has occurred on the Switch. In this case, replace the Switch. The red ST1 LED of the Switch blinks. A problem has occurred on the Switch or line. The LINK LED (10GBASE-R port [10G Check the error message and take appropriate show logging models] and 1000BASE-X port) and the...
  • Page 38: Isolating The Cause Of External Power Unit Failures

    2 Troubleshooting Switch Failures 2.1.2 Isolating the cause of external power unit failures Use the procedure described below to isolate the cause of the failure if a failure occurs on an EPU. Table 2-3 Isolating the cause of external power unit failures Problem Action The POWER LED of the EPU is lit in...
  • Page 39: Replacing The Switch And Optional Modules

    2 Troubleshooting Switch Failures Problem Action Failure other than the above Replace the power supply module. 2.1.3 Replacing the Switch and optional modules The procedure to replace the Switch and optional modules is described in the Hardware Instruction Manual. Follow the instructions in the manual. #: Optional modules include the following: Transceiver (SFP, SFP+), direct attach cable, EPU, power supply module, and memory card...
  • Page 40 2 Troubleshooting Switch Failures...
  • Page 41: Troubleshooting Functional Failures During Operation

    Troubleshooting Functional Failures During Operation This chapter describes what actions to take when a problem occurs, such as when a Switch does not operate correctly or cannot communicate. 3.1 Login-related problems 3.2 Operation terminal problems 3.3 Problems occurring while saving files 3.4 Network interface communication failures 3.5 Layer 2 network communication failures 3.6 IPv4 network communication failures...
  • Page 42: Login-Related Problems

    3 Troubleshooting Functional Failures During Operation 3.1 Login-related problems 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: (1) If another user can log in: Ask the user who can log in to execute the password operation command in administrator...
  • Page 43: Operation Terminal Problems

    3 Troubleshooting Functional Failures During Operation 3.2 Operation terminal problems 3.2.1 Information cannot be entered from the console or does not display correctly If a problem occurs during connection to the console, check the problem and take action according to the following table. Table 3-1 Problems occurring during connection to the console and action to take Problem Items to check...
  • Page 44 3 Troubleshooting Functional Failures During Operation Problem Items to check Login is not possible. Perform the following procedure: Make sure that the login prompt is displayed on the screen. If it is not, the Switch is starting up. Wait a while. Take the actions specified in 3.1 Login-related problems.
  • Page 45: Login From A Remote Terminal Is Not Possible

    3 Troubleshooting Functional Failures During Operation 3.2.2 Login from a remote terminal is not possible If a problem occurs during connection to a remote terminal (telnet, FTP, etc.), check the status according to the following table. Table 3-2 Problems occurring during connection to a remote terminal and action to take Problem Action Remote connection is not...
  • Page 46: Login Authentication Using Radius Is Not Possible

    3 Troubleshooting Functional Failures During Operation 3.2.3 Login authentication using RADIUS is not possible If a login cannot be authenticated by using RADIUS, check the following. (1) Communication with the RADIUS server Use the operation command to check if a connection from the Switch to the RADIUS ping server has been established.
  • Page 47: Problems Occurring While Saving Files

    3 Troubleshooting Functional Failures During Operation 3.3 Problems occurring while saving files 3.3.1 Information cannot be saved in the startup configuration file If a problem such as inability to copy information to the startup configuration file by using an operation command occurs, check the status according to the following table. Table 3-3 Problems occurring while copying information to the startup configuration file and action to take Items to check and...
  • Page 48: Copying Or Writing Information To The Ramdisk Is Not Possible

    3 Troubleshooting Functional Failures During Operation Items to check and Items to check commands Try to execute the Perform the following procedure: format mc operation When only the prompt without any message is displayed, memory command. card formatting has terminated normally. Try to write the specified file to the memory card again.
  • Page 49: Update By Using The "Ppupdate" Operation Command Is Not Possible

    3 Troubleshooting Functional Failures During Operation 3.3.4 Update by using the "ppupdate" operation command is not possible Check the following: Check whether the update file specified by using the ppupdate operation command is applicable for the Switch.  Make sure that the update file is appropriate for AX2500S series switches. ...
  • Page 50: Network Interface Communication Failures

    3 Troubleshooting Functional Failures During Operation 3.4 Network interface communication failures 3.4.1 Ethernet port cannot be connected If it is possible that the Ethernet port caused the communication failure, check the port status as described below. (1) Checking the port status Use the show port operation command to check the port status.
  • Page 51: Actions To Be Taken For 10Base-T/100Base-Tx/1000Base-T Problems

    3 Troubleshooting Functional Failures During Operation Port state Cause Action see 3.9.2 Communication failures occurring when SML is used [OS-L2A].  If any of the reasons described above do not apply and you want to activate the port, make sure the cable is connected to the target port, and activate then use the operation command to...
  • Page 52 3 Troubleshooting Functional Failures During Operation Items to check Cause Action Check whether the cables are connected correctly. For cable connections, see the Hardware Instruction Manual. Replace with the connection interface supported by the Switch. For the connection interfaces supported by the Switch, see the Hardware Instruction Manual and the Configuration Guides.
  • Page 53: Actions To Be Taken For 100Base-Fx [24S4X]/1000Base-X Problems

    3 Troubleshooting Functional Failures During Operation Items to check Cause Action show Use the Packets Adjust the jumbo frame settings to those on the remote interfaces operation exceeding the device. command to display the maximum failure statistics, and allowed frame check whether there is a length are count for the item shown...
  • Page 54 3 Troubleshooting Functional Failures During Operation Items to check Cause Action show Use the Line quality on Check the type of the optical fiber. interfaces operation the receiving command to display the side is If an optical attenuator is used, check the attenuation receive-error statistics, degraded.
  • Page 55: Actions To Be Taken For 10Gbase-R Problems [10G Models]

    3 Troubleshooting Functional Failures During Operation Items to check Cause Action If the LINK LED of the The link-up and Check the type of the optical fiber. port is blinking green, link-down of a check the status of the port are Check whether the cables are connected correctly.
  • Page 56: Actions To Be Taken For Direct Attach Cable Problems [10G Models]

    3 Troubleshooting Functional Failures During Operation Items to check Cause Action show Use the Line quality on Check the type of the optical fiber. interfaces operation the receiving command to display the side is If an optical attenuator is used, check the attenuation receive-error statistics, degraded.
  • Page 57: Communication Failures When Link Aggregation Is Used

    3 Troubleshooting Functional Failures During Operation Table 3-10 Failure analysis method for direct attach cable problems [10G models] Items to check Cause Action show Use the Line quality on Check the direct attach cable type. interfaces operation the receiving command to display the side is Check whether the cable is connected correctly (for failure statistics, and...
  • Page 58 3 Troubleshooting Functional Failures During Operation Items to check and commands Action show channel-group Check the status of each port displayed for Status. If all ports of Use the detail operation command to the link aggregation group have gone down, the link aggregation check the operating status of the group also goes down.
  • Page 59: Layer 2 Network Communication Failures

    3 Troubleshooting Functional Failures During Operation 3.5 Layer 2 network communication failures 3.5.1 Layer 2 communication by VLANs is not possible If Layer 2 communication is not possible when VLANs are used, isolate the cause of the problem according to the failure analysis method described below. (1) Checking the VLAN status Execute the show vlan...
  • Page 60 3 Troubleshooting Functional Failures During Operation # show vlan mac-vlan VLAN ID:100 MAC Counts:4 0012.e200.0001 (static) 0012.e200.00:02 (static) 0012.e200.0003 (static) 0012.e200.00:04 (dot1x)  Execute the show vlan mac-vlan operation 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.
  • Page 61 3 Troubleshooting Functional Failures During Operation information about the destination MAC address that caused the communication failure. > show mac-address-table Date 2010/08/09 21:30:08 UTC Aging time : 300 MAC address VLAN Type Port-list 0012.e2cf.fd5d Dot1x 0012.e203.0110 Dynamic 0/15 0012.e203.0132 Dynamic 0/49 0012.e27f.fffa Snoop...
  • Page 62: Failures Occurring When The Spanning Tree Functionality Is Used

    3 Troubleshooting Functional Failures During Operation 3.5.2 Failures occurring when the Spanning Tree functionality is used If Layer 2 communication fails or the operating status of the Spanning Tree Protocol does not conform to the network configuration when the Spanning Tree functionality is used, use the analysis method described below to isolate the cause of the problem.
  • Page 63: Failures Occurring When The Ring Protocol Functionality Is Used

    3 Troubleshooting Functional Failures During Operation Items to check and commands Action show Execute the Check the BPDU sending or receiving counter. spanning-tree statistics For a root port: operation command for the If the BPDU receiving counter has been incremented, go to Spanning Tree Protocol that caused No.
  • Page 64 3 Troubleshooting Functional Failures During Operation Figure 3-2 Analysis flowchart If operation cannot be performed correctly or a ring network failure is detected when the Ring Protocol is used, use the failure analysis method described in the table below to isolate the cause of the problem for the relevant node in the target ring network.
  • Page 65 3 Troubleshooting Functional Failures During Operation Items to check and commands Action show axrp detail Use the If the VLAN ID defined in the network configuration is displayed for Control VLAN ID, go to No. 5. operation command to check the control VLAN ID.
  • Page 66: Failures When The Dhcp Snooping Functionality Is Used

    3 Troubleshooting Functional Failures During Operation Items to check and commands Action show axrp detail Use the If the backup ring ID and the VLAN ID for the multi-fault monitoring operation command to check the functionality defined in the network configuration are displayed for backup ring IDs and VLAN IDs for Backup Ring ID and Control VLAN ID, go to No.
  • Page 67 3 Troubleshooting Functional Failures During Operation (2) When the binding database cannot be saved If the binding database cannot be saved when the DHCP snooping functionality is used, take action according to the tables below. (a) The database cannot be saved to internal flash memory Table 3-15 When the save location for the binding database is internal flash memory Items to check and commands Action...
  • Page 68 3 Troubleshooting Functional Failures During Operation For details about save events and the wait-to-write time, see the Configuration Guide Vol. 2. (b) The database cannot be saved to a memory card Table 3-16 When the save location for the binding database is a memory card Items to check and commands Action show ip dhcp snooping...
  • Page 69 3 Troubleshooting Functional Failures During Operation Items to check and commands Action backup ip dhcp snooping database url mc Execute the operation If the file specified for the command. After the backup process configuration command exists in addition to the file specified for show backup is complete, execute the...
  • Page 70 3 Troubleshooting Functional Failures During Operation Items to check and commands Action show logging It was not able to restore binding database from Use the operation flash. command to check the operation log has been recorded, restoration has failed. for restoration of the binding The binding database saved in internal flash memory might be database.
  • Page 71: Multicast Forwarding By Igmp Snooping Is Not Possible

    3 Troubleshooting Functional Failures During Operation Items to check and commands Action MC file is not reading. is displayed for <reason>, the file Restart the Switch. saved on the memory card or the memory card itself might be corrupted. Clear the IP addresses on the DHCP client terminal. (In Windows, ipconfig /release, in the Command Prompt window, execute...
  • Page 72 3 Troubleshooting Functional Failures During Operation Table 3-19 Failure analysis method for multicast forwarding Items to check and Action commands If multicast forwarding is not Check the following: show performed, use the - Check whether log information about a physical fault has been logging operation command to recorded.
  • Page 73: Multicast Forwarding By Mld Snooping Is Not Possible

    3 Troubleshooting Functional Failures During Operation # If the Switch is the IGMP querier, the same address is displayed for IGMP querying system IP Address . If any other device is the IGMP querier, the address displayed for IGMP querying system is not the same as the address displayed for IP Address 3.5.6 Multicast forwarding by MLD snooping is not possible...
  • Page 74 3 Troubleshooting Functional Failures During Operation Items to check and Action commands Make sure filtering and QoS Certain packets might have been discarded by filtering or packets control are configured correctly. might have been discarded by the QoS control shaper. Make sure that the setting conditions for filtering and QoS control in the configuration are correct, and that the shaper is used appropriately in the system configuration.
  • Page 75: Ipv4 Network Communication Failures

    3 Troubleshooting Functional Failures During Operation 3.6 IPv4 network communication failures 3.6.1 Communication is not possible or is disconnected There are three probable causes of problems that occur during communication on an IPv4 network employing a Switch: A configuration related to IP communication is changed. The network configuration is changed.
  • Page 76 3 Troubleshooting Functional Failures During Operation (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 Message and Log Reference.
  • Page 77 3 Troubleshooting Functional Failures During Operation (4) Identifying the range for a failure (from a customer's terminal) To use the customer's terminal to identify the range for a failure so that you can determine the fault location on the route with a remote device in an environment in which login to the Switch is not possible, do the following: Make sure the customer's terminal has the ping...
  • Page 78: Communication Failures Occurring When The Dhcp Server Is Used

    3 Troubleshooting Functional Failures During Operation  See (8) Checking the filtering and QoS configuration information. (7) Checking the DHCP server configuration information If IP addresses for clients are assigned by the DHCP server functionality on the Switch, the IP addresses might have not been properly assigned. Check whether the setting conditions for the DHCP server functionality in the configuration are correct.
  • Page 79 3 Troubleshooting Functional Failures During Operation to determine the fault location on the route, do the following:  Log in to the Switch.  If there are devices such as an L3 switch between the client and the server, use the ping operation command to check the communication between the L3 switch and the remote device (DHCP client).
  • Page 80: Ipv6 Network Communication Failures

    3 Troubleshooting Functional Failures During Operation 3.7 IPv6 network communication failures 3.7.1 Communication is not possible or a disconnection occurred There are three probable causes of problems that occur during communication on an IPv6 network employing a Switch: A configuration related to IPv6 communication is changed. The network configuration is changed.
  • Page 81 3 Troubleshooting Functional Failures During Operation these messages in the log displayed by the Switch. For details about the contents of the log, see Message and Log Reference. Log in to the Switch. Use the show logging operation command to display the log. Each entry in the log indicates the date and time that a failure occurred.
  • Page 82 3 Troubleshooting Functional Failures During Operation customer's terminal and the remote device is possible. If communication with the remote device cannot be verified by using the ping ipv6 functionality, use the ping ipv6 operation command to check communication with each of the devices up to the remote device, beginning with the device closest to the customer's terminal.
  • Page 83: Layer 2 Authentication Communication Failures

    3 Troubleshooting Functional Failures During Operation 3.8 Layer 2 authentication communication failures 3.8.1 Communication failures occurring when IEEE 802.1X is used If communication 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-21 Failure analysis method for IEEE 802.1X Items to check and commands Action...
  • Page 84 3 Troubleshooting Functional Failures During Operation Items to check and commands Action show dot1x RxTotal [EAPoverRADIUS Execute the If the value displayed for under statistics frames] is 0, packets have not been received from the RADIUS operation command, and make sure packets have been server.
  • Page 85 3 Troubleshooting Functional Failures During Operation Items to check and commands Action  (Reason: Tunnel-Type Attribute is not VLAN(13)) Dynamic allocation has failed because the value of the Tunnel-Type RADIUS attribute for the attribute is not (13). VLAN(13) Tunnel-Type for the attribute for the RADIUS attribute of the RADIUS server.
  • Page 86 3 Troubleshooting Functional Failures During Operation Items to check and commands Action  If authentication linked with the NAP Make sure access permission for the quarantine server is set quarantine system cannot be in the authentication IPv4 access list. performed in port-based ...
  • Page 87: Communication Failures Occurring When Web Authentication Is Used

    3 Troubleshooting Functional Failures During Operation 3.8.2 Communication failures occurring when Web authentication is used If a failure occurs when Web authentication is used, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-23 Failure analysis method for Web authentication Items to check and commands Action...
  • Page 88 3 Troubleshooting Functional Failures During Operation Items to check and commands Action  Check whether the entered If the password does not match, use the web-authentication passwd password is correct. operation command to remove change the password, or use the web-authentication user operation command to delete set web-authentication...
  • Page 89 3 Troubleshooting Functional Failures During Operation Items to check and commands Action show Execute the If the following operation log data is not displayed with operation web-authentication logging log type LOGIN, authentication has failed: command and check for operation  Login succeeded problems.
  • Page 90 3 Troubleshooting Functional Failures During Operation Table 3-24 Checking the configuration of Web authentication Items to check and commands Action Web authentication configuration Make sure the following configuration commands have been set correctly. [Common to Web authentication]  aaa authentication web-authentication default group radius ...
  • Page 91: Communication Failures Occurring When Mac-Based Authentication Is Used

    3 Troubleshooting Functional Failures During Operation 3.8.3 Communication failures occurring when MAC-based authentication is used If communication is not possible when MAC-based authentication is used, isolate the cause of the problem according to the failure analysis method described in the following table.
  • Page 92 3 Troubleshooting Functional Failures During Operation Items to check and commands Action [Dynamic VLAN mode] Correct the configuration so that the VLAN ID specified for Tunnel-Private-Group-ID RADIUS attribute of the attributes for the RADIUS server matches the VLAN ID of the authenticating port ...
  • Page 93 3 Troubleshooting Functional Failures During Operation Items to check and commands Action  If authentication information for the port to which the authentication terminal is connected is not displayed, check whether the authenticating port has been configured mac-authentication port correctly by using the configuration command.
  • Page 94 3 Troubleshooting Functional Failures During Operation Table 3-26 Checking the configuration of MAC-based authentication Items to check and commands Action MAC-based authentication Make sure the following configuration commands have been set configuration correctly. [Common to MAC-based authentication]  aaa authentication mac-authentication default group radius ...
  • Page 95: Communication Failures Occurring When Secure Wake-On-Lan Is Used [Os-L2A]

    3 Troubleshooting Functional Failures During Operation 3.8.4 Communication failures occurring when secure Wake-on-LAN is used [OS-L2A] If a failure occurs when secure Wake-on-LAN is used, isolate the cause of the problem according to the failure analysis method described in the table below. ...
  • Page 96 3 Troubleshooting Functional Failures During Operation Items to check and commands Action show wol-device name Use the Check whether the terminal name, the terminal MAC address, and operation command to check the information for the VLAN to which the terminal belongs are information registered in the WOL correct.
  • Page 97: Communication Failures In The High-Reliability Functionality Based On A Redundant Configuration

    3 Troubleshooting Functional Failures During Operation 3.9 Communication failures in the high-reliability functionality based on a redundant configuration 3.9.1 Communication failures occurring when uplink redundancy is used If switching cannot be performed as expected when uplink redundancy is used, isolate the cause of the problem according to the failure analysis method described in the following table.
  • Page 98: Communication Failures Occurring When Sml Is Used [Os-L2A]

    3 Troubleshooting Functional Failures During Operation Items to check and commands Action  Check whether the sending of flush When not set: control frames is set on the Switch. Wait until aging of the MAC address table on the upstream switch has finished.
  • Page 99 3 Troubleshooting Functional Failures During Operation Items to check and commands Action Check if more than two devices If more than two devices configuring the SML are connected: configuring the SML are connected, Perform the following procedure for recovery: and if the same SML ID is set for the Connect no more than two devices configuring the SML.
  • Page 100: Snmp Communication Failures

    3 Troubleshooting Functional Failures During Operation 3.10 SNMP communication failures 3.10.1 MIBs cannot be obtained from the SNMP manager Make sure the configuration has been registered correctly. When using SNMPv1 or SNMPv2C Execute the show running-config operation command, and check whether the community name and access list have been registered correctly.
  • Page 101: Traps Cannot Be Received By The Snmp Manager

    3 Troubleshooting Functional Failures During Operation 3.10.2 Traps cannot be received by the SNMP manager Make sure the configuration has been registered correctly. When using SNMPv1 or SNMPv2C Execute the show running-config operation command, and check whether the information about the SNMP manager and traps has been registered in the configuration for the Switch.
  • Page 102: Troubleshooting The Sflow Statistics (Flow Statistics) Functionality

    3 Troubleshooting Functional Failures During Operation 3.11 Troubleshooting the sFlow statistics (flow statistics) functionality The following figure shows the workflow for troubleshooting the sFlow statistics functionality on the Switch. Figure 3-7 Workflow for troubleshooting the sFlow statistics functionality 3.11.1 sFlow packets cannot be sent to the collector (1) Checking the route to the collector See 3.6.1 Communication is not possible or is disconnected and 3.7.1 Communication is not possible or a disconnection occurred, and make sure that the network is correctly...
  • Page 103 3 Troubleshooting Functional Failures During Operation Exported sFlow samples: Couldn't export sFlow samples: Overflow time of sFlow queue: 0 seconds sFlow collector data : Collector IP address: 192.168.1.1 UDP: 6343 Source IP address: 192.168.1.100 Send FlowSample UDP packets Send failed packets: Send CounterSample UDP packets: Send failed packets: Collector IP address: 192.168.1.1...
  • Page 104 3 Troubleshooting Functional Failures During Operation Configured sFlow egress ports : ---- Received sFlow samples: Dropped sFlow samples Exported sFlow samples: Couldn't export sFlow samples: > Note: Make sure that the underlined part displays an appropriate sampling interval.  Make sure that sflow forward has been set for the physical port at which the flow statistics are recorded.
  • Page 105: Flow Samples Cannot Be Sent To The Collector

    3 Troubleshooting Functional Failures During Operation Note: Make sure that the underlined parts are active active up If the port status is Down , see 3.6.1 Communication is not possible or is disconnected and 3.7.1 Communication is not possible or a disconnection occurred. (5) Checking the settings on the collector ...
  • Page 106 3 Troubleshooting Functional Failures During Operation (config)#...
  • Page 107: Communication Failures In The Neighboring Device Management Functionality

    3 Troubleshooting Functional Failures During Operation 3.12 Communication failures in the neighboring device management functionality 3.12.1 Neighboring device information cannot be obtained by the LLDP functionality If neighboring device information cannot be obtained correctly by using the LLDP functionality, isolate the cause of the problem according to the failure analysis method described in the following table.
  • Page 108: Ntp Communication Failures

    3 Troubleshooting Functional Failures During Operation 3.13 NTP communication failures 3.13.1 Time information cannot be obtained from the NTP server If time information cannot be obtained from the NTP server, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-31 Failure analysis method for NTP Items to check and commands Action...
  • Page 109: Communication Failures In The Ieee 802.3Ah/Udld Functionality

    3 Troubleshooting Functional Failures During Operation 3.14 Communication failures in the IEEE 802.3ah/UDLD functionality 3.14.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-32 Failure analysis method when the IEEE 802.3ah/UDLD functionality is used Items to check and commands Action...
  • Page 110: Communication Failures In Filtering And Qos Configurations

    3 Troubleshooting Functional Failures During Operation 3.15 Communication failures in filtering and QoS configurations 3.15.1 Checking the filtering and QoS control configuration information If a communication problem occurs on a network employing the Switch, it is possible that certain packets have been discarded either by filtering or by the QoS control shaper. To determine which functionality discarded which packets when packets have been discarded in the Switch by filtering and QoS control, do the following.
  • Page 111: Port Mirroring Failures

    3 Troubleshooting Functional Failures During Operation 3.16 Port mirroring failures 3.16.1 BPDUs are sent from a mirror port To stop sending BPDUs from a mirror port when the port mirroring functionality is enabled, use the spanning-tree bpdufilter configuration command to configure the BPDU filter functionality for the mirror port.
  • Page 112: Power Saving Functionality Failures

    3 Troubleshooting Functional Failures During Operation 3.17 Power saving functionality failures 3.17.1 LED brightness control is disabled If a problem occurs in LED brightness control during a power saving operation, perform the check procedure described in the following table. Table 3-33 Problems in power saving operation and action to take Items to check and commands Action The LEDs do not light when the...
  • Page 113: Power Saving Scheduling Is Disabled

    3 Troubleshooting Functional Failures During Operation Items to check and commands Action show system When the user logs in to the console Use the operation command to check the Brightness mode. (RS-232C), the LEDs do not light information displayed for with the normal brightness ...
  • Page 114 3 Troubleshooting Functional Failures During Operation Items to check and commands Action When the wake-up option is set, Make sure that the wake-up option is configured. linking up the port configured to Make sure that the Switch is connected correctly with the detect link-up fails to cancel sleep port configured to detect link-up.
  • Page 115: Problems Related To The Support Of A Long Life Solution

    3 Troubleshooting Functional Failures During Operation 3.18 Problems related to the support of a long life solution 3.18.1 Dates are not displayed correctly in temperature history information If some of the date and time information is missing from the output of the show environment temperature-logging operation command, the following problems might...
  • Page 116 3 Troubleshooting Functional Failures During Operation...
  • Page 117: Obtaining Failure Information

    Obtaining Failure Information This chapter describes how to obtain failure information. 4.1 Obtaining failure information 4.2 Writing data to a memory card 4.3 Transferring files via FTP...
  • Page 118: Obtaining Failure Information

    4 Obtaining Failure Information 4.1 Obtaining failure information You can use the show tech-support operation command to collect information in a batch operation when a failure has occurred. It might take tens of minutes for the show tech-support operation command to display information on the screen.
  • Page 119: Writing Data To A Memory Card

    4 Obtaining Failure Information 4.2 Writing data to a memory card Failure information copied to the RAMDISK can be written to a memory card. Note, however, that memory cards have a capacity limit. This section describes how to write the Switch information to a memory card via an operation terminal.
  • Page 120: Transferring Files Via Ftp

    4 Obtaining Failure Information 4.3 Transferring files via FTP Failure information copied to the RAMDISK can be transferred to a remote terminal via FTP by logging in to the Switch via FTP. Make sure a VLAN and an IP address are set for the port used for the FTP connection. On your PC, open the command prompt window.
  • Page 121: Line Testing

    Line Testing 5.1 Testing a line...
  • Page 122: Testing A Line

    5 Line Testing 5.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. Figure 5-1 What loops back the test frames for various line test types Table 5-1 Test types and fault locations to be identified Test type What loops back frames...
  • Page 123: Internal Loopback Test

    5 Line Testing 5.1.1 Internal loopback test The internal loopback test, which loops back frames on the Switch, is executed to check for faults. You can execute this test for all line types. The test procedure is described below. Use the inactivate operation command to change the port to be tested into an inactive state.
  • Page 124: Loop Connector Loopback Test

    5 Line Testing 5.1.2 Loop connector loopback test The loop connector loopback test, which loops back frames on the loop connector, is executed to check for any faults. You can execute this test for all line types. The test procedure is described below. Use the inactivate operation command to change the port to be tested into an...
  • Page 125 5 Line Testing Figure 5-3 Overview of a 10BASE-T/100BASE-TX loop connector (3) 10BASE-T/100BASE-TX/1000BASE-T loop connector Create two 6-to-7-cm long twisted pair cables before you start the procedure. Figure 5-4 Twisted pair cable As shown in the following figure, insert the cables into the connector and crimp them with a crimping tool.
  • Page 126 5 Line Testing...
  • Page 127: Appendix

    Appendix A Detailed Display Contents of the show tech-support Command...
  • Page 128: Detailed Display Contents Of The Show Tech-Support Command

    A. Detailed Display Contents of the show tech-support Command A. Detailed Display Contents of the show tech-support Command A.1 Detailed display contents of the show tech-support command The following table lists descriptions of the content that is displayed when protocol parameters are used with the show tech-support operation command.
  • Page 129 A. Detailed Display Contents of the show tech-support Command Command (displayed) Description layer-2 parameter specified specified show power-control schedule Power saving schedule information show mc-file Information on files stored on the memory card show ramdisk-file Information on files stored on the RAMDISK show mc Memory card usage...
  • Page 130 A. Detailed Display Contents of the show tech-support Command Command (displayed) Description layer-2 parameter specified specified show vlan summary VLAN information show vlan detail VLAN details show vlan mac-vlan MAC VLAN information show spanning-tree detail Spanning Tree details show spanning-tree port-count Number of accommodated Spanning Tree Protocols show spanning-tree statistics...
  • Page 131 A. Detailed Display Contents of the show tech-support Command Command (displayed) Description layer-2 parameter specified specified show authentication fail-list Information on terminals that failed to pass Layer 2 authentication show authentication logging Operation log information for all Layer 2 authentication events show dot1x detail IEEE 802.1X authentication status information...
  • Page 132 A. Detailed Display Contents of the show tech-support Command Command (displayed) Description layer-2 parameter specified specified show mac-authentication Operation log information for MAC-based logging authentication show mac-authentication MAC-based authentication statistics statistics show mac-authentication Entries registered or changed in the mac-address edit internal MAC-based authentication DB show mac-authentication Entries registered in the internal...
  • Page 133 A. Detailed Display Contents of the show tech-support Command Command (displayed) Description layer-2 parameter specified specified show efmoam statistics Statistics on the IEEE 802.3ah/OAM functionality show storm-control detail Storm control information show loop-detection Information on the L2 loop detection functionality show loop-detection logging Log information for the L2 loop detection functionality...
  • Page 134 A. Detailed Display Contents of the show tech-support Command Command (displayed) Description layer-2 parameter specified specified show netconf denied-host OAN: Access rejected status information show software-update user OAN: User list information for software updates show on-api webauth-html-file OAN: User list information related to user replacement HTML files for the Web authentication login page...
  • Page 135: Index

    Index detailed display contents of the show tech-support command, 102 actions to be taken for 100BASE-FX [24S4X]/1000BASE-X problems, 27 actions to be taken for Ethernet port cannot be connected, 24 10BASE-T/100BASE-TX/1000BASE-T external power failures problems, 25 isolating the cause, 12 actions to be taken for 10GBASE-R problems [10G models], 29 actions to be taken for direct attach cable...
  • Page 136 Index login authentication using RADIUS is not communication failures, 84 possible, 20 login from a remote terminal is not possible, 19 login-related problems, 16 restoring data by using the restore operation loop connector loopback test, 98 command is not possible, 23 memory card saving or restoring the binding database is not writing data to, 93...

This manual is also suitable for:

Ax2500s

Table of Contents