All rights reserved. Printed in the USA. September 1997.
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 an y 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.
Trademarks
ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, Optivity , PPX, Quick2Config, and Bay Networks
are registered trademarks, and ANH, ASN, Bay•SIS, BayStack, BayStream, BCNX, BLNX, EZ Install,
EZ Internetwork, EZ LAN, IP AutoLearn, PathMan, PhonePlus, RouterMan, SPEX, Switch Node,
Bay Networks Press, and the Bay Networks logo are trademarks of Bay Networks, Inc.
All other trademarks and registered trademarks are the property of their respective owners.
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.
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.
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.
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).
ii
117349-A Rev. A
Page 3
Bay Networks, Inc. Software License Agreement
NOTICE:
installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement).
BY COPYING OR USING THE SOFTWARE, Y OU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS
LICENSE A GREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER
WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and
conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a
credit for the full purchase price
1. License Grant.
nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single
authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup
purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in
support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend
to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other
Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software
License Agreement that accompanies such software and upon payment by the end user of the applicable license fees
for such software.
2. Restrictions on use; reservation of rights.
Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any
revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any
copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use
for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user
manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or
transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and
its licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise
disclose to any third party the Software, or any information about the operation, design, performance, or
implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however,
Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s f acility,
provided they have agreed to use the Software only in accordance with the terms of this license.
3. Limited warranty.
installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function
substantially as described in its accompanying user manual during its warranty period, which begins on the date
Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole
remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be
included in a future Software release. Bay Networks further warrants to Licensee that the media on which the
Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days
from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is
returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not
apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility
for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained
from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the
Licensee’s requirements, b) that the Software will operate in the hardw are or software combinations that the Licensee
may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the
operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot
be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered,
except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’ s product,
resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE
FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL
OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMIT ATION ANY WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of
Please carefully read this license agreement before copying or using the accompanying software or
Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal,
The Software and user manuals are protected under copyright laws.
Bay Networks warrants each item of Software, as delivered by Bay Networks and properly
117349-A Rev. Aiii
Page 4
its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or
altered files, data, or programs.
4. Limitation of liability.
COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR
PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN
IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT
SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT
EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.
5. Government Licensees.
by or on behalf of the United States Government. The Software and documentation are commercial products, licensed
on the open market at market prices, and were developed entirely at private expense and without the use of any U.S.
Government funds. The license to the U.S. Gov ernment is granted only with restricted rights, and use, duplication, or
disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial
Computer Software––Restricted Rights clause of F AR 52.227-19 and the limitations set out in this license for civilian
agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.
6. Use of Software in the European Community.
European Community. If Licensee uses the Software within a country in the European Community, the Software
Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the
examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such
intended examination of the Software and may procure support and assistance from Bay Networks.
7. Term and termination.
Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the
Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information
shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if
Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason,
Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay
Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.
8. Export and Re-export.
or information without first obtaining any required export licenses or other governmental approvals. Without limiting
the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first
obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert
any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports
are restricted or embargoed under United States export control laws and regulations, or to any national or resident of
such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any
military end user or for any military end use, including the design, development, or production of any chemical,
nuclear, or biological weapons.
9. General.
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement
will be governed by the laws of the state of California.
Should you have any questions concerning this Agreement, contact Bay Netw orks, Inc., 4401 Great America P arkway,
P.O. Box 58185, Santa Clara, California 95054-8185.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND
LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND
COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS
AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY
NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.
If any provision of this Agreement is held to be invalid or unenforceable by a court of competent
IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY
This provision applies to all Software and documentation acquired directly or indirectly
This provision applies to all Software acquired for use within the
This license is effective until terminated; however, all of the restrictions with respect to
Licensee agrees not to export, directly or indirectly, the Software or related technical data
If you are an experienced network administrator responsible for operating and
managing Bay Networks® routers. It describes how to use event messages to
determine the status of your router.
Event Messages for Routers
•An overview of events (Chapter 1)
•A list of all event messages arranged alphabetically by entity
(Chapters 2 through 9)
Software Suites
Routing and Switching software is available in the following suites:
•The
Bridge, Translation Bridge, SNMP Agent, Bay Networks HDLC, PPP, OSPF,
EGP, BGP, and basic DLSw.
•The
IPX, and ATM DXI, in addition to the System Suite.
•The
addition to the System Suite.
•The
entirety.
•The
signaling, in addition to the LAN Suite.
System Suite
LAN Suite
WAN Suite
Corporate Suite
ARE ATM Suite
includes IP routing, 802.1 Transparent Bridge, Source Route
includes DECnet Phase 4, AppleTalk Phase 2, OSI, VINES,
includes ATM DXI, Frame Relay, LAPB, and X.25, in
provides
includes the System, LAN, and WAN suites in their
provides RFC 1483 and 1577 compliance, ATM UNI 3.0
117349-A Rev. A
•The
ARE VNR Corporate Suite
addition to the ARE ATM Suite and Corporate Suite.
provides ATM Forum LAN Emulation, in
xxv
Page 26
Event Messages for Routers
Availability of features and functionality described in this guide depends on the
suites you are using.
Audience
Written for network managers and technicians, this guide assumes that you have a
working knowledge of TCP/IP networking, and have some familiarity with
network management principles concerning the MIB, SNMP, system event
messaging, file system and configuration management.
Before Y ou Begin
For information on using the Events Manager to view Bay Networks event
messages, see
Configuring and Managing Routers with Site Manager
.
If you use Technician Interface, see
information on viewing Bay Networks event messages.
Conventions
This section describes the conventions used in this guide.
angle brackets (< >)Indicate that you choose the text to enter based on the
bold text
brackets ([ ])Indicate optional elements. You can choose none, one,
Using Technician Interface Software
description inside the brackets. Do not type the
brackets when entering the command. Example: if
ping
dinfo
<ip_address>
command.
PVCs
, you enter
command syntax is
192.32.10.12
Indicates text that you need to enter, command names,
and buttons in menu paths.
Example: Enter
Example: Use the
Example: ATM DXI > Interfaces >
PVCs button in the window that appears when you
select the Interfaces option from the ATM DXI menu.
or all of the options.
wfsm &
for
ping
identifies the
xxvi
117349-A Rev. A
Page 27
.
.
About This Guide
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:
Bay Networks Trap Monitor Filters
Set
separator ( > )Separates menu and option names in instructions and
internal pin-to-pin wire connections.
Example: Protocols > AppleTalk identifies the
AppleTalk option in the Protocols menu.
Example: Pin 7 > 19 > 20
.
ellipsis pointsHorizontal (. . .) and verticalellipsis points indicate
()
omitted information.
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
show at routes
nets
, you enter either
|
show at nets
or
, but not both.
117349-A Rev. A
xxvii
Page 28
Event Messages for Routers
Acronyms
AARPAppleTalk Address Resolution Protocol
ACEAdvanced Communications Engine
ACKacknowledgment
AISAlarm Indication Signal
AMIAddress Mark Inversion
ANIAutomatic Number Identification
ARPAddress Resolution Protocol
ASAutonomous System
ASNAccess Stack Node
ATMAsynchronous Transfer Mode
AURPAppleTalk Update-based Routing Protocol
B8ZSBinary Eight Zeros Suppression
BCNBackbone Concentrator Node
xxviii
BDRBackup Designated Router
BGPBorder Gateway Protocol
BOFLBreath of Life
BODbandwidth on demand
BOOTPBootstrap Protocol
BPDUBridge Protocol Data Unit
CACommunications Equipment Available
CCITTConsultative Committee on International Telegraph and
T elephone
CICConnect Incoming Call
CISCard Information Structure
CNConcentrator Node
COMcommunications port
CPEcustomer premises equipment
117349-A Rev. A
Page 29
About This Guide
CPUCentral Processing Unit
CRNCall Request with Number
CRSConfiguration Report Server
CSMA/CDCarrier Sense Multiple Access/Carrier Detect
CSU/DSUChannel Service Unit/Data Service Unit
CTSClear To Send
DCEData Communications Equipment
DDN/PDNDefense Data Network/Public Data Network
DICDisconnect Incoming Call
DLCIData Link Connection Identifier
DLCMIData Link Control Management Interface
DLSSee DLSw
DLSwData Link Switching
DMAPDirect Memory Access Processor
117349-A Rev. A
DNISDialed Number Identification Service
DOSDisk Operating System
DPData Path
DRDesignated Router
DS1E1Multichannel T1/E1
DSRData Set Ready
DTEData Terminal Equipment
DTRData T erminal Ready
DUARTDual Universal Asynchronous Receiver/Transmitter
DXIData Exchange Interface
EGPExterior Gateway Protocol
FDDIFiber Distributed Data Interface
FDLFacility Data Link
FIFOFirst-In-First-Out
xxix
Page 30
Event Messages for Routers
FLOPFloppy Disk Controller
FNFeeder Node
FRFrame Relay
FREFast Routing Engine
FSfile system
GAMEGate Access Management Entity
GFSgeneric file system
HIMIBHardware Implemented MIB
HSNHistory Serial Number
HSSIHigh Speed Serial Interface
HUBAccess Node Repeater
HWFHardware Filter
IEinformation element
IHUI hear you
xxx
I/Oinput/output
IDMAIndependent Direct-Memory Access
IMRIntegrated Multiport Repeater
IPInternet Protocol
IPSOSee RIPSO
IPEXInternet Protocol over X.25
IPXInternet Packet Exchange
ISDNIntegrated Services Digital Network
IS-ISIntermediate System to Intermediate System
ISOInternational Organization for Standardization
LANlocal area network
LAPBLink Access Procedure Balanced
LBLearning Bridge
LCPLink Control Protocol
117349-A Rev. A
Page 31
About This Guide
LCTLink Confidence Test
LEDLight-Emitting Diode
LEMLink Error Monitor
LERlink error rate
LLlow level
LLCLogical Link Control
LMILocal Management Interface
LNLink Node
LNMLAN Network Manager
LOADERDynamic Loader
LOFLoss of Frame
LOSLoss of Signal
LQRLink Quality Report
MACmedia access control
117349-A Rev. A
MAUMedia Attachment Unit
MCT1Multichannel T1
MIBManagement Information Base
MIRMaximum Information Rate
MODEMIFModem Interface
MTUmaximum transmission unit
NANPNorth American Numbering Plan
NAKnegative acknowledgment
NBMANon-Broadcast Multi-Access
NCPNetwork Control Program
NetBIOSNetwork Basic Input-Output System
NMInon-maskable interrupt
NMLNative Mode LAN
NICNetwork Information Center
xxxi
Page 32
Event Messages for Routers
NOVRAMNon-Volatile Random Access Memory
NOV_SYNCNon-Volatile Synchronization
NTPNetwork Time Protocol
NVFSNon-Volatile File System
OOFOut-Of-Frame
OSIOpen Systems Interconnection
OSPFOpen Shortest Path First
OUIorganizationally unique identifier
P AMPhysical Access Method
P APPassword Authentication Protocol
PCphysical connection
PCAPPacket Capture
PCMPhysical Connection Management
PCMCIAPersonal Computer Memory Card International
Association
xxxii
PDUprotocol data unit
PHYPhysical Level
PLCPPhysical Layer Convergence Protocol
PPPPoint-to-Point Protocol
PPXParallel Packet Express
PROMProgrammable Read-Only Memory
PTYpseudo teletypewriter
PVCpermanent virtual circuit
QENETQuad Ethernet
QLLCQualified Link Level Control
RARPReverse Address Resolution Protocol
RAIRemote Alarm Indication
RAMRandom Access Memory
117349-A Rev. A
Page 33
About This Guide
REMRing Error Monitor
RIrouting information
RIFrouting information field
RIPRouting Information Protocol
RIPSORevised IP Security Option
RPCremote procedure call
RPSRing Parameter Server
RSVPResource Reservation Protocol
RTCReal Time Clock
RTMPRouting Table Maintenance Protocol
RUIRemote User Interface
SAPService Access Point
SIPSMDS Interface Protocol
SMDSSwitched Multimegabit Data Services
SYSsystem
TBLtable
TCPTransmission Control Protocol
TELNETTelnet Server
TFtraffic filter
TFTPTrivial File Transfer Protocol
TI_RUITechnician Interface/Remote User Interface
TNCTelnet Client
TTRTTarget Token Rotation Time
TTYteletypewriter
UNIUser Network Interface
VCvirtual circuit
VINESVirtual Networking System
WANwide area network
xxxiv
WEPWAN Encryption Protocol
VBRVariable Bit Rate
VCIvirtual circuit interface
VPIvirtual path interface
XMODEMXmodem/Ymodem
XNSXerox Network Systems
ZIPZone Information Protocol
XCVR(Ethernet) Transceiv er
117349-A Rev. A
Page 35
Ordering Bay Networks Publications
To purchase additional copies of this document or other Bay Networks
publications, order by part number from Bay Networks Press
numbers:
•Phone--U.S./Canada: 888-422-9773
•Phone--International: 510-490-4752
•FAX--U.S./Canada and International: 510-498-2609
The Bay Networks Press catalog is available on the World Wide Web at
support.baynetworks.com/Library/GenMisc
available on the W orld W ide Web at
support.baynetworks.com/Library/tpubs.
Bay Networks Customer Service
You can purchase a support contract from your Bay Networks distributor or
authorized reseller, or directly from Bay Networks Services. For information
about, or to purchase a Bay Networks service contract, either call your local Bay
Networks field sales office or one of the following numbers:
About This Guide
™
at the following
. Bay Networks publications are
117349-A Rev. A
RegionTelephone numberFax number
United States and
Canada
Europe33-4-92-96-69-6633-4-92-96-69-96
Asia/Pacific61-2-9927-8888 61-2-9927-8899
Latin America561-988-7661561-988-7550
800-2LANWAN; then enter Express
Routing Code (ERC) 290, when prompted,
to purchase or renew a service contract
978-916-8880 (direct)
978-916-3514
Information about customer service is also available on the World Wide Web at
support.baynetworks.com.
xxxv
Page 36
Event Messages for Routers
How to Get Help
If you purchased a service contract for your Bay Networks product from a
distributor or authorized reseller, contact the technical support staff for that
distributor or reseller for assistance.
If you purchased a Bay Networks service program, call one of the following Bay
Networks Technical Solutions Centers:
Technical Solutions Center Telephone numberFax number
Billerica, MA800-2LANWAN978-916-3514
Santa Clara, CA800-2LANWAN408-495-1188
Valbonne, France33-4-92-96-69-6833-4-92-96-69-98
Sydney, Australia61-2-9927-880061-2-9927-8811
Tokyo, Japan81-3-5402-018081-3-5402-0173
xxxvi117349-A Rev. A
Page 37
Chapter 1
Overview
This chapter gives an overview of Bay Networks event messages and provides
information on the following topics:
•Event message format
•Entities
•Severity levels
•SNMP trap format
Understanding Events and Traps
An event is something that happens to the operating status of a router platform.
The router stores the event as a single entry in a memory-resident log.
A trap is simply an event that the router platform transmits to some external
network device.
An event message provides a brief description of an event, along with the event
code associated with that event. The event code is useful if you are using
third-party network management software to view Bay Networks events. It is also
useful when looking up events in this book.
This guide provides detailed descriptions of the Bay Networks event messages,
along with recommended responses to these events.
117349-A Rev. A1-1
Page 38
Event Messages for Routers
Viewing Event Messages
You view the log file containing Bay Networks event messages using the Bay
Networks network management software (Site Manager), the Bay Networks
command-line interface (Technician Interface), or any compatible third-party
network management software.
For information on viewing e vents using Site Manager or a compatible third-party
network management software, see Configuring and Managing Routers with Site
Manager. For information on viewing events using the Technician Interface, see
Using Technician Interface Software.
Event Message Format
Chapters 2 through 9 organize Bay Network event messages by entity, severity,
and event code. A typical event description consists of six entries, as T
shows.
Table 1-1.Event Message Format
able 1-1
EntryDescription
Entity Code/Event Code The code assigned to the entity issuing the event and the code assigned to the
event. Together, this pair uniquely identifies a Bay Network router platform event.
Decimal IdentifierThe decimal equivalent of the 32-bit SNMP trap that the router platform transmits.
Network management applications use this decimal identifier.
SeverityFault, Warning, Information, or Trace.
MessageText displayed in event log.
MeaningClarification of event message.
ActionRecommended user response to event (if necessary).
Entities
Events are always associated with a particular entity. An entity is the software that
generates a message. Entities include Bay Networks software dedicated to the
operation of a software service, such as TFTP and IP, and the GAME operating
system. T
associated entity codes.
1-2117349-A Rev. A
able 1-2 lists the entities (both their abbreviations and full names) and
Page 39
Overview
Table 1-2.Entities
EntityDescriptionCode
ACEAdvanced Communications Engine board10
AOTPolled Asynchronous over TCP/IP137
APPLETALKAppleTalk protocol36
APPNAdvanced Peer-to-Peer Networking protocol86
ARPAddress Resolution Protocol19
ASYNCAsynchronous Protocol87
A TMAsynchronous Transfer Mode78
ATM_DXIAsynchronous Transfer Mode/Data Exchange
Interface protocol
ATM_LEAsynchronous Transfer Mode LAN Emulation service100
ATM_SIGAsynchronous Transfer Mode Signaling service95
ATMINTFAsynchronous Transfer Mode Interface service76
BGPBorder Gateway protocol52
BGP3Border Gateway protocol Version 353
BGP4Border Gateway protocol Version 472
BISYNCBisynchronous over TCP/IP (BOT) protocol105
BODBandwidth on Demand: dial backup and
dial-on-demand services
BOOTRouter boot operation22
BOOTPBootstrap protocol59
BTSBinary Synchronous Communication Transport service104
CRMCircuit Resource Manager service91
CSMACDCarrier Sense Multiple Access/ Carrier Detect
(Ethernet) driver
Data
Compression
(WCP)
DCMMWData Collection Module Middleware96
DECNETDECnet IV protocol4
Data Compression84
49
54
9
(continued)
117349-A Rev. A1-3
Page 40
Event Messages for Routers
Table 1-2.Entities
EntityDescriptionCode
DLSData Link Switching (DLSw) protocol50
DMAPDirect Memory Access processor39
DOSDisk Operating System28
DPData Path service6
DSU/CSUDigital Service Unit/Channel Service Unit111
DS1E1Multichannel T1/E163
DVMRPDistance Vector Multicast Routing Protocol (refers to FTP
service)
E1E1 driver35
EGPExterior Gateway protocol46
FDDIFiber Distributed Data Interface driver8
FLOPFloppy disk controller32
FNTS_ATM Fujitsu Network Transmission Systems ATM 116
FRFrame Relay protocol25
FSFile System64
FTPFTP service (referred to as the DVMRP entity)88
GAMEGate Access Management Entity5
HSSIHigh Speed Serial Interface driver27
HUBAccess Node repeater71
HWCOMPHardware Compression driver99
HWFHardware Filter37
IGMPIGMP service83
IPInternet protocol2
IPv6Internet Protocol version 6100
IPEXIP Encapsulation on X.2593
IPXInternet Packet Exchange protocol30
ISDNISDN service79
ISDN_BRIISDN BRI driver service80
KEYMGRKey Manager118
LAPBLink Access Procedure Balanced73
(continued)
88
(continued)
1-4117349-A Rev. A
Page 41
Overview
Table 1-2.Entities
EntityDescriptionCode
LBLearning Bridge protocol1
LLCLogical Link Control protocol48
LNMLAN Network Manager protocol51
LOADERDynamic loader55
MCT1Multichannel T167
MIBManagement Information Base13
MODEMModem service110
MODEMIFModem Interface57
MODULEModule driver21
NATNetwork Address Translation141
NBASENBASE75
NBIPNetBIOS over IP service77
NLSPNetwork Link State Protocol97
NMLNative Mode LAN1
NOV_SYNCNon-Volatile memory Synchronization61
NTPNetwork Time Protocol109
NVFSNon-Volatile File System11
OSIOpen Systems Interconnection protocol38
OSPFOpen Shortest Path First 12
PCAPPacket Capture62
PINGPING MIB85
PPPPoint-to-Point Protocol44
PPRIProtocol Priority service90
PTYPseudo TTY driver41
QLLCQualified Link Level Control122
RADIUSRadius service115
RARPReverse Address Resolution Protocol45
RFWALLFirewall service119
RIP6Routing Information Protocol version 6120
(continued)
(continued)
117349-A Rev. A1-5
Page 42
Event Messages for Routers
Table 1-2.Entities
EntityDescriptionCode
RREDUNDRouter Redundancy service98
RSVPResource Reservation Protocol139
RUIBOOTRemote User Interface Boot102
SDLCSynchronous Data Link Control74
SMDSSwitched Multimegabit Data Service24
SNMPSimple Network Management Protocol3
SP ANSpanning T ree protocol16
SRSource Routing Bridge protocol29
ST2ST2 service94
STAStatistical thresholds and alarms56
STATSStatistical data collection92
SWSERVSwitched access service58
SYNCSynchronous driver20
SYSSystem record60
SYSLOGSystem log89
T1T1 driver34
TBLRouting table14
TCPTransmission Control Protocol47
TELNETTelnet server protocol40
TFTraffic Filter15
TFTPTrivial File Transfer Protocol7
TIBay Networks Technician Interface0
TI_RUITechnician Interface/Remote User Interface (Site
Manager)
TNCTelnet Client protocol70
TOKEN_RINGToken Ring driver26
TTYTeletypewriter17
VINESVirtual Networking System protocol23
WEPWAN Encryption Protocol117
WCPData compression84
(continued)
18
(continued)
1-6117349-A Rev. A
Page 43
Overview
Table 1-2.Entities
EntityDescriptionCode
X25X.25 protocol43
XMODEMXmodem/Ymodem protocol42
XNSXerox Networking Systems protocol31
Severity Levels
Event and trap messages are always associated with one of five severity levels.
able 1-3 describes the severity levels and lists the code that corresponds to each
T
one. This guide does not cover Debug messages, because these are for Bay
Networks internal use only.
Table 1-3.Severity Levels
SeverityDescriptionCode
FaultIndicates a major service disruption. A configuration, network,
WarningIndicates that a service acted in an unexpected manner. 4
InformationIndicates routine events. Usually no action is required.2
TraceIndicates information about each packet that traversed the
DebugIndicates information that Bay Networks Customer Support
(continued)
8
or hardware problem usually causes such a disruption. The
entities involved keep restarting until the problem is resolved
either by the router itself or by you.
10
network. Bay Networks recommends viewing this type of trap
message only when diagnosing network problems.
1
uses. These messages are not documented.
117349-A Rev. A1-7
Page 44
Event Messages for Routers
SNMP T rap Format
Some third-party network management applications, such as Net Expert,
OpenView and SunNet, allow you to trigger a desired operation when a specific
SNMP trap is received. This section describes the SNMP trap format.
The router platform transmits Bay Networks enterprise-specific traps as a 32-bit
value as follows:
•Octets 1 and 2 (the most significant 16 bits) contain values of 1 and 0
respectively to identify a Bay Networks enterprise-specific trap.
•Octet 3 contains a code value that identifies the software entity that generated
the trap. T
code values.
•Octet 4 contains the event code that (in conjunction with the entity code)
uniquely identifies the event.
Each 32-bit value is accompanied by three variable bindings that convey the ev ent
string that describes the trap condition, the slot that hosts the entity that generated
the trap, and the trap severity as listed earlier in T
able 1-2, shown earlier, lists software entities and their associated
able 1-3.
For example, the following event issued by the HSSI entity may be configured as
an SNMP trap:
The sections that follow list Bay Networks event messages in alphabetical order
by entity . This chapter cov ers entities from A CE
entity, this chapter lists event messages by severity and event code. Each event
message provides a meaning, along with a recommended response if one is
required.
®
through ATMINTF . W ithin each
ACE Events
The Advanced Communications Engine service, referred to as the ACE entity,
issues the following event messages. The entity code assigned to ACE events
is 10.
Severity:Fault
Message:ACE hardware diagnostic: Undefined cascaded interrupt level 6
Meaning:A cascaded Level 6 interrupt occurred for an unknown reason.
Action:Contact the Bay Networks Technical Solutions Center if this condition persists.
Severity:Fault
Message:ACE hardware diagnostic: NMI: AC power failure
Meaning:A lower power condition is detected.
Action:Contact the Bay Networks Technical Solutions Center if this condition persists.
Severity:Fault
Message:ACE hardware diagnostic: NMI: local parity error
Meaning:A parity error is detected in the local memory bank.
Action:Replace the ACE processor if this condition persists.
Severity:Fault
Message:ACE hardware diagnostic: NMI: global parity error
Meaning:A parity error is detected in the global memory bank.
Action:Replace the ACE processor if this condition persists.
Severity:Fault
Message:ACE hardware diagnostic: NMI: unknown interrupt
Meaning:A Level 7 (NMI) interrupt occurred for an unknown reason.
Action:Contact the Bay Networks Technical Solutions Center if this condition persists.
Severity:Warning
Message:ACE hardware diagnostic: <message>
Meaning:A cascaded Level 6 interrupt occurred. The message text indicates the source of the
interrupt.
Action:Contact the Bay Networks Technical Solutions Center if there are multiple occurrences of
Severity:Warning
Message:ACE backplane type did not initialize in NOVRAM
Meaning:The backplane type detected is invalid.
Action:Enter the backplane FN, backplane LN, or backplane CN command at the
Technician Interface prompt to initialize the backplane in NOVRAM. Then reboot the
router.
AOT Events
Polled Asynchronous over TCP/IP (AOT) issues the following event messages.
The entity code assigned to AOT events is 137.
Severity:Fault
Message:System error, service attempting restart.
Meaning:AOT experienced a fatal error and is restarting automatically.
Action:Verify that the configuration is correct. Call the Bay Networks Technical Solutions Center
Severity:Warning
Message:Illegal node id in aarp response <response_no.>
Meaning:The router received an illegal response (one that specified 0 or FF as the node ID) in reply
to an AARP request. The packet could be corrupted.
Severity:Warning
Message:Illegal net range <network_start_no.> -- <network_end_no.> for circuit <circuit_no.>
Meaning:The circuit <circuit_no.> was configured with a network range that is invalid.
Action:Assign a valid network range using the router’s Network Start and Network End
Severity:Warning
Message:No default zone configured on circuit <circuit_no.>
Meaning:The circuit <circuit_no.> was not assigned to a default zone.
Action:Assign the circuit to the default zone specified for this network, then re-enable the
Severity:Warning
Message:Illegal network number <network_ID> for circuit <circuit_no.>
Meaning:The circuit <circuit_no.> was assigned an illegal network number <network_ID>.
Action:Assign a valid network number to the circuit, then re-enable the interface.
Severity:Warning
Message:Illegal node number <node_ID> for circuit <circuit_no.>
Meaning:The circuit <circuit_no.> has been assigned an illegal node number <node_ID>.
Action:Assign a valid node number to circuit <circuit_no.>, then re-enable the interface.
Severity:Warning
Message:Net or node were zero -- dynamically obtaining address for circuit <circuit_no.>
Meaning:The circuit <circuit_no.> has been statically assigned an illegal address with either the
network ID portion or node ID portion of the address equal to 0, which is an invalid value
for either of these fields. The router will dynamically obtain a valid address for circuit
<circuit_no.>.
Severity:Warning
Message:Received invalid BrRq from <network_ID>.<node_ID> on circuit <circuit_no.>
Meaning:The circuit <circuit_no.> received an invalid broadcast request packet from the node
whose AppleTalk address is <network_ID>.<node_ID>. The packet could be corrupted.
Severity:Warning
Message:Received invalid FwdReq from <network_ID>.<node_ID> on circuit <circuit_no.>
Meaning:The circuit <circuit_no.> receiv ed an invalid forward request packet from the node whose
AppleTalk address is <network_ID>.<node_ID>. The packet could be corrupted.
Severity:Warning
Message:Static configuration conflict -- address in use
Meaning:This circuit has been statically assigned an address that is already in use on the AppleTalk
network.
Action:Assign a new address to this circuit (checking first to make certain that it is unique on the
AppleTalk network), or allow the router to dynamically assign an address to the circuit.
Severity:Warning
Message:No free node numbers
Meaning:All node numbers are in use on this network. This can occur if two (usually synchronous)
interfaces initialize at the same time and randomly pick the same node ID.
Action:Reduce the number of AppleTalk nodes on the network, or increase the size of the network
range. (For example, if the network range is 2 to 3, increase it to 2 to 4.) If this event
occurred on a synchronous circuit, statically configure the AppleTalk address on each
interface.
Severity:Warning
Message:Getnetinfo reply: zone should have been null
Meaning:Another router sent an incorrect response to this router’s GetNetInfo request.
Action:Check to see if the other router is misconfigured.
Severity:Warning
Message:GNI Timeout -- No NetInfoReply received
Meaning:An AppleTalk interface that is configured as a nonseed router sent out GetNetInfo packets
but did not receive a valid GetNetInfo reply in the time allowed (6 seconds).
Action:Every network must contain at least one seed router; make certain that a seed router is
Severity:Warning
Message:Could not get complete zone list
Meaning:The router could not get the entire zone list from the seed router to which it sent out a
GetNetInfo request. This can only happen if the router fails, or if the router is configured
on a highly unstable network.
Severity:Warning
Message:RTMP Timeout -- No RTMP DATA recvd
Meaning:An AppleTalk interface configured as a nonseed router did not receive a response to its
RTMP request in the time allowed (6 seconds).
Action:Check the status of other routers on the network, then re-enable the AppleTalk interface.
Severity:Warning
Message:Failed adding local net -- no buffers
Meaning:This slot is running low on buffers, probably due to excessive traffic.
Action:Disable, then enable the affected circuit.
Severity:Warning
Message:Bad non extended net <network_ID> from <network_ID>.<node_ID>
Meaning:The router received an RTMP packet from the router <network_ID>.<node_ID> that
contained an illegal network number.
Action:Check the configuration of the originating router.
Severity:Warning
Message:Bad distance <distance> for net <network_ID> from <network_ID>.<node_ID>
Meaning:The router received an RTMP packet from the router <network_ID>.<node_ID>
specifying an illegal hop count of between 16 and 30. A valid hop count is between 0 and
15.
Action:Check the configuration of the originating router.
Severity:Warning
Message:Range type conflict for net <network_ID> from <network_ID>.<node_ID>
Meaning:The router received an RTMP packet from the router <network_ID>.<node_ID>
containing an unexpected range type (either nonextended or extended).
Action:Check the configuration of all routers on the network.
Severity:Warning
Message:Invalid zone len <zone_name_length> -- zone <first_four_characters_of_zone _name>
Meaning:The router received an illegal zone name from another router. The zone name length
<zone_name_length> is in hexadecimal, as are the first four characters of the zone name
<first_four_characters_of_zone name>.
Action:Check the configuration of all routers on the network.
Severity:Warning
Message:GetNetInfo reply: bad multicast length
Meaning:A GetNetInfo reply received by the router contained an invalid mulicast length (the valid
length for Token Ring and Ethernet is 6; the valid length for SMDS is 8).
Action:Check the configuration of the originating router.
Severity:Warning
Message:Number of zones on extended net conflict
Meaning:When the AppleTalk interface was initialized, a seed router was configured with a total
zone count for this network that was different from the total zone count configured on
other routers.
Action:Check the configuration of the seed routers on the network.
Severity:Warning
Message:No WAN Broadcast Address configured
Meaning:No WAN broadcast address has been configured for the AppleTalk interface.
Action:Specify a WAN broadcast address for the interface.
Severity:Warning
Message:No SMDS individual address configured
Meaning:No SMDS individual address has been configured for the AppleTalk interface.
Action:Specify an SMDS individual address for the interface.
Severity:Warning
Message:Configured WAN broadcast address length doesn’t match protocol
Meaning:The WAN broadcast address length is incorrect.
Action:Reconfigure the WAN Broadcast Address parameter.
Severity:Warning
Message:PPP requires a network range of one network
Meaning:If you enable AppleTalk routing services on a PPP circuit, you must specify the network
range so that the network start equals the network end. (For example, 5-5 and 7-7 are v alid
network ranges; however, 8-10 is not.)
Action:Reconfigure the Network Start or Network End parameter.
Severity:Warning
Message:Only one zone allowed on a PPP circuit
Meaning:Multiple AppleTalk zones are configured on this PPP circuit. If you enable AppleTalk
routing services on a PPP circuit, then you can only specify a single zone for the network.
Severity:Warning
Message:Negotiated routing protocol not supported
Meaning:PPP did not negotiate RTMP as the routing protocol.
Action:Reconfigure the remote end of this PPP circuit so that it runs RTMP.
Severity:Warning
Message:Length of MAC address is incorrect for media
Meaning:The MAC address specified is too long for this type of WAN interface.
Action:Reconfigure the WAN MAC Address parameter.
Severity:Warning
Message:Unsupported media <circuit_type_PAM_ID><WAN_protocol_L2_ID>
Meaning:AppleTalk is enabled on an unsupported type of circuit or is running over an unsupported
Severity:Warning
Message:MTU too small <MTU_size>
Meaning:The MTU value is set too low for this circuit.
Action:Increase the MTU size for this circuit.
Severity:Warning
Message:Bad net range <network_start_no.> -- <network_end_no.> from <IP_address>
Meaning:The router received an AURP RI-Response or RI-Update packet from the router peer
<IP_address> that contained an illegal network range.
Action:Check the configuration of the originating router.
Severity:Warning
Message:Bad non extended net <network_ID> from <IP_address>
Meaning:The router received an AURP RI-Response or RI-Update packet from the router peer
<IP_address> that contained an illegal network number.
Action:Check the configuration of the originating router.
Severity:Warning
Message:AURP: range overlap <network_start_no.> -- <network_end_no.> from <IP_address>
ignored
Meaning:The router received an AURP RI-Response or RI-Update packet from the router peer
<IP_address> containing a network range <network_start_no.> -- <network_end_no.>
that overlapped with an existing network range. The overlapping network range was
ignored.
Action:Eliminate the overlap of the network ranges, then restart the AURP connection (disable,
then enable the connection), so that the ignored network range is retransmitted.
Severity:Info
Message:Interface <network_ID>.<node_ID> up on circuit <circuit_no.>
Meaning:The circuit identified by <circuit_no.> has become enabled, thus providing AppleTalk
routing service to the interface. The interface’s AppleTalk address is
<network_ID>.<node_ID>.
Severity:Info
Message:Interface <network_ID>.<node_ID> down on circuit <circuit_no.>
Meaning:The circuit identified by <circuit_no.> has become disabled, thus disabling AppleTalk
routing service to the interface. The interface’s AppleTalk address is
<network_ID>.<node_ID>.
Severity:Info
Message:AURP Connection closed (timed out) <IP_address>
Meaning:The router has closed the connection to the specified peer, because the configured timeout
Severity:Info
Message:AURP Connection closed by peer <IP_address>
Meaning:The peer external router <IP_address> has closed the AURP connection between itself
Severity:Info
Message:AURP Connection request from <IP_address> rejected
Meaning:The local router received an AURP connection request from peer external router
<IP_address>; however, it rejected the request, because no connection is configured
between the routers.
Severity:Info
Message:AURP Connection request reject by <IP_address> (code <error_code_no.>)
Meaning:The peer has rejected an Open request from the local router. The code is the error code in
the Open Response packet. Refer to the following table for more information on AURP
error codes.
Severity:Trace
Message:AARP: node <network_ID>.<node_ID> deleted
Meaning:The router deleted the node whose address is <network_ID>.<node_ID> from its AARP
Severity:Trace
Message:RTMP: net <network_start_no.> -- <network_end_no.> came up
Meaning:The router added the network <network_start_no.> -- <network_end_no.> to its RTMP
Severity:Trace
Message:RTMP: net <network_start_no.> -- <network_end_no.> went down
Meaning:The router deleted the network <network_start_no.> -- <network_end_no.> from its
Severity:Trace
Message:FWD: entry <network_ID>.<node_ID> to <network_ID>.<node_ID> came up
Meaning:The router added the nodes <network_ID>.<node_ID> to <network_ID>.<node_ID> to
Severity:Trace
Message:FWD: entry <network_ID>.<node_ID> to <network_ID>.<node_ID> went down
Meaning:The router deleted the nodes <network_ID>.<node_ID> to <network_ID>.<node_ID>
Severity:Trace
Message:ZIP: entry <zone_name> on net <network_ID> came up
Meaning:The router added zone <zone_name> on network <network_ID> to its zone table.
Severity:Trace
Message:ZIP: entry <zone_name> on net <network_ID> went down
Meaning:The router deleted zone <zone_name> on network <network_ID> from its zone table.
2-20117349-A Rev. A
Page 67
Event Messages (ACE through ATMINTF)
APPN Events
The Advanced Peer-to-Peer Networking service, referred to as the APPN entity,
issues the following event messages. The entity code assigned to APPN events is
Severity:Fault
Message:System error, APPN service attempting restart.
Meaning:The APPN driver experienced a fatal error and is restarting automatically. The driver will
attempt to restart up to five times.
Action:Contact the Bay Networks Technical Solutions Center if this condition persists.
type = <type>, Sending CP name = <CP_name>, Sending LU name = <LU_name>,
Partner LU name = <LU_name>.
Meaning:The LU detected an error, causing it to send an UNBIND to its partner LU. The SNA
<sense_data> denotes the exact error condition detected. The <mode_name> is the name
of the deactivated session. If no node name is available when the alert is sent, the mode
name is encoded as eight X’40’ bytes.
Action:Review the associated resources and check the communications program in both the local
code>, Sending CP name = <CP_name>, Partner CP name = <CP_name>.
Meaning:SNA session setup failed due to a problem with BIND processing, or a problem occurred
with the communications program at the remote node. The SNA <sense_data> denotes
the exact BIND with an UNBIND and the exact error condition being reported.
Action:Check the communications program at the remote node and contact the Bay Networks
code>, Sending CP name = <CP_name>, Partner CP name = <CP_name>.
Meaning:A format error was detected in a topology database update (TDU) general data stream
(GDS) variable. The topology database manager instructs session services to UNBIND the
CP-CP session over which the TDU was received. The associated SNA <sense_data> is
sent in the UNBIND. The TDU containing the error is ignored. The SNA <sense_data>
denotes the exact error condition being reported.
Action:Check the communications program at the remote node, or contact the Bay Networks
Meaning:The architecture-defined maximum for the resource sequence number (RSN) has been
reached. The resource (a node or transmission group) is no longer available for use. The
topology database manager continues to run. The TDU causing the error is discarded.
Action:Check the name of the resource in question.
reference code>, Sending CP name = <CP_name>, Partner CP name = <CP_name>.
Meaning:Indicates a protocol violation on a LOCATE or BIND request or, that the
architecture-defined maximum resource sequence number (RSN) has been reached. The
resource (a node or transmission group) is no longer available for use. The TDU causing
the error is discarded. The SNA <sense_data> denotes the exact error condition being
reported.
Action:Check the communications program at the remote node, or contact the Bay Networks
code>, Sending CP name = <CP_name>, Partner CP name = <CP_name>.
Meaning:Insufficient resources are available for directory services. Deadlock has been detected
between directory services (DS) components in two nodes. When this condition exists,
directory services instructs session services to UNBIND the CP-CP session to the other
node. If this problem reoccurs, it may indicate a node configuration error. The SNA
<sense_data> denotes the exact error condition being reported.
Action:Check the communications program at the remote node, or contact the Bay Networks
alert reference code>, Sending CP name = <CP_name>, Partner CP name =
<CP_name>.
Meaning:An end node CP, without authorization, has attempted to delete a resource (Directory
Services). Probable cause is that an unauthorized user attempted to change the
configuration. The SNA <sense_data> denotes the exact error condition being reported.
Action:Check the communications program at the remote node; check for unauthorized users.
Severity:Warning
Message:Out of resources: Sense = <sense_data>, Alert code = <product alert reference code>,
Sending CP name = <CP_name>.
Meaning:Indicates the failure of an intermediate session setup due to insufficient storage. If the
session connection manager is unable to allocate the resources needed for a session, it
UNBINDS the session. The SNA <sense_data> denotes the exact error condition being
reported.
Severity:Warning
Message:SNA protocol error: Sense = <sense_data>, Alert code = <pr oduct alert r eference code>,
Sending CP name = <CP_name>, Destination LU name = <LU_name>.
Meaning:The session connector has received an invalid request unit (RU) and has signaled the
session connector manager to UNBIND the session. The SNA <sense_data> denotes the
exact error condition being reported. The <product alert reference code> identifies the
module in the multiprotocol network program that discovered the error.
Action:Check the communication program in the adjacent node; check the pacing parameters in
<transaction_program_name>, Sending CP name = <CP_name>.
Meaning:A required transaction program cannot be started.
Action:Check the APPN configuration for any setting(s) that may be preventing the transaction
reference code>, Sending CP name = <CP_name>, Partner CP name = <CP_name>.
Meaning:Indicates a protocol violation on a LOCATE or BIND request. The SNA <sense_data>
denotes the exact error condition being reported.
Action:Check the communications program at the remote node. Contact the Bay Networks
Technical Solutions Center if the problem persists.
Severity:Warning
Message:DLUR configuration error - Partner LU does not support DLUS: Alert code = <product
alert reference code>, Sending CP name = <CP_name>.
Meaning:Indicates that the primary/backup DLUS node does not support DLUR.
Action:Check the adjacent link station configuration to see if DLUR is enabled or disabled.
Severity:Info
Message:Directory entry added: name = <parent_resource_name>, owner = <parent_name>.
Meaning:A directory entry was added to the local directory services database. This entry may have
been generated by a local resource registration, or it may be the cached results of a
Severity:Info
Message:Directory entry removed: name = <parent_resource_name>, owner = <parent_name>.
Meaning:A directory entry was removed from the local directory database. This entry may have
been deregistered, suspected to be invalid, or is being replaced by a newer entry.
Severity:Info
Message:RTP Connection activated: name = <name>.
Meaning:The Rapid Transport Protocol (RTP) connection was activ ated. The <name> indicates the
Severity:Info
Message:RTP Connection deactivated: name = <name>.
Meaning:The RTP connection was deactivated. The <name> indicates the 8-byte RTP connection
Severity:Info
Message:RTP Connection Path Switched: name = <name>.
Meaning:The existing RTP connection switched to another path. The <name> indicates the 8-byte
Severity:Info
Message:RTP Connection Connected: name = <name>.
Meaning:RTP established a connection. The <name> indicates the 8-byte RTP connection name.
Severity:Info
Message:RTP Connection Disconnected: name = <CP_name>.
Meaning:The existing RTP connection was disconnected. The <name> indicates the 8-byte RTP
Severity:Info
Message:RTP Connection Session Count Changing: name = <name>, connections: <number>
Meaning:The number of active RTP sessions is changing. The <name> indicates the 8-byte RTP
connection name. The <number> indicates the latest number of sessions over the RTP
Severity:Info
Message:RTP Connection Indication: Conn state <state>, cause <cause>: name = <name>
Meaning:The RTP connection changed state. The <state> indicates the current condition and
<cause> indicates the reason. The <name> indicates the 8-byte RTP connection name.
Severity:Info
Message:Focal point acquired: ms category = <focal_point_category>, fp name = <CP_name>,
appl name = <focal_point_application_name>, fp type = <focal_point_type>.
Meaning:The local network node acquired SNA-formatted network management data from an entry
point node on the network. A focal point is an entry point that provides centralized
management and control for other entry points. The fp name is the fully qualified control
point name of the current focal point. The appl name is the name of the current focal point
application. The fp type indicates the type of focal point: explicit primary, backup, default
primary, domain, or host. For detailed information on focal and entry points, refer to the
IBM publication, IBM Systems Network Architecture: Management Services
Severity:Info
Message:Focal point revoked: ms category = <focal_point_category>, fp name = <CP_name>,
appl name = <focal_point_application_name>, fp type = <focal_point_type>.
Meaning:The local network node revoked SNA-formatted network management data from an entry
point node on the network. A focal point is an entry point that provides centralized
management and control for other entry points. The fp name is the fully qualified control
point name of the current focal point. The appl name is the name of the current focal point
application. The fp type indicates the type of focal point: explicit primary, backup, default
primary, domain, or host. For detailed information on focal and entry points, refer to the
IBM publication, IBM Systems Network Architecture: Management Services
Severity:Info
Message:ISR session activated: FQCP name = <CP_name>, PCID = <procedure_correlator_ID>.
Meaning:An intermediate session was activated. The FQCP name indicates the fully qualified
control point name of the originator of the session. The PCID indicates the 8-byte
hexadecimal procedure correlator ID of the activated session.
Severity:Info
Message:NN Topology -- Node activated: node name = <name>, node type = <node_type>.
Meaning:A topology update was received indicating that a node is no w acti ve. The node name is the
fully qualified name of the node. The node type indicates a network node (NN) or a virtual
Severity:Info
Message:NN Topology -- Node deactivated: node name = <name>, node type = <node_type>.
Meaning:A topology update was received indicating that a node is now inactive. The node name is
the fully qualified name of the node. The node type indicates a network node (NN) or a
Severity:Info
Message:Endpoint session activated: LU name = <LU_name>, PLU name = <LU_name>.
Meaning:A session was activated between a local LU and a partner LU. The LU name is an 8-byte
Severity:Info
Message:Endpoint session deactivated: LU name = <LU_name>, PLU name = <LU_name>.
Meaning:A session was deactivated between a local LU and a partner LU. The LU name is an
Severity:Info
Message:DLUR: PU activated, PU name = <LU_name>, LS name = <link_station_name>.
Meaning:A PU2.0 device has been activated by the SSCP through the DLUR/DLUS pipe.
Severity:Info
Message:DLUR: PU deactivated, PU name = <LU_name>, LS name = <link_station_name>.
Meaning:A PU2.0 device has been deactivated by the SSCP through the DLUR/DLUS pipe.
Severity:Fault
Message:System error, async TTY service attempting restart.
Meaning:The ASYNC driver experienced a fatal error and is restarting automatically. The driver
will attempt to restart up to five times.
Action:Verify that the configuration is correct. Call the Bay Networks Technical Solutions Center
Severity:Warning
Message:Connector COM <connector_no.> out of range.
Meaning:The synchronous connector COM <connector_no.> is invalid and will be ignored.
Action:Modify the configuration file to accurately describe the link module described in the
Severity:Warning
Message:Connector COM <connector_no.> not verified with diagnostic.
Meaning:The connector identified by <connector_no.> has been placed in service. However,
powerup diagnostics were aborted/terminated prior to verifying the connection.
Action:Rerun powerup diagnostics by issuing the technician interface diags command to the slot
in question if you wish to verify COM <connector_no.> integrity.
Severity:Warning
Message:Connector COM <connector_no.>: Failed to connect to, port <port_no.>.
Connector COM <connector_no.>: Listening failed on, port <port_no.>.
Connector COM <connector_no.>: Invalid remote IP address, port <port_no.>.
Connector COM <connector_no.>: Connect failed to, port <port_no.>.
Meaning:A connection or listening failure occurred when the ASYNC protocol attempted to
connect to a destination port, or an invalid remote IP address was specified.
Action:Check the ASYNC configuration for an incorrect remote IP address, or check the cabling
Severity:Warning
Message:Connector COM <connector_no.>: Inactivity time out on connection.
Meaning:The ASYNC idle timer value was exceeded and the connection timed out.
Action:Check the ASYNC configuration and increase the idle timer value.
Severity:Warning
Message:Configured Connector COM <connector_no.>: Configured MTU of <value_1> is too
large, use <value_2> or smaller
Meaning:The MTU on the specified synchronous connection is too large.
Action:Reconfigure the MTU for the specified synchronous connector so that it is equal to or less
Severity:Info
Message:Connector COM <connector_no.> configuration deleted.
Meaning:The record for the specified synchronous connection has been deleted from the
Severity:Info
Message:Connector COM <connector_no.>: Providing asynch passthrough service.
Meaning:The ASYNC protocol was enabled on a specific communications port.
Severity:Fault
Message:System error, service attempting restart.
Meaning:ATM experienced a fatal error and is restarting automatically. ATM attempts to restart.
Action:Verify that the configuration is correct. Call the Bay Networks Technical Solutions Center
Severity:Fault
Message:Out of memory while allocating vc-cct table block.
Meaning:ATM ran out of memory while trying to allocate enough space for a vc-cct table.
Action:Contact the Bay Networks Technical Solutions Center.
Severity:Warning
Message:Line <line_no.>: No ATM Interface MIB entry found.
Meaning:The ATM Interface Table (object ID 1.3.6.1.4.18.3.4.23.1.1) does not contain an entry for
the specified line.
Action:Check the configuration of the ATM interface. Make sure that the line number equals the
Severity:Warning
Message:Line <line_no.> Cct <circuit_no.>: No ATM Service Record MIB entry found.
Meaning:No ATM services record exists on line <line_no.> cct <circuit_no.>.
Action:Configure an ATM service record for this line circuit combination.
Severity:Warning
Message:Line <line_no.>: Pkt length error- <SHORT/LONG>.
Meaning:ATM rejected a received frame because it was either less than six characters long (short)
or longer than the maximum allowed frame size for the current media (long).
Severity:Warning
Message:VPI/VCI <VPI_no.>/<VCI_no.> configured as Hybrid but with no direct circuit value.
Meaning:A circuit value is missing for this hybrid virtual channel.
Action:Check the circuit entry and verify that the direct circuit number is not 0.
Severity:Warning
Message:ATM unable to allocate memory.
Meaning:ATM was unable to allocate buffer memory.
Action:Contact the Bay Networks Technical Solutions Center.
Severity:Warning
Message:ATM call reference <call_ref> already used.
Meaning:ATM has been requested to act upon an already used call reference.
Action:Contact the Bay Networks Technical Solutions Center.
Severity:Warning
Message:ATM registration failed on cct <circuit_no.>.
Meaning:The circuit <circuit_no.> cannot forward a registration message to ATM.
Action:Contact the Bay Networks Technical Solutions Center.
Severity:Info
Message:Line <line_no.> Cct <circuit_no.> ATM Service Record disabled.
Meaning:The ATM Service Record is disabled on the specified line and circuit number.
Severity:Info
Message:Line <line_no.>: Multiple duplicate active lines
Meaning:Duplicate lines are in the process of becoming active. Contact the Bay Networks T echnical
Severity:Info
Message:Line <line_no.> Cct <circuit_no.> ATM Service Record set to delete
Meaning:ATM deleted the ATM Service Record for the specified line and circuit.
Severity:Trace
Message:Line <line_no.>, Cct <circuit_no.>: Deleted Service Record
Meaning:ATM deleted the Service Record from the specified line and circuit.
Severity:Fault
Message:System error, service attempting restart.
Meaning:ATM DXI experienced a fatal error and is restarting automatically. ATM DXI will attempt
to restart up to five times.
Action:Verify that the configuration is correct. Call the Bay Networks Technical Solutions Center
Severity:Warning
Message:Line <line_no.> LLIndex <low_level_index>: ATM LMI address is of incorrect type.
Meaning:The Local Management Interface protocol has dropped a packet because of an address
Severity:Warning
Message:Line <line_no.> LLIndex <low_level_index>: No ATM Interface MIB entry found.
Meaning:The ATM Interface Table (object ID 1.3.6.1.4.18.3.5.9.5.2) does not contain an entry for
the specified line.
Action:Check the configuration of the ATM interface. Make sure that the line number is equal to
Severity:Warning
Message:Line <line_no.> LLIndex <low_level_index>: ATM LMI service has terminated.
Meaning:The LMI protocol has failed or been removed from the specified line.
Severity:Warning
Message:Line <line_no.> LLIndex <low_level_index>: No extended address bit in atm dxi header.
Meaning:The ATM DXI code has dropped a packet because of a mismatch between the setting of
the extended address bit and the actual length of the address contained in the packet.
Severity:Warning
Message:Line <line_no.> LLIndex <low_level_index>: Pkt length error- <SHORT/LONG>.
Meaning:A received frame has been rejected because it was either less than six characters long
(short) or longer than the maximum allowed frame size for the current media (long).
Severity:Warning
Message:Line <line_no.> LLIndex <low_level_index>: Unsupported control
(<rcvd_control_value>) on PVC <VPI_ID>/<VCI_ID>.
Meaning:The specified virtual path/virtual circuit received an unknown or unsupported Control
field. The received control value must be the same as the value defined by RFC 1294.
Action:Check the configuration of the ATM interface or the ATM PVC. Verify that both endpoints
Severity:Warning
Message:Line <line_no.> LLIndex <low_level_index> -- Misdelivered CS_PDU detected.
Meaning:A Segmentation and Reassembly Packet Data Unit (CS_PDU) has been discarded,
because an invalid virtual path ID/virtual circuit ID w as detected at the CS ATM Adaption
layer.
Action:Check the configuration of the ATM interface or the ATM PVC.
Severity:Warning
Message:Line <line_no.> LLIndex <low_level_index> -- Misdelivered MPE_PDU detected.
Meaning:An MPE_PDU has been discarded because of an inactive SAP (Service Access Point).
Action:Check the configuration of the ATM Interface or the ATM PVC. Verify that both endpoints
Severity:Warning
Message:Vpi/Vci <VPI_ID>/<VCI_ID> configured as 2but with no Direct Circuit value.
Meaning:A circuit value is missing for this direct/hybrid virtual channel. Check the PVC entry and
Severity:Warning
Message:LMI response from DSU timed out on line <line_no.> LLIndex <low_level_index>
Meaning:The LMI response from the DSU has timed out on the specified line.