Alaxala AX2400S series Průvodce řešením problémů

AX6700S/AX6600S/AX6300S/AX3800S/AX3600S/AX2400STroubleshooting GuideAX36S-T001X-E0

iiReading sequence of the manualsThe following shows the manuals you need to consult according to your requirements determined from the following work

3. Troubleshooting Functional Failures During Operation30Default restartPush and hold the RESET button for at least five seconds.Take care when perfor

3. Troubleshooting Functional Failures During Operation313.4 Stack configuration problems3.4.1 Stack configuration is not possibleIf you cannot config

3. Troubleshooting Functional Failures During Operation323.4.2 Stack configuration cannot be editedIf you can make a stack configuration but cannot ed

3. Troubleshooting Functional Failures During Operation333.5 Network interface communication failures3.5.1 Ethernet port cannot be connectedIf it is p

3. Troubleshooting Functional Failures During Operation34For details about the log, see the manual Message and Log Reference.2. Isolating the cause of

3. Troubleshooting Functional Failures During Operation35(3) Checking statisticsYou can use the show port statistics command to check the number of se

3. Troubleshooting Functional Failures During Operation363.5.3 Actions to be taken for 10BASE-T/100BASE-TX/1000BASE-T problemsIf a 10BASE-T/100BASE-TX

3. Troubleshooting Functional Failures During Operation37Table 3-10: Failure analysis method for 10BASE-T/100BASE-TX/1000BASE-T problemsNo. Items to c

3. Troubleshooting Functional Failures During Operation383.5.4 Actions to be taken for 100BASE-FX/1000BASE-X problemsIf a 100BASE-FX/1000BASE-X proble

3. Troubleshooting Functional Failures During Operation391. Checking the logFor details about the log, see the manual Message and Log Reference.2. Iso

iiiAX3800S and AX3650S series switches

3. Troubleshooting Functional Failures During Operation40Check the cable length. For the cable length, see the Hardware Instruction Manual.Check wheth

3. Troubleshooting Functional Failures During Operation413.5.5 Actions to be taken for 10GBASE-R/40GBASE-R problemsIf a 10GBASE-R/40GBASE-R problem oc

3. Troubleshooting Functional Failures During Operation42Check whether the cables are connected correctly (for example, check for incomplete insertion

3. Troubleshooting Functional Failures During Operation433.5.6 Actions to be taken for PoE problemsIf a problem such as a disabled power supply unit o

3. Troubleshooting Functional Failures During Operation44Table 3-13: Communication failure analysis method when PoE is used3.5.7 Communication failure

3. Troubleshooting Functional Failures During Operation45• Port DownThe status of the port is link down. For details, see 3.5 Network interface commun

3. Troubleshooting Functional Failures During Operation463.6 Layer 2 network communication failures3.6.1 Layer 2 communication by VLANs is not possibl

3. Troubleshooting Functional Failures During Operation47Execute the show vlan mac-vlan command and make sure the MAC address set for a VLAN by using

3. Troubleshooting Functional Failures During Operation48port for the transfer.When Snoop is displayed for Type:See 3.6.4 Multicast forwarding by IGMP

3. Troubleshooting Functional Failures During Operation49in the configuration are correct, and that bandwidth monitoring, drop control, or the shaper

ivAX3640S and AX3630S series switches

3. Troubleshooting Functional Failures During Operation503.6.3 Failures occurring when the Ring Protocol functionality is usedThis subsection describe

3. Troubleshooting Functional Failures During Operation51Table 3-16: Failure analysis method for the Ring ProtocolNo. Items to check and commandsActio

3. Troubleshooting Functional Failures During Operation523.6.4 Multicast forwarding by IGMP snooping is not possibleIf multicast forwarding is not pos

3. Troubleshooting Functional Failures During Operation53Figure 3-4: Analysis flowchartTable 3-17: Failure analysis method for multicast forwardingNo.

3. Troubleshooting Functional Failures During Operation543 Make sure the settings for using IPv4 multicast are correct.Check the following:• For AX380

3. Troubleshooting Functional Failures During Operation55# If the Switch is the IGMP querier, the same address is displayed for IGMP querying system a

3. Troubleshooting Functional Failures During Operation56Figure 3-5: Analysis flowchartTable 3-18: Failure analysis method for multicast forwardingNo.

3. Troubleshooting Functional Failures During Operation573 Make sure the settings for using IPv6 multicast are correct.Check the following:• For AX380

3. Troubleshooting Functional Failures During Operation58#: If the Switch is the MLD querier, the same address is displayed for MLD querying system an

3. Troubleshooting Functional Failures During Operation593.7 IPv4 network communication failures3.7.1 Communication is not possible or is disconnected

vAX2400S series switches

3. Troubleshooting Functional Failures During Operation60Figure 3-6: Failure analysis procedure when IPv4 communication is not possible(1) Checking th

3. Troubleshooting Functional Failures During Operation615. If a log entry was not displayed for the date and time when communication was disabled, se

3. Troubleshooting Functional Failures During Operation62device is impossible, the address might not have been resolved by ARP. To check the status of

3. Troubleshooting Functional Failures During Operation63configuration. For details about the procedure, see 3.25.1 Checking the filters and QoS confi

3. Troubleshooting Functional Failures During Operation64Figure 3-7: Failure analysis procedure on DHCP and BOOTP relays(a) Checking the log and inter

3. Troubleshooting Functional Failures During Operation651. Log in to the Switch.2. Use the ping command to check the communication with the two remot

3. Troubleshooting Functional Failures During Operation663. If the routing information obtained by the Switch does not contain the routing information

3. Troubleshooting Functional Failures During Operation672. The network configuration is changed.3. The DHCP server fails.First, check for cause 1. De

3. Troubleshooting Functional Failures During Operation684. Check the settings of the device used as the DHCP relay agent. If the Switch is used as th

3. Troubleshooting Functional Failures During Operation693.7.3 Dynamic DNS link does not work in the DHCP functionality(1) Communication problems on t

viAbbreviations used in the manual AC Alternating CurrentACK ACKnowledgeADSL Asymmetric Digital Subscriber LineALG App

3. Troubleshooting Functional Failures During Operation702. Make sure that the key information and the authentication key specified on the DNS server

3. Troubleshooting Functional Failures During Operation71(f) Checking the filters and QoS configuration informationOnly certain packets might have bee

3. Troubleshooting Functional Failures During Operation723.8 IPv4 unicast routing communication failures3.8.1 No RIP routing information existsIf RIP

3. Troubleshooting Functional Failures During Operation733.8.3 No BGP4 routing information existsIf BGP4 routing information cannot be found in the ro

3. Troubleshooting Functional Failures During Operation743.8.4 IPv4 routing information cannot be found in VRFIf the routing information of each proto

3. Troubleshooting Functional Failures During Operation753.9 Communication failures in the IPv4 multicast routing functionalityThis section describes

3. Troubleshooting Functional Failures During Operation763 Make sure that PIM-SM is running on one or more interfaces.show ip pim interfaceIf PIM-SM i

3. Troubleshooting Functional Failures During Operation77(2) Items to check for BSRThe following table shows the items to check when the Switch is use

3. Troubleshooting Functional Failures During Operation78(4) Items to check for last-hop-routerThe following table shows the items to check when the S

3. Troubleshooting Functional Failures During Operation79Table 3-27: Items to check for first-hop-router3.9.2 Multicast data is forwarded twice in the

viiIPv6 Internet Protocol version 6IPV6CP IP Version 6 Control Protocol IPX Internetwork Packet ExchangeISO International

3. Troubleshooting Functional Failures During Operation80Notes:•first-hop-router: The router that is connected directly to the multicast sender•last-h

3. Troubleshooting Functional Failures During Operation81(2) Items to check for last-hop-routerThe following table shows the items to check when the S

3. Troubleshooting Functional Failures During Operation82(3) Items to check for first-hop-routerThe following table shows the items to check when the

3. Troubleshooting Functional Failures During Operation83Table 3-32: Items to check when data continues to be forwarded twice3.9.5 IPv4 multicast comm

3. Troubleshooting Functional Failures During Operation843.9.6 Problems that occur during IPv4 multicast communication in the extranetTo resolve probl

3. Troubleshooting Functional Failures During Operation85Figure 3-12: Example of an IPv4 PIM-DM networkNotes:•first-hop-router: The router that is con

3. Troubleshooting Functional Failures During Operation86(2) Items to check for last-hop-routerThe following table shows the items to check when the S

3. Troubleshooting Functional Failures During Operation87IPv4 PIM-DM network configuration.Table 3-37: Items to check for first-hop-router3.9.8 Multic

3. Troubleshooting Functional Failures During Operation883.10 IPv6 network communication failures3.10.1 Communication is not possible or is disconnect

3. Troubleshooting Functional Failures During Operation89For details about the contents of the log, see the manual Message and Log Reference.1. Log in

viiiRA Router AdvertisementRADIUS Remote Authentication Dial In User ServiceRDI Remote Defect IndicationREJ REJect RFC

3. Troubleshooting Functional Failures During Operation903. If communication with the remote device cannot be verified by using the ping ipv6 function

3. Troubleshooting Functional Failures During Operation91possible, address information might not be correctly distributed by RA. Therefore, check whet

3. Troubleshooting Functional Failures During Operation92Figure 3-14: Failure analysis procedure on IPv6 DHCP relays(1) Checking the log and interface

3. Troubleshooting Functional Failures During Operation931. Log in to the Switch.2. Use the show ipv6 neighbors command to check the status of address

3. Troubleshooting Functional Failures During Operation94prefix or address to the target client is set by the ipv6 dhcp relay destination configuratio

3. Troubleshooting Functional Failures During Operation95(b) Checking the status of the IPv6 DHCP server on the Switch1. Checking whether the IPv6 DHC

3. Troubleshooting Functional Failures During Operation96!(config)#(d) Duplicate assignment to a client1. Checking the binding informationUse the show

3. Troubleshooting Functional Failures During Operation971. The configuration has been set but not distributed.2. An operation or event has occurred t

3. Troubleshooting Functional Failures During Operation98Destination Next Hop Interface Metric Protocol Age3ffe:1234:5678::/

3. Troubleshooting Functional Failures During Operation993.11 IPv6 unicast routing communication failures3.11.1 RIPng routing information cannot be fo

ixcurrent vendor, or a switch from another vendor. The context decides the meaning.Conventions: KB, MB, GB, and TBThis manual uses the following conve

3. Troubleshooting Functional Failures During Operation1003.11.3 No BGP4+ routing information existsIf BGP4+ routing information cannot be found in th

3. Troubleshooting Functional Failures During Operation1013.11.4 No IPv6 routing information exists in the VRFIf routing information for each protocol

3. Troubleshooting Functional Failures During Operation1023.12 Communication failures in the IPv6 multicast routing functionalityThis section describe

3. Troubleshooting Functional Failures During Operation1034 Check whether MLD snooping is set for the interface on which PIM runs.show mld-snoopingIf

3. Troubleshooting Functional Failures During Operation104(2) Items to check for BSRThe following table shows the items to check when the Switch is us

3. Troubleshooting Functional Failures During Operation105(4) Items to check for last-hop-routerThe following table shows the items to check when the

3. Troubleshooting Functional Failures During Operation1063.12.2 Multicast data is forwarded twice in the IPv6 PIM-SM networkIf multicast data is forw

3. Troubleshooting Functional Failures During Operation107network configuration.Table 3-51: Items checked in commonNo. Items to check and commands Act

3. Troubleshooting Functional Failures During Operation108(2) Items to check for last-hop-routerThe following table shows the items to check when the

3. Troubleshooting Functional Failures During Operation109(3) Items to check for first-hop-routerThe following table shows the items to check when the

3. Troubleshooting Functional Failures During Operation110Table 3-54: Items to check when data continues to be forwarded twice3.12.5 IPv6 multicast co

3. Troubleshooting Functional Failures During Operation111multicast communication is possible in each VRF. After that, check the following.Table 3-56:

3. Troubleshooting Functional Failures During Operation1123.13 Layer 2 authentication communication failures3.13.1 Communication failures occurring wh

3. Troubleshooting Functional Failures During Operation1136 Execute the show dot1x logging command, and check whether authentication failed.• If New S

3. Troubleshooting Functional Failures During Operation114For AX3800S, AX3600S, or AX2400S series switches, if communication is not possible on a port

3. Troubleshooting Functional Failures During Operation115failures.Table 3-58: Communication failure analysis method for IEEE 802.1X3.13.2 Communicati

3. Troubleshooting Functional Failures During Operation1163 Make sure that the Web server is running. • Execute the following command to check whether

3. Troubleshooting Functional Failures During Operation1177Use the show web-authentication statistics command to check the communication status with t

3. Troubleshooting Functional Failures During Operation118Check the following for the configuration related to Web authentication.13 Check whether aut

3. Troubleshooting Functional Failures During Operation119Table 3-60: Checking the configuration of Web authenticationNo. Items to check Action1 Check

xiContentsPreface iSafety Information [AX6700S] xvSafety Information [AX6600S] xxviiSafety Information [AX6300S] xxxixSafety Information [AX3800S]

3. Troubleshooting Functional Failures During Operation120Check the following for the accounting of Web authentication.Table 3-61: Checking the accoun

3. Troubleshooting Functional Failures During Operation121Table 3-62: Failure analysis method for MAC-based authenticationNo. Items to check and comma

3. Troubleshooting Functional Failures During Operation122Check the following for the configuration related to MAC-based authentication.Table 3-63: Ch

3. Troubleshooting Functional Failures During Operation123Check the following for the accounting of MAC-based authentication.Table 3-64: Checking the

3. Troubleshooting Functional Failures During Operation1243 Execute the show fense server command to check the operating status of the authentication

3. Troubleshooting Functional Failures During Operation125Check the following for the configuration related to the authentication VLAN.Table 3-66: Che

3. Troubleshooting Functional Failures During Operation1264 Check the filtering configuration. Make sure that the filters are correctly set between th

3. Troubleshooting Functional Failures During Operation1273.14 Communication failures in the high-reliability functionality3.14.1 GSRP communication f

3. Troubleshooting Functional Failures During Operation128Table 3-68: Failure analysis method when state switching fails in a GSRP configurationIn a G

3. Troubleshooting Functional Failures During Operation1293.14.2 Communication is not possible with the VRRP configuration of IPv4 networksIf communic

 Relevant productsThis manual applies to the models in the AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, and AX2400S series of switches. Export

xii3.5.6 Actions to be taken for PoE problems ... 433.5.7 Communication failure

3. Troubleshooting Functional Failures During Operation130If VLANs and VRIDs for the primary virtual router are the same among devices that make up th

3. Troubleshooting Functional Failures During Operation1313.14.3 Communication is not possible with the VRRP configuration of IPv6 networksIf communic

3. Troubleshooting Functional Failures During Operation132Table 3-71: Failure analysis method for VRRPNo. Items to check and commands Action1 On the S

3. Troubleshooting Functional Failures During Operation1337 Execute the show vrrpstatus command with the statistics parameter, and check the reception

3. Troubleshooting Functional Failures During Operation1343.14.4 Communication is not possible with uplink redundancyIf communication is not possible

3. Troubleshooting Functional Failures During Operation135Table 3-72: Failure analysis method for uplink redundancyNo. Items to check and commands Act

3. Troubleshooting Functional Failures During Operation1363.15 SNMP communication failures3.15.1 MIBs cannot be obtained from the SNMP managerMake sur

3. Troubleshooting Functional Failures During Operation137When using SNMPv3Execute the show snmp-server configuration command, and check whether the i

3. Troubleshooting Functional Failures During Operation1383.16 Troubleshooting the sFlow statistics (flow statistics) functionalityThe following figur

3. Troubleshooting Functional Failures During Operation139 Send CounterSample UDP packets: 621 Send failed packets: 0> Note: Make sure that

xiii3.16.1 sFlow packets cannot be sent to the collector ...1383.16.2 Flow samples cannot be s

3. Troubleshooting Functional Failures During Operation140 switchport mode access sflow forward ingress <-- sflow forward must be set.!(conf

3. Troubleshooting Functional Failures During Operation141(1) Checking whether packets are forwardedExecute the show interfaces command, and check whe

3. Troubleshooting Functional Failures During Operation1423.17 Communication failures in the neighboring device management functionality3.17.1 Neighbo

3. Troubleshooting Functional Failures During Operation143Table 3-74: Failure analysis method when the OADP functionality is usedNo. Items to check an

3. Troubleshooting Functional Failures During Operation1443.18 NTP communication failures3.18.1 The Switch cannot be synchronized by using NTPIf the s

3. Troubleshooting Functional Failures During Operation1453.19 Communication failures in the IEEE 802.3ah/UDLD functionality3.19.1 Port is in inactiva

3. Troubleshooting Functional Failures During Operation1463.20 Problems due to the redundant configuration of the BCU, CSU, or MSU3.20.1 Active-standb

3. Troubleshooting Functional Failures During Operation1473.21 Problems due to the redundant configuration of the BSU3.21.1 BSU switchover is not poss

3. Troubleshooting Functional Failures During Operation1484notconnect The target BSU is not implemented. Make sure that as many BSU boards as the numb

3. Troubleshooting Functional Failures During Operation1493.22 Problems due to the redundant configuration of the NIF3.22.1 The standby NIF cannot be

xiv5.4 Collecting information and transferring files by using the "ftp" command on a remote terminal  ...

3. Troubleshooting Functional Failures During Operation1503.23 Power saving-related problems3.23.1 Scheduling is disabledIf scheduling is disabled, pe

3. Troubleshooting Functional Failures During Operation1513.24 Packet congestion in CPU processing does not recoverThis section describes how to take

3. Troubleshooting Functional Failures During Operation152If the packet type is arp, a large number of ARP packets have been received. In this case, a

3. Troubleshooting Functional Failures During Operation1533.25 Communication failures in filters and QoS configurations3.25.1 Checking the filters and

3. Troubleshooting Functional Failures During Operation154discard_pkt statistics item displayed for the port input and output queues of the input and

3. Troubleshooting Functional Failures During Operation1553.26 Access list logging problems3.26.1 Actions to be taken when access list logs are not ou

3. Troubleshooting Functional Failures During Operation1563.27 DHCP snooping problems3.27.1 Problems related to DHCPIf DHCP cannot distribute IP addre

3. Troubleshooting Functional Failures During Operation1573.27.2 Problems related to saving the binding databaseIf binding information cannot be inher

3. Troubleshooting Functional Failures During Operation1583.27.3 Problems related to ARPIf ARP packets are discarded, IPv4 communication is not possib

3. Troubleshooting Functional Failures During Operation159If there is no problem, go to No. 2.2 Check whether the ip verify source configuration comma

xvSafety Information [AX6700S]Using AX6700S series switches correctly and safely• This guide provides important information for ensuring safe use of A

3. Troubleshooting Functional Failures During Operation1603.28 Policy-based routing problems3.28.1 Actions to take when packets are not forwarded in p

3. Troubleshooting Functional Failures During Operation161#1If you execute the dump bsu command, do not execute any more commands until a log entry is

3. Troubleshooting Functional Failures During Operation162#The second time you execute the dump policy command, the memory dump file you collected the

3. Troubleshooting Functional Failures During Operation163target.3. Due to network congestion, communication with the polling monitoring track target

3. Troubleshooting Functional Failures During Operation164If the track operating status is Init, the track is stopped because it is immediately after

3. Troubleshooting Functional Failures During Operation1653.29 Policy-based switching problems3.29.1 Actions to be taken when packets are not forwarde

3. Troubleshooting Functional Failures During Operation166#1If you execute the dump bsu command, do not execute any more commands until a log entry is

167Chapter4. Troubleshooting Communication Failures Due to a Resource ShortageThis chapter describes communication failures due to a resource shortage

4. Troubleshooting Communication Failures Due to a Resource Shortage1684.1 MAC address table resource shortage4.1.1 Checking the MAC address table res

4. Troubleshooting Communication Failures Due to a Resource Shortage169#: This message might be output with log message No. 1 in the above table.If an

xviIf 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 t

4. Troubleshooting Communication Failures Due to a Resource Shortage170#1: For details, see the manual Operation Command Reference.#2: For details, se

4. Troubleshooting Communication Failures Due to a Resource Shortage1714.2 When a VLAN identification table resource shortage occurs4.2.1 Checking the

4. Troubleshooting Communication Failures Due to a Resource Shortage172If any of these log messages are output, you cannot set up any additional funct

4. Troubleshooting Communication Failures Due to a Resource Shortage1734.3 When a resource shortage occurs in shared memory4.3.1 Checking the resource

175Chapter5. Obtaining Failure InformationThis chapter mainly describes how to obtain failure information.5.1 Collecting maintenance information5.2 Tr

5. Obtaining Failure Information1765.1 Collecting maintenance informationWhen a fault occurs with the switch during operation, log and dump informatio

5. Obtaining Failure Information177(2) Maintenance information for AX3800S, AX3600S, and AX2400S series switchesThe following table lists the maintena

5. Obtaining Failure Information1785.1.2 Collecting failure information by using the "dump" commandIn the AX6700S, AX6600S, and AX6300S seri

5. Obtaining Failure Information1791. In the active system, execute the dump psp command for the PSP in the active system.2. In the active system, exe

xviiswitch without grounding could result in electric shock or failures due to electrical noise.• When the Switch is connected to a DC power supply un

5. Obtaining Failure Information180of NIF number 1 when the BSUs are installed on the BSU numbers 1 and 2 in a redundant BCU environment.1. Log in to

5. Obtaining Failure Information18111/01 18:18:42 E3 CSU 25070700 2301:000000000000 PSP online dump command executed.4. After the above log informatio

5. Obtaining Failure Information1822. In the active BCU, execute the dump nif command for all the ports that have failed.Example:The following procedu

5. Obtaining Failure Information1835.2 Transferring maintenance information filesThis section describes how to transfer files that contain log or dump

5. Obtaining Failure Information184(2) Transferring log information to a remote terminalFigure 5-2: Transferring log information to a remote terminal&

5. Obtaining Failure Information185200 EPRT command successful.150 Opening BINARY mode data connection for 'nimd.core'.100% |***************

5. Obtaining Failure Information186> cd /usr/var/core/> ls <---1interfaceControl.core nodeIn

5. Obtaining Failure Information1875.3 Collecting information and transferring files by using the "show tech-support" commandYou can use the

5. Obtaining Failure Information188...

5. Obtaining Failure Information1895. Specify the destination directory.6. Specify a file name.(3) Use the "remote command" command to use t

xviiiHandle power cables carefully.• Do not place anything heavy on a power cable. Do not pull, bend, or process a cable. Doing so could damage the ca

5. Obtaining Failure Information1905.4 Collecting information and transferring files by using the "ftp" command on a remote terminalYou can

5. Obtaining Failure Information191Figure 5-11: Obtaining the "show tech-support" unicast informationclient-host> ftp 192.168.0.60

5. Obtaining Failure Information192220 192.168.0.60 FTP server (NetBSD-ftpd) ready.Name (192.168.0.60:staff1): staff1331 Password required for staff1.

5. Obtaining Failure Information1935.5 Writing data to a memory cardFailure and maintenance information can be written to a memory card. Note, however

195Chapter6. Line Testing6.1 Testing a line

6. Line Testing1966.1 Testing a lineIn line tests, what loops back test frames varies depending on the test type. The following figure shows what loop

6. Line Testing197Date 2006/03/10 00:20:21 UTCInterface type :100BASE-TXTest count :30 Send-OK :

6. Line Testing198Figure 6-4: Twisted pair cable2. As shown in the following figure, insert the cables into the connector and crimp them by using a cr

199Chapter7. Device RestartThis chapter mainly describes how to restart the device.7.1 Restarting the device

xixWhen pressing the button of the basic control unit, do not use anything with a fragile tip, or anything that might become caught in the switch, suc

7. Device Restart2007.1 Restarting the device7.1.1 Device restartYou can use the reload command to restart the device. Log data is stored when the dev

7. Device Restart201In step 2, you will be asked whether you want to capture the CPU memory dump. According to the figure above, you do not use any pa

7. Device Restart202Figure 7-4: Confirmation messages for CPU memory dump capturingAX3800S, AX3600S, and AX2400S series switchesAs an example, the fol

7. Device Restart203In this step, choose whether you capture the dump.Figure 7-6: Selection of the CPU memory dump typeIn step 2, you will be asked wh

7. Device Restart204Figure 7-7: Confirmation messages for CPU memory dump capturing

205AppendixA. Detailed Display Contents of the "show tech-support" Command

A. Detailed Display Contents of the "show tech-support" Command206A. Detailed Display Contents of the "show tech-support" CommandA

A. Detailed Display Contents of the "show tech-support" Command20715 /usr/local/diag/pk_tmrd Operating time information (for Version 11.2 an

A. Detailed Display Contents of the "show tech-support" Command20841 stty -a -f /dev/tty00 Console terminal information YYYY42cat /var/log/c

A. Detailed Display Contents of the "show tech-support" Command20961 cat /var/tmp/gen/trace/mng_sub.trcConfiguration command trace informati

xxDo not install the Switch in a dusty or humid location.• Do not install the Switch in a dusty or humid location. Doing so could result in fire or el

A. Detailed Display Contents of the "show tech-support" Command21084 show channel-group statistics lacpLACP statistics for link aggregationN

A. Detailed Display Contents of the "show tech-support" Command211106 show dot1x detail Authentication status information on IEEE 802.X auth

A. Detailed Display Contents of the "show tech-support" Command212129 show ipv6 pim interface (detail)Information on interfaces with IPv6 PI

A. Detailed Display Contents of the "show tech-support" Command213149 show ip arp inspection statisticsDynamic ARP inspection statistics (fo

A. Detailed Display Contents of the "show tech-support" Command214167 show graceful-restart unicastOperating status of restart routers that

A. Detailed Display Contents of the "show tech-support" Command215185 show web-authentication user commitDisplay of entries registered in th

A. Detailed Display Contents of the "show tech-support" Command216Legend Y: Displayed; N: Not displayedNote: Parentheses in the Command (dis

A. Detailed Display Contents of the "show tech-support" Command2177 show cpu days hours minutes secondsCPU utilization YYYY8show memory summ

A. Detailed Display Contents of the "show tech-support" Command21832 show session Login session information YYYY33/usr/sbin/pstat -t Termina

A. Detailed Display Contents of the "show tech-support" Command21953 show netstat interface Kernel interface information YYYY54show vlan lis

xxisupply unit from a Switch, hold the power supply unit tightly. Pulling a power supply unit carelessly from a Switch might cause the power supply un

A. Detailed Display Contents of the "show tech-support" Command22075 show loop-detection statisticsStatistics on L2 loop detection (for Vers

A. Detailed Display Contents of the "show tech-support" Command22195 show dot1x detail Authentication status information on IEEE 802.X authe

A. Detailed Display Contents of the "show tech-support" Command222116 show ipv6 mld interface Information on interfaces with MLD enabledNNYN

A. Detailed Display Contents of the "show tech-support" Command223137 show ip dhcp snooping logging infoDHCP snooping log information (for V

A. Detailed Display Contents of the "show tech-support" Command224155 show ipv6 route summary Number of active and inactive routes maintaine

A. Detailed Display Contents of the "show tech-support" Command225173 show web-authentication loginDisplay of authenticated-user information

A. Detailed Display Contents of the "show tech-support" Command226Legend Y: Displayed; N: Not displayedNote: Parentheses in the Command (dis

A. Detailed Display Contents of the "show tech-support" Command2279 /sbin/dmesg Kernel event information YYYY10cat /var/run/dmesg.boot Kerne

A. Detailed Display Contents of the "show tech-support" Command22835 ls -lTiR /var/tmp/mmi* CLI information file list (for versions earlier

A. Detailed Display Contents of the "show tech-support" Command22956 show port statistics Port statistics YYYY57show port protocol Protocol

History of Amendments[Edition 14]Summary of amendments[Edition 13]Summary of amendments[Edition 12]Summary of amendments[Edition 11]Summary of amendme

xxiiDo not touch the SFP-T during operation and just after operation stops.• During operation (when a link is established), the temperature of the SFP

A. Detailed Display Contents of the "show tech-support" Command23077 show spanning-tree statisticsSpanning tree statistics NNNY78show vlan d

A. Detailed Display Contents of the "show tech-support" Command231100 show ip dhcp snooping logging infoDHCP snooping log information (for V

A. Detailed Display Contents of the "show tech-support" Command232Legend: Y: Displayed, N: Not displayedNote: Parentheses in the Command (di

233IndexSymbols"MC not found." is displayed when the memory card is accessed 25Aactions to be taken for 100BASE-FX/1000BASE-X problems 38act

Index234faults for AX6700S, AX6600S, and AX6300S series switches 16flow samples cannot be sent to the collector 140forgotten login user password 24for

Index235the Switch cannot be synchronized by using NTP 144transferring files using the ftp command 183transferring files using the zmodem command 185t

xxiiiDo not turn off the power during a software update (while the ppupdate command is executing).• The Switch automatically restarts after the ppupda

xxivWhen carrying or packing a Switch and its optional modules, wear a wrist strap to protect against static electricity.• Be sure to wear an antistat

xxvDo not place a Switch where it will be exposed to hydrogen sulfide or salt.• Placing a Switch in an area where sulfides are present, such as a hot-

xxvi

xxviiSafety Information [AX6600S]Using AX6600S series switches correctly and safely• This guide provides important information for ensuring safe use o

xxviiiIf anything seems wrong, immediately turn off the power.• If smoke or an unusual smell is emanating from the Switch, or if liquid is spilled int

xxixgrounding could result in electric shock or failures due to electrical noise.• When the Switch is connected to a DC power supply unit, always conn

xxxHandle power cables carefully.• Do not place anything heavy on a power cable. Do not pull, bend, or process a cable. Doing so could damage the cabl

xxxiWhen pressing the button of the control and switching unit, do not use anything with a fragile tip, or anything that might become caught in the Sw

[Edition 10]Summary of amendments[Edition 9]Summary of amendmentsCommunication is not possible or is disconnected • The description was changed in acc

xxxiiDo not install the Switch in a dusty or humid location.• Do not install the Switch in a dusty or humid location. Doing so could result in fire or

xxxiiinot allow hair or other objects near the ventilation slots. They might be sucked into the Switch, resulting in injury.When moving the Switch, do

xxxivcable coating, resulting in fire or electric shock.• When connecting or disconnecting the power cable from the outlet, always hold the plug, not

xxxvincinerate it, or immerse it in water.Cleaning• Remove dust on and around the Switch regularly. In addition to causing the Switch to stop, accumul

xxxviDo not turn off the power during a software update (while the ppupdate command is executing).• The Switch automatically restarts after the ppupda

xxxviiWhen carrying or packing a Switch and its optional modules, wear a wrist strap to protect against static electricity.• Be sure to wear an antist

xxxviiiDo not place a Switch where it will be exposed to hydrogen sulfide or salt.• Placing a Switch in an area where sulfides are present, such as a

xxxixSafety Information [AX6300S]Using AX6300S series switches correctly and safely• This guide provides important information for ensuring safe use o

xlIf 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 th

xligrounding could result in electric shock or failures due to electrical noise.• When the Switch is connected to a DC power supply unit, always conne

[Edition 8]Summary of amendments[Edition 7]Summary of amendmentsItem ChangesAddition of series • A description relating to the addition of AX6600S ser

xliiHandle power cables carefully.• Do not place anything heavy on a power cable. Do not pull, bend, or process a cable. Doing so could damage the cab

xliiiWhen pressing the button of the management and switching unit, do not use anything with a fragile tip, or anything that might become caught in th

xlivDo not install the Switch in a dusty or humid location.• Do not install the Switch in a dusty or humid location. Doing so could result in fire or

xlvnot allow hair or other objects near the ventilation slots. They might be sucked into the Switch, resulting in injury.When moving the Switch, do no

xlvicable coating, resulting in fire or electric shock.• When connecting or disconnecting the power cable from the outlet, always hold the plug, not t

xlviiincinerate it, or immerse it in water.Cleaning• Remove dust on and around the Switch regularly. In addition to causing the Switch to stop, accumu

xlviiiDo not turn off the power during a software update (while the ppupdate command is executing).• The Switch automatically restarts after the ppupd

xlixWhen carrying or packing a Switch and its optional modules, wear a wrist strap to protect against static electricity.• Be sure to wear an antistat

lboth devices. If you hear noise on the TV or radio, do the following:1. Place the Switch as far away as possible from the TV or radio.2. Adjust the o

liSafety Information [AX3800S] [AX3600S] [AX2400S]Using AX3800S, AX3600S, and AX2400S series switches correctly and safely• This guide provides import

[Edition 6]Summary of amendments[Edition 5]Summary of amendments[Edition 4]Summary of amendmentsDetailed display contents of the "show tech-suppo

liiIf 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 t

liiiUse the Switch only with the indicated power supply.• Do not use the Switch at any voltage other than the indicated voltage. Doing so could result

livdue to the high output power of EPU-B.Handle power cables carefully.• Do not place anything heavy on a power cable. Do not pull, bend, or process a

lvDo not place the Switch in an unstable location.• When installing the Switch on a table, position the Switch horizontally on a worktable strong enou

lvi• If you must stack multiple Switches during transport, use appropriate packaging. Failure to do so might cause the Switches to become deformed or

lviiDo 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

lviii• Condensation might form on the surfaces and the inside of the Switch if it is moved from a cold location to a warm location. Using the Switch i

lixDo not place a Switch in a high-temperature location.• Do not place a Switch in direct sunlight or near a heater or other heat-generating apparatus

lx• Replacing a fan unit of a redundant power model AX3830STurn off the power before installing or removing a power supply module.• Before installing

lxiMake sure that you use a valid combination for the direct attach cable and the Switch.The following Switches support SFPP-CU1M/3M/5M. Use the trans

[Edition 3]Summary of amendments[Edition 2]Summary of amendmentsItem ChangesAdditional model • A description relating to the additional model was adde

lxiiair 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

1Chapter1. OverviewThis chapter provides an overview of failure analysis.1.1 Overview of analyzing failures1.2 Overview of analyzing failures of all o

1. Overview21.1 Overview of analyzing failuresUse this manual when there is a problem in an AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, or AX2400S se

1. Overview31.2 Overview of analyzing failures of all or part of the Switch1.2.1 Failure analysis for AX6700S, AX6600S, and AX6300S series switchesIf

1. Overview4#1: The BCU, CSU, or MSU can be turned off by the Inactivate operation from the system operation panel or by entering a command from the o

1. Overview51.2.2 Failure analysis for AX3800S, AX3600S, and AX2400S series switchesIf a failure occurs during operation and the actual switch can be

1. Overview6Table 1-2: LED indications, buttons, and connectorsNo.Name Type Status LEDbrightnessDescription1 PWR LED: Green Power supply status Green

1. Overview74 MC Connector Memory card slot -- -- Memory card slot5 ACC LED: Green Memory card status ON Regular The memory card is being accessed. (D

1. Overview811 1-24 LED: Green or orangeOperating status of 10/100/1000BASE-T Ethernet portsGreen Regular Link established, 100 Mbit/s#4, full duplex#

1. Overview9Legend: --: Not applicable#1: The LED blinks green at long intervals (turns on for 0.5 seconds and off for 5 seconds).#2: This applies whe

1. Overview101.3 Overview of analyzing failures of functionalityThe following table provides an overview of analyzing functional failures on the Switc

1. Overview11Spanning tree failure 3.6.2 Failures occurring when the Spanning Tree functionality is usedRing Protocol failure 3.6.3 Failures occurring

1. Overview12No OSPFv3 information 3.11.2 OSPFv3 routing information cannot be foundNo BGP4+ information 3.11.3 No BGP4+ routing information existsNo

1. Overview13 Neighboring device information cannot be obtained by the LLDP functionality-- 3.17.1 Neighboring device information cannot be obtained

15Chapter2. Troubleshooting Switch FailuresThis chapter describes how to take actions when a failure occurs on a Switch.2.1 Troubleshooting faults for

2. Troubleshooting Switch Failures162.1 Troubleshooting faults for AX6700S, AX6600S, and AX6300S series switches2.1.1 Procedure for handling switch fa

2. Troubleshooting Switch Failures17Table 2-2: Points to be checked in case of power failures6 The STATUS LED of the BCU, CSU, or MSU is lit in red, t

2. Troubleshooting Switch Failures182.1.2 Replacing the switch and optional modulesThe procedure to replace the switch and optional modules is describ

2. Troubleshooting Switch Failures192.2 Troubleshooting faults for AX3800S, AX3600S, and AX2400S series switches2.2.1 Procedure for handling switch fa

iPrefaceRelevant productsThis manual applies to the models in the AX6700S, AX6600S, AX6300S, AX3800S, AX3600S, and AX2400S series of switches.Before y

2. Troubleshooting Switch Failures20Table 2-4: Isolating the cause of power failures2.2.2 Isolating the cause of external redundant power unit failure

2. Troubleshooting Switch Failures21Table 2-5: Isolating the cause of external redundant power unit failuresTable 2-6: Isolating the cause of external

23Chapter3. Troubleshooting Functional Failures During OperationThis chapter describes what actions to take when a problem occurs, such as when a Swit

3. Troubleshooting Functional Failures During Operation243.1 Problems related to login passwords3.1.1 Forgotten login user passwordIf a user forgets h

3. Troubleshooting Functional Failures During Operation253.2 Memory card problems3.2.1 The "show system" or "show mc" command disp

3. Troubleshooting Functional Failures During Operation263.3 Operation terminal problems3.3.1 Information cannot be entered from the console or does n

3. Troubleshooting Functional Failures During Operation27Table 3-4: Problems occurring during connection to the modem and action to take3.3.2 Login fr

3. Troubleshooting Functional Failures During Operation28Table 3-5: Problems occurring during connection to a remote terminal and action to take3.3.3

3. Troubleshooting Functional Failures During Operation29 2. Use the killuser command to forcibly log out the target user.Specify the login number yo