ALAXALA AX2200S/AX1250S/AX1240S Troubleshooting Guide AX1240S-T001X-70
Relevant products This manual applies to models of the AX2200S series switch, the AX1250S series switch, and the AX1240S series switch.
(Edition 7) Summary of amendments Location and title Changes Failures occurring when the Ring Protocol functionality is used A description of the multi-fault monitoring functionality was added. In addition to the above changes, minor editorial corrections were made. (Edition 6) Summary of amendments Location and title Changes Update by using the ppupdate operation command is not possible A description related to action against failure to update prior to Ver. 2.3.A software was added.
(Edition 3) Summary of amendments Location and title Changes Login-related problems : troubleshooting : login-related problem : login The actions to be taken were changed. Failures occurring when the Ring Protocol functionality is used This subsection was added. In addition to the above changes, minor editorial corrections were made.
Preface Relevant products This manual applies to the models of AX2200S, AX1250S, and AX1240S series switches. The manual describes the functionality of software supported by OS-LT4, OS-LT3, and OS-LT2 software and the optional licenses. 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.
Preface Abbreviations used in the manual AC ACK ADSL ALG ANSI ARP AS AUX BGP BGP4 BGP4+ II Alternating Current ACKnowledge Asymmetric Digital Subscriber Line Application Level Gateway American National Standards Institute Address Resolution Protocol Autonomous System Auxiliary Border Gateway Protocol Border Gateway Protocol - version 4 Multiprotocol Extensions for Border Gateway Protocol - version 4
Preface bit/s BPDU BRI CC CDP CFM CIDR CIR CIST CLNP CLNS CONS CRC CSMA/CD CSNP CST 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 IPv6 IPV6CP IPX ISO ISP IST L2LD LAN LCP LED bits per second (can also appear as bps) Bridge Protocol Data Unit Basic Rate Interface Continuity Check Cisco Discovery Protocol Connectivity Fault Management Classless Inter-Domain Routing Committed Information Rate Comm
Preface LLC LLDP LLQ+3WFQ LSP LSP LSR MA MAC MC MD5 MDI MDI-X MEP MIB MIP MRU MSTI MSTP MTU NAK NAS NAT NCP NDP NET 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 QoS RA RADIUS RDI REJ RFC RIP RIPng RMON RPF RQ IV Logical Link Control Link Layer Discovery Protocol Low Latency Queueing + 3 Weighted Fair Queueing Label Switched Path Link State PDU Label Switched Router Maintenance Association Media Access Control Memory Card Messag
Preface RSTP SA SD SDH SDU SEL SFD SFP SMTP SNAP SNMP SNP SNPA SPF SSAP STP TA TACACS+ TCP/IP TLA ID TLV TOS TPID TTL UDLD UDP ULR UPC UPC-RED VAA VLAN VRRP WAN WDM WFQ WRED WS WWW XFP Rapid Spanning Tree Protocol Source Address Secure Digital Synchronous Digital Hierarchy Service Data Unit NSAP SELector Start Frame Delimiter Small Form factor Pluggable Simple Mail Transfer Protocol Sub-Network Access Protocol Simple Network Management Protocol Sequence Numbers PDU Subnetwork Point of Attachment Shortest
Preface VI
Safety Information Using AX2200S, AX1250S, and AX1240S series switches correctly and safely This manual provides important information intended to ensure safe use of AX2200S, AX1250S, and AX1240S series switches. Please read this manual completely before using the Switches. Keep this manual handy after reading it, so that it is available for later reference. Operate the Switch according to the instructions and procedures provided in this manual.
Safety Information If anything seems wrong, immediately turn off the power. If smoke or an unusual smell is coming from the Switch, or if liquid is spilled into the Switch or a foreign object falls into the Switch, immediately turn off power to the Switch as described below. Continuing operation could result in a fire or electric shock. Actions to take for abnormal conditions Action to take Turn off the Switch and unplug the power cable. Do not allow any foreign objects to get into the Switch.
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.
Safety Information Ground the Switch. Always use a grounded outlet. Failure to do so might not only result in electric shock, but it might also introduce unwanted electrical noise that could cause a Switch failure. Handle power cables carefully. Do not place anything heavy on a power cable. Do not pull, bend, or modify a cable. Doing so could damage the cable, resulting in a fire or electric shock.
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 affixed to a Switch.
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. When installing the Switch in a rack, make sure the Switch in the rack is stably positioned.
Safety Information Use the Switch's power button to turn off the Switch power. 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 metals. 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.
Safety Information Ensure adequate heat dissipation from the Switch by not stacking devices. As the AX2230S-24T, AX1250S-24T2C, and AX1240S-24T2C are fanless models, heat also dissipates from the top panels of these switches. To ensure adequate heat dissipation, do not stack another device on top of or below the Switch. Contact could result in a malfunction. When mounting these switches in a rack, keep a space of 1U or more between them. Do not place the Switch in a high-temperature location.
Safety Information Handle memory cards carefully. When inserting a memory card, do not push the card too strongly or flick it with your finger. When removing a memory card, do not forcibly pull out the card if it is locked. Doing so might damage the connector of the memory card slot. When moving the Switch, remove memory cards. If a card is subjected to excessive force when the switch is moved, the connector of the memory card slot might be damaged.
Safety Information Wear an antistatic wrist strap when carrying or packing a switch. 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 carrying and packing optional modules, handle them carefully. Do not touch a connector when carrying or packing a transceiver or a memory card. Also, when storing a module, use an antistatic bag. Use care when handling an air duster.
Contents Preface .............................................................................................................................................. I Safety Information .............................................................................................................. Safety-1 1. Overview ...................................................................................................................................... 1 1.1 Overview of analyzing failures ...........................
Contents 3.9.2 Traps cannot be received by the SNMP manager ............................................... 68 3.10 Communication failures in the neighboring device management functionality ............... 69 3.10.1 Neighboring device information cannot be obtained by the LLDP functionality 69 3.11 NTP communication failures............................................................................................ 71 3.11.1 Time information cannot be acquired from the NTP server ...........................
1. Overview This chapter provides an overview of failure analysis. 1.1 Overview of analyzing failures 1.2 Overview of failure analysis for the entire Switch or a part of the Switch 1.
1. Overview 1.1 Overview of analyzing failures Use this manual when there is a problem on an AX2200S, AX1250S, or AX1240S series switch. When failure analysis requires looking at the actual Switch, do the analysis according to 1.2 Overview of failure analysis for the entire Switch or a part of the Switch. When failure analysis requires logging in to the Switch, do the analysis according to 1.3 Overview of functional failure analysis.
1. Overview 1.2 Overview of failure analysis for the entire Switch or a 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 AX1240S-24T2C switch shown in the following figure and Table 1-1 LED indications, buttons, and connectors.
1. Overview No. Model name Type Functionality Description 7 LINK LED: Green Indicates the operating status of a 1000BASE-T/1000BASE -X Ethernet port. Green: Initial state after the Switch is turned on or a link is established. Off: If the ST1 LED is green, a link failure has occurred or the port is blocked. 8 T/R LED: Green 9 1-24 LED: Green or orange Indicates the operating status of a 10BASE-T/100BASE-TX Ethernet port. Green: A link has been established.
1. Overview 1.3 Overview of functional failure analysis The following table provides an overview of analyzing functional failures on the Switch. Table 1-2 Status of functional failures and where to find information Category Sub-category See Forgotten login password Forgotten login user password 3.1.1 Forgotten login password Forgotten login user ID 3.1.2 Forgotten login user ID Forgotten device administrator password 3.1.
1. Overview Category Sub-category See 100BASE-FX [AX1250S] /1000BASE-X communication failure 3.4.4 Actions to be taken for 100BASE-FX [AX1250S]/1000BASE-X problems PoE problems [AX2200S] [AX1240S] 3.4.5 Actions to be taken for PoE problems [AX2200S] [AX1240S] Link aggregation failure 3.4.6 Communication failures when link aggregation is used VLAN failure 3.5.1 Layer 2 communication by VLANs is not possible Spanning Tree failure 3.5.
1. Overview Category Sub-category See Traps cannot be received. 3.9.2 Traps cannot be received by the SNMP manager Information about neighboring devices by the LLDP functionality cannot be obtained. -- 3.10.1 Neighboring device information cannot be obtained by the LLDP functionality NTP communication failures -- 3.11 NTP communication failures Communication failures when the IEEE 802.3ah/UDLD functionality is used Port in inactivate status 3.12.1 Port is in inactivate status by the IEEE 802.
1.
2. Troubleshooting Switch Failures This chapter describes how to take actions when a failure occurs on a Switch. 2.
2. Troubleshooting Switch Failures 2.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. Failure description Action 1 Immediately take the following actions: 1. Turn off the Switch. 2. Remove the power cable from the Switch. 3. Replace the Switch. 2 Smoke emanates from the switch. An abnormal odor emanates from the switch. An abnormal sound emanates from the switch.
2. Troubleshooting Switch Failures Table 2-2 Action to take when the Switch stops and the PWR LED turns off No. Failure description Action 1 The power button of the Switch is off. Turn on the Switch. 2 The power cable is disconnected or loose. Perform the following procedure: 1. Turn off the Switch. 2. Connect the power cable correctly. 3. Turn on the Switch.
2.
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 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 3.7 Layer 2 authentication communication failures 3.
3. Troubleshooting Functional Failures During Operation 3.1 Login-related problems 3.1.1 Forgotten login password During operation, if a user forgets his or her password and is unable to log in to the Switch, perform the following procedure: Restart the Switch, and then press CTRL+N three or more times. By doing so, the startup configuration file and the password information are not loaded. When the Switch has restarted, use the password operation command to set a password. Restart the Switch.
3. Troubleshooting Functional Failures During Operation 3.2 Operation terminal problems 3.2.1 Information cannot be entered from the console or does not appear 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 No. Failure description Items to check 1 Nothing is displayed on the screen. Perform the following procedure: 1.
3. Troubleshooting Functional Failures During Operation No. Failure description Items to check 5 Login is not possible. Perform the following procedure: 1. Make sure that the login prompt is displayed on the screen. If it is not, the Switch is starting up. Wait a while. 2. Execute the procedure described in 3.1 Login-related problems. If you are unable to log in, the internal flash memory might be corrupted. Try to execute the format flash operation command.
3. Troubleshooting Functional Failures During Operation No. Problem Action 2 Login is not possible. Perform the following procedure: 1. Make sure that the line vty or ftp-server configuration command has been set. For details, see the Configuration Guides. 2. Make sure that the terminal you are using has an IP address that is permitted in the access list for the configuration command line vty mode.
3. Troubleshooting Functional Failures During Operation set-number-of-RADIUS-servers If the time increases significantly, an application on a remote terminal, such as Telnet, might have terminated due to a timeout. If this happens, change the RADIUS configuration settings or the timeout setting of an application running on a remote terminal. In addition, Telnet or FTP might have failed even when a message indicating successful RADIUS authentication is output to the operation log.
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 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 No.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Items to check 3 Try to execute the format mc operation command. Perform the following procedure: 1. When only the prompt without any message is displayed, memory card formatting has terminated normally. Try to write the specified file to the memory card again. 2. If Can't gain access to MC. is displayed, remove the memory card, and then make sure that no dust is on the memory card or in the slot.
3. Troubleshooting Functional Failures During Operation 3.3.4 Update by using the ppupdate operation command is not possible If update by using the ppupdate operation command is not possible or if another similar problem occurs, check the status according to the following table. Table 3-6 Problems occurring while using the ppupdate configuration command and action to take No. Items to check and commands Items to check 1 Check the response message to the command. 1. 2. 3.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Items to check 2 Try to execute the show critical-logging command. When FROM write fail [cnt=xxxxxxxx,size=xxxxxxxx,err=xxxxxxxx] is obtained, execute the restore operation command again. If an error still occurs, the internal flash memory might be corrupted. Replace the Switch.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Items to check 3 If the hardware revision is shown as a number other than 1 and 9 If no-software is specified for the backup operation command, no-software must be specified for the restore operation command as well. If software for an AX1250S or AX1230S switch is contained in the backup file, Switch information other than the software is restored.
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. The following table describes the actions to be taken for the port status. Table 3-10 Checking the port status and action to take No .
3. Troubleshooting Functional Failures During Operation No . Items to check and commands Action Use the show efmoam operation command to make sure information other than Forced Down or Down is displayed for the target port. Use the show loop-detection operation command to make sure that the port has been released from the blocked state set by the L2 loop detection frame and that Up is displayed.
3. Troubleshooting Functional Failures During Operation No. 2 3 Items to check Cause Action the Cause and Action columns. Link down Replace with the connection interface supported by the Switch. For the connection interfaces supported by the Switch, see the Hardware Instruction Manual and Configuration Guides.
3. Troubleshooting Functional Failures During Operation No. 2 3 4 Items to check Cause Action whether there is a count for the following item for the target line: If there is a count, see the Cause and Action columns. Link down Check whether the cables are connected correctly (for example, check for incomplete insertion). For cable connections, see the Hardware Instruction Manual.
3. Troubleshooting Functional Failures During Operation Isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-13 Failure analysis method for 100BASE-FX [AX1250S] /1000BASE-X problems No . Items to check Cause Action 1 Use the show interfaces operation command to display the failure statistics, and check whether there is a count for the following item for the target line: If there is a count, see the Cause and Action columns.
3. Troubleshooting Functional Failures During Operation No . Items to check Cause Action 4 If automatic switching to the SFP transceiver does not occur when 1000BASE-SX2 is used, check the usage of the RJ45 port and the media-type setting. Both an SFP transceiver and RJ45 cable are inserted when automatic media detection has been set.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 4 Execute the activate power inline operation command, and then use the show power inline operation command to check the information displayed for Status for the target port. Execute the activate power inline operation command, and then use the show power inline operation command to check the information displayed for Status for the target port.
3. Troubleshooting Functional Failures During Operation Table 3-15 Communication failure analysis method when link aggregation is used No. Items to check and commands Action 1 Use the show channel-group detail operation command to check the link aggregation setting that caused the communication failure. Make sure the link aggregation mode is the same as the mode for the remote device. If the modes are different, set the same link aggregation mode that is set for the remote device.
3. Troubleshooting Functional Failures During Operation 3.5 Layer 2 network communication failures 3.5.1 Layer 2 communication by VLANs is not possible If Layer 2 communication is not possible when VLANs are used, isolate the cause of the problem according to the failure analysis method described in the table below. (1) Checking the VLAN status Execute the show vlan or show vlan detail operation command to check the status of the VLAN.
3. Troubleshooting Functional Failures During Operation address set for a VLAN by using the Layer 2 authentication functionality has not been set for another VLAN in the configuration. A MAC address shown with an * (asterisk) indicates that the entry has not been registered in the hardware due to device capacity. # show vlan mac-vlan : VLAN ID:500 MAC Counts:4 0012.e200.aa01 (static) 0012.e200.aa03 (static) VLAN ID:600 MAC Counts:1 * 0012.e200.aa01 (dot1x) 0012.e200.aa02 (static) 0012.e200.
3. Troubleshooting Functional Failures During Operation 0010.c6ce.e1c6 0012.e284.c703 001b.7887.a492 0100.5e00.00fc 1024 1024 1024 1024 MacAuth Dynamic Dynamic Snoop 0/29 0/49-50 0/49-50 0/49-50 > Take one of the actions described below according to the value displayed for Type. When Dynamic is displayed for Type: The MAC address learning information might not have been updated. Use the clear mac-address-table operation command to clear the old information.
3. Troubleshooting Functional Failures During Operation Table 3-16 Failure analysis method for Spanning Tree No. Items to check and commands Action 1 Execute the show spanning-tree operation command for Spanning Tree that caused the failure, and then check the status of the protocol for Spanning Tree. If the displayed status is Enable, go to No. 2.
3. Troubleshooting Functional Failures During Operation 3.5.3 Failures occurring when the Ring Protocol functionality is used This subsection describes failures occurring in the Autonomous Extensible Ring Protocol. The Autonomous Extensible Ring Protocol (abbreviated hereafter to Ring Protocol) is a Layer 2 network redundancy protocol for ring topologies. If communication is not possible when the Ring Protocol is used, use the following analysis flowchart to determine the problem and isolate the cause.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 3 Use the show axrp operation command to check the ring port and its status for each VLAN group. If the information about the port and status defined in the network configuration is displayed for Ring Port and Role/State, go to No. 4. If any other information is displayed, check the configuration. 4 Use the show axrp detail operation command to check the control VLAN ID.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 2 Check the connection between the DHCP server and the DHCP client terminal. Make sure the DHCP server is connected to a trusted port. If the DHCP server is connected to an untrusted port, connect it to a trusted port. Make sure the DHCP client terminal is connected to an untrusted port. If the DHCP client terminal is connected to a trusted port, connect it to an untrusted port.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 3 Check the status of the ST1 LED on the front of the switch, and then use the show logging operation command to check the operation log for saving of the binding database. If the ST1 LED is blinking red and It was not able to store binding database in flash. has been recorded, use the following procedure to change the save location to a memory card (MC). 1.
3. Troubleshooting Functional Failures During Operation No. 3 Items to check and commands Action operation command to check the configuration. If ip dhcp snooping database url mc is not set, set the ip dhcp snooping database url mc configuration command. Use the show logging operation command to check the operation log for saving the binding database. If It was not able to store binding database in mc.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action If Can't execute is displayed, remove the memory card and check the memory card and memory card slot for dust. If there is dust, wipe it off with a dry cloth, and then insert the memory card into the slot again. After inserting the memory card, execute the format mc operation command again. If the same message appears again, the memory card might have been corrupted. Replace it with another memory card.
3. Troubleshooting Functional Failures During Operation No. 2 Items to check and commands Action binding operation command to check the time that the database was saved. If the time displayed for Last succeeded time is too old, continue with No. 3. Use the show running-config operation command to check the configuration. If ip dhcp snooping database url mc is set, continue with No. 3.
3. Troubleshooting Functional Failures During Operation Figure 3-2 Analysis flowchart Table 3-23 Failure analysis method for multicast forwarding No. Items to check and commands Action 1 If multicast forwarding is not performed, use the show logging operation command to check whether a failure has occurred. Check the following: - Check whether log information about a physical fault has been recorded. 2 Make sure filtering and QoS control are configured correctly.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 3 If multicast forwarding is not performed, use the show igmp-snooping operation command to check the IGMP snooping configuration. 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-3 Analysis flowchart Table 3-24 Failure analysis method for multicast forwarding No. Items to check and commands Action 1 If multicast forwarding is not performed, use the show logging operation command to check whether a failure has occurred. Check the following: - Check whether log information about a physical fault has been recorded. 2 Make sure filtering and QoS control are configured correctly.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 3 If multicast forwarding is not performed, use the show mld-snooping operation command to check the MLD snooping configuration. 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.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: 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 (1) Checking the device failure log One probable cause of disabled communication is a line failure (or damage). The following describes the procedure for displaying the messages that indicate a hardware failure. You can find these messages in the device failure log displayed by the Switch. For details about the contents of the device failure log, see the Message Log Reference. 1. Log in to the Switch. 2.
3. Troubleshooting Functional Failures During Operation Switch is not possible, do the following: 1. Make sure the customer's terminal has the ping functionality. 2. Use the ping functionality to check whether communication between the customer's terminal and the remote device is possible. 3.
3. Troubleshooting Functional Failures During Operation 3.7 Layer 2 authentication communication failures 3.7.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-25 Failure analysis method for IEEE802.1X No. Items to check and commands Action 1 Use the show dot1x operation command to check the operating status of IEEE 802.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 4 Execute the show dot1x statistics operation command, and make sure packets have been received from the RADIUS server. If the value displayed for RxTotal under [EAPoverRADIUS frames] is 0, packets have not been received from the RADIUS server. Check the following: If the RADIUS server is associated with the remote network, make sure a route to the remote network exists.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 7 Execute the show dot1x logging operation command, and check whether dynamic allocation in VLAN-based authentication (dynamic) failed. If Failed to assign VLAN (Reason:xxxxx) is displayed, check the information displayed for (Reason:xxxxx) and take action as described below.
3. Troubleshooting Functional Failures During Operation No. 8 Items to check and commands If authentication linked with the NAP quarantine system cannot be performed in port-based authentication (static) mode, check the setting of the authentication IPv4 access list.
3. Troubleshooting Functional Failures During Operation as a VLAN after RADIUS authentication. Specify a unique VLAN name. If the same VLAN name is used for two or more VLANs, the smallest VLAN ID is allocated as the post-authentication VLAN in RADIUS authentication mode. Do not specify a number at the beginning of the VLAN name. A number at the beginning will be recognized as the VLAN ID, which might result in an authentication failure.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 4 Check the setting of the authentication IPv4 access list. [Fixed VLAN mode] [Dynamic VLAN mode] If an unauthenticated terminal sends certain types of packets to destinations outside the Switch, make sure an authentication IPv4 access list is set.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action [Legacy mode] Make sure the VLAN ID of the RADIUS server matches the VLAN ID specified in the web-authentication vlan configuration command and in the switchport mac vlan command for the port connected to the terminal to be authenticated. If a VLAN name has been registered on the RADIUS server, make sure the target VLAN name matches the VLAN name #2 specified in the name configuration command.
3. Troubleshooting Functional Failures During Operation #2 Be careful of the following when using a VLAN name configured using the name configuration command as a VLAN after RADIUS authentication. Specify a unique VLAN name. If the same VLAN name is used for two or more VLANs, the smallest VLAN ID is allocated as the post-authentication VLAN in RADIUS authentication mode. Do not specify a number at the beginning of the VLAN name.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 4 Check the filtering configuration. Certain packets might have been discarded by filtering or packets might have been discarded by the shaper of QoS control. 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. For details about the procedure, see 3.13.
3. Troubleshooting Functional Failures During Operation (c) Identifying the range for a failure (from the Switch) If a failure has not occurred on the Switch, a failure might have occurred somewhere on the route between the Switch and the remote device. To identify the range for a failure in order to determine the fault location on the route, do the following: Log in to the Switch.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action [Fixed VLAN mode] If the mac-authentication vlan-check configuration command is set, make sure the MAC address and the VLAN ID to which the terminal to be authenticated belongs are registered. [Dynamic VLAN mode] [Legacy mode] Make sure the MAC address and the post-authentication VLAN ID are registered. 3 Check whether the MAC address is registered on the RADIUS server.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 4 Use the show mac-authentication statistics operation command to check the communication status with the RADIUS server.
3. Troubleshooting Functional Failures During Operation #1 If the switchport mac vlan configuration command has not been set, check whether the VLAN ID for the RADIUS server has been set using the vlan configuration command with mac-based specified. #2 Be careful of the following when using a VLAN name configured using the name configuration command as a VLAN after RADIUS authentication. Specify a unique VLAN name.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 2 VLAN interface setting [Fixed VLAN mode] Make sure the IP address for the VLAN interface is set correctly. [Dynamic VLAN mode] [Legacy mode] Make sure the IP addresses for the following VLAN interfaces are set correctly: Pre-authentication VLAN Post-authentication VLAN 3 Check the filtering configuration.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 2 Make sure the URL of the user authentication page is correct. If the URL of the user authentication page is not correct, use the correct URL. For the IP address of the URL, use the IP address of the VLAN used for secure Wake-on-LAN. 3 Use the show wol-authenticaion user operation command to check whether user information is registered.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 8 If the startup check is enabled, check the IP address information. 9 Use the show running-config operation command to check the VLAN interface configuration. For a DHCP client: Make sure that dhcp is registered and that DHCP snooping is configured for the Switch. For a fixed-IP address terminal: Make sure the IP address of the terminal is registered.
3. Troubleshooting Functional Failures During Operation 3.8 Communication failures in the high-reliability functionality based on a redundant configuration 3.8.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. Table 3-32 Failure analysis method for uplink redundancy No.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 7 Check whether the sending of flush control frames is set on the Switch. When not set: Wait until aging of the MAC address table on the upstream switch has finished. When set: Check the configuration of the port and the sending VLAN for which sending of flush control frames has been set. If the configuration is not correct, set the configuration again.
3. Troubleshooting Functional Failures During Operation 3.9 SNMP communication failures 3.9.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. If IP addresses for the SNMP manager to which access is permitted are not restricted, an access list need not be set.
3. Troubleshooting Functional Failures During Operation 3.10 Communication failures in the neighboring device management functionality 3.10.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-33 Failure analysis method when the LLDP functionality is used No.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 5 Execute the show lldp operation command, and check the number of neighboring device information items on the port to which the neighboring device is connected. 70 If 0 is displayed for Neighbor Counts, check No. 1 through No. 5 on the neighboring device. If the number of neighboring device information items is also 0 on the neighboring device, the connection between the devices might be incorrect.
3. Troubleshooting Functional Failures During Operation 3.11 NTP communication failures 3.11.1 Time information cannot be acquired from the NTP server If time information cannot be acquired from the NTP server, isolate the cause of the problem according to the failure analysis method described in the following table. Table 3-34 NTP failure analysis method No. Items to check and commands Action 1 Use the show clock operation command to make sure that the time zone is set.
3. Troubleshooting Functional Failures During Operation 3.12 Communication failures in the IEEE 802.3ah/UDLD functionality 3.12.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-35 Failure analysis method when the IEEE 802.3ah/UDLD functionality is used No.
3. Troubleshooting Functional Failures During Operation 3.13 Communication failures in filtering and QoS configurations 3.13.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 shaper of QoS control.
3. Troubleshooting Functional Failures During Operation 3.14 Port mirroring failures 3.14.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 filtering functionality for the mirror port.
3. Troubleshooting Functional Failures During Operation 3.15 Power saving functionality failures 3.15.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-36 Problems in power saving operation and action to take No. Items to check and commands Action 1 The LEDs do not light when the status of the ports changes to link up. Perform the following procedure: 1.
3. Troubleshooting Functional Failures During Operation No. Items to check and commands Action 4 When the user logs in to the console (RS-232C), the LEDs do not light with normal brightness (automatic operation is disabled). Use the show system operation command to check the information displayed for Brightness mode. normal displayed: LED operation is set to normal brightness. Check the setting of the system port-led trigger configuration command.
3. Troubleshooting Functional Failures During Operation 3.16 Failures occurring when long-life solution is supported 3.16.1 Correct date not displayed in temperature history If the execution result of the show environment temperature-logging operation command does not contain the collection date or time, one of the following events may have occurred. 1.
3.
4. Obtaining Failure Information This chapter mainly describes how to obtain failure information. 4.1 Obtaining failure information 4.2 Writing data to a memory card 4.
4. Obtaining Failure Information 4.1 Obtaining failure information You can use the show tech-support operation command to collect information when a failure has occurred in a batch operation. It might take tens of minutes for the show tech-support command to display information. As described below, we recommend that you either save the information on the RAMDISK and then write the information to a memory card or transfer the information via FTP.
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 by using an operation terminal. Figure 4-2 Writing information to a memory card Insert a memory card into the Switch to which information is to be written.
4. Obtaining Failure Information 4.3 Transferring files via FTP Failure information copied from 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. (For a standard Windows XP PC, click the Start menu, choose All Programs and then Accessories, and then click Command Prompt.
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 table below lists 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.
A. Detailed display contents of the show tech-support command No.
A. Detailed display contents of the show tech-support command No.
A. Detailed display contents of the show tech-support command No.
A. Detailed display contents of the show tech-support command No.
A.
Index troubleshooting, 37 1 1000BASE-T troubleshooting, 26 1000BASE-X troubleshooting, 27 100BASE-FX [AX1250S] troubleshooting, 27 100BASE-TX troubleshooting, 25, 26 10BASE-T troubleshooting, 25, 26 A administrator mode forgotten password, 14 B binding database troubleshooting, 23 BPDUs sent from mirror port, 74 C cannot be entered, 18 card writing data to memory card, 81 commands cannot be entered, 18 communication failures in filtering and QoS configurations, 73 in high-reliability functionality based on
Index forgotten user ID, 14 from remote terminal not possible, 16 troubleshooting, 14 login authentication using RADIUS not possible, 17 long-life solution failure information, 77 M MAC-based authentication troubleshooting communication failures, 59 memory card cannot copy or write information, 19 writing data to, 81 MIBs cannot be obtained from SNMP manager, 68 mirroring port mirroring failures, 74 MLD snooping multicast forwarding, 44 multicast forwarding by IGMP snooping troubleshooting, 42 multicast for
Index communication failures when link aggregation used, 30 Ethernet port, 24 functional failures during operation, 13 how to get failure information, 79 IPv4 network communication failures, 47 Layer 2 authentication communication failures, 50 Layer 2 communication by VLANs, 32 Layer 2 network communication failures, 32 login, 14 multicast forwarding by IGMP snooping, 42 multicast forwarding by MLD snooping, 44 network interface communication failures, 24 NTP communication failures, 71 operation terminal/co
