Avaya Troubleshooting Routers Průvodce řešením problémů

Troubleshooting Routers Router Software Version 10.0Site Manager Software Version 4.0Part No. 112937 Rev. AJanuary 1996

xUsing TFTP to Transfer the File ... B-31Using XMODEM to Transfer the File

Troubleshooting Routers5-22• You configured the DTE/DCE (Data Terminal Equipment/Data Communication Equipment) with promiscuous mode turned on.The remo

Troubleshooting a Data Link Connection Problem5-23Troubleshooting the Internal Clock Settings (Lab Environments Only)If you are using crossover cables

Troubleshooting Routers5-24Troubleshooting a Token Ring ConnectionThis section assumes that you have isolated a problem to a Token Ring connection. If

Troubleshooting a Data Link Connection Problem5-252. If you are using the Technician Interface, enter the following command to list the instances of t

Troubleshooting Routers5-26Troubleshooting Other Data Link ProtocolsThis section assumes that you have isolated a problem to a data link connection. I

Troubleshooting a Data Link Connection Problem5-275. Verify the configuration parameters.6. Use Packet Capture and a network analyzer to check the segm

6-1Chapter 6Troubleshooting a Network Connection ProblemThis chapter describes how to solve network layer problems. It assumes you have already determ

Troubleshooting Routers6-2Troubleshooting AppleTalkThis section assumes that you have isolated a problem to AppleTalk. If not, refer to Chapter 2 to d

Troubleshooting a Network Connection Problem6-35. Verify the configuration parameters.6. Use Packet Capture and a network analyzer to check the segment

xi Figures Figure 1-1. Filtering Parameters Window ...1-6Figure 3-1. Verifying the Sl

Troubleshooting Routers6-4Static Configuration Conflict Event MessageThe node number associated with the interface is already in use by another node on

Troubleshooting a Network Connection Problem6-54. Use the Technician Interface or the Statistics Manager to inspect the global DLSw settings, such as

Troubleshooting Routers6-6Troubleshooting IPThis section assumes that you have isolated a problem to IP. If not, refer to Chapter 2 to determine wheth

Troubleshooting a Network Connection Problem6-7wfIpBase.wfIpBaseZeroSubnetEnable.0 = 2wfIpBase.wfIpBaseEstimatedNetworks.0 = 0wfIpBase.wfIpBaseHosts.0

Troubleshooting Routers6-8Troubleshooting Telnet, FTP, and TFTPThe message Unknown Network or Network Unreachable indicates that the device does not h

Troubleshooting a Network Connection Problem6-95. Make sure that the ICMP echo outs statistic is increasing for the IP interface.6. Use the ping -p co

Troubleshooting Routers6-10Router Cannot Ping Another Local DeviceWhen the router cannot ping another device on the network, it does not necessarily m

Troubleshooting a Network Connection Problem6-11Router Cannot Ping Endstation, but Can Ping Other Endstations on the Same SegmentIf the router can pin

Troubleshooting Routers6-12Host Did Not Respond MessageIf the endstation or router displays this message, do the following: 1. Make sure that the ends

Troubleshooting a Network Connection Problem6-131. Compare the endstation’s interface number, network number, and subnet mask to those of the router’s

Troubleshooting Routers6-14If the attempts to ping fail, verify that you configured the router with the correct IP network, interface, and subnet addre

Troubleshooting a Network Connection Problem6-15Troubleshooting Open Shortest Path First (OSPF)Do the following to troubleshoot an OSPF routing proble

Troubleshooting Routers6-165.Enter the following command to display the IP forwarding table:get wfIpBaseRtEntry.7.*The Technician Interface displays t

Troubleshooting a Network Connection Problem6-172. Make sure that the IPX routing software is up. To do this, use the Statistics Manager Quick Get Fac

Troubleshooting Routers6-18Example$show ipx circuitIPX Circuit Configuration Information (ALL)-------------------------------------------Circuit Sta

Troubleshooting a Network Connection Problem6-19ExampleIPX RIP Interface Record Configuration Information (All)---------------------------------------

Troubleshooting Routers6-20Example$show ipx route find 0x00000986IPX Routing Table Information-----------------------------Destination NextHop Net Ne

Troubleshooting a Network Connection Problem6-21Troubleshooting OSIThis section assumes that you have isolated a problem to OSI. If not, refer to Chap

Troubleshooting Routers6-22This command allows you to display OSI database information about an individual slot in the router. The display includes in

Troubleshooting a Network Connection Problem6-23The alias definition isosiadjs = echo “Dynamic Adjacencies”; get wfOsiDynAdjEntry.95. To display the pa

xiii Tables Table 1-1. Technician Interface Event Message Filters ...1-7Table 1-2. Example of an Imaginary

Troubleshooting Routers6-24For a successful connection, the control protocol on both sides of the configured demand circuits comes up, and the associat

Troubleshooting a Network Connection Problem6-25Refer to one of the following sections, if it applies to the problem:•“Master Cannot Connect to Slave”

Troubleshooting Routers6-262.If the router’s connection to the modem is a 44-pin synchronous interface, and the modem is a master, make sure the modem

Troubleshooting a Network Connection Problem6-27If it is, configure the DCE for DSR to follow CD, or configure DSR to be in the off state until the DCE

Troubleshooting Routers6-28ExampleIf you are filtering events from Slots 3 and 4, you enterlog -fftwid -eISDN -eISDN_BRI -eSWSERV -s3 -s43.Refer to the

Troubleshooting a Network Connection Problem6-294. Look at the attribute values of the following MIB objects:• wfIsdnSwitchCfgEntry• wfPppCircuitEntry

Troubleshooting Routers6-30Troubleshooting Other Networking ProtocolsThis section assumes that you have isolated a problem to a network protocol. If n

Troubleshooting a Network Connection Problem6-313. Check the values of the following statistics twice and compare them to determine whether the protoc

7-1Chapter 7Troubleshooting a Site Manager ProblemThis chapter describes how to solve Site Manager problems. It includes the following sections:•“Site

Troubleshooting Routers7-2Cannot Find File MessageIf a message like the one in Figure 7-1 states that the application cannot find the WFSM.EXE or WINSO

Troubleshooting a Site Manager Problem7-33. Make sure that the environment variable PATH contains only the path to the protocol stack that you want Si

Troubleshooting Routers7-44.Verify that you updated the /etc/services file correctly, as follows:• If the workstation running Site Manager is accessing

Troubleshooting a Site Manager Problem7-5Cannot Establish a Site Manager Session with the RouterIf the connection to the router fails to establish, do

Troubleshooting Routers7-6Using the Technician Interface to Enable AccessEnable SNMP access as follows:1. Enter the following Technician Interface com

Troubleshooting a Site Manager Problem7-7b. Try to use Distinct or Chameleon to ping other stations on the LAN. c. Try to ping the router port from ot

Troubleshooting Routers7-8If the ping attempts fail, but the number of transmitted requests increments, the workstation has a path to the requested ad

Troubleshooting a Site Manager Problem7-9Cannot Allocate Colormap MessageThe Site Manager cannot allocate any colors for its display because another p

8-1Chapter 8Getting HelpThis chapter includes the following sections:•“Reporting a Problem to the Bay Networks Technical Response Center”•“Sending and

xv About This Guide If you are responsible for isolating and solving problems associated with Bay Networks routers, read this guide. Audience This gu

Troubleshooting Routers8-28.What, if anything, has changed in the router and/or network?9. Can you reproduce the problem, and if so, how?10. How is th

Getting Help8-3• Fax copies to the Bay Networks Technical Response Center at: (508)-670-8765Use the Bay Networks anonymous FTP file server as follows:1

A-1Appendix AReading the Event LogThis appendix provides examples and explanations of the descriptive text in event messages, including debug messages

Troubleshooting RoutersA-2System StartupThe following sample message is from a log of a Series 7 router after we restarted it by entering the boot 2:-

Reading the Event LogA-3Each slot transmits BOFL requests via the backplane to the other slots in the router in order to determine which slots are act

Troubleshooting RoutersA-4The router is loading the router software image.@ 41: mm/dd/yy 11:48:22.269 DEBUG # 2 BOOT ( 13) Image loaded, ju

Reading the Event LogA-5The software interface to the kernel provides for the transmission of both unreliable and reliable messages. The two types of

Troubleshooting RoutersA-6@ 84: mm/dd/yy 11:48:35.662 DEBUG # 2 LOADER ( 2) Loader starting service gate 0x04016 @ 0x30039a2e (env=0x0000000

Reading the Event LogA-7@ 112: mm/dd/yy 11:48:36.502 DEBUG # 2 LOADER ( 2) Loader starting service gate 0x00074 @ 0x300a17b2 (env=0x00000000,

Troubleshooting Routersxvi Bay Networks Customer Support Bay Networks provides live telephone technical support to our distributors, resellers, and

Troubleshooting RoutersA-8DECnet successfully loaded onto Slot 2 and is initializing.@ 135: mm/dd/yy 11:48:38.631 DEBUG # 2 LOADER ( 30) Image

Reading the Event LogA-9@ 152: mm/dd/yy 11:48:39.564 INFO # 2 IPX ( 42) IPX ADD Nwif cct 1 Network 00.00.00.aa@ 153: mm/dd/yy 11:48:39.5

Troubleshooting RoutersA-10Slot 3 is booting revision 9.00 of bn.exe.@ 176: mm/dd/yy 11:48:41.007 INFO # 3 GAME ( 11) Starting image rel/9.

Reading the Event LogA-11Data Path always registers Ethernet and SNAP frames for IP. In this example, Data Path registers ISAPs on Circuit 1 for the f

Troubleshooting RoutersA-12@ 238: mm/dd/yy 11:48:49.932 DEBUG # 3 MIB ( 13) Received configuration from remote slot 0xa0000011@ 239: mm/dd

Reading the Event LogA-13@ 277: mm/dd/yy 11:48:51.279 DEBUG # 2 LOADER ( 32) Loader serving request for tftp.exe from 0x1000602c@ 278: mm/dd/

Troubleshooting RoutersA-14@ 310: mm/dd/yy 11:48:52.564 DEBUG # 3 LOADER ( 30) Image hdlc.exe loaded successfully from 2:bn.exe@ 311: mm/dd/y

Reading the Event LogA-15@ 345: mm/dd/yy 11:50:29.741 INFO # 2 MIB ( 9) wfNode.2.0 set to 0x51e3200000000000@ 346: mm/dd/yy 11:50:45.59

Troubleshooting RoutersA-16@ 364: mm/dd/yy 11:50:47.569 INFO # 3 TELNET ( 4) Connection Manager initializing.@ 365: mm/dd/yy 11:50:47.598

Reading the Event LogA-17@ 403: mm/dd/yy 11:52:07.684 DEBUG # 2 NVFS ( 63) NVFS manager is opening file 'log.sav' for writing

About This Guidexvii • In Germany, call 0130-37-32. • In Europe (except for the United Kingdom and Germany), call (44) 272-760681.• Outside the U.S.,

Troubleshooting RoutersA-18Dial-on-Demand Raise DTR LogThe following log shows a successful dial-on-demand connection between the COM2 port in Slot 2

Reading the Event LogA-19The following messages appear even if you did not connect a modem to the router. Unlike V.25bis, Raise DTR does not look for

Troubleshooting RoutersA-20The PPP link over the dial-on-demand circuit establishes an LCP (Link Control Protocol) connection. The messages beginning

Reading the Event LogA-21# 70: mm/dd/yy 14:15:35.136 DEBUG SLOT 2 SWSERV Code: 46Connector COM2: FSM State: RDTR_WAIT_FOR_ULI(3)Connector

Troubleshooting RoutersA-22intf gate spawned - line 202102The router returns to a “wait_state,” a state in which it is waiting for data.# 81: mm/dd

Reading the Event LogA-23# 12: mm/dd/yy 13:07:25.002 DEBUG SLOT 2 PCAP Code: 65wait_state - line 202101The FSM (finite state machine) messa

Troubleshooting RoutersA-24The router pings the remote side of the dial-on-demand link to provide data to transmit across the link, and displays a “da

Reading the Event LogA-25# 32: mm/dd/yy 13:10:18.784 TRACE SLOT 2 MODEMIF Code: 35Connector COM1: Sent CRN cmd to T3053# 65: mm/dd/yy 1

Troubleshooting RoutersA-26Sending LCP Configure-Request on circuit 2.# 76: mm/dd/yy 13:13:23.806 TRACE SLOT 2 PPP Code: 55Received LCP C

Reading the Event LogA-27# 89: mm/dd/yy 13:13:26.228 DEBUG SLOT 2 SWSERV Code: 46Connector COM1: FSM Event: V25BIS_EVENT_ULI_IND(15); isd

Troubleshooting Routersxviii Conventions This section describes the conventions used in this guide.angle brackets (< >) Indicate that you choos

Troubleshooting RoutersA-28# 104: mm/dd/yy 13:13:53.406 DEBUG SLOT 2 MODEMIF Code: 9Connector COM1: modem present V.25bis mode# 105: mm

Reading the Event LogA-29Connector COM1, Logical Line 1 LLC service withdrawn.# 6: mm/dd/yy 10:31:33.105 WARNING SLOT 5 DS1E1 Code: 4Conn

Troubleshooting RoutersA-30 Hardware map address - 3072f784 Initialization block - 80006c00 Receive descriptor ring - 80002600 Transmit d

Reading the Event LogA-31Connector COM1, Logical Line 1 time_slot = 23.Connector COM1, Logical Line 1 time_slot = 24.Connector COM1, Logical Line 1 in

Troubleshooting RoutersA-32Connector COM2, Logical Line 1 LLC service withdrawn.# 5: mm/dd/yy 10:43:14.238 INFO SLOT 4 DS1E1 Code: 27Co

Reading the Event LogA-33The same unscheduled message shown in Line 8 earlier applies to FDL Line Loop IA and IB.If you click on FDL Disable ALL, the

Troubleshooting RoutersA-34Connector COM1, Logical Line 1 time_slot = 3.Connector COM1, Logical Line 1 time_slot = 4.Connector COM1, Logical Line 1 ti

Reading the Event LogA-35The following command displays the new port status:[3:1]$ show ds1e1 portDS1E1 Port Status:------------------ 2 entries in ta

Troubleshooting RoutersA-362 entries in table.If you configure the primary clock source as the Port 2 loop and the secondary clock source as the Port 1

B-1Appendix BUsing the Technician Interface to Configure andRun Packet CaptureThis appendix include the following sections:•“Overview”•“Implementation

About This Guidexix Ordering Bay Networks Publications To purchase additional copies of this document or other Bay Networks publications, order by pa

Troubleshooting RoutersB-2You can use Packet Capture to do the following:• Copy all incoming packets, outgoing packets, or both.• Filter and copy inco

Using the Technician Interface to Configure and Run Packet CaptureB-3The decoded format identifies each field in the packet and, where appropriate, disp

Troubleshooting RoutersB-4Implementation NotesPacket Capture copies packets received or transmitted as error-free. It does not copy packets containing

Using the Technician Interface to Configure and Run Packet CaptureB-5Assigning the Processors to Run Packet CaptureTo assign processors to run Packet

Troubleshooting RoutersB-6If you want to copy packets from more than one circuit, and the circuits are on different I/O modules, add the hexadecimal v

Using the Technician Interface to Configure and Run Packet CaptureB-7Get the number of the logical line from which you want to copy packets as follows

Troubleshooting RoutersB-8The second 1 represents the numeric code for “create.”ExampleEnter the following command to create an instance for Logical L

Using the Technician Interface to Configure and Run Packet CaptureB-9• HSSIget wfHssiEntry.60.<slot>.<connector>60 represents the wfHssiLi

Troubleshooting RoutersB-10Allocating Memory for the Packet Capture FileYou must allocate memory to store the Packet Capture file in order to capture p

Using the Technician Interface to Configure and Run Packet CaptureB-11Specifying the Number of Bytes in Each Packet to CopyYou must specify the number

4401 Great America Parkway 8 Federal StreetSanta Clara, CA 95054 Billerica, MA 01821 Copyright © 1988–1996 Bay Networks, Inc. All rights reserved. Pr

Troubleshooting Routersxx CID channel identifierCN Concentrator NodeCRC cyclic redundancy checkCRN call request numberCSMA/CD Carrier Sense Multiple A

Troubleshooting RoutersB-12Starting Packet CaptureEnter the following Technician Interface command to start Packet Capture:set wfPktCaptureEntry.5.<

Using the Technician Interface to Configure and Run Packet CaptureB-13Using the Technician Interface to Display a Packet Capture FileEnter the followi

Troubleshooting RoutersB-14Example 1Enter the following command to display all packets associated with Line Number 102101:pktdump 102101Pkt# 1 mm/dd

Using the Technician Interface to Configure and Run Packet CaptureB-15Pkt# 3 mm/dd/yy 10:20:28.462 CSMACD 60 Rx00000000: 00 00 a2 00 93 c5 00 00 a2

Troubleshooting RoutersB-16Deleting a Packet Capture InstanceYou may want to delete all MIB information about a Packet Capture instance if you no long

Using the Technician Interface to Configure and Run Packet CaptureB-17Enter the following command to change the direction of the packets that Packet C

Troubleshooting RoutersB-18If you want Packet Capture to terminate itself and• You configured Packet Capture to copy incoming packets, enterset wfPktCa

Using the Technician Interface to Configure and Run Packet CaptureB-19ExampleEnter the following command if you configured the Packet Capture instance

Troubleshooting RoutersB-20Refer to the following sections to set the parameters for each filter. Setting the Filter Response to a MatchEnter the follo

Using the Technician Interface to Configure and Run Packet CaptureB-21Specifying the String to Compare with the Packet DataEnter the following Technic

About This Guidexxi GFWD GAME forwardGH Gate HandleGRPC GAME RPCHSSI High Speed Serial InterfaceICMP Internet Control Message ProtocolIEEE Institute

Troubleshooting RoutersB-22Specifying the ReferenceEnter the following Technician Interface command to specify the reference, which is the field in the

Using the Technician Interface to Configure and Run Packet CaptureB-23Specifying the OffsetEnter the following Technician Interface command to specify

Troubleshooting RoutersB-24• 22 for Transmit Filter 122 represents the wfPktCaptureTxFltr1Size attribute.•33 for Transmit Filter 233 represents the wf

Using the Technician Interface to Configure and Run Packet CaptureB-25<value> is• 1 if you want Packet Capture to copy a packet if it matches ei

Troubleshooting RoutersB-26Example 2This example starts and stops Packet Capture. The instructions are as follows:1. Start Packet Capture:set wfPktCap

Using the Technician Interface to Configure and Run Packet CaptureB-273. Specify the number of bytes after the Reference with which to begin the compa

Troubleshooting RoutersB-285.Specify the string as the hexadecimal number ffffffffffff:set wfPktCaptureEntry.28.102101 0xffffffffffff28 represents the

Using the Technician Interface to Configure and Run Packet CaptureB-29wfPktCaptureEntry.wfPktCaptureTxFltr1Offset.102101 = 0wfPktCaptureEntry.wfPktCap

Troubleshooting RoutersB-30Getting the Name of the Packet Capture FileTo get a Packet Capture file stored in the router’s memory, you must know its nam

Using the Technician Interface to Configure and Run Packet CaptureB-312. Issue the following command to establish an FTP connection with the router.op

Troubleshooting Routersxxii PDU protocol data unitPPP Point-to-Point ProtocolPROM programmable, read-only memory chipPTP point-to-point (Standard Pro

Troubleshooting RoutersB-322.Issue the following command to establish a TFTP connection with the router.connect <IP_address><IP_address> i

Using the Technician Interface to Configure and Run Packet CaptureB-33Displaying the FileYou can use the Packet Dump utility to display a Packet Captu

Troubleshooting RoutersB-34These utilities are also available in the /perm/pkt_convert directory on the Bay Networks FTP file server. Refer to Chapter

Using the Technician Interface to Configure and Run Packet CaptureB-35Packet Convert creates a Sniffer file named PCAP0300.TRC.• For a SYNC Packet Capt

Troubleshooting RoutersB-36Examplelist wfPktCaptureEntrywfPktCaptureDelete = 1wfPktCaptureDisable = 2wfPktCaptureState = 3wfPktCaptureFname = 4wfPktCa

Using the Technician Interface to Configure and Run Packet CaptureB-37Packet Capture Parameter DescriptionsThe following sections describe each parame

Troubleshooting RoutersB-38 Parameter: Delete Attribute Name: wfPktCaptureDelete Attribute Number: 1 Default: 1 (Create) Options: 1 (Create) | 2 (Dele

Using the Technician Interface to Configure and Run Packet CaptureB-39 Parameter: State Attribute Name: wfPktCaptureState Attribute Number: 3 Default:

Troubleshooting RoutersB-40 Parameter: Control Attribute Name: wfPktCaptureControl Attribute Number: 5 Default: 2 (Stop) Options: 1 (Start) | 2 (Stop

Using the Technician Interface to Configure and Run Packet CaptureB-41 Parameter: Buffer Size Attribute Name: wfPktCaptureBufSize Attribute Number: 8

About This Guidexxiii TTL time to liveULI upper layer indicationVC virtual circuitVCI virtual channel identifierVCL virtual channel linkVME Versa Modu

Troubleshooting RoutersB-42 Parameter: Direction Attribute Name: wfPktCaptureDirection Attribute Number: 10 Default: 1 (Receive) Options: 1 (Receive)

Using the Technician Interface to Configure and Run Packet CaptureB-43 Parameters: TriggerPacket Capture supports two trigger parameters. The MIB info

Troubleshooting RoutersB-44• 3 to terminate when data matches the Filter 2 Match parameter setting.If you set the Packet Capture Receive Trigger to 2

Using the Technician Interface to Configure and Run Packet CaptureB-45 Instructions: Set to 1 (capture) if you want Packet Capture to copy only the pa

Troubleshooting RoutersB-46 Parameters: ReferencePacket Capture supports four Reference parameters. The MIB information is as follows: Default: 1 Opti

Using the Technician Interface to Configure and Run Packet CaptureB-47 Parameters: SizePacket Capture supports four Size parameters. The MIB informati

Troubleshooting RoutersB-48 Instructions: Enter any hexadecimal number or character string up to 16 characters. Parameters: GroupPacket Capture suppor

Using the Technician Interface to Configure and Run Packet CaptureB-49An example of a hexadecimal display of a CSMA/CD frame follows.Pkt# 10 mm/dd/yy

Troubleshooting RoutersB-50ATMThe ATM protocol currently does not have a special data link filter offset. If you configure a data link filter, set the of

Using the Technician Interface to Configure and Run Packet CaptureB-51Frame Relay Switch and SMDS SwitchThe Frame Relay Switch and SMDS Switch work th

Troubleshooting RoutersB-52PTP (STANDARD)The PTP, or Standard, protocol has a data link filter offset of 16 bytes from the beginning of the packet. The

Using the Technician Interface to Configure and Run Packet CaptureB-5300000020: 00 00 00 00 00 00 00 00 aa aa 03 00 80 c2 00 0e00000030: 00 00 00 00 0

Troubleshooting RoutersB-54FDDIThe FDDI physical media has a data link filter offset of 13 bytes. This places the data link filter point at the DSAP byt

Using the Technician Interface to Configure and Run Packet CaptureB-55An example of a hexadecimal display of an ISDN frame follows:Pkt# 1 11/02/94 16:

Troubleshooting RoutersB-56ExampleThe code for a single CSMA/CD interface on Slot 2 using XCVR1 is 0000102101. Site Manager removes the leading zeros,

Index-1Symbols* in get command, 1-17AACE32 memory limitations, 3-13adding VC gate w/GH event message, 5-5address format, synchronous, 5-21adjacency co

Index-2bootfailure, 3-3image. See router software imagePROMs, 3-6bouncing MAC addresses, 6-11bridge ID, 6-4buffersallocating for Packet Capture, B-10p

Index-3delete attribute, 6-30diags command, 3-20dial-on-demand raise DTR event messages, A-18 to A-22dial-on-demand V.25bis event messages, A-22 to A-

Index-4GGAME (Gate Access Management Entity), 1-9gates, 1-9get command, 1-16, 1-17get command, 8-3getting helpfrom a Bay Networks Technical Response C

Index-5LBO (line build out), 5-17LEDsASN, 3-4failure to light, 3-3power supplies, 3-2red fail, 4-4line coding, 5-17line number, B-6, B-7, B-40, B-55li

1-1 Chapter 1Introduction This chapter includes the following sections:•“Preventing Problems”•“Preparing to Troubleshoot”•“Documenting Each Step”•“Pe

Index-6MTU (maximum transfer unit) maximum exceeded, 5-3multimode fiber, orange, 4-5munich.exe file, 5-18Nnetstat -r command, 6-8Network General Sniffer

Index-7SDLC, B-52SMDS, B-52starting, B-12terminating, B-12Token Ring, B-53trigger, B-17X.25, B-53PAP (Password Authentication Protocol), 6-29parameter

Index-8routing tables, 1-22the log, 1-5scope of a problem, determining, 2-1 to 2-3Screen Builder tool, 1-20Screen Manager tool, 1-20script commands, 1

Index-9transmission queue (Tx) space shortage, 5-9transmission statistics not changing, 5-26, 6-31trigger, B-17, B-42UUDP port numbers for SNMP, 7-3un

Index-10wfPktCapture<Rx | Tx>Fltr<no.>Ref, B-22, B-46wfPktCapture<Rx | Tx>Fltr<no.>Size, B-23, B-47wfPktCapture<Rx | Tx>

Troubleshooting Routers1-2 Reading the Release Notes and Relevant Documentation The release notes and the manuals that describe how to configure and m

Introduction1-3 If you use the Configuration Manager in dynamic mode to make changes, select File ➔ Save or File ➔ Save As to copy the configuration fr

Troubleshooting Routers1-4 Responding to a Failed prom Command If you reboot after the prom command fails, a Bay Networks representative must reinser

Introduction1-5 You can use the Technician Interface log command to display the log in the router’s memory or the Events Manager tool’s File ➔ Get

Bay Networks, Inc. 4401 Great America Parkway, Santa Clara, CA 950548 Federal Street, Billerica, MA 01821 Bay Networks Software License This Software

Troubleshooting Routers1-6• The processor board loses power because you removed it, a fuse blew, or the router lost power.Filtering Event MessagesYou

Introduction1-7The Technician Interface log command supports optional arguments you can use to filter the display of event messages (see Table 1-1).Ref

Troubleshooting Routers1-8You can use the Technician Interface or Events Manager to combine the filters. For example, you enter the following command t

Introduction1-9The name of the router’s operating system is GAME (Gate Access Management Entity). In addition to assuming the typical responsibilities

Troubleshooting Routers1-10Using the Technician Interface to Access the MIBThe Technician Interface is an out-of-band router management and troublesho

Introduction1-11Town = 5Street = 6HouseNo = 7Bedrooms = 8Bathrooms = 9TotalSquareFeet = 10HowMuchILikeIt = 11You set up attributes to describe cars—at

Troubleshooting Routers1-12Suppose you create a lot of diverse objects and you want to organize them. You can create an object to organize and provide

Introduction1-13object named Things, and assign the object identifier 1 to Things. If you created this hierarchy of objects, you could specify a color

Troubleshooting Routers1-14You can view all the attribute names and numeric identifiers of an object by entering the Technician Interface list <obje

Introduction1-15You can view all the instances of an object configured on the router by entering the Technician Interface list instances <object>

Bay Networks, Inc. 4401 Great America Parkway, Santa Clara, CA 950548 Federal Street, Billerica, MA 01821 Bay Networks Software License (continued)

Troubleshooting Routers1-16ExampleThis example shows the instances of the object wfIpInterfaceEntry. The instance format differs from that of the obje

Introduction1-17Remember to save the changes to a file on the router’s memory card or floppy disk before rebooting. You can do this with the Configuratio

Troubleshooting Routers1-18You can also insert an asterisk in place of the instance in a get command to display all of the values of a single attribut

Introduction1-19Using the Technician Interface Scripts to Access the MIBThe script files are simple programs consisting of one or more SNMP get command

Troubleshooting Routers1-20If you click an attribute and click Retrieve, the Site Manager retrieves and displays all of the values of that attribute.

Introduction1-21If the ping command yields the response “Target does not respond,” the station you issued the ping from believes it knows how to get t

Troubleshooting Routers1-22Unlike the Series 5 software, more than one user can establish an inbound or outbound Telnet session with a router at the s

Introduction1-23To learn more about the Technician Interface recording feature, enterhelp recordYou can use the Statistics Manager to save tables to fi

Troubleshooting Routers1-24— You can refer to it in order to tell whether, after implementing a test solution, you repeated important diagnostic steps

2-1Chapter 2Determining the Scope of a ProblemThis chapter poses the initial questions you should answer to narrow the cause of a problem to such topi

v Contents Troubleshooting Routers About This Guide Audience ...

Troubleshooting Routers2-24.Are you using a workaround to prevent the symptoms from occurring? If so, what?Consideration of the workaround you are usi

Determining the Scope of a Problem2-3• A single protocol on multiple ports within all slots running that protocol?If so, the problem is most likely in

3-1Chapter 3Troubleshooting an Operational ProblemThis chapter describes how to solve problems with the basic operation of the hardware and software.

Troubleshooting Routers3-2Damaged RouterIf you detect physical damage to the router, report the problem to the Bay Networks Technical Response Center.

Troubleshooting an Operational Problem3-3LEDs Not LitThe LEDs (light emitting diodes) on a FRE® (Fast Routing Engine), SRM (System Resource Module), o

Troubleshooting Routers3-4For detailed instructions on router software image compatibility, refer to the Upgrading Routers from Version 5 to Version 1

Troubleshooting an Operational Problem3-5a. If the ASN is in a stack, make sure the SPX slot dial on the rear panel of each ASN points to a different

Troubleshooting Routers3-6Checking the Boot PROMsMake sure that the boot PROM images are compatible with the router software image as follows:Check th

Troubleshooting an Operational Problem3-7However, if you specify the router software image and configuration files when booting the router, all processo

viUsing Packet Capture ...1-21Using Inbound Telnet to Access the

Troubleshooting Routers3-8If the slots are operating with router software images from different volumes, do the following:1. Display the directory for

Troubleshooting an Operational Problem3-9Verifying That the Configuration Files in Each Processor MatchTo display the source of the configuration files t

Troubleshooting Routers3-103.Determine which configuration file is the one you want to use. 4. Back up the unwanted configuration file.5. Remove the unwan

Troubleshooting an Operational Problem3-116. Engage the thumb clips of the other FRE processor modules.7. Wait for the modules to reset.8. Enter the T

Troubleshooting Routers3-12In order for the memory card to accommodate a file, the file’s size must be less than or equal to the “contiguous free space.

Troubleshooting an Operational Problem3-13To make sure the applications are loaded on the slot, enter the Technician Interface loadmap <slot_no.>

Troubleshooting Routers3-14The response shows the filename, starting offset (load address), and number of bytes of each dynamically loadable applicatio

Troubleshooting an Operational Problem3-15wfKernelEntry.wfKernelBufOwnerTask3.2 = "31619B04"wfKernelEntry.wfKernelMemOwnerTask1.2 = "30

Troubleshooting Routers3-16Determining which protocol owns a task can help you determine which protocols are using the most memory. To do this, compar

Troubleshooting an Operational Problem3-17Bad Forward Checksum ErrorsAn event message beginning with “buf=” follows the bad forward reception buffer c

viiDropped Frames ...5-4ATM VC . . . Failed Messa

Troubleshooting Routers3-18Go to the appropriate section to determine which slot sent the BOFL packet:•“Finding the Slot That Sent a Bad Backplane-BOF

Troubleshooting an Operational Problem3-19Finding the Slot That Sent a Bad Packet That Was Not a BOFL PacketFind the number of the slot that sent the

Troubleshooting Routers3-20Call the Bay Networks Technical Response Center and describe the situation. Depending on whether the slot sending or receiv

4-1Chapter 4Troubleshooting a Physical Media ProblemThis chapter describes how to solve physical media problems. It assumes you have already determine

Troubleshooting Routers4-2Determining the Media-Specific StateUse the Statistics Manager Quick Get tool or the Technician Interface to check the media-

Troubleshooting a Physical Media Problem4-3Respond to State attribute values as follows:1. If the media-specific state of the interface in question is

Troubleshooting Routers4-44.If the cable and the transceiver are OK, use Packet Capture to test the reception and transmission of data as it passes th

Troubleshooting a Physical Media Problem4-5You can also loop back PPP lines. But if you configured them with a password, you must configure them in prom

5-1Chapter 5Troubleshooting a Data Link Connection ProblemThis chapter describes how to solve data link layer problems. It assumes you have already de

viiiEndstation Can Ping Local and Remote Interfaces on the Router, but Cannot Ping a Remote Station ...

Troubleshooting Routers5-2Troubleshooting an ATM ConnectionThis section assumes that you have isolated a problem to an ATM connection. If not, refer t

Troubleshooting a Data Link Connection Problem5-3The attributes include the number of cells received and transmitted, and the number of frames dropped

Troubleshooting Routers5-4Refer to one of the following sections if it applies to your problem:•“Dropped Frames”•“ATM VC . . . Failed Message”•“Upper-

Troubleshooting a Data Link Connection Problem5-54. Match the error code in the message to the error code column in Table 5-1, and perform the associa

Troubleshooting Routers5-6Troubleshooting an Ethernet ConnectionThis section assumes that you have isolated a problem to an Ethernet connection. If no

Troubleshooting a Data Link Connection Problem5-7• wfCSMACDOctetsRxOkThis shows the number of bytes received without error.• wfCSMACDFramesRxOkThis sh

Troubleshooting Routers5-8• wfCSMACDBablErrorTxThis shows the number of frames transmitted that were larger than 1518 octets. “BablErrorTx” stands for

Troubleshooting a Data Link Connection Problem5-9Check the wfKernelEntry for the slot where the problem is occurring to determine whether free buffers

Troubleshooting Routers5-10• wfCSMACDCerrThis shows the number of Ethernet controller chip collision detections. This is meaningful only if the attach

Troubleshooting a Data Link Connection Problem5-11If the Ethernet controller is not a QENET, you can ignore this attribute. If the Ethernet controller

ix Appendix A Reading the Event Log System Startup ...

Troubleshooting Routers5-12• wfFDDIRingOverrunRx (get wfFddiEntry.21.*)This shows the number of LLC (logical link control) reception ring overrun even

Troubleshooting a Data Link Connection Problem5-13• 4 = wrap BThis state indicates that the A and B ports connect to two different concentrators that

Troubleshooting Routers5-14Troubleshooting a Frame Relay ConnectionThis section assumes that you have isolated a problem to a Frame Relay connection.

Troubleshooting a Data Link Connection Problem5-15Frame Relay Switch Keeps Marking the Circuit as DownTroubleshoot as follows:1. Check the polling int

Troubleshooting Routers5-16PVC Transmitting, but Not ReceivingIf the log reveals that the PVC (permanent virtual circuit) is active, and the statistic

Troubleshooting a Data Link Connection Problem5-17Troubleshooting an MCT1 ConnectionThis section assumes that you have isolated a problem to an MCT1 (

Troubleshooting Routers5-18The Sync LED stays on when the framer is in sync with the carrier’s clock.6. Make sure that you set the LBO appropriately.

Troubleshooting a Data Link Connection Problem5-19Troubleshooting a Synchronous ConnectionThis section assumes that you have isolated a problem to a s

Troubleshooting Routers5-20This shows the number of times the router dropped frames it received because of a lack of buffers or a lack of space on the

Troubleshooting a Data Link Connection Problem5-21Checking the Address Format (Bay Networks Standard Only)If the router is running Version 7.0 or late