Avaya Bayrs Version 12 20 Users Manual V 12.20, 12.20 Change Notice
2015-06-01
: Avaya Avaya-Bayrs-Version-12-20-Users-Manual-734884 avaya-bayrs-version-12-20-users-manual-734884 avaya pdf
Open the PDF directly: View PDF .
Page Count: 218
Download | |
Open PDF In Browser | View PDF |
BayRS Version 12.20 Document Change Notice BayRS Version 12.20 Site Manager Software Version 6.20 BCC Version 4.00 Part No. 300020-B Rev. 00 June 1998 4401 Great America Parkway Santa Clara, CA 95054 8 Federal Street Billerica, MA 01821 Copyright © 1998 Bay Networks, Inc. All rights reserved. Printed in the USA. June 1998. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Bay Networks, Inc. The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license. A summary of the Software License is included in this document. Trademarks ACE, AN, BCN, BLN, BN, BNX, FRE, LN, Optivity, PPX, Quick2Config, and Bay Networks are registered trademarks and Advanced Remote Node, ANH, ARN, ASN, BayRS, BaySecure, BayStack, BCC, SPEX, System 5000, and the Bay Networks logo are trademarks of Bay Networks, Inc. Microsoft, MS, MS-DOS, Win32, Windows, and Windows NT are registered trademarks of Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective owners. Restricted Rights Legend Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19. Statement of Conditions In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the right to make changes to the products described in this document without notice. Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein. Portions of the code in this software product may be Copyright © 1988, Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that such portions of the software were developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission. SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties). ii 300020-B Rev. 00 Bay Networks, Inc. Software License Agreement NOTICE: Please carefully read this license agreement before copying or using the accompanying software or installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement). BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price. 1. License Grant. Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal, nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software License Agreement that accompanies such software and upon payment by the end user of the applicable license fees for such software. 2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws. Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and its licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise disclose to any third party the Software, or any information about the operation, design, performance, or implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however, Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s facility, provided they have agreed to use the Software only in accordance with the terms of this license. 3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Networks and properly installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function substantially as described in its accompanying user manual during its warranty period, which begins on the date Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be included in a future Software release. Bay Networks further warrants to Licensee that the media on which the Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the Licensee’s requirements, b) that the Software will operate in the hardware or software combinations that the Licensee may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered, except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product, resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of 300020-B Rev. 00 iii its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs. 4. Limitation of liability. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE. 5. Government Licensees. This provision applies to all Software and documentation acquired directly or indirectly by or on behalf of the United States Government. The Software and documentation are commercial products, licensed on the open market at market prices, and were developed entirely at private expense and without the use of any U.S. Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS 252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable. 6. Use of Software in the European Community. This provision applies to all Software acquired for use within the European Community. If Licensee uses the Software within a country in the European Community, the Software Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such intended examination of the Software and may procure support and assistance from Bay Networks. 7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason, Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license. 8. Export and Re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data or information without first obtaining any required export licenses or other governmental approvals. Without limiting the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports are restricted or embargoed under United States export control laws and regulations, or to any national or resident of such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any military end user or for any military end use, including the design, development, or production of any chemical, nuclear, or biological weapons. 9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement will be governed by the laws of the state of California. Should you have any questions concerning this Agreement, contact Bay Networks, Inc., 4401 Great America Parkway, P.O. Box 58185, Santa Clara, California 95054-8185. LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT. iv 300020-B Rev. 00 Contents About This Guide Conventions ..................................................................................................................... xv Bay Networks Technical Publications ..............................................................................xvi Bay Networks Customer Service ....................................................................................xvii How to Get Help .............................................................................................................xvii Bay Networks Educational Services .............................................................................. xviii Document Change Notice Configuring and Managing Routers with Site Manager ..................................................... 4 Cache Mode ................................................................................................................ 4 Configuring Ethernet, FDDI, and Token Ring Services ..................................................... 7 802.1Q Tagging Overview ........................................................................................... 7 Implementation Considerations ................................................................................. 13 Configuring 802.1Q Tagged Circuits ......................................................................... 14 802.1Q Parameters ................................................................................................... 19 Configuring IP Utilities ..................................................................................................... 21 DNS Overview ........................................................................................................... 21 Creating the DNS Client ............................................................................................ 22 Customizing the DNS Client ...................................................................................... 23 Disabling DNS ........................................................................................................... 28 Deleting DNS ............................................................................................................ 29 DNS Global Parameters ............................................................................................ 29 DNS Server Record Parameters ............................................................................... 33 Configuring OSI Services ................................................................................................ 35 Configuring OSI over ATM ......................................................................................... 35 Configuring Manual Area Addresses ........................................................................ 36 Configuring OSI and TARP ....................................................................................... 38 TARP Parameter Descriptions ................................................................................... 48 300020-B Rev. 00 v Configuring PPP Services ............................................................................................... 55 show ppp alerts ......................................................................................................... 55 show ppp bad-packets .............................................................................................. 56 show ppp disabled .................................................................................................... 56 show ppp enabled ..................................................................................................... 56 show ppp interfaces .................................................................................................. 57 show ppp ip ............................................................................................................... 57 show ppp ipx ............................................................................................................. 58 show ppp line ............................................................................................................ 59 show ppp lqr .............................................................................................................. 61 Event Messages for Routers ........................................................................................... 63 AHB Fault Events ...................................................................................................... 66 AHB Warning Events ................................................................................................ 70 AHB Info Events ........................................................................................................ 73 ATM_LE Warning Events .......................................................................................... 74 ATM_LE Info Events .................................................................................................. 75 BGP Warning Event .................................................................................................. 75 CSMACD Info Event .................................................................................................. 76 DCMMW Fault Event ................................................................................................. 76 DCMMW Warning Events ......................................................................................... 77 DNS Fault Event ........................................................................................................ 77 DNS Info Event .......................................................................................................... 78 DP Warning Events ................................................................................................... 78 DP Info Events .......................................................................................................... 79 DP Trace Event ......................................................................................................... 81 DS1E1 Warning Event .............................................................................................. 82 DVS Warning Event ................................................................................................... 82 DVS Info Events ........................................................................................................ 82 FRPT Fault Event ...................................................................................................... 83 FRPT Warning Events .............................................................................................. 84 FRPT Info Events ...................................................................................................... 85 FRPT Trace Event ..................................................................................................... 88 FR_SVC Fault Event ................................................................................................. 89 FR_SVC Warning Event ........................................................................................... 89 FR_SVC Info Events ................................................................................................. 90 vi 300020-B Rev. 00 FR_SVC_API Warning Events .................................................................................. 91 FR_SVC_API Info Events ......................................................................................... 92 FR_SVC_API Trace Events ....................................................................................... 93 GRE Fault Event ....................................................................................................... 94 GRE Warning Events ................................................................................................ 94 GRE Info Events ........................................................................................................ 95 HTTP Fault Event ...................................................................................................... 95 HTTP Warning Events .............................................................................................. 96 HTTP Info Events ...................................................................................................... 97 HTTP Trace Events ................................................................................................... 98 ISDB Fault Events ................................................................................................... 102 ISDB Warning Events ............................................................................................. 103 ISDB Info Events ..................................................................................................... 105 L2TP Fault Event ..................................................................................................... 107 L2TP Warning Events ............................................................................................. 108 L2TP Info Events ..................................................................................................... 111 L2TP Trace Events .................................................................................................. 113 LB Warning Event ................................................................................................... 115 LOADER Info Events ............................................................................................... 115 MIP Fault Event ....................................................................................................... 116 MIP Warning Events ............................................................................................... 117 MIP Info Events ....................................................................................................... 118 MPS Fault Events .................................................................................................... 120 MPS Warning Events .............................................................................................. 121 MPS Info Events ...................................................................................................... 124 NLSP Info Event ...................................................................................................... 126 OSPF Fault Events .................................................................................................. 127 OSPF Warning Events ............................................................................................ 128 OSPF Info Event ..................................................................................................... 129 PPP Warning Events ............................................................................................... 129 RFWALL Warning Events ........................................................................................ 130 RFWALL Info Events ............................................................................................... 131 RFWALL Trace Event .............................................................................................. 131 RMONSTAT Info Events .......................................................................................... 132 STAC_LZS Fault Event ............................................................................................ 132 300020-B Rev. 00 vii STAC_LZS Warning Events .................................................................................... 133 STAC_LZS Info Events ............................................................................................ 134 STAC_LZS Trace Event ........................................................................................... 135 STAC_PPP Fault Event ........................................................................................... 135 STAC_PPP Warning Events .................................................................................... 136 STAC_PPP Info Events ........................................................................................... 138 STAC_PPP Trace Event .......................................................................................... 139 TAG1.Q Fault Event ................................................................................................. 139 TAG1.Q Warning Event ........................................................................................... 139 TAG1.Q Info Events ................................................................................................. 140 TAG1.Q Trace Event ................................................................................................ 145 TELNET Fault Event ............................................................................................... 146 TELNET Warning Event .......................................................................................... 146 TELNET Info Events ................................................................................................ 147 TELNET Trace Events ............................................................................................. 149 VCCT Fault Event ................................................................................................... 150 WCP Fault Event ..................................................................................................... 150 WCP Warning Events ............................................................................................. 151 WCP Info Events ..................................................................................................... 154 WCP Trace Event .................................................................................................... 155 X.25_PAD Fault Event ............................................................................................. 155 X.25_PAD Warning Events ...................................................................................... 156 X.25_PAD Info Event ............................................................................................... 157 X.25_PAD Trace Event ............................................................................................ 157 Managing Your Network Using the HTTP Server .......................................................... 158 Starting the HTTP Server Using the BCC ............................................................... 158 Customizing HTTP Server Parameters Using the BCC .......................................... 158 Upgrading Routers from Version 7-11.xx to Version 12.00 ............................................ 160 Boot and Diagnostic PROM Upgrades for Version 12.20 ........................................ 160 Using Technician Interface Scripts ................................................................................. 161 show ahb ................................................................................................................. 162 show bgp ................................................................................................................. 166 show fr ..................................................................................................................... 168 show fwall ................................................................................................................ 174 show hifn ................................................................................................................. 175 viii 300020-B Rev. 00 show l2tp ................................................................................................................. 177 show lane les .......................................................................................................... 180 show mospf ............................................................................................................. 181 show mpoa .............................................................................................................. 182 show nhrp ............................................................................................................... 184 show osi .................................................................................................................. 190 show ospf ................................................................................................................ 191 show ppp ................................................................................................................. 193 show sr .................................................................................................................... 193 show stac ................................................................................................................ 194 show sync ............................................................................................................... 196 show wcp ................................................................................................................ 199 300020-B Rev. 00 ix Figures Figure 1. VLAN Topology ........................................................................................... 8 Figure 2. Connecting VLANs Using a Router ........................................................... 10 Figure 3. Connecting VLANs Using 802.1Q Tagging ............................................... 11 Figure 4. IEEE 802.1Q Tagging ............................................................................... 12 300020-B Rev. 00 xi Tables Table 1. Version 12.20/6.20 Documentation ............................................................ 1 Table 2. TARP Packet Types .................................................................................. 38 Table 3. TARP Packet Fields ................................................................................. 39 Table 4. New and Amended Event Messages ....................................................... 63 Table 5. Required Boot and Diagnostic PROMs for BayRS Version 12.20 .......... 160 300020-B Rev. 00 xiii About This Guide If you are responsible for configuring and managing Bay Networks® routers, you need to read this guide to learn about changes to router software and hardware documentation since BayRS™ Version 12.10. Table 1 of this guide lists the manuals included in Version 12.20, identifies new and revised manuals since Version 12.10, and lists those manuals that we have not revised and which are affected by sections in this document change notice. Conventions angle brackets (< >) Indicate that you choose the text to enter based on the description inside the brackets. Do not type the brackets when entering the command. Example: if command syntax is ping, you enter ping 192.32.10.12 bold text Indicates text that you need to enter, command names, and buttons in menu paths. Example: Enter wfsm & Example: Use the dinfo command. Example: ATM DXI > Interfaces > PVCs identifies the PVCs button in the window that appears when you select the Interfaces option from the ATM DXI menu. 300020-B Rev. 00 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. xv BayRS Version 12.20 Document Change Notice screen text Indicates data that appears on the screen. Example: Set Bay Networks Trap Monitor Filters 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 vertical line (|) Indicates that you enter only one of the parts of the command. The vertical line separates choices. Do not type the vertical line when entering the command. Example: If the command syntax is show at routes | nets, you enter either show at routes or show at nets, but not both. Bay Networks Technical Publications You can now print technical manuals and release notes free, directly from the Internet. Go to support.baynetworks.com/library/tpubs. Find the Bay Networks products for which you need documentation. Then locate the specific category and model or version for your hardware or software product. Using Adobe Acrobat Reader, you can open the manuals and release notes, search for the sections you need, and print them on most standard printers. You can download Acrobat Reader free from the Adobe Systems Web site, www.adobe.com. Documentation sets and CDs are available through your local Bay Networks sales office or account representative. xvi 300020-B Rev. 00 About This Guide Bay Networks Customer Service You can purchase a support contract from your Bay Networks distributor or authorized reseller, or directly from Bay Networks Services. For information about, or to purchase a Bay Networks service contract, either call your local Bay Networks field sales office or one of the following numbers: Region Telephone number Fax number United States and Canada 800-2LANWAN; then enter Express Routing 978-916-3514 Code (ERC) 290, when prompted, to purchase or renew a service contract 978-916-8880 (direct) Europe 33-4-92-96-69-66 33-4-92-96-69-96 Asia/Pacific 61-2-9927-8888 61-2-9927-8899 Latin America 561-988-7661 561-988-7550 Information about customer service is also available on the World Wide Web at support.baynetworks.com. How to Get Help If you purchased a service contract for your Bay Networks product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you purchased a Bay Networks service program, call one of the following Bay Networks Technical Solutions Centers: 300020-B Rev. 00 Technical Solutions Center Telephone number Fax number Billerica, MA 800-2LANWAN 978-916-3514 Santa Clara, CA 800-2LANWAN 408-495-1188 Valbonne, France 33-4-92-96-69-68 33-4-92-96-69-98 Sydney, Australia 61-2-9927-8800 61-2-9927-8811 Tokyo, Japan 81-3-5402-0180 81-3-5402-0173 xvii BayRS Version 12.20 Document Change Notice Bay Networks Educational Services Through Bay Networks Educational Services, you can attend classes and purchase CDs, videos, and computer-based training programs about Bay Networks products. Training programs can take place at your site or at a Bay Networks location. For more information about training programs, call one of the following numbers: Region Telephone number United States and Canada 800-2LANWAN; then enter Express Routing Code (ERC) 282 when prompted 978-916-3460 (direct) xviii Europe, Middle East, and Africa 33-4-92-96-15-83 Asia/Pacific 61-2-9927-8822 Tokyo and Japan 81-3-5402-7041 300020-B Rev. 00 Document Change Notice Table 1 lists the manuals included in the Version 12.20/6.20 release and those manuals affected by sections in this document change notice. Table 1. Version 12.20/6.20 Documentation Document Title Revised Book for 12.20/6.20 BayRS and Site Manager Software Installation ✔ BCC Quick Reference ✔ Affected by Section in DCN Cable Guide ✔ Configuring and Managing Routers with Site Manager Configuring and Troubleshooting Bay Dial VPN Networks ✔ Configuring AppleTalk Services Configuring APPN Services Configuring ATM DXI Services Configuring ATM Half-Bridge Services Configuring ATM Services ✔ Configuring BaySecure FireWall-1 Configuring BayStack Remote Access ✔ Configuring Bridging Services Configuring BSC Transport Services Configuring Data Compression Services ✔ (continued) 300020-B Rev. 00 1 BayRS Version 12.20 Document Change Notice Table 1. Version 12.20/6.20 Documentation (continued) Document Title Revised Book for 12.20/6.20 Affected by Section in DCN Configuring Data Encryption Services Configuring DECnet Services Configuring Dial Services ✔ Configuring DLSw Services ✔ Configuring Ethernet, FDDI, and Token Ring Services Configuring Frame Relay Services ✔ Configuring Interface and Router Redundancy Configuring IP Multicasting and Multimedia Services ✔ Configuring IP Services ✔ ✔ Configuring IP Utilities Configuring IPv6 Services Configuring IPX Services ✔ Configuring L2TP Services ✔ Configuring LLC Services Configuring LNM Services ✔ Configuring OSI Services Configuring Polled AOT Transport Services ✔ Configuring PPP Services Configuring RADIUS Configuring RMON and RMON2 ✔ Configuring SDLC Services Configuring SMDS Configuring SNMP, BootP, DHCP, and RARP Services Configuring Traffic Filters and Protocol Prioritization Configuring VINES Services (continued) 2 300020-B Rev. 00 Table 1. Version 12.20/6.20 Documentation (continued) Document Title Configuring WAN Line Services Revised Book for 12.20/6.20 Affected by Section in DCN ✔ Configuring X.25 Gateway Services Configuring X.25 Services Configuring XNS Services Connecting ASN Routers to a Network Event Messages for Routers ✔ Managing Your Network Using the HTTP Server ✔ Quick-Starting Routers Troubleshooting Routers Upgrading Routers from Version 7-11.xx to Version 12.00 ✔ Using Technician Interface Scripts ✔ Using Technicial Interface Software Using the Bay Command Console ✔ Writing Technician Interface Scripts 300020-B Rev. 00 3 BayRS Version 12.20 Document Change Notice Configuring and Managing Routers with Site Manager The following section is an amendment to Configuring and Managing Routers with Site Manager. Cache Mode BayRS Version 12.20 is supported by an enhanced Site Manager Version 6.20. Earlier versions of Site Manager provided three distinct configuration modes: • Local mode, which creates or edits a configuration file locally on the Site Manager workstation for later implementation on a target router • Remote mode, which downloads a configuration file from a target router for local update or modification • Dynamic mode, which uses SNMP set and get commands to provide real-time configuration access to a target router See Configuring and Managing Routers with Site Manager for information about each of these three configuration modes. Site Manager Version 6.20 provides a fourth configuration mode, cache mode, which is a hybrid of the existing remote and dynamic modes. Cache mode addresses the problem of long response times that may be encountered while configuring a router in dynamic mode, while still providing real-time configuration to the target router. In dynamic mode, Site Manager uses SNMP set operations to write directly to the router’s management information base, and thus provide real-time configuration. However, before issuing an SNMP set command, Site Manager may have to read several information base items from the router using SNMP get operations. Long response times in dynamic mode are caused mainly by the large number of SNMP retrievals (get operations) that precede the SNMP set. To improve response time, cache mode saves a copy of the router’s existing operational configuration to a local file on the Site Manager workstation. Site Manager then uses this local file to obtain information base values previously obtained through SNMP get operations. Site Manager also updates the local file to reflect any dynamic changes made during the cache mode configuration session. Consequently, the local copy of the router’s configuration always mirrors the router’s operational state. 4 300020-B Rev. 00 Configuring and Managing Routers with Site Manager Implementing Cache Mode To access cache mode from the Site Manager window, complete the following tasks: Site Manager Procedure You do this System responds 1. In the main Site Manager window, choose Tools. 2. Choose Configuration Manager. 3. Choose Cache. The Save Configuration File window opens. 4. Enter a file name and select a volume. The existing router operational configuration is saved in the router’s file system under this name and in the specified volume. Site Manager downloads a copy of the configuration file and stores it locally under the name specified. Site Manager then opens the Configuration Manager window, which displays the hardware configuration of the target router. 5. Dynamically configure the target router. Saving a Configuration Generated in Cache Mode To save a configuration generated in cache mode, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Save As. The Save Configuration File window opens. 2. Enter a file name. The existing router operational configuration is saved in the router’s file system under this name. (continued) 300020-B Rev. 00 5 BayRS Version 12.20 Document Change Notice Site Manager Procedure (continued) 6 You do this System responds 3. Select a volume. The configuration file is saved to the specified flash media. The Save Configuration File window opens again. 4. Enter a file name. The existing router operational configuration is saved on the local (Site Manager workstation) file system under this name. 5. Click on Save. Site Manager saves the file locally. 300020-B Rev. 00 Configuring Ethernet, FDDI, and Token Ring Services Configuring Ethernet, FDDI, and Token Ring Services The following sections are amendments to Configuring Ethernet, FDDI, and Token Ring Services: Section Page 802.1Q Tagging Overview -7 Implementation Considerations -13 Configuring 802.1Q Tagged Circuits -14 802.1Q Parameters -19 802.1Q Tagging Overview This section describes the Bay Networks implementation of 802.1Q tagging and how to configure it on the router. Virtual LAN Overview Traditional LANs are defined by physical media: • Early first-generation LANs were defined by the cable or fiber that connected workstations. • Later second-generation LANs, or LAN segments, are defined by the concentrators, repeaters, or hubs (all physical layer, or layer 1, devices) that connect workstations. Traditional LANs are connected by bridges at layer 2 or by routers at layer 3. Modern, intelligent switching devices have enabled the construction and interconnection of virtual LANs (VLANs). The term VLAN is generally understood to mean the following: • A VLAN is a flexible, software-defined logical group of devices; VLAN boundaries are independent of the physical media. Figure 1 shows a second-generation network topology with a bridge connecting four LANs or LAN segments, and the same physical topology with an intelligent switching device (such as one of the Accelar™ family of routing switches) providing connectivity. 300020-B Rev. 00 7 BayRS Version 12.20 Document Change Notice Hub Hub LAN Segment 1 LAN Segment 1 Engineering VLAN Hub Hub LAN Segment 2 Hub LAN Segment 2 Hub LAN Segment 3 LAN Segment 3 Marketing VLAN Hub Hub LAN Segment 4 LAN Segment 4 Bridge VLAN device SN0007A Figure 1. VLAN Topology As illustrated in Figure 1, the four VLAN segments can be reconfigured as two VLANs: the Engineering VLAN, consisting of LAN segments 1 and 2, and the Marketing VLAN, consisting of LAN segments 3 and 4. • A VLAN contains broadcast traffic within software-defined boundaries. With reference to Figure 1, broadcast traffic within the bridged topology is propagated across all physical interfaces. For example, a broadcast frame originated by a workstation on LAN segment 1 is forwarded to LAN segments 2, 3, and 4. In contrast, within the VLAN topology, a broadcast frame originated by a workstation on LAN segment 1 is forwarded only to LAN segment 2. Broadcast traffic is confined with the bounds of the VLAN. 8 300020-B Rev. 00 Configuring Ethernet, FDDI, and Token Ring Services • A VLAN provides low-latency, wire-speed communication between VLAN members. All members of the Engineering VLAN, for example, communicate at wire speed whether they are physically connected to LAN segment 1 or 2. • A VLAN supports network segmentation or microsegmentation; a VLAN segment can consist of one or many workstations. • A VLAN is a closed bridge group, with boundaries enforced by spanning tree protocols. • Intra-VLAN communication is provided by layer 2 switching. • Inter-VLAN communication requires additional layer 3 services. Layer 3 services may be provided by the VLAN device or by an adjacent router. Intra-VLAN Traffic Flow Intra-VLAN traffic (where the frame source and the frame destination are both on the same VLAN) is forwarded at layer 2 by the VLAN device. Forwarding decisions are based on layer 2 forwarding tables that associate specific MAC/layer 2 addresses with specific device ports. Inter-VLAN Traffic Flow Inter-VLAN traffic (where the frame source and the frame destination are not on the same VLAN) requires layer 3 (routing) services. Certain advanced platforms (such as the Accelar family of routing switches) can provide these services. More commonly, however, routing services are provided by an adjacent router, as shown in Figure 2, where frames originating on the Marketing VLAN and destined for the Sales VLAN are switched across a dedicated port by the VLAN device to the attached router. The router, operating at layer 3, redirects the frame across another dedicated port to the VLAN device, which in turns switches the frame at layer 2 to the recipient VLAN. The configuration illustrated in Figure 2 is inefficient for both the router and the VLAN device, because it requires a dedicated port for each VLAN. In network topologies that support multiple VLANs, the costs for dedicated ports may be prohibitive. 300020-B Rev. 00 9 BayRS Version 12.20 Document Change Notice Engineering IP VLAN Marketing IP VLAN VLAN device Traffic flow Dedicated VLAN-specific untagged ports Sales IP VLAN Router SN0020A Figure 2. Connecting VLANs Using a Router In contrast, Figure 3 depicts a topology in which the same three VLANs share a common connection to the adjacent router. This common connection is enabled by a packet encapsulation format specified in IEEE 802.1Q, Draft Standard for Virtual Bridged Local Area Networks. This packet encapsulation format is referred to as 802.1Q tagging. 10 300020-B Rev. 00 Configuring Ethernet, FDDI, and Token Ring Services Engineering IP VLAN Marketing IP VLAN VLAN device Sales all-protocol VLAN Traffic flow Single untagged port serves the Marketing and Sales VLANs Router SN0021A Figure 3. Connecting VLANs Using 802.1Q Tagging 802.1Q Tagging 802.1Q tagging enables multiple VLANs to share a common connection to a router. The router provides layer 3 routing services for the VLAN clients. The router may provide standard routing services, that is, directing received frames toward a remote destination; or it may function as a so-called “one-armed” router, returning frames to the device from which it received them, but forwarding them to a different logical entity. Shared usage of a common physical port (often referred to as a tagged port) is facilitated by the addition of two 2-byte fields within the standard Ethernet header (Figure 4). 300020-B Rev. 00 11 BayRS Version 12.20 Document Change Notice IEEE 802.1Q encapsulation Ethernet encapsulation Destination address (6 octets) Destination address (6 octets) Source address (6 octets) Source address (6 octets) Tag protocol identifier (2 octets) Protocol type (2 octets) Tag control information (2 octets) Data (46 to 1496 octets) Protocol type (2 octets) FCS (4 octets) Data (46 to 1496 octets) Maximum size: 1514 octets FCS (4 octets) Maximum size: 1518 octets SN0016A Figure 4. IEEE 802.1Q Tagging The IEEE has not yet standardized values for the tag protocol identifier (TPID) field, leaving vendors to provide their own proprietary values. The Accelar family of routing switches, for example, writes a value of 8100 (hexadecimal) to this field. The tag control information (TCI) field contains a unique value that identifies the VLAN on which the frame originated. This value is assigned during the configuration of the layer 2 device. The addition of the four bytes required for the TPID and TCI fields raises the possibility of generating frames up to 1518 bytes in length, four bytes larger than the maximum packet size specified by Ethernet. Consequently, for frames on which 802.1Q tagging is enabled, BayRS accepts such outsized frames. 12 300020-B Rev. 00 Configuring Ethernet, FDDI, and Token Ring Services Router Processing of Tagged Frames 802.1Q tagging is supported only on 100BASE-T interfaces that connect the Bay Networks router to an 802.1Q-compliant switch or routing switch. With 802.1Q tagging enabled, the physical connection between the router and the adjacent device supports multiple virtual connections. The number of connections is equal to the number of virtual connections plus a default physical connection that provides transit services for other non-VLAN traffic that may be received from or forwarded to the adjacent device. Upon receipt of a frame across a virtual connection, a circuit manager strips the four bytes of 802.1Q header information and directs a now standard Ethernet frame to a connection-specific routing process. The routing process consults its forwarding table and, in turn, directs the frame to a circuit manager handling the next-hop connection. If that connection is a non-tagged, non-virtual connection, processing is completed as for any other standard Ethernet frame. However, if the next-hop connection is a tagged, virtual connection, the circuit manager inserts the four bytes of 802.1Q header information that identify that VLAN into the standard Ethernet header. After performing the 802.1Q encapsulation, the circuit manager forwards the frame across the virtual connection toward the destination VLAN. Implementation Considerations Before you configure 802.1Q tagging on a router, note the following considerations. 300020-B Rev. 00 • 802.1Q tagging is supported only on 100BASE-T interfaces; it is not supported on other LAN interfaces. • 802.1Q tagging cannot be used to extend a VLAN across multiple devices. • The VLAN type (port-based, protocol-based, address-based, and so on) is ignored by the router. 13 BayRS Version 12.20 Document Change Notice Configuring 802.1Q Tagged Circuits Use Site Manager to configure 802.1Q tagging. This section includes information about the following topics: Topic Page Adding a Tagged Circuit to an Unconfigured 100BASE-T Interface -14 Adding a Tagged Circuit to an Existing 100BASE-T Interface -16 Editing a Tagged Circuit -17 Disabling a Tagged Circuit -18 Deleting a Tagged Circuit -18 Adding a Tagged Circuit to an Unconfigured 100BASE-T Interface The following procedure describes how to add an 802.1Q tagged circuit to a previously unconfigured 100BASE-T interface. This procedure assumes that you are configuring the 802.1Q tagged circuit for IP routing. To enable other routing protocols on an 802.1Q tagged circuit, see the appropriate guide for that protocol. Site Manager Procedure You do this System responds 1. In the Configuration Manager window, click on a 100BASE-T connector. The Add Circuit window opens. 2. Click on OK. The Select Protocols window opens. 3. Choose VLAN, then click on OK. The Edit VLAN Interface Parameters window opens. 4. Click on Add. The TAG1Q Parameters window opens. 5. Set the following parameters: • VLAN Name • Global VLAN Id Click on Help or see the parameter descriptions beginning on page -19. 6. Click on OK. The Edit VLAN Interface Parameters window opens. Note that 802.1Q tagged circuits are displayed with a Vn extension. (continued) 14 300020-B Rev. 00 Configuring Ethernet, FDDI, and Token Ring Services Site Manager Procedure (continued) You do this System responds 7. Select the 802.1Q tagged circuit that you are adding. Set the Protocol Type (hex) parameter. Retain the default value for connection to Bay Networks 802.1Q-enabled devices. 8. Click on Apply and Done. You return to the Configuration Manager window. To add IP routing to the 802.1Q tagged circuit: 9. Choose Circuits. 10. Choose Edit Circuits. The Circuit List window opens. 11. Select the 802.1Q tagged circuit. Note that 802.1Q tagged circuits are displayed with a Vn extension. 12. Click on Edit. The Circuit Definition window opens. 13. Choose Protocols. 14. Choose Add/Delete. The Select Protocols window opens. 15. Select IP and click on OK. The IP Configuration window opens. 16. Enter an IP address and subnet mask and The Circuit Definition window opens. click on OK. 17. Choose File. 300020-B Rev. 00 18. Choose Exit. The Circuit List window opens. 19. Click on Done. You return to the Configuration Manager window. 15 BayRS Version 12.20 Document Change Notice Adding a Tagged Circuit to an Existing 100BASE-T Interface To add an 802.1Q tagged circuit to an existing 100BASE-T interface, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, click on a 100BASE-T connector. The Edit Connector window opens. 2. Click on Edit Circuit. The Circuit Definition window opens. 3. Choose Protocols. The Protocols menu opens. 4. Choose Add/Delete. The Select Protocols window opens. 5. Choose VLAN, then click on OK. The Edit VLAN Interface Parameters window opens. 6. Click on Add. The TAG1Q Parameters window opens. 7. Set the following parameters: • VLAN Name • Global VLAN Id Click on Help or see the parameter descriptions beginning on page -19. 8. Click on OK. The Edit VLAN Interface Parameters window opens. Note that 802.1Q tagged circuits are displayed with a Vn extension. 9. Select the 802.1Q tagged circuit that you are adding. Set the Protocol Type (hex) parameter. Retain the default value for connection to Bay Networks 802.1Q-enabled devices. 10. Click on Apply and Done. You return to the Configuration Manager window. To add IP routing to the 802.1Q tagged circuit: 11. Choose Circuits. 12. Choose Edit Circuits. The Circuit List window opens. 13. Select the 802.1Q tagged circuit. Note that 802.1Q tagged circuits are displayed with a Vn extension. (continued) 16 300020-B Rev. 00 Configuring Ethernet, FDDI, and Token Ring Services Site Manager Procedure (continued) You do this System responds 14. Click on Edit. The Circuit Definition window opens. 15. Choose Protocols. 16. Choose Add/Delete. The Select Protocols window opens. 17. Select IP and click on OK. The IP Configuration window opens. 18. Enter an IP address and subnet mask and The Circuit Definition window opens. click on OK. 19. Choose File. 20. Choose Exit. The Circuit List window opens. 21. Click on Done. You return to the Configuration Manager window. Editing a Tagged Circuit To edit an 802.1Q tagged circuit, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose VLAN. The VLAN menu opens. 3. Choose Interfaces. The Edit VLAN Interface Parameters window opens. 4. Select the 802.1Q tagged circuit that you want to edit. Site Manager displays the current parameter values for the circuit. 5. Edit the following parameters as required: • VLAN Name • Global VLAN Id • Protocol Type (hex) Click on Help or see the parameter descriptions beginning on page -19. 6. Click on Apply and Done. 300020-B Rev. 00 You return to the Configuration Manager window. 17 BayRS Version 12.20 Document Change Notice Disabling a Tagged Circuit To disable an 802.1Q tagged circuit, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose VLAN. The VLAN menu opens. 3. Choose Interfaces. The Edit VLAN Interface Parameters window opens. 4. Select the 802.1Q tagged circuit that you want to disable. Site Manager displays the current parameter values for the circuit. 5. Set the Enable/Disable parameter to Disable. 6. Click on Apply and Done. You return to the Configuration Manager window. Deleting a Tagged Circuit To delete an 802.1Q tagged circuit, complete the following tasks: Site Manager Procedure 18 You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose VLAN. The VLAN menu opens. 3. Choose Interfaces. The Edit VLAN Interface Parameters window opens. 4. Select the 802.1Q tagged circuit that you want to delete. Site Manager displays the current parameter values for the circuit. 5. Click on Delete and Done. You return to the Configuration Manager window. 300020-B Rev. 00 Configuring Ethernet, FDDI, and Token Ring Services 802.1Q Parameters The Edit VLAN Interface Parameters window contains the parameters for all 802.1Q tagged circuits on the router. The parameter descriptions follow: Parameter: Enable/Disable Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > VLAN > Interfaces Enable Enable | Disable Enables or disables the 802.1Q tagged circuit. Set to Disable to disable a previously configured 802.1Q tagged circuit. Set to Enable to enable a disabled 802.1Q tagged circuit. MIB Object ID: 1.3.1.6.1.4.1.18.3.5.1.12.6.1.1.1.2 Parameter: VLAN Name Path: Default: Options: Function: Configuration Manager > Protocols > VLAN > Interfaces None Any character string Provides a mnemonic to associate with the VLAN. This string is not used by BayRS. Instructions: Enter a name for the VLAN. MIB Object ID: 1.3.1.6.1.4.1.18.3.5.1.12.6.1.1.1.3 Parameter: Global VLAN Id Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > VLAN > Interfaces None Any integer value from 1 to 4095 Provides a unique identifier for the VLAN within the layer 2/layer 3 topology Enter the unique VLAN numeric identifier that was assigned to the VLAN when it was initially configured on the adjacent layer 2 device. This value must match the one assigned during the initial VLAN configuration. MIB Object ID: 1.3.1.6.1.4.1.18.3.5.1.12.6.1.1.1.5 300020-B Rev. 00 19 BayRS Version 12.20 Document Change Notice Parameter: Protocol Type (hex) Path: Default: Options: Function: Configuration Manager > Protocols > VLAN > Interfaces 33024 (8100 hexadecimal) Any integer value Specifies the contents of the TPID field in 802.1Q encapsulated frames originated by this VLAN. Instructions: Enter (in decimal notation) the TPID value that was assigned to the VLAN when it was initially configured on the adjacent layer 2 device. This value must match the one assigned during the initial VLAN configuration. MIB Object ID: 1.3.1.6.1.4.1.18.3.5.1.12.6.1.1.1.8 20 300020-B Rev. 00 Configuring IP Utilities Configuring IP Utilities The following sections are amendments to Configuring IP Utilities: Section Page DNS Overview -21 Creating the DNS Client -22 Customizing the DNS Client -23 Disabling DNS -28 Deleting DNS -29 DNS Global Parameters -29 DNS Server Record Parameters -33 DNS Overview The Domain Name System (DNS) is a distributed database system, with DNS clients requesting host name/address resolution information from various DNS servers. DNS is used with numerous types of networking applications and protocols. Specifically, DNS provides a directory service that allows client devices to retrieve information from a server-based database. For the Internet, DNS enables a device to obtain the IP address of a host based on the host’s domain name. The Bay Networks router functions as a DNS client. 300020-B Rev. 00 21 BayRS Version 12.20 Document Change Notice Creating the DNS Client To create the DNS client, first configure an IP interface. Then create and enable the DNS client by completing the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose Create DNS. The DNS Configuration window opens. 5. Click on OK. You return to the Configuration Manager window. After you create and enable the DNS client, you must specify at least one DNS server. You can specify up to a maximum of three DNS servers. To specify a DNS server, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose DNS Servers. The DNS Server List window opens. 5. Click on Add. The DNS Server Record window opens. 6. Set the following parameters: • Index • IP Address • Port Number Click on Help or see the parameter descriptions beginning on page -33. (continued) 22 300020-B Rev. 00 Configuring IP Utilities Site Manager Procedure (continued) You do this System responds 7. Click on OK. The DNS Server List window reopens; it now lists the index value and the IP address of the server you configured. 8. Click on Done. You return to the Configuration Manager window. Customizing the DNS Client When you create the DNS client, default values are in effect for all parameters. You may want to change these values, depending on the requirements of your network. This section provides information about how to customize the DNS client configuration. It includes information about the following topics: 300020-B Rev. 00 Topic Page Modifying the DNS Client Configuration -24 Disabling the Recursion Bit -24 Modifying How the DNS Client Handles Server Responses -25 Modifying the DNS Server List -26 23 BayRS Version 12.20 Document Change Notice Modifying the DNS Client Configuration You can modify how the router makes requests to the DNS server, for example, how often requests are repeated and how long it waits between requests. To modify how the router sends DNS requests, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose Global. The Edit DNS Global Parameters window opens. 5. Edit any of the following parameters: • Time Out • Max Retransmission • Max Outstanding Query • IP Type of Service • Domain Name • Use Default Domain Name Click on Help or see the parameter descriptions beginning on page -29. 6. Click on OK. You return to the Configuration Manager window. Disabling the Recursion Bit If the first DNS server that the router contacts does not have the information requested, you can instruct that server to contact another server that can respond by setting a recursion bit in the DNS information header packet. The recursion bit is enabled by default. If you do not want to contact more than one server, you must disable the recursion bit. 24 300020-B Rev. 00 Configuring IP Utilities To disable the recursion bit, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose Global. The Edit DNS Global Parameters window opens. 5. Set the Recursion parameter to Disable. Click on Help or see the parameter description on page -32. 6. Click on OK. You return to the Configuration Manager window. Modifying How the DNS Client Handles Server Responses To specify whether the router accepts the DNS server’s response when it contains a truncation bit or whether the router accepts data from only the authorized DNS server, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose Global. The Edit DNS Global Parameters window opens. (continued) 300020-B Rev. 00 25 BayRS Version 12.20 Document Change Notice Site Manager Procedure (continued) You do this System responds 5. Edit one or both of the following parameters: • Ignore Truncation Error • Use Auth Answer Only Click on Help or see the parameter descriptions on page -32. 6. Click on OK. You return to the Configuration Manager window. Modifying the DNS Server List The DNS server list contains the DNS servers (up to a maximum of three) that the DNS client can query. You can add and delete entries in the DNS server list. Displaying the DNS Server List To view the list of DNS servers to which the router can connect, complete the following tasks: Site Manager Procedure 26 You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose DNS Servers. The DNS Server List window opens. This window lists all configured DNS servers. 5. Select a server from the list. The DNS Server List window displays the IP address and DNS port for the selected server. 6. Click on Done. You return to the Configuration Manager window. 300020-B Rev. 00 Configuring IP Utilities Adding Entries to the DNS Server List To add a new entry (up to a maximum of three) to the DNS server list, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose DNS Servers The DNS Server List window opens. This window lists all configured DNS servers. 5. Click on Add. The DNS Server Record window opens. 6. Set the following parameters: • Index • IP Address • Port Number Click on Help or see the parameter descriptions on page -33. 7. Click on OK. The DNS Server List window reopens. 8. Click on Apply and Done. You return to the Configuration Manager window. Deleting Entries from the DNS Server List To delete an entry from the DNS server list, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. (continued) 300020-B Rev. 00 27 BayRS Version 12.20 Document Change Notice Site Manager Procedure (continued) You do this System responds 4. Choose DNS Servers. The DNS Server List window opens. This window lists all configured DNS servers. 5. Select the server that you want to delete. Site Manager highlights the entry. 6. Click on Delete. Site Manager removes the entry. 7. Click on OK. The DNS Server List window reopens. 8. Click on Apply and Done. You return to the Configuration Manager window. Disabling DNS To disable DNS client services from all circuits on the router, complete the following tasks: Site Manager Procedure 28 You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose Global. The Edit DNS Global Parameters window opens. 5. Set the Enable parameter to Disable. Click on Help or see the parameter description on page -29. Site Manager disables DNS on the router. 6. Click on OK. You return to the Configuration Manager window. 300020-B Rev. 00 Configuring IP Utilities Deleting DNS To delete DNS client services from the router, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose Global Protocols. The Global Protocols menu opens. 3. Choose DNS. The DNS menu opens. 4. Choose Delete DNS. A message window prompts: Do you REALLY want to delete DNS? 5. Click on OK. You return to the Configuration Manager window. DNS Global Parameters The Edit DNS Global Parameters window contains the global DNS parameters for the DNS client on the router. The parameter descriptions follow. Parameter: Enable Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > Global Protocols > DNS > Global Enable Enable | Disable Enables or disables DNS on the router. Accept the default, Enable, to enable DNS client services on this router. To temporarily disable DNS, set this parameter to Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.2 300020-B Rev. 00 29 BayRS Version 12.20 Document Change Notice Parameter: Time Out Path: Default: Options: Function: Configuration Manager > Protocols > Global Protocols > DNS > Global 5 1 to 60 seconds Specifies, in seconds, the amount of time the router waits before it retransmits a request to the DNS server. Instructions: If you have a large network, set this value higher than the default, so that the router will not time out before it receives a response from the DNS server. Otherwise, accept the default. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.3 Parameter: Max Retransmission Path: Default: Options: Function: Configuration Manager > Protocols > Global Protocols > DNS > Global 3 0 to 15 Specifies the maximum number of times that the router can retransmit a request to the DNS server before it records an error. Instructions: Accept the default, or enter a value from 0 to 15. Entering a high value may delay router response time when errors occur. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.4 Parameter: Max Outstanding Query Path: Default: Options: Function: Configuration Manager > Protocols > Global Protocols > DNS > Global 20 1 to 100 Specifies the maximum number of outstanding queries to the server that the router allows. Instructions: Accept the default, or enter a value from 1 to 100. If you select a high value, be sure that the router has enough memory to accommodate the number of outstanding queries that you specify. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.5 30 300020-B Rev. 00 Configuring IP Utilities Parameter: IP Type of Service Path: Default: Options: Function: Configuration Manager > Protocols > Global Protocols > DNS > Global Low Delay Normal | Low Delay Specifies the type of service set in the IP datagram. The type of service specifies to the transport layer (UDP) how the router handles DNS packets. Instructions: Bay Networks recommends Low Delay for DNS packet transfers, because a Low Delay setting specifies a high priority for the packets. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.6 Parameter: Domain Name Path: Configuration Manager > Protocols > Global Protocols > DNS > Global Default: None Options: Any combination of up to 255 alphanumeric characters that specifies a network domain, for example, baynetworks.com. Function: Specifies the default domain name that the router uses when trying to reach a DNS server. You can use this domain name when issuing a ping command to verify the connection to a DNS server. For Version 12.20, this parameter is valid only for use with the Technician Interface. For example, if you want to check the connection from router A to remote Bay Networks router B, you can set this parameter to baynetworks.com. When you enter the command ping router, router A, the DNS client, adds baynetworks.com to the command, making the actual command ping router.baynetworks.com. The DNS server translates the name to an IP address. Instructions: Enter the default domain name. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.7 300020-B Rev. 00 31 BayRS Version 12.20 Document Change Notice Parameter: Recursion Path: Default: Options: Function: Configuration Manager > Protocols > Global Protocols > DNS > Global Enable Enable | Disable Sets the recursion bit in the DNS packet header so that if the first server that the router contacts does not have the required information, that server finds another server that can respond to the request. Instructions: Bay Networks recommends that you accept the default, Enable, to implement recursion for resolving requests to a DNS server. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.8 Parameter: Ignore Truncation Error Path: Default: Options: Function: Configuration Manager > Protocols > Global Protocols > DNS > Global Enable Enable | Disable Specifies whether the router should reject DNS server responses that contain the truncation bit in the DNS header. Typically the information that the router uses is in the first few bytes of the response messages, so it can ignore the rest of the message. Instructions: Accept the default, Enable, to ignore the error messages. To accept truncation error messages, set this parameter to Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.9 Parameter: Use Auth Answer Only Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > Global Protocols > DNS > Global Disable Enable | Disable Specifies whether the router should accept data only from the authorized server. Select Enable to accept data only from an authorized server. Select Disable to accept data from any server. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.10 32 300020-B Rev. 00 Configuring IP Utilities Parameter: Use Default Domain Name Path: Default: Options: Function: Configuration Manager > Protocols > Global Protocols > DNS > Global Enable Enable | Disable If you entered a value for the Domain Name parameter, this parameter instructs the router to use that name when sending requests to a DNS server. Instructions: Accept the default, Enable, to use the default domain name. Otherwise, select Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.1.11 DNS Server Record Parameters The DNS Server Record window contains the parameters that specify the “approved” DNS servers for the router’s DNS client. The parameter descriptions follow. Parameter: Index Path: Configuration Manager > Protocols > Global Protocols > DNS > DNS Servers > Add Default: None Options: 1 to 3 Function: Specifies the order in which the router contacts the DNS server. For example, the router first contacts a server with an index of 1. If that server is not operating, the router then contacts a server with an index of 2. Instructions: Determine the order in which you want the router to contact a particular server and assign the appropriate index value to that server. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.2.1.2 300020-B Rev. 00 33 BayRS Version 12.20 Document Change Notice Parameter: IP Address Path: Configuration Manager > Protocols > Global Protocols > DNS > DNS Servers > Add Default: 0.0.0.0 Options: Any valid IP address Function: Specifies the IP address of the DNS server that responds to DNS client requests. Instructions: Enter a 32-bit IP address. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.2.1.3 Parameter: Port Number Path: Configuration Manager > Protocols > Global Protocols > DNS > DNS Servers > Add Default: 53 Options: 1 to 46000 Function: Specifies the UDP port on the DNS server to which the router should connect. Instructions: In most cases, accept the default. Only in special situations should you specify another UDP port number. MIB Object ID: 1.3.6.1.4.1.18.3.5.3.19.2.1.4 34 300020-B Rev. 00 Configuring OSI Services Configuring OSI Services The following sections are amendments to Configuring OSI Services. Section Page Configuring OSI over ATM -35 Configuring Manual Area Addresses -36 Configuring OSI and TARP -38 Configuring OSI over ATM To configure OSI to run over ATM, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, click on an ATM link module interface (ATM1). The Add Circuit window opens. 2. Click on OK. The Initial ATM Signaling Config window opens. 3. Edit any parameters you need to change. Click on Help for more information about any field. For OSI over ATM, Protocol Standard can be either UNI_V30 or UNI_V31. 4. Click on OK. The Edit ATM Connector window opens. 5. Click on Service Attributes. The ATM Service Records List window opens. 6. Click on Add. The ATM Service Record Parameters window opens. 7. Set the Data Encapsulation Type parameter to LLC/SNAP or NLPID. 8. Press the Enter or Tab key to advance to the Virtual Connection Type parameter. 9. Set the Virtual Connection Type parameter to PVC. (continued) 300020-B Rev. 00 35 BayRS Version 12.20 Document Change Notice Site Manager Procedure (continued) You do this System responds 10. Click on OK. The Select Protocols window opens. 11. Click on OSI, then click on OK. The OSI Configuration window opens. 12. Set the Router ID parameter. Click on Help for more information. 13. Click on OK. Site Manager asks if you want to edit the OSI interface details. 14. Click on OK to edit OSI interface parameters or Cancel to accept the default values. The ATM Virtual Channel Link window opens. 15. Click on Add. The ATM Virtual Channel Link Parameters window opens. 16. Set the VPI Number parameter. Click on Help for more information. 17. Set the VCI Number parameter. Click on Help for more information. 18. Click on OK. You return to the ATM Virtual Channel Link window. 19. Click on Done. You return to the ATM Service Records List window. 20. Click on Done. You return to the Edit ATM Connector window. 21. Click on Done. You return to the Configuration Manager window. Configuring Manual Area Addresses Manual area addresses are synonymous area addresses configured on the same intermediate system. You may want to configure manual area addresses when more than one addressing authority can assign addresses to the routing domain, or to allow a routing domain to be reconfigured during operation. Note: The OSI Area Address Alias 1 and Area Address Alias 2 parameters, used in previous releases to configure manual area addresses, no longer exist. 36 300020-B Rev. 00 Configuring OSI Services To configure manual area addresses for OSI, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols. The Protocols menu opens. 2. Choose OSI. The OSI menu opens. 3. Choose Manual Area Addresses. The OSI Area Address Configuration window opens. 4. Click on Add. The OSI Area Address Configuration Add window opens. 5. Enter an area address. Click on Help or see the parameter description below for more information. 6. Click on OK. 7. To add more area addresses, repeat steps 4 through 6. 8. Click on Done. Site Manager adds the addresses you specified. Parameter: Area Address Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Manual Area Addresses None Any valid OSI address in hexadecimal notation from 3 to 13 bytes long Specifies a synonymous area address configured on the same intermediate system. Instructions: Enter an area address in hexadecimal notation. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.1.16 300020-B Rev. 00 37 BayRS Version 12.20 Document Change Notice Configuring OSI and TARP OSI uses the TID Address Resolution Protocol (TARP) to map OSI network service access point (NSAP) Level 3 addresses to target identifier (TID) addresses. It is similar to the DNS protocol that IP uses, where names are converted to IP addresses. A TID is a name that applies to an entire router. It can be any text string, up to 40 characters long, and is similar to a UNIX host name. OSI addresses also apply to an entire router. An OSI NSAP address consists of the domain address, area address, the router ID, and a value called the N selector, which is always 00. It can be up to 13 bytes long. TARP locates either the OSI NSAP address of a particular TID address or the TID address of a particular OSI NSAP address. How TARP Works TARP resolves the NSAP-to-TID mapping by flooding requests that network management stations originate throughout the OSI domain. When a request reaches the network entity that owns the requested TID or NSAP, that entity sends a response that contains its NSAP and TID back to the originator. When the management station obtains the address it requested, it can proceed with its operation, such as polling the device for alarms. The router’s role is to propagate the requests throughout the network, forwarding them to Level 1 or Level 2 adjacencies, as appropriate. TARP Packet Types TARP has five types of packets (Table 2). Table 2. TARP Packet Types Packet Type Function Type 1 Request for the OSI NSAP address that maps to the TID address that the request packet supplies. Type 1 requests are only flooded within the originating network entity’s routing area (Level 1 adjacencies). Type 2 Same request as Type 1, but the requests are flooded throughout the OSI domain (both Level 1 and Level 2 adjacencies). (continued) 38 300020-B Rev. 00 Configuring OSI Services Table 2. TARP Packet Types (continued) Packet Type Function Type 3 Response to either a Type 1, Type 2, or Type 5 request. This response is sent directly to the originator of the request. Type 4 Notification of a change made to either the TID or NSAP address of a network entity. Type 4 packets are flooded throughout the OSI domain. Type 5 Request for the TID that maps to the OSI NSAP address included in the request packet. Because the destination NSAP is known, the request is sent directly to the network entity. TARP Packet Fields Each TARP packet includes the following fields (Table 3): Table 3. 300020-B Rev. 00 TARP Packet Fields Name Length in Bytes Description tar_lif 2 TARP lifetime (hops). If the network entity receives a TARP packet with a tar_lif field equal to 0, it discards the packet. Before forwarding a TARP packet, a receiving device decrements this field by 1. If the field then has a value of 0, it can drop the packet rather than forwarding it to a recipient that will drop it. tar_seq 2 TARP sequence number. The originating network entity assigns a sequence number to each packet it originates. For each new packet, the sequence number increments by 1. tar_pro 1 Protocol Address Type. This field must have a value of FE. tar_tcd 1 TARP type code. The type of TARP packet. tar_tln 1 Target TID length. The number of octets present in the tar_tor field. tar_oln 1 Originator TID length. The number of octets present in the tar_tor field. tar_pln 1 NSAP length. The number of octets in the tar_por field. tar_ttg N Target TID. tar_tor N Originator TID. tar_por N NSAP of originator. 39 BayRS Version 12.20 Document Change Notice Originating TARP Requests For the router to act as a TARP client, it must be able to originate all five types of packets. The router maintains a data cache that contains the results of TARP requests it has made and generates a Type 3 response to Type 1 or Type 5 packets. The router also generates TARP requests via Technician Interface commands. Before they send out a TARP request, the TARP entities check the TARP data network’s caches for a mapping and send out the request only if they do not find one. Because the main purpose of the Bay Networks implementation of TARP is to forward TARP packets, the router originates TARP requests for debugging purposes only, and so sends out requests whether or not there is a match in the data cache. Finding an NSAP If you use the -f option with the Technician Interface tarp pkt command on the router, you can learn the NSAP of a particular TID. The router sends a Type 1 packet to all Level 1 OSI adjacencies, and the T1 timer is set. If T1 expires before the router receives a response, it sends a Type 2 request to all Level 1 and Level 2 OSI adjacencies, and the T2 timer is set. If T2 expires before the router receives a response, the T4 timer is started, and an error recovery procedure begins. When the T4 timer expires, the router generates a second Type 2 request, and the T2 timer starts again. If T2 expires before the router receives a response, the router reports back to the application that the TID could not be resolved. Finding a TID To learn the TID of a particular NSAP, the router sends a Type 5 packet. Because it knows the destination NSAP, it does not flood the request out all adjacencies. It sends the Type 5 request directly to that NSAP, and starts the T3 timer. If the T3 timer expires before the router receives a response, the router reports back to the application that the NSAP could not be resolved. 40 300020-B Rev. 00 Configuring OSI Services Receiving TARP Requests After OSI processes an inbound OSI packet and determines that it is a TARP packet, the TARP software examines the packet. If the tar_lif field has a value of 0, it discards the packet. If the tar_pro field has a value other than FE, it discards the packet. It performs the loop detection procedure on the tar_seq field. If the packet passes all of these checks, TARP then checks to see if the packet is for itself as follows: 300020-B Rev. 00 • If the tar_tcd field has a value of 1 or 2 and the tar_ttg field is the router’s TID, the request is for this router. It responds with a Type 3 packet. • If the tar_tcd field has a value of 3, it is either for this router or it could be a Type 3 response packet to another router. The router checks to see whether it has any outstanding requests of Type 1, 2, or 5 that match this response. If so, it removes the request from the queue of outstanding requests that it has sent and creates an entry in the TARP data cache for the NSAP/TID pair the response describes. If not, it drops the packet. • If the tar_tcd field has a value of 4, the router processes and floods it to its adjacencies. It checks the TARP data cache for an entry that matches the TID in the tar_tor field. If found, it updates the TID/NSAP pair in the data cache with the new information. Then it floods the Type 4 packet to all of its Level 1 and Level 2 adjacencies, except the one that sent the packet, and resets the sequence number of this packet. • If the tar_tcd field has a value of 5, it is a request for this router’s TID. The router responds with a Type 3 packet or by forwarding a Type 5 packet to another router. • If none of the above cases is true, the router forwards the packet to its appropriate adjacencies. 41 BayRS Version 12.20 Document Change Notice Loop Detection To prevent TARP storms and recursive loops in a looped topology, TARP maintains a loop detection buffer that keeps a record of the last sequence number received from a particular NSAP. It checks each TARP PDU that it receives against any corresponding entry in the loop detection buffer. If it finds no match: • It processes the packet and adds a new entry to the loop detection buffer. • It checks the tar_seq field. If the value is 0, it starts a timer set to the value you configure for the TARP LDB timer. When this timer expires, the entry is removed. If there is a match, TARP compares the tar_seq value in the received packet with the value in the LDB entry. • If the packet’s tar_seq value is nonzero and is lower than the value in the buffer, it discards the packet. • If the packet’s tar_seq value is greater than the value in the buffer, TARP processes the packet and assigns this tar_seq value to the buffer. • If the packet’s tar_seq value is 0 and the TARP LDB timer is running, TARP discards the packet. If the timer is not running, the tar_seq remains 0 and the TARP LDB timer is started. Loop Detection Buffer Size You can configure the maximum number of entries for the loop detection buffer. When a loop detection buffer that contains the maximum number of entries receives a new entry, TARP removes the oldest entry. Loop Detection Timer Each tar_seq field with a value of 0 has an associated timer, the TARP LDB timer, that you can configure. When this timer expires, TARP removes the entry from the buffer. 42 300020-B Rev. 00 Configuring OSI Services Flush Timer The loop detection buffer also has a flush timer. When it expires, TARP empties the entire buffer. You can configure this timer to any value from 0 to 1440 minutes. The default value is 5 minutes. Configuring TARP You can use Site Manager to configure TARP parameters. However, to originate TARP requests and to view the contents of the TARP data caches and the L2 data cache, you must use the Technician Interface. To configure TARP, you need to provide a target ID (TID) for the first circuit you configure. All other parameters have default values, which you can edit to suit the requirements of your network. Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose a link or net module. The Add Circuit window opens. 2. Click on OK. The Select Protocols window opens. 3. Choose OSI and TARP, then click on OK. The OSI Configuration window opens. 4. Set the Router ID parameter. Click on Help or see the parameter description on page -48. 5. Click on OK. A dialog box prompts: “Do you want to edit the OSI Interface details?” 6. Click on Cancel. The TARP Parameters window opens. 7. Set the Target Identifier parameter. Click on Help or see the parameter description on page -49. 8. Click on OK. The Edit OSI Interface window opens. 9. Accept the defaults, or edit the parameters You return to the Configuration Manager as your network requires. When you are window. finished, click on OK. 300020-B Rev. 00 43 BayRS Version 12.20 Document Change Notice Editing TARP Global Parameters To edit TARP global parameters, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols > OSI > Tarp > Global. The Edit TARP Global Parameters window opens. 2. Edit one or more of the following parameters: • Enable • Target Identifier • Tarp Originate • Pkt Lifetime • Start Sequence Number • Tarp Data Cache • Tarp L2 Data Cache • Tarp T1 Timer • Tarp T2 Timer • Tarp T3 Timer Click on Help or see the parameter descriptions beginning on page -48. 3. When you are finished, click on OK. 44 You return to the Configuration Manager window. 300020-B Rev. 00 Configuring OSI Services Editing TARP Circuit Parameters To edit TARP circuit parameters, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols > OSI > Tarp > Circuits. The TARP Interface Lists window opens. 2. Edit any of the following parameters: • Enable • Circuit Propagate Pkts • Circuit Originate Pkts Click on Help or see the parameter descriptions page -52. 3. Click on Done. You return to the Configuration Manager window. Adding or Deleting TARP Static Adjacencies To add a TARP static adjacency, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols > OSI > Tarp > ADJ TARP. The TARP Static Adjacencies window opens. 2. Click on Add. The Static Adjacencies Configuration window opens. 3. Set the Static Adjacent NSAP Address parameter. Include a 00 NSEL value at the end of the NSAP address. Click on Help or see the parameter description on page -53. 300020-B Rev. 00 4. Click on OK. The TARP Static Adjacencies window opens. 5. Click on Done. You return to the Configuration Manager window. 45 BayRS Version 12.20 Document Change Notice To delete a TARP static adjacency, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols > OSI > Tarp > ADJ TARP. The TARP Static Adjacencies window opens. 2. Select a static adjacency address, then click on Delete. The Static Adjacencies address is no longer visible. 3. Click on Done. You return to the Configuration Manager window. Configuring TARP to Ignore a Static Adjacency To configure TARP to ignore a defined static adjacency, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols > OSI > Tarp > ADJ Ignore. The TARP Ignore Adjacencies window opens. 2. Click on Add. The Ignore Adjacencies Configuration window opens. 3. Set the Ignore Adjacent NSAP Address parameter. Click on Help or see the parameter description on page -54. 46 4. Click on OK. You return to the TARP Ignore Adjacencies window. 5. Click on Done. You return to the Configuration Manager window. 300020-B Rev. 00 Configuring OSI Services To delete a TARP Ignore Adjacency setting, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols > OSI > Tarp > ADJ Ignore. The TARP Ignore Adjacencies window opens. 2. Select an ignore adjacency address, then click on Delete. The selected address is no longer visible. 3. Click on Done. You return to the Configuration Manager window. To enable or disable a TARP Ignore Adjacency setting, complete the following tasks: Site Manager Procedure You do this System responds 1. In the Configuration Manager window, choose Protocols > OSI > Tarp > ADJ Ignore. The TARP Ignore Adjacencies window opens. 2. Select an ignore adjacency NSAP address, then click on Values. The Values Selection window opens. 3. Set the Enable parameter. Click on Help or see the parameter description on page -53. 300020-B Rev. 00 4. Click on OK. The TARP Ignore Adjacencies window opens. 5. Click on Done. You return to the Configuration Manager window. 47 BayRS Version 12.20 Document Change Notice TARP Parameter Descriptions This section describes TARP parameters. This is the same information you receive using Site Manager online Help. TARP Global Parameters This section describes TARP global parameters. Parameter: Router ID Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Global The router ID set when you initially enable OSI services Any valid 6-byte system ID Identifies the router within its local area. The system ID is the ID portion of the router’s NSAP address. Instructions: You specify the router ID only the first time you configure an OSI interface. Site Manager uses this router ID for any additional interfaces you configure. Enter a new 6-byte system ID in hexadecimal format. If the ID is not 6 bytes, add leading zeros. Every router in a domain must have a unique system ID; using a router’s MAC address for the system ID meets this requirement. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.1.6 Parameter: Enable Path: Default: Options: Function: Instructions: Configuration Manager > Protocols > OSI > Tarp > Global Enable Enable | Disable Enables or disables TARP on this interface. If you want to use TARP on the interface, accept the default. Otherwise, choose Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.2 48 300020-B Rev. 00 Configuring OSI Services Parameter: Target Identifier Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global None Any text string from 4 to 40 characters (spaces not allowed) Identifies the router. This is the value that OSI TARP maps to the NSAP address. Instructions: Enter the name that identifies this router. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.4 Parameter: Tarp Originate Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global Enable Enable | Disable Specifies whether the router can originate TARP packets for this interface. The only reason for the router to originate TARP packets is for debugging purposes. A router can forward TARP packets even if it cannot originate TARP packets. Instructions: If you want the router to originate TARP packets, accept the default. Otherwise, choose Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.5 Parameter: Pkt Lifetime Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global 25 1 to 100 Specifies the maximum number of hops a TARP packet that this router originates can make. Instructions: Choose a value within the valid range, or accept the default value. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.6 300020-B Rev. 00 49 BayRS Version 12.20 Document Change Notice Parameter: Start Sequence Number Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global 1 1 to 65535 Each TARP packet that the router originates has a sequence number that increments by one for each packet sent. Instructions: Choose the number that you want the router to use for the first packet. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.7 Parameter: Tarp Data Cache Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global Enable Enable | Disable Specifies the Level 1 database of the TID-to-NSAP mappings that the router learns from requests it originates. When it receives a response, the TARP software stores the new entry in the data cache. The only reason to disable this parameter is to conserve resources. Instructions: Accept the default, or choose Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.10 Parameter: Tarp L2 Data Cache Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global Enable Enable | Disable Specifies the Level 2 database of the TID-to-NSAP mappings. This cache functions as a proxy to store mappings at remote sites. If the router receives a request that is not for it, but that is in the Level 2 cache, it responds to the request instead of flooding the request to all of its adjacencies. Instructions: Accept the default, or choose Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.11 50 300020-B Rev. 00 Configuring OSI Services Parameter: Tarp T1 Timer Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global 15 1 to 3600 Specifies the number of seconds the router waits for a response to a Type 1 request it originated. Instructions: Accept the default, or choose another value. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.12 Parameter: Tarp T2 Timer Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global 25 1 to 3600 Specifies the number of seconds the router waits for a response to a Type 2 request it originated. Instructions: Accept the default, or choose another value. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.13 Parameter: Tarp T3 Timer Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Global 40 1 to 3600 Specifies the number of seconds the router waits for a response to a Type 5 request it originated. Instructions: Accept the default, or choose another value. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.14.14 300020-B Rev. 00 51 BayRS Version 12.20 Document Change Notice TARP Circuit Parameters This section describes TARP circuit parameters. Parameter: Enable Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Circuits Enable Enable | Disable Enables TARP on this circuit. For TARP to operate properly, OSI must also be configured on this circuit. Instructions: To use TARP on the circuit, accept the default, Enable. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.15.1.2 Parameter: Circuit Propagate Pkts Path: Default: Options: Function: Instructions: MIB Object ID: Configuration Manager > Protocols > OSI > Tarp > Circuits Enable Enable | Disable Specifies whether this circuit can forward TARP packets. If you want this circuit to forward TARP packets, accept the default, Enable. 1.3.6.1.4.1.18.3.5.6.15.1.5 Parameter: Circuit Originate Pkts Path: Default: Options: Function: Instructions: MIB Object ID: 52 Configuration Manager > Protocols > OSI > Tarp > Circuits Enable Enable | Disable Specifies whether this circuit can originate TARP packets. If you want this circuit to originate TARP packets, accept the default, Enable. 1.3.6.1.4.1.18.3.5.6.15.1.6 300020-B Rev. 00 Configuring OSI Services TARP Static Adjacency Parameters This section describes TARP static adjacency parameters. Parameter: Enable Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Adj Tarp None Enable | Disable Enables the adjacency that you define using the Static Adjacent NSAP Address parameter. Instructions: The default, Enable, appears after you add a static adjacent NSAP address. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.17.1.2 Parameter: Static Adjacent NSAP Address Path: Default: Options: Function: Instructions: MIB Object ID: Configuration Manager > Protocols > OSI > Tarp > Adj Tarp None Any valid NSAP address Links the router to a specific NSAP address to which it forwards TARP packets. Enter the address in hexadecimal format. 1.3.6.1.4.1.18.3.5.6.17.1.3 TARP Ignore Adjacencies Parameters This section describes TARP ignore adjacency parameters. Parameter: Enable Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Adj Ignore None Enable | Disable Enables the router to ignore the static adjacency that you defined using the Ignore Adjacent NSAP Address parameter. Instructions: Select Enable or Disable. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.18.1.2 300020-B Rev. 00 53 BayRS Version 12.20 Document Change Notice Parameter: Ignore Adjacent NSAP Address Path: Default: Options: Function: Configuration Manager > Protocols > OSI > Tarp > Adj Ignore None Any valid NSAP address Specifies the adjacency that you want the router to ignore for purposes of forwarding TARP packets. Instructions: Enter the address in hexadecimal format. MIB Object ID: 1.3.6.1.4.1.18.3.5.6.18.1.3 Using the Technician Interface to Send TARP Requests To request that the router originate a TARP packet, you use the Technician Interface tarp pkt command. This command accepts the following arguments: -t Specifies the type of TARP packet to send (1, 2, 4, or 5). -i TID to include in the request. Valid only for Type 1, Type 2, and Type 4 packets. The request is for the NSAP that maps to this TID. -n NSAP to include in the request. Valid only for Type 4 or Type 5 packets. The request is for the TID that maps to this NSAP. -f Enables you to find an NSAP by going through a timer sequence (see “Finding an NSAP” on page -40). Using the Technician Interface to View TARP Data Caches The following commands display TARP data caches: 54 tarp ldb Displays the loop detection buffer entries. tarp tdc Displays the TARP data cache. 300020-B Rev. 00 Configuring PPP Services Configuring PPP Services The following sections describe amendments to Configuring PPP Services. Topic Page show ppp alerts -55 show ppp bad-packets -56 show ppp disabled -56 show ppp enabled -56 show ppp interfaces -57 show ppp ip -57 show ppp ipx -58 show ppp line -59 show ppp lqr -61 show ppp alerts The BCC show ppp alerts command displays information about PPP exception conditions. The output contains the following information: 300020-B Rev. 00 Circuit The circuit for which this command displays information. Slot/ /Conn Names the physical interface. Line State The operational state of this line. Protocol The currently active protocol on this circuit. State Indicates whether PPP is enabled or disabled on this circuit. 55 BayRS Version 12.20 Document Change Notice show ppp bad-packets The BCC show ppp bad-packets command displays information about invalid packets received on the specified circuit. The output contains the following information: Circuit Name The circuit for which this command displays information. # Bad Packets Number of invalid packets received. Last Bad Packet Information about the last invalid packet received. show ppp disabled The BCC show ppp disabled command displays information about the protocols disabled on the specified PPP circuit. The output contains the following information: Circuit The circuit for which this command displays information. Line # The line within the circuit to which this information applies. Protocol The protocol disabled on this line. State The operational state of this line. show ppp enabled The BCC show ppp enabled command displays information about the protocols enabled on the specified PPP circuit. The output contains the following information: 56 Circuit The circuit for which this command displays information. Line # The line within the circuit to which this information applies. Protocol The protocol enabled on this line. State The operational state of this line. 300020-B Rev. 00 Configuring PPP Services show ppp interfaces The BCC show ppp interfaces command displays configuration information for each type of interface configured on each circuit. The output contains the following information: Circuit The circuit for which this command displays information. Slot/ /Conn Names the physical interface. Driver State The operational state of the driver, if one is present. Protocol The protocol or protocols configured on this circuit. State The operational state of each configured protocol. Line State The operational state of each line in the circuit. show ppp ip The BCC show ppp ip command displays information about the PPP IP configuration. The output contains the following information: 300020-B Rev. 00 Circuit The circuit for which this command displays information. State The operational state of the interface. Local Config The IP address that this router wants to use. Local Address The IP address that the peer router wants the local router to use. Remote Config The IP address that this router wants the remote peer to use. Remote Address The IP address that the remote peer wants to use. 57 BayRS Version 12.20 Document Change Notice show ppp ipx The BCC show ppp ipx command displays information about the PPP IPX configuration. show ppp ipx config The show ppp ipx config command displays summary information about the PPP IPX configuration. The output contains the following information: Circuit The circuit for which this command displays information. State The operational state of the interface. Network Number The configured IPX network number. Remote Node The node number that the local router tells the remote peer to use if the peer sends a node number of 0. Routing Protocol The IPX routing protocol on the interface. show ppp ipx name-local The show ppp ipx name-local command displays information about the PPP IPX local router. The output contains the following information: 58 Circuit name Names the physical interface. State The operational state of the interface. Local Router Name The name of the local router. 300020-B Rev. 00 Configuring PPP Services show ppp ipx name-remote The show ppp ipx name-remote command displays information about the PPP IPX remote peer router. The output contains the following information: Circuit name Names the physical interface. State The operational state of the interface. Remote Router Name The name of the remote router. show ppp ipx negotiated The show ppp ipx negotiated command displays information about the PPP IPX negotiated connection. The output contains the following information: Circuit Names the physical interface. State The operational state of the interface. Network Number The negotiated IPX network number. Config Complete Indicates whether IPXCP converged on all required options. Routing Protocol The negotiated IPX routing protocol used on the link. show ppp line The BCC show ppp line command displays information about the PPP lines configured for the specified interface. show ppp line async-map The show ppp line async-map command displays information about the PPP async control character map configured for the specified interface. 300020-B Rev. 00 59 BayRS Version 12.20 Document Change Notice The output contains the following information: Circuit The circuit for which this command displays information. Slot/ /Conn Names the physical interface. Configured Async Map The configured value of the async control character map. Actual Async Map The actual value of the async control character map. show ppp line config The show ppp line config command displays information about the configured PPP line parameter values for the specified interface. The output contains the following information: Circuit The circuit for which this command displays information. Slot/ /Conn Names the physical interface. LCP The operational state of the Link Control Protocol. Restart Timer The number of seconds that the restart timer waits before retransmitting data. Echo Req Freq The number of seconds that the router waits between the transmission of echo-request packets. Echo Rep Loss The maximum number of unacknowledged echo-reply packets that the router transmits before declaring the point-to-point link down. Max Conf Req The maximum number of unacknowledged configure-request packets that the router transmits before assuming that the peer router on the other end of the link is unable to respond. Max Term Req The maximum number of unacknowledged terminate-request packets that the router transmits before assuming that the peer router on the other end of the link is unable to respond. Max Conf Fail The maximum number of configure-NAK packets that the router transmits before sending a configure-reject packet for those options that it does not agree with. show ppp line params The show ppp line params command displays information about the PPP line parameters configured for the specified interface. 60 300020-B Rev. 00 Configuring PPP Services The output contains the following information: Circuit The circuit for which this command displays information. Slot/ /Conn Names the physical interface. LCP The operational state of the Link Control Protocol. Magic Number The operational state of the loopback test that the peer normally performs as part of its network integrity checking. MRU The maximum receive unit size. Local Auth. Prot The type of authentication protocol that this interface uses. Remote Auth. Prot. The type of authentication protocol that the remote peer uses. show ppp lqr The BCC show ppp lqr command displays information about the configured PPP link quality values for the specified interface. show ppp lqr config The show ppp lqr config command displays information about the PPP link quality reporting configured for the specified interface. The output contains the following information: 300020-B Rev. 00 Circuit The circuit for which this command displays information. Slot/ /Conn Names the physical interface. LQ Protocol The Link Quality Protocol used on this interface. Remote Timer Specifies whether the remote peer runs the link quality report timer. LQR Repeat Period The maximum number of seconds between the transmission of LQR packets. Inbound Quality The minimum acceptable success rate (percentage) of packets that the peer router sent and this router received on this interface over the last five LQR reporting periods. Outbound Quality The minimum acceptable success rate (percentage) of packets that this router sent on this interface and the peer router received. 61 BayRS Version 12.20 Document Change Notice show ppp lqr stats The show ppp lqr stats command displays information about the PPP link quality reporting statistics for the specified interface. The output contains the following information: Circuit The circuit for which this command displays information. Slot/ /Conn Names the physical interface. LCP State The operational state of the Link Control Protocol. LQR Repeat Period The maximum number of seconds between the transmission of LQR packets. Inbound Quality The minimum acceptable success rate (percentage) of packets that the peer router sent and this router received on this interface over the last five LQR reporting periods. Outbound Quality The minimum acceptable success rate (percentage) of packets that this router sent on this interface and the peer router received. 62 LQR In The current inbound quality. LQR Out The current outbound quality. 300020-B Rev. 00 Event Messages for Routers Event Messages for Routers Table 4 lists the service and entity names that correspond to the new or amended sections in Event Messages for Routers. Table 4. New and Amended Event Messages Service Entity Section Page ATM Half Bridge AHB AHB Fault Events AHB Warning Events AHB Info Events -66 -70 -73 ATM LAN Emulation ATM_LE ATM_LE Warning Events ATM_LE Info Events -74 -75 Border Gateway Protocol BGP BGP Warning Event -75 Carrier Sense Multiple Access/ Collision Detection CSMACD CSMACD Info Event -76 RMON Data Collection Module (DCM) Middleware DCMMW DCMMW Fault Event DCMMW Warning Events -76 -77 Domain Name System DNS DNS Fault Event DNS Info Event -77 -78 Data Path DP DP Warning Events DP Info Events DP Trace Event -78 -79 -81 Multichannel T1/EI Driver Service DS1E1 DS1E1 Warning Event -82 Bay Dial VPN Services DVS DVS Warning Event DVS Info Events -82 -82 Frame Relay PVC Pass Through Events FRPT FRPT Fault Event FRPT Warning Events FRPT Info Events FRPT Trace Event -83 -84 -85 -88 Frame Relay Switched Virtual Circuits FR_SVC FR_SVC Fault Event FR_SVC Warning Event FR_SVC Info Events -89 -89 -90 (continued) 300020-B Rev. 00 63 BayRS Version 12.20 Document Change Notice Table 4. New and Amended Event Messages (continued) Service Entity Section Page Frame Relay Switched Virtual Circuits API FR_SVC_API FR_SVC_API Warning Events FR_SVC_API Info Events FR_SVC_API Trace Events -91 -92 -93 Generic Routing Encapsulation GRE GRE Fault Events GRE Warning Events GRE Info Events -94 -94 -95 Hypertext Transfer Protocol HTTP HTTP Fault Event HTTP Warning Events HTTP Info Events HTTP Trace Events -95 -96 -97 -98 Intelligent Serial Daughter Board ISDB ISDB Fault Events ISDB Warning Events ISDB Info Events -102 -103 -105 Layer 2 Tunneling Protocol L2TP L2TP Fault Event L2TP Warning Events L2TP Info Events L2TP Trace Events -107 -108 -111 -113 Learning Bridge LB LB Warning Event -115 Dynamic Loader LOADER LOADER Info Events -115 Mobile IP MIP MIP Fault Event MIP Warning Events MIP Info Events -116 -117 -118 Multiple Protocol Over MPS ATM Server MPS Fault Events MPS Warning Events MPS Info Events -120 -121 -124 Network Link State Protocol NLSP NLSP Info Event -126 Open Shortest Path First OSPF OSPF Fault Events OSPF Warning Events OSPF Info Event -127 -128 -129 Point-to-Point Protocol PPP PPP Warning Events -129 FireWall-1 RFWALL RFWALL Warning Events RFWALL Info Events RFWALL Trace Event -130 -131 -131 RMONSTAT RMONSTAT RMONSTAT Info Event -132 (continued) 64 300020-B Rev. 00 Event Messages for Routers Table 4. New and Amended Event Messages (continued) Service Entity Section Page STAC LZS STAC_LZS STAC_LZS Fault Event STAC_LZS Warning Events STAC_LZS Info Events STAC_LZS Trace Event -132 -133 -134 -135 STAC PPP STAC_PPP STAC_PPP Fault Event STAC_PPP Warning Events STAC_PPP Info Events STAC_PPP Trace Event -135 -136 -138 -139 802.1Q TAG1.Q TAG1.Q Fault Event TAG1.Q Warning Event TAG1.Q Info Events TAG1.Q Trace Event -139 -139 -140 -145 Telnet server TELNET TELNET Fault Event TELNET Warning Event TELNET Info Events TELNET Trace Events -146 -146 -147 -149 Virtual circuit service VCCT for DLSw/APPN Boundary functionality VCCT Fault Event -150 WAN Compression Protocol WCP WCP Fault Event WCP Warning Events WCP Info Events WCP Trace Event -150 -151 -154 -155 X.25 PAD X.25_PAD X.25_PAD Fault Event X.25_PAD Warning Event X.25_PAD Info Event X.25_PAD Trace Event -155 -156 -157 -157 In addition, the following change applies to the definition of “Trace” events provided in Event Messages for Routers: Former (incorrect) definition -- Trace indicates information about each packet that traversed the network. Bay Networks recommends viewing this type of trap message only when diagnosing network problems. 300020-B Rev. 00 65 BayRS Version 12.20 Document Change Notice Corrected definition -- A series of related, time-stamped Trace messages describe the progress of a specific process running in the device software. A progression of Trace messages may indicate either a normal or abnormal sequence in the operation of any internal process. Trace messages for a specific entity (for example, a protocol) collectively depict the general health of that entity. For this reason, and because of the amount of information that Trace messages collectively record, Bay Networks recommends viewing them only when necessary for the purpose of troubleshooting device operation. AHB Fault Events ATM Half Bridge, also known as the AHB entity, issues the following fault event messages. The entity code assigned to AHB events is 149. 66 Entity Code/Event Code 149/6 Decimal Identifier 16815366 Severity: Fault Message: Unable to initialize BTM Meaning: AHB was unable to initialize the bridge table manager (BTM). This condition may be caused by insufficient memory resources. Check system memory usage. Action: Contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 149/7 Decimal Identifier 16815367 Severity: Fault Message: Bad opcode in BTM update mesg, message ignored. Meaning: Internal error occurred. Action: Contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 149/8 Decimal Identifier 16815368 Severity: Fault Message: Duplicate host sequence number detected, terminating Meaning: An attempt was made to add a new bridge table entry and the unique serial number assigned was already in use by another bridge table entry. Action: Contact the Bay Networks Technical Solutions Center. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 149/9 Decimal Identifier 16815369 Severity: Fault Message: Unable to add network to local bridge table. Meaning: Unable to add a new IP network in the bridge table. This condition may be caused by insufficient memory resources. Action: Check system memory usage. Entity Code/Event Code 149/10 Decimal Identifier 16815370 Severity: Fault Message: Unable to add remote network mask on slots Meaning: Unable to add a new IP network in the bridge table. This condition may be caused by insufficient memory resources. Action: Check system memory usage. Entity Code/Event Code 149/11 Decimal Identifier 16815371 Severity: Fault Message: Unable to delete network mask , slot , ignored Meaning: Unable to delete a new IP network in the bridge table. This condition may be caused by insufficient memory resources. Action: Check system memory usage. Entity Code/Event Code 149/12 Decimal Identifier 16815372 Severity: Fault Message: No circuit available when inserting route for net , mask , circuit Meaning: No available AHB circuit could be found when adding a new route entry in the IP routing table. Action: Check to make sure that at least one AHB circuit is in the up state. 300020-B Rev. 00 67 BayRS Version 12.20 Document Change Notice 68 Entity Code/Event Code 149/13 Decimal Identifier 16815373 Severity: Fault Message: Insert route failed for net , mask , circuit Meaning: Unable to insert an AHB-type route in the IP routing table. Action: Check to be sure IP is loaded and operational on the local slot, and that the circuit identified in this message is in the up state. Entity Code/Event Code 149/14 Decimal Identifier 16815374 Severity: Fault Message: Delete route failed for net , mask , circuit Meaning: Unable to remove an AHB-type route from the IP routing table. Action: Check to be sure IP is loaded and operational on the local slot. Entity Code/Event Code 149/15 Decimal Identifier 16815375 Severity: Fault Message: Unable to get buffer for map message data . Meaning: No buffers are available for control data. Action: Restart AHB. Entity Code/Event Code 149/16 Decimal Identifier 16815376 Severity: Fault Message: Unable to add new VC to cct Meaning: Unable to add a new ATM PVC as directed by the AHB initialization file. Action: Verify that ATM is configured properly, and that the maximum number of VCs on this circuit has not been exceeded. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 149/17 Decimal Identifier 16815377 Severity: Fault Message: Unable to get circuit info Meaning: Unable to obtain information about the circuit identified in the message. Action: Contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 149/18 Decimal Identifier 16815378 Severity: Fault Message: File Read Error Code Meaning: Error occurred during reading of AHB initialization file (or alternate initialization file). Action: Verify that AHB can read the existing initialization data file. Entity Code/Event Code 149/19 Decimal Identifier 16815379 Severity: Fault Message: Child gate died, type= , subsystem restarting Meaning: AHB terminated abnormally. Action: None Entity Code/Event Code 149/20 Decimal Identifier 16815380 Severity: Fault Message: Bad message ID received by master gate, ignored. Meaning: An unrecognized control message was received by AHB. Action: If this problem persists, contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 149/21 Decimal Identifier 16815381 Severity: Fault Message: Failed send to master gate, killing myself. Meaning: An internal error occurred. Action: Contact the Bay Networks Technical Solutions Center. 300020-B Rev. 00 69 BayRS Version 12.20 Document Change Notice Entity Code/Event Code 149/22 Decimal Identifier 16815382 Severity: Fault Message: Unable to add AHB cct . Meaning: An internal error occurred. Action: Contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 149/23 Decimal Identifier 16815383 Severity: Fault Message: Proxy reregistration error. Meaning: An internal error occurred. Action: Contact the Bay Networks Technical Solutions Center. AHB Warning Events ATM Half Bridge, also known as the AHB entity, issues the following warning event messages. The entity code assigned to AHB events is 149. 70 Entity Code/Event Code 149/24 Decimal Identifier 16815384 Severity: Warning Message: Circuit not found while adding ATM PVCs. Meaning: The circuit identified in the bridge entry could not be found when attempting to create a new PVC (as directed by the host entry in the initialization file). Action: Verify that you configured the identified circuit. Entity Code/Event Code 149/25 Decimal Identifier 16815385 Severity: Warning Message: AHB interface not found for circuit . Meaning: The AHB interface identified by circuit number could not be located when an attempt was made to add a new bridge table entry. Action: Contact the Bay Networks Technical Solutions Center. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 149/26 Decimal Identifier 16815386 Severity: Warning Message: Unable to set inbound filtering, no ATM control for circuit . Meaning: An internal error occurred. Action: Contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 149/27 Decimal Identifier 16815387 Severity: Warning Message: Unsupported encaps type on circuit . Meaning: AHB was configured on an ATM service record that uses an encapsulation type other than RFC 1483 SNAP/LLC. This interface will not be used. Action: Check the configuration of the ATM service record on which AHB is configured. Entity Code/Event Code 149/28 Decimal Identifier 16815388 Severity: Warning Message: Reference VC on circuit not found. Meaning: The reference PVC to be used as a template when creating a new ATM PVC could not be located on the router. The VPI/VCI for this reference PVC is identified within a host entry in the AHB initialization file. Action: Check the ATM PVC list on this service record to verify that you configured the VPI/VCI, then reload AHB. Entity Code/Event Code 149/29 Decimal Identifier 16815389 Severity: Warning Message: Error reading SLOT data, line . Meaning: Missing or invalid slot label in AHB initialization file. Action: Check the syntax for the identified line number. 300020-B Rev. 00 71 BayRS Version 12.20 Document Change Notice 72 Entity Code/Event Code 149/30 Decimal Identifier 16815390 Severity: Warning Message: Error reading data, line . Meaning: Invalid host entry in AHB initialization file. Action: Check the syntax for the identified line number. Entity Code/Event Code 149/31 Decimal Identifier 16815391 Severity: Warning Message: No AHB base record configured. Meaning: The AHB base MIB object could not be located. Action: Verify that the configuration file exists prior to rebooting. Entity Code/Event Code 149/32 Decimal Identifier 16815392 Severity: Warning Message: Failed to open file , using alternate Meaning: The initialization file identified in the AHB base record could not be read. Action: Verify that this file exists on the router’s flash file system. Entity Code/Event Code 149/33 Decimal Identifier 16815393 Severity: Warning Message: Failed to open file , giving up. Meaning: The alternate initialization file identified in the AHB base record could not be read. Action: Verify that this file exists on the router’s flash file system. 300020-B Rev. 00 Event Messages for Routers AHB Info Events ATM Half Bridge, also known as the AHB entity, issues the following info event messages. The entity code assigned to AHB events is 149. Entity Code/Event Code 149/34 Decimal Identifier 16815394 Severity: Info Message: AHB interface is up. Meaning: The AHB interface is operational and ready to forward packets in either direction. Entity Code/Event Code 149/35 Decimal Identifier 16815395 Severity: Info Message: AHB interface is down. Meaning: The AHB interface is not operational. Action: Check the ATM line status and ATM circuit status. Entity Code/Event Code 149/36 Decimal Identifier 16815396 Severity: Info Message: Reading from data file Meaning: AHB is now reading the initialization file. This condition occurs after you first load the subsystem or after you perform a reset operation. Entity Code/Event Code 149/37 Decimal Identifier 16815397 Severity: Info Message: Finished reading data file. Meaning: AHB has finished reading the initialization file. The bridge table is now populated with all bridge entries identified in the initialization file. 300020-B Rev. 00 73 BayRS Version 12.20 Document Change Notice Entity Code/Event Code 149/38 Decimal Identifier 16815398 Severity: Info Message: AHB initialization complete Meaning: AHB has initialized and is now operational on the local slot. Entity Code/Event Code 149/39 Decimal Identifier 16815399 Severity: Info Message: Read_data: waiting 10 seconds for IP. Meaning: AHB is waiting for IP to become operational prior to reading the initialization file. Action: If this event persists, verify that IP is loaded and operational on the current slot. ATM_LE Warning Events The ATM LAN Emulation service, also known as the ATM_LE entity, supports the following warning event messages. The entity code assigned to ATM_LE events is 100. 74 Entity Code/Event Code 100/52 Decimal Identifier 16802868 Severity: Warning Message: Line : Circuit : Instance LES is unreachable. Meaning: The indicated LES is not responding. Entity Code/Event Code 100/54 Decimal Identifier 16802870 Severity: Warning Message: Line : Circuit : ATM LEC now trying next le server. Meaning: The ATM LAN emulation client is trying the next configured LAN emulation server (LES). 300020-B Rev. 00 Event Messages for Routers ATM_LE Info Events The ATM LAN Emulation service, also known as the ATM_LE entity, supports the following info event messages. The entity code assigned to ATM_LE events is 100. Entity Code/Event Code 100/50 Decimal Identifier 16802866 Severity: Info Message: Line : Circuit : Instance LES is deleted. Meaning: The indicated LES has been deleted. Entity Code/Event Code 100/51 Decimal Identifier 16802867 Severity: Info Message: Line : Circuit : Instance LES is disabled. Meaning: The indicated LES is disabled. BGP Warning Event The Border Gateway Protocol service, also known as the BGP entity, supports the following warning event message. The entity code assigned to BGP events is 52. Entity Code/Event Code 52/215 Decimal Identifier 16790743 Severity: Warning Message: Cluster loop detected on . Meaning: BGP has detected a loop in a route reflector cluster. Action: Check your AS configuration. 300020-B Rev. 00 75 BayRS Version 12.20 Document Change Notice CSMACD Info Event The Carrier Sense Multiple Access/Collision Detection service, also known as the CSMACD entity, supports the following info message. The entity code assigned to CSMACD events is 9. Entity Code/Event Code 9/44 Decimal Identifier 16779564 Severity: Info Message: Connector XCVR : XCHIP and THUNDERSwitchInterface Initialization Complete Meaning: The XCHIP and THUNDERSwitch have been initialized on the CSMA/CD connector identified by XCVR . DCMMW Fault Event The RMON data collection module (DCM) middleware, also known as the DCMMW entity, supports the following new fault event message. The entity code assigned to DCMMW events is 96. 76 Entity Code/Event Code 96/88 Decimal Identifier 16801880 Severity: Fault Message: DCMMW_NO_CSMACD Meaning: You must configure the Ethernet interface before you attempt to configure the Ethernet DCM on the router. Action: Configure an Ethernet interface before configuring the Ethernet DCM on the router. 300020-B Rev. 00 Event Messages for Routers DCMMW Warning Events The RMON data collection module (DCM) middleware, also known as the DCMMW entity, supports the following new warning event messages. The entity code assigned to DCMMW events is 96. Entity Code/Event Code 96/89 Decimal Identifier 16801881 Severity: Warning Message: DCMMW_DCM_BAD_VERSION Meaning: An older version of the Ethernet DCM image is running on the router. Action: Upgrade the Ethernet DCM image to Version 2.00.1 to run RMON or RMON2 on the router. Entity Code/Event Code 96/90 Decimal Identifier 16801882 Severity: Warning Message: DCMMW_DCM_LOWMEM_RMON2 Meaning: There is insufficient memory available on the Ethernet DCM to collect RMON2 statistics. The Ethernet DCM will collect only RMON statistics. Action: Increase the Ethernet DCM’s memory to 8 MB to collect RMON2 statistics. DNS Fault Event The Domain Name System (DNS), also known as the DNS entity, issues the following fault event message. The entity code assigned to DNS events is 117. Entity Code/Event Code 117/1 Decimal Identifier 16807169 Severity: Fault Message: System error, service attempting restart. Meaning: The router experienced a fatal error 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 Technical Solutions Center if the router fails to restart. 300020-B Rev. 00 77 BayRS Version 12.20 Document Change Notice DNS Info Event The Domain Name System (DNS), also known as the DNS entity, issues the following info event message. The entity code assigned to DNS events is 117. Entity Code/Event Code 117/3 Decimal Identifier 16807171 Severity: Info Message: Protocol initializing. Meaning: DNS has begun its initialization process. DP Warning Events The Data Path service, also known as the DP entity, issues the following modified and new warning messages. The entity code assigned to DP events is 6. 78 Entity Code/Event Code 6/69 Decimal Identifier 16778821 Severity: Warning Message: Priority Queuing Length Based Filter disabled, cannot use the LBP filter for IP Circuit . Meaning: A length-based filter was configured for IP. This is not allowed; therefore, the filter was disabled. Action: Remove this IP filter and specify IP-specific prioritizations. Entity Code/Event Code 6/83 Decimal Identifier 16778835 Severity: Warning Message: Line : MTU , not same circuit MTU , ignoring line. Meaning: You tried to group a line with a circuit group that had a different maximum transmission unit (MTU) value. Action: Change the MTU value of the line you are trying to add to match the MTU of the circuit group. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 6/93 Decimal Identifier 16778845 Severity: Warning Message: : Multiprotocol encapsulation is not configured for Bridging. Meaning: You must configure multiprotocol encapsulation (MPE) for this circuit. Action: Configure MPE for the ATM interface or circuit. Entity Code/Event Code 6/100 Decimal Identifier 16778852 Severity: Warning Message: The active IP accounting table is now percent full. Meaning: This message occurs when the active IP Accounting table reaches a specified percentage of its maximum number of unique entries. The warning prevents loss of information by enabling you to copy the active table to a checkpoint table and to reset the active table before it overflows. Note: You can configure both the maximum number of entries in the active IP Accounting table and the percentage of maximum entries to initiate this log message. For information, see Configuring IP Services or the Site Manager Help for these parameters. Action: Copy the active IP Accounting table to the checkpoint IP Accounting table by using SNMP commands to get the value of wfCkAcctFlag and reset it to the same value. This action flushes the active table, making space for new entries. DP Info Events The Data Path service, also known as the DP entity, issues the following modified and new info event messages. The entity code assigned to DP events is 6. Entity Code/Event Code 6/81 Decimal Identifier 16778833 Severity: Info Message: Line : added to group of lines for cct . Meaning: The specified connector was added to the specified number of lines that make up the specified circuit group. 300020-B Rev. 00 79 BayRS Version 12.20 Document Change Notice 80 Entity Code/Event Code 6/85 Decimal Identifier 16778837 Severity: Info Message: Last line in circuit died, circuit going down. Meaning: The last active line in a multiline circuit group has gone down, causing the circuit to go to the down state. Entity Code/Event Code 6/86 Decimal Identifier 16778838 Severity: Info Message: Line deleted from circuit , active lines left. Meaning: A line in a multiline circuit group has gone down, leaving only the specified number of active lines. Entity Code/Event Code 6/102 Decimal Identifier 16778854 Severity: Info Message: Firewall syn VM installed. Meaning: Firewall is active on this synchronous interface. Entity Code/Event Code 6/103 Decimal Identifier 16778855 Severity: Info Message: Firewall VM installed. Meaning: Firewall is active on this Ethernet interface. Entity Code/Event Code 6/104 Decimal Identifier 16778856 Severity: Info Message: Firewall 1294sync VM installed. Meaning: Firewall is active on this synchronous interface. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 6/105 Decimal Identifier 16778857 Severity: Info Message: Firewall FDDI VM installed. Meaning: Firewall is active on this FDDI interface. Entity Code/Event Code 6/106 Decimal Identifier 167788858 Severity: Info Message: Firewall Enet VM installed. Meaning: Firewall is active on this Ethernet interface. Entity Code/Event Code 6/107 Decimal Identifier 167788859 Severity: Info Message: Firewall PPP VM installed. Meaning: Firewall is active on this PPP interface. DP Trace Event The Data Path service, also known as the DP entity, issues the following trace event message. The entity code assigned to DP events is 6. Entity Code/Event Code 6/91 Decimal Identifier 16778843 Severity: Trace Message: cct : Outgoing pkt dropped; no header space. Meaning: The system received a packet from Ethernet or FDDI that was to be bridged over frame relay or ATM. When frame relay or ATM tried to add the necessary header information to the packet, there was not enough space for the header. Therefore, the system dropped the packet. Action: No action required. 300020-B Rev. 00 81 BayRS Version 12.20 Document Change Notice DS1E1 Warning Event The Multichannel T1/E1 driver service, referred to as the DS1E1 entity, issues the following warning event message. The entity code assigned to DS1E1 events is 63. Entity Code/Event Code 63/93 Decimal Identifier 16793437 Severity: Warning Message: Connector COM , current timeslot assigned is not supported. Meaning: On an ARN with a T1 or E1 card, and an ISDN card, the current assignment of DS0s for the T1 interface on this connector is invalid. Action: Have the service provider change the T1 channel assignments. You can also provision more contiguous channels. DVS Warning Event Bay Dial VPN service, also known as the DVS entity, issues the following warning event message. The entity code assigned to DVS events is 159. Entity Code/Event Code 159/5 Decimal Identifier 16817925 Severity: Warning Message: Meaning: Unexpected buffer or unexpected signal. DVS Info Events Bay Dial VPN service, also known as the DVS entity, issues the following info event messages. The entity code assigned to DVS events is 159. 82 Entity Code/Event Code 159/1 Decimal Identifier 16817921 Severity: Info Message: Protocol initializing. Meaning: DVS (Layer 3, Mobile IP Protocol) is loading on this slot. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 159/2 Decimal Identifier 16817922 Severity: Info Message: Protocol loaded. Meaning: DVS (Layer 3, Mobile IP Protocol) is loaded on this slot. Entity Code/Event Code 159/3 Decimal Identifier 16817923 Severity: Info Message: : DVS up on interface Meaning: DVS is operational on the indicated circuit on the indicated interface. Entity Code/Event Code 159/4 Decimal Identifier 16817924 Severity: Info Message: : DVS down on interface Meaning: DVS is not operational on the indicated circuit on the indicated interface. FRPT Fault Event The Frame Relay PVC Pass Through service, also known as the FRPT entity, issues the following fault event message. The entity code assigned to FRPT events is 143. Entity Code/Event Code 143/1 Decimal Identifier 16813825 Severity: Fault Message: System error, FRPT gate attempting restart. Meaning: The router experienced a fatal error 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 Technical Solutions Center if the router fails to restart. 300020-B Rev. 00 83 BayRS Version 12.20 Document Change Notice FRPT Warning Events The Frame Relay PVC Pass Through service, also known as the FRPT entity, issues the following warning event messages. The entity code assigned to FRPT events is 143. 84 Entity Code/Event Code 143/2 Decimal Identifier 16813826 Severity: Warning Message: Config error: New interface ignored, conflicts with . Meaning: A configuration error exists. This newly created mapping interface uses a circuit that already exists; each PVC configured for pass through must have a dedicated circuit. The router will not recognize the interface. Action: Reconfigure pass through so that each circuit participates in only one pass through mapping. Entity Code/Event Code 143/3 Decimal Identifier 16813827 Severity: Warning Message: Config error: New mapping ignored, interface(s) not found. Meaning: A configuration error exists. The specified pass through entry includes an interface that does not exist. Action: Reconfigure pass through to include only valid circuit numbers and DLCIs. Entity Code/Event Code 143/4 Decimal Identifier 16813828 Severity: Warning Message: Config error: New mapping ignored, interface(s) in use. Meaning: A configuration error exists. The new mapping entry specified includes at least one interface that already participates in a pass through mapping. Action: Reconfigure pass through to include each interface in only one mapping. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 143/5 Decimal Identifier 16813829 Severity: Warning Message: Interface detected unexpected death of partner ( ). Meaning: The specified interface has detected that the interface to which it maps has failed. Action: None required. Entity Code/Event Code 143/6 Decimal Identifier 16813830 Severity: Warning Message: Meaning: This is a generic warning message. FRPT Info Events The Frame Relay PVC Pass Through service, also known as the FRPT entity, issues the following info event messages. The entity code assigned to FRPT events is 143. Entity Code/Event Code 143/7 Decimal Identifier 16813831 Severity: Info Message: Service initializing. Meaning: Pass through service is starting up. Entity Code/Event Code 143/8 Decimal Identifier 16813832 Severity: Info Message: Service down. Meaning: Pass through service is not working. 300020-B Rev. 00 85 BayRS Version 12.20 Document Change Notice 86 Entity Code/Event Code 143/9 Decimal Identifier 16813833 Severity: Info Message: Interface initializing ( ). Meaning: The specified pass through interface is starting up. Entity Code/Event Code 143/10 Decimal Identifier 16813834 Severity: Info Message: Interface down ( ). Meaning: The specified pass through interface is not working. Entity Code/Event Code 143/11 Decimal Identifier 16813835 Severity: Info Message: Interface added ( ). Meaning: The specified pass through interface has been added to the network. Entity Code/Event Code 143/12 Decimal Identifier 16813836 Severity: Info Message: Interface deleted ( ). Meaning: The specified pass through interface has been deleted from the network. Entity Code/Event Code 143/13 Decimal Identifier 16813837 Severity: Info Message: Interface Enabled ( ). Meaning: The specified pass through interface is enabled. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 143/14 Decimal Identifier 16813838 Severity: Info Message: Interface Disabled ( ). Meaning: The specified pass through interface is disabled. Entity Code/Event Code 143/15 Decimal Identifier 16813839 Severity: Info Message: Interface unable to raise partner . Meaning: The specified pass through interface is unable to reach the interface to which it maps. Entity Code/Event Code 143/16 Decimal Identifier 16813840 Severity: Info Message: Mapping added ( ). Meaning: The specified mapping has been added to the network. Entity Code/Event Code 143/17 Decimal Identifier 16813841 Severity: Info Message: Mapping deleted ( ). Meaning: The specified mapping has been deleted from the network. Entity Code/Event Code 143/18 Decimal Identifier 16813842 Severity: Info Message: Mapping Enabled ( ). Meaning: The specified mapping is enabled. 300020-B Rev. 00 87 BayRS Version 12.20 Document Change Notice Entity Code/Event Code 143/19 Decimal Identifier 16813843 Severity: Info Message: Mapping Disabled ( ). Meaning: The specified mapping is disabled. Entity Code/Event Code 143/20 Decimal Identifier 16813844 Severity: Info Message: Mapping became Active ( ). Meaning: The specified mapping is active. Entity Code/Event Code 143/21 Decimal Identifier 16813845 Severity: Info Message: Mapping became Inactive ( ). Meaning: The specified mapping is inactive. FRPT Trace Event The Frame Relay PVC Pass Through service, also known as the FRPT entity, issues the following trace event message. The entity code assigned to FRPT events is 143. 88 Entity Code/Event Code 143/22 Decimal Identifier 16813846 Severity: Trace Message: Meaning: This is a generic message. 300020-B Rev. 00 Event Messages for Routers FR_SVC Fault Event The Frame Relay Switched Virtual Circuits service, also known as the FR_SVC entity, issues the following fault event message. The entity code assigned to FR_SVC events is 136. Entity Code/Event Code 136/1 Decimal Identifier 16812033 Severity: Fault Message: FR SVC System Error Meaning: The frame relay subsystem experienced a fatal error and is restarting automatically. Action: Verify that the configuration is correct. Call the Bay Networks Technical Solutions Center if the router fails to restart. FR_SVC Warning Event The Frame Relay Switched Virtual Circuits service, also known as the FR_SVC entity, issues the following warning event message. The entity code assigned to FR_SVC events is 136. Entity Code/Event Code 136/2 Decimal Identifier 16812034 Severity: Warning Message: Client registration error cct of type Meaning: The specified client registration error has occurred on the specified circuit. Action: Contact the Technical Solutions Center. 300020-B Rev. 00 89 BayRS Version 12.20 Document Change Notice FR_SVC Info Events The Frame Relay Switched Virtual Circuits service, also known as the FR_SVC entity, issues the following info event messages. The entity code assigned to FR_SVC events is 136. 90 Entity Code/Event Code 136/3 Decimal Identifier 16812035 Severity: Info Message: Service initializing Meaning: Frame relay SVC service is initializing. Entity Code/Event Code 136/4 Decimal Identifier 16812036 Severity: Info Message: Master gate down. Meaning: The frame relay master gate is down. Entity Code/Event Code 136/5 Decimal Identifier 16812037 Severity: Info Message: Frame relay SVC MIB initializing. Meaning: The frame relay SVC MIB is initializing. Entity Code/Event Code 136/6 Decimal Identifier 16812038 Severity: Info Message: Frame relay SVC sig ctrl initializing Meaning: The frame relay SVC signaling control function is initializing. Entity Code/Event Code 136/7 Decimal Identifier 16812039 Severity: Info Message: Frame relay SVC sig ctrl rcvd LAPF link up. Meaning: Frame relay SVC signaling control has received a message that the LAPF link is up. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 136/8 Decimal Identifier 16812040 Severity: Info Message: Frame relay SVC sig ctrl rcvd LAPF link down. Meaning: Frame relay SVC signaling control has received a message indicating that the LAPF link is down. FR_SVC_API Warning Events The Frame Relay SVC API service, also known as the FR_SVC_API entity, issues the following warning event messages. The entity code assigned to FR_SVC_API events is 146. Entity Code/Event Code 146/1 Decimal Identifier 16814593 Severity: Warning Message: Message sent to API Gate failed. Meaning: An internal message the router sent failed to reach the API gate. Action: Contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 146/2 Decimal Identifier 16814594 Severity: Warning Message: Frame relay master gate died. Meaning: The frame relay master gate failed. Action: Contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 146/7 Decimal Identifier 16814599 Severity: Warning Message: Unexpected error signalling Setup Gate. Meaning: An error occurred in trying to set up an SVC. Action: Contact the Technical Solutions Center. 300020-B Rev. 00 91 BayRS Version 12.20 Document Change Notice FR_SVC_API Info Events The Frame Relay SVC API service, also known as the FR_SVC_API entity, issues the following info event messages. The entity code assigned to FR_SVC_API events is 146. 92 Entity Code/Event Code 146/6 Decimal Identifier 16814598 Severity: Info Message: Connect confirm received from FR subsystem. Meaning: A connect confirmation message has been received from the frame relay subsystem. Entity Code/Event Code 146/9 Decimal Identifier 16814601 Severity: Info Message: Success message sent to Setup Gate. Meaning: The connection has completed successfully. Entity Code/Event Code 146/11 Decimal Identifier 16814603 Severity: Info Message: Q933 registration success received on cct . Meaning: Q933 has completed registration successfully on the specified circuit. Entity Code/Event Code 146/12 Decimal Identifier 16814604 Severity: Info Message: Q933 ack'd request . Meaning: Q933 has acknowledged the specified request. Entity Code/Event Code 146/13 Decimal Identifier 16814605 Severity: Info Message: CCT Gate on circuit registered. Meaning: The circuit gate on the specified circuit has registered. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 146/14 Decimal Identifier 16814606 Severity: Info Message: Request for a new SVC received. Meaning: The frame relay subsystem has received a request for a new SVC. Entity Code/Event Code 146/15 Decimal Identifier 16814607 Severity: Info Message: Request sent to signaling gate on circuit . Meaning: The frame relay subsystem has sent a request to the signaling gate on the specified circuit. FR_SVC_API Trace Events The Frame Relay SVC API service, also known as the FR_SVC_API entity, issues the following trace event messages. The entity code assigned to FR_SVC_API events is 146. Entity Code/Event Code 146/3 Decimal Identifier 16814595 Severity: Trace Message: lapf gate created. Meaning: The LAPF gate is created. Entity Code/Event Code 146/4 Decimal Identifier 16814596 Severity: Trace Message: lapf gate called. Meaning: The LAPF gate has been called. 300020-B Rev. 00 93 BayRS Version 12.20 Document Change Notice GRE Fault Event The Generic Routing Encapsulation service, referred to as the GRE entity, issues the following fault event message. The entity code assigned to GRE events is 114. Entity Code/Event Code 114/6 Decimal Identifier 16806406 Severity: Warning Message: Meaning: This is a fault message. GRE Warning Events The Generic Routing Encapsulation service, referred to as the GRE entity, issues the following warning event messages. The entity code assigned to GRE events is 114. 94 Entity Code/Event Code 114/5 Decimal Identifier 16806405 Severity: Warning Message: Meaning: This is a warning message. Entity Code/Event Code 114/17 Decimal Identifier 16806417 Severity: Warning Message: GRE tunnel misconfiguration caused internal loop - dropping packet Meaning: The GRE tunnel configuration caused an internal loop. Action: Reconfigure the GRE tunnel. 300020-B Rev. 00 Event Messages for Routers GRE Info Events The Generic Routing Encapulation service, referred to as the GRE entity, issues the following info event messages. The entity code assigned to GRE events is 114. Entity Code/Event Code 114/1 Decimal Identifier 16806401 Severity: Info Message: Meaning: This is a log message. Entity Code/Event Code 114/3 Decimal Identifier 16806403 Severity: Info Message: GRE up on interface Meaning: DVS is ready to receive tunneled traffic from the RAS. Entity Code/Event Code 114/4 Decimal Identifier 16806404 Severity: Info Message: GRE down on interface Meaning: DVS is no longer able to receive tunneled traffic from the RAS. HTTP Fault Event The HTTP Server software, referred to as the HTTP entity, issues the following fault event message. The entity code assigned to HTTP events is 145. Entity Code/Event Code 145/1 Decimal Identifier 16814337 Severity: Fault Message: System error, service attempting restart. Meaning: HTTP experienced a fatal error and is restarting automatically. Action: Verify that the configuration is correct. Call the Bay Networks Technical Solutions Center if HTTP fails to restart. 300020-B Rev. 00 95 BayRS Version 12.20 Document Change Notice HTTP Warning Events The HTTP Server software, referred to as the HTTP entity, issues the following warning event messages. The entity code assigned to HTTP events is 145. 96 Entity Code/Event Code 145/7 Decimal Identifier 16814343 Severity: Warning Message: Failed to initialize HTTP Server for host , remote port . Meaning: The HTTP Server for the indicated device and port failed to initialize. Entity Code/Event Code 145/8 Decimal Identifier 16814344 Severity: Warning Message: TCP failed to establish connection with host , remote port . Meaning: The indicated TCP connection did not open. Entity Code/Event Code 145/9 Decimal Identifier 16814345 Severity: Warning Message: TCP transmit returned bad status code . Meaning: TCP transmission returned an error, indicated by the status code. Entity Code/Event Code 145/10 Decimal Identifier 16814346 Severity: Warning Message: Authorization failed (AUTH_FAILED), HTTP status: 401 Unauthorized host
, port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: The indicated user is attempting to access an entity without having appropriate access privileges. The variables identify the protected entity, the user making the attempt, the referrer, and the user agent. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 145/11 Decimal Identifier 16814347 Severity: Warning Message: Bad msg digest (AUTH_FORGERY), HTTP status: 401 Unauthorized host , port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: The indicated user is attempting to access an entity without having appropriate access privileges. The variables identify the protected entity, the user making the attempt, the referrer, and the user agent. HTTP Info Events The HTTP Server software, referred to as the HTTP entity, issues the following info event messages. The entity code assigned to HTTP events is 145. Entity Code/Event Code 145/2 Decimal Identifier 16814338 Severity: Info Message: Protocol Initializing. Meaning: The HTTP protocol is initializing. Entity Code/Event Code 145/3 Decimal Identifier 16814339 Severity: Info Message: Server listening for requests on local port . Meaning: The HTTP Server is listening for requests on the indicated local port. Entity Code/Event Code 145/4 Decimal Identifier 16814340 Severity: Info Message: Server is disabled. Meaning: The HTTP Server is not enabled. 300020-B Rev. 00 97 BayRS Version 12.20 Document Change Notice Entity Code/Event Code 145/5 Decimal Identifier 16814341 Severity: Info Message: Adding user to group . Meaning: The specified user is being added to the indicated group. Entity Code/Event Code 145/6 Decimal Identifier 16814342 Severity: Info Message: Meaning: This message is a variable string that indicates one of several possible information messages. Entity Code/Event Code 145/32 Decimal Identifier 16814368 Severity: Info Message: Server not listening for requests on local port . Meaning: The HTTP Server has stopped listening for requests on the indicated interface. Entity Code/Event Code 145/33 Decimal Identifier 16814369 Severity: Info Message: Server down. Meaning: The HTTP Server is not operational. HTTP Trace Events The HTTP Server software, referred to as the HTTP entity, issues the following trace event messages. The entity code assigned to HTTP events is 145. 98 Entity Code/Event Code 145/12 Decimal Identifier 16814348 Severity: Trace Message: Loading archive . Meaning: The indicated archive is loading. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 145/13 Decimal Identifier 16814349 Severity: Trace Message: Rejecting connection from host . Meaning: A connection request from the indicated host has not been accepted. Entity Code/Event Code 145/14 Decimal Identifier 16814350 Severity: Trace Message: Opening connection with host , remote port . Meaning: The HTTP Server is opening a connection with the indicated host and port. Entity Code/Event Code 145/15 Decimal Identifier 16814351 Severity: Trace Message: Closing connection with host , remote port . Meaning: HTTP is closing a connection with the indicated host and port. Entity Code/Event Code 145/16 Decimal Identifier 16814352 Severity: Trace Message: TCP aborted with status = . Meaning: TCP abnormally terminated for the reason code shown in this message. Entity Code/Event Code 145/17 Decimal Identifier 16814353 Severity: Trace Message: Received unexpected TCP message, type
while in state. Meaning: HTTP received a TCP message unusual in this context. The variables indicate the type of message and the HTTP state. 300020-B Rev. 00 99 BayRS Version 12.20 Document Change Notice 100 Entity Code/Event Code 145/18 Decimal Identifier 16814354 Severity: Trace Message: Bad request (BAD_REQUEST), HTTP status: 400 Bad request host , port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: HTTP received an invalid request. The variables in the message indicate the source of the request, the user making the attempt, the referrer, and the user agent. Entity Code/Event Code 145/19 Decimal Identifier 16814355 Severity: Trace Message: Form data parse error (BAD_FORM), HTTP status: 400 Bad request host , port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: An error occurred in parsing form data. The request is invalid. The variables in the message indicate the source of the problem, the user making the attempt, the referrer, and the user agent. Entity Code/Event Code 145/20 Decimal Identifier 16814356 Severity: Trace Message: Bad imagemap (BAD_IMAGEMAP), HTTP status: 400 Bad request host , port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: A problem exists with an image map. The variables in the message indicate the source of the problem, the user making the attempt, the referrer, and the user agent. Entity Code/Event Code 145/21 Decimal Identifier 16814357 Severity: Trace Message: Archive not loaded (UNAVAILABLE), HTTP status: 503 Unavailable host , port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: The requested archive is not available. The variables in the message indicate the source of the problem, the user making the attempt, the referrer, and the user agent. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 145/22 Decimal Identifier 16814358 Severity: Trace Message: No resources (NO_RESOURCES), HTTP status: 503 Unavailable host , port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: The requested resource is not available. The variables in the message indicate the source of the problem, the user making the attempt, the referrer, and the user agent. Entity Code/Event Code 145/23 Decimal Identifier 16814359 Severity: Trace Message: Unknown EWS status code host
, port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: HTTP has received a nonstandard status code, indicated in the message. The variables in the message indicate the source of the problem, the user making the attempt, the referrer, and the user agent. Entity Code/Event Code 145/24 Decimal Identifier 16814360 Severity: Trace Message: Internal Error, HTTP status: 500 Internal Error host , port , URL ' ', method ' ' realm , user , Referer: ' ', User-agent: ' ' Meaning: An error internal to HTTP has occurred. The variables in the message indicate the source of the problem, the user making the attempt, the referrer, and the user agent. 300020-B Rev. 00 101 BayRS Version 12.20 Document Change Notice ISDB Fault Events The ISDB (Intelligent Serial Daughter Board) service, also known as the ISDB entity, issues the following fault event messages. The entity code assigned to ISDB events is 151. 102 Entity Code/Event Code 151/1 Decimal Identifier 16815873 Severity: Fault Message: Meaning: The ISDB experienced a fatal error and is restarting automatically. Action: Verify that the configuration is correct. Call the Bay Networks Technical Solutions Center if the router fails to restart. Entity Code/Event Code 151/18 Decimal Identifier 16815890 Severity: Fault Message: Isdb Hardware Flash Burn Failure Meaning: The ISDB flash burn has failed. Action: Try to reformat the flash. If this does not work, call the Bay Networks Technical Solutions Center. Entity Code/Event Code 151/19 Decimal Identifier 16815891 Severity: Fault Message: Isdb Hardware Flash Burn Failure - Time Exceeded Meaning: The ISDB flash burn has failed because the connection between the ISDB and the router has failed. Action: Check that the router and the ISDB hardware are properly connected. 300020-B Rev. 00 Event Messages for Routers ISDB Warning Events The ISDB (Intelligent Serial Daughter Board) service, also known as the ISDB entity, issues the following warning event messages. The entity code assigned to ISDB events is 151. Entity Code/Event Code 151/2 Decimal Identifier 16815874 Severity: Warning Message: Meaning: This is a generic warning message. Entity Code/Event Code 151/3 Decimal Identifier 16815875 Severity: Warning Message: received an unexpected buffer Meaning: The ISDB has received buffers it should not have received. The router code is malfunctioning. Action: The contents of the buffer will appear in the router log. Report the contents to the Bay Networks Technical Solutions Center. Entity Code/Event Code 151/4 Decimal Identifier 16815876 Severity: Warning Message: received an unexpected signal. Meaning: The ISDB has received signals it should not have received. The router code is malfunctioning. Action: Contact the Bay Networks Technical Solutions Center. Entity Code/Event Code 151/5 Decimal Identifier 16815877 Severity: Warning Message: A file error of type has occurred. Meaning: A read, write, open, seek, or close error of the specified type has occurred. Action: Contact the Bay Networks Technical Solutions Center. 300020-B Rev. 00 103 BayRS Version 12.20 Document Change Notice 104 Entity Code/Event Code 151/6 Decimal Identifier 16815878 Severity: Warning Message: Download/Upload operation aborted Meaning: An ISDB download or upload operation has aborted. Action: None Entity Code/Event Code 151/7 Decimal Identifier 16815879 Severity: Warning Message: Receive ERROR Meaning: The ISDB has received an error of the specified type. Action: None Entity Code/Event Code 151/20 Decimal Identifier 16815892 Severity: Warning Message: Transfer Already In Progress Meaning: An ISDB image transfer is occurring. Action: None Entity Code/Event Code 151/21 Decimal Identifier 16815893 Severity: Warning Message: Download Attempted on Non-Present Connector Meaning: A download of an ISDB image has been attempted on a connector that is not active. Action: Locate the correct connector and attach the ISDB board. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 151/22 Decimal Identifier 16815894 Severity: Warning Message: Isdb Hardware Failure FFFFFF00 Connector Meaning: An ISDB hardware failure has occurred. Action: Verify that you installed the correct version of arn.exe to support the ISDB. Verify that there is an ISDB on this slot. ISDB Info Events The ISDB (Intelligent Serial Daughter Board) service, also known as the ISDB entity, issues the following info event messages. The entity code assigned to ISDB events is 151. Entity Code/Event Code 151/8 Decimal Identifier 16815880 Severity: Info Message: Meaning: This is a generic information message. Entity Code/Event Code 151/9 Decimal Identifier 16815881 Severity: Info Message: ISDB Gate up Meaning: The ISDB gate is up. Entity Code/Event Code 151/10 Decimal Identifier 16815882 Severity: Info Message: ISDB Gate down Meaning: The ISDB gate is down. 300020-B Rev. 00 105 BayRS Version 12.20 Document Change Notice 106 Entity Code/Event Code 151/11 Decimal Identifier 16815883 Severity: Info Message: Download Started Meaning: An ISDB download has begun. Entity Code/Event Code 151/12 Decimal Identifier 16815884 Severity: Info Message: Upload Started Meaning: An ISDB upload has begun. Entity Code/Event Code 151/13 Decimal Identifier 16815885 Severity: Info Message: Download/Upload operation complete Meaning: The ISDB download or upload operation is complete. Entity Code/Event Code 151/23 Decimal Identifier 16815895 Severity: Info Message: Isdb Hardware Stop Connector Meaning: The ISDB hardware on the specified connector has stopped. Entity Code/Event Code 151/24 Decimal Identifier 16815896 Severity: Info Message: Isdb Hardware Start Connector Meaning: The ISDB hardware on the specified connector has started. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 151/25 Decimal Identifier 16815897 Severity: Info Message: Isdb Hardware Flash Burn Starting Meaning: An ISDB flash burn is starting. Entity Code/Event Code 151/26 Decimal Identifier 16815898 Severity: Info Message: Isdb Hardware Flash Burn Complete Meaning: An ISDB flash burn is complete. Entity Code/Event Code 151/29 Decimal Identifier 16815901 Severity: Info Message: Isdb Hardware Reset Connector Meaning: The ISDB hardware is resetting for the specified connector. L2TP Fault Event The Layer 2 Tunneling Protocol (L2TP), also known as the L2TP entity, issues the following fault event message. The entity code for L2TP is 150. Entity Code/Event Code 150/1 Decimal Identifier 16815617 Severity: Fault Message: System error, service attempting restart Meaning: L2TP experienced a fatal error. L2TP will attempt to restart automatically. Action: Verify that the configuration is correct. Call the Bay Networks Technical Solutions Center if L2TP fails to restart. 300020-B Rev. 00 107 BayRS Version 12.20 Document Change Notice L2TP Warning Events The Layer 2 Tunneling Protocol (L2TP), also known as the L2TP entity, issues the following warning event messages. The entity code for L2TP is 150. 108 Entity Code/Event Code 150/12 Decimal Identifier 16815628 Severity: Warning Message: Proxy LCP unsuccessful, SID = , TID = Meaning: LCP negotiations were unsuccessful. Entity Code/Event Code 150/14 Decimal Identifier 16815630 Severity: Warning Message: Failed to authenticate user , SID = , TID = Meaning: The RADIUS server could not verify the remote user’s identity. Action: Check the RADIUS server’s user name configuration. Entity Code/Event Code 150/21 Decimal Identifier 16815637 Severity: Warning Message: Max. retransmit reached. Taking down tunnel, TID , LAC IP: , LNS IP: Meaning: The router has reached the maximum number of times it will retransmit data. The LNS is now disconnecting the L2TP tunnel. Action: Try another call or try increasing the values of the Retransmit Timer, Maximum Retransmit, and Hello Timer configuration parameters. Entity Code/Event Code 150/22 Decimal Identifier 16815638 Severity: Warning Message: Retransmit buffer ring full, dropping outbound buffers, TID: Meaning: The router is running low on buffer space. Action: Increase the buffer allocation. 300020-B Rev. 00 Event Messages for Routers Entity Code/Event Code 150/23 Decimal Identifier 16815639 Severity: Warning Message: The LAC has invalid Protocol Version , LAC IP: Meaning: The LAC has the wrong L2TP software version. Action: Update the LAC’s L2TP software. Ensure that you are not running PPTP or L2F. Entity Code/Event Code 150/24 Decimal Identifier 16815640 Severity: Warning Message: has invalid Framing Capabilities , LAC IP: Meaning: The LAC requires a framing capability that the router does not support. Action: None Entity Code/Event Code 150/25 Decimal Identifier 16815641 Severity: Warning Message: has invalid Framing Type , LAC SID: , TID: , LAC IP: . Meaning: The LAC requires a framing type that the router does not support. Action: None Entity Code/Event Code 150/26 Decimal Identifier 16815642 Severity: Warning Message: has invalid Bearer Capabilities , LAC IP: Meaning: The LAC requires a bearer capability that the router does not support. Action: None 300020-B Rev. 00 109 BayRS Version 12.20 Document Change Notice 110 Entity Code/Event Code 150/27 Decimal Identifier 16815643 Severity: Warning Message: has invalid Bearer Type , LAC TID: , LAC IP: Meaning: The LAC requires a bearer type that the router does not support. Action: None Entity Code/Event Code 150/29 Decimal Identifier 16815645 Severity: Warning Message: Attempted to establish session using existing LAC SID , TID