Avaya Troubleshooting Routers Troubleshooting guide

  • Hello! I am an AI chatbot trained to assist you with the Avaya Troubleshooting Routers Troubleshooting guide. I’ve already reviewed the document and can help you find the information you need or explain it in simple terms. Just ask your questions, and providing more details will help me assist you more effectively!
Troubleshooting Routers
Router Software Version 10.0
Site Manager Software Version 4.0
Part No. 112937 Rev. A
January 1996
4401 Great America Parkway 8 Federal Street
Santa Clara, CA 95054 Billerica, MA 01821
Copyright © 1988–1996 Bay Networks, Inc.
All rights reserved. Printed in the USA. January 1996.
The information in this document is subject to change without notice. The statements, configurations, technical data, and
recommendations in this document are believed to be accurate and reliable, but are presented without express or implied
warranty. Users must take full responsibility for their applications of any products specified in this document. The
information in this document is proprietary to Bay Networks, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance with the
terms of that license. A summary of the Software License is included in this document.
Restricted Rights Legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notice for All Other Executive Agencies
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the
rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial
Computer Software-Restricted Rights clause at FAR 52.227-19.
Trademarks of Bay Networks, Inc.
ACE, AFN, BCN, BLN, BN, CN, FRE, LN, Optivity, SynOptics, SynOptics Communications, Wellfleet and the Wellfleet
logo are registered trademarks and AN, ANH, ASN, BaySIS, BayStack, BCNX, BLNX, BNX, EZ Internetwork, EZ LAN,
FN, PathMan, PhonePlus, PPX, Quick2Config, RouterMan, SPEX, Bay Networks, Bay Networks Press, the Bay Networks
logo and the SynOptics logo are trademarks of Bay Networks, Inc.
Third-Party Trademarks
All other trademarks and registered trademarks are the property of their respective owners.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to
make changes to the products described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit
layout(s) described herein.
Portions of the code in this software product are Copyright © 1988, Regents of the University of California. All rights
reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright
notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other
materials related to such distribution and use acknowledge that such portions of the software were developed by the
University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from
such portions of the software without specific prior written permission.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE.
In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains
restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).
Bay Networks, Inc.
4401 Great America Parkway, Santa Clara, CA 95054
8 Federal Street, Billerica, MA 01821
Bay Networks Software License
This Software License shall govern the licensing of all software provided to licensee by Bay Networks (“Software”).
Bay Networks will provide licensee with Software in machine-readable form and related documentation
(“Documentation”). The Software provided under this license is proprietary to Bay Networks and to third parties from
whom Bay Networks has acquired license rights. Bay Networks will not grant any Software license whatsoever, either
explicitly or implicitly, except by acceptance of an order for either Software or for a Bay Networks product
(“Equipment”) that is packaged with Software. Each such license is subject to the following restrictions:
1. Upon delivery of the Software, Bay Networks grants to licensee a personal, nontransferable, nonexclusive license
to use the Software with the Equipment with which or for which it was originally acquired, including use at any
of licensee’s facilities to which the Equipment may be transferred, for the useful life of the Equipment unless
earlier terminated by default or cancellation. Use of the Software shall be limited to such Equipment and to such
facility. Software which is licensed for use on hardware not offered by Bay Networks is not subject to restricted
use on any Equipment, however, unless otherwise specified on the Documentation, each licensed copy of such
Software may only be installed on one hardware item at any time.
2. Licensee may use the Software with backup Equipment only if the Equipment with which or for which it was
acquired is inoperative.
3. Licensee may make a single copy of the Software (but not firmware) for safekeeping (archives) or backup
purposes.
4. Licensee may modify Software (but not firmware), or combine it with other software, subject to the provision
that those portions of the resulting software which incorporate Software are subject to the restrictions of this
license. Licensee shall not make the resulting software available for use by any third party.
5. Neither title nor ownership to Software passes to licensee.
6. Licensee shall not provide, or otherwise make available, any Software, in whole or in part, in any form, to any
third party. Third parties do not include consultants, subcontractors, or agents of licensee who have licensee’s
permission to use the Software at licensee’s facility, and who have agreed in writing to use the Software only in
accordance with the restrictions of this license.
7. Third-party owners from whom Bay Networks has acquired license rights to software that is incorporated into
Bay Networks products shall have the right to enforce the provisions of this license against licensee.
8. Licensee shall not remove or obscure any copyright, patent, trademark, trade secret, or similar intellectual
property or restricted rights notice within or affixed to any Software and shall reproduce and affix such notice on
any backup copy of Software or copies of software resulting from modification or combination performed by
licensee as permitted by this license.
Note:
This is Bay Networks basic license document. In the absence of a
software license agreement specifying varying terms, this license — or the
license included with the particular product — shall govern licensee’s use of
Bay Networks software.
Bay Networks, Inc.
4401 Great America Parkway, Santa Clara, CA 95054
8 Federal Street, Billerica, MA 01821
Bay Networks Software License
(continued)
9. Licensee shall not reverse assemble, reverse compile, or in any way reverse engineer the Software. [Note:
For
licensees in the European Community, the Software Directive dated 14 May 1991 (as may be amended from time
to time) shall apply for interoperability purposes. Licensee must notify Bay Networks in writing of any such
intended examination of the Software and Bay Networks may provide review and assistance.]
10. Notwithstanding any foregoing terms to the contrary, if licensee licenses the Bay Networks product “Site
Manager,” licensee may duplicate and install the Site Manager product as specified in the Documentation. This
right is granted solely as necessary for use of Site Manager on hardware installed with licensee’s network.
11. This license will automatically terminate upon improper handling of Software, such as by disclosure, or Bay
Networks may terminate this license by written notice to licensee if licensee fails to comply with any of the
material provisions of this license and fails to cure such failure within thirty (30) days after the receipt of written
notice from Bay Networks. Upon termination of this license, licensee shall discontinue all use of the Software
and return the Software and Documentation, including all copies, to Bay Networks.
12. Licensee’s obligations under this license shall survive expiration or termination of this license.
v
Contents
Troubleshooting Routers
About This Guide
Audience .......................................................................................................................... xv
Before You Begin ............................................................................................................. xv
Bay Networks Customer Support ....................................................................................xvi
CompuServe .............................................................................................................xvi
InfoFACTS ................................................................................................................xvii
World Wide Web .......................................................................................................xvii
How to Get Help .............................................................................................................xvii
Conventions ...................................................................................................................xviii
Ordering Bay Networks Publications ...............................................................................xix
Acronyms .........................................................................................................................xix
Chapter 1
Introduction
Preventing Problems ......................................................................................................1-1
Reading the Release Notes and Relevant Documentation ......................................1-2
Minimizing Disruption When Installing New Software ..............................................1-2
Selecting the Proper Tool for Configuring a Router ..................................................1-2
Saving Your Configuration Changes .........................................................................1-2
Backing Up Your Files ..............................................................................................1-3
Maintaining Consistent Files in Multiple Memory Cards ..........................................1-3
Handling Memory Cards to Prevent Static Damage ................................................1-3
Responding to a Failed prom Command .................................................................1-4
Preparing to Troubleshoot ...............................................................................................1-4
Getting Acquainted with the Troubleshooting Tools ..................................................1-4
Using the System Log to Display Event Messages ...........................................1-4
Displaying and Changing Configuration Settings and Statistics ........................1-9
Using Ping .......................................................................................................1-20
vi
Using Packet Capture ......................................................................................1-21
Using Inbound Telnet to Access the Technician Interface ................................1-21
Taking a Snapshot of Your Network ........................................................................1-22
Documenting Each Step ...............................................................................................1-23
Performing One Corrective Task at a Time ...................................................................1-24
Chapter 2
Determining the Scope of a Problem
Chapter 3
Troubleshooting an Operational Problem
Damaged Router ............................................................................................................3-2
Power Problem ...............................................................................................................3-2
Blown Fuse .....................................................................................................................3-2
LEDs Not Lit ...................................................................................................................3-3
Router Won’t Boot ..........................................................................................................3-3
Checking the Boot PROMs .............................................................................................3-6
Making Sure the Router Software Image Is Correct for the Router ................................3-6
Making Sure All Slots Use the Same Router Software Image and Configuration File ...3-6
Verifying That the Router Software Images in Each Processor Match .....................3-7
Verifying That the Configuration Files in Each Processor Match .............................3-9
Lost Password ..............................................................................................................3-10
No Space Left on Memory Card ...................................................................................3-11
Memory or Buffer Problem ...........................................................................................3-12
Bad Forward Checksum Errors ....................................................................................3-17
Finding the Slot That Sent a Bad Backplane-BOFL-Packet ...................................3-18
Finding the Slot That Sent a Bad Packet That Was Not a BOFL Packet ................3-19
Fault Message ..............................................................................................................3-20
Chapter 4
Troubleshooting a Physical Media Problem
Making Sure the Link Module Is Working .......................................................................4-1
Determining the Media-Specific State ............................................................................4-2
Troubleshooting the Cable Connection ...........................................................................4-4
Chapter 5
Troubleshooting a Data Link Connection Problem
Troubleshooting an ATM Connection ..............................................................................5-2
vii
Dropped Frames ......................................................................................................5-4
ATM VC . . . Failed Message .....................................................................................5-4
Upper-Layer Protocols Failing to Pass Packets ........................................................5-5
Troubleshooting an Ethernet Connection .......................................................................5-6
Troubleshooting an FDDI Connection ...........................................................................5-11
Troubleshooting a Frame Relay Connection .................................................................5-14
Log messages from Frame Relay Indicate Circuit Is Down ...................................5-14
Frame Relay Switch Keeps Marking the Circuit as Down ......................................5-15
Frame Relay Circuit Up, but Protocol Data Is Not Transmitting ..............................5-15
PVC Transmitting, but Not Receiving .....................................................................5-16
Frame Relay Configured with LMI Invokes an Xoff State .......................................5-16
Troubleshooting an MCT1 Connection .........................................................................5-17
Troubleshooting a Synchronous Connection ................................................................5-19
Checking the Address Format (Bay Networks Standard Only) ..............................5-21
Troubleshooting a Synchronous to X.21 Connection .............................................5-21
Reception Errors Incrementing or Reception Count Not Incrementing ..................5-21
Troubleshooting the Internal Clock Settings (Lab Environments Only) ..................5-23
Troubleshooting a Token Ring Connection ...................................................................5-24
Troubleshooting Other Data Link Protocols ..................................................................5-26
Chapter 6
Troubleshooting a Network Connection Problem
Troubleshooting AppleTalk ..............................................................................................6-2
Local Net Range Conflict Event Message ................................................................6-3
Zone . . . Conflict Event Message .............................................................................6-3
Static Configuration Conflict Event Message ...........................................................6-4
Troubleshooting DLSw ....................................................................................................6-4
Troubleshooting IP ..........................................................................................................6-6
Troubleshooting Telnet, FTP, and TFTP ...................................................................6-8
Ping Does Not Work .................................................................................................6-9
Router Cannot Ping Another Local Device ......................................................6-10
Router Cannot Ping Endstation, but Can Ping Other Endstations on the Same
Segment ..........................................................................................................6-11
Endstation Cannot Ping the Remote Interface on the Router ..........................6-11
Endstation Can Ping Devices on the Same Segment, but Cannot Ping the Router 6-12
viii
Endstation Can Ping Local and Remote Interfaces on the Router, but Cannot Ping a
Remote Station ................................................................................................6-14
Troubleshooting Routing Information Protocol (RIP) ..............................................6-14
Troubleshooting Open Shortest Path First (OSPF) ................................................6-15
Troubleshooting IPX .....................................................................................................6-16
Troubleshooting OSI .....................................................................................................6-21
Troubleshooting Switched Services ..............................................................................6-23
Master Cannot Connect to Slave ...........................................................................6-25
Troubleshooting RS232 Raise DTR Dial (Unbalanced) .........................................6-25
Troubleshooting V.35 Raise DTR Dial (Balanced) ..................................................6-26
Troubleshooting ISDN BRI and PRI .......................................................................6-27
Troubleshooting Other Networking Protocols ...............................................................6-30
Chapter 7
Troubleshooting a Site Manager Problem
Site Manager Won’t Start ...............................................................................................7-1
Site Manager Won’t Start on a PC ...........................................................................7-1
Cannot Find File Message .................................................................................7-2
Working Directory or Path Is Invalid Message ...................................................7-3
Unable to Find UDP Port Numbers for SNMP Message ...................................7-3
Site Manager Won’t Start on a UNIX Workstation ....................................................7-3
Unable to Load SNMP MIB or File Was Inaccessible Message ........................7-4
Unable to Run . . . Module Message ..................................................................7-4
Cannot Establish a Site Manager Session with the Router ............................................7-5
Using an Alternative Site Manager Workstation to Enable Access ..........................7-5
Using the Technician Interface to Enable Access ....................................................7-6
Cannot Connect after Upgrading a Series 5 Router ................................................7-6
Cannot Connect Site Manager Running on a PC ....................................................7-6
Cannot Connect Site Manager Running on a UNIX Workstation .............................7-7
Target Does Not Respond (or Similar Message) ............................................................7-8
Cannot Allocate Colormap Message ..............................................................................7-9
UNIX Workstation Generating Core Dumps ...................................................................7-9
Chapter 8
Getting Help
Reporting a Problem to the Bay Networks Technical Response Center .........................8-1
Sending and Retrieving Files to and from Bay Networks ...............................................8-2
ix
Appendix A
Reading the Event Log
System Startup .............................................................................................................. A-2
Dial-on-Demand Raise DTR Log ................................................................................. A-18
Dial-on-Demand V.25bis .............................................................................................. A-22
MCT1 Log Information in a Lab Testing Environment .................................................. A-28
Appendix B
Using the Technician Interface to Configure and Run Packet Capture
Overview ........................................................................................................................ B-1
Implementation Notes .................................................................................................... B-4
Getting Started .............................................................................................................. B-4
Preparing Packet Capture to Run ........................................................................... B-4
Assigning the Processors to Run Packet Capture ............................................ B-5
Creating an Instance of Packet Capture ........................................................... B-6
Allocating Memory for the Packet Capture File ............................................... B-10
Specifying the Number of Bytes in Each Packet to Copy ...................................... B-11
Enabling Packet Capture ................................................................................ B-11
Starting Packet Capture ........................................................................................ B-12
Terminating Packet Capture ..................................................................................B-12
Using the Technician Interface to Display a Packet Capture File .......................... B-13
Deleting a Packet Capture Instance ...................................................................... B-16
Using Optional Features .............................................................................................. B-16
Configuring the Direction of the Packets to be Copied .......................................... B-16
Configuring a Termination Trigger ......................................................................... B-17
Assigning Filters .................................................................................................... B-19
Setting the Filter Response to a Match .......................................................... B-20
Specifying the String to Compare with the Packet Data ................................. B-21
Specifying the Data to Compare with the String ............................................. B-21
Selecting the Number of Filters that Must Match ............................................ B-24
Configuration Examples .............................................................................................. B-25
Displaying the Current Packet Capture Configuration Settings ................................... B-28
Displaying Event Messages Issued by Packet Capture ............................................... B-29
Using a Sun Workstation or DOS PC to Display Packets ............................................ B-29
Getting the Name of the Packet Capture File ........................................................ B-30
Using FTP to Transfer the File ............................................................................... B-30
x
Using TFTP to Transfer the File ............................................................................. B-31
Using XMODEM to Transfer the File ..................................................................... B-32
Displaying the File ................................................................................................. B-33
Converting a Packet Capture File to Network General Sniffer Format ........................ B-33
Reference Guide to Packet Capture ............................................................................ B-35
Displaying the Packet Capture Attribute Names and Numbers ............................. B-35
Packet Capture Parameter Descriptions ............................................................... B-37
Basic Parameters ........................................................................................... B-37
Trigger Parameters ......................................................................................... B-42
Filter Parameters ............................................................................................ B-44
Media-Specific Instructions and Examples ........................................................... B-48
CSMA/CD ....................................................................................................... B-48
Protocols Supported By Synchronous, T1, E1, and MCT1 ............................. B-49
Token Ring ...................................................................................................... B-53
FDDI ............................................................................................................... B-54
HSSI ............................................................................................................... B-54
ISDN ............................................................................................................... B-54
Interpreting a Packet Capture Instance Number ................................................... B-55
Index
xi
Figures
Figure 1-1. Filtering Parameters Window ...................................................................1-6
Figure 3-1. Verifying the Slot ID on an ASN ...............................................................3-5
Figure 3-2. Finding the Slot Number When the Message References
a Backplane BOFL .................................................................................3-17
Figure 3-3. Finding the Slot Number When the Message Does Not Reference
a Backplane BOFL .................................................................................3-19
Figure 6-1. Comparing the Endstation and Router Configurations ..........................6-13
Figure 7-1. Cannot Find File Error Message ..............................................................7-2
xiii
Tables
Table 1-1. Technician Interface Event Message Filters .............................................1-7
Table 1-2. Example of an Imaginary Object Named House ....................................1-12
Table 3-1. ASN Front-Panel LEDs ............................................................................3-4
Table 3-2. ASN SPX Rear-Panel LEDs ....................................................................3-4
Table 3-3. Memory Configuration System Software Limitations .............................3-13
Table 4-1. Values of Media State Attributes ..............................................................4-2
Table 5-1. Error Codes in the “ATM VC mod failed” Log Message ...........................5-5
Table B-1. Determining the Slot Mask ...................................................................... B-5
Table B-2. Structure of a Line Number ................................................................... B-55
xv
About This Guide
If you are responsible for isolating and solving problems associated with Bay
Networks routers, read this guide.
Audience
This guide assumes
You have experience configuring and managing Bay Networks routers.
You have a working knowledge of Site Manager and the Technician Interface.
You have a working knowledge of the protocols running on your routers.
Before You Begin
Before using this guide to solve a problem, refer to the following documents:
Release Notes for Router Software Version 10.0
Release Notes for Site Manager Software Version 4.0
Known Anomalies: Router Software 10.0 and Site Manager 4.0
This manual assumes that you also have access to the following Bay Networks
manuals, which are on the CD-ROM:
Using Technician Interface Software
Using Technician Interface Scripts
Managing Routers and BNX Platforms
Event Messages for Routers and BNX Platforms
The manuals associated with the software you are using
Troubleshooting Routers
xvi
Bay Networks Customer Support
Bay Networks provides live telephone technical support to our distributors,
resellers, and service-contracted customers from two U.S. and three international
support centers. If you have purchased your Bay Networks product from a
distributor or authorized reseller, contact the technical support staff of that
distributor or reseller for assistance with installation, configuration,
troubleshooting, or integration issues.
Customers also have the option of purchasing direct support from Bay Networks
through a variety of service programs. The programs include priority access
telephone support, on-site engineering assistance, software subscription, hardware
replacement, and other programs designed to protect your investment.
To purchase any of these support programs, including PhonePlus™ for 24-hour
telephone technical support, call 1-800-2LANWAN. Outside the U.S. and
Canada, call (408) 764-1000. You can also receive information on support
programs from your local Bay Networks field sales office, or purchase Bay
Networks support directly from your reseller. Bay Networks provides several
methods of receiving support and information on a nonpriority basis through the
following automated systems.
CompuServe
Bay Networks maintains an active forum on CompuServe. All you need to join us
online is a computer, a modem, and a CompuServe account. We also recommend
using the CompuServe Information Manager software, available from
CompuServe.
The Bay Networks forum contains libraries of technical and product documents
designed to help you manage and troubleshoot your Bay Networks products.
Software agents and patches are available, and the message boards are monitored
by technical staff and can be a source for problem solving and shared experiences.
Customers and resellers holding Bay Networks service contracts can visit the
special libraries to acquire advanced levels of support documentation and
software.
To open an account and receive a local dial-up number, call CompuServe at
1-800-524-3388 and ask for Representative No. 591.
In the United Kingdom, call Freephone 0800-289378.
About This Guide
xvii
In Germany, call 0130-37-32.
In Europe (except for the United Kingdom and Germany), call
(44) 272-760681.
Outside the U.S., Canada, and Europe, call (614) 529-1349 and ask for
Representative No. 591, or consult your listings for an office near you.
Once you are online, you can reach our forum by typing the command GO
BAYNETWORKS at any ! prompt.
InfoFACTS
InfoFACTS is the Bay Networks free 24-hour fax-on-demand service. This
automated system contains libraries of technical and product documents designed
to help you manage and troubleshoot your Bay Networks products. The system
can return a fax copy to the caller or to a third party within minutes of being
accessed.
World Wide Web
The World Wide Web (WWW) is a global information system for file distribution
and online document viewing via the Internet. You need a direct connection to the
Internet and a Web Browser (such as Mosaic or Netscape).
Bay Networks maintains a WWW Home Page that you can access at
http://www.baynetworks.com. One of the menu items on the Home Page is the
Customer Support Web Server, which offers technical documents, software
agents, and an E-mail capability for communicating with our technical support
engineers.
How to Get Help
For additional information or advice, contact the Bay Networks Technical
Response Center in your area:
United States 1-800-2LAN-WAN
Valbonne, France (33) 92-966-968
Sydney, Australia (61) 2-903-5800
Tokyo, Japan (81) 3-328-005
Troubleshooting Routers
xviii
Conventions
This section describes the conventions used in this guide.
angle brackets (< >) Indicate that you choose the text to enter based on the
description inside the brackets. Do not type the
brackets when entering the command. Example: if
command syntax is
ping
<ip_address>
, you enter
ping
192.32.10.12
arrow character (
) Separates menu and option names in instructions.
Example: Protocols
AppleTalk identifies the
AppleTalk option in the Protocols menu.
bold text
Indicates text that you need to enter and command
names in text. Example: Use the
dinfo
command.
brackets ([ ]) Indicate optional elements. You can choose none, one,
or all of the options.
ellipsis points (. . .) Indicate omitted information.
italic text
Indicates variable values in command syntax
descriptions, new terms, file and directory names, and
book titles.
quotation marks (“ ”) Indicate the title of a chapter or section within a book.
screen text
Indicates data that appears on the screen. Example:
Set
Bay Networks Trap Monitor Filters
vertical line (|) Indicates that you enter only one of the parts of the
command. The vertical line separates choices. Do not
type the vertical line when entering the command.
Example: If the command syntax is
show at routes
|
nets
,
you enter either
show at routes
or
show at
nets
, but not both.
About This Guide
xix
Ordering Bay Networks Publications
To purchase additional copies of this document or other Bay Networks
publications, order by part number from Bay Networks Press™ at the following
numbers. You may also request a free catalog of Bay Networks Press product
publications.
Phone: 1-800-845-9523
FAX - U.S./Canada: 1-800-582-8000
FAX - International: 1-916-939-1010
Acronyms
AAL ATM adaptation layer
ACE Advanced Communications Engine
AFN Access Feeder Node
ALC adaption layer control
ALN Access Link Node
AMI alternate mark inversion
AN Access Node
ARP Address Resolution Protocol
ASCII American Standard Code for Information Interchange
ASN Access Stack Node
AT AppleTalk
ATM Asynchronous Transfer Mode
B8ZS binary eight zeros substitution
BCN Backbone Concentrator Node
BECN Backward Explicit Congestion Notification
BERT bit error rate test
BLN Backbone Link Node
BN Backbone Node
BOFL breath of life
BRI basic rate interface
CD Carrier Detect
CHAP Challenge Handshake Authentication Protocol
Troubleshooting Routers
xx
CID channel identifier
CN Concentrator Node
CRC cyclic redundancy check
CRN call request number
CSMA/CD Carrier Sense Multiple Access/ Carrier Detect (Ethernet)
CSU channel service unit
CTS clear to send
DCE data communication equipment
DLCI data link control identifier
DLSw Data Link Switch
DOS Disk Operating System
DP Data Path
DPRAM Dual Port RAM
DS directory service
DS1E1 multichannel T1/E1 driver service
DSAP destination service access point
DSL digital subscriber loop
DSR data set ready
DSU digital service unit
DTE data terminal equipment
DTR data terminal ready
EIA Electronic Industry Association
ESF extended super frame
FDDI Fiber Distributed Data Interface
FDL Facility Data Link
FECN Forward Explicit Congestion Notification (FECN)
FN Feeder Node
FRE Fast Routing Engine
FRE-2 Fast Routing Engine - 2
FSI FDDI System Interface
FSM finite state machine
FTP File Transfer Protocol
GAME Gate Access Management Entity
/