Page 1
Event Messages for
Routers and BNX
Platforms
Router Software Version 11.0
Site Manager Software Version 5.0
Part No. 114082 Rev. A
August 1996
Page 2
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. August 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 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.
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, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, Optivity, PPX, SynOptics, SynOptics
Communications, Wellfleet and the Wellfleet logo are registered trademarks and ANH, ASN, Bay•SIS, BCNX,
BLNX, EZ Install, EZ Internetwork, EZ LAN, PathMan, PhonePlus, Quick2Config, RouterMan, SPEX,
Bay Networks, Bay Networks Press, the Bay Networks logo and the SynOptics logo are trademarks of
Bay Networks, Inc.
Third-Party T rademarks
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 Univ ersity 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).
ii
114082 Rev. A
Page 3
Bay Networks Software 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.
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 whatsoev er , 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, none xclusiv e 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.
114082 Rev. A
iii
Page 4
Bay Networks Software License
9. Licensee shall not reverse assemble, reverse compile, or in any way reverse engineer the Software. [Note: For
licensees in the European Community, the Softw are Directiv e 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.
(continued)
iv
114082 Rev. A
Page 5
Contents
Event Messages for Routers and BNX Platforms i
About This Guide
Software Suites .............................................................................................................xxiii
Audience ........................................................................................................................xxiv
Before You Begin ...........................................................................................................xxiv
Conventions ...................................................................................................................xxiv
Acronyms .......................................................................................................................xxvi
Ordering Bay Networks Publications ............................................................................xxxii
Technical Support and Online Services
Bay Networks Customer Service .................................................................................xxxiv
Bay Networks Information Services ..............................................................................xxxv
World Wide Web .....................................................................................................xxxv
Customer Service FTP ...........................................................................................xxxv
Support Source CD ...............................................................................................xxxvi
CompuServe ......................................................................................................... xxxvi
InfoFACTS ............................................................................................................xxxvii
How to Get Help ................................................................................................... xxxvii
Chapter 1
Overview
Understanding Events and Traps ....................................................................................1-1
Viewing Event Messages ................................................................................................1-2
Event Message Format ..................................................................................................1-2
Entities ............................................................................................................................ 1-3
Severity Levels ................................................................................................................1-7
SNMP Trap Format .........................................................................................................1-8
114082 Rev. A
v
Page 6
Chapter 2
Event Messages (ACE through ATMINTF)
ACE Events ....................................................................................................................2-1
Fault Events .............................................................................................................2-1
Warning Events ........................................................................................................2-3
APPLETALK Events ........................................................................................................2-3
Fault Event ...............................................................................................................2-3
Warning Events ........................................................................................................2-4
Info Events .............................................................................................................2-15
Trace Events ..........................................................................................................2-17
APPN Events ................................................................................................................2-19
Fault Event .............................................................................................................2-19
Warning Events ......................................................................................................2-20
Info Events .............................................................................................................2-29
ARP Events ..................................................................................................................2-38
Info Events .............................................................................................................2-38
ASYNC Events .............................................................................................................2-39
Fault Event .............................................................................................................2-39
Warning Events ......................................................................................................2-39
Info Events .............................................................................................................2-41
ATM Events ...................................................................................................................2-42
Fault Events ...........................................................................................................2-42
Warning Events ......................................................................................................2-43
Info Events .............................................................................................................2-45
Trace Events ..........................................................................................................2-48
ATM_DXI Events ...........................................................................................................2-49
Fault Event .............................................................................................................2-49
Warning Events ......................................................................................................2-49
Info Events .............................................................................................................2-53
Trace Events ..........................................................................................................2-58
ATM_LE Events ............................................................................................................2-61
Fault Event .............................................................................................................2-61
Warning Events ......................................................................................................2-61
Info Events .............................................................................................................2-93
Trace Events ..........................................................................................................2-94
vi
114082 Rev. A
Page 7
ATM_SIG ....................................................................................................................2-100
Fault Events .........................................................................................................2-100
Warning Events ....................................................................................................2-101
Info Events ...........................................................................................................2-103
ATMINTF Events .........................................................................................................2-106
Fault Events .........................................................................................................2-106
Warning Events ....................................................................................................2-107
Info Events ...........................................................................................................2-117
Chapter 3
Event Messages (BGP through EGP)
BGP Events ....................................................................................................................3-1
Fault Event ...............................................................................................................3-1
Warning Events ........................................................................................................3-2
Info Events .............................................................................................................3-19
BGP3 Events ................................................................................................................3-23
Fault Event .............................................................................................................3-23
Warning Events ......................................................................................................3-24
Info Events .............................................................................................................3-24
BGP4 Events ................................................................................................................3-25
Fault Event .............................................................................................................3-25
Warning Events ......................................................................................................3-25
Info Events .............................................................................................................3-26
BISYNC Events ............................................................................................................3-26
Fault Events ...........................................................................................................3-26
Warning Events ......................................................................................................3-27
Info Events .............................................................................................................3-28
BOD Events ..................................................................................................................3-29
Fault Event .............................................................................................................3-29
Info Events .............................................................................................................3-29
BOOT Events ................................................................................................................3-30
Fault Event .............................................................................................................3-31
Warning Events ......................................................................................................3-31
BOOTP Events .............................................................................................................3-34
Fault Events ...........................................................................................................3-35
Warning Events ......................................................................................................3-36
114082 Rev. A
vii
Page 8
Info Events .............................................................................................................3-43
BTS Events ...................................................................................................................3-45
Fault Events ...........................................................................................................3-46
Info Events .............................................................................................................3-46
Trace Events ..........................................................................................................3-47
CRM Events .................................................................................................................3-47
Fault Events ...........................................................................................................3-47
Warning Events ......................................................................................................3-48
Info Events .............................................................................................................3-49
CSMACD Events ..........................................................................................................3-50
Fault Event .............................................................................................................3-50
Warning Events ......................................................................................................3-50
Info Events .............................................................................................................3-58
Data Compression Events ............................................................................................3-60
Fault Event .............................................................................................................3-60
Warning Events ......................................................................................................3-61
Info Events .............................................................................................................3-66
Trace Event ............................................................................................................3-67
DCMMW Events ...........................................................................................................3-67
Fault Events ...........................................................................................................3-68
Warning Events ......................................................................................................3-70
Info Events .............................................................................................................3-71
DECNET Events ...........................................................................................................3-72
Fault Event .............................................................................................................3-72
Warning Events ......................................................................................................3-72
Info Events .............................................................................................................3-77
Trace Events ..........................................................................................................3-78
DLS Events ...................................................................................................................3-80
Fault Event .............................................................................................................3-81
Warning Event ........................................................................................................3-81
Info Events .............................................................................................................3-82
Trace Events ..........................................................................................................3-83
DMAP Event .................................................................................................................3-84
Fault Event .............................................................................................................3-84
DOS Events ..................................................................................................................3-85
viii
114082 Rev. A
Page 9
Fault Events ...........................................................................................................3-85
Info Events .............................................................................................................3-87
DP Events .....................................................................................................................3-90
Fault Event .............................................................................................................3-91
Warning Events ......................................................................................................3-91
Info Events .............................................................................................................3-93
Trace Events ..........................................................................................................3-95
DS1E1 Events ..............................................................................................................3-96
Fault Event .............................................................................................................3-96
Warning Events ......................................................................................................3-96
Info Events ...........................................................................................................3-107
DVMRP Events ...........................................................................................................3-114
Fault Event ...........................................................................................................3-114
Warning Event ......................................................................................................3-114
Info Events ...........................................................................................................3-115
E1 Events ...................................................................................................................3-115
Fault Event ...........................................................................................................3-116
Warning Events ....................................................................................................3-116
Info Events ...........................................................................................................3-117
EGP Events ................................................................................................................3-120
Fault Event ...........................................................................................................3-121
Warning Events ....................................................................................................3-121
Info Events ...........................................................................................................3-128
Chapter 4
Event Messages (FDDI through FRSW_ISDN)
FDDI Events ...................................................................................................................4-1
Fault Events .............................................................................................................4-1
Warning Events ........................................................................................................4-4
Info Events .............................................................................................................4-12
FLOP Events ................................................................................................................4-15
Fault Event .............................................................................................................4-15
Warning Events ......................................................................................................4-16
FR Events .....................................................................................................................4-21
Fault Event .............................................................................................................4-21
Warning Events ......................................................................................................4-21
114082 Rev. A
ix
Page 10
Info Events .............................................................................................................4-25
Trace Events ..........................................................................................................4-30
FRSW Events ...............................................................................................................4-48
Fault Event .............................................................................................................4-48
Warning Events ......................................................................................................4-49
Info Events .............................................................................................................4-60
Trace Events ..........................................................................................................4-65
FRSW_BILLING Events ...............................................................................................4-74
Fault Event .............................................................................................................4-74
Warning Events ......................................................................................................4-74
Info Events .............................................................................................................4-82
Trace Events ..........................................................................................................4-83
FRSW_ISDN Events ....................................................................................................4-88
Fault Event .............................................................................................................4-88
Warning Events ......................................................................................................4-89
Info Events .............................................................................................................4-92
Chapter 5
Event Messages (FS through LOADER)
FS Events .......................................................................................................................5-1
Fault Event ...............................................................................................................5-1
FTP Events .....................................................................................................................5-2
Fault Event ...............................................................................................................5-2
Warning Event ..........................................................................................................5-3
Info Events ...............................................................................................................5-3
Trace Events ............................................................................................................5-5
GAME Events .................................................................................................................5-5
Fault Events .............................................................................................................5-6
Warning Events ......................................................................................................5-13
Info Events .............................................................................................................5-16
Trace Events ..........................................................................................................5-18
HSSI Events .................................................................................................................5-18
Fault Event .............................................................................................................5-18
Warning Events ......................................................................................................5-18
Info Events .............................................................................................................5-20
HUB Events ..................................................................................................................5-22
x
114082 Rev. A
Page 11
Fault Events ...........................................................................................................5-22
Warning Events ......................................................................................................5-23
Info Events .............................................................................................................5-23
HWCOMP ..................................................................................................................... 5-27
Fault Events ...........................................................................................................5-27
Warning ..................................................................................................................5-28
Info .........................................................................................................................5-31
HWF Events .................................................................................................................5-31
Warning Events ......................................................................................................5-31
Info Events .............................................................................................................5-32
IGMP Events ................................................................................................................5-33
Fault Events ...........................................................................................................5-34
Warning Events ......................................................................................................5-34
Information Events .................................................................................................5-35
IP Events ......................................................................................................................5-37
Fault Event .............................................................................................................5-37
Warning Events ......................................................................................................5-37
Info Events .............................................................................................................5-49
IPEX .............................................................................................................................5-52
Fault Events ...........................................................................................................5-53
Warning ..................................................................................................................5-53
Info .........................................................................................................................5-54
Trace ......................................................................................................................5-54
IPX Events ....................................................................................................................5-55
Warning Events ......................................................................................................5-55
Info Events .............................................................................................................5-57
Trace Events ..........................................................................................................5-62
ISDN Events .................................................................................................................5-65
Fault Event .............................................................................................................5-65
Warning Events ......................................................................................................5-65
Info Events .............................................................................................................5-66
Trace Events ..........................................................................................................5-67
ISDN BRI Events ..........................................................................................................5-68
Fault Event .............................................................................................................5-69
Warning Events ......................................................................................................5-69
114082 Rev. A
xi
Page 12
Info Events .............................................................................................................5-71
LAPB Events ................................................................................................................5-76
Fault Event .............................................................................................................5-76
Warning Events ......................................................................................................5-76
Info Events .............................................................................................................5-78
LB Events .....................................................................................................................5-79
Fault Event .............................................................................................................5-80
Warning Events ......................................................................................................5-80
Info Events .............................................................................................................5-81
Trace Event ............................................................................................................5-82
LLC Events ...................................................................................................................5-82
Fault Event .............................................................................................................5-82
Info Events .............................................................................................................5-82
LNM Events ..................................................................................................................5-83
Fault Event .............................................................................................................5-83
Warning Events ......................................................................................................5-84
Info Events .............................................................................................................5-85
LOADER Events ...........................................................................................................5-88
Fault Event .............................................................................................................5-88
Warning Events ......................................................................................................5-88
Trace Events ..........................................................................................................5-93
Chapter 6
Event Messages (MCT1 through OSPF)
MCT1 Events ..................................................................................................................6-1
MIB Events .....................................................................................................................6-1
Fault Event ...............................................................................................................6-1
Warning Event ..........................................................................................................6-2
Info Events ...............................................................................................................6-2
MODEMIF Events ...........................................................................................................6-3
Fault Events .............................................................................................................6-3
Warning Events ........................................................................................................6-4
Info Events ...............................................................................................................6-8
Trace Events ..........................................................................................................6-10
MODULE Events ..........................................................................................................6-15
Fault Event .............................................................................................................6-15
xii
114082 Rev. A
Page 13
Warning Events ......................................................................................................6-16
Info Events .............................................................................................................6-20
NBASE Events .............................................................................................................6-20
Fault Event .............................................................................................................6-20
Info Events .............................................................................................................6-21
NBIP Events .................................................................................................................6-21
Fault Event .............................................................................................................6-21
Warning Events ......................................................................................................6-22
Info Events .............................................................................................................6-22
NLSP Events ................................................................................................................6-24
Fault Event .............................................................................................................6-24
Warning Events ......................................................................................................6-24
Info Events .............................................................................................................6-31
Trace Events ..........................................................................................................6-35
NML Events ..................................................................................................................6-44
Fault Event .............................................................................................................6-44
NOV_SYNC Events ......................................................................................................6-44
Fault Event .............................................................................................................6-44
Info Event ...............................................................................................................6-45
NTP Events ..................................................................................................................6-45
Fault Event .............................................................................................................6-45
Warning Event ........................................................................................................6-46
Info Events .............................................................................................................6-46
Trace Events ..........................................................................................................6-49
NVFS Events ................................................................................................................6-50
Fault Event .............................................................................................................6-50
Warning Events ......................................................................................................6-50
Info Events .............................................................................................................6-55
OSI Events ...................................................................................................................6-57
Fault Event .............................................................................................................6-57
Info Events .............................................................................................................6-57
Trace Events ..........................................................................................................6-59
OSPF Events ................................................................................................................6-60
Fault Event .............................................................................................................6-61
Warning Events ......................................................................................................6-63
114082 Rev. A
xiii
Page 14
Info Events .............................................................................................................6-77
Trace Events ..........................................................................................................6-79
Chapter 7
Event Messages (PCAP through RUIBOOT)
PCAP Events ..................................................................................................................7-1
Fault Event ...............................................................................................................7-1
Warning Events ........................................................................................................7-2
Info Events .............................................................................................................7-15
PING Events .................................................................................................................7-16
Fault Event .............................................................................................................7-16
Info Events .............................................................................................................7-17
PPP Events ..................................................................................................................7-17
Fault Event .............................................................................................................7-17
Warning Events ......................................................................................................7-18
Info Events .............................................................................................................7-34
Trace Events ..........................................................................................................7-43
PPRI Events .................................................................................................................7-59
Fault Event .............................................................................................................7-59
Warning Event ........................................................................................................7-59
Trace Events ..........................................................................................................7-61
PTY Events ...................................................................................................................7-64
Info Event ...............................................................................................................7-64
RARP Protocol Events .................................................................................................7-64
Fault Events ...........................................................................................................7-64
Information Events .................................................................................................7-65
RREDUND Events ........................................................................................................7-65
Fault Event .............................................................................................................7-66
Warning Events ......................................................................................................7-67
Information Events .................................................................................................7-72
Trace Events ..........................................................................................................7-76
RUIBOOT Events ..........................................................................................................7-80
Fault Events ...........................................................................................................7-80
Warning Events ......................................................................................................7-80
Info Events .............................................................................................................7-80
xiv
114082 Rev. A
Page 15
Chapter 8
Event Messages (SDLC through SWSERV)
SDLC Events ..................................................................................................................8-1
Fault Event ...............................................................................................................8-1
Warning Events ........................................................................................................8-2
Info Events ...............................................................................................................8-2
SMDS Events .................................................................................................................8-3
Fault Event ...............................................................................................................8-3
Warning Events ........................................................................................................8-3
Info Events ...............................................................................................................8-8
Trace Events ..........................................................................................................8-10
SMDS_SW Events .......................................................................................................8-12
Fault Event .............................................................................................................8-12
Warning Events ......................................................................................................8-12
Information Events .................................................................................................8-23
Trace Event ............................................................................................................8-24
SMDS_SW_BILLING Events ........................................................................................8-25
Fault Event .............................................................................................................8-25
Warning Events ......................................................................................................8-25
Information Events .................................................................................................8-31
Trace Events ..........................................................................................................8-32
SNMP Events ...............................................................................................................8-37
Fault Event .............................................................................................................8-37
Warning Events ......................................................................................................8-38
Info Events .............................................................................................................8-39
Trace Event ............................................................................................................8-39
SPAN Events ................................................................................................................8-40
Fault Event .............................................................................................................8-40
Warning Events ......................................................................................................8-40
Info Events .............................................................................................................8-41
Trace Event ............................................................................................................8-42
SR Events .....................................................................................................................8-43
Fault Event .............................................................................................................8-43
Warning Events ......................................................................................................8-43
Info Events .............................................................................................................8-45
114082 Rev. A
xv
Page 16
Trace Event ............................................................................................................8-49
ST2 Events ...................................................................................................................8-49
Fault Events ...........................................................................................................8-49
Information Events .................................................................................................8-49
STA Events ...................................................................................................................8-50
Fault Event .............................................................................................................8-50
Warning Events ......................................................................................................8-51
Info Events .............................................................................................................8-51
STATS Events ...............................................................................................................8-53
Fault Event .............................................................................................................8-53
Warning Events ......................................................................................................8-53
Information Events .................................................................................................8-62
Trace Events ..........................................................................................................8-63
SWSERV Events ..........................................................................................................8-64
Fault Event .............................................................................................................8-64
Warning Event ........................................................................................................8-64
Info Events .............................................................................................................8-65
Trace Events ..........................................................................................................8-88
Chapter 9
Event Messages (SYNC through XNS)
SYNC Events ..................................................................................................................9-1
Fault Event ...............................................................................................................9-1
Warning Events ........................................................................................................9-2
Info Events .............................................................................................................9-13
SYS Events ..................................................................................................................9-17
Fault Event .............................................................................................................9-17
Warning Event ........................................................................................................9-17
Info Event ...............................................................................................................9-17
SYSLOG Events ...........................................................................................................9-18
Fault Event .............................................................................................................9-18
Info Events .............................................................................................................9-18
T1 Events .....................................................................................................................9-19
Fault Event .............................................................................................................9-19
Warning Events ......................................................................................................9-20
Info Events .............................................................................................................9-21
xvi
114082 Rev. A
Page 17
TBL Events ...................................................................................................................9-24
Fault Event .............................................................................................................9-24
TCP Events ..................................................................................................................9-25
Fault Event .............................................................................................................9-25
Info Events .............................................................................................................9-25
TELNET Events ............................................................................................................9-31
Fault Event .............................................................................................................9-31
Warning Event ........................................................................................................9-32
Info Events .............................................................................................................9-32
Trace Events ..........................................................................................................9-34
TF Events .....................................................................................................................9-35
Info Events .............................................................................................................9-35
TFTP Events .................................................................................................................9-36
Fault Event .............................................................................................................9-36
Warning Event ........................................................................................................9-37
Info Event ...............................................................................................................9-38
Trace Events ..........................................................................................................9-38
Technician Interface Events ..........................................................................................9-40
Fault Event .............................................................................................................9-40
Warning Events ......................................................................................................9-40
Info Events .............................................................................................................9-41
TI_RUI Events ..............................................................................................................9-42
Fault Event .............................................................................................................9-42
Warning Events ......................................................................................................9-42
Info Event ...............................................................................................................9-43
Trace Event ............................................................................................................9-43
TNC Events ..................................................................................................................9-43
Fault Events ...........................................................................................................9-44
Warning Events ......................................................................................................9-45
Info Events .............................................................................................................9-45
TOKEN_RING Events ..................................................................................................9-46
Fault Event .............................................................................................................9-47
Warning Events ......................................................................................................9-47
Info Events .............................................................................................................9-50
TTY Events ...................................................................................................................9-53
114082 Rev. A
xvii
Page 18
Fault Event .............................................................................................................9-53
Warning Events ......................................................................................................9-53
Info Events .............................................................................................................9-55
VINES Events ...............................................................................................................9-55
Fault Event .............................................................................................................9-56
Warning Event ........................................................................................................9-56
Info Events .............................................................................................................9-56
Trace Events ..........................................................................................................9-59
X25 Events ...................................................................................................................9-60
Fault Event .............................................................................................................9-60
Warning Events ......................................................................................................9-61
Info Events .............................................................................................................9-64
XMODEM Events .........................................................................................................9-67
Fault Event .............................................................................................................9-67
Info Event ...............................................................................................................9-67
XNS Events ..................................................................................................................9-67
Fault Event .............................................................................................................9-68
Warning Event ........................................................................................................9-68
Info Events .............................................................................................................9-68
Trace Events ..........................................................................................................9-71
xviii
114082 Rev. A
Page 19
Figures
Figure 1-1. Sample SNMP Trap ..................................................................................1-9
Figure 1-2. Trap Representation .................................................................................1-9
114082 Rev. A
xix
Page 20
Page 21
Tables
Table 1-1. Event Message Format ............................................................................1-2
Table 1-2. Entities .....................................................................................................1-4
Table 1-3. Severity Levels .........................................................................................1-8
114082 Rev. A
xxi
Page 22
Page 23
About This Guide
If you are an experienced network administrator responsible for operating and
managing Bay Networks™ routers or the Bay Networks Backbone Node Switch
(BNX
®
) software, use this guide. It describes how to use event messages to
determine the status of your router or BNX platform.
Event Messages for Routers and BNX Platforms offers
Page 24
Event Messages for Routers and BNX Platforms
• The
Availability of features and functionality described in this guide depends on the
suites you are using.
BNX Suite
PPP, OSPF, EGP, BGP, File-Based Performance Statistics, Frame Relay
switching, and Frame Relay billing, and selected components from the
Corporate, ARE A TM, and ARE VNR Corporate suites.
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
If you use Technician Interface, see
information on viewing Bay Networks event messages.
includes IP Routing, SNMP Agent, Bay Networks HDLC,
Managing Routers and BNX Platforms
Using Technician Interface Software
.
for
Conventions
This section describes the conventions used in this guide.
angle brackets (< >) Indicate that you choose the text to enter based on the
xxiv
description inside the brackets. Do not type the
brackets when entering the command. Example: if
ping
command syntax is
192.32.10.12
<ip_address>
, you enter
114082 Rev. A
ping
Page 25
.
About This Guide
bold text
Indicates text that you need to enter, command names,
and buttons in menu paths.
Example: Enter
Example: Use the
Example: ATM DXI > Interfaces >
wfsm &
dinfo
command.
PVCs
identifies the
PVCs button in the window that appears when you
select the Interfaces option from the ATM DXI menu.
brackets ([ ]) Indicate optional elements. You can choose none, one,
or all of the options.
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 points Horizontal (. . .) and vertical ellipsis 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
114082 Rev. A
nets
|
, you enter either
show at nets
or
, but not both.
xxv
Page 26
Event Messages for Routers and BNX Platforms
Acronyms
AARP AppleTalk Address Resolution Protocol
ACE Advanced Communications Engine
ACK acknowledgment
AIS Alarm Indication Signal
AMI Address Mark Inversion
ANI Automatic Number Identification
ARP Address Resolution Protocol
AS Autonomous System
ASN Access Stack Node
ATM Asynchronous Transfer Mode
AURP AppleTalk Update-based Routing Protocol
B8ZS Binary Eight Zeros Suppression
BCN Backbone Concentrator Node
xxvi
BDR Backup Designated Router
BGP Border Gateway Protocol
BOFL Breath of Life
BOD bandwidth on demand
BOOTP Bootstrap Protocol
BPDU Bridge Protocol Data Unit
CA Communications Equipment Available
CCITT Consultative Committee on International Telegraph and
T elephone
CIC Connect Incoming Call
CIS Card Information Structure
CN Concentrator Node
COM communications port
CPE customer premises equipment
114082 Rev. A
Page 27
About This Guide
CPU Central Processing Unit
CRN Call Request with Number
CRS Configuration Report Server
CSMA/CD Carrier Sense Multiple Access/Carrier Detect
CSU/DSU Channel Service Unit/Data Service Unit
CTS Clear To Send
DCE Data Communications Equipment
DDN/PDN Defense Data Network/Public Data Network
DIC Disconnect Incoming Call
DLCI Data Link Connection Identifier
DLCMI Data Link Control Management Interface
DLS See DLSw
DLSw Data Link Switching
DMAP Direct Memory Access Processor
114082 Rev. A
DNIS Dialed Number Identification Service
DOS Disk Operating System
DP Data Path
DR Designated Router
DS1E1 Multichannel T1/E1
DSR Data Set Ready
DTE Data Terminal Equipment
DTR Data T erminal Ready
DUART Dual Universal Asynchronous Receiver/Transmitter
DXI Data Exchange Interface
EGP Exterior Gateway Protocol
FDDI Fiber Distributed Data Interface
FDL Facility Data Link
FIFO First-In-First-Out
xxvii
Page 28
Event Messages for Routers and BNX Platforms
FLOP Floppy Disk Controller
FN Feeder Node
FR Frame Relay
FRE Fast Routing Engine
FS file system
GAME Gate Access Management Entity
GFS generic file system
HIMIB Hardware Implemented MIB
HSN History Serial Number
HSSI High Speed Serial Interface
HUB Access Node Repeater
HWF Hardware Filter
IE information element
IHU I hear you
xxviii
I/O input/output
IDMA Independent Direct-Memory Access
IMR Integrated Multiport Repeater
IP Internet Protocol
IPSO See RIPSO
IPEX Internet Protocol over X.25
IPX Internet Packet Exchange
ISDN Integrated Services Digital Network
IS-IS Intermediate System to Intermediate System
ISO International Organization for Standardization
LAN local area network
LAPB Link Access Procedure Balanced
LB Learning Bridge
LCP Link Control Protocol
114082 Rev. A
Page 29
About This Guide
LCT Link Confidence Test
LED Light-Emitting Diode
LEM Link Error Monitor
LER link error rate
LL low level
LLC Logical Link Control
LMI Local Management Interface
LN Link Node
LNM LAN Network Manager
LOADER Dynamic Loader
LOF Loss of Frame
LOS Loss of Signal
LQR Link Quality Report
MAC media access control
114082 Rev. A
MAU Media Attachment Unit
MCT1 Multichannel T1
MIB Management Information Base
MIR Maximum Information Rate
MODEMIF Modem Interface
MTU Maximum Transfer Unit
NANP North American Numbering Plan
NAK negative acknowledgment
NBMA Non-Broadcast Multi-Access
NCP Network Control Program
NetBIOS Network Basic Input-Output System
NMI non-maskable interrupt
NML Native Mode LAN
NIC Network Information Center
xxix
Page 30
Event Messages for Routers and BNX Platforms
NOVRAM Non-Volatile Random Access Memory
NOV_SYNC Non-Volatile Synchronization
NTP Network Time Protocol
NVFS Non-Volatile File System
OOF Out-Of-Frame
OSI Open Systems Interconnection
OSPF Open Shortest Path First
OUI organizationally unique identifier
P AM Physical Access Method
P AP Password Authentication Protocol
PC physical connection
PCAP Packet Capture
PCM Physical Connection Management
PCMCIA Personal Computer Memory Card International
Association
xxx
PDU protocol data unit
PHY Physical Level
PLCP Physical Layer Convergence Protocol
PPP Point-to-Point Protocol
PPX Parallel Packet Express
PROM Programmable Read-Only Memory
PTY pseudo teletypewriter
PVC permanent virtual circuit
QENET Quad Ethernet
RARP Reverse Address Resolution Protocol
RAI Remote Alarm Indication
RAM Random Access Memory
REM Ring Error Monitor
114082 Rev. A
Page 31
About This Guide
RI routing information
RIF routing information field
RIP Routing Information Protocol
RIPSO Revised IP Security Option
RPC remote procedure call
RPS Ring Parameter Server
RTC Real Time Clock
RTMP Routing Table Maintenance Protocol
RUI Remote User Interface
SAP Service Access Point
SIP SMDS Interface Protocol
SMDS Switched Multimegabit Data Services
SMT Station Management
SNAP Subnetwork Access Protocol
114082 Rev. A
SNI Subscriber Network Interface
SNMP Simple Network Management Protocol
SPAN Spanning Tree
SQE Signal Quality Error
SR Source Routing
SRAM Static Random Access Memory
SRM Systems Resource Module
SRT Source Routing Transparent
SSI SMDS-to-Access Server Interface
STA Statistical Thresholds and Alarms
SWSER V Switched Access Services
SYNC Synchronous
SYS system
TBL table
xxxi
Page 32
Event Messages for Routers and BNX Platforms
TCP Transmission Control Protocol
TELNET Telnet Server
TF traffic filter
TFTP Trivial File Transfer Protocol
TI_RUI Technician Interface/Remote User Interface
TNC Telnet Client
TTRT Target Token Rotation Time
TTY teletypewriter
UNI User Network Interface
VC virtual circuit
VINES Virtual Networking System
WAN wide area network
VBR Variable Bit Rate
VCI virtual circuit interface
VPI virtual path interface
XMODEM Xmodem/Ymodem
XNS Xerox Network Systems
ZIP Zone Information Protocol
XCVR (Ethernet) Transceiv er
Ordering Bay Networks Publications
To purchase additional copies of this document or other Bay Networks
publications, order by part number from the Bay Networks Press
following telephone or fax numbers:
• Telephone - U.S./Canada 1-888-4BAYPRESS
• Telephone - International 1-510-490-4752
• Fax 1-510-498-2609
You can also use these numbers to request a free catalog of Bay Networks Press
product publications.
xxxii
™
at the
114082 Rev. A
Page 33
Technical Support and Online Services
To ensure comprehensive network support to our customers and partners
worldwide, Bay Networks Customer Service has Technical Response Centers
in key locations around the globe:
• Billerica, Massachusetts
• Santa Clara, California
• Sydne y , Australia
• Tokyo, Japan
• Valbonne, France
114082 Rev. A
The Technical Response Centers are connected via a redundant Frame Relay
Network to a Common Problem Resolution system, enabling them to transmit and
share information, and to provide live, around-the-clock support 365 days a year.
Bay Networks Information Services complement the Bay Networks Service
program portfolio by giving customers and partners access to the most current
technical and support information through a choice of access/retrieval means.
These include the World W ide Web, CompuServ e, Support Source CD, Customer
Support FTP, and InfoFACTS document fax service.
xxxiii
Page 34
Event Messages for Routers and BNX Platforms
Bay Networks Customer Service
If you purchased your Bay Networks product from a distributor or authorized
reseller, contact that distributor’s or reseller’s technical support staf f for assistance
with installation, configuration, troubleshooting, or integration issues.
Customers can also purchase direct support from Bay Networks through a variety
of service programs. As part of our PhonePlus™ program, Bay Netw orks Service
sets the industry standard, with 24-hour, 7-days-a-week telephone support
available worldwide at no extra cost. Our complete range of contract and
noncontract services also includes equipment staging and integration, installation
support, on-site services, and replacement parts delivery -- within approximately
4 hours.
To purchase any of the Bay Networks support programs, or if you have questions
on program features, use the following numbers:
Region Telephone Number Fax Number
United States and
Canada
1-800-2LANWAN; enter Express Routing
Code (ERC) 290 when prompted
(508) 670-8766
xxxiv
(508) 436-8880 (direct)
Europe (33) 92-968-300 (33) 92-968-301
Asia/Pacific Region (612) 9927-8800 (612) 9927-8811
Latin America (407) 997-1713 (407) 997-1714
In addition, you can receive information on support programs from your local
Bay Networks field sales office, or purchase Bay Networks support directly
from your authorized partner.
114082 Rev. A
Page 35
Bay Networks Information Services
Bay Networks Information Services provide up-to-date support information as a
first-line resource for network administration, expansion, and maintenance. This
information is available from a variety of sources.
W orld Wide Web
The Bay Networks Customer Support Web Server offers a diverse library of
technical documents, software agents, and other important technical information
to Bay Networks customers and partners.
A special benefit for contracted customers and resellers is the ability to access the
Web Server to perform Case Management. This feature enables your support staff
to interact directly with the network experts in our worldwide Technical Response
Centers. A registered contact with a valid Site ID can
• View a listing of support cases and determine the current status of any open
case. Case history data includes severity designation, and telephone, e-mail,
or other logs associated with the case.
Technical Support and Online Services
• Customize the listing of cases according to a variety of criteria, including
date, severity, status, and case ID.
• Log notes to existing open cases.
• Create new cases for rapid, efficient handling of noncritical network
situations.
• Communicate directly via e-mail with the specific technical resources
assigned to your case.
The Bay Networks URL is http://www.baynetworks.com. Customer Service is a
menu item on that home page.
Customer Service FTP
Accessible via URL ftp://support.baynetworks.com (134.177.3.26), this site
combines and organizes support files and documentation from across the
Bay Networks product suite, including switching products from our Centillion™
®
and Xylogics
site lets you quickly locate information on any of your Bay Networks products.
114082 Rev. A xxxv
business units. Central management and sponsorship of this FTP
Page 36
Event Messages for Routers and BNX Platforms
Support Source CD
This CD-ROM -- sent quarterly to all contracted customers -- is a complete Bay
Networks Service troubleshooting knowledge database with an intelligent text
search engine.
The Support Source CD contains extracts from our problem-tracking database;
information from the Bay Networks Forum on CompuServe; comprehensive
technical documentation, such as Customer Support Bulletins, Release Notes,
software patches and fixes; and complete information on all Bay Networks
Service programs.
You can run a single version on Macintosh Windows 3.1, Windows 95,
Windows NT, DOS, or UNIX computing platforms. A Web links feature enables
you to go directly from the CD to various Bay Networks Web pages.
CompuServe
For assistance with noncritical network support issues, Bay Networks Information
Services maintain an active forum on CompuServe, a global bulletin-board
system. This forum provides file services, technology conferences, and a message
section to get assistance from other users.
The message section is monitored by Bay Networks engineers, who provide
assistance wherever possible. Customers and resellers holding Bay Networks
service contracts also have access to special libraries for advanced levels of
support documentation and software. To take advantage of CompuServe’ s recently
enhanced menu options, the Bay Networks Forum has been re-engineered to allow
links to our Web sites and FTP sites.
We recommend the use of CompuServe Information Manager software to access
these Bay Networks Information Services resources. To open an account and
receive a local dial-up number in the United States, call CompuServe at
1-800-524-3388. Outside of the United States, call 1-614-529-1349, or your
nearest CompuServe office. Ask for Representative No. 591. When you’re on line
with your CompuServe account, you can reach us with the command GO
BAYNET.
xxxvi 114082 Rev. A
Page 37
InfoFACTS
InfoFACTS is the Bay Networks free 24-hour fax-on-demand service. This
automated system has libraries of technical and product documents designed to
help you manage and troubleshoot your Bay Networks products. The system
responds to a fax from the caller or to a third party within minutes of being
accessed.
To use InfoFACTS in the United States or Canada, call toll-free 1-800-786-3228.
Outside of North America, toll calls can be made to 1-408-764-1002. In Europe,
toll-free numbers are also available for contacting both InfoFACTS and
CompuServe. Please check our Web page for the listing in your country.
How to Get Help
Use the following numbers to reach your Bay Networks Technical Response
Center:
Technical Response Center Telephone Number Fax Number
Billerica, MA 1-800-2LANWAN (508) 670-8765
Santa Clara, CA 1-800-2LANWAN (408) 764-1188
Valbonne, France (33) 92-968-968 (33) 92-966-998
Sydney, Australia (612) 9927-8800 (612) 9927-8811
Tokyo, Japan (81) 3-5402-0180 (81) 3-5402-0173
Technical Support and Online Services
114082 Rev. A xxxvii
Page 38
Page 39
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 or BNX.
The router or BNX stores the event as a single entry in a memory-resident log.
A trap is simply an event that the router or BNX 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.
114082 Rev. A 1-1
Page 40
Event Messages for Routers and BNX Platforms
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 Managing Routers and BNX Platforms. 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 Table 1-1
shows.
Table 1-1. Event Message Format
Entry Description
Entity Code/Event
Code
Decimal Identifier The decimal equivalent of the 32-bit SNMP trap that the router or
Severity Fault, Warning, Information, or Trace.
Message Text displayed in event log.
Meaning Clarification of event message.
Action Recommended user response to event (if necessary).
1-2 114082 Rev. A
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 or BNX platform event.
BNX platform transmits. Network management applications use
this decimal identifier.
Page 41
Entities
Overview
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. Table 1-2 lists the entities (both their abbreviations and full names) and
associated entity codes.
114082 Rev. A 1-3
Page 42
Event Messages for Routers and BNX Platforms
Table 1-2. Entities
Entity Description Code
ACE Advanced Communications Engine board 10
APPLETALK AppleTalk protocol 36
APPN Advanced Peer-to-Peer Networking protocol 86
ARP Address Resolution Protocol 19
A TM Asynchronous Transfer Mode 78
ATM_DXI Asynchronous Transfer Mode/Data Exchange
Interface protocol
ATM_LE Asynchronous Transfer Mode LAN Emulation service 100
ATM_SIG Asynchronous Transfer Mode Signaling service 95
ATMINTF Asynchronous Transfer Mode Interface service 76
BGP Border Gateway protocol 52
BGP3 Border Gateway protocol Version 3 53
BGP4 Border Gateway protocol Version 4 72
BISYNC Bisynchronous over TCP/IP (BOT) protocol 105
BOD Bandwidth on Demand: dial backup and
dial-on-demand services
BOOT Router boot operation 22
BOOTP Bootstrap protocol 59
BTS Binary Synchronous Communication Transport service 104
CDM Configuration Database Manager 103
CRM Circuit Resource Manager service 91
CSMACD Carrier Sense Multiple Access/ Carrier Detect
(Ethernet) driver
DCMMW Data Collection Module Middleware 96
DECNET DECnet IV protocol 4
DLS Data Link Switching (DLSw) protocol 50
DMAP Direct Memory Access processor 39
DOS Disk Operating System 28
DP Data Path service 6
49
54
9
(continued)
1-4 114082 Rev. A
Page 43
Overview
Table 1-2. Entities
Entity Description Code
DS1E1 Multichannel T1/E1 63
DVMRP Distance Vector Multicast Routing Protocol (refers to FTP
service)
E1 E1 driver 35
EGP Exterior Gateway protocol 46
FDDI Fiber Distributed Data Interface driver 8
FLOP Floppy disk controller 32
FR Frame Relay protocol 25
FRSW Frame Relay Switch service 65
FRSW_BILLING Frame Relay Switch billing 66
FRSW_ISDN Frame Relay Switch ISDN service 107
FS File System 64
FTP FTP service (referred to as the DVMRP entity) 88
GAME Gate Access Management Entity 5
GFS Generic File System 33
HSSI High Speed Serial Interface driver 27
HUB Access Node repeater 71
HWCOMP Hardware Compression driver 99
HWF Hardware Filter 37
IGMP IGMP service 83
IP Internet protocol 2
IPEX IP Encapsulation on X.25 93
IPX Internet Packet Exchange protocol 30
ISDN ISDN service 79
ISDN_BRI ISDN BRI driver service 80
LAPB Link Access Procedure Balanced 73
LB Learning Bridge protocol 1
LLC Logical Link Control protocol 48
LNM LAN Network Manager protocol 51
LOADER Dynamic loader 55
(continued)
88
(continued)
114082 Rev. A 1-5
Page 44
Event Messages for Routers and BNX Platforms
Table 1-2. Entities
Entity Description Code
MCT1 Multichannel T1 67
MIB Management Information Base 13
MODEMIF Modem Interface 57
MODULE Module driver 21
NBASE NBASE 75
NBIP NetBIOS over IP service 77
NLSP Network Link State Protocol 97
NML Native Mode LAN 1
NOV_SYNC Non-Volatile memory Synchronization 61
NTP Network Time Protocol 109
NVFS Non-Volatile File System 11
OSI Open Systems Interconnection protocol 38
OSPF Open Shortest Path First 12
PCAP Packet Capture 62
PING PING MIB 85
PPP Point-to-Point Protocol 44
PPRI Protocol Priority service 90
PTY Pseudo TTY driver 41
RARP Reverse Address Resolution Protocol 45
RREDUND Router Redundance service 98
RUIBOOT Remote User Interface Boot 102
SDLC Synchronous Data Link Control 74
SMDS Switched Multimegabit Data Service 24
SMDS_SW SMDS Switch 68
SMDS_BILLING SMDS Switch billing 69
SNMP Simple Network Management Protocol 3
SP AN Spanning T ree protocol 16
SR Source Routing Bridge protocol 29
ST2 ST2 service 94
(continued)
(continued)
1-6 114082 Rev. A
Page 45
Overview
Table 1-2. Entities
Entity Description Code
STA Statistical thresholds and alarms 56
STATS Statistical data collection 92
SWSERV Switched access service 58
SYNC Synchronous driver 20
SYS System record 60
SYSLOG System log 89
T1 T1 driver 34
TBL Routing table 14
TCP Transmission Control Protocol 47
TELNET Telnet server protocol 40
TF Traffic Filter 15
TFTP Trivial File Transfer Protocol 7
TI Bay Networks Technician Interface 0
TI_RUI Technician Interface/Remote User Interface (Site
Manager)
TNC Telnet Client protocol 70
TOKEN_RING Token Ring driver 26
TTY Teletypewriter 17
VINES Virtual Networking System protocol 23
WCP Data compression 84
X25 X.25 protocol 43
XMODEM Xmodem/Ymodem protocol 42
XNS Xerox Networking Systems protocol 31
(continued)
18
Severity Levels
Event and trap messages are always associated with one of five severity levels.
Table 1-3 describes the severity levels and lists the code that corresponds to each
one. This guide does not cover Debug messages, because these are for Bay
Networks internal use only.
114082 Rev. A 1-7
Page 46
Event Messages for Routers and BNX Platforms
Table 1-3. Severity Levels
Severity Description Code
Fault Indicates a major service disruption. A configuration, network,
Warning Indicates that a service acted in an unexpected manner. 4
Information Indicates routine events. Usually no action is required. 2
Trace Indicates information about each packet that traversed the
Debug Indicates information that Bay Networks Customer Support
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 or BNX 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.
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.
• Octet 3 contains a code value that identifies the software entity that generated
the trap. Table 1-2, shown earlier, lists software entities and their associated
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 event
string that describes the trap condition, the slot that hosts the entity that generated
the trap, and the trap severity as listed earlier in Table 1-3.
For example, the following event issued by the HSSI entity may be configured as
an SNMP trap:
1-8 114082 Rev. A
Page 47
Entity Code/Event Code 27/2
Severity: Warning
Message: Connector HSSI <connector_number> transmitter time-out.
Figure 1-1 shows the 32-bit portion of the trap as transmitted by the router or
BNX platform:
Bay Networks
specific Software event
Overview
01 00
27 02
EV0001A
Figure 1-1. Sample SNMP Trap
• Octets 1 and 2 identify a Bay Networks enterprise-specific trap.
• Octet 3 identifies the software entity that generated the trap.
• Octet 4 identifies the event.
Reference to the HSSI section of this directory finds the same trap listed as
16784130, a decimal value that network management applications use.
Figure 1-2 illustrates the equivalence of the two values.
16,784,13010 = 00000001 00000000 00011011 00000010
00000001 00011011 0000001000000000
2
01 00 27 02
EV0002A
Figure 1-2. Trap Representation
114082 Rev. A 1-9
Page 48
Page 49
Chapter 2
Event Messages (ACE through ATMINTF)
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.
Fault Events
Entity Code/Event Code 10/2
Decimal Identifier 16779778
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 Response Center if this condition persists.
114082 Rev. A 2-1
Page 50
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 10/3
Decimal Identifier 16779779
Severity: Fault
Message: ACE hardware diagnostic: NMI: AC power failure
Meaning: A lower power condition is detected.
Action: Contact the Bay Networks Technical Response Center if this condition persists.
Entity Code/Event Code 10/4
Decimal Identifier 16779780
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.
Entity Code/Event Code 10/5
Decimal Identifier 16779781
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.
Entity Code/Event Code 10/6
Decimal Identifier 16779782
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 Response Center if this condition persists.
2-2 114082 Rev. A
Page 51
Event Messages (ACE through ATMINTF)
Warning Events
Entity Code/Event Code 10/1
Decimal Identifier 16779777
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 Response Center if there are multiple occurrences of
this event.
Entity Code/Event Code 10/7
Decimal Identifier 16779783
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.
APPLETALK Events
The AppleTalk service, referred to as the APPLETALK entity, issues the
following ev ent messages. The entity code assigned to APPLET ALK events is 36.
Fault Event
Entity Code/Event Code 36/1
Decimal Identifier 16786433
Severity: Fault
Message: AppleTalk Error: <fatal_error_message>
Meaning: The router experienced a fatal error <fatal_error_message> and is restarting
automatically. The router will attempt to restart up to five times.
Action: Verify that the configuration is correct. Call the Bay Networks T echnical Response Center
if the router fails to restart.
114082 Rev. A 2-3
Page 52
Event Messages for Routers and BNX Platforms
Warning Events
Entity Code/Event Code 36/14
Decimal Identifier 16786446
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.
Entity Code/Event Code 36/15
Decimal Identifier 16786447
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
parameters, then re-enable the interface.
Entity Code/Event Code 36/16
Decimal Identifier 16786448
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
interface.
router’s Network Start and Network End
Entity Code/Event Code 36/17
Decimal Identifier 16786449
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.
2-4 114082 Rev. A
Page 53
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 36/18
Decimal Identifier 16786450
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.
Entity Code/Event Code 36/19
Decimal Identifier 16786451
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.>.
Entity Code/Event Code 36/20
Decimal Identifier 16786452
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.
Entity Code/Event Code 36/21
Decimal Identifier 16786453
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.
114082 Rev. A 2-5
Page 54
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 36/22
Decimal Identifier 16786454
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.
Entity Code/Event Code 36/23
Decimal Identifier 16786455
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.
Entity Code/Event Code 36/24
Decimal Identifier 16786456
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.
Entity Code/Event Code 36/25
Decimal Identifier 16786457
Severity: Warning
Message: Couldn’t add default zone
Meaning: The router could not add the default zone specified for this network to its zone list. This
could be caused by lack of memory on the slot.
2-6 114082 Rev. A
Page 55
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 36/26
Decimal Identifier 16786458
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
configured on this network.
Entity Code/Event Code 36/27
Decimal Identifier 16786459
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.
Action: Re-enable the AppleTalk interface.
Entity Code/Event Code 36/28
Decimal Identifier 16786460
Severity: Warning
Message: Local net range conflict
Meaning: The network range assigned to this router is different from the network range assigned to
other routers on the network.
Action: Check the configuration of this router and reconfigure if necessary.
Entity Code/Event Code 36/29
Decimal Identifier 16786461
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.
114082 Rev. A 2-7
Page 56
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 36/30
Decimal Identifier 16786462
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.
Entity Code/Event Code 36/31
Decimal Identifier 16786463
Severity: Warning
Message: Bad net range <network_start_no.> -- <network_end_no.> from
<network_ID>.<node_ID>
Meaning: The router received an RTMP packet from the router <network_ID>.<node_ID> that
contained an illegal network range.
Action: Check the configuration of the originating router.
Entity Code/Event Code 36/32
Decimal Identifier 16786464
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.
Entity Code/Event Code 36/33
Decimal Identifier 16786465
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.
2-8 114082 Rev. A
Page 57
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 36/34
Decimal Identifier 16786466
Severity: Warning
Message: Range overlap <network_start_no.> -- <network_end_no.> from
<network_ID>.<node_ID>
Meaning: The router received an RTMP packet from the router <network_ID>.<node_ID>
containing a network range <network_start_no.> -- <network_end_no.> that overlapped
with an existing network range.
Action: Check the configuration of the originating router.
Entity Code/Event Code 36/35
Decimal Identifier 16786467
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.
Entity Code/Event Code 36/36
Decimal Identifier 16786468
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.
Entity Code/Event Code 36/37
Decimal Identifier 16786469
Severity: Warning
Message: A zip reply had a net number <network_ID> not found in rtmp table on circuit
<circuit_no.>
Meaning: The router received a ZIP reply containing a network number <network_ID> that is not
present in the router’s RTMP table for this interface. This could occur if the network is
unstable.
114082 Rev. A 2-9
Page 58
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 36/38
Decimal Identifier 16786470
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.
Entity Code/Event Code 36/39
Decimal Identifier 16786471
Severity: Warning
Message: Default zone -- seed conflict
Meaning: When the AppleTalk interface was initialized, a seed router was configured with a default
zone that was different than the default zone configured for other routers.
Action: Check the configuration of the seed routers on the network.
Entity Code/Event Code 36/40
Decimal Identifier 16786472
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.
Entity Code/Event Code 36/41
Decimal Identifier 16786473
Severity: Warning
Message: Zone name conflict
Meaning: When the AppleTalk interface was initialized, a seed router found a zone name in a ZIP
reply that was not on its local zone list.
Action: Check the configuration of the seed routers on the network.
2-10 114082 Rev. A
Page 59
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 36/42
Decimal Identifier 16786474
Severity: Warning
Message: Bad zip reply
Meaning: The AppleTalk interface received a malformed ZIP reply packet.
Entity Code/Event Code 36/44
Decimal Identifier 16786476
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.
Entity Code/Event Code 36/45
Decimal Identifier 16786477
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.
Entity Code/Event Code 36/46
Decimal Identifier 16786478
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.
114082 Rev. A 2-11
Page 60
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 36/47
Decimal Identifier 16786479
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.
Entity Code/Event Code 36/48
Decimal Identifier 16786480
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.
Action: Delete all other zones for this interface.
Entity Code/Event Code 36/49
Decimal Identifier 16786481
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.
Entity Code/Event Code 36/50
Decimal Identifier 16786482
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.
2-12 114082 Rev. A
Page 61
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 36/51
Decimal Identifier 16786483
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
WAN protocol.
Action: Reconfigure the interface.
Entity Code/Event Code 36/52
Decimal Identifier 16786484
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.
Entity Code/Event Code 36/61
Decimal Identifier 16786493
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.
Entity Code/Event Code 36/62
Decimal Identifier 16786494
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.
114082 Rev. A 2-13
Page 62
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 36/63
Decimal Identifier 16786495
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.
Entity Code/Event Code 36/64
Decimal Identifier 16786496
Severity: Warning
Message: A ZI-Rsp had a net number<network_ID> not found in rtmp table on connection
<connection_no.>
Meaning: The router received a ZI-Response from router peer <IP_address> containing a network
number <network_ID> that is not present in the router’s routing table.
Entity Code/Event Code 36/65
Decimal Identifier 16786497
Severity: Warning
Message: Update <update_type> for network <network_start_no.> -- <network_end_no.> not sent
on connection <IP_address>: overlaps existing update <update_type> for network
<network_start_no.> -- <network_end_no.>.
Meaning: An event occurred in the router’s local internet that would have caused it to send update
tuples that overlapped. The overlapping update is not sent.
Action: Restart the AURP connection (disable, then enable the connection) to send the ignored
update’s network information.
2-14 114082 Rev. A
Page 63
Event Messages (ACE through ATMINTF)
Info Events
Entity Code/Event Code 36/2
Decimal Identifier 16786434
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>.
Entity Code/Event Code 36/3
Decimal Identifier 16786435
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>.
Entity Code/Event Code 36/4
Decimal Identifier 16786436
Severity: Info
Message: Protocol initializing
Meaning: The router is initializing AppleTalk routing.
Entity Code/Event Code 36/5
Decimal Identifier 16786437
Severity: Info
Message: Protocol terminating
Meaning: The router is terminating AppleTalk routing.
Entity Code/Event Code 36/53
Decimal Identifier 16786485
Severity: Info
Message: AURP initializing
Meaning: The router is initializing AppleTalk AURP support.
114082 Rev. A 2-15
Page 64
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 36/54
Decimal Identifier 16786486
Severity: Info
Message: AURP terminating
Meaning: The router is terminating AppleTalk AURP support.
Entity Code/Event Code 36/55
Decimal Identifier 16786487
Severity: Info
Message: AURP Connection opened <IP_address>
Meaning: The router has successfully opened the connection to the specified peer.
Entity Code/Event Code 36/56
Decimal Identifier 16786488
Severity: Info
Message: AURP Connection closed <IP_address>
Meaning: The router has closed the connection to the specified peer.
Entity Code/Event Code 36/57
Decimal Identifier 16786489
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
and number of retries have been exceeded.
Entity Code/Event Code 36/58
Decimal Identifier 16786490
Severity: Info
Message: AURP Connection closed by peer <IP_address>
Meaning: The peer external router <IP_address> has closed the AURP connection between itself
and the local router.
2-16 114082 Rev. A
Page 65
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 36/59
Decimal Identifier 16786491
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.
Entity Code/Event Code 36/60
Decimal Identifier 16786492
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.
Error Code Error
-1 Normal connection clode
-2 Routing loop detected
-3 Connection out of sync
-4 Option-negotiation error
-5 Invalid version number
-6 Insufficient resources for connection
-7 Authentication error
Trace Events
Entity Code/Event Code 36/6
Decimal Identifier 16786438
Severity: Trace
Message: AARP: node <network_ID>.<node_ID> added
Meaning: The router added the node whose address is <network_ID>.<node_ID> to its AARP
table.
114082 Rev. A 2-17
Page 66
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 36/7
Decimal Identifier 16786439
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
table.
Entity Code/Event Code 36/8
Decimal Identifier 16786440
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
table.
Entity Code/Event Code 36/9
Decimal Identifier 16786441
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
RTMP table.
Entity Code/Event Code 36/10
Decimal Identifier 16786442
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
its forwarding table.
Entity Code/Event Code 36/11
Decimal Identifier 16786443
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>
from its forwarding table.
2-18 114082 Rev. A
Page 67
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 36/12
Decimal Identifier 16786444
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.
Entity Code/Event Code 36/13
Decimal Identifier 16786445
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.
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
86.
Fault Event
Entity Code/Event Code 86/1
Decimal Identifier 16799233
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 Response Center if this condition persists.
114082 Rev. A 2-19
Page 68
Event Messages for Routers and BNX Platforms
Warning Events
Entity Code/Event Code 86/2
Decimal Identifier 16799234
Severity: Warning
Message: LU 6.2 received negative BIND response: Mode= <mode_name>, Sense = <sense_data>,
Sending CP name = <CP_name>, Sending LU name = <LU_name>, Partner LU name =
<LU_name>.
Meaning: A partner LU that supports only nonextended BINDs detected an error causing it to send
an -RSP (BIND). The LU receiving the -RSP (BIND) generates this message.
Action: Review the associated resources and check the communications program in both the local
and remote nodes.
Entity Code/Event Code 86/3
Decimal Identifier 16799235
Severity: Warning
Message: LU 6.2 sent negative BIND response: Mode= <mode_name>, Sense = <sense_data>,
Sending CP name = <CP_name>, Sending LU name = <LU_name>, Partner LU name =
<LU_name>.
Meaning: An LU detected an error, causing it to send an -RSP(BIND) response to its partner LU.
The SNA <sense_data> denotes the exact error condition detected.
Action: Review the associated resources and check the communications program in both the local
and remote nodes.
Entity Code/Event Code 86/4
Decimal Identifier 16799236
Severity: Warning
Message: LU 6.2 session activation rejected: Mode= <mode _name>, Sense = <sense_data>,
Sending CP name = <CP_name>, Sending LU name = <LU_name>, Partner LU name =
<LU_name>.
Meaning: The CP has rejected the LU’s request for assistance in the initiation of a session. The
session manager informs the resource manager that the session activation has failed. The
SNA <sense_data> denotes the exact error condition detected.
Action: Review the associated resources and check the communications program.
2-20 114082 Rev. A
Page 69
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/5
Decimal Identifier 16799237
Severity: Warning
Message: LU 6.2 UNBIND request sent: Mode= <mode_name>, Sense = <sense_data>, UNBIND
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
and remote nodes.
Entity Code/Event Code 86/6
Decimal Identifier 16799238
Severity: Warning
Message: LU 6.2 UNBIND request received: Mode= <mode_name>, Sense = <sense_data>,
UNBIND type = <type>, Sending CP name = <CP_name>, Sending LU name =
<LU_name>, Partner LU name = <LU_name>.
Meaning: The partner LU (which supports extended BINDs) rejected the BIND with an UNBIND.
The SNA <sense_data> denotes the exact error condition detected.
Action: Review the associated resources and check the communications program in both the local
and remote nodes.
Entity Code/Event Code 86/7
Decimal Identifier 16799239
Severity: Warning
Message: Session setup failure: Sense = <sense_data>, Alert code = <product alert reference
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
Technical Response Center for assistance.
114082 Rev. A 2-21
Page 70
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 86/8
Decimal Identifier 16799240
Severity: Warning
Message: Invalid XID received: Sense = <sense_data>, Alert code = <product alert reference
code>, Sending CP name = <CP_name>, Partner CP name = <CP_name>.
Meaning: XID negotiation was terminated by this node because the received XID was invalid in
format, or contained unacceptable values. The SN A <sense_data> denotes the e xact error
condition being reported.
Action: Check the communications program at the remote node.
Entity Code/Event Code 86/9
Decimal Identifier 16799241
Severity: Warning
Message: XID protocol error: Sense = <sense_data>, Alert code = <product alert reference code>,
Sending CP name = <CP_name>, Partner CP name = <CP_name>.
Meaning: XID negotiation was terminated by this node because the remote node violated protocols
for XID exchange. The SNA <sense_data> denotes the exact error condition being
reported.
Action: Check the communications program at the remote node.
Entity Code/Event Code 86/10
Decimal Identifier 16799243
Severity: Warning
Message: Incorrect Set Mode command received: Sense = <sense_data>, Alert code = <product
alert reference code>, Sending CP name = <CP_name>, Partner CP name =
<CP_name>.
Meaning: An invalid Set Mode (SM) was received. The SNA <sense_data> denotes the exact error
condition being reported.
Action: Check the communications program at the remote node.
2-22 114082 Rev. A
Page 71
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/11
Decimal Identifier 16799243
Severity: Warning
Message: XID negotiation terminated: Sense = <sense_data>, Alert code = <product alert
reference code>, Sending CP name = <CP_name>, Partner CP name = <CP_name>.
Meaning: XID negotiation was terminated by the remote node. An XID negotiation error control
vector (x’22’) was received. The SNA <sense_data> denotes the exact error condition
being reported.
Action: Check the communications program at both the local and remote nodes.
Entity Code/Event Code 86/12
Decimal Identifier 16799244
Severity: Warning
Message: Unable to communicate with remote node (XID failure): Sense = <sense_data>, Alert
code = <product alert reference code>, Sending CP name = <CP_name>, Partner CP
name = <CP_name>.
Meaning: XID negotiation was terminated by the alert sender because no response was receiv ed and
the XID retry limit was reached. The SNA <sense_data> denotes the exact error condition
being reported.
Action: Check the communications program and configuration at the remote node. Check the
network connections.
Entity Code/Event Code 86/13
Decimal Identifier 16799245
Severity: Warning
Message: Unable to communicate with remote node (DLC failure): Alert code = <product alert
reference code>, Sending CP name = <CP_name>.
Meaning: The communications program was abnormally terminated due to a failed DLC (interface)
or path control component.
Action: Check the communications program at the remote node. Check the network connections.
If the problem persists, contact the Bay Networks Technical Response Center.
114082 Rev. A 2-23
Page 72
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 86/14
Decimal Identifier 16799246
Severity: Warning
Message: XID negotiation terminated: Sense = <sense_data>, Alert code = <product alert
reference code>, Sending CP name = <CP_name>.
Meaning: XID negotiation was terminated because one or more resources were unavailable. The
SNA <sense_data> denotes the exact error condition being reported.
Action: Check the communications program, or contact the Bay Networks Technical Response
Center.
Entity Code/Event Code 86/15
Decimal Identifier 16799247
Severity: Warning
Message: CP-CP session failure: Sense = <sense_data>, Alert code = <product alert reference
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
Technical Response Center.
Entity Code/Event Code 86/16
Decimal Identifier 16799248
Severity: Warning
Message: Topology capacity exceeded: Alert code = <product alert reference code>, Maximum
entries = <number>, Sending CP name = <CP_name>.
Meaning: The node table is full. This condition is probably the result of a configuration error. The
TDU causing the condition is ignored.
Action: Check the configuration file for the maximum number of node and transmission group
(TG) entries in the topology database.
2-24 114082 Rev. A
Page 73
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/17
Decimal Identifier 16799249
Severity: Warning
Message: Topology protocol error: Alert code = <product alert reference code>, Resource name =
<resource_name>, Sending CP name = <CP_name>.
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.
Entity Code/Event Code 86/18
Decimal Identifier 16799250
Severity: Warning
Message: Directory services protocol error: Sense = <sense_data>, Alert code = <product alert
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
Technical Response Center.
Entity Code/Event Code 86/19
Decimal Identifier 16799251
Severity: Warning
Message: CP-CP session failure: Sense = <sense_data>, Alert code = <product alert reference
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
Technical Response Center.
114082 Rev. A 2-25
Page 74
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 86/20
Decimal Identifier 16799252
Severity: Warning
Message: Unauthorized network change attempted: Sense = <sense_data>, Alert code = <product
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.
Entity Code/Event Code 86/21
Decimal Identifier 16799253
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.
Action: Check the memory on the router.
Entity Code/Event Code 86/22
Decimal Identifier 16799254
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
the configuration.
2-26 114082 Rev. A
Page 75
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/23
Decimal Identifier 16799255
Severity: Warning
Message: Software program error: Sense = <sense_data>, Alert code = <product alert reference
code>, Sending CP name = <CP_name>, ABEND code = <code>.
Meaning: The communications program was abnormally terminated. Indicates an ABEND of a
session connector or session connector manager for a reason other than lack of resources.
Action: If the message reoccurs and the problem persists, contact the Bay Networks Technical
Response Center.
Entity Code/Event Code 86/24
Decimal Identifier 16799256
Severity: Warning
Message: Management services protocol error: Sense = <sense_data>, Alert code = <product alert
reference code>, Sending CP name = <CP_name>.
Meaning: Indicates a management services protocol error. The received multiple-domain support
message unit (MDS-MU) cannot be processed. The SNA <sense_data> denotes the e xact
error condition being reported.
Action: Check the communications program in the remote node. Contact the Bay Networks
Technical Response Center if the problem persists.
Entity Code/Event Code 86/25
Decimal Identifier 16799257
Severity: Warning
Message: SNA protocol error: Sense = <sense_data>, Alert code = <pr oduct alert r eference code>,
Port name = <link_station_name>, TG name = <transmission_group>, Sending CP name
= <CP_name>, Partner CP name = <CP_name>.
Meaning: Indicates an SNA protocol violation. The received path information unit (PIU) is
discarded. The SNA <sense_data> denotes the exact error condition being reported.
Action: Check the communications program in the remote node. Contact the Bay Networks
Technical Response Center if the problem persists.
114082 Rev. A 2-27
Page 76
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 86/26
Decimal Identifier 16799258
Severity: Warning
Message: CP-CP session failure: Alert code = <product alert reference code>, TP name =
<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
program from starting.
Entity Code/Event Code 86/27
Decimal Identifier 16799259
Severity: Warning
Message: Unauthorized access attempted: Alert code = <product alert reference code>, TP name =
<transaction_program_name>, Sending CP name = <CP_name>.
Meaning: Indicates that a BIND was received from an end node (EN) that this network node (NN)
does not serve. If the end node includes the route selection control vector (RSCV) in the
BIND, the network node does not make this check.
Action: Check the APPN configuration to see if the end node <CP_name> is properly configured.
Entity Code/Event Code 86/28
Decimal Identifier 16799260
Severity: Warning
Message: Session services protocol error: Sense = <sense_data>, Alert code = <product alert
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 Response Center if the problem persists.
2-28 114082 Rev. A
Page 77
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/29
Decimal Identifier 16799261
Severity: Warning
Message: DLUR protocol error: Sense = <sense_data>, Alert code = <product alert reference
code>, Sending CP name = <CP_name>.
Meaning: Indicates a Dependent Logical Unit Requester protocol violation. The SNA <sense_data>
denotes the exact error condition being reported.
Action: Check the communications program at the network node. Contact the Bay Networks
Technical Response Center if the problem persists.
Entity Code/Event Code 86/30
Decimal Identifier 16799262
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.
Info Events
Entity Code/Event Code 86/31
Decimal Identifier 16799263
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
network search.
Entity Code/Event Code 86/32
Decimal Identifier 16799264
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.
114082 Rev. A 2-29
Page 78
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 86/33
Decimal Identifier 16799265
Severity: Info
Message: DLC activated: name = <dlc_name>
Meaning: The APPN interface was activated. The <dlc_name> is the configured DLC name.
Entity Code/Event Code 86/34
Decimal Identifier 16799266
Severity: Info
Message: DLC deactivated: name = <dlc_name>.
Meaning: The APPN interface was deactivated. The <dlc_name> is the configured DLC name.
Entity Code/Event Code 86/35
Decimal Identifier 16799267
Severity: Info
Message: RTP Connection activated: name = <name>.
Meaning: The Rapid Transport Protocol (RTP) connection was activated. The <name> indicates the
8-byte RTP connection name.
Entity Code/Event Code 86/36
Decimal Identifier 16799268
Severity: Info
Message: RTP Connection deactivated: name = <name>.
Meaning: The RTP connection was deactivated. The <name> indicates the 8-byte RTP connection
name.
Entity Code/Event Code 86/37
Decimal Identifier 16799269
Severity: Info
Message: RTP Connection Setup Failed: name = <name>.
Meaning: The RTP connection failed. The <name> indicates the 8-byte RTP connection name.
2-30 114082 Rev. A
Page 79
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/38
Decimal Identifier 16799270
Severity: Info
Message: RTP Connection Path Switched: name = <name>.
Meaning: The existing RTP connection switched to another path. The <name> indicates the 8-byte
RTP connection name of the switched path.
Entity Code/Event Code 86/39
Decimal Identifier 16799271
Severity: Info
Message: RTP Connection Connected: name = <name>.
Meaning: RTP established a connection. The <name> indicates the 8-byte RTP connection name.
Entity Code/Event Code 86/40
Decimal Identifier 16799272
Severity: Info
Message: RTP Connection Disconnected: name = <CP_name>.
Meaning: The existing RTP connection was disconnected. The <name> indicates the 8-byte RTP
connection name.
Entity Code/Event Code 86/41
Decimal Identifier 16799273
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
connection.
Entity Code/Event Code 86/42
Decimal Identifier 16799274
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.
114082 Rev. A 2-31
Page 80
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 86/43
Decimal Identifier 16799275
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
(SC30-3346).
Entity Code/Event Code 86/44
Decimal Identifier 16799276
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
(SC30-3346).
Entity Code/Event Code 86/45
Decimal Identifier 16799277
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.
2-32 114082 Rev. A
Page 81
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/46
Decimal Identifier 16799278
Severity: Info
Message: ISR session deactivated: FQCP name = <CP_name>, PCID =
<procedure_correlator_ID>.
Meaning: An intermediate session was deactivated. 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 deactivated session.
Entity Code/Event Code 86/47
Decimal Identifier 16799279
Severity: Info
Message: TG activated: dest name = <node_name>, dest type = <node_type>, TG number =
<number>.
Meaning: The transmission group indicated by the TG number was activated. The dest name is the
fully qualified destination node name. The destination type indicates an end node (EN) or
network node (NN).
Entity Code/Event Code 86/48
Decimal Identifier 16799280
Severity: Info
Message: TG deactivated: dest name = <node_name>, dest type = <node_type>, TG number =
<number>.
Meaning: The transmission group indicated by the TG number was deactiv ated. The dest name is the
fully qualified destination node name. The destination type indicates an end node (EN) or
network node (NN).
Entity Code/Event Code 86/49
Decimal Identifier 16799281
Severity: Info
Message: LS activated: ls name = <link_station_name>, adjacent CP name = <CP_name>,
adjacent node type = <node_type>.
Meaning: The link station indicated by the <link_station_name> was activated. The adjacent CP
name indicates the control point name. The adjacent node type indicates an end node
(EN), or network node (NN).
114082 Rev. A 2-33
Page 82
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 86/50
Decimal Identifier 16799282
Severity: Info
Message: LS deactivated: ls name = <link_station_name>, adjacent CP name = <CP_name>,
adjacent node type = <node_type>.
Meaning: The link station indicated by the <link_station_name> was deactivated. The adjacent CP
name indicates the control point name. The adjacent node type can be an end node (EN),
network node (NN), or low-entry networking node (LEN).
Entity Code/Event Code 86/51
Decimal Identifier 16799283
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
routing node (VRN).
Entity Code/Event Code 86/52
Decimal Identifier 16799284
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
virtual routing node (VRN).
Entity Code/Event Code 86/53
Decimal Identifier 16799285
Severity: Info
Message: NN Topology -- TG acti vated: owner name = <node_name>, dest name = <node_name>,
TG number = <number>.
Meaning: A topology update was received indicating that a TG is now active. The owner name
indicates the name of the originating node. The destination name is the fully qualified
destination node for the TG. The TG number identifies the TG between the two nodes.
2-34 114082 Rev. A
Page 83
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/54
Decimal Identifier 16799286
Severity: Info
Message: NN Topology -- TG deactivated: owner name = <node_name>, dest name =
<node_name>, TG number = <number>.
Meaning: A topology update was received indicating that a TG is now inactive. The owner name
indicates the name of the originating node. The destination name is the fully qualified
destination node for the TG. The TG number identifies the TG between the two nodes.
Entity Code/Event Code 86/55
Decimal Identifier 16799287
Severity: Info
Message: PORT activated: name = <port_name>.
Meaning: The port indicated by the <port_name> was activated.
Entity Code/Event Code 86/56
Decimal Identifier 16799288
Severity: Info
Message: PORT deactivated: name = <port_name>.
Meaning: The port indicated by the <port_name> was deactivated.
Entity Code/Event Code 86/57
Decimal Identifier 16799289
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
character string.
Entity Code/Event Code 86/58
Decimal Identifier 16799290
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
8-byte character string.
114082 Rev. A 2-35
Page 84
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 86/59
Decimal Identifier 16799291
Severity: Info
Message: DLUR: CP-SVR Pipe activated to DLUS <name>.
Meaning: A DLUR pipe was activated to a configured DLUS.
Entity Code/Event Code 86/60
Decimal Identifier 16799292
Severity: Info
Message: DLUR: CP-SVR Pipe deactivated to DLUS <name>.
Meaning: A DLUR pipe was deactivated with a configured DLUS.
Entity Code/Event Code 86/61
Decimal Identifier 16799293
Severity: Info
Message: DLUR: LU Session State Change: LU name = <LU_name>, PU name = <PU_name>,
SSCP-LU <state>, LU-LU <state>.
Meaning: A dependent LU being serviced by DLUR has changed session state. The SSCP-LU and
LU-LU session states, Active and Inactive, are logged.
Entity Code/Event Code 86/62
Decimal Identifier 16799294
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.
Entity Code/Event Code 86/63
Decimal Identifier 16799295
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.
2-36 114082 Rev. A
Page 85
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 86/64
Decimal Identifier 16799296
Severity: Info
Message: APING initiated, FQLU name = <LU_name>.
Meaning: An APING command was issued from the technician interface to the fully qualified
<LU_name>. For detailed information on APING, refer to the Bay Networks manual,
Using Technician Interface Software.
Entity Code/Event Code 86/65
Decimal Identifier 16799297
Severity: Info
Meaning: APING completed, FQLU name = <LU_name>.
Meaning: An APING command was issued from the technician interface to the fully qualified
target LU and was successful. For detailed information on APING, refer to the Bay
Networks manual, Using Technician Interface Software.
Entity Code/Event Code 86/66
Decimal Identifier 16799298
Severity: Info
Message: APING failed, FQLU name = <LU_name>.
Meaning: An APING command was issued from the technician interface to the fully qualified
target LU and failed.
Action: Retry the ping -appn command and ensure that you have specified a correct
<LU_name>. For detailed information on APING, refer to the Bay Networks manual,
Using Technician Interface Software.
114082 Rev. A 2-37
Page 86
Event Messages for Routers and BNX Platforms
ARP Events
The Address Resolution Protocol service, referred to as the ARP entity, issues the
following event messages. The entity code assigned to ARP events is 19.
Info Events
Entity Code/Event Code 19/1
Decimal Identifier 16782081
Severity: Info
Message: Service is up on circuit <circuit_no.>
Meaning: ARP is providing service to the specified circuit.
Entity Code/Event Code 19/2
Decimal Identifier 16782082
Severity: Info
Message: Service is down on circuit <circuit_no.>
Meaning: ARP is no longer providing service to the specified circuit.
Entity Code/Event Code 19/5
Decimal Identifier 16782085
Severity: Info
Message: Invalid ARP Source: <source_IP_addr ess> MAC: <MAC_address> on
<interface_address>
Meaning: ARP received a resolution request from a host on a different network.
Entity Code/Event Code 19/6
Decimal Identifier 16782086
Severity: Info
Message: Invalid ARP Request: Src: <source_IP_address> MAC: <MAC_address> & Dest:
<destination_IP_address> on diff nets
Meaning: The source and destination address of the ARP request are on different networks.
2-38 114082 Rev. A
Page 87
Event Messages (ACE through ATMINTF)
ASYNC Events
The asynchronous protocol, referred to as the ASYNC entity, issues the following
event messages. The entity code assigned to ASYNC events is 87.
Fault Event
Entity Code/Event Code 87/1
Decimal Identifier 16799489
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 T echnical Response Center
if the ASYNC driver fails to restart.
Warning Events
Entity Code/Event Code 87/2
Decimal Identifier 16799490
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
specified slot.
Entity Code/Event Code 87/3
Decimal Identifier 16799491
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.
114082 Rev. A 2-39
Page 88
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 87/4
Decimal Identifier 16799492
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
and connection to the remote port.
Entity Code/Event Code 87/5
Decimal Identifier 16799493
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.
Entity Code/Event Code 87/6
Decimal Identifier 16799494
Severity: Warning
Message: Connector COM <connector_no.>: Data Comms Equipment (DCE) unavailable
(connection indicator signal lost).
Meaning: The connection indicator (Data Set Ready) on the specified synchronous connection has
been lost.
Action: Check your cables.
Entity Code/Event Code 87/7
Decimal Identifier 16799495
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
than the value specified by <value_2>.
2-40 114082 Rev. A
Page 89
Event Messages (ACE through ATMINTF)
Info Events
Entity Code/Event Code 87/8
Decimal Identifier 16799496
Severity: Info
Message: Connector COM <connector_no.> disabled.
Meaning: The synchronous connection COM <connector_no.> is disabled.
Entity Code/Event Code 87/9
Decimal Identifier 16799497
Severity: Info
Message: Connector COM <connector_no.> enabled.
Meaning: The synchronous connection COM <connector_no.> is enabled.
Entity Code/Event Code 87/10
Decimal Identifier 16799498
Severity: Info
Message: Connector COM <connector_no.> configuration deleted.
Meaning: The record for the specified synchronous connection has been deleted from the
configuration.
Entity Code/Event Code 87/11
Decimal Identifier 16799499
Severity: Info
Message: Connector COM <connector_no.> providing LLC1 service.
Meaning: The specified synchronous connection is enabled and providing LLC1 service.
Entity Code/Event Code 87/12
Decimal Identifier 16799500
Severity: Info
Message: Connector COM <connector_no.>: Providing asynch passthrough service.
Meaning: The ASYNC protocol was enabled on a specific communications port.
114082 Rev. A 2-41
Page 90
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 87/13
Decimal Identifier 16799501
Severity: Info
Message: Connector COM <connector_no.>: Aborting connection to, port <port_no.>
Connector COM <connector_no.>: Connecting to, port <port_no.>.
Connector COM <connector_no.>: Listening on, port <port_no.>.
Connector COM <connector _no.>:Calling, port <port_no.>.
Connector COM <connector_no.>: Connected to, port <port_no.>.
Connector COM <connector_no.>: Connection timed out, port <port_no.>.
Connector COM <connector_no.>: Connection aborted by, port <port_no.>.
Connector COM <connector_no.>: Connection closed by, port <port_no.>.
Meaning: These are informational messages reporting the current ASYNC status.
ATM Events
The Asynchronous Transfer Mode service, referred to as the ATM entity, issues
the following event messages. The entity code assigned to ATM events is 78.
Fault Events
Entity Code/Event Code 78/24
Decimal Identifier 16797208
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 T echnical Response Center
if ATM fails to restart.
Entity Code/Event Code 78/53
Decimal Identifier 16797237
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 Response Center.
2-42 114082 Rev. A
Page 91
Event Messages (ACE through ATMINTF)
Warning Events
Entity Code/Event Code 78/16
Decimal Identifier 16797200
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
line number in the physical interface entry.
Entity Code/Event Code 78/17
Decimal Identifier 16797201
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.
Entity Code/Event Code 78/18
Decimal Identifier 16797202
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).
Entity Code/Event Code 78/19
Decimal Identifier 16797203
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.
114082 Rev. A 2-43
Page 92
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 78/20
Decimal Identifier 16797204
Severity: Warning
Message: ATM received a response from the driver for unknown call reference <call_ref> on line
number <line_no.>.
Meaning: The driver sent ATM a commit, reserve, or release message with an unknown call
reference.
Action: Contact the Bay Networks Technical Response Center.
Entity Code/Event Code 78/21
Decimal Identifier 16797205
Severity: Warning
Message: ATM unable to allocate memory.
Meaning: ATM was unable to allocate buffer memory.
Action: Contact the Bay Networks Technical Response Center.
Entity Code/Event Code 78/22
Decimal Identifier 16797206
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 Response Center.
Entity Code/Event Code 78/23
Decimal Identifier 16797207
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 Response Center.
2-44 114082 Rev. A
Page 93
Event Messages (ACE through ATMINTF)
Info Events
Entity Code/Event Code 78/01
Decimal Identifier 16797185
Severity: Info
Message: Line <line_no.>: ATM Service provided.
Meaning: ATM service has completed initialization on the specified line.
Entity Code/Event Code 78/02
Decimal Identifier 16797186
Severity: Info
Message: Line <line_no.>: ATM Service activated on Interface.
Meaning: ATM service is enabled on the specified line.
Entity Code/Event Code 78/03
Decimal Identifier 16797187
Severity: Info
Message: Line <line_no.>: ATM Service terminating.
Meaning: ATM service is terminating on the specified line.
Entity Code/Event Code 78/04
Decimal Identifier 16797188
Severity: Info
Message: Line <line_no.>: ATM Service is down.
Meaning: ATM service is not operational on the specified line.
Entity Code/Event Code 78/05
Decimal Identifier 16797189
Severity: Info
Message: Line <line_no.>: ATM Interface disabled.
Meaning: The ATM interface is disabled on the specified line.
114082 Rev. A 2-45
Page 94
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 78/06
Decimal Identifier 16797190
Severity: Info
Message: Line <line_no.>: ATM Interface enabled.
Meaning: The ATM interface is enabled on the specified line.
Entity Code/Event Code 78/07
Decimal Identifier 16797191
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.
Entity Code/Event Code 78/08
Decimal Identifier 16797192
Severity: Info
Message: Line <line_no.>: VPI/VCI <VPI_no.>/<VCI_no.> activated.
Meaning: The specified VPI/VCI is up and running on the specified line.
Entity Code/Event Code 78/09
Decimal Identifier 16797193
Severity: Info
Message: Line <line_no.>: VPI/VCI <VPI_no.>/<VCI_no.> deleted.
Meaning: The specified VPI/VCI is deleted from the specified line.
Entity Code/Event Code 78/10
Decimal Identifier 16797194
Severity: Info
Message: Line <line_no.>: VPI/VCI <VPI_no.>/<VCI_no.> enabled.
Meaning: The specified VPI/VCI is enabled on the specified line.
2-46 114082 Rev. A
Page 95
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 78/11
Decimal Identifier 16797195
Severity: Info
Message: Line <line_no.>: VPI/VCI <VPI_no.>/<VCI_no.> reconfigured.
Meaning: The specified VPI/VCI is reconfigured.
Entity Code/Event Code 78/12
Decimal Identifier 16797196
Severity: Info
Message: Line <line_no.>: VPI/VCI <VPI_no.>/<VCI_no.> disabled.
Meaning: The specified VPI/VCI is disabled on the specified line.
Entity Code/Event Code 78/13
Decimal Identifier 16797197
Severity: Info
Message: Line <line_no.>: VPI/VCI <VPI_no.>/<VCI_no.> has been added.
Meaning: The specified line now contains the specified VPI/VCI.
Entity Code/Event Code 78/14
Decimal Identifier 16797198
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
Response Center.
Entity Code/Event Code 78/15
Decimal Identifier 16797199
Severity: Info
Message: Line <line_no.>: Bad cct number
Meaning: ATM has received a circuit number of 0 from the driver.
114082 Rev. A 2-47
Page 96
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 78/48
Decimal Identifier 16797256
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.
Trace Events
Entity Code/Event Code 78/25
Decimal Identifier 16797209
Severity: Trace
Message: Line <line_no.>: Deleted ATM Interface Table
Meaning: The ATM Interface Table is deleted from the virtual circuit.
Entity Code/Event Code 78/26
Decimal Identifier 16797209
Severity: Trace
Message: Line <line_no.>: Deleted VPI/VCI <VPI_no.>/<VCI_no.> ATM VCL T able
Meaning: The ATM Virtual Channel Link Table no longer contains the specified VPI/VCI.
Entity Code/Event Code 78/56
Decimal Identifier 16797240
Severity: Trace
Message: Line <line_no.>, Cct <circuit_no.>: Deleted Service Record
Meaning: ATM deleted the Service Record from the specified line and circuit.
Entity Code/Event Code 78/57
Decimal Identifier 16797241
Severity: Trace
Message: Line <line_no.>, Cct <circuit_no.>: Deleted VPI/VCI <VPI_no.>/<VCI_no.> from
ATM PVC Table
Meaning: The ATM PVC Table no longer contains the specified VPI/VCI for the specified line and
circuit.
2-48 114082 Rev. A
Page 97
Event Messages (ACE through ATMINTF)
ATM_DXI Events
The Asynchronous Transfer Mode/Data Exchange Interface service, referred to as
the ATM_DXI entity, issues the following event messages. The entity code
assigned to ATM_DXI events is 49.
Note: The <low_level_index> variable shown in several of the event
messages is reserved for future use.
Fault Event
Entity Code/Event Code 49/36
Decimal Identifier 16789796
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 T echnical Response Center
if ATM DXI fails to restart.
Warning Events
Entity Code/Event Code 49/22
Decimal Identifier 16789782
Severity: Warning
Message: Line <line_no.> LLIndex <low_level_index>: ATM LMI received invalid message type
<message_type>.
Meaning: The Local Management Interface (LMI) protocol has dropped a packet, because it did not
recognize or could not parse the message type. The valid message types are 0
(GetRequest), 1 (GetNextRequest), 2 (GetResponse), 3 (SetRequest), and 4 (Trap).
114082 Rev. A 2-49
Page 98
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 49/23
Decimal Identifier 16789783
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
type mismatch.
Entity Code/Event Code 49/24
Decimal Identifier 16789784
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
the line number in the physical interface entry.
Entity Code/Event Code 49/25
Decimal Identifier 16789785
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.
Entity Code/Event Code 49/26
Decimal Identifier 16789786
Severity: Warning
Message: Line <line_no.> LLIndex <low_level_index>: Bad vpi/vci <VPI_ID>/<VCI_ID> for a
<packet_type>.
Meaning: The ATM DXI code has dropped a packet received on the specified line, because the
destination virtual path/virtual circuit is unknown.
Action: Check the configuration of the ATM PVC. Verify that the VPI and VCI have been
configured.
2-50 114082 Rev. A
Page 99
Event Messages (ACE through ATMINTF)
Entity Code/Event Code 49/27
Decimal Identifier 16789787
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.
Entity Code/Event Code 49/28
Decimal Identifier 16789788
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).
Entity Code/Event Code 49/29
Decimal Identifier 16789789
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 A TM PVC. V erify that both endpoints
have the same configuration.
Entity Code/Event Code 49/30
Decimal Identifier 16789790
Severity: Warning
Message: Line <line_no.> LLIndex <low_level_index> -- CS_PDU length mismatch on ATM PVC
<VPI_ID>/<VCI_ID>.
Meaning: A Convergence Sublayer Packet Data Unit (CS_PDU) has been discarded, because a
comparison of the header BASize field, the Trailer Length field, and the actual length of
the CS_VCI_PDU showed a mismatch.
114082 Rev. A 2-51
Page 100
Event Messages for Routers and BNX Platforms
Entity Code/Event Code 49/31
Decimal Identifier 16789791
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.
Entity Code/Event Code 49/32
Decimal Identifier 16789792
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 A TM PVC. V erify that both endpoints
have the same configuration.
Entity Code/Event Code 49/33
Decimal Identifier 16789793
Severity: Warning
Message: Line <line_no.> LLIndex <low_level_index> -- CS_PDU BETag mismatch on ATM
PVC <VPI_ID>/<VCI_ID>.
Meaning: A CS_PDU has been discarded, because the header BETag and the trailer BETag failed to
match.
Entity Code/Event Code 49/34
Decimal Identifier 16789794
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
verify that the direct circuit number is not 0.
2-52 114082 Rev. A
Loading...