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.
■ 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. If any questions remains, please consult with our sales department. ■ Trademarks Cisco is a registered trademark of U.S. Cisco Systems, Inc. in the U.
Introduction ■ Applicable product This manual describes models IP8800/S6700, IP8800/S6600, IP8800/S6300, IP8800/S3600 and IP8800/S2400. Please read the manual carefully and thoroughly understand the instructions and cautions contained herein before operating the device. Keep the manual in a location close at hand for easy reference when necessary. Unless otherwise specified, this manual describes functions common to the models. The mark below refers to functions specific to respective models.
Introduction For IP8800/S6700, IP8800/S6600, and IP8800/S6300 Procedures from unpacking the product to making basic settings at the initial installation IP8800/S6700 Quick Start Guide (IP88S67-Q001) IP8800/S6600 Quick Start Guide (IP88S66-Q001) IP8800/S6300 Quick Start Guide (IP88S63-Q001) Information on the facility requirement of the hardware IP8800/S6700 Hardware lnstallation Guide (IP88S67-H001) Information on handling of the hardware IP8800/S6600 Hardware lnstallation Guide (IP88S66-H001) IP8800/
Introduction For IP8800/S3600 Procedures from unpacking the product to making basic settings at the initial installation IP8800/S3600, IP8800/S2400 Quick Start Guide (IP88S36-Q001) Information on the facility requirement of the hardware IP8800/S3600, IP8800/S2400 Hardware lnstallation Guide (IP88S36-H001) Information on handling of the hardware Information on software functions, configuration, and confirmation by using operation commands IP8800/S3600 Software Manual Configuration Settings, Vol.
Introduction For IP8800/S2400 Procedures from unpacking the product to making basic settings at the initial installation IP8800/S3600, IP8800/S2400 Quick Start Guide (IP88S36-Q001) Information on the facility requirement of the hardware IP8800/S3600, IP8800/S2400 Hardware Installation Guide (IP88S36-H001) Information on handling of the hardware Information on software functions, configuration, and confirmation by using operation commands IP8800/S2400 Software Manual Configuration Settings, Vol.
Introduction CIR CIST CLNP CLNS CONS CRC CSMA/CD CSNP CST CSU DA DC DCE DHCP DIS DNS DR DSAP DSCP DTE DVMRP E-Mail EAP EAPOL EFM ES FAN FCS FDB FQDN FTTH GBIC GSRP HMAC IANA ICMP ICMPv6 ID IEC IEEE IETF IGMP IP IPCP IPv4 IPv6 IPV6CP IPX ISO ISP IST L2LD LAN LCP LED LLC LLDP LLPQ LLQ+3WFQ LLRLQ LSP LSP LSR MA MAC MC MD5 MDI MDI-X MEP MIB Committed Information Rate Common and Internal Spanning Tree ConnectionLess Network Protocol ConnectionLess Network System Connection Oriented Network System Cyclic Redund
Introduction MIP MRU MSTI MSTP MSU MTU NAK NAS NAT NCP NDP NET NIF NLA ID NPDU NSAP NSSA NTP OADP OAM OSPF OUI PAD PAE PC PCI PDU PICS PID PIM PIM-DM PIM-SM PIM-SSM PoE PRI PS PSNP PSP QoS RA RADIUS RDI REJ RFC RGQ RIP RIPng RMON RPF RQ RSTP SA SD SDH SDU SEL SFD SFP SMTP SNAP SNMP SNP SNPA SOP SPF SSAP STP TA TACACS+ TCP/IP TLA ID TLV VI Maintenance domain Intermediate Point Maximum Receive Unit Multiple Spanning Tree Instance Multiple Spanning Tree Protocol Management and Switching Unit Maximum Transfe
Introduction TOS TPID TTL UDLD UDP UPC UPC-RED uRPF VAA VLAN VPN VRF VRRP WAN WDM WFQ WGQ WRED WS WWW XFP 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 unicast Reverse Path Forwarding VLAN Access Agent Virtual LAN Virtual Private Network Virtual Routing and Forwarding/Virtual Routing and Forwarding Instance Virtual Router Redundancy Protocol Wide Area Network Wavelength Div
Contents Introduction I Safety Guide [IP8800/S6700] v Safety Guide [IP8800/S6600] xvii Safety Guide [IP8800/S6300] xxix Safety Guide [IP8800/S3600] [IP8800/S2400] 1 Overview 1 1.1 Failure Analysis Overview 2 1.2 System and Partial Failure Analysis Overview 3 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 2 3 xli 3 4 7 Troubleshooting System Failures 11 2.
Contents 3.4 Network Interface Communication Failure 3.4.1 Ethernet Port Cannot Be Connected 27 3.4.2 Communication Failure in Basic Switching Unit BSU/PSP 29 3.4.3 Actions against Troubles on 10BASE-T/100BASE-TX/1000BASE-T 30 3.4.4 Actions against Troubles on 1000BASE-X 32 3.4.5 Actions against Troubles on 10GBASE-R 33 3.4.6 Communication Failure on Using PoE 35 3.4.7 Communication Failure on Using Link Aggregation 36 3.5 Layer 2 Network Communication Failure 38 3.5.
Contents 3.13 Communication Failure on High-reliability Function 103 3.13.1 GSRP Communication Failures 103 3.13.2 Communication with VRRP Configuration in IPv4 Network Is Disabled 105 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.
Contents 5.1.2 Collecting Failure Information Using dump Command [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 5.2 Transferring Files for Maintenance Information 144 5.2.1 Transferring Files Using ftp Command 145 5.2.2 Transferring Files Using zmodem Command [IP8800/S3600] [IP8800/S2400] 148 5.2.3 Transferring Maintenance Information Files Using show tech-support Command 148 5.2.4 Transferring Files Using ftp Command from the Operation Terminal 150 5.3 Writing to MC 5.3.
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. • For any operation, follow the directions and procedures given by this document.
Safety Guide [IP8800/S6700] WARNING ■ 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. • For the device with AC power supply mounted, power off the device and unplug the power cable from the outlet.
Safety Guide [IP8800/S6700] ■ 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. • When the device is connected to the power supply of 200VAC, leak current of up to 5mA flows for each device.
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. Otherwise, a personal injury due to drop or fall may be caused. For installation and carrying of the device, use a handling equipment such as a hand lifter. Otherwise, a personal injury due to drop or fall may be caused.
Safety Guide [IP8800/S6700] ■ 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. ■ Work to add or replace equipment must be performed by a trained engineer or maintenance personnel.
Safety Guide [IP8800/S6700] CAUTION ■ 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. If the device is operated immediately a fire or electric shock can be caused. Thus, in this case, leave the device as it is for several hours before starting operation.
Safety Guide [IP8800/S6700] ■ 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. If pulling it forward carelessly, it may drop and cause a personal injury. The label below is attached to the DC power supply. ■ Do not touch the inside of the device.
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 °C/140 °F in temperature. Do not touch it when working or immediately after stopping to prevent getting burned. Caution. Hot! (all sides) • To remove an SFP-T, follow the following procedures.
Safety Guide [IP8800/S6700] CAUTION ■ 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). The device may be damaged. ■ Handle a memory card with care. • Do not forcedly push or flip a memory card to insert.
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. ■ After removing an optional component, be sure to attach a blank panel. • After removing an optional component, be sure to attach a blank panel.
Safety Guide [IP8800/S6700] ■ 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. Change the direction of the antenna for the television or radio set. 3. Use different outlets. ■ Keep the device away from a place with hydrogen sulfide or much salt.
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. • For any operation, follow the directions and procedures given by this document.
Safety Guide [IP8800/S6600] WARNING ■ 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. • For the device with AC power supply mounted, power off the device and unplug the power cable from the outlet.
Safety Guide [IP8800/S6600] ■ 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. • When the device is connected to the DC power supply, be sure to connect the grounding terminal.
Safety Guide [IP8800/S6600] The label below is attached to the device. 45kg IP8800/S6604 64kg IP8800/S6608 ■ 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. A heavy material may be placed as a result of covering the cable with a floor carpet. • Use the attached power cable or the power cable complying with the specifications.
Safety Guide [IP8800/S6600] ■ 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.
Safety Guide [IP8800/S6600] CAUTION ■ 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. If the device is operated immediately a fire or electric shock can be caused. Thus, in this case, leave the device as it is for several hours before starting operation.
Safety Guide [IP8800/S6600] ■ 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. ■ Do not bring hairs or any foreign matters close to the intake/exhaust port of the device. • The cooling fan unit is provided on the device. Do not put any material close to the intake/exhaust port.
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. Personal injury may be caused. The label below is attached to the fan unit. ■ Do not roughly handle the power cable. • Do not put the power cable close to the heating apparatus.
Safety Guide [IP8800/S6600] ■ Do not touch a working (including immediately after stopping) SFP-T. • A working (establishing a link) SFT-P can have up to 65 °C/140 °F in temperature. Do not touch it when working 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. • To remove an SFP-T without turning off the device, execute the inactivate command, and remove the SFP-T five minutes later.
Safety Guide [IP8800/S6600] CAUTION ■ 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). The device may be damaged. ■ Handle a memory card with care. • Do not forcedly push or flip a memory card to insert.
Safety Guide [IP8800/S6600] ■ 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. ■ After removing an optional component, be sure to attach a blank panel. • After removing an optional component, be sure to attach a blank panel.
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. Keep the device from the television or radio set as far away as possible. 2. Change the direction of the antenna for the television or radio set. 3. Use different outlets. ■ Keep the device away from a place with hydrogen sulfide or much salt.
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. • For any operation, follow the directions and procedures given by this document. • Observe the cautions labeled on the device or those presented by this document.
Safety Guide [IP8800/S6300] WARNING ■ 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. • For the device with AC power supply mounted, power off the device and unplug the power cable from the outlet.
Safety Guide [IP8800/S6300] ■ 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. • For connecting the DC power supply, be sure to connect the grounding terminal. If the power supply is used without grounding, an electric shock may be caused and failures may occur due to electric noise.
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 Mass IP8800/S6304 45kg/100 lb IP8800/S6308 64kg/142 lb Number of people 3 or more The label below is attached to the device.
Safety Guide [IP8800/S6300] ■ 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. ■ Work to add or replace equipment must be performed by a trained engineer or maintenance personnel.
Safety Guide [IP8800/S6300] CAUTION ■ 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. If the device is operated immediately a fire or electric shock can be caused. Thus, in this case, leave the device as it is for several hours before starting operation.
Safety Guide [IP8800/S6300] ■ 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. ■ Do not bring hairs or any foreign matters close to the intake/exhaust port of the device. • The cooling fan unit is provided on the device. Do not put any material close to the intake/exhaust port.
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. Personal injury may be caused. The label below is attached to the fan unit. ■ Do not roughly handle the power cable. • Do not put the power cable close to the heating apparatus.
Safety Guide [IP8800/S6300] ■ Do not touch a working (including immediately after stopping) SFP-T. • A working (establishing a link) SFT-P can have up to 65 °C/140 °F in temperature. Do not touch it when working 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. • To remove an SFP-T without turning off the device, execute the inactivate command, and remove the SFP-T five minutes later.
Safety Guide [IP8800/S6300] CAUTION ■ 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). The device may be damaged. ■ Handle a memory card with care. • Do not forcedly push or flip a memory card to insert.
Safety Guide [IP8800/S6300] 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. ■ Be sure to install the network interface module with the tray attached.
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. Keep the device from the television or radio set as far away as possible. 2. Change the direction of the antenna for the television or radio set. 3. Use different outlets. ■ Keep the device away from a place with hydrogen sulfide or much salt.
Safety Guide [IP8800/S3600] [IP8800/S2400] ■ Safety guide for the IP8800/S3600 and IP8800/S2400 series • This document provides safety-related notices for use of the IP8800/S3600 and IP8800/S2400 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. • For any operation, follow the directions and procedures given by this document.
Safety Guide [IP8800/S3600] [IP8800/S2400] WARNING ■ 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.
Safety Guide [IP8800/S3600] [IP8800/S2400] ■ Do not use power not specified. • Do not use a supply voltage not specified. Fire disasters or electric shock may be caused. ■ The current capacity supplied to the power distribution panel must be larger than the operating current of the breaker. • The current capacity supplied to the power distribution panel must be larger than the operating current of the breaker. Otherwise, the breaker may not work in the event of a failure and cause fire disasters.
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. ■ 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.
Safety Guide [IP8800/S3600] [IP8800/S2400] CAUTION ■ Do not place the device in an unstable location. • If the device is being placed on a table, be sure to install it horizontally on a workbench or the like that can sufficiently bear the weight of the device. If the device is placed on an unstable location such as a shaky table or slope, the device may fall and drop and consequently personal injury may be caused. • To mount the device on a rack, make sure that the device is placed in a stable location.
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. As a result, fire disasters or electric shock may be caused. • When stacking the devices for transportation, put them into package boxes. Otherwise, the device may be deformed or damaged.
Safety Guide [IP8800/S3600] [IP8800/S2400] off the power switches on all power supplies mounted on the device. ■ Do not touch the device directly if you have metal allergies. • This device is coated with metals including zinc, nickel, and gold. If you have allergies to them, do not touch the device directly to prevent getting dermatitis. ■ Be careful of the laser beams. • The device uses the laser beams, which is invisible, clear and colorless. Do not peep in the optical transceiver directly.
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. • Do not put a material weighing over 5 kg/11.1 lb on 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.
Safety Guide [IP8800/S3600] [IP8800/S2400] CAUTION ■ Do not install the device in any place possibly reaching a high temperature. • Be careful that the parts may be damaged if left in a place exposed to direct sunlight or close to a heating apparatus. ■ 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.
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.
Safety Guide [IP8800/S3600] [IP8800/S2400] ■ 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. ■ When carrying or packing an optional component, take care for handling. • Take care not to touch the connector when carrying or packing the transceiver, memory card, power supply, fan unit, or power module.
1 Overview This chapter outlines the failure analysis. 1.1 Failure Analysis Overview 1.2 System and Partial Failure Analysis Overview 1.
1. Overview 1.1 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 "1.2 System and Partial Failure Analysis Overview." To login and check the system, follow the instructions in "1.3 Functional Failure Analysis Overview.
1. Overview 1.2 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 IP8800/S6300" to troubleshoot.
1. Overview No.
1.
1. Overview No. Name Type Function Description 11 1-24 LED: Green/ Orange Indicates the operation status of 10/ 100/1000BASE-T Ethernet port. Lit in green: Link established Blinking in green: Link established and frames being sent/received Lit in orange: Line failure detected OFF: If ST1 LED is lit in green, the link failed or is blocked 12 RESET Switch (Non-locked) System manual reset switch Restarts the system. Note: Figure 1-2 and Table 1-2 show a typical system.
1. Overview 1.3 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.
1. Overview Item IPv4 unicast routing communication failure Reference No RIP information 3.7.1 No RIP Routing Information Exists No OSPF information 3.7.2 No OSPF Routing Information Exists No BGP4 information 3.7.3 No BGP4 Routing Information Exists No VRF information 3.7.4 No Routing Information Exist [OP-NPAR] Communication disabled on PIM-SM network 3.8.1 Communication on IPv4 PIM-SM Network Is Disabled Data double-relayed on PIM-SM network 3.8.
1. Overview Item Subitem Reference Neighboring system information cannot be acquired by LLDP function - 3.16.1 Unable to Obtain Neighboring System Information via LLDP Function Neighboring system information cannot be acquired by OADP function - 3.16.2 Unable to Obtain Neighboring System Information via OADP Function Communication failure in NTP - 3.17.1 Time Synchronization by NTP Is Disabled Failure when using IEEE802.3ah/ UDLD function Port becomes inactive 3.18.
2 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 System Failures 2.1 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 No. 1 Failure • Fume generated from the system • Unusual odor occurs from the system • Unusual sound occurs from the system Action Execute the steps below immediately. 1. Power off the system. 2.
2. Troubleshooting System Failures No. Failure Action 5 Error message output to the system operation panel Take the action against the corresponding error message in the manual "Message Log Reference." 6 STATUS LED on BCU/CSU/MSU is lit in red, other LEDs are OFF, and no message on the system operation panel 1. Check the single/redundant configuration of BCU/CSU/MSU. (1) For the single configuration, follow the step 3 and later. (2) For the redundant configuration, follow the step 2 and later. 2.
2. 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.
2. Troubleshooting System Failures 2.2 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 No. Failure Action 1 • Fume generated from the system • Unusual odor occurs from the system • Unusual sound occurs from the system Execute the steps below immediately. 1. Power off the system. 2. Remove the power cable of the system.
2. Troubleshooting System Failures No. Failure Action 5 • 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 System or line has failed. 1. For the redundant power supply model, check the states of the power supplies and fan unit. Replace them if they have failed. - If ALM LED on the fan unit is lit in red, replace the fan unit.
2. Troubleshooting System Failures 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 No. Failure Action 1 POWER LED on the external power unit is lit in green Check LED on the power module mounted on the external power unit and identify the power module that is not normally running. If the power module is normally running, the states below are provided.
2. 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.
3 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 3.8 IPv4 Multicast Routing Communication Failure 3.
3. Troubleshooting Functional Failures in Operation 3.20 Problems on Redundant Configuration of Basic Switching Unit (BSU) [IP8800/S6700] 3.
3. Troubleshooting Functional Failures in Operation 3.1 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.
3. Troubleshooting Functional Failures in Operation 3.2 Problems on MC 3.2.1 "MC:--------" is displayed by entering the show system command or the show mc command When "MC:--------" is displayed by entering the show system command or the show mc command, follow the instruction in "Table 3-1: Problems and Actions When "MC:--------" is displayed" Table 3-1: Problems and Actions When "MC:--------" is displayed No. Failure Troubleshooting Steps 1 Check to see ACC LED.
3. Troubleshooting Functional Failures in Operation 3.3 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 "Table 3-3: Problems and Actions When Connecting to Console." When there is a problem connecting to the modem, follow the instruction in "Table 3-4: Problems and Actions When Connecting to Modem." Also, see the manual provided with the modem.
3. Troubleshooting Functional Failures in Operation Table 3-4: Problems and Actions When Connecting to Modem No. Failure Troubleshooting Steps 1 Automatic termination to the modem is disabled. Check the following. • Cable is connected properly. • Modem is powered on. • Telephone number is correct. • Settings of the modem are correct. • Line can be connected by connecting the modem to two terminals and dialing. 2 Abnormal characters are displayed upon login.
3. Troubleshooting Functional Failures in Operation No. Symptom Action to Be Taken or Reference 3 Key entry rejected. Determine the cause by following the steps below: 1. Data sending/receiving may be interrupted by the XON/XOFF flow control. Restart the data sending/receiving (press [Q] key with the [Ctrl] key pressed). If key entry is still disabled, check No. 2 or later. 2. Check to see if the communication software is configured properly. 3. The screen may be suspended by [Ctrl]+[S].
3. 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.
3. Troubleshooting Functional Failures in Operation 3.4 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. Checking log For the log, see the manual "Message Log Reference." 2. Isolating the problem according to the NIF status.
3. Troubleshooting Functional Failures in Operation Table 3-7: Check and Action for Port Status No. Port Status Problem Action 1 active up The port is operating normally. None 2 active down Line failure occurred in the port. According to the log of the port displayed by the show logging command, see the corresponding part in manual "Message Log Reference" and follow [Action] described.
3.
3. Troubleshooting Functional Failures in Operation No. BSU Operation Status 5 fault Problem Unavailable configuration has been set. 6 Action Use configuration command fldm prefer to correctly set flow distribution pattern of the filter and QoS function. Use configuration command fwdm prefer to correctly set the distribution pattern of the maximum number of entries per device. 7 The BSU/PSP is faulty.
3. Troubleshooting Functional Failures in Operation Table 3-9: Troubleshooting for Failed 10BASE-T/100BASE-TX/1000BASE-T No. Troubleshooting Steps 1 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. • Link down Problem Line quality is degraded. Action Check to see if the cable type is correct.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps Problem 5 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 Packets with invalid frame length are received. Follow the jumbo frame setting on the remote system.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps 2 According to the receiving error 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. • CRC errors • Symbol errors Problem Line quality on receiving side is degraded. Action Check the type of fiber optics. For the mode, see "Hardware Installation Guide.
3. 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 No. Troubleshooting Steps 1 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.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps 3 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 Problem Line quality on sending side is degraded. Action Check the type of fiber optics. For the fiber optics type, see "Hardware Installation Guide.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 3 Check to see Threshold(W) and Allocate(W) by the show power inline command. Because a value in Allocate(W) is larger than one in Threshold(W), electricity is not able to be provided. First, check to see the amount of power supply provided to the whole system, the amount of electrical power allocation to the ports, and power consumption of the ports. And then configure these items to adjust allocations.
3. Troubleshooting Functional Failures in Operation No. 2 Troubleshooting Steps and Command Check the setting of failed port status using the show channel-group command with "detail" parameter specified. Action Check the status of each port. If all ports in a link aggregation group are Down, the link aggregation group is also Down. Take the action below for the Down port depending on the Reason displayed. • CH Disabled The link aggregation group is Disabled and Down. • Port Down The link is down. See "3.
3. Troubleshooting Functional Failures in Operation 3.5 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" parameter specified and check the VLAN status. Check items for each VLAN function are listed below.
3. Troubleshooting Functional Failures in Operation 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) 0012.e200.aa02 (static) 0012.e200.aa04 (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.
3. Troubleshooting Functional Failures in Operation [When Type displayed is Dot1x] See "3.12.1 Communication Failure on Using IEEE 802.1X." [When Type displayed is Wa] See "3.12.2 Communication Failure on Using Web Authentication." [When Type displayed is Macauth] See "3.12.3 Communication Failure on Using MAC Authentication." • Flooding is executed if the MAC address is not displayed.
3. Troubleshooting Functional Failures in Operation bridge for each MST instance for route bridge, when checking the route bridge. Table 3-14: Spanning Tree Failure Analysis Method No. Troubleshooting Steps and Command 1 Execute the show spanning-tree command for the failed spanning tree and check the protocol status of the spanning tree. Action If shown as Enable, go to No. 2. When tree information is not displayed while Ring Protocol and PVST+ both are in use, go to No.7.
3. Troubleshooting Functional Failures in Operation and isolate the problem. Figure 3-4: Analysis Flow Analysis Flow Any failure on node constituting ring network or port as ring port? Any failure on cable or hardware? Replace the faulty parts. Any failure on software? Correct the problem on hardware configuration. Execute the dump command and collect the failure information. Correct the problem on settings.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 4 Execute the show axrp command to check the ring port for each VLAN group and its operation state. Go to No. 5 if "Ring Port" and "Role/State" correspond to the port state of network configuration. Execute the show axrp detail command to check the control VLAN ID. Go to No. 6 if "Control VLAN ID" corresponds to the VLAN ID of network configuration.
3. 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 Analysis Flow see the manual "Message Log Reference" and perform the actions described in [Action] associated with each log message.
3. Troubleshooting Functional Failures in Operation Table 3-16: Troubleshooting on Multicast Relay No. Troubleshooting Steps and Command Action 1 Use the show logging command to check if any failure occurs. Check the following: - Check the log information for physical failures. 2 Check if filtering and QoS are set correctly. 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.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command 4 Check the IGMP snooping configuration using the show igmp-snooping command. Action Check the following: - Check that the message below is displayed to confirm the existence of the IGMP querier which monitors group members. [IP8800/S3600] (1) If the IGMP querier exists, the IGMP querier IP address is displayed. IGMP querying system: 192.168.11.
3. Troubleshooting Functional Failures in Operation 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 See the manual "Message Log Reference" and perform the action described in [Action] associated with each log message.
3. Troubleshooting Functional Failures in Operation Table 3-17: Troubleshooting on Multicast Relay No. Troubleshooting Steps and Command Action 1 Use the show logging command to check if any failure occurs. Check the log information for physical failures. 2 Check if filtering and QoS are set correctly. 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.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 4 Check the MLD snooping configuration using the show mld-snooping command. Check the following: - Check that the message below is displayed to confirm the existence of the MLD querier which monitors group members. (1) If the MLD querier exists, the MLD querier IP address is displayed.
3. Troubleshooting Functional Failures in Operation 3.6 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. Network configuration has changed 3. Network component failures For 1 and 2 above, check for the differences in the configuration and network configuration provided before and after the change.
3. Troubleshooting Functional Failures in Operation Figure 3-7: Failure Analysis Procedure When IPv4 Communication Disabled Verify if there is a line failure log message. A line failure log message exists. No line failure log message exists. See the manual"Message Log Reference"and perform the action described in [Action] associated with each log message. Check the Up/Down status of the interface.
3. 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. Log in to the system. 2. Check the Up/Down status of the interface between the systems using the show ip interface command. 3.
3. Troubleshooting Functional Failures in Operation (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. Use the following procedure: 1. Log in to the system. 2.
3. 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. DHCP/BOOTP server failures For 2 above, check for the differences in the network configuration provided before and after the change.
3. Troubleshooting Functional Failures in Operation (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. For the procedure, see "3.6.1 Communication Is Disabled or Is Disconnected.
3. 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 Failure" if the route information on the failed interface is missing in the route information acquired by this system or if the next hop address is invalid. 4.
3. Troubleshooting Functional Failures in Operation Figure 3-9: DHCP Server Failure Analysis Procedure 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)( No failure on this system (Connected via relay agent) A failure occurred on this system Refer to "(1)DHCP/BOOTP relay communication failure.
3. 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." 3. If the server and the client are directly connected, check the HUB and cable connections. 4.
3. Troubleshooting Functional Failures in Operation Figure 3-10: Troubleshooting for DHCP Server Failure with DNS Cooperation 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) No failure on this system (Multiple devices exist between DNS server and DHCP server.) A failure occurred on this system Verify the failure occurrence on other devices.
3. 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. Log in to the system. 2.
3. Troubleshooting Functional Failures in Operation 3.7 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 "3.7.4 No Routing Information Exist [OP-NPAR]." [OP-NPAR] Table 3-18: RIP Failure Analysis Method No.
3. 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 "3.7.4 No Routing Information Exist [OP-NPAR]." [OP-NPAR] Table 3-20: BGP4 Failure Analysis Method No.
3. Troubleshooting Functional Failures in Operation 3.8 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. The figure below illustrates a network example of IPv4 PIM-SM.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 4 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 If suppression of protocol packet and multicast packet relay is provided, correct the configuration. 5 Check the PIM neighboring information.
3. Troubleshooting Functional Failures in Operation Table 3-23: BSR Check Items No. Troubleshooting Steps and Command Action 1 Confirm that this system is a candidate for BSR. show ip pim bsr If this system is not a candidate for BSR, check the configuration and set the configuration to run this system as a candidate for BSR. Since this system does not run as a candidate for BSR if no address is set for the loopback interface, confirm that an address is set for the loopback interface.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 4 Check to see if IGMP snooping is set to the port in which static group join function is working. show igmp-snooping When IGMP snooping is set, confirm the following: • Confirm that relay port is set as multicast port for IGMP snooping • See "3.5.4 Multicast Relay by IGMP snooping Is Disabled." 5 Confirm that no interface in abnormal state is detected.
3. Troubleshooting Functional Failures in Operation Table 3-27: Check Items When Double-relay Continues No. Troubleshooting Steps and Command Action 1 Check the PIM neighboring information on the interface of the network having multiple routers. show ip pim neighbor If the neighboring router is not displayed, check the following: • Confirm that PIM is running on the interface connected to the neighboring router using the show ip pim interface command.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 3 Confirm that IGMP snooping is set to the interface with PIM enabled. show igmp-snooping When the IGMP snooping is set, confirm the following: • The port to which neighboring router connected is set as a multicast router port for IGMP snooping. • See "3.5.4 Multicast Relay by IGMP snooping Is Disabled.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 5 If there is an interface in which the relay target group participates, confirm that this system is DR. show ip pim interface If this system is not DR, check DR of the relay target interface. 6 Confirm that IGMP snooping is set to the interface with static group join function enabled.
3. Troubleshooting Functional Failures in Operation Table 3-31: Check Items When Double-relay Continues No. Troubleshooting Steps and Command Action 1 Check the PIM neighboring information on the interface of the network having multiple routers. show ip pim neighbor If the neighboring router is not displayed, check the following: • Confirm that PIM is running on the interface connected to the neighboring router using the show ip pim command with "interface" parameter specified.
3. Troubleshooting Functional Failures in Operation 3.9 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. Network component failures For 1 and 2 above, check for the differences in the configuration and network configuration provided before and after the change.
3. 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 Disconnected.
3. Troubleshooting Functional Failures in Operation 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.
3. Troubleshooting Functional Failures in Operation Figure 3-14: IPv6DHCP Server Failure Analysis Procedure Verify the operation log using the show logging command. No physical failure message exists. A physical failure message exists. Check the Up/Down status of the interface using the show ipv6 interface command. Go to "3.4 Network Interface Communication Failure." Check the status of IPv6DHCP server. The settings of this system are correct.
3. Troubleshooting Functional Failures in Operation 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. Confirm that IPv6DHCP server functions is enabled.
3. 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. (e) Checking client setting Check the client setting referring manuals provided with client.
3.
3. Troubleshooting Functional Failures in Operation (c) Checking the DUID You can check the DUID in the "< Server DUID >" section of the output of the show ipv6 dhcp server statistics command. For details, see "Configuration Settings.
3. Troubleshooting Functional Failures in Operation 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 No. Troubleshooting Steps and Command 1 2 3 3.10.2 Action RIPng neighboring information is displayed. show ipv6 rip neighbor Go to No.
3. 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 No. 1 2 3 4 5 80 Troubleshooting Steps and Command Action Check the BGP4+ peer status. show ipv6 bgp neighbors Go to No. 2 if the peer status is other than Established.
3. Troubleshooting Functional Failures in Operation 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. The figure below illustrates a network example of IPv6 PIM-SM.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 5 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 If suppression of protocol packet and multicast packet relay is provided, correct the configuration. 6 Check the PIM neighboring information.
3. Troubleshooting Functional Failures in Operation Table 3-39: BSR Check Items No. Troubleshooting Steps and Command Action 1 Confirm that this system is a candidate for BSR. show ipv6 pim bsr If this system is not a candidate for BSR, check the configuration and set the configuration to run this system as a candidate for BSR. Since this system does not run as a candidate for BSR if no address is set for the loopback interface, confirm that an address is set for the loopback interface.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 4 Confirm that MLD snooping is set to the interface with PIM enabled. show mld-snooping When MLD snooping is set, confirm the following: • Confirm that multicast router port for MLD snooping is set to the forwarding port. • See "3.5.5 Multicast Relay by MLD snooping Is Disabled." 5 Confirm that no interface in abnormal state is detected.
3. Troubleshooting Functional Failures in Operation 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.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 7 Check to see if the unicast route to the multicast data sender exists. show ipv6 route If the unicast route does not exist, see "3.10 IPv6 Unicast Routing Communication Failure." 8 Confirm that PIM is running on the sending interface for the unicast route to the multicast data sender.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 8 Check to see if IGMP snooping is set to the port in which static group join function is running. show mld-snooping When MLD snooping is set, confirm the following: • Chec to see if the forwarding port is set as a multicast port for MLD snooping • See "3.5.5 Multicast Relay by MLD snooping Is Disabled." 9 Confirm that no interface in abnormal state is detected.
3. Troubleshooting Functional Failures in Operation Table 3-47: Check Items When Double-relay Continues 88 No. Troubleshooting Steps and Command Action 1 Check the PIM neighboring information on the interface of the network having multiple routers. show ipv6 pim neighbor If the neighboring router is not displayed, check the following: • Confirm that PIM is running on the interface connected to the neighboring router using the show ipv6 pim command with "interface" parameter specified.
3. Troubleshooting Functional Failures in Operation 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 No. Troubleshooting Steps and Command Action 1 Execute the show dot1x command and check the operation status of the IEEE802.1X.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 6 Execute the show dot1x logging command and check to see if authentication failed. • 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.
3. Troubleshooting Functional Failures in Operation No. 7 Troubleshooting Steps and Command Execute the show dot1x logging command and check to see if dynamic assignment of VLAN authentication (dynamic) failed. Action • If "Failed to assign VLAN.(Reason: No Tunnel-Type Attribute)" is output, the dynamic assignment has been failed as there is no Tunnel-Type attribute in the RADIUS attribute of the RADIUS frame. Add the Tunnel-Type attribute in setting of the RADIUS attribute for the RADIUS server.
3. Troubleshooting Functional Failures in Operation Table 3-49: IEEE 802.1X Failure Analysis Method [IP8800/S3600] [IP8800/S2400] No. Troubleshooting Steps and Command Action 1 Confirm that VLAN with VLAN authentication (static) set and other VLANs are not provided on the trunk port. Since communication is enabled only with the VLAN on which VLAN authentication (static) is set, exclude the port from authentication or set the VLAN with VLAN authentication (static) and other VLANs on different ports.
3. Troubleshooting Functional Failures in Operation No. 4 Troubleshooting Steps and Command Check to see authentication Ipv4 access list Action • For IP8800/S6700, IP8800/S6600, and IP8800/S6300 models, go to No.9. • If a terminal before authentication sends packets out of the system, confirm that authentication IPv4 access list is applied.
3. Troubleshooting Functional Failures in Operation No. 11 Troubleshooting Steps and Command Execute the show web-authentication logging command to check to see if the system operates correctly. Action • If the log "The login failed because of hardware restriction." is output by the show web-authentication logging command, see "4.2.2 Action to Be Taken When VLAN Identification Table Resource Shortage Occurs.
3. Troubleshooting Functional Failures in Operation Table 3-51: Checking Web Authentication Configuration No.
3. Troubleshooting Functional Failures in Operation No. Check Point Troubleshooting Steps 5 Check to see the access filter setting for authentication. 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. 6 Check to see the ARP relay setting.
3. Troubleshooting Functional Failures in Operation 3.12.3 Communication Failure on Using MAC Authentication For MAC authentication failure, isolate the problem according to the failure analysis method described in "Table 3-53: Failure Analysis Method for MAC Authentication.
3. Troubleshooting Functional Failures in Operation No. 5 Troubleshooting Steps and Command Check to see authentication IPv4 access list. 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.
3. Troubleshooting Functional Failures in Operation Table 3-54: Checking MAC Authentication Configuration No.
3. Troubleshooting Functional Failures in Operation Table 3-56: Authentication VLAN Failure Analysis Method No. Troubleshooting Steps and Command 1 Execute the show logging command and check to see if hardware failures are recorded in the operation log. • If hardware failures are recorded in the operation log, replace the system. • Otherwise, go to No. 2. 2 Execute the show fense server command and confirm that the system runs normally. • If error message "Connection failed to VAA program.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 8 Execute the show vlan mac-vlan command and confirm that the authenticated MAC address is registered in the MAC VLAN function. • If the authenticated MAC address is registered by the show vlan mac-vlan command, authentication for the MAC address is not enabled. Clear the MAC address registered by the command.
3. Troubleshooting Functional Failures in Operation No.
3. Troubleshooting Functional Failures in Operation 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 No.
3. Troubleshooting Functional Failures in Operation Table 3-59: Analysis Method for Abnormal Status in GSRP Configuration No. Troubleshooting Steps and Command 1 Check the status of the VLAN group in which master/backup is not switched as expected, using the show gsrp command. Action Go to No. 2 if one system is master and the other system is non-master. If one of the systems is Backup (No Neighbor), recover from the communication failure between direct links.
3. Troubleshooting Functional Failures in Operation 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 No.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 7 Execute the show logging command and the show vrrpstatus command with "statistics" parameter specified to check the receiving status of the ADVERTISEMENT packets. • If "Virtual router of received VRRP packet for which the advertisement interval is different than the one configured for local virtual router.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 11 Execute show vrrpstatus command with "detail" parameter specified to confirm that the virtual router status is not "Initial." 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" column. (For non-operation factors, see "Operation Commands.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 5 Execute the show vrrpstatus command with "statistics" parameter specified to check the receiving status of ADVERTISEMENT packets. • If "Virtual router of received VRRP packet for which the advertisement interval is different than the one configured for local virtual router.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command Action 9 Execute show vrrpstatus command with "detail" parameter specified to check the virtual router status. 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" column. (For non-operation factors, see "Operation Commands.
3. 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. Execute the show snmp-server command to confirm that the community name and access list have been registered correctly.
3. Troubleshooting Functional Failures in Operation 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.
3. 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. Checking configuration. Checking failures etc. 3.15.1 sFlow Packets Do Not Reach Collector (1) Checking route to the collector See "3.6.
3. Troubleshooting Functional Failures in Operation 2093(2041) : 0 Exported sFlow samples : 37269 Couldn't exported sFlow samples sFlow collector data : Collector IP address: 192.168.4.199 UDP:6343 Source IP address: 130.130.130.1 Send FlowSample UDP packets : 12077 Send failed packets: 0 Send CounterSample UDP packets: 621 Send failed packets: 0 Collector IP address: 192.168.4.203 UDP:65535 Source IP address: 130.130.130.
3. 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 <- sflow forward must be set here. ! (config)# • See "3.23.1 Checking Filtering/QoS Setting Information" to confirm that "filter" is not set for the physical port subject to flow statistics.
3. Troubleshooting Functional Failures in Operation 3.15.2 Flow Sample Does Not Reach Collector If problem still persists even after checking "3.15.1 sFlow Packets Do Not Reach Collector," check the following: (1) Checking presence/absence of the relay packet Execute the show interfaces command to check to see if the packet is relayed.
3. 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. Table 3-63: Failure Analysis Method When Using LLDP Functions No.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command 2 Execute the show oadp command to check the port information displayed. Action If the information on the port to which the neighboring system is connected appears in "Enabled Port," go to No. 3. If the information on the port to which the neighboring system is connected does not appear in "Enabled Port," the port is not covered by the OADP function. Enable the OADP function for the port.
3. 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 No. Troubleshooting Steps and Command 1 Execute the show clock command to see if a time zone has been set up. If the command retrieves the time zone setting, go to No. 2.
3. Troubleshooting Functional Failures in Operation 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 No.
3. 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 No.
3. Troubleshooting Functional Failures in Operation 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.
3. Troubleshooting Functional Failures in Operation No. 122 BSU Operation Status Problem Action 4 notconnect The BSU is not installed. Check if as many BSU boards as required for active BSU + standby BSU (if standby BSU is not required, only active BSU) are installed. If installed, no action is required. If not so, install the required number of BSU boards. 5 initialize The BSU is being initialized. Wait until initialization completes.
3. Troubleshooting Functional Failures in Operation 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. Table 3-69: Problems and Actions When Using Power Saving Feature with Power Saving Feature No.
3. 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. The following message is displayed when the system detects packet congestion.
3. Troubleshooting Functional Failures in Operation No. Troubleshooting Steps and Command 4 Collecting analysis information • Execute the show tech-support command and the dump bsu command in this order for two times. [IP8800/S6700] • Execute the show tech-support command and the dump psp command in this order for two times. [IP8800/S6600] [IP8800/S6300] • Execute the show tech-support command for two times. [IP8800/S3600] [IP8800/S2400] Action Send the collected information to the support division.
3. 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.
3. Troubleshooting Functional Failures in Operation 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. 4. Review to see if discard control and shaper have been set up appropriately for the system operation.
4 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.
4. Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 4.1 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. The operation log message output is shown in the table below. Table 4-1: Operation Log Message for Checking Resource Usage No.
4. Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] No. Trigger Log Message 9 Web authentication (Static VLAN mode) The login failed because of hardware restriction. Note: This log is displayed when the show web-authentication logging command is executed. 10 MAC authentication The login failed because of hardware restriction. Note: This log is displayed when the show mac-authentication logging command is executed. * The log message of No.
4. 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.
4. Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 4.2 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. The operation log message to be output is shown in the table below. Table 4-4: Operation Log Message for Checking Resource Usage No.
4. 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. No. 1, 2, and 3 in the above table show that setting cannot be registered to the VLAN identification table by the configuration command. No.
4. Troubleshooting Communication Failures Due to Resource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 4.3 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.
5 Collecting Failure Information This chapter focuses on collecting the failure information. 5.1 Collecting Failure Information 5.2 Transferring Files for Maintenance Information 5.
5. Collecting Failure Information 5.1 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 "5.2.3 Transferring Maintenance Information Files Using show tech-support Command"). Memory dump at failure occurrence time can be collected by using the dump command. 5.1.
5. Collecting Failure Information Figure 5-1: Collecting Failure Information from the Remote Operation Terminal Collecting basic information client-host> ftp 192.168.0.60 <-------- 1 Connected to 192.168.0.60. 220 192.168.0.60 FTP server (NetBSD-ftpd) ready. Name (192.168.0.60:staff1): staff1 331 Password required for staff1. Password: 230 User staff1 logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> get .show-tech show-tech.txt <-------- 2 local: show-tech.txt remote: .
5. 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. For IP8800/S6700 1.
5. Collecting Failure Information 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. > dump psp Dump command accept. > 11/01 17:43:42 E3 MSU 25070700 2301:000000000000 PSP online dump command executed. 2. After above log is displayed, execute next dump command. > dump nif 1 Dump command accept.
5. 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. Execute the dump psp command for the standby PSP from the active system.
5. Collecting Failure Information 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:> dump psp Dump command accept. SBY:> 11/01 18:20:42 E3 MSU 25070700 2301:000000000000 PSP online dump command executed.
5. Collecting Failure Information 5.2 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. Table 5-2: Maintenance Information No.
5. Collecting Failure Information No. Item Storage Location and File Name 7 NIF dump information file created when the dump nif command is executed [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] /usr/var/hardware/nif**.*** in the active or standby system where the command is executed (In Ver.10.5 or earlier, /dump0/nif**.cmd) **: NIF number of the specified NIF ***: Serial number assigned from when dump was collected. Up to two files, the oldest and latest files, are stored.
5. 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. (2) Transferring log information to the remote operation terminal Figure 5-3: Transferring Log Information Files to the Remote Operation Terminal > show logging > log.
5. Collecting Failure Information (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 <--------------2 Connected to 192.168.0.1. 220 FTP server (Version 6.00LS) ready. Name (192.168.0.1:staff1): staff1 331 Password required for staff1. Password: 230 User staff1 logged in.
5. 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. (1) Transferring dump files to a console Figure 5-5: Transferring Dump Files to a Console > cd > zmodem put rmdump > <--------------1 <--------------2 1.
5. Collecting Failure Information (1) Transferring maintenance information to the remote operation terminal or remote host Figure 5-8: Transferring Maintenance Information Files to the Remote Operation Terminal or Remote Host [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] > show tech-support ftp <---1 Specify Host Name of FTP Server. : 192.168.0.1 <---2 Specify User ID for FTP connections. : staff1 <---3 Specify Password for FTP connections. : <---4 Specify Path Name on FTP Server.
5. 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.
5. Collecting Failure Information Figure 5-10: Collecting Dump Files from the Remote Terminal client-host> ftp 192.168.0.60 <---1 Connected to 192.168.0.60. 220 192.168.0.60 FTP server (NetBSD-ftpd) ready. Name (192.168.0.60:staff1): staff1 331 Password required for staff1. Password: 230 User staff1 logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> binary <---2 200 Type set to I. ftp> get dump.tgz <---3 local: dump.tgz remote: .
5. Collecting Failure Information 5.3 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. Check the size of the file to be copied (tech.log) using the ls -l command.) > ls -l tech.
6 Line Test 6.
6. Line Test 6.1 Testing Line 6.1.1 Ethernet Port In line tests, the loopback points of frames or data sent for the test differs depending on the type of test specified.
6. Line Test > no test interfaces gigabitethernet 1/1 [Enter] > activate gigabitethernet 1/1 [Enter] IP8800/S3600 and IP8800/S2400 A case of test conducted on Port 1 of NIF 0 at a transmission interval of one second is shown as a test example. Execute the test interfaces command and the no test interfaces command in this order from the operation terminal. > inactivate gigabitethernet 0/1 [Enter] > test interfaces gigabitethernet 0/1 internal [Enter] (Wait about 1 minute.
6.
6. Line Test > no test interfaces gigabitethernet 0/1 [Enter] (Remove the loop connector from the corresponding port and restore the connection.) > activate gigabitethernet 0/1 [Enter] Check the test execution result in the same way for the test execution result of "(1)Checking frame loopback within system.
7 Restarting the System This chapter describes the procedures for restarting the system. 7.
7. Restarting the System 7.1 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.
7. Restarting the System 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.
7. Restarting the System Figure 7-4: Dump Collection Confirmation Message 1. Collect memory dump? Memory dump is already collected 3. Restart? Restarting without collecting memory dump 2. Delete existing Memory dump? 3.
7. Restarting the System Next, select whether to collect the dump. Figure 7-6: Selecting CPU Memory Dump Type Select whether to collect memory dump Parameter to input Collecting memory dump Not collecting memory dump Checking Collecting RM memory dump dump collection Not checking memory dump collection Collects memory dump when neither (checking/not checking) is selected dump-image no-dump-image None -f As memory dump is collected in Step 2, no parameter is selected as shown in figure above.
7. Restarting the System Figure 7-7: CPU Memory Dump Collection Confirmation Message 1. Collect memory dump? Memorydump is already collected 3. Restart? Restarting without collecting memory dump 2. Delete existing memory dump? Restarting after overwriting memory dump 2.
Appendix Appendix A Contents of show tech-support Command Display 165
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. For details on the display contents, see "Operation Commands." [Note] Some of the information displayed by the show tech-support command is not covered in "Operation Commands.
Appendix A Contents of show tech-support Command Display Description No Parameter Specified unicast multi cast layer-2 show netstat all-protocol-address numeric Layer 4 related statistical information Y Y Y Y 19 show netstat statistics Layer 3 related statistical information Y Y Y Y 20 show dumpfile Sampled dump file information Y Y Y Y 21 ls -lTiR /dump0 Dump file information Y Y Y Y 22 ls -lTiR /usr/var/hardware Hardware dump file information (for Ver.10.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 49 cat /standby/var/log/ fixsb.log Kernel internal trace information (for Ver.10.5 and later) Y Y Y Y 50 cat /usr/var/pplog/ ppupdate.log Log information on updating software (for Ver.11.1 and later) Y Y Y Y 51 cat /usr/var/pplog/ ppupdate2.log Log information on updating software (for Ver.11.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 77 show lldp detail LLDP function neighboring system information Y Y Y Y 78 show oadp detail OADP function neighboring system information Y Y Y Y 79 show loop-detection Information on L2 loop detection (for Ver.10.7 and later) N N N Y 80 show loop-detection statistics Statistical information on L2 loop detection (for Ver.10.
Appendix A Contents of show tech-support Command Display No.
Appendix A Contents of show tech-support Command Display No.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 141 show ip rip statistics RIP statistical information RIP statistical information on each VRF (for Ver.11.0 and later) N Y N N 142 show ip rip advertised-routes summary Number of routes advertised by RIP Number of routes advertised by RIP on each VRF (for Ver.11.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 155 show graceful-restart unicast Operation state of the restart router for graceful restart in the unicast routing protocol (for Ver.10.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 176 show sflow detail sFlow statistical information (detail) display (for Ver.10.3 and later) Y Y Y Y 177 show mac-authentication Display of MAC authentication settings (for Ver.10.6 and later) N N N Y 178 show mac-authentication statistics Display of MAC authentication statistical information (for Ver.10.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 9 /sbin/dmesg Event information in kernel Y Y Y Y 10 cat /var/run/dmesg.boot Event information in kernel (for Ver.10.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 41 cat /usr/var/pplog/ ppupdate.log Log information during software update (for Ver.11.1 and later) Y Y Y Y 42 cat /usr/var/pplog/ ppupdate2.log Log information during software update (for Ver.11.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 69 show loop-detection Information on L2 Loop detection function (for Ver.10.7 and later) N N N Y 70 show loop-detection statistics Statistics information on L2 Loop detection function (for Ver.10.7 and later) N N N Y 71 sshow loop-detection logging Log information on L2 Loop detection function (for Ver.10.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 96 show netstat multicast numeric Kernel internal route related information (multicast) N N Y N 97 show ip multicast statistics Statistics information on IPv4 multicast (for Ver.10.5 and later) N N Y N 98 show ipv6 multicast statistics Statistics information on IPv6 multicast (for Ver.10.
Appendix A Contents of show tech-support Command Display No.
Appendix A Contents of show tech-support Command Display No.
Appendix A Contents of show tech-support Command Display No Parameter Specified unicast multi cast layer-2 Display of internal MAC authentication DB registration (Ver.10.6 and later) N N N Y Authenticated user information (account information) display (for Ver.10.6 and later) N N N Y show mac-authentication logging MAC authentication activity log display (for Ver.10.6 and later) N N N Y swdev logging Display of SW logs (for Ver.11.1.C and later) Y Y Y Y No.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 19 ls -lTiR /dump0 Dump file information Y Y Y Y 20 ls -lTiR /usr/var/hardware Hardware dump file information (for Ver.10.5 and later) Y Y Y Y 21 ls -lTiR /usr/var/core core file information Y Y Y Y 22 ls -lTiR /config config file information Y Y Y Y 23 ls -lTiR /var Memory file system information (for Ver.10.1.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 49 cat /var/tmp/gen/trace/ mng_sub.trc Configuration command trace information 3 (for Ver.10.7 and later) Y Y Y Y 50 tail -n 400 /var/tmp/gen/ trace/api.trc Configuration command trace information 4 (for Ver.10.7 and later) Y Y Y Y 51 tail -n 400 /var/tmp/gen/ trace/ctl.trc Configuration command trace information 5 (for Ver.10.
Appendix A Contents of show tech-support Command Display No. 76 Command (Display) show qos queueing No Parameter Specified unicast multi cast layer-2 for earlier than Ver.10.6 N Y Y Y for Ver.10.
Appendix A Contents of show tech-support Command Display No. Command (Display) Description No Parameter Specified unicast multi cast layer-2 100 port snd/rcv statistics Port sending/receiving statistical information Y Y Y Y 101 internal SW HW event statistics0 Internal SW event statistical information 0 (for Ver.10.5 and later) Y Y Y Y 102 internal SW HW event statistics1 Internal SW event statistical information 1 (for Ver.10.
Index Symbols "MC not found" is displayed when MC is accessed 22 "MC:--------" is displayed by entering the show system command or the show mc command 22 A Action to Be Taken When MAC Address Table Resource Shortage Occurs 130 Action to Be Taken When Resource Shortage of Shared Memory Occurs 135 Action to Be Taken When VLAN Identification Table Resource Shortage Occurs 133 Actions against Troubles on 1000BASE-X 32 Actions against Troubles on 10BASE-T/100BASE-TX/ 1000BASE-T 30 Actions against Troubles on 10
Index L Layer 2 Authentication Communication Failure 89 Layer 2 Communication by VLAN Is Disabled 38 Layer 2 Network Communication Failure 38 Login Authentication Using RADIUS/TACACS+ Is Disabled 25 Login from the Remote Operation Terminal Is Disabled 24 M MAC Address Table Resource Shortage 130 MIBs Cannot Be Obtained from SNMP Manager 110 Multicast Data Is Double-relayed on IPv4 PIM-SM Network 66 Multicast Data Is Double-relayed on IPv4 PIM-SSM Network 69 Multicast Data Is Double-relayed on IPv6 PIM-SM
