NECメーカーIP8800/S2400の使用説明書/サービス説明書
ページ先へ移動 of 250
Thoroughly read and store this manual. • Read and thoroughly un derstand safety-relat ed explana tions before using this product. • Keep this manual in a location close at hand for easy reference.
■ Applicable produ cts This manual describes models IP8 800/S6700, IP8800/S6 600 , IP8800/S63 00, IP8800/S3600, and IP8 800/S2400 series. ■ Caution when exporting The necessary procedures are to be adopted when exporting this product after first confirming the re gulations of the Foreign Ex change and Foreign T rade Law , U.
I Introduction ■ Applicable product This manual describes models IP8800/S6700, IP8800/S6600, IP8800/S 6300, IP8800/S3600 and IP8800/S2400. Please read the manual carefully and thor oughly under stand the instructions and cautions contained he rein before operating the device.
Introduction II For IP8800/S6700, IP8800 /S 6600, and IP8800/S6300 Procedures from unpacking the product to making basic settings at the initial installation IP8800/S6700 Quick S t art Guide (IP88S67-.
Introduction III For IP8800/S3600 Procedures from unpacking the product to making basic settings at the initial installation IP8800/S3600, IP8800/S2400 Quick S t art Guide (IP88S36-Q001) Information o.
Introduction IV For IP8800/S2400 ■ Conventions: abbreviations AC Alternating Current ACK ACKnowledge ADSL Asymmetric Digital Subscriber Line ALG Application Level Gateway ANSI American National Stan.
Introduction V CIR Committed Information Rate CIST Common and Internal Spanning Tree CLNP ConnectionLess Network Protocol CLNS ConnectionLess Network System CONS Connection Oriented Network System CRC.
Introduction VI MIP Maintenance domain Intermediat e Point MRU Maximum Receive Unit MSTI Multiple Spanning Tree Instanc e MSTP Multiple Spanning Tree Protoco l MSU Management and Switching Unit MTU Ma.
Introduction VII TOS Type Of Service TPID Tag Protocol Identifier TTL Time To Live UDLD Uni-Directional Link Detection UDP User Datagram Protocol UPC Usage Parameter Control UPC-RED Usage Parameter Co.
.
i Content s Introduction I Safety Guide [ IP8800/S6700] v Safety Guide [ IP8800/S6600] xvii Safety Guide [ IP8800/S6300] xxix Safety Guide [ IP8800/S3600] [IP88 00/S2400] xli 1 Overview 1 1.1 Failure Analysis Overview 2 1.2 System and Partial Fa ilure Analysis Overview 3 1.
Contents ii 3.4 Network Interface Communication Failure 27 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.
Contents iii 3.13 Communication Failure on High-reliability Fu nction 103 3.13.1 GSRP Communication Failures 103 3.13.2 Communication with VRRP Confi guratio n in IPv4 Network Is Disabled 105 3.13.3 Communication with VRRP Confi guratio n in IPv6 Network Is Disabled 107 3.
Contents iv 5.1.2 Collecting Failure Information U sing dump Command [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 140 5.2 T ransferring Fil es for Maintenance Information 144 5.2.1 Transferring Files Using f tp Co mmand 145 5.2.2 T ransferring Files Using zmodem Command [IP8800/S3600] [IP880 0/S2400] 148 5.
v Safety Guide [IP8800/S6700] ■ Safety guide for t he IP8800/S6700 series • This document provides safety-related notices for use of the IP8800/S6700 serie s. T o util ize the functions of this device, read this document completely and carefully before using the device.
Safety Guide [IP8800/S6700] vi ■ In case a failure should occur , power off the devi ce immediately . • In case fume or unusual odor sh ould occur , o r foreign matters shoul d come into the device, power off the device as follows. If the device is used in a faulty st ate, fire disasters or electric shock may be caused.
Safety Guide [IP8800/S6700] vii ■ Grounding is required. • When the device is connected to the power supp ly of 100V AC, leak current of up to 3.5mA flows for each device. Be sure to use the grounded outlet. If the powe r supply is used without grounding, an electric shock may be caused and failures may occur due to electric noise.
Safety Guide [IP8800/S6700] viii ■ 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 spec ialized carrier .
Safety Guide [IP8800/S6700] ix ■ Before powering off, turn of f all power switches or breakers on the device. • Multiple input power supplies are provided to the device. Befo re powering off, turn of f all power switches (when AC power supply is mounted) or b reakers (w hen DC power supply is mounted) on the device.
Safety Guide [IP8800/S6700] x ■ Do not install the device in a humid or dusty environment. • Do not install the de vice in a humi d or dusty environ ment. Fire disasters or el ectric shock may be caused. • Moving the device fro m a cold place to a warm place may form condensation on the surface or internal o f the device.
Safety Guide [IP8800/S6700] xi ■ Do not drop an optional component. • Handle the opti onal component careful ly not to drop it. If dropped, pe rsonal injury may be caused . • The weight and depth of the DC power supply are 5.6 kg/12.4 lb and 163 mm/6.
Safety Guide [IP8800/S6700] xii ■ 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 .
Safety Guide [IP8800/S6700] xiii ■ Do not power off the device dur ing sof tware update (when the ppupdate command is being executed). • By the execution of the ppupdate command, the device automatically restart s.
Safety Guide [IP8800/S6700] xiv ■ For carrying or packaging t he device and optional compone nt, use an antistatic wrist strap. • Use an antistatic wrist strap. If you handle the devi ce without the antistatic wris t strap, the device can be damaged by the static electricity .
Safety Guide [IP8800/S6700] xv ■ Do not bring a TV or ra dio close to the device. • Leaving a TV or radio close to the device can adverse ly influence to each othe r . 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.
.
xvii Safety Guide [IP8800/S6600] ■ Safety guide for t he IP8800/S6600 series • This document provides safety-related notice s for use of the IP8800/S6600 series. T o utilize the functions o f this device, read this document completel y and carefully before using the device.
Safety Guide [IP8800/S6600] xviii ■ In case a failure should occur , power off the devi ce 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 stat e, fi re disasters or elec tric shock may be caused.
Safety Guide [IP8800/S6600] xix ■ Grounding is required. • Leak current of up to 3.5mA flows fo r each device. If connecting the device with AC power , be sure to use the grounded outlet. If the power sup ply is used without gr ounding, an ele ctric shock may be caused and failures may occur due to electric noise.
Safety Guide [IP8800/S6600] xx The label below is attached to the device. ■ Handle the power c able with caution. • Do not put a heavy material on the power cable or do not pu ll, bend, or modify the power cable. The power cable will be damaged and fire disasters or electric s hock may be caused.
Safety Guide [IP8800/S6600] xxi ■ Work to add or replace eq uipment must be performed by a trained engineer or maintenance personnel. • T o add or replace opti onal components must be p erfor med by a trained engineer o r maintenance personnel.
Safety Guide [IP8800/S6600] xxii ■ Do not install the device in a humid or dusty environment. • Do not install the device in a humid or dusty environm ent. Fire disaste rs or el ectric 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.
Safety Guide [IP8800/S6600] xxiii ■ Do not block the intake and/or exhaust port. • Do not block the intake/exhaust port of the device. Bl ocki ng 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.
Safety Guide [IP8800/S6600] xxiv ■ When removing the fan unit, do not put your hand close to the rotating fan. • The fan may still be rotating immediately after the remo val of the fan unit. While the fan is rotating, do not put your hand or fing er close to it.
Safety Guide [IP8800/S6600] xxv ■ 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 stoppi ng to prevent getting burn ed.
Safety Guide [IP8800/S6600] xxvi ■ Do not power off the device dur ing sof tware update (when the ppupdate command is being executed). • By the execution of the ppupdate command, the device automatically restarts.
Safety Guide [IP8800/S6600] xxvii ■ For carrying or packaging t he device and optional component, use an antistatic wrist strap. • Use an antistatic wrist strap. If you handle the devi ce without the antistatic wrist strap, the device can be damaged by the static e lectricity .
Safety Guide [IP8800/S6600] xxviii ■ Do not bring a TV or r adio close to the device. • Leaving a TV or radio close to the device can adversely infl uence 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.
xxix Safety Guide [IP8800/S6300] ■ Safety guide for the IP8800/S6300 series • This document provides safety-related notice s 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 alwa ys refer it later .
Safety Guide [IP8800/S6300] xxx ■ In case a failure should occur , power off the devi ce 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 stat e, fi re disasters or elec tric shock may be caused.
Safety Guide [IP8800/S6300] xxxi ■ Grounding is required. • Leak current of up to 3.5mA flows for each device. For co nnecting to the AC power supp ly , be sure to use the grounded outlet. If the power sup ply is used without gr ounding, an ele ctric shock may be caused and failures may occur due to electric noise.
Safety Guide [IP8800/S6300] xxxii ■ The device must be carried and inst alled by at least three people. • The table below shows mass of the devices. The device must be carried and i nstalled by at least three people. Otherwise, a personal in jury due to drop or fall may be caused.
Safety Guide [IP8800/S6300] xxxiii ■ Before powering off, turn of f all power switches or breakers on the device. • Multiple input power su pplies are provided to the device. Before po wering off, turn of f all power switches (when AC power supply is mounte d) or breakers (when DC po wer supply is mounted) on the de vice.
Safety Guide [IP8800/S6300] xxxiv ■ Do not install the device in a humid or dusty environment. • Do not install the device in a humid or dusty environm ent. Fire disaste rs or el ectric 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.
Safety Guide [IP8800/S6300] xxxv ■ Do not block the intake and/or exhaust port. • Do not block the intake/exhaust port of the device. Bl ocki ng the intake/exhaust port keeps heat inside and fire disasters may be caused. Keep a space of at le ast 70mm/2.
Safety Guide [IP8800/S6300] xxxvi ■ When removing the fan unit, do not put your hand close to the rotating fan. • The fan may still be rotating immediately after the remo val of the fan unit. While the fan is rotating, do not put your hand or fing er close to it.
Safety Guide [IP8800/S6300] xxxvii ■ 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 stoppi ng to prevent getting burn ed.
Safety Guide [IP8800/S6300] xxxviii ■ Do not power off the device dur ing sof tware update (when the ppupdate command is being executed). • By the execution of the ppupdate command, the device au tomatically restart s.
Safety Guide [IP8800/S6300] xxxix damaged by the static e lectricity . ■ After removing an optional component, be sure to att ach a blank panel. • After removing an optional component, be sure to atta ch a blank panel. Using the device without the blank panel attached, the air flow in the device cannot be main tained.
Safety Guide [IP8800/S6300] xl ■ Do not bring a TV or r adio close to the device. • Leaving a TV or radio close to the device can adversely infl uence 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.
xli Safety Guide [IP8800/S3600] [IP8800/S2400] ■ Safety guide for the IP88 00/S3600 and IP8800/ S2400 series • This document provides safe ty-related notices for use of the IP88 00/S3600 and IP8800/S2400 series . T o utilize the functions of this device, read this docu ment co mpletely and carefully before using the device.
Safety Guide [IP8800/S3600] [IP8800/S2 400] xlii ■ In case a failure should occur , power off the devi ce immediately . • In case a trouble such as smo ke or unusual odor shoul d occur or foreig n materials or water sho uld come in to the device, power off the device immediately .
Safety Guide [IP8800/S3600] [IP8800/S2400] xliii ■ Do not use power not specified. • Do not use a supply voltage not specified. Fire disasters or ele ctric shock may be caused. ■ The current capacity supplied to the power distribution p ane l must be larger than the operating current of the breaker .
Safety Guide [IP8800/S3600] [IP8800/S2 400] xliv ■ Do not use the cable with the protection cap detached. • Do not remove protection cap except whe n connecting the cable . Operating them with the protection cap detached may cause an electric shock.
Safety Guide [IP8800/S3600] [IP8800/S2400] xlv ■ Do not place the device in an unstable location. • If the device i s being placed on a table, be sure to in stall it horizontally on a workbench or the like that can sufficiently bear the weight of the device.
Safety Guide [IP8800/S3600] [IP8800/S2 400] xlvi ■ Precaution on carrying the device • When moving the device, power off the device, remove the power cable out of the ou tlet, remove a ll other cables from the device, and then move th e device. Ot herwise, the device or cable may be defo rmed or damaged.
Safety Guide [IP8800/S3600] [IP8800/S2400] xlvii off the power switches on all power supplies mounted on the device. ■ Do not touch the devic e directly if you have metal allergies. • This device is coated with metals includi ng zinc, nickel, and gold.
Safety Guide [IP8800/S3600] [IP8800/S2 400] xlviii ■ Do not ride, recline, or pl ace 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.
Safety Guide [IP8800/S3600] [IP8800/S2400] xlix ■ Do not install the device in any place possibly reac hing a high temperature. • Be careful that th e parts may be damaged if left in a place exposed to di rect sunlight or close to a heating apparatus.
Safety Guide [IP8800/S3600] [IP8800/S2 400] l ■ Before installing/uninst al ling 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.
Safety Guide [IP8800/S3600] [IP8800/S2400] li ■ For carrying or pack aging the device and optional com ponent, use an antistatic wrist strap. • Use an antistatic wrist strap. If you handle the device without the antis tatic wrist strap, the device can be damaged by the static electricity .
.
1 1 Overview This chapter outlines the failure analysis. 1.1 Failure Analysis Overview 1.2 System a nd Partial Fa ilure Analysis Overview 1.3 Functional Failure Analysis Overview.
1. Overview 2 1.1 Failure Analysis Overview For any problems with IP8800/S6700, IP880 0/S6600, IP8800/S6300, IP8800/S3600, and IP8800/S2400, refer to this manual. T o visually check the system, follow t he instructions in " 1.2 System and Partial Fa ilure Analysis Overview .
1. Overview 3 1.2 System and Partial Failure Analysis Overview 1.2.1 Failure Analysis for IP8800 /S6700, IP8800/S 6600, and IP8800/ S6300 If a failure occurs during operation and the system can be visually and directly checked, follow the procedure in " 2.
1. Overview 4 *1 BCU/CSU/MSU can be powered of f by Inactivate opera tion from the system operati on panel or by inputting the command from the operation term inal. *2 The switch is provided in an indent ed position on the panel su rface. Us e a thin tip screwdriver t o press it.
1. Overview 5 For IP8800/S3600 and IP8800/S2400, the generi c names of the models are as follows: • AC power supply model: IP8800/ S3640-24T , IP8800/S3630-24T , IP8800/S3630-24T2X, IP8800/S3630-24P.
1. Overview 6 Note: Figure 1-2 and T able 1-2 show a typical system. For more details on each system , see "Hardware Installation Guide." 11 1-24 LED: Green/ Orange Indicates the operatio n status of 10/ 100/1000BA SE-T Ethernet po rt.
1. Overview 7 1.3 Functional Failure Analysis Overview The overview of functional failur e analysis for this system is shown in the table b elow . Some communication failure in the lowe r layer may cause the communication fa ilure in the upper layer , check the items in the lower layer as well .
1. Overview 8 IPv4 unicast r outing communication failure No RIP in formation 3.7.1 No RIP Routing Information Exists No OSPF information 3.7.2 No OSPF Routing Infor mation Exists No BGP4 information 3.7.3 No BG P4 Routin g Information Exists No VRF information 3.
1. Overview 9 Neighboring syst em information cannot be acquired by LLDP function - 3.16.1 Unable to Obtain Neighbor ing System Information via LLDP Function Neighboring syst em information cannot be acquired by OADP function - 3.16.2 Unable to Obtain Neighbor ing System Information via OADP Function Communication failure in NTP - 3.
.
11 2 T roubleshooting System Failures This chapter explains how to deal with the problems on the system. 2.1 T roubleshooting for IP8 800/S6700, IP8800/S6600, and IP8800/S6300 2.
2. T roubleshoo ting System Failures 12 2.1 T roubleshooting for IP 8800/S6700, IP8800/S6600, and IP8800/S6300 2.1.1 T roubleshooting Proced ure on System Failures Follow the procedure below when the system failed. T a ble 2-1: T r oubleshooting System Failu res No.
2. T roubleshooting System Failure s 13 T able 2-2: Power Fai lure Check Items 5 Erro r message output to the system operation panel T ake the action against the cor respo nding error message in the manual "Message Log Refe rence.
2. T roubleshoo ting System Failures 14 2.1.2 Replacement Method of Optional Component s The optional component repl acement procedures are described in "H ardware Installation Guide.
2. T roubleshooting System Failure s 15 2.2 T roubleshooting for IP8800/S3600 and IP8800/ S2400 2.2.1 T roubleshooting Proc edure on System Failures Follow the procedure below wh en the system failed.
2. T roubleshoo ting System Failures 16 T able 2-4: Isolating Power Supply Failure 5 • ST1 LED on the system is blinking in red • LINK LED (10GB ASE-R port and 1000BASE-X po rt) and 1-48 LED (10/10 0/ 1000BASE-T port) on each port of the sy stem are lit in orange or OFF System or line has failed.
2. T roubleshooting System Failure s 17 2.2.2 Isolating Failures on External Power Unit If the external power unit fails, follow the steps below to isolate the failure. T able 2-5: Isol ating Failures on External Power Unit T able 2-6: Isol ating Failures on External Power Unit (Main Body) T ab le 2-7: Isolating Failure s on Power Module No.
2. T roubleshoo ting System Failures 18 2.2.3 Replacement Method of Syst em and Optional Component s The replacement procedures for optiona l components are described in "Hardw are Installation Guide." Follow the procedures described in the manual.
19 3 T roubleshooting 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 T erminal 3.
3. T roubleshoo ting Functional Failures in Operation 20 3.20 Problems on Redundant Conf iguration of Basic Sw itch ing Unit (BSU) [IP880 0/S6700] 3.23 Communication Failure Caused by Settings of Filt.
3. T roubleshooting Functional Failures in Operation 21 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 proced ure below . 1. Reporting to th e system a dministrator First, consult the system administra tor .
3. T roubleshoo ting Functional Failures in Operation 22 3.2 Problems on MC 3.2.1 "MC:--------" is di splayed by entering the show system command or the show mc command When "MC:-------.
3. T roubleshooting Functional Failures in Operation 23 3.3 Problems on Operation T erminal 3.3.1 Unable to Input/Display from the Console Correctly When there is a problem con necting to the console, fol low the instruction in " T able 3-3: Problems and Actions When Connecting to Console .
3. T roubleshoo ting Functional Failures in Operation 24 T able 3-4 : Problems and Actions When Connecting to Modem 3.3.2 Login from the Remote Operation T erminal Is Failed When connecting to the remote operation terminal fail s, take actions in the following table.
3. T roubleshooting Functional Failures in Operation 25 3.3.3 Login Authentication Usin g RADIUS/T ACACS+ Is Disabled If login authentication using RADIUS/T ACACS+ is failed, check the following: 1. Communication with the RADIUS/T ACACS+ server Use the ping command to see if communication from this system to the RADIUS/T ACACS+ server is achieved.
3. T roubleshoo ting Functional Failures in Operation 26 3. Notes on writing command list Care must be taken about th e handling of spaces when you describe the command list for the command authorization on this system on the RADIUS/T AC ACS+ server .
3. T roubleshooting Functional Failures in Operation 27 3.4 Network Interface Communication Failure 3.4.1 Ethernet Port Ca nnot Be Connected If the Ethernet port has possibly cau sed th e communicati on failure, check for the NIF [IP8800/S6700] [IP8800/ S6600] [IP8800/S6300] and port statuses as follows.
3. T roubleshoo ting Functional Failures in Operation 28 T able 3-7 : Check and Action for Port S tatus (3) Checking statistical information Enter the show port statistic s command to check the number of sen t/received packets and the number of discarded packets on all ports installed on this system .
3. T roubleshooting Functional Failures in Operation 29 Figure 3-2: Example of "Checking Port Operation St atus" [IP8800/S6700] [IP8800/S66 00] [IP8800/S6300] > show port statistics 2006/.
3. T roubleshoo ting Functional Failures in Operation 30 3.4.3 Actions against T roubl es on 10BASE-T/100BASE-TX/ 1000BASE-T If a trouble occurs on 10BASE-T/100BASE -TX/1 000BASE-T , follow the proce dure below to isolate the problem. 1. Checking log For the log, see the manual "Message Log Reference.
3. T roubleshooting Functional Failures in Operation 31 T able 3-9: Troubleshooting for Failed 10BASE-T/100BASE -TX/1000B ASE-T No. Troubleshooting S teps Problem Action 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.
3. T roubleshoo ting Functional Failures in Operation 32 3.4.4 Actions against T roubles on 1000BASE-X If a trouble occurs on 1000BASE-X, follow the procedure below to isolate the problem. 1. Checking log For the log, see the manual "Message Log Reference.
3. T roubleshooting Functional Failures in Operation 33 3.4.5 Actions against T roubles on 10GBASE-R If a trouble occurs on 10GBASE-R, follow th e procedure below to isolate the problem. 1. Checking log For the log, see the manual "Message Log Reference.
3. T roubleshoo ting Functional Failures in Operation 34 2. Isolating the problem according to the failure analysis method Isolate the problem according to the failure analysis method listed below . T able 3-1 1: Failure Analysis Me thod for Troubles on 10GBASE-R No.
3. T roubleshooting Functional Failures in Operation 35 3.4.6 Communication Failure on Using PoE If electricity is not provided wh en PoE is in use, isolate th e problem using the failure anal ysis meth ods listed in the following table.
3. T roubleshoo ting Functional Failures in Operation 36 3.4.7 Communication Failure on Using Link Aggregation If communication is disabled or if dege nerated operation is performed when link aggregation is in use, isolate the problem using the failure analysis me thods listed in the following table.
3. T roubleshooting Functional Failures in Operation 37 2 Check the setting of failed port status using the show channel-group command with "detail" parameter specified. Check the status of each port. If all port s in a link aggregation group are Down, th e link aggregation grou p is also Down.
3. T roubleshoo ting Functional Failures in Operation 38 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 pr oblem using failure analysis me thod listed in the following table.
3. T roubleshooting Functional Failures in Operation 39 that the identical MAC address is set in the configuration and is disabl ed. # show vlan mac-vlan : VLAN ID:500 MAC Counts:4 0012.e200.aa01 (static) 001 2.e200.aa02 (static) 0012.e200.aa03 (static) 001 2.
3. T roubleshoo ting Functional Failures in Operation 40 [When T ype displayed is Dot1x] See " 3.12.1 Communication Fail ure on Using IEEE 802.1X ." [When T ype displayed is W a] See " 3.12.2 Communication Failure on Using W eb Authentication .
3. T roubleshooting Functional Failures in Operation 41 bridge for each MST instance for route bridge, when checking the route bridge. T able 3-14: S panning Tree Failure Analysis Method 3.5.3 Failures on Using Ring Protocol This subsection describe s Autonomous Ex tensible Ring Protocol failure.
3. T roubleshoo ting Functional Failures in Operation 42 and isolate the problem. Figure 3-4: Analysis Flow When the Ring Protocol is not running normally or the ring network failure is dete cted, isolate the problem by following the failure analys is methods shown in the table below for all the nodes configuring the ring network.
3. T roubleshooting Functional Failures in Operation 43 4 Execute the show axrp command to check the ring po rt for each VLAN group and its operation state. Go to No. 5 if "Ring Port" and "Role/State" correspon d to the port state of network configuration.
3. T roubleshoo ting Functional Failures in Operation 44 3.5.4 Multicast Relay by IGMP snooping Is Disabled If multicast relay is disa bled when using IGMP snooping, follow the analys is flow to identify the symptom using steps shown in the table below and isolate the problem.
3. T roubleshooting Functional Failures in Operation 45 T able 3-16: T r oubleshooting on Multicast Relay No. T roubleshooting S teps and Command Action 1U s e t h e show logging command to check if any failure occur s. Check the following: - Check the log informati on for physical failures.
3. T roubleshoo ting Functional Failures in Operation 46 * If this system is the IGMP querier , the address displaye d in "IGMP querying system" ma tches the address displayed in "IP Ad.
3. T roubleshooting Functional Failures in Operation 47 3.5.5 Multicast Relay by MLD snooping Is Disabled If multicast relay is disabled when using MLD snooping, follow the analys is flow to identify the symptom using steps shown in the table below and isolate the problem.
3. T roubleshoo ting Functional Failures in Operation 48 T able 3-17: Troubleshooting on Multicast Relay No. Troubleshooting S teps and Command Action 1U s e t h e show logging command to check if any failure occurs. Check the log informati on for physic al failures.
3. T roubleshooting Functional Failures in Operation 49 * If this system is the MLD querier , th e address displayed in "MLD querying sy st em" matches the a d dress displayed in "IP Ad.
3. T roubleshoo ting Functional Failures in Operation 50 3.6 IPv4 Network Communication Failure 3.6.1 Communication Is Disabled or Is Disconnected There are three possibl e causes t hat result in comm unication failure on the IPv4 ne twork using this system.
3. T roubleshooting Functional Failures in Operation 51 Figure 3-7: F ailure Analysis Procedure When IPv4 Communica tion Disabled (1) Checking log Communication may be interrupted by a line failure (or dama ge). The following procedure displays hardware error messages among this sy stem's log messages.
3. T roubleshoo ting Functional Failures in Operation 52 (2) Checking interface st atus It is also possible that a failure h as occurred on the hardware of the neighboring sy stem connected to this system even if the hardware on this system is running properly .
3. T roubleshooting Functional Failures in Operation 53 (6) Checking unicast routing informatio n Check the route information acquired by this system if co mmunication is not possible even when the ad.
3. T roubleshoo ting Functional Failures in Operation 54 3.6.2 IP Addresses Cannot Be Assigned Using DHCP Function (1) DHCP/BOOTP relay communication failu re There are three possible causes for DH CP/BOOTP relay comm unication failures: 1. Configuration relating to DHCP/BOOTP rela y has changed 2.
3. T roubleshooting Functional Failures in Operation 55 (a) Checking the log and interface On possible cause for the server not assigning IP addresse s 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.
3. T roubleshoo ting Functional Failures in Operation 56 2. Execute the show ip route command to check the route info rmation acquired by this system. 3.
3. T roubleshooting Functional Failures in Operation 57 Figure 3-9: DHCP Server Failure Analysis Procedure (a) Checking configuration IP addresses may not be assigned to cl ients due to configurati on setting errors for resources on the DHCP server . The followings are the steps to check the configuration: 1.
3. T roubleshoo ting Functional Failures in Operation 58 communication to the other party cannot be verified with the ping command, use ping to check communication toward clients starting from the system clo sest to this system. For an example of issuing ping and how to interpret the result, see the manua l "Configuration Settings.
3. T roubleshooting Functional Failures in Operation 59 Figure 3-10: T rou bleshooting for DHCP Server Failure with DNS Cooperatio n (a) Checking configuration This failure may be cause d by the incorrect DNS update on Dynamic DNS due to the DHCP server errors or the conflict with the settings on the DNS se rver .
3. T roubleshoo ting Functional Failures in Operation 60 (d) Identifying the extent of the failure (performed from this system) If no failure is found o n this system, a failure may exist somewhere in the rout e between this system and the remote system.
3. T roubleshooting Functional Failures in Operation 61 3.7 IPv4 Unicast Routing Communication Failure 3.7.1 No RIP Routing Information Exists Isolate the problem according to the fail ure analysis method listed below if RIP route information does not exist in the displayed route informatio n acquired by this system.
3. T roubleshoo ting Functional Failures in Operation 62 3.7.3 No BGP4 Routing Information Exists Isolate the problem according to the fa ilure analysis method listed below if BG P4 route in formation does not exist in the displayed route informati on acquired by this system.
3. T roubleshooting Functional Failures in Operation 63 3.8 IPv4 Multicast Routing Communication Failure Actions to be taken if IPv4 multicast com munication failures occu r on this system are described below .
3. T roubleshoo ting Functional Failures in Operation 64 (2) BSR check items The table below shows the items to be checked when this system is BSR in t he IPv4 PI M-SM network configuration. 4 Confirm in the configuration that suppress ion of protocol packet and multicast packet relay through filtering, etc.
3. T roubleshooting Functional Failures in Operation 65 T able 3-23: BSR Check Items (3) Rendezvous point router check items The table below shows the items to be checked when this system is the rendezvous point router in the IPv4 PIM-SM network configuration.
3. T roubleshoo ting Functional Failures in Operation 66 (5) first-hop-router check items The table below shows the items to be checked when this system is the first-hop-router in the IPv4 PIM-SM network configuration. T able 3-2 6: first-hop-router Check Items 3.
3. T roubleshooting Functional Failures in Operation 67 T able 3-27: Check Items When Double-relay Continues 3.8.3 Communication on IPv4 PIM-SSM Network Is Disabled If multicast relay on the IPv4 PIN-SSM netw ork configu ration is disa bled, isolate the cause accor ding to the failure analysis method below .
3. T roubleshoo ting Functional Failures in Operation 68 (2) last-hop-router check items The table below shows the items to be checked when this system is the last-hop-router in the IPv4 PIM-SSM network configuration. T able 3-2 9: last-hop-router Check Items 3 Confirm that IGMP snooping is set to the interface with PIM enabled.
3. T roubleshooting Functional Failures in Operation 69 (3) first-hop-router check items The table below shows the items to be ch ecked when this system is the first- hop-router in the IPv4 PIM-SSM network configuration. T able 3-30: first-hop-router Check Items 3.
3. T roubleshoo ting Functional Failures in Operation 70 T able 3-3 1: Check Items When Double-relay Continues 3.8.5 IPv4 Multicast Communi cation Failure In VRF [OP-NP AR] If IPv4 multicast communication failure st i ll continues, ch eck the following: T able 3-3 2: Check Items for VRF No.
3. T roubleshooting Functional Failures in Operation 71 3.9 IPv6 Network Communication Failure 3.9.1 Communication Is Disabled or Is Disconnected There are th ree possible caus es that result i n comm unication failure on the IPv6 ne twork using this system.
3. T roubleshoo ting Functional Failures in Operation 72 (1) Checking the log and interface Communication may be interrupted by a lin e failure (or damage) or a neighbor ing system failure. Check the log displayed on this system or the interface up/down st atus using the show ipv6 interface command.
3. T roubleshooting Functional Failures in Operation 73 1. Log in to the system. 2. Execute show ipv6 route command to check the route info rmation 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.
3. T roubleshoo ting Functional Failures in Operation 74 Figure 3-14: IPv6DHCP Server Failure An alysis Procedure (a) Checking the log and interface Communication may be interrupted by NIM or interface failure (or damage) or fail ure in the ne ighboring system.
3. T roubleshooting Functional Failures in Operation 75 Check the number of remaining prefixes that can be distributed from the IP v6DHCP server using the show ipv6 dhcp server statistics command. For the instructions, see "Conf iguration Settings.
3. T roubleshoo ting Functional Failures in Operation 76 detail command, it is necessary to matc h the displayed DUIDs and client syst ems. T o do that, compare the val ue of distributed prefixes displayed in th e bin ding information and the informati on of prefixes distributed to client system.
3. T roubleshooting Functional Failures in Operation 77 T able 3-34: Retentio n of Route Information to Prefix Distribution T arg et (Legend) Y : Guaranteed Y/N: Not guaranteed (each status informatio.
3. T roubleshoo ting Functional Failures in Operation 78 (c) Checking the DUID Y ou can check the DUID in the "< Server DUI D >" section of the output of the show ipv6 dhcp server statistics command. For details, see "Configuration Settings.
3. T roubleshooting Functional Failures in Operation 79 3.10 IPv6 Unicast Routing Communication Failure 3.10.1 No RIPng Routing Information Exi sts Isolate the problem according to the fail ure analysis method listed below if RI Png route informati on does not exist in the displayed route informat ion acquired by this system.
3. T roubleshoo ting Functional Failures in Operation 80 3.10.3 No BGP4+ Routing Information Exist s Isolate the problem according to the fa ilure analysis method listed below if BG P4+ route information does not exist in the displayed route informati on acquired by this system.
3. T roubleshooting Functional Failures in Operation 81 3.1 1 IPv6 Multicast Routing Communication Failure Actions to be taken if IPv6 multicast com munication failures occu r on this system are described below .
3. T roubleshoo ting Functional Failures in Operation 82 (2) BSR check items The table below shows the items to be checked when this system is BSR in t he IPv6 PI M-SM network configuration. 5 Confirm in the configur ation that suppression of pr otocol packet and multicast packet relay through filteri ng, etc.
3. T roubleshooting Functional Failures in Operation 83 T able 3-39: BSR Check Items (3) Rendezvous point router check items The table below shows the items to be checked when this system is the rendezvous point router in the IPv6 PIM-SM network configuration.
3. T roubleshoo ting Functional Failures in Operation 84 (5) first-hop-router check items The table below shows the items to be checked when this system is the first-hop-router in the IPv6 PIM-SM network configuration. T able 3-4 2: first-hop-router Check Items 3.
3. T roubleshooting Functional Failures in Operation 85 3.1 1.3 Communication on IPv6 PIM-SSM Network Is Disabled If multicast relay on the IPv6 PIN-SSM netw ork configu ration is disa bled, isolate the cause accor ding to the failure analysis method below .
3. T roubleshoo ting Functional Failures in Operation 86 (2) last-hop-router check items The table below shows the items to be checked when this system is the last-hop-router in the IPv6 PIM-SSM network configuration. T able 3-4 5: last-hop-router Check Items 7 Check to see if the unicast route to the multicast data sender exists.
3. T roubleshooting Functional Failures in Operation 87 (3) first-hop-router check items The table below shows the items to be ch ecked when this system is the first- hop-router in the IPv6 PIM-SSM network configuration. T able 3-46: first-hop-router Check Items 3.
3. T roubleshoo ting Functional Failures in Operation 88 T able 3-4 7: Check Items When Double-relay Continues No. Troubleshooting S teps and Command Action 1 Check the PIM neighboring inform ation on the interface of the network having multiple routers.
3. T roubleshooting Functional Failures in Operation 89 3.12 Layer 2 Authentication Communication Failure 3.12.1 Communicati on Failure on Using IEEE 802.1X If authentication is disabled when using IEEE 802.1X, isol ate the prob lem by following fa ilure analysis methods shown in the table below .
3. T roubleshoo ting Functional Failures in Operation 90 6 Execute the show dot1x logging command and check to see if authentication failed. • If "New Supplicant Auth Fail." is ou tput, authentication failed due to the following cause. Ch eck to see if ther e is any problem.
3. T roubleshooting Functional Failures in Operation 91 If communication is not possible on the port or VLAN on wh ich IEEE 802.1X runs, isolat e the problem by following failure analysis methods shown in the table be low . Otherwise, see " 3.5 Layer 2 Network Communication Failure .
3. T roubleshoo ting Functional Failures in Operation 92 T able 3-4 9: IEEE 802.1X Failure Analysis Method [IP8800/S3600 ] [IP8800/S2400] 3.12.2 Communication Failure on Using W eb Authentication Isolate the problem according to the fa ilure analysis method described in " T abl e 3-50: Fail ure Analysis Method for W eb Authenticat ion .
3. T roubleshooting Functional Failures in Operation 93 4 Check to see authentication Ipv4 access list • For IP8800/S6700, IP8800/S6600, an d 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. T roubleshoo ting Functional Failures in Operation 94 For the configuration relating to the W e b authentication, check the following: 1 1 Ex ecute the show web-authentication logging command to check to see if the system operates correctly . • If the log "The login failed bec ause of hardwar e restriction.
3. T roubleshooting Functional Failures in Operation 95 T able 3-51: Checking Web Authentication Configuration No. Check Point Troubleshooting S teps 1 Setting of W eb authentication configur ation Co.
3. T roubleshoo ting Functional Failures in Operation 96 For the configuration relating to the W eb au thentication accountin g, check the following. T a ble 3-52: Web Authentication Failure Analysis Meth od 5 Check to see the acce ss filter setting for authentication.
3. T roubleshooting Functional Failures in Operation 97 3.12.3 Communicati on Failure on Using MAC Authentication For MAC authentication failure, isolat e the problem according to the fail ure analysis method described in " Ta b l e 3-53: Failure Analysis Meth od for MAC Authentication .
3. T roubleshoo ting Functional Failures in Operation 98 For the configuration relating to the MA C authentication, check the following: 5 Check to see authentica tion IPv4 access list. • For IP8800/S670 0, IP8800/S6600 , and IP8800/S6300 models, go to No.
3. T roubleshooting Functional Failures in Operation 99 T able 3-54: Checking MAC Authentication Configuration For the configurati on relating to t he MAC authentic ation accounting , check the f ollowing. T able 3-55: MAC Authentication Failure Analysis Method 3.
3. T roubleshoo ting Functional Failures in Operation 100 T a ble 3-56: Authentication VLAN Failure Analysis Method No. T roubleshooting S teps and Command Action 1 Execute the show logging command and check to see if hardware failures are rec orded in the operation log.
3. T roubleshooting Functional Failures in Operation 101 For the configuration relating to the authentication VLAN, check the following. T able 3-57: Checking Authentication VLAN Configuration 8 Exec ute the show vlan mac-vlan command and confirm that the authenticated MAC address is registered in the MAC VLAN function.
3. T roubleshoo ting Functional Failures in Operation 102 3 Setting of DHCP relay agent Confi rm that the following inter-VLAN DHCP relay agent is set correctly: • Between pre-authentication VLAN an.
3. T roubleshooting Functional Failures in Operation 103 3.13 Communication Failure on High-reliability Function 3.13.1 GSRP Communication Failures If the communicat ion is not possib le in the GSRP configurat i on, isolate the pr oblem accord ing to the failure analysis method shown in the table below .
3. T roubleshoo ting Functional Failures in Operation 104 T able 3-5 9: Analysis Method for Abnormal S tatus in GSRP Configuration When detecting the reception timeout of GSRP Advertise in GSRP configuration cau ses unknown adjacency , isolate the cause according to the table below .
3. T roubleshooting Functional Failures in Operation 105 3.13.2 Communication with VRRP Conf iguration in IPv4 Network Is Disabled Isolate the problem according to the failure analysis me thods shown in the tab le belo w if communication with the VRRP configurati on is disabled.
3. T roubleshoo ting Functional Failures in Operation 106 7 Execute the show logging command and the show vrrpstatus command with "statistics" parameter specified to check the receiving status of the ADVER TISEMENT packets.
3. T roubleshooting Functional Failures in Operation 107 3.13.3 Communication with VRRP Conf iguration in IPv6 Network Is Disabled Isolate the problem according to the failure analysis me thods shown in the tab le belo w if communication with the VRRP configurati on is disabled.
3. T roubleshoo ting Functional Failures in Operation 108 5 Execute the show vrrpstatus comman d with "statistics" parame t er specified to check the receiving status of ADVER TISEMENT packets.
3. T roubleshooting Functional Failures in Operation 109 9E x e c u t e show vrrpstatus command with "detail" parameter specified to check the virtual router status.
3. T roubleshoo ting Functional Failures in Operation 110 3.14 SNMP Communication Failure 3.14.1 MIBs Cannot Be Obt ain ed from SNMP Manager Confirm that the configuration has been set correctly .
3. T roubleshooting Functional Failures in Operation 111 When using SNMPv3 Execute the show snmp-server command to confirm that the informat ion on the SNMP manager and trap has been registered in the configuration for this system.
3. T roubleshoo ting Functional Failures in Operation 112 3.15 T roubleshooting of sFlow S tatistics (Flow S tatistics) Function The flow for troubleshooting of sFlow statis tics function in this system is as follows. Figure 3-18: Troubleshooting Flow of sFlow S tatistics Function 3.
3. T roubleshooting Functional Failures in Operation 113 2093(2041) Exported sFlow samples : 37269 Couldn't exp orted sFlow samples : 0 sFlow collector data : Collector IP address: 192.
3. T roubleshoo ting Functional Failures in Operation 114 Figure 3-23: Display Example of Configuratio n 3 (config)# show interfaces interface gigabitethernet 1/2 switchport mode access sflow forward ingress <- sflow forw ard must be set here. ! (config)# •S e e " 3.
3. T roubleshooting Functional Failures in Operation 115 3.15.2 Flow Sample Does Not Reach Collector If problem still persists even after checking " 3.
3. T roubleshoo ting Functional Failures in Operation 116 3.16 Communication Failure s on Neighboring System Managing Function 3.16.1 Unable to Obt ain Neighbori ng System Information via LLDP Functio.
3. T roubleshooting Functional Failures in Operation 117 2 Execute the show oadp command to check the port inform ation displaye d. If the informa tion on the port to which the ne ighboring system is con nected appears in "En abled Port," go to No.
3. T roubleshoo ting Functional Failures in Operation 118 3.17 NTP Communication Failure 3.17.1 T ime Synchronization by NTP Is Disabled If time synchronization by NTP is disabled, isolate the pr oblem by following the failure analysis methods shown in the table below .
3. T roubleshooting Functional Failures in Operation 119 3.18 Communication Failure on IEEE802.3ah/UDLD Function 3.18.1 Port Becomes Inactive Du e to IEEE802.3ah/UDLD Function If the port becomes inactive due to I EEE802.3ah/UDLD function, isol ate the problem by following failure analysis methods shown in the table below .
3. T roubleshoo ting Functional Failures in Operation 120 3.19 Problems on Redundant Configuration of Basic Control Unit (BCU)/Cont rol and Switching Unit (CSU)/Management and Switching Unit (MSU) [IP8800/S6700] [IP8800/ S6600] [IP8800/S6300] 3.
3. T roubleshooting Functional Failures in Operation 121 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 th e redundant configuration, fo llo w the instruction shown below .
3. T roubleshoo ting Functional Failures in Operation 122 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.
3. T roubleshooting Functional Failures in Operation 123 3.21 Problems on Power Saving Feature 3.21.1 Schedule Is Di sabled [IP8800/S6700] [IP8800/S6600] If schedule is disabled, follow the instruction shown below .
3. T roubleshoo ting Functional Failures in Operation 124 3.22 Congestion Caused by Packets Processed Through CPU Is Not Recovered This section describes the procedur e when congestion caused by packets requiring the handling of CPU is not recovered.
3. T roubleshooting Functional Failures in Operation 125 4 Collecting ana lys is 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.
3. T roubleshoo ting Functional Failures in Operation 126 3.23 Communication Failure Caused by Settings of Filtering/QoS 3.23.1 Checking Filtering/ QoS Setting Information As a cause for communica tio.
3. T roubleshooting Functional Failures in Operation 127 IP8800/S3600 and IP8800/S2 400 1. Log in to the system. 2. Check the "discard packets" statistical in formation of the output interface using the show qos queueing command.
.
129 4 T roubleshooting Communication Failures Due to Resource Short a ge [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 4.1 MAC Address T able Resource Shortage 4.
4. T roubleshoo ting Communication Failures Due to Res ource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 130 4.1 MAC Address T able Resource Shortage 4.1.1 Checking Resource Usage of MAC Address T able This system outputs operati on log messages when the MAC address ta ble usage reaches 80% and 100% of the accommodating condition.
4. Troubleshooting Communication Failures Due to Res ource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 131 * The log message of No. 1 may b e output at the same time. If these log messages are output, the function that newly u ses the MAC addre ss table cannot be set.
4. T roubleshoo ting Communication Failures Due to Res ource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 132 *1 For details, see the ma nual "Operation Commands.
4. Troubleshooting Communication Failures Due to Res ource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 133 4.2 When Resource Short age of VLAN Identification T able Occurs 4.
4. T roubleshoo ting Communication Failures Due to Res ource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 134 If these log messages are output, the function that newly us es the VLAN identification a ddress table cannot be set.
4. Troubleshooting Communication Failures Due to Res ource Shortage [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] 135 4.3 When Resource Short age Occurs in Shared Memory 4.3.1 Checking Resource Us age of Shared Memory Shared memory usage can be checked with the show system command.
.
137 5 Collecting Failure Information This chapter focuses on collec ting the failure information. 5.1 Collecting Fail ure Information 5.2 T ransferring File s fo r Maintenance Information 5.
5. Collecting Failure Information 138 5.1 Collecting Failure Information The information on failures can be collected at once using the show tech-support command. This command can also transfe r the collec ted failure info rmation to a spe cified ftp serv er (see " 5 .
5. Collecting Failure Information 139 Figure 5-1: Col lecting Failure Info rmatio n from the Remote Operation T erminal 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-ft pd) ready.
5. Collecting Failure Information 140 5.1.2 Collecting Failure Information Using dump Command [IP8800/ S6700] [IP8800/S6600] [IP8800/S6300] (1) Collecting memory dump when commun ication failure occurs When any communication failur e occurs, co llect memory dump by execut ing all of the foll owing commands.
5. Collecting Failure Information 141 2. Execute the dump nif command for the faulty port from the active system. [Example] The following is an example when communi cation fa ilure occurs in NIF number 1 and port number 1. 1. Login the active system and execute the dump command.
5. Collecting Failure Information 142 For IP8800/S6600 1. Execute the dump psp command for active PS P from the active system. 2. Execute the dump nif command for all faulty por ts from the active system. 3. Execute the dump psp standby command for the standby PSP from the active system.
5. Collecting Failure Information 143 3. After above log is di splayed, execute next dump command. > dump psp standby Dump command accept. > 11/01 18:18:42 E3 MSU 25070700 2301:00 0000000000 PSP online dump comman d executed. 4. After above log is displayed, logi n the standby system and execute next dump command.
5. Collecting Failure Information 144 5.2 T ransferring Files for Maintenance Information This section describes how to transfer log information or dump information auto matic ally stored when failure occurred while opera ting to the console or remot e operation terminal.
5. Collecting Failure Information 145 5.2.1 T ransferring Files Using ftp Command Use the ftp command to transfer files between this system and the remote operation terminal.
5. Collecting Failure Information 146 2. Specify the address of target. 3. Changes the interaction mode. 4. Enter binary mode.* 5. Specify the target directory . 6. T ransfers the dump file. * Be sure to transfer d ump files in binar y mode. The correc t dump information wi ll not be obtain ed if dump files are transferred in ASCII mode.
5. Collecting Failure Information 147 (3) T ransferring failure backup information files to the remote operation termin al Figure 5-4: Transferring the Failure Backup Information File to the Remote Operation T erminal > cd /usr/var/core/ > ls <----------------- --------1 nimd.
5. Collecting Failure Information 148 5.2.2 T ransferring File s Using zmodem Command [IP8800/S3600] [IP8800/S2400] T o transfer files between this system and the console connected via RS232C cable, the zmodem command is used. Before starting communi cation, prepare the com m unication program on the console for receiving.
5. Collecting Failure Information 149 (1) T ransferring maintenance information to the remote operation termin al or remote host Figure 5-8: Transferring Maintenance Informa tion Files to the Remote Operation T erminal or Remote Host [IP8800/S6700] [IP8800/S6600] [IP8800/S6300] > show tech-support ftp <---1 Specify Host Name of FTP Server.
5. Collecting Failure Information 150 ........... ......................................... ................................ ...... ...................
5. Collecting Failure Information 151 Figure 5-10: Collecting Dump Files from th e Remote T erminal client-host> ftp 192.168.0.60 <---1 Connected to 192.168.0.60. 220 192.168.0.60 FTP server (NetBSD-ft pd) ready. Name (192.168.0.60:staff1): staff1 331 Password required for staff1.
5. Collecting Failure Information 152 5.3 W riting to MC The failure and maintenance information can be written to MC. Note that MC is subject to the capacity limi t. 5.3.1 Writing Fil e to MC Using Operation T erminal When writing t he system informati on to MC, use the operation terminal.
153 6 Line T est 6.1 T esting Line.
6. Line T est 154 6.1 T esting Line 6.1.1 Ethernet Port In line tests, the loopback points of frame s or data sent for the test dif fers depending on the type of test specified.
6. Line T e st 155 > no test interfaces gigabitethernet 1/ 1 [Enter] > activate gigabitethernet 1/1 [Enter] IP8800/S3600 and IP8800/S2 400 A case of test conducted on Port 1 of NIF 0 at a transmi ssion interval of on e second is shown as a test example.
6. Line T est 156 Figure 6-3: Execution Result Example of the test interfaces command and the no test interfaces command [IP8800/S3600] [IP8800/S2400] > inactivate gigabitethernet 0/1 > test int.
6. Line T e st 157 > no test interfaces gigabitethernet 0/ 1 [Enter] (Remove the loop connector from the corres ponding port and restore the connection.) > activate gigabitethernet 0/1 [Enter] Check the test execution result i n the same way for the test execution result of " (1)Checking frame loopback within system .
.
159 7 Rest arting the System This chapter describes the procedures for restarting the system. 7.1 Rest arting the Syste m.
7. Restarting the System 160 7.1 Restarting the System 7.1.1 Restarting the System The system can be restarted by using the re load command. Log is stored at restart time. For input format and parameter of the command, see the manual "Operation Commands.
7. Restarting the System 161 As CPU memory dump is collected in S tep 2, no parameter is selected as shown in figure above. St e p 3 At last, select which system is restar ted or stopped. Figure 7-3: Selecting the System to Be Restarted or S topped As the standby system is rest arted in Step 3, select "standby" as show n in figure above.
7. Restarting the System 162 Figure 7-4: Dump Collection Confirmation Message IP8800/S3600 and IP8800/S240 0 The following is an example showing how to select the p arameter of the reload command when re starting the system and collecting the C PU memory dump according to the confi rmation message.
7. Restarting the System 163 Next, select whether to collect the dump. Figure 7-6: Selecti ng CPU Memo ry Dump T ype As memory dump is collected in Step 2, no parameter is sele cted as shown in figure above. Combining parameters sele cted in Step 1 and S tep 2 resu lts in "reload .
7. Restarting the System 164 Figure 7-7: CPU Memory Dump Collection Confirmati on Message 1. Collect memory dump? Memorydump is already collected 3. Restart? 2. Delete existing memory dump? Restarting without collecting memory dump Restarting after overwriting memory dump 2.
165 Appendix Appendix A Contents of show tech-support Command Display.
Appendix A Contents of show tech-support Command Display 166 Appendix A Contents of show tech-support Command Display Appnedix A.1 Contents of show tech-support Co mmand Display The contents of the show tech-support command displayed for each protocol parameter are shown in the table below .
Appendix A Contents of show tech-support Command Display 167 18 show netstat all-protocol-address numeric Layer 4 related statistical information Y Y Y Y 19 show netstat statistics Layer 3 related sta.
Appendix A Contents of show tech-support Command Display 168 49 cat /standby/var/log/ fixsb.log Kernel internal trace informat ion (for V e r .10.5 and later) YY Y Y 50 cat /usr/var/pplog/ ppupdate.log Log informatio n on updating software (for V er .
Appendix A Contents of show tech-support Command Display 169 77 show lldp detail LLDP function neighb oring system information YY Y Y 78 show oadp detail OADP function neighboring system information YY Y Y 79 show loop-detection Information on L2 loo p detection (for V er .
Appendix A Contents of show tech-support Command Display 170 103 show mld-snooping MLD snooping Information N N N Y 104 show mld-snooping group MLD snooping group informatio n N N N Y 105 show mld-sno.
Appendix A Contents of show tech-support Command Display 171 11 9 show ipv6 mld group Information on group managed by MLD NN Y N 120 show ipv6 pim interface (detail) Information on in terface with IPv.
Appendix A Contents of show tech-support Command Display 172 141 show ip rip statistics RIP statistical information RIP statistical information on each VRF (for V er.1 1.0 and later) NY N N 142 show ip rip advertised-routes summary Number of routes advertised by RIP Number of routes advertised by R IP on each VRF (for V er .
Appendix A Contents of show tech-support Command Display 173 155 show graceful-restart unicast Operation state of th e restart router for graceful restart in the unicast routing protocol (for V er .
Appendix A Contents of show tech-support Command Display 174 (Legend) Y : Displayed, N: Hidden Note: Parenthesis in the column of Command (Display) indicates display depending on the software version. (2) IP8800/S3600 The display contents for IP8800/S3 600 are shown in the table below .
Appendix A Contents of show tech-support Command Display 175 9 /sbin/dmesg Event informatio n in kernel Y Y Y Y 10 cat /var/run/dmesg.boot Event information in kernel (for V er .
Appendix A Contents of show tech-support Command Display 176 41 cat /usr/var/pplog/ ppupdate.log Log informatio n during software update (for V er .11.1 and later) YY Y Y 42 cat /usr/var/pplog/ ppupdate2.log Log informatio n during software update (for V er .
Appendix A Contents of show tech-support Command Display 177 69 show loop-detection Information on L2 Loop detection function (fo r V er .1 0.7 and later) NN N Y 70 show loop-detection statistics Statistics informa tion on L2 Loop detection functio n (for V er .
Appendix A Contents of show tech-support Command Display 178 96 show netstat multicast numeric Kernel internal route related information (multicast) NN Y N 97 show ip multicast statistics Statistics information on IPv4 multicast (for V er .10.5 and later) NN Y N 98 show ipv6 multicast statistics Statistics information on IPv6 multicast (for V er .
Appendix A Contents of show tech-support Command Display 179 124 show ip dhcp server statistics DHCP server statistical information N Y N N 125 show ip dhcp conflict DHCP Server Conflicted IP address .
Appendix A Contents of show tech-support Command Display 180 147 show ipv6 ospf discard-packets Packet information discarded by OSPFv3 NY N N 148 show ipv6 ospf statistics Statistical inform ation of .
Appendix A Contents of show tech-support Command Display 181 (Legend) Y : Displayed, N: Hidden Note: Parenthesis in the column of Comma nd (Display) ind icates display depending on the software ver sion. (3) IP8800/S2400 The display contents for IP8800/S2400 are shown in the table below .
Appendix A Contents of show tech-support Command Display 182 19 ls -lTiR /dump0 Dump file in fo rmation Y Y Y Y 20 ls -lTiR /usr/var/hardware Hardware dump file information (for V er.
Appendix A Contents of show tech-support Command Display 183 49 cat /var/tmp/gen/trace/ mng_sub.trc Configuration command trace information 3 (f or V er .10.7 and later) YY Y Y 50 tail -n 400 /var/tmp/gen/ trace/api.trc Configuration command trace information 4 (f or V er .
Appendix A Contents of show tech-support Command Display 184 76 show qos queueing All queue statistical information for earlier than Ve r . 1 0 . 6 NY Y Y for V er .
Appendix A Contents of show tech-support Command Display 185 (Legend) Y : Displayed, N: Hidden Note: Parenthesis in the column of Comma nd (Display) ind icates display depending on the software ver sion.
.
187 Index Symbols "MC not found" is displayed when MC is accessed 22 "MC:--------" is displayed by en tering the show system command or the show mc command 22 A Action to Be T aken.
Index 188 L Layer 2 Authentication Communication Failure 89 Layer 2 Communication by VLAN Is Disabled 38 Layer 2 Network Communication Failur e 38 Login Authentication Usi ng RADIUS/T ACACS+ Is Disabl.
デバイスNEC IP8800/S2400の購入後に（又は購入する前であっても）重要なポイントは、説明書をよく読むことです。その単純な理由はいくつかあります：
NEC IP8800/S2400をまだ購入していないなら、この製品の基本情報を理解する良い機会です。まずは上にある説明書の最初のページをご覧ください。そこにはNEC IP8800/S2400の技術情報の概要が記載されているはずです。デバイスがあなたのニーズを満たすかどうかは、ここで確認しましょう。NEC IP8800/S2400の取扱説明書の次のページをよく読むことにより、製品の全機能やその取り扱いに関する情報を知ることができます。NEC IP8800/S2400で得られた情報は、きっとあなたの購入の決断を手助けしてくれることでしょう。
NEC IP8800/S2400を既にお持ちだが、まだ読んでいない場合は、上記の理由によりそれを行うべきです。そうすることにより機能を適切に使用しているか、又はNEC IP8800/S2400の不適切な取り扱いによりその寿命を短くする危険を犯していないかどうかを知ることができます。
ですが、ユーザガイドが果たす重要な役割の一つは、NEC IP8800/S2400に関する問題の解決を支援することです。そこにはほとんどの場合、トラブルシューティング、すなわちNEC IP8800/S2400デバイスで最もよく起こりうる故障・不良とそれらの対処法についてのアドバイスを見つけることができるはずです。たとえ問題を解決できなかった場合でも、説明書にはカスタマー・サービスセンター又は最寄りのサービスセンターへの問い合わせ先等、次の対処法についての指示があるはずです。
