Page 1 IP8800/S6700, IP8800/S6600, IP8800/S6300, IP8800/S3600, IP8800/S2400 Troubleshooting Guide IP88S36-T001-000 Thoroughly read and store this manual. • Read and thoroughly understand safety-related explanations before using this product. • Keep this manual in a location close at hand for easy reference.
Page 2 ■ Applicable products This manual describes models IP8800/S6700, IP8800/S6600, IP8800/S6300, IP8800/S3600, and IP8800/S2400 series. ■ Caution when exporting The necessary procedures are to be adopted when exporting this product after first confirming the regulations of the Foreign Exchange and Foreign Trade Law, U.S. export control related regulations, etc.
Page 3 [IP8800/S2400]: The description is applicable to IP8800/S2400. If more than one mark is indicated such as [IP8800/S3600] [IP8800/S2400], the function is only supported by those two models or the description is not applicable to other models. The mark below refers to functions supported by option licenses.
Page 4 IP8800/S6300 Software Manual Configuration Commands, Vol.2 (IP88S63-S005) IP8800/S6300 Software Manual Operation Commands, Vol.1 (IP88S63-S006) IP8800/S6300 Software Manual Operation Commands, Vol.2 (IP88S63-S007) IP8800/S6300 Software Manual Message Log Reference (IP88S63-S008) IP8800/S6300 Software Manual MIB Reference (IP88S63-S009) IP8800/S6700, IP8800/S6600, IP8800/S6300, IP8800/S3600, IP8800/S2400 Troubleshooting Guide (IP88S36-T001)
Page 5 Syntax and parameter details of operation commands Details of operation messages and logs Details of supported MIBs lnformation on troubleshooting IP8800/S3600, IP8800/S2400 Quick Start Guide (IP88S36-Q001) IP8800/S3600, IP8800/S2400 Hardware lnstallation Guide (IP88S36-H001) IP8800/S3600 Software Manual Configuration Settings, Vol.1 (IP88S36-S001) IP8800/S3600 Software Manual Configuration Settings, Vol.2 (IP88S36-S002)
Page 6 BPDU CIDR IP8800/S3600, IP8800/S2400 Quick Start Guide (IP88S36-Q001) IP8800/S3600, IP8800/S2400 Hardware Installation Guide (IP88S36-H001) IP8800/S2400 Software Manual Configuration Settings, Vol.1 (IP88S24-S001) IP8800/S2400 Software Manual Configuration Settings, Vol.2 (IP88S24-S002) IP8800/S2400 Software Manual Configuration Commands (IP88S24-S003) IP8800/S2400 Software Manual Operation Commands (IP88S24-S004)
Page 7 CIST CLNP CLNS CONS CSMA/CD CSNP DHCP DSAP DSCP DVMRP E-Mail EAPOL FQDN FTTH GBIC GSRP HMAC IANA ICMP ICMPv6 IEEE IETF IGMP IPCP IPv4 IPv6 IPV6CP L2LD LLDP LLPQ LLQ+3WFQ LLRLQ MDI-X Committed Information Rate Common and Internal Spanning Tree ConnectionLess Network Protocol ConnectionLess Network System Connection Oriented Network System...
Page 8 Introduction MSTI MSTP NLA ID NPDU NSAP NSSA OADP OSPF PICS PIM-DM PIM-SM PIM-SSM PSNP RADIUS RIPng RMON RSTP SMTP SNAP SNMP SNPA SSAP TACACS+ TCP/IP TLA ID Maintenance domain Intermediate Point Maximum Receive Unit Multiple Spanning Tree Instance Multiple Spanning Tree Protocol Management and Switching Unit Maximum Transfer Unit Not AcKnowledge...
Page 9 TPID UDLD UPC-RED uRPF VLAN VRRP WRED ■ Conventions: kB, MB, GB, and TB 1 kB(kilobytes), 1 MB(megabytes), 1 GB(gigabytes), and 1 TB(terabytes) indicate 1024 bytes, 1024 1024 bytes respectively. Type Of Service Tag Protocol Identifier Time To Live Uni-Directional Link Detection User Datagram Protocol Usage Parameter Control Usage Parameter Control - Random Early Detection...
Page 11: Table Of Contents
1.1 Failure Analysis Overview 1.2 System and Partial Failure Analysis Overview 1.2.1 Failure Analysis for IP8800/S6700, IP8800/S6600, and IP8800/S6300 1.2.2 Failure Analysis for IP8800/S3600 and IP8800/S2400 1.3 Functional Failure Analysis Overview Troubleshooting System Failures 2.1 Troubleshooting for IP8800/S6700, IP8800/S6600, and IP8800/S6300 2.1.1 Troubleshooting Procedure on System Failures...
Page 12 Contents 3.4 Network Interface Communication Failure 3.4.1 Ethernet Port Cannot Be Connected 3.4.2 Communication Failure in Basic Switching Unit BSU/PSP 3.4.3 Actions against Troubles on 10BASE-T/100BASE-TX/1000BASE-T 3.4.4 Actions against Troubles on 1000BASE-X 3.4.5 Actions against Troubles on 10GBASE-R 3.4.6 Communication Failure on Using PoE 3.4.7 Communication Failure on Using Link Aggregation 3.5 Layer 2 Network Communication Failure 3.5.1 Layer 2 Communication by VLAN Is Disabled...
Page 13 3.13 Communication Failure on High-reliability Function 3.13.1 GSRP Communication Failures 3.13.2 Communication with VRRP Configuration in IPv4 Network Is Disabled 3.13.3 Communication with VRRP Configuration in IPv6 Network Is Disabled 3.14 SNMP Communication Failure 3.14.1 MIBs Cannot Be Obtained from SNMP Manager 3.14.2 Traps Cannot Be Received by SNMP Manager 3.15 Troubleshooting of sFlow Statistics (Flow Statistics) Function 3.15.1 sFlow Packets Do Not Reach Collector...
Page 14 [IP8800/S6300] 5.2 Transferring Files for Maintenance Information 5.2.1 Transferring Files Using ftp Command 5.2.2 Transferring Files Using zmodem Command [IP8800/S3600] [IP8800/S2400] 5.2.3 Transferring Maintenance Information Files Using show tech-support Command 5.2.4 Transferring Files Using ftp Command from the Operation Terminal 5.3 Writing to MC...
Page 15: Safety Guide [Ip8800/S6700]
Safety Guide [IP8800/S6700] ■ Safety guide for the IP8800/S6700 series • This document provides safety-related notices for use of the IP8800/S6700 series. To utilize the functions of this device, read this document completely and carefully before using the device. • Keep this document at hand after you read it, so that you can always refer it later. •...
Page 16 Safety Guide [IP8800/S6700] ■ In case a failure should occur, power off the device immediately. • In case fume or unusual odor should occur, or foreign matters should come into the device, power off the device as follows. If the device is used in a faulty state, fire disasters or electric shock may be caused. •...
Page 17 ■ Grounding is required. • When the device is connected to the power supply of 100VAC, leak current of up to 3.5mA flows for each device. Be sure to use the grounded outlet. If the power supply is used without grounding, an electric shock may be caused and failures may occur due to electric noise.
Page 18 Safety Guide [IP8800/S6700] ■ The device must be carried and installed by the trained personnel or specialized carrier. • The weight of the device is 82 kg/182 lb at the maximum. The device must be carried and installed by the trained personnel or specialized carrier.
Page 19 ■ Before powering off, turn off all power switches or breakers on the device. • Multiple input power supplies are provided to the device. Before powering off, turn off all power switches (when AC power supply is mounted) or breakers (when DC power supply is mounted) on the device. The label below is attached to the device.
Page 20 Safety Guide [IP8800/S6700] ■ Do not install the device in a humid or dusty environment. • Do not install the device in a humid or dusty environment. Fire disasters or electric shock may be caused. • Moving the device from a cold place to a warm place may form condensation on the surface or internal of the device.
Page 21 ■ Do not drop an optional component. • Handle the optional component carefully not to drop it. If dropped, personal injury may be caused. • The weight and depth of the DC power supply are 5.6 kg/12.4 lb and 163 mm/6.4 in respectively. When removing the DC power supply, hold it securely.
Page 22 Safety Guide [IP8800/S6700] ■ Be careful of laser beams. • The network interface module as indicated below uses laser beams. Do not peep in the optical transceiver directly. ■ Do not touch a working (including immediately after stopping) SFP-T. • A working (establishing a link) SFT-P can have up to 65 working or immediately after stopping to prevent getting burned.
Page 23 ■ Do not power off the device during software update (when the ppupdate command is being executed). • By the execution of the ppupdate command, the device automatically restarts. Do not power off the device during restart (until the STATUS LED on the basic control unit changes from blinking in green into steady light).
Page 24 Safety Guide [IP8800/S6700] ■ For carrying or packaging the device and optional component, use an antistatic wrist strap. • Use an antistatic wrist strap. If you handle the device without the antistatic wrist strap, the device can be damaged by the static electricity. ■...
Page 25 ■ Do not bring a TV or radio close to the device. • Leaving a TV or radio close to the device can adversely influence to each other. If a TV or radio interferes the device, remedy as follows: 1. Keep the device from the television or radio set as far away as possible. 2.
Page 27: Safety Guide [Ip8800/S6600]
Safety Guide [IP8800/S6600] ■ Safety guide for the IP8800/S6600 series • This document provides safety-related notices for use of the IP8800/S6600 series. To utilize the functions of this device, read this document completely and carefully before using the device. • Keep this document at hand after you read it, so that you can always refer it later. •...
Page 28 Safety Guide [IP8800/S6600] ■ In case a failure should occur, power off the device immediately. • In case fume or unusual odor should occur, or foreign matters should come into the device, power off the device as follows. If the device is used in a faulty state, fire disasters or electric shock may be caused. •...
Page 29 ■ Grounding is required. • Leak current of up to 3.5mA flows for each device. If connecting the device with AC power, be sure to use the grounded outlet. If the power supply is used without grounding, an electric shock may be caused and failures may occur due to electric noise.
Page 30 Safety Guide [IP8800/S6600] The label below is attached to the device. 45kg IP8800/S6604 ■ Handle the power cable with caution. • Do not put a heavy material on the power cable or do not pull, bend, or modify the power cable. The power cable will be damaged and fire disasters or electric shock may be caused.
Page 31 ■ Work to add or replace equipment must be performed by a trained engineer or maintenance personnel. • To add or replace optional components must be performed by a trained engineer or maintenance personnel. To add or replace a power supply involves to plug and unplug power cables; a person other than the preceding ones may fail to handle things, which can cause fire disaster, electric shock, and equipment failure.
Page 32 Safety Guide [IP8800/S6600] ■ Do not install the device in a humid or dusty environment. • Do not install the device in a humid or dusty environment. Fire disasters or electric shock may be caused. • Moving the device from a cold place to a warm place may form condensation on the surface or internal of the device.
Page 33 ■ Do not block the intake and/or exhaust port. • Do not block the intake/exhaust port of the device. Blocking the intake/exhaust port keeps heat inside and fire disasters may be caused. Keep a space of at least 70mm from the intake/exhaust port. ■...
Page 34 Safety Guide [IP8800/S6600] ■ When removing the fan unit, do not put your hand close to the rotating fan. • The fan may still be rotating immediately after the removal of the fan unit. While the fan is rotating, do not put your hand or finger close to it.
Page 35 ■ Do not touch a working (including immediately after stopping) SFP-T. • A working (establishing a link) SFT-P can have up to 65 or immediately after stopping to prevent getting burned. Caution. Hot! (all sides) • To remove an SFP-T, follow the following procedures. Otherwise, you may get burned. •...
Page 36 Safety Guide [IP8800/S6600] ■ Do not power off the device during software update (when the ppupdate command is being executed). • By the execution of the ppupdate command, the device automatically restarts. Do not power off the device during restart (until the STATUS LED on the control swithcing unit changes from blinking in green into steady light).
Page 37 ■ For carrying or packaging the device and optional component, use an antistatic wrist strap. • Use an antistatic wrist strap. If you handle the device without the antistatic wrist strap, the device can be damaged by the static electricity. ■...
Page 38 Safety Guide [IP8800/S6600] ■ Do not bring a TV or radio close to the device. • Leaving a TV or radio close to the device can adversely influence to each other. If a TV or radio interferes the device, remedy as follows: 1.
Page 39: Safety Guide [Ip8800/S6300]
Safety Guide [IP8800/S6300] ■ Safety guide for the IP8800/S6300 series • This document provides safety-related notices for use of the IP8800/S6300 series. Read this document completely and carefully before using the device. • Keep this document at hand after you read it, so that you can always refer it later. •...
Page 40 Safety Guide [IP8800/S6300] ■ In case a failure should occur, power off the device immediately. • In case fume or unusual odor should occur, or foreign matters should come into the device, power off the device as follows. If the device is used in a faulty state, fire disasters or electric shock may be caused. •...
Page 41 ■ Grounding is required. • Leak current of up to 3.5mA flows for each device. For connecting to the AC power supply, be sure to use the grounded outlet. If the power supply is used without grounding, an electric shock may be caused and failures may occur due to electric noise.
Page 42 Safety Guide [IP8800/S6300] ■ The device must be carried and installed by at least three people. • The table below shows mass of the devices. The device must be carried and installed by at least three people. Otherwise, a personal injury due to drop or fall may be caused. Number of people to carry the device Model IP8800/S6304...
Page 43 ■ Before powering off, turn off all power switches or breakers on the device. • Multiple input power supplies are provided to the device. Before powering off, turn off all power switches (when AC power supply is mounted) or breakers (when DC power supply is mounted) on the device. The label below is attached to the device.
Page 44 Safety Guide [IP8800/S6300] ■ Do not install the device in a humid or dusty environment. • Do not install the device in a humid or dusty environment. Fire disasters or electric shock may be caused. • Moving the device from a cold place to a warm place may form condensation on the surface or internal of the device.
Page 45 ■ Do not block the intake and/or exhaust port. • Do not block the intake/exhaust port of the device. Blocking the intake/exhaust port keeps heat inside and fire disasters may be caused. Keep a space of at least 70mm/2.8 in from the intake/exhaust port. ■...
Page 46 Safety Guide [IP8800/S6300] ■ When removing the fan unit, do not put your hand close to the rotating fan. • The fan may still be rotating immediately after the removal of the fan unit. While the fan is rotating, do not put your hand or finger close to it.
Page 47 ■ Do not touch a working (including immediately after stopping) SFP-T. • A working (establishing a link) SFT-P can have up to 65 or immediately after stopping to prevent getting burned. Caution. Hot! (all sides) • To remove an SFP-T, follow the following procedures. Otherwise, you may get burned. •...
Page 48 Safety Guide [IP8800/S6300] ■ Do not power off the device during software update (when the ppupdate command is being executed). • By the execution of the ppupdate command, the device automatically restarts. Never power off the device during restart (until the STATUS LED on the management and switching unit changes from blinking in green into steady light).
Page 49 damaged by the static electricity. ■ After removing an optional component, be sure to attach a blank panel. • After removing an optional component, be sure to attach a blank panel. Using the device without the blank panel attached, the air flow in the device cannot be maintained. In such a case, the temperature rise inside the device may cause a failure.
Page 50 Safety Guide [IP8800/S6300] ■ Do not bring a TV or radio close to the device. • Leaving a TV or radio close to the device can adversely influence to each other. If a TV or radio interferes the device, remedy as follows: 1.
Page 51: Safety Guide [Ip8800/S3600] [Ip8800/S2400]
■ Symbols • We have various symbols displayed on the IP8800/S3600 and IP8800/S2400 series and in the manuals to guide you in using the IP8800/S3600 and IP8800/S2400 series correctly and safely without injuring yourself and others, or damaging equipment assets.
Page 52 Safety Guide [IP8800/S3600] [IP8800/S2400] ■ In case a failure should occur, power off the device immediately. • In case a trouble such as smoke or unusual odor should occur or foreign materials or water should come in to the device, power off the device immediately. If the device is used in a faulty state, fire disasters or electric shock may be caused.
Page 53 (on the device side) with the margin of 8 to 10 mm (0.3 to 0.4 in).. If the margin is too small, loose connection or cable disconnection may be caused. On the other hand, too large margin may cause conductor exposure, resulting in electric shock. Safety Guide [IP8800/S3600] [IP8800/S2400] xliii...
Page 54 Safety Guide [IP8800/S3600] [IP8800/S2400] ■ Do not use the cable with the protection cap detached. • Do not remove protection cap except when connecting the cable. Operating them with the protection cap detached may cause an electric shock. Since external power supply EPU-B has a high output power, the label below is attached near the external power connector.
Page 55 • When moving the external power unit (EPU), do not carry it by holding its handle of power module. The handle may be removed and the device may be dropped. As a result, personal injury may be caused. Also, the device may be deformed and fire disasters or electric shock may be caused. Safety Guide [IP8800/S3600] [IP8800/S2400] CAUTION...
Page 56 Safety Guide [IP8800/S3600] [IP8800/S2400] ■ Precaution on carrying the device • When moving the device, power off the device, remove the power cable out of the outlet, remove all other cables from the device, and then move the device. Otherwise, the device or cable may be deformed or damaged.
Page 57 ■ Do not touch the inside of the device. • Do not put your hand inadvertently inside the device. Mechanical parts may cause personal injury. Safety Guide [IP8800/S3600] [IP8800/S2400] ° °...
Page 58 Safety Guide [IP8800/S3600] [IP8800/S2400] ■ Do not ride, recline, or place a heavy loading on the device. • Do not ride on or lean against the device. The device may be damaged. Alternatively, the device may lose its balance and fall or drop. As a result, personal injury may be caused.
Page 59 • When replacing the power supply or fan unit with the device powered on, complete the entire task from removal to installation within three minutes. If it takes more than three minutes, a failure may occur due to temperature rise inside the device. Safety Guide [IP8800/S3600] [IP8800/S2400] CAUTION xlix...
Page 60 Safety Guide [IP8800/S3600] [IP8800/S2400] ■ Before installing/uninstalling the power module, turn off the power switch. • Before installing/uninstalling the power module, turn off the power switch on the power module to be installed or uninstalled. If operation is performed while the power switch on the power module is on, a failure or device trouble may be caused.
Page 61 For a configuration using DC power supply, turn off the breaker of the power supply equipment. ■ Discarding the device • Discard the device according to the ordinance or rule of the local government or call the local waste material handling facility. Safety Guide [IP8800/S3600] [IP8800/S2400]...
Page 63: Overview
Overview This chapter outlines the failure analysis. 1.1 Failure Analysis Overview 1.2 System and Partial Failure Analysis Overview 1.3 Functional Failure Analysis Overview...
Page 64: Failure Analysis Overview
Overview Failure Analysis Overview For any problems with IP8800/S6700, IP8800/S6600, IP8800/S6300, IP8800/S3600, and IP8800/S2400, refer to this manual. To visually check the system, follow the instructions in To login and check the system, follow the instructions in "1.2 System and Partial Failure Analysis "1.3 Functional Failure Analysis...
Page 65: System And Partial Failure Analysis Overview
System and Partial Failure Analysis Overview 1.2.1 Failure Analysis for IP8800/S6700, IP8800/S6600, and IP8800/ S6300 If a failure occurs during operation and the system can be visually and directly checked, follow the procedure in "2.1 Troubleshooting for IP8800/S6700, IP8800/S6600, and The device status is displayed on the basic control unit (BCU) for IP8800/S6700, the control and switching unit (CSU) for IP8800/S6600, and management and switching unit (MSU) for IP8800/S6300.
Page 66: Failure Analysis For Ip8800/S3600 And Ip8800/S2400
*9 Operation can be shut down by inputting a command. Figure 1-1: Example of Front Panel Layout 1.2.2 Failure Analysis for IP8800/S3600 and IP8800/S2400 If a failure occurs during operation and the system can be visually and directly checked, follow the procedure in "2.2 Troubleshooting for IP8800/S3600 and...
Page 67 For IP8800/S3600 and IP8800/S2400, the generic names of the models are as follows: • AC power supply model: IP8800/S3640-24T, IP8800/S3630-24T, IP8800/S3630-24T2X, IP8800/S3630-24P, IP8800/S2430-24T, IP8800/S2430-24T2X, IP8800/S2430-48T, IP8800/S2430-48T2X • DC power supply model: IP8800/S3630-24TD, IP8800/S3630-24T2XD, IP8800/S2430-24TD, IP8800/ S2430-24T2XD, IP8800/S2430-48TD • Redundant power supply model: IP8800/S3640-24TW, IP8800/S3640-24T2XW, IP8800/S3640-48TW, IP8800/...
Page 68 Overview Name Type 1-24 LED: Green/ Orange RESET Switch (Non-locked) Note: Figure 1-2 and Table 1-2 show a typical system. For more details on each system, see "Hardware Installation Guide." Function Indicates the operation status of 10/ Lit in green: Link established 100/1000BASE-T Ethernet port.
Page 69: Functional Failure Analysis Overview
Functional Failure Analysis Overview The overview of functional failure analysis for this system is shown in the table below. Some communication failure in the lower layer may cause the communication failure in the upper layer, check the items in the lower layer as well. Table 1-3: Functional Failure Status and Reference Item Forgot login password...
Page 70 Overview Item IPv4 unicast routing No RIP information communication failure No OSPF information No BGP4 information No VRF information IPv4 multicast routing Communication disabled on PIM-SM communication failure network Data double-relayed on PIM-SM network Communication disabled on PIM-SSM network Data double-relayed on PIM-SSM network Communication failure of VRF IPv6 network communication Communication disabled...
Page 71 Item Neighboring system information cannot be acquired by LLDP function Neighboring system information cannot be acquired by OADP function Communication failure in NTP Failure when using IEEE802.3ah/ Port becomes inactive UDLD function Problems on redundant configuration of basic control unit (BCU)/control and switching unit (CSU)/management and switching unit (MSU)
Page 73: Troubleshooting System Failures
Troubleshooting System Failures This chapter explains how to deal with the problems on the system. 2.1 Troubleshooting for IP8800/S6700, IP8800/S6600, and IP8800/S6300 2.2 Troubleshooting for IP8800/S3600 and IP8800/S2400...
Page 74: Troubleshooting For Ip8800/S6700, Ip8800/S6600, And Ip8800/S6300
Troubleshooting System Failures Troubleshooting for IP8800/S6700, IP8800/S6600, and IP8800/S6300 2.1.1 Troubleshooting Procedure on System Failures Follow the procedure below when the system failed. Table 2-1: Troubleshooting System Failures Failure • Fume generated from the system • Unusual odor occurs from the system •...
Page 75 Failure Error message output to the system operation panel STATUS LED on BCU/CSU/MSU is lit in red, other LEDs are OFF, and no message on the system operation panel Table 2-2: Power Failure Check Items Failure Power switch on the power supply is OFF •...
Page 76: Replacement Method Of Optional Components
Troubleshooting System Failures 2.1.2 Replacement Method of Optional Components The optional component replacement procedures are described in "Hardware Installation Guide." Follow the procedures described in the manual.
Page 77: Troubleshooting For Ip8800/S3600 And Ip8800/S2400
Troubleshooting for IP8800/S3600 and IP8800/ S2400 2.2.1 Troubleshooting Procedure on System Failures Follow the procedure below when the system failed. Table 2-3: Troubleshooting System Failures Failure • Fume generated from the system • Unusual odor occurs from the system • Unusual sound occurs from the system login prompt is not displayed PWR LED on the system is OFF ST1 LED on the system is lit in red...
Page 78 Troubleshooting System Failures Failure • ST1 LED on the system is blinking in red • LINK LED (10GBASE-R port and 1000BASE-X port) and 1-48 LED (10/100/ 1000BASE-T port) on each port of the system are lit in orange or OFF "EPU:Disconnect"...
Page 79: Isolating Failures On External Power Unit
2.2.2 Isolating Failures on External Power Unit If the external power unit fails, follow the steps below to isolate the failure. Table 2-5: Isolating Failures on External Power Unit Failure POWER LED on the external power unit is lit in green POWER LED on the external power unit is OFF Table 2-6: Isolating Failures on External Power Unit (Main Body)
Page 80: Replacement Method Of System And Optional Components
Troubleshooting System Failures 2.2.3 Replacement Method of System and Optional Components The replacement procedures for optional components are described in "Hardware Installation Guide." Follow the procedures described in the manual.
Page 81: Troubleshooting Functional Failures In Operation
Troubleshooting Functional Failures in Operation This chapter describes actions to be taken when the system does not operate normally or the communication is not possible. 3.1 Problems on Login Password 3.2 Problems on MC 3.3 Problems on Operation Terminal 3.4 Network Interface Communication Failure 3.5 Layer 2 Network Communication Failure 3.6 IPv4 Network Communication Failure 3.7 IPv4 Unicast Routing Communication Failure...
Page 82 Troubleshooting Functional Failures in Operation 3.20 Problems on Redundant Configuration of Basic Switching Unit (BSU) [IP8800/S6700] 3.23 Communication Failure Caused by Settings of Filtering/QoS...
Page 83: Problems On Login Password
Problems on Login Password 3.1.1 Forgot the Login User Password If you forgot the login user password and cannot login to the system during operation, follow the procedure below. 1. Reporting to the system administrator First, consult the system administrator. However, if there is no login user eligible for the administrator (e.g., there is no other login user), perform a default restart and set a password again.
Page 84: Problems On Mc
If a fault still occurs after the MC has been replaced, memory slot card might be broken. In this case, replace the BCU [IP8800/S6700], the CSU [IP8800/S6600], the MSU [IP8800/S6300], the system [IP8800/S3600], or the system [IP8800/S2400]. displayed." Troubleshooting Steps When ACC LED is lit in green, it indicates other process might be accessing to MC.
Page 85: Problems On Operation Terminal
Problems on Operation Terminal 3.3.1 Unable to Input/Display from the Console Correctly When there is a problem connecting to the console, follow the instruction in Connecting to Console." When there is a problem connecting to the modem, follow the instruction in Connecting to Modem."...
Page 86: Login From The Remote Operation Terminal Is Failed
Troubleshooting Functional Failures in Operation Table 3-4: Problems and Actions When Connecting to Modem Failure Automatic termination to the modem is disabled. Abnormal characters are displayed upon login. Line is busy and cannot be connected by redialing after disconnection. Line cannot be reconnected after line failure. Line cannot be reconnected after disconnection.
Page 87: Login Authentication Using Radius/Tacacs+ Is Disabled
Symptom Key entry rejected. Some users remain in the login state. 3.3.3 Login Authentication Using RADIUS/TACACS+ Is Disabled If login authentication using RADIUS/TACACS+ is failed, check the following: 1. Communication with the RADIUS/TACACS+ server Use the ping command to see if communication from this system to the RADIUS/TACACS+ server is achieved. If it is not possible to communicate with the server, see address has been defined in configuration, check the connectivity between this system and RADIUS/ TACACS+ servers by issuing ping from the local address.
Page 88 Troubleshooting Functional Failures in Operation 3. Notes on writing command list Care must be taken about the handling of spaces when you describe the command list for the command authorization on this system on the RADIUS/TACACS+ server. For example, if show ip (show ip followed by a space) is set in the permitted command list, the show ip interface command is permitted but the show ipv6 interface command is prohibited.
Page 89: Network Interface Communication Failure
Network Interface Communication Failure 3.4.1 Ethernet Port Cannot Be Connected If the Ethernet port has possibly caused the communication failure, check for the NIF [IP8800/S6700] [IP8800/ S6600] [IP8800/S6300] and port statuses as follows. (1) Checking NIF status [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 1.
Page 90 Troubleshooting Functional Failures in Operation Table 3-7: Check and Action for Port Status Port Status Problem active up The port is operating normally. active down Line failure occurred in the port. inactive The inactive state is set by one of the following: •...
Page 91: Communication Failure In Basic Switching Unit Bsu/Psp
1/ 1 geth1/1 1/ 2 geth1/2 down 1/ 3 geth1/3 down (Omitted hereafter) > Figure 3-3: Example of "Checking Port Operation Status" [IP8800/S3600] [IP8800/S2400] > show port statistics 2006/03/23 12:00:00 Port Counts:48 Port Name Status 0/ 1 geth0/1 0/ 2...
Page 92: Actions Against Troubles On 10Base-T/100Base-Tx/1000Base-T
Troubleshooting Functional Failures in Operation BSU Operation Status fault Unavailable configuration has been set. The BSU/PSP is faulty. inactive The inactivate bsu command is set. [IP8800/S6700] The BSU is not fully inserted. Different type of BSUs are installed together. BSU not supported by the software version is installed.
Page 93 Table 3-9: Troubleshooting for Failed 10BASE-T/100BASE-TX/1000BASE-T Troubleshooting Steps According to the failure Line quality is statistical information degraded. displayed by the show interfaces command, check to see if the statistical information below is counted for the port. If counted, see "Problem" and "Action"...
Page 94: Actions Against Troubles On 1000Base-X
Troubleshooting Functional Failures in Operation Troubleshooting Steps According to the failure statistical information displayed by the show interfaces command, check to see if the statistical information below is counted for the port. If counted, see "Problem" and "Action" columns. • Long frames Check to see if statistics in the following is not counted by the show qos...
Page 95: Actions Against Troubles On 10Gbase-R
If counted, see "Problem" and "Action" columns. [IP8800/ S3600] [IP8800/S2400] • TX fault Check to see if the combination of transceivers is valid when using the 1 core optical cable such as 1000BASE-BX.
Page 96 Troubleshooting Functional Failures in Operation 2. Isolating the problem according to the failure analysis method Isolate the problem according to the failure analysis method listed below. Table 3-11: Failure Analysis Method for Troubles on 10GBASE-R Troubleshooting Steps According to the failure statistical information displayed by the show interfaces command, check to see if the...
Page 97: Communication Failure On Using Poe
Troubleshooting Steps According to the failure statistical information displayed by the show interfaces command, check to see if the statistical information below is counted for the port. If counted, see "Problem" and "Action" columns. [IP8800/S6700] [IP8800/S6600] [IP8800/ S6300] • RF According to the failure statistical information displayed by the show interfaces...
Page 98: Communication Failure On Using Link Aggregation
Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Check to see Threshold(W) and Allocate(W) by the show power inline command. Check to see if a fault occurs by the show logging command. 3.4.7 Communication Failure on Using Link Aggregation If communication is disabled or if degenerated operation is performed when link aggregation is in use, isolate the problem using the failure analysis methods listed in the following table.
Page 99 Troubleshooting Steps and Command Check the setting of failed port status using the show channel-group command with "detail" parameter specified. Troubleshooting Functional Failures in Operation Action Check the status of each port. If all ports in a link aggregation group are Down, the link aggregation group is also Down.
Page 100: Layer 2 Network Communication Failure
Troubleshooting Functional Failures in Operation Layer 2 Network Communication Failure 3.5.1 Layer 2 Communication by VLAN Is Disabled If layer 2 communication is disabled when using VLAN, isolate the problem using failure analysis method listed in the following table. (1) Checking VLAN status Execute the show vlan command or execute the show vlan command with "detail"...
Page 101 that the identical MAC address is set in the configuration and is disabled. # 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) (2) Checking port status • Execute the show vlan command with "detail" parameter specified, and confirm that the port is Up. If the port is Down, see 3.4 Network Interface Communication Failure "...
Page 102: Failures On Using Spanning Tree
MAC address learning limitation. In addition, check to see if the threshold in the Storm Control function is not too low. • IP8800/S3600 and IP8800/S2400: If the communication still has been blocked despite no display appears, check to see if the Suppress Port-to-Port Forwarding has been enabled.
Page 103: Failures On Using Ring Protocol
bridge for each MST instance for route bridge, when checking the route bridge. Table 3-14: Spanning Tree Failure Analysis Method Troubleshooting Steps and Command Execute the show spanning-tree command for the failed spanning tree and check the protocol status of the spanning tree. Execute the show spanning-tree command for the failed spanning tree and check the bridge identifier of the route bridge...
Page 104 Troubleshooting Functional Failures in Operation and isolate the problem. Figure 3-4: Analysis Flow Any failure on cable or hardware? Correct the problem Replace the faulty on hardware parts. configuration. When the Ring Protocol is not running normally or the ring network failure is detected, isolate the problem by following the failure analysis methods shown in the table below for all the nodes configuring the ring network.
Page 105 Troubleshooting Steps and Command Execute the show axrp command to check the ring port for each VLAN group and its operation state. Execute the show axrp detail command to check the control VLAN Execute the show axrp detail command to check the VLAN ID which belongs to the VLAN group.
Page 106: Multicast Relay By Igmp Snooping Is Disabled
Troubleshooting Functional Failures in Operation 3.5.4 Multicast Relay by IGMP snooping Is Disabled If multicast relay is disabled when using IGMP snooping, follow the analysis flow to identify the symptom using steps shown in the table below and isolate the problem. Figure 3-5: Analysis Flow Is there log information? Is filter setting correct?
Page 107 Table 3-16: Troubleshooting on Multicast Relay Troubleshooting Steps and Command Use the show logging command to check if any failure occurs. Check if filtering and QoS are set correctly. Check the settings of IPv4 multicasts if you want to use IPv4 multicast at the same time.
Page 108 Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Check the IGMP snooping configuration using the show igmp-snooping command. Execute the show igmp-snooping command with "group" parameter specified, and check IPv4 multicast group address. * If this system is the IGMP querier, the address displayed in "IGMP querying system" matches the address displayed in "IP Address";...
Page 109: Multicast Relay By Mld Snooping Is Disabled
3.5.5 Multicast Relay by MLD snooping Is Disabled If multicast relay is disabled when using MLD snooping, follow the analysis flow to identify the symptom using steps shown in the table below and isolate the problem. Figure 3-6: Analysis Flow Analysis Flow Is there log information? Is filter setting correct?
Page 110 Troubleshooting Functional Failures in Operation Table 3-17: Troubleshooting on Multicast Relay Troubleshooting Steps and Command Use the show logging command to check if any failure occurs. Check if filtering and QoS are set correctly. Check the settings of IPv6 multicasts if you want to use IPv6 multicast at the same time.
Page 111 Troubleshooting Steps and Command Check the MLD snooping configuration using the show mld-snooping command. Execute the show mld-snooping command with "group" parameter specified, and check IPv6 multicast group address. * If this system is the MLD querier, the address displayed in "MLD querying system" matches the address displayed in "IP Address";...
Page 112: Ipv4 Network Communication Failure
Troubleshooting Functional Failures in Operation IPv4 Network Communication Failure 3.6.1 Communication Is Disabled or Is Disconnected There are three possible causes that result in communication failure on the IPv4 network using this system. 1. Configuration on IP communication has changed 2.
Page 113 Figure 3-7: Failure Analysis Procedure When IPv4 Communication Disabled <IPv4 communication is disabled.> Verify if there is a line failure log message. No line failure log message exists. Check the Up/Down status of the interface. down Identify the extent of the failure using the ping command.
Page 114 Troubleshooting Functional Failures in Operation (2) Checking interface status It is also possible that a failure has occurred on the hardware of the neighboring system connected to this system even if the hardware on this system is running properly. The procedure for checking the status of interface between this system and the neighboring system is described below. 1.
Page 115 (6) Checking unicast routing information Check the route information acquired by this system if communication is not possible even when the address resolution with the neighboring system is achieved, or if communication is disabled in the midway to the other party during IPv4 unicast communication, or if the route to the other party is abnormal.
Page 116: Ip Addresses Cannot Be Assigned Using Dhcp Function
Troubleshooting Functional Failures in Operation 3.6.2 IP Addresses Cannot Be Assigned Using DHCP Function (1) DHCP/BOOTP relay communication failure There are three possible causes for DHCP/BOOTP relay communication failures: 1. Configuration relating to DHCP/BOOTP relay has changed 2. Network configuration has changed 3.
Page 117 (a) Checking the log and interface On possible cause for the server not assigning IP addresses to clients, communication between client and server may have been disabled. Check the log displayed on this system or the interface up/down status using the show ip interface command.
Page 118 Troubleshooting Functional Failures in Operation 2. Execute the show ip route command to check the route information acquired by this system. 3. Go to "3.7 IPv4 Unicast Routing Communication in the route information acquired by this system or if the next hop address is invalid. 4.
Page 119 Figure 3-9: DHCP Server Failure Analysis Procedure <IP addresses cannot be assigned to clients.> Check the configuration. Verify the failure occurrence using the show logging command and the show ip interface command. No failure on this system (Connected directly)( "(1)DHCP/BOOTP relay communication Verify the setting information of filter and QoS.
Page 120: Dynamicdns Cooperation In Dhcp Function Is Disabled
Troubleshooting Functional Failures in Operation communication to the other party cannot be verified with the ping command, use ping to check communication toward clients starting from the system closest to this system. For an example of issuing ping and how to interpret the result, see the manual "Configuration Settings."...
Page 121 Figure 3-10: Troubleshooting for DHCP Server Failure with DNS Cooperation <DNS update disabled> Check the configuration. Verify if there is a failure occurrence using the show logging command and the show ip interface command. No failure on this system (Connected directly) Verify the failure occurrence on other devices.
Page 122 Troubleshooting Functional Failures in Operation (d) Identifying the extent of the failure (performed from this system) If no failure is found on this system, a failure may exist somewhere in the route between this system and the remote system. The procedure to locate the failure in the route to the remote system and identify the failure range is as follows: 1.
Page 123: Ipv4 Unicast Routing Communication Failure
IPv4 Unicast Routing Communication Failure 3.7.1 No RIP Routing Information Exists Isolate the problem according to the failure analysis method listed below if RIP route information does not exist in the displayed route information acquired by this system. Besides, when the upper limit of routing is set by configuration command maximum routes, see Information Exist [OP-NPAR]."...
Page 124: No Bgp4 Routing Information Exists
Troubleshooting Functional Failures in Operation 3.7.3 No BGP4 Routing Information Exists Isolate the problem according to the failure analysis method listed below if BGP4 route information does not exist in the displayed route information acquired by this system. Besides, when the upper limit of routing is set by configuration command mazimum routes, see Information Exist [OP-NPAR]."...
Page 125: Ipv4 Multicast Routing Communication Failure
IPv4 Multicast Routing Communication Failure Actions to be taken if IPv4 multicast communication failures occur on this system are described below. 3.8.1 Communication on IPv4 PIM-SM Network Is Disabled If multicast relay is disabled in the IPv4 PIN-SM network configuration, isolate the cause according to the failure analysis method below.
Page 126: Show Ip Route
Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Confirm in the configuration that suppression of protocol packet and multicast packet relay through filtering, etc. is not provided on the interface that allows PIM and IGMP to run. show running-config Check the PIM neighboring information.
Page 127 Table 3-23: BSR Check Items Troubleshooting Steps and Command Confirm that this system is a candidate for BSR. show ip pim bsr Confirm that this system is BSR. show ip pim bsr (3) Rendezvous point router check items The table below shows the items to be checked when this system is the rendezvous point router in the IPv4 PIM-SM network configuration.
Page 128: Multicast Data Is Double-Relayed On Ipv4 Pim-Sm Network
Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Check to see if IGMP snooping is set to the port in which static group join function is working. show igmp-snooping Confirm that no interface in abnormal state is detected. show ip igmp interface (5) first-hop-router check items The table below shows the items to be checked when this system is the first-hop-router in the IPv4 PIM-SM network configuration.
Page 129: Communication On Ipv4 Pim-Ssm Network Is Disabled
Table 3-27: Check Items When Double-relay Continues Troubleshooting Steps and Command Check the PIM neighboring information on the interface of the network having multiple routers. show ip pim neighbor 3.8.3 Communication on IPv4 PIM-SSM Network Is Disabled If multicast relay on the IPv4 PIN-SSM network configuration is disabled, isolate the cause according to the failure analysis method below.
Page 130 Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Confirm that IGMP snooping is set to the interface with PIM enabled. show igmp-snooping Confirm in the configuration that suppression of protocol packet and multicast packet relay through filtering, etc. is not provided on the interface that allows PIM and IGMP to run.
Page 131: Multicast Data Is Double-Relayed On Ipv4 Pim-Ssm Network
Troubleshooting Steps and Command If there is an interface in which the relay target group participates, confirm that this system is DR. show ip pim interface Confirm that IGMP snooping is set to the interface with static group join function enabled. show igmp-snooping Confirm that no interface in abnormal state is detected.
Page 132: Ipv4 Multicast Communication Failure In Vrf [Op-Npar]
Troubleshooting Functional Failures in Operation Table 3-31: Check Items When Double-relay Continues Troubleshooting Steps and Command Check the PIM neighboring information on the interface of the network having multiple routers. show ip pim neighbor 3.8.5 IPv4 Multicast Communication Failure In VRF [OP-NPAR] If IPv4 multicast communication failure still continues, check the following: Table 3-32: Check Items for VRF Troubleshooting Steps and Command...
Page 133: Ipv6 Network Communication Failure
IPv6 Network Communication Failure 3.9.1 Communication Is Disabled or Is Disconnected There are three possible causes that result in communication failure on the IPv6 network using this system. 1. Configuration on IPv6 communication has changed 2. Network configuration has changed 3.
Page 134 Troubleshooting Functional Failures in Operation (1) Checking the log and interface Communication may be interrupted by a line failure (or damage) or a neighboring system failure. Check the log displayed on this system or the interface up/down status using the show ipv6 interface command. For the procedure, see 3.6.1 Communication Is Disabled or Is "...
Page 135: Ipv6 Dhcp Troubleshooting
1. Log in to the system. 2. Execute show ipv6 route command to check the route information acquired by this system. 3. For IP8800/S6700, IP8800/S6600, and IP8800/S6300, check to see if packets are discarded because of the Null interface. If the route information sending interface resulting a communication failure is null0, packets are discarded because of the Null interface.
Page 136 Troubleshooting Functional Failures in Operation Figure 3-14: IPv6DHCP Server Failure Analysis Procedure <Unable to distribute the configuration.> Verify the operation log using the show logging command. No physical failure message exists. Check the Up/Down status of the interface using the show ipv6 interface command.
Page 137 Check the number of remaining prefixes that can be distributed from the IPv6DHCP server using the show ipv6 dhcp server statistics command. For the instructions, see "Configuration Settings." If the distributable number of prefixes is 0, increase the number of prefixes to be distributed. The prefixes can be distributed up to 1024. (c) Procedure to check configuration 1.
Page 138 Troubleshooting Functional Failures in Operation detail command, it is necessary to match the displayed DUIDs and client systems. To do that, compare the value of distributed prefixes displayed in the binding information and the information of prefixes distributed to client system.
Page 139 Table 3-34: Retention of Route Information to Prefix Distribution Target Retention Information Concerning Prefix Server Function Restart Command Execution Route information to client (Legend) Y: Guaranteed Y/N: Not guaranteed (each status information may be retained) N: Not guaranteed (re-setting required because of initialization) Note Route management functions required when setting route information to prefix distribution target.
Page 140 Troubleshooting Functional Failures in Operation (c) Checking the DUID You can check the DUID in the "< Server DUID >" section of the output of the command. For details, see "Configuration Settings." statistics show ipv6 dhcp server...
Page 141: 3.10 Ipv6 Unicast Routing Communication Failure
3.10 IPv6 Unicast Routing Communication Failure 3.10.1 No RIPng Routing Information Exists Isolate the problem according to the failure analysis method listed below if RIPng route information does not exist in the displayed route information acquired by this system. Table 3-35: Failure Analysis of RIPng Troubleshooting Steps and Command RIPng neighboring information is displayed.
Page 142: No Bgp4+ Routing Information Exists
Troubleshooting Functional Failures in Operation 3.10.3 No BGP4+ Routing Information Exists Isolate the problem according to the failure analysis method listed below if BGP4+ route information does not exist in the displayed route information acquired by this system. Table 3-37: BGP4+ Failure Analysis Method Troubleshooting Steps and Command Check the BGP4+ peer status.
Page 143: 3.11 Ipv6 Multicast Routing Communication Failure
3.11 IPv6 Multicast Routing Communication Failure Actions to be taken if IPv6 multicast communication failures occur on this system are described below. 3.11.1 Communication on IPv6 PIM-SM Network Is Disabled If multicast relay on the IPv6 PIN-SM network configuration is disabled, isolate the cause according to the failure analysis method below.
Page 144 Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Confirm in the configuration that suppression of protocol packet and multicast packet relay through filtering, etc. is not provided on the interface that allows PIM and MLD to run. show running-config Check the PIM neighboring information.
Page 145 Table 3-39: BSR Check Items Troubleshooting Steps and Command Confirm that this system is a candidate for BSR. show ipv6 pim bsr Confirm that this system is BSR. show ipv6 pim bsr (3) Rendezvous point router check items The table below shows the items to be checked when this system is the rendezvous point router in the IPv6 PIM-SM network configuration.
Page 146: Multicast Data Is Double-Relayed On Ipv6 Pim-Sm Network
Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Confirm that MLD snooping is set to the interface with PIM enabled. show mld-snooping Confirm that no interface in abnormal state is detected. show ipv6 mld interface (5) first-hop-router check items The table below shows the items to be checked when this system is the first-hop-router in the IPv6 PIM-SM network configuration.
Page 147: Communication On Ipv6 Pim-Ssm Network Is Disabled
3.11.3 Communication on IPv6 PIM-SSM Network Is Disabled If multicast relay on the IPv6 PIN-SSM network configuration is disabled, isolate the cause according to the failure analysis method below. The figure below illustrates a network example of IPv6 PIM-SSM. Figure 3-17: Example of IPv6 PIM-SSM Network Multicast sender first-hop-router...
Page 148 Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Check to see if the unicast route to the multicast data sender exists. show ipv6 route Confirm that PIM is running on the sending interface for the unicast route to the multicast data sender. show ipv6 pim interface Confirm that the PIM-SSM group addresses contain the relay target group address, referring to the configuration.
Page 149: Multicast Data Is Double-Relayed On Ipv6 Pim-Ssm Network
Troubleshooting Steps and Command Check to see if IGMP snooping is set to the port in which static group join function is running. show mld-snooping Confirm that no interface in abnormal state is detected. show ipv6 mld interface (3) first-hop-router check items The table below shows the items to be checked when this system is the first-hop-router in the IPv6 PIM-SSM network configuration.
Page 150 Troubleshooting Functional Failures in Operation Table 3-47: Check Items When Double-relay Continues Troubleshooting Steps and Command Check the PIM neighboring information on the interface of the network having multiple routers. show ipv6 pim neighbor Action If the neighboring router is not displayed, check the following: •...
Page 151: 3.12 Layer 2 Authentication Communication Failure
3.12 Layer 2 Authentication Communication Failure 3.12.1 Communication Failure on Using IEEE 802.1X If authentication is disabled when using IEEE 802.1X, isolate the problem by following failure analysis methods shown in the table below. Table 3-48: IEEE 802.1X Failure Analysis Method Troubleshooting Steps and Command Execute the show dot1x command and check the operation status of the...
Page 152 Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Execute the show dot1x logging command and check to see if authentication failed. Action • If "New Supplicant Auth Fail." is output, authentication failed due to the following cause. Check to see if there is any problem. (1) User ID or password is not registered on the authentication server.
Page 153 (dynamic) failed. If communication is not possible on the port or VLAN on which IEEE 802.1X runs, isolate the problem by following failure analysis methods shown in the table below. Otherwise, see [IP8800/S3600] [IP8800/S2400] Troubleshooting Functional Failures in Operation Action •...
Page 154: Communication Failure On Using Web Authentication
URL redirect is enabled by configuration command web-authentication redirect enable. - When URL redirect is enabled in IP8800/S3600 or IP8800/S2400 models, check to see if IP address dedicated for Web authentication configured web-authentication ip address.
Page 155 • For IP8800/S3600 and IP8800/S2400 models, even though the dead interval lets RADIUS server get recovered from no-response state and become able to communicate, the system is not able to collate...
Page 156 Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Execute the show web-authentication logging command to check to see if the system operates correctly. If no account is recorded in the accounting server, use the show web-authentication statistics command to check the communication status with the accounting server.
Page 157 <when static vlan mode is set> • web-authentication ip address • web-authentication port • web-authentication static-vlan max-user • web-authentication web-port When you use IP8800/S3600 or IP8800/S2400, confirm the settings by using the following commands. • authentication arp-relay • authentication ip access-group • web-authentication redirect enable •...
Page 158 Check to see the settings of syslog server. Troubleshooting Steps When using IP8800/S3600 or IP8800/S2400 model in static VLAN mode, confirm that the filter condition permits pre-authenticated terminals to send packets out of the system by the configuration command authentication ip access-group or ip access-list extended.
Page 159: Communication Failure On Using Mac Authentication
• For IP8800/S3600 and IP8800/S2400 models, even though the dead interval lets RADIUS server get recovered from no-response state and become able to communicate, the system is not able to collate...
Page 160 Action • For IP8800/S6700, IP8800/S6600, and IP8800/S6300 models, go to No.6. • For IP8800/S3600 and IP8800/S2400 models, if pre-authenticated terminal sends packets out of the system, confirm that authentication IPv4 access list is applied. If access list and authentication IPv4 access list both are applied to the port for authentication, make sure the filter conditions described in IPv4 access list are set in the access list as well.
Page 161: Communication Failure On Using Authentication Vlan [Op-Vaa]
• mac-authentication radius-server host • mac-authentication static-vlan max-user • mac-authentication system-auth-control When using IP8800/S3600 or IP8800/S2400 model in static VLAN mode, confirm that the filter condition permits pre-authenticated terminals to send packets out of the system is set by the configuration command authentication ip access-group or ip access-list extended.
Page 162 Troubleshooting Functional Failures in Operation Table 3-56: Authentication VLAN Failure Analysis Method Troubleshooting Steps and Command Execute the show logging command and check to see if hardware failures are recorded in the operation log. Execute the show fense server command and confirm that the system runs normally.
Page 163 Troubleshooting Steps and Command Execute the show vlan mac-vlan command and confirm that the authenticated MAC address is registered in the MAC VLAN function. Execute the show fense logging command and confirm that exchange with the authentication server is performed. For the configuration relating to the authentication VLAN, check the following.
Page 164 Troubleshooting Functional Failures in Operation Check Point Setting of DHCP relay agent Filter setting Troubleshooting Steps Confirm that the following inter-VLAN DHCP relay agent is set correctly: • Between pre-authentication VLAN and authentication server VLAN • Between post-authentication VLAN and authentication server VLAN Confirm that the following inter-VLAN filter is set correctly: •...
Page 165: 3.13 Communication Failure On High-Reliability Function
3.13 Communication Failure on High-reliability Function 3.13.1 GSRP Communication Failures If the communication is not possible in the GSRP configuration, isolate the problem according to the failure analysis method shown in the table below. Table 3-58: Analysis Method for Communication Failure in GSRP Configuration Troubleshooting Steps and Command On this system and remote system constituting a GSRP group, check the status...
Page 166 Troubleshooting Functional Failures in Operation Table 3-59: Analysis Method for Abnormal Status in GSRP Configuration Troubleshooting Steps and Command Check the status of the VLAN group in which master/backup is not switched as expected, using the show gsrp command. Check to see if the master/backup selection method (Selection-Pattern), the number of active ports (Active-Ports) on this system and the remote system, the priority information...
Page 167: Communication With Vrrp Configuration In Ipv4 Network Is Disabled
3.13.2 Communication with VRRP Configuration in IPv4 Network Is Disabled Isolate the problem according to the failure analysis methods shown in the table below if communication with the VRRP configuration is disabled. Table 3-61: VRRP Failure Analysis Method Troubleshooting Steps and Command Check the status of the remote systems and this system constituting a same virtual router and confirm that one system is used as a...
Page 168 Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Execute the show logging command and the show vrrpstatus command with "statistics" parameter specified to check the receiving status of the ADVERTISEMENT packets. Check the statistical information of the physical port to which the remote system constituting the same virtual router is connected using the show interfaces command.
Page 169: Communication With Vrrp Configuration In Ipv6 Network Is Disabled
Troubleshooting Steps and Command Execute show vrrpstatus command with "detail" parameter specified to confirm that the virtual router status is not "Initial." 3.13.3 Communication with VRRP Configuration in IPv6 Network Is Disabled Isolate the problem according to the failure analysis methods shown in the table below if communication with the VRRP configuration is disabled.
Page 170 Troubleshooting Functional Failures in Operation Troubleshooting Steps and Command Execute the show vrrpstatus command with "statistics" parameter specified to check the receiving status of ADVERTISEMENT packets. Check the statistical information of the physical port to which the remote system constituting the same virtual router is connected using the show interfaces command.
Page 171 Troubleshooting Steps and Command Execute show vrrpstatus command with "detail" parameter specified to check the virtual router status. Troubleshooting Functional Failures in Operation Action If the virtual router is set to "Initial," check the following items: • If the current priority is not set to zero (0), delete the non-operation factors displayed in the "Admin State"...
Page 172: 3.14 Snmp Communication Failure
Troubleshooting Functional Failures in Operation 3.14 SNMP Communication Failure 3.14.1 MIBs Cannot Be Obtained from SNMP Manager Confirm that the configuration has been set correctly. When using SNMPv1 or SNMPv2C Execute the show access-list command to confirm that the IP address of the SNMP manager has been registered on the access list in the configuration.
Page 173 When using SNMPv3 Execute the show snmp-server command to confirm that the information on the SNMP manager and trap has been registered in the configuration for this system. If it is not correctly registered, execute the configuration command below to set up the information on the SNMP manager and trap. •...
Page 174: Troubleshooting Of Sflow Statistics (Flow Statistics) Function
Troubleshooting Functional Failures in Operation 3.15 Troubleshooting of sFlow Statistics (Flow Statistics) Function The flow for troubleshooting of sFlow statistics function in this system is as follows. Figure 3-18: Troubleshooting Flow of sFlow Statistics Function Checking route to the collector. Checking operation status by operation command.
Page 175 2093(2041) Exported sFlow samples : 37269 sFlow collector data : Collector IP address: 192.168.4.199 UDP:6343 Source IP address: 130.130.130.1 Send FlowSample UDP packets Send CounterSample UDP packets: Collector IP address: 192.168.4.203 UDP:65535 Source IP address: 130.130.130.1 Send FlowSample UDP packets Send CounterSample UDP packets: >...
Page 176 Troubleshooting Functional Failures in Operation Figure 3-23: Display Example of Configuration 3 (config)# show interfaces interface gigabitethernet 1/2 switchport mode access sflow forward ingress (config)# • See "3.23.1 Checking Filtering/QoS Setting port subject to flow statistics. • Specifying Source IP address for sFlow packets with "sflow source," check to see if the IP address is assigned to the port of this system.
Page 177: Flow Sample Does Not Reach Collector
3.15.2 Flow Sample Does Not Reach Collector If problem still persists even after checking (1) Checking presence/absence of the relay packet Execute the show interfaces command to check to see if the packet is relayed. Figure 3-26: Display Example of Port Status >...
Page 178: Communication Failures On Neighboring System Managing Function
Troubleshooting Functional Failures in Operation 3.16 Communication Failures on Neighboring System Managing Function 3.16.1 Unable to Obtain Neighboring System Information via LLDP Function If it is not possible to acquire correctly neighbor system information with LLDP functions, isolate the problem using the failure analysis method shown in the table below.
Page 179 Troubleshooting Steps and Command Execute the show oadp command to check the port information displayed. Execute the show oadp statistics command to check for the statistics on the port to which the neighboring system is connected. Execute the show interfaces command to check the status of the port to which the neighboring system is connected.
Page 180: 3.17 Ntp Communication Failure
Troubleshooting Functional Failures in Operation 3.17 NTP Communication Failure 3.17.1 Time Synchronization by NTP Is Disabled If time synchronization by NTP is disabled, isolate the problem by following the failure analysis methods shown in the table below. Table 3-65: NTP Failure Analysis Method Troubleshooting Steps and Command Execute the show clock command to see if a time zone has been set up.
Page 181: Communication Failure On Ieee802.3Ah/Udld Function
3.18 Communication Failure on IEEE802.3ah/UDLD Function 3.18.1 Port Becomes Inactive Due to IEEE802.3ah/UDLD Function If the port becomes inactive due to IEEE802.3ah/UDLD function, isolate the problem by following failure analysis methods shown in the table below. Table 3-66: Failure Analysis Method When IEEE802.3ah/UDLD Function Is in Use Troubleshooting Steps and Command Use the show efmoam command to check the failure type of the port which becomes inactive...
Page 182: Problems On Redundant Configuration Of Basic Control Unit (Bcu)/Control And Switching Unit (Csu)/Management And Switching Unit (Msu) [Ip8800/S6700] [Ip8800/S6600] [Ip8800/S6300]
Troubleshooting Functional Failures in Operation 3.19 Problems on Redundant Configuration of Basic Control Unit (BCU)/Control and Switching Unit (CSU)/Management and Switching Unit (MSU) [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 3.19.1 Active System Switchover Is Disabled If switch between the active system and standby system is disabled, follow instructions in the table below. Table 3-67: Problems and Actions When Switching Active System Cause for Switchover Disabled The standby system is not...
Page 183: Problems On Redundant Configuration Of Basic Switching Unit (Bsu) [Ip8800/S6700]
3.20 Problems on Redundant Configuration of Basic Switching Unit (BSU) [IP8800/S6700] 3.20.1 Active BSU Switchover Is Disabled If BSU cannot be switched in the redundant configuration, follow the instruction shown below. 1. Checking log For the log, see the manual "Message Log Reference." 2.
Page 184 Troubleshooting Functional Failures in Operation BSU Operation Status notconnect The BSU is not installed. initialize The BSU is being initialized. disable no power enable is set by configuration command. Problem Check if as many BSU boards as required for active BSU + standby BSU (if standby BSU is not required, only active BSU) are installed.
Page 185: 3.21 Problems On Power Saving Feature
3.21 Problems on Power Saving Feature 3.21.1 Schedule Is Disabled [IP8800/S6700] [IP8800/S6600] If schedule is disabled, follow the instruction shown below. 1. Check to see if the current time is included in the displayed schedule by using the show power-control schedule command, and isolate the problem according to the table below.
Page 186: Congestion Caused By Packets Processed Through Cpu Is Not Recovered
Troubleshooting Functional Failures in Operation 3.22 Congestion Caused by Packets Processed Through CPU Is Not Recovered This section describes the procedure when congestion caused by packets requiring the handling of CPU is not recovered. When a large amount of the packets requiring software process are received, the overflow on the receiving queue to CPU will cause the packet congestion.
Page 187 [IP8800/S6600] [IP8800/S6300] • Execute the show tech-support command for two times. [IP8800/S3600] [IP8800/S2400] Note • When executing the dump bsu command or the dump psp command, do not execute the next command until the log appears indicating memory dump file collection has been completed.
Page 188: Communication Failure Caused By Settings Of Filtering/Qos
Troubleshooting Functional Failures in Operation 3.23 Communication Failure Caused by Settings of Filtering/QoS 3.23.1 Checking Filtering/QoS Setting Information As a cause for communication failure on the network using this system, certain packets may have been discarded by filtering or packets may have been discarded through bandwidth monitoring, discarding control, or shaper of the QoS control.
Page 189 IP8800/S3600 and IP8800/S2400 1. Log in to the system. 2. Check the "discard packets" statistical information of the output interface using the show qos queueing command. 3. If the statistical information identified in step 2 is incremented, packets are discarded through discarding control and shaper of QoS control.
Page 191: Troubleshooting Communication Failures Due To Resource Shortage [Ip8800/S6700] [Ip8800/S6600] [Ip8800/S6300]
Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 4.1 MAC Address Table Resource Shortage 4.2 When Resource Shortage of VLAN Identification Table Occurs 4.3 When Resource Shortage Occurs in Shared Memory...
Page 192: Mac Address Table Resource Shortage
Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] MAC Address Table Resource Shortage 4.1.1 Checking Resource Usage of MAC Address Table This system outputs operation log messages when the MAC address table usage reaches 80% and 100% of the accommodating condition.
Page 193 Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] Trigger Web authentication (Static VLAN mode) MAC authentication * The log message of No. 1 may be output at the same time. If these log messages are output, the function that newly uses the MAC address table cannot be set. Review the network configuration and set the configuration allowing for operation below the limit of the system's accommodating condition.
Page 194 Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] *1 For details, see the manual "Operation Commands." *2 For details, see the manual "Configuration Commands."...
Page 195: When Resource Shortage Of Vlan Identification Table Occurs
Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] When Resource Shortage of VLAN Identification Table Occurs 4.2.1 Checking VLAN Identification Table Resource Usage This system outputs an operation log message when the usage of VLAN identification table reaches 80% of the accommodating condition.
Page 196 Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] If these log messages are output, the function that newly uses the VLAN identification address table cannot be set. Review the network configuration and set the configuration allowing for operation below the limit of the system's accommodating condition.
Page 197: When Resource Shortage Occurs In Shared Memory
Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] When Resource Shortage Occurs in Shared Memory 4.3.1 Checking Resource Usage of Shared Memory Shared memory usage can be checked with the show system command. # show system Shared resources Used/Max: 0B/1638400B IPv4 Unicast Single-path used : 0B IPv4 Unicast Multi-path used : 0B IPv6 Unicast Single-path used : 0B...
Page 199: Collecting Failure Information
Collecting Failure Information This chapter focuses on collecting the failure information. 5.1 Collecting Failure Information 5.2 Transferring Files for Maintenance Information 5.3 Writing to MC...
Page 200: Collecting Failure Information
Collecting Failure Information Collecting Failure Information The information on failures can be collected at once using the show tech-support command. This command can also transfer the collected failure information to a specified ftp server (see Files Using show tech-support Command"). Memory dump at failure occurrence time can be collected by using the dump command.
Page 201 Figure 5-1: Collecting Failure Information from the Remote Operation Terminal Collecting basic information client-host> ftp 192.168.0.60 Connected to 192.168.0.60. 220 192.168.0.60 FTP server (NetBSD-ftpd) ready. Name (192.168.0.60:staff1): staff1 331 Password required for staff1. Password: 230 User staff1 logged in. Remote system type is UNIX. Using binary mode to transfer files.
Page 202: Ip8800/S6300]
Collecting Failure Information 5.1.2 Collecting Failure Information Using dump Command [IP8800/ S6700] [IP8800/S6600] [IP8800/S6300] (1) Collecting memory dump when communication failure occurs When any communication failure occurs, collect memory dump by executing all of the following commands.The collected memory dump files are stored under /dump0 in the system where the command is executed. Delete the memory dump file after collecting it.
Page 203 2. Execute the dump nif command for the faulty port from the active system. [Example] The following is an example when communication failure occurs in NIF number 1 and port number 1. 1. Login the active system and execute the dump command. >...
Page 204 Collecting Failure Information For IP8800/S6600 1. Execute the dump psp command for active PSP from the active system. 2. Execute the dump nif command for all faulty ports from the active system. 3. Execute the dump psp standby command for the standby PSP from the active system. 4.
Page 205 3. After above log is displayed, execute next dump command. > dump psp standby Dump command accept. > 11/01 18:18:42 E3 MSU 25070700 2301:000000000000 PSP online dump command executed. 4. After above log is displayed, login the standby system and execute next dump command. SBY:>...
Page 206: Transferring Files For Maintenance Information
This section describes how to transfer log information or dump information automatically stored when failure occurred while operating to the console or remote operation terminal. Three commands are available, that is, ftp, zmodem [IP8800/S3600] [IP8800/S2400], and show tech-support. Maintenance information includes the following items.
Page 207: Transferring Files Using Ftp Command
***: Serial number assigned from when dump was collected. Up to two files, the [IP8800/S3600] oldest and latest files, are stored. [IP8800/S2400] Delete the files after transfer. Log information Stored with the following name depending on the collected directory (see 5-3: Transferring Log Information Files to the Remote Operation Operation log: log.txt...
Page 208 Collecting Failure Information 2. Specify the address of target. 3. Changes the interaction mode. 4. Enter binary mode.* 5. Specify the target directory. 6. Transfers the dump file. Be sure to transfer dump files in binary mode. The correct dump information will not be obtained if dump files are transferred in ASCII mode.
Page 209 (3) Transferring failure backup information files to the remote operation terminal Figure 5-4: Transferring the Failure Backup Information File to the Remote Operation Terminal > cd /usr/var/core/ > ls <-------------------------1 nimd.core nodeInit.core > ftp 192.168.0.1 Connected to 192.168.0.1. 220 FTP server (Version 6.00LS) ready. Name (192.168.0.1:staff1): staff1 331 Password required for staff1.
Page 210: Transferring Files Using Zmodem Command [Ip8800/S3600] [Ip8800/S2400]
Collecting Failure Information 5.2.2 Transferring Files Using zmodem Command [IP8800/S3600] [IP8800/S2400] To transfer files between this system and the console connected via RS232C cable, the zmodem command is used. Before starting communication, prepare the communication program on the console for receiving.
Page 211 6. Specify a file name. 7. Select whether to collect dump files of standby system. Figure 5-9: Transferring Maintenance Information Files to the Remote Operation Terminal or Remote Host [IP8800/S3600] [IP8800/S2400] > show tech-support ftp Specify Host Name of FTP Server.
Page 212: Transferring Files Using Ftp Command From The Operation Terminal
Collecting Failure Information Operation normal end. ########## Dump files' Information ########## ***** ls -l /dump0 ***** total 2344 -rwxrwxrwx 1 root wheel 2400114 Dec 8 16:46 rmdump ***** ls -l /usr/var/hardware ***** -rwxrwxrwx 1 root wheel 264198 Dec 8 16:43 ni00.000 ########## End of Dump files' Information ########## ########## Core files' Information ########## ***** ls -l /usr/var/core *****...
Page 213 Figure 5-10: Collecting Dump Files from the Remote Terminal client-host> ftp 192.168.0.60 Connected to 192.168.0.60. 220 192.168.0.60 FTP server (NetBSD-ftpd) ready. Name (192.168.0.60:staff1): staff1 331 Password required for staff1. Password: 230 User staff1 logged in. Remote system type is UNIX. Using binary mode to transfer files.
Page 214: Writing To Mc
Collecting Failure Information Writing to MC The failure and maintenance information can be written to MC. Note that MC is subject to the capacity limit. 5.3.1 Writing File to MC Using Operation Terminal When writing the system information to MC, use the operation terminal. Figure 5-11: Writing Information to MC Insert MC to which the information is written.
Page 215: Line Test
Line Test 6.1 Testing Line...
Page 216: Testing Line
In this test, test frame loops back in this system to check for the NIF failure [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] and system failure (excluding RJ45 connector and transceivers) [IP8800/3600] [IP8800/S2400]. This test is available for all line types.
Page 217 S6300]," the no test interfaces command [IP8800/S6700] [IP8800/S6600] [IP8800/S3600], 6-3: Execution Result Example of the test interfaces command and the no test interfaces command [IP8800/S3600] [IP8800/S2400]," and the no test interfaces Command [IP8800/S3600] [IP8800/2400] are displayed. Check the following: "Send-NG" and "Receive-NG" are 0.
Page 218 [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] and system failure (including RJ45 connector and transceivers) [IP8800/S3600] [IP8800/S2400]. This test is available for all line types. For each line type, remove the cable of the test target port number and connect the loop connector for each line type to execute the test.
Page 219 > no test interfaces gigabitethernet 0/1 (Remove the loop connector from the corresponding port and restore the connection.) > activate gigabitethernet 0/1 Check the test execution result in the same way for the test execution result of system." [Enter] [Enter] "(1)Checking frame loopback within Line Test...
Page 221: Restarting The System
Restarting the System This chapter describes the procedures for restarting the system. 7.1 Restarting the System...
Page 222: Restarting The System
Restarting the System Restarting the System 7.1.1 Restarting the System The system can be restarted by using the reload command. Log is stored at restart time. For input format and parameter of the command, see the manual "Operation Commands." IP8800/S6700, IP8800/S6600, and IP8800/S6300 The following is an example showing how to select the parameter of the reload command when "restarting the standby system"...
Page 223 As CPU memory dump is collected in Step 2, no parameter is selected as shown in figure above. Step3 At last, select which system is restarted or stopped. Figure 7-3: Selecting the System to Be Restarted or Stopped Specifying the active system Parameter to input Active...
Page 224 Memory dump? Restarting after overwriting memory dump IP8800/S3600 and IP8800/S2400 The following is an example showing how to select the parameter of the reload command when restarting the system and collecting the CPU memory dump according to the confirmation message. Step1 Select whether to restart or stop the system.
Page 225 Next, select whether to collect the dump. Figure 7-6: Selecting CPU Memory Dump Type Collecting memory dump dump-image Parameter to input As memory dump is collected in Step 2, no parameter is selected as shown in figure above. Combining parameters selected in Step 1 and Step 2 results in "reload ." Entering this command outputs the dump collection confirmation message as shown below.
Page 226 Restarting the System Figure 7-7: CPU Memory Dump Collection Confirmation Message Memorydump is already collected 2. Delete existing memory dump? Restarting after overwriting memory dump 1. Collect memory dump? 3. Restart? Restarting without collecting memory dump 2. Delete existing Restarting after collecting memory RM dump? dump...
Page 227: Appendix
Appendix Appendix A Contents of show tech-support Command Display...
Page 228: Appendix A Contents Of Show Tech-Support Command Display
Appendix A Contents of show tech-support Command Display Appendix A Contents of show tech-support Command Display Appnedix A.1 Contents of show tech-support Command Display The contents of the show tech-support command displayed for each protocol parameter are shown in the table below.
Page 229 Command (Display) show netstat all-protocol-address numeric show netstat statistics show dumpfile ls -lTiR /dump0 ls -lTiR /usr/var/hardware ls -lTiR /usr/var/core ls -lTiR /config ls -lTiR /standby/dump0 ls -lTiR /standby/usr/var/ hardware ls -lTiR /standby/usr/var/ core ls -lTiR /standby/config ls -lTiR /var df -ik du -Pk / show logging...
Page 230 Appendix A Contents of show tech-support Command Display Command (Display) cat /standby/var/log/ fixsb.log cat /usr/var/pplog/ ppupdate.log cat /usr/var/pplog/ ppupdate2.log cat /standby/usr/var/ pplog/ppupdate.log cat /standby/usr/var/ pplog/ppupdate2.log tail -n 30 /var/log/ authlog tail -n 30 /var/log/ xferlog cat /var/log/ssh.log show accounting cat /var/tmp/gen/trace/ mng.trc tail -n 20 /var/tmp/gen/ trace/api.trc...
Page 231 Command (Display) show lldp detail show oadp detail show loop-detection show loop-detection statistics show loop-detection logging show channel-group statistics show channel-group statistics lacp show spanning-tree statistics show vlan detail show vlan mac-vlan show qos queueing show shaper show access-filter show qos-flow show lldp statistics show oadp statistics show mac-address-table...
Page 232 Appendix A Contents of show tech-support Command Display Command (Display) show mld-snooping show mld-snooping group show mld-snooping statistics show netstat routing-table numeric show netstat multicast numeric show ip multicast statistics show ipv6 multicast statistics show ip igmp interface show ip igmp group show ip pim interface (detail) show ip pim neighbor...
Page 233 Command (Display) show ipv6 mld group show ipv6 pim interface (detail) show ipv6 pim neighbor (detail) show ipv6 pim bsr show ipv6 pim rp-mapping show ipv6 mroute show ipv6 mcache show ip multicast statistics show ipv6 multicast statistics show vrrpstatus detail statistics show vrrpstatus group show vrrpstatus vrrp-vlan...
Page 234 Appendix A Contents of show tech-support Command Display Command (Display) show ip rip statistics show ip rip advertised-routes summary show ip rip received-routes summary show ip ospf show ip ospf discard-packets show ip ospf statistics show ip ospf neighbor detail show ip ospf virtual-links detail show ip ospf database...
Page 235 Command (Display) show graceful-restart unicast show ipv6 interface ipv6-unicast show ipv6 route summary show ipv6 rip advertised-routes summary show ipv6 rip received-routes summary show ipv6 rip statistics show ipv6 ospf show ipv6 ospf discard-packets show ipv6 ospf statistics show ipv6 ospf neighbor detail show ipv6 ospf virtual-links detail...
Page 236 Appendix A Contents of show tech-support Command Display Command (Display) show sflow detail show mac-authentication show mac-authentication statistics show mac-authentication mac-address edit show mac-authentication mac-address commit show mac-authentication login show mac-authentication logging show power-control schedule pktbusdisp nifhdcinfo devstatus (Legend) Y: Displayed, N: Hidden Note: Parenthesis in the column of Command (Display) indicates display depending on the software version.
Page 237 Command (Display) /sbin/dmesg cat /var/run/dmesg.boot cat /var/log/messages /usr/local/diag/statShow fstat /usr/local/diag/rtsystat /usr/local/diag/rtastat show netstat all-protocol-address numeric show netstat statistics show dumpfile ls -lTiR /dump0 ls -lTiR /usr/var/hardware ls -lTiR /usr/var/core ls -lTiR /config ls -lTiR /var df -ik du -Pk / show logging show logging reference show ntp associations...
Page 238 Appendix A Contents of show tech-support Command Display Command (Display) cat /usr/var/pplog/ ppupdate.log cat /usr/var/pplog/ ppupdate2.log tail -n 30 /var/log/ authlog tail -n 30 /var/log/ xferlog cat /var/log/ssh.log show accounting cat /var/tmp/gen/trace/ mng.trc tail -n 20 /var/tmp/gen/ trace/api.trc cat /var/tmp/gen/trace/ mng_sub.trc tail -n 400 /var/tmp/gen/ trace/api.trc...
Page 239 Command (Display) show loop-detection show loop-detection statistics sshow loop-detection logging show channel-group statistics show channel-group statistics lacp show spanning-tree statistics show vlan detail show vlan mac-vlan show qos queueing show access-filter show qos-flow show lldp statistics show oadp statistics show mac-address-table show fense server detail show fense statistics show fense logging...
Page 240 Appendix A Contents of show tech-support Command Display Command (Display) show netstat multicast numeric show ip multicast statistics show ipv6 multicast statistics show ip igmp interface show ip igmp group show ip pim interface show ip pim neighbor show ip pim bsr show ip pim rp-mapping show ip mroute show ip mcache...
Page 241 Command (Display) show ip dhcp server statistics show ip dhcp conflict show ipv6 dhcp server statistics show ip route summary show ip rip statistics show ip rip advertised-routes summary show ip rip received-routes summary show ip ospf show ip ospf discard-packets show ip ospf statistics show ip ospf neighbor...
Page 242 Appendix A Contents of show tech-support Command Display Command (Display) show ipv6 ospf discard-packets show ipv6 ospf statistics show ipv6 ospf neighbor detail show ipv6 ospf virtual-links detail show ipv6 ospf database database-summary show ipv6 bgp neighbor detail show ipv6 bgp notification-factor show ipv6 bgp received-routes summary show ipv6 bgp...
Page 243 (Legend) Y: Displayed, N: Hidden Note: Parenthesis in the column of Command (Display) indicates display depending on the software version. (3) IP8800/S2400 The display contents for IP8800/S2400 are shown in the table below. Table A-3: Details of Display Contents (IP8800/S2400) Command (Display)
Page 244 Appendix A Contents of show tech-support Command Display Command (Display) ls -lTiR /dump0 ls -lTiR /usr/var/hardware ls -lTiR /usr/var/core ls -lTiR /config ls -lTiR /var df -ik du -Pk / show logging show logging reference show ntp associations /usr/bin/w -n last -30 show session /usr/sbin/pstat -t...
Page 245 Command (Display) cat /var/tmp/gen/trace/ mng_sub.trc tail -n 400 /var/tmp/gen/ trace/api.trc tail -n 400 /var/tmp/gen/ trace/ctl.trc show netstat interface show vlan list show port show port statistics show port protocol show port transceiver debug show interfaces nif XXX_NIF line XXX_LINE debug show running-config show channel-group detail show spanning-tree detail...
Page 246 Appendix A Contents of show tech-support Command Display Command (Display) show qos queueing show access-filter show qos-flow show lldp statistics show oadp statistics show mac-address-table show fense server detail show fense statistics show fense logging show dot1x logging show dot1x statistics show dot1x detail show igmp-snooping show igmp-snooping group...
Page 247 Command (Display) port snd/rcv statistics internal SW HW event statistics0 internal SW HW event statistics1 show mac-authentication show mac-authentication statistics show mac-authentication mac-address edit show mac-authentication mac-address commit show mac-authentication login show mac-authentication logging swdev logging (Legend) Y: Displayed, N: Hidden Note: Parenthesis in the column of Command (Display) indicates display depending on the software version.
Page 249: Index
Counter Sample Does Not Reach Collector 115 Ethernet Port 154 Ethernet Port Cannot Be Connected 27 Failure Analysis for IP8800/S3600 and IP8800/S2400 4 Failure Analysis for IP8800/S6700 and IP8800/S6300 3 Failure Analysis Overview 2 Failures on Using Ring Protocol 41...
Page 250 Transferring Files Using zmodem Command 148 Transferring Maintenance Information Files Using show tech-support Command 148 Traps Cannot Be Received by SNMP Manager 110 Troubleshooting for IP8800/S3600 and IP8800/S2400 15 Troubleshooting for IP8800/S6700 and IP8800/S6300 12 Troubleshooting of sFlow Statistics (Flow Statistics) Function 112...

This manual is also suitable for:

Ip8800/s6700 series Ip8800/s6300 series Ip8800/s3600 series Ip8800/s6600 series

NEC IP8800/S2400 Series Troubleshooting Manual

Safety Guide [IP8800/S6700]

Safety Guide [IP8800/S6600]

Safety Guide [IP8800/S6300]

Safety Guide [IP8800/S3600] [IP8800/S2400]

1 Overview

2 Troubleshooting System Failures

3 Troubleshooting Functional Failures in Operation

4 Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300]

5 Collecting Failure Information

6 Line Test

7 Restarting the System

Appendix

Appendix A Contents of Show Tech-Support Command Display

Quick Links

Troubleshooting

Related Manuals for NEC IP8800/S2400 Series

Summary of Contents for NEC IP8800/S2400 Series

This manual is also suitable for:

Table of Contents