advertisement
Release Notes for BayRS Version 12.20
BayRS Version 12.20
Site Manager Software Version 6.20
BCC Version 4.00
Part No. 301151-B Rev. 00
September 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. September 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
AN, BCN, BLN, BN, FRE, and Bay Networks are registered trademarks and Advanced Remote Node, ANH, ARN,
ASN, BayRS, 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 301151-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 its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered files, data, or programs.
301151-B Rev. 00 iii
iv
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.
301151-B Rev. 00
Contents
Release Notes for BayRS Version 12.20
Next Hop Resolution Protocol for MPOA .........................................................1-14
301151-B Rev. 00 v
vi
Domain Name Removal Prior to RADIUS Authentication ................................1-18
FRE-2-060E Processor Module with Advanced Compression Coprocessor
Daughterboard .......................................................................................................1-22
DSU/CSU Test LED Remains On After Reset .................................................1-23
301151-B Rev. 00
Network Booting on DSU/CSU Interfaces .......................................................1-24
IP Fragmentation Not Supported over GRE Tunnels .............................................1-24
ATM Event Message Numbering Changed ............................................................1-25
ARN Router Not a Supported DVS Radius Client ..................................................1-25
BayRS Version 12.20 Flash Memory Requirements ..............................................1-25
FT1/T1 and ISDN Phone Line Configuration ...................................................1-26
FT1/T1 DSU/CSU Diagnostic PROM Requirements .......................................1-26
Selecting 56K Rate Adaption on FT1/T1 DSU/CSU Lines ..............................1-27
Dial Backup on a Primary Leased Line ...........................................................1-27
Protocol Prioritization No Call Filters and TCP Applications ..................................1-28
DCM Memory Requirements for RMON2 ........................................................1-29
Enabling RMON on the ARN 10/100 Router ...................................................1-29
Configuring NTP Using the Technician Interface .............................................1-29
Setting Modem Initialization Strings Using the Technician Interface ...............1-30
301151-B Rev. 00 vii
Tables
BCC Board Types: AN and ANH Modules ..............................................1-7
BCC Board Types: BLN and BCN Modules ............................................1-8
BCC Board Types: ASN Modules .........................................................1-10
BCC Board Types: ARN Modules .........................................................1-11
BCC Board Types: System 5000 Modules ............................................1-12
Standards Supported by Version 12.20 ................................................1-33
Approved Flash Memory Cards ............................................................1-39
301151-B Rev. 00 ix
Technical Support
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.
301151-B Rev. 00 xi
Release Notes for BayRS Version 12.20
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
United States and
Canada
Europe
Asia/Pacific
Latin America
Telephone number Fax number
800-2LANWAN; then enter Express Routing
Code (ERC) 290, when prompted, to purchase or renew a service contract
978-916-3514
978-916-8880 (direct)
33-4-92-96-69-66 33-4-92-96-69-96
61-2-9927-8888 61-2-9927-8899
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:
Technical Solutions Center Telephone number
Billerica, MA
Santa Clara, CA
Valbonne, France
Sydney, Australia
Tokyo, Japan
800-2LANWAN
800-2LANWAN
33-4-92-96-69-68
61-2-9927-8800
81-3-5402-0180
Fax number
978-916-3514
408-495-1188
33-4-92-96-69-98
61-2-9927-8811
81-3-5402-0173 xii 301151-B Rev. 00
Technical Support
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)
33-4-92-96-15-83 Europe, Middle East, and
Africa
Asia/Pacific
Tokyo and Japan
61-2-9927-8822
81-3-5402-7041
301151-B Rev. 00 xiii
Release Notes for
BayRS Version 12.20
This document contains the latest information about Bay Networks
®
BayRS
™
Version 12.20.
These release notes include information about:
•
•
•
New Features in BayRS Version 12.20
•
•
Guidelines for Working with BayRS Version 12.20
•
•
•
Upgrading to Version 12.20
To upgrade BayRS to Version 12.20, or to upgrade Site Manager software to
Version 6.20, see Upgrading Routers from Version 7-11.xx to Version 12.00, also in your upgrade package, and the upgrade section of the BayRS Version 12.20
Document Change Notice.
301151-B Rev. 00 1
2
Release Notes for BayRS Version 12.20
Upgrading L2TP Configurations to Version 12.20
If you have a BayRS Version 12.10 configuration file that includes L2TP operating on a router using BayRS Version 12.20, the router automatically upgrades the assigned user network addresses to Version 12.20 L2TP IP interface addresses. L2TP IP interface addresses are internal to the router. When communicating with the remote user, the router associates the user’s IP address with an L2TP IP interface address that you configure.
The Version 12.10 assigned user network addresses apply to the entire router. In
Version 12.20, each slot has a unique L2TP IP address. Consequently, if the number of configured L2TP slots is greater than the number of configured assigned user network addresses, the router may not be able to upgrade every slot from a Version 12.10 configuration to a Version 12.20 configuration.
The router automatically converts all assigned user network addresses to L2TP IP addresses. For slots that exceed the number of assigned user network addresses, you will need to manually configure L2TP IP interface addresses. To do this, delete L2TP from the slot, then configure a new L2TP interface. Each slot must have L2TP IP interface address.
Using the BCC
The BCC
™
is a command-line interface for configuring Bay Networks devices. It also supports Technician Interface commands and scripts.
Before using the BCC, refer to the following sections listing the platforms, protocols, and interfaces that the BCC supports.
Platforms Supported
The BCC runs on AN
®
, ANH
™
, ARN
®
, ASN
®
, System 5000
™
, and BN
® platforms including ARE, FRE
®
, and FRE-2 processor modules. Each slot must have:
• 16 MB of dynamic RAM (DRAM)
• 2 MB of free memory space available when you start the BCC
If you try to start the BCC with insufficient DRAM or free memory on a slot, the
BCC returns an error message. In that case, use Site Manager instead of the BCC.
301151-B Rev. 00
Release Notes for BayRS Version 12.20
Number of BCC Sessions
You can open one BCC session per slot in read-write (configuration) mode. Other users can open additional BCC sessions in read-only (nonconfiguration) mode, depending on memory resources available on the slot supporting your login session. When memory requirements are insufficient to support additional BCC sessions on a login slot, the system displays the following message:
BCC requires 2MB of free memory. Current available memory is
<numeric value of current available memory>.
Each BCC session is mutually exclusive. If you make a change in a BCC session in read-write mode, this change does not appear in another BCC session.
Changing Sync to Serial
In BCC syntax, the term “sync” has been changed to “serial.” This global change affects all sync-related config or show commands.
BCC Help Initialization
Obtaining a response from a BCC Help request may require an initialization time of about one minute. This initialization occurs only when issuing the first Help command after booting the device. Subsequent requests for BCC Help information take only one or two seconds.
Interfaces Supported
You can use BCC commands to configure the following interfaces:
• ATM
• Console
• DCM
• DSU/CSU
• Ethernet
• FDDI
• FT1
• HSSI
301151-B Rev. 00 3
Release Notes for BayRS Version 12.20
• ISDN/BRI
• MCE1/MCT1
• Serial (synchronous)
• Token ring
• V.34 modem adapter (for the ARN router)
• Virtual (referred to in Site Manager as Circuitless IP)
Tables
list the link and net modules that the BCC supports.
Global Protocols Supported
You can use BCC commands to configure the following global protocols:
• IP (including access policies, static routes, and adjacent hosts)
• ARP
• BGP (including accept and announce policies)
• HTTP
• IGMP
• IPX (including static-netbios-route)
• IPXWAN
• OSPF (including accept and announce policies)
• RIP (including accept and announce policies)
• FTP
• NTP
• SNMP
• Telnet
• TFTP
4 301151-B Rev. 00
Release Notes for BayRS Version 12.20
Interface Protocols Supported
You can use BCC commands to configure the following interface protocols:
• IP
• ARP
• ATM
• Dial backup
• Frame relay (multiline not supported)
• IPX
• IGMP
• OSPF
• RIP
• Router Discovery (RDISC)
• Proprietary Standard Point-to-Point
• PPP (certain line parameters only; no multiline or multilink supported)
Getting Started
Caution: BCC configuration and source commands make immediate changes to the active device configuration. Read about the source command in Using the Bay Command Console.
Before using the BCC, save your configuration files by copying them onto the same flash memory card using new file names.
To start the BCC, enter bcc at the Technician Interface prompt.
To display the online instructions for new BCC users, enter help learning-bcc at the bcc>
prompt. Then to display a full summary of the Help features of the BCC interface, enter help -more .
For more information about how to use the BCC interface, see Using the Bay
Command Console.
301151-B Rev. 00 5
Release Notes for BayRS Version 12.20
For instructions on using the BCC to add and change protocol services, see the documentation for that protocol.
If you use the BCC show config command to view a router configuration, the
BCC displays only the components or protocols it supports.
Deleting Interfaces with the BCC
Before using the BCC to delete an interface, make sure that you did not use Site
Manager to configure it with a protocol that the BCC does not recognize. If you did, use Site Manager to delete the interface.
Identifying Board Types
Tables
identify the Board Type parameter values displayed by the
BCC. Use the “Board Type” column to identify a hardware module in an AN,
ANH, ARN, ASN, System 5000, or BN router configuration.
Note: You cannot use BCC commands to configure the operation of an FE1 adapter module for any AN or ANH router or an X.25 PAD or V.34 console modem daugherboard for the ARN router. (Use Site Manager to configure these daughterboards.) Inserting a daughterboard into an AN base module redefines its module ID and board type.
6 301151-B Rev. 00
Release Notes for BayRS Version 12.20
Table 1.
BCC Board Type andeds andedsg andedsh andedst andst ansdsedst anseds ansedsg ansedsh ansedst ansets ansetsg ansetsh ansetst antst ansedsi ansedsti ansedshi andsti ansedsgx
Table 1 lists the AN and ANH board types
BCC Board Types: AN and ANH Modules
Technician
Interface or MIB
Module ID Description
1033
1050
1035
1034
1037
1041
1024
1047
1026
1025
1030
1049
1032
1031
1039
1027
1028
1029
1038
1048
AN-ENET (2 Ethernet ports, 2 serial ports)
ANH-8 (2 Ethernet ports, 2 serial ports) and an 8-port Ethernet hub active for the first Ethernet port
ANH-12 (2 Ethernet ports, 2 serial ports) and a 12-port Ethernet hub
AN-ENET (2 Ethernet ports, 2 serial ports, 1 token ring port)
AN-TOKEN (2 serial ports, 1 token ring port)
AN-ENET/TOKEN (1 Ethernet port, 2 serial ports, 1 token ring port)
AN-ENET (1 Ethernet port, 2 serial ports) with 16 MB DRAM
ANH-8 (1 Ethernet port, 2 serial ports) and an 8-port Ethernet hub
ANH-12 (1 Ethernet port, 2 serial ports) and a 12-port Ethernet hub
AN-ENET/TOKEN (1 Ethernet port, 2 serial ports, 1 token ring port) with 16 MB DRAM
AN-ENET (1 Ethernet port, 3 serial ports) with16 MB DRAM
ANH-8 (1 Ethernet port, 3 serial ports) and an 8-port Ethernet hub
ANH-12 (1 Ethernet port, 3 serial ports) and a 12-port Ethernet hub
AN-ETS (1 Ethernet port, 3 serial ports, 1 token ring port)
AN-TOKEN (3 serial, 1 token ring port)
AN-ENET with ISDN (2 Ethernet ports, 2 serial ports) with
16 MB DRAM
AN-ENET/TOKEN with ISDN (1 Ethernet port, 2 serial ports,
1 token ring port)
ANH-12 with ISDN (1 Ethernet port, 2 serial ports) and a 12-port
Ethernet hub
AN-TOKEN with ISDN (2 serial ports, 1 token ring port)
(continued)
ANH-8 with DCM (1 Ethernet port, 2 serial ports) and an 8-port
Ethernet hub
301151-B Rev. 00 7
Release Notes for BayRS Version 12.20
Table 1.
BCC Board Type ansedsgi ansedsx ansedstx ansedsc andstc ansedstc ansedshc ansedsgc ansedsf ansedshf ansedsgf
BCC Board Types: AN and ANH Modules (continued)
Technician
Interface or MIB
Module ID Description
1051
1055
1058
1090
1091
1092
1093
1094
1100
1106
1108
ANH-8 with ISDN (1 Ethernet port, 2 serial ports)and an 8-port
Ethernet hub
AN-ENET with DCM (2 Ethernet ports, 2 serial ports)
AN-ENET/TOKEN with DCM (1 Ethernet port, 2 serial ports,
1 token ring port) with 16 MB DRAM
AN-ENET with CSU/DSU (2 Ethernet ports, 2 serial ports)
AN-TOKEN with CSU/DSU (2 serial ports, 1 token ring port)
AN-ENET/TOKEN with CSU/DSU (1 Ethernet port, 2 serial ports,
1 token ring port)
ANH-12 with CSU/DSU (1 Ethernet port, 2 serial ports) and a
12-port Ethernet hub
ANH-8 with CSU/DSU (1 Ethernet port, 2 serial ports) and an
8-port Ethernet hub
AN-ENET with T1/FT1 (2 Ethernet ports, 2 serial ports)
ANH-12 with T1/FT1 (1 Ethernet port, 2 serial ports) and a 12-port
Ethernet hub
ANH-8 with T1/FT1 (1 Ethernet port, 2 serial ports) and an 8-port
Ethernet hub
Table 2.
BCC
Board Type comp comp128 de100 dst416
Table 2 lists the BLN and BCN board types.
BCC Board Types: BLN and BCN Modules
Technician
Interface or MIB
Module ID
Site Manager
Model Number Description
4353 AG2104037
4354
4864
40
AG2104038
50038
5740
Octal Sync with 32-context compression daughterboard
Octal Sync with 128-context compression daughterboard
100BASE-T Ethernet
(continued)
Dual Sync with token ring
8 301151-B Rev. 00
Table 2.
BCC
Board Type dtok enet3 esaf esafnf osync qef qenf qtok shssi sse sync wffddi1m wffddi1mf wffddi1s wffddi1sf wffddi2m wffddi2mf wffddi2s wffddi2sf atmcoc3mm atmcoc3sm atmce3 atmcds3 smct1 mct1
Release Notes for BayRS Version 12.20
BCC Board Types: BLN and BCN Modules (continued)
Technician
Interface or MIB
Module ID
Site Manager
Model Number Description
176
132
236
232
195
199
192
196
194
198
4608
4609
5121
5120
169
225
118
80
193
197
4352
164
162
256
168
5710
5505
5531
5532
5431
5008
5950
5450
50021
5295
5410
5280
5943
5949
5942
5948
5930
5946
5940
5947
AG13110112
AG13110113
AG13110114
AG13110115
5944
5945
Dual token ring
Dual Ethernet
Dual Sync Dual Ethernet with 2-CAM filters
Dual Sync Dual Ethernet with 6-CAM filters
Dual Sync Dual Ethernet without hardware filters
Octal Sync
Quad Ethernet with hardware filters
Quad Ethernet without hardware filters
Quad token ring
HSSI
Single Sync with Ethernet
Quad Sync
Hybrid FDDI with single mode on connector B
Hybrid FDDI with single mode on connector B and with hardware filters
Hybrid FDDI with single mode on connector A
Hybrid FDDI with single mode on connector A and with hardware filters
Multimode FDDI
Multimode FDDI with hardware filters
Single Mode FDDI
Single Mode FDDI with hardware filters
ATM STS-3/STM-1 MMF
ATM STS-3/STM-1 SMF
ATM E3
ATM DS-3
Single Port MCT1e
(continued)
Dual Port MCT1
301151-B Rev. 00 9
Release Notes for BayRS Version 12.20
Table 2.
BCC
Board Type qmct1db15 qmct1ds0a smce1ii75 mce1ii75 smce1ii120 mce1ii120
BCC Board Types: BLN and BCN Modules (continued)
Technician
Interface or MIB
Module ID
Site Manager
Model Number Description
5377
5378
189
188
191
190
AG2111007
AG2104052
AG2111003
AG2111004
AG2111001
AG2111002
Quad Port MCT1 DB15
Quad Port MCT1 DB15 with DS0A
75 ohm Single Port Multichannel E1 (MCE1-II) for 75 ohm Leased Line
75 ohm Dual Port Multichannel E1 (MCE1-II) for
75 ohm Leased Line
120 ohm Single Port Multichannel E1 (MCE1-II) for ISDN PRI and Leased Line
120 ohm Dual Port Multichannel E1 (MCE1-II) for ISDN PRI and Leased Line
Table 3.
BCC
Board Type denm dsnm1n dtnm qsyncm spex spexhsd mmfsddas smfsddas smammbdas mmasmbdas dsnm1nisdn mce1nm
Table 3 lists the ASN board types.
BCC Board Types: ASN Modules
Technician
Interface or MIB
Module ID Description
1280
1540
2048
1664
512
769
1793
1801
1825
1833
1588
2816
Dual Port Ethernet Net Module
Dual Port Synchronous Net Module
Dual Port Token Ring Net Module
Quad Port Synchronous Net Module
SPEX Net Module
SPEX - Hot Swap Net Module
Multimode FDDI Net Module
Single Mode FDDI Net Module
Hybrid PHY A FDDI Net Module
Hybrid PHY B FDDI Net Module
ISDN BRI/Dual Sync Net Module
MCE1 Net Module
(continued) asnqbri
10
2560 Quad BRI Net Module
301151-B Rev. 00
Table 3.
BCC
Board Type se100nm dmct1nm shssinm
Release Notes for BayRS Version 12.20
BCC Board Types: ASN Modules (continued)
Technician
Interface or MIB
Module ID Description
2304
2944
3584
100BASE-T Ethernet Net Module
Dual Port MCT1 Net Module
HSSI Net Module
Table 4.
BCC
Board Type arnmbstr arnmbsen arnmbenx10 arnssync arnis arnisdnu arndcsu arnv34 arnft1 arntsync arnsenet arnstkrg arnentsync arnisdnu arnpbtenx10 arnpbenx10
Table 4 lists the ARN board types.
BCC Board Types: ARN Modules
Technician
Interface or MIB
Module ID Description
8704
8720
8896
8736
8784
8800
8768
8752
8776
8848
8832
8816
8864
8880
8960
8928
ARN Token Ring Base Module with 0, 8, 16, or 32 MB DRAM
ARN Ethernet Base Module with 0, 4, 8, 16, or 32 DRAM
ARN Ethernet Base Module - xxMB DRAM with DCM
ARN Serial Adapter Module
ARN ISDN BRI S/T Adapter Module
ARN ISDN BRI U Adapter Module
ARN 56/64K DSU/CSU Adapter Module
ARN V.34 Modem Adapter Module
T1/FT1 DSU/CSU Adapter Module
ARN Tri-Serial Port Expansion Module
ARN Ethernet Port Expansion Module
ARN Token Ring Expansion Module
ARN Ethernet and Tri-Serial Expansion Module
ARN Token Ring and Tri-Serial Expansion Module
ARN Ethernet and Tri-Serial Expansion Module with DCM
ARN Ethernet Expansion Module with DCM
(continued)
301151-B Rev. 00 11
Release Notes for BayRS Version 12.20
Table 5.
BCC
Board Type se100nm denm dsnm1n dtnm qsyncnm iqe iqtok mmfsddas smfsddas smammbdas mmasmbdas asnqbri mce1nm dmct1nm shssinm atm5000bh
Table 5 lists the System 5000 board types.
BCC Board Types: System 5000 Modules
Technician
Interface or MIB
Module ID Description
1408
2176
1793
1801
1825
1833
2560
2816
2304
1280
1540
2048
1664
2944
3584
524544
Router 100BASE-T Ethernet Net Module
Router Dual Ethernet Net Module
Router Dual Synchronous Net Module
Router Dual Token Ring Net Module
Router Quad Port Synchronous Net Module
5380 Ethernet Router Module
5580 Token Ring Router Module
Router Multimode FDDI Net Module
Router Single Mode FDDI Net Module
Router Hybrid PHY A FDDI Net Module
Router Hybrid PHY B FDDI Net Module
Router Quad Port ISDN BRI Net Module
Router MCE1 Net Module
Router Dual Port MCT1 Net Module
Router HSSI Net Module
Centillion Multiprotocol Engine
Sending BCC Feedback
After you use the BCC, we welcome your feedback. Please visit the BCC Web site at the following URL, where you can leave us a message: http://support.baynetworks.com/library/tpubs/bccfeedbk
12 301151-B Rev. 00
Release Notes for BayRS Version 12.20
New Features in BayRS Version 12.20
BayRS Version 12.20 provides the following new Site Manager and BCC features.
Cache Mode
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. For information about cache mode, see the
BayRS Version 12.20 Document Change Notice.
ATM Configuration
The following features are new for ATM in BayRS Version 12.20. For more information about ATM, see Configuring ATM Services.
ATM BCC Support
You can use BCC commands to configure PVC, classical IP, and LAN emulation service records. You can also use BCC commands to configure IP (PVC, classical
IP, and LEC service records) or IPX (PVC and LEC service records only) over
ATM.
MPOA Server Configuration
BayRS Version 12.20 supports MPOA server (MPS) configuration over ATM.
Multi-Protocol Over ATM (MPOA) is the ATM Forum standard that specifies a way to efficiently transport intersubnet, unicast data in a LANE environment.
MPOA provides a direct connection between MPOA clients that reside on separate ELANs by allowing the LAN emulation clients to establish
“cut-through” VCs that bypass the MPS.
MPOA also ensures interoperability with the existing infrastructure of routers.
MPOA servers make use of routers that run standard network layer protocols, such as OSPF, providing a smooth integration with existing networks.
301151-B Rev. 00 13
Release Notes for BayRS Version 12.20
ATM Router Redundancy
BayRS Version 12.20 supports warm standby redundancy for ATM routers. This redundancy protects a network from the irrecoverable failure of an entire ATM router.
Router redundancy for ATM enables you to switch over from a primary router connected to an ATM network to a secondary router connected to the same ATM network. The primary router is configured to be in a router redundancy group.
One or more secondary routers are also configured to be members of the same RR group.
Next Hop Resolution Protocol for MPOA
The Next Hop Resolution Protocol (NHRP) resolves a layer 3 media-independent protocol address to a layer 2 media-dependent address. As implemented in BayRS
Version 12.20, NHRP resolves layer 3 IP addresses and layer 2 ATM addresses.
Specifically, NHRP works in conjunction with MultiProtocol Over ATM (MPOA) clients and servers to provide a facilitated SVC-based delivery of IP datagrams over an ATM cloud.
OSI Configuration
The following features are new for OSI in BayRS Version 12.20. For information about OSI configuration, see the BayRS Version 12.20 Document Change Notice.
OSI over ATM
OSI over ATM includes support for the following encapsulation methods:
LLC/SNAP 1483 encapsulation and NLPID 1490 encapsulation.
With OSI over ATM, you also can configure 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.
14 301151-B Rev. 00
Release Notes for BayRS Version 12.20
TARP over OSI
The Transport Identifiers (TID) Address Resolution Protocol (TARP) has been added to the OSI suite for BayRS Version 12.20. OSI uses 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.
8021.Q Tagging
8021.Q virtual LAN (VLAN) tagging enables a router to connect VLANs in layer 2 VLAN environments, acting as a default router for VLANs performing a
"one armed router" function, while continuing to deliver WAN connectivity and security/firewalling between domains. This is not an implementation of VLANs on the router. It only provides for termination of VLANs on a router and does not extend the VLAN across the wide area.
802.1Q tagging supports only 100BASE-T and is implemented on ASN, ARN, and BN router platforms. For information about 802.1Q, see the BayRS Version
12.20 Document Change Notice.
Bay Dial VPN
Bay Dial Virtual Private Network (Dial VPN) services provide switched connectivity to virtual private networks (VPNs) based on Internet Engineering
Task Force (IETF) specifications. Corporate customers can subscribe to this service for remote dial access to virtual private networks or to the Internet over telephone lines.
For information about configuring Bay Dial VPN, see Configuring and
Troubleshooting Bay Dial VPN Services.
301151-B Rev. 00 15
Release Notes for BayRS Version 12.20
BGP Route Reflector
A BGP router configured for internal BGP (IBGP) must establish a peer-to-peer session with every other IBGP speaker in the AS. In an AS with a large number of
IBGP speakers, this full-mesh topology can result in high bandwidth and maintenance costs. For example, a full-mesh topology for an AS with 50 IBGP speakers requires 1,225 internal peer-to-peer connections.
To avoid the high cost of a full-mesh topology to support IBGP speakers within a large AS, you can configure a router to function as an IBGP route reflector. An
IBGP speaker that needs to communicate with other BGP speakers in the AS establishes a peer-to-peer RR client session with the IBGP route reflector.
For more information about BGP Route Reflector, see Configuring IP Services.
IBGP Equal Cost Multipath
BGP equal-cost multipath (ECMP) support allows an IBGP speaker to perform route balancing within an AS by using multiple equal-cost routes submitted to the routing table by OSPF or RIP. For more information about IBGP equal-cost multipath, see Configuring IP Multicasting and Multimedia Services.
Generic Routing Encapsulation
Generic Routing Encapsulation (GRE), which is defined in RFCs 1701 and 1702, is a generalized protocol that defines a method for encapsulating any payload inside any network (layer 3) protocol. For BayRS Version 12.20, GRE allows the layer 3 protocol IP to be encapsulated in IP. GRE tunnels are manually configured on the routers. For the tunneled protocol, the tunnels will be viewed as a logical single-hop point-to-point link. Routing information for the tunneled protocol can be exchanged over GRE tunnels. For more information about GRE, see
Configuring IP Services.
16 301151-B Rev. 00
Release Notes for BayRS Version 12.20
IGMP Relay
A router configured as an IGMP Relay (IGMP-R) device provides the following services on behalf of an MOSPF AS boundary router:
• Solicits multicast group membership information by sending IGMP host membership queries to hosts on its attached local networks
• Receives host membership reports and unsolicited join messages from hosts on attached networks and forwards them to the MOSPF boundary router
• Forwards multicast data to group members on locally attached networks
To an IGMP host on a directly attached network, the IGMP-R device appears to be a multicast router. The host receives a host membership query from IGMP-R and responds by sending an IGMP response. A host can also send IGMP-R an unsolicited join message.
To the MOSPF AS boundary router, the IGMP-R device appears to be a locally attached host. The MOSPF router (which also runs IGMP) sends IGMP host queries to the IGMP-R. IGMP-R responds by forwarding -- relaying -- IGMP host reports and unsolicited join messages from its attached hosts.
For more information about IGMP Relay, see Configuring IP Multicasting and
Multimedia Services.
Equal Cost Multipath IP Static Routes
IP supports equal-cost multipath (ECMP) static routes for traffic load balancing. If
IP considers the ECMP routes to be the best routes, IP uses them in the way you specify -- in round-robin fashion, for example -- to forward data.
L2TP Configuration
The following features are new for L2TP in BayRS Version 12.20. For more information about L2TP, see Configuring L2TP Services.
301151-B Rev. 00 17
Release Notes for BayRS Version 12.20
Domain Name Removal Prior to RADIUS Authentication
In BayRS Version 12.20, there is a new feature for L2TP configuration that enables you to remove the domain name from the complete user name before
RADIUS authentication takes place. By default, this feature is enabled; consequently, the LNS automatically removes the delimiter, which separates the user name and the domain name, and the entire domain name.
If your RADIUS server database includes domain names as part of the user name entries, you need to disable this feature. To do this, set the Remove Domain Name parameter to Disable.
RIP Support
For BayRS 12.20, the LNS now supports RIP. RIP is particularly useful when the remote host is a router, because it enables the LNS to learn routing information from the remote router.
Flow Control
For an L2TP session, you can enable flow control. Flow control manages congestion across the connection, ensures that packets are not lost, and makes sure the devices at each end of the connection are communicating properly.
L2TP IP Address Assignment
When configuring the LNS, you must configure an IP address for every slot that has an L2TP interface. This address is referred to as the L2TP IP interface
address.
The L2TP IP interface address is internal to the LNS. When communicating with the remote user, the LNS associates the user’s IP address, which is assigned by the
RADIUS server, with the L2TP IP interface address that you configured.
Dial Backup
You can now use the BCC to configure dial backup service. For more information about using the BCC to configure dial backup service, see Configuring Dial
Services.
18 301151-B Rev. 00
Release Notes for BayRS Version 12.20
Data Collection Module
You can now use the BCC to configure a data collection module (DCM) for
RMON and RMON2 on an AN/ANH and ARN router. For information about configuring a DCM, see Configuring RMON and RMON2.
Domain Name System
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. For more information about
DNS, see the BayRS Version 12.20 Document Change Notice.
NAT
NAT “N to 1” translation is a feature enhancement to Network Address
Translation (NAT). “N to 1” address translation allows you to use a single IP address to represent a range of IP addresses on the private network. “N to 1” translations allow multiple hosts on the private network to be mapped to a single source address on the global or public side of the NAT. For more information about NAT III, see Configuring IP Services.
ARN, ASN, and System 5000 Support
You can use the BCC to configure the ARN, ASN, and System 5000 router and all related hardware modules, except for the X.25 PAD module, FE1 adapter module, and V.34 console modem. You cannot use the BCC to configure the
ARN/10/100-TX or the ARN 100-FX base units.
301151-B Rev. 00 19
Release Notes for BayRS Version 12.20
WAN Line Configuration
You can use BCC Version 4.00 to configure and customize line services for:
• Serial WAN circuits
• An internal DSU/CSU installed on a Bay Networks router
• Multichannel E1 (MCE1) or Multichannel T1 (MCT1) circuits
• Fractional T1 (FT1) circuits
For more information, see Configuring WAN Line Services.
Frame Relay
You can use the BCC to configure frame relay on serial, HSSI, and MCT1/E1 modules. You can also use BCC commands to configure frame relay as a backup interface over dial services. Frame relay supports the BN, ASN, AN, ARN, and
System 5000 platforms.
HTTP Web Server
You can use the BCC to configure the HTTP Web server. The router operating system contains an embedded Web server engine which, along with Web-based management pages, provides a simple, easy, and cost-effective way to monitor
Bay Networks devices. For information about configuring the HTTP Server, see the BayRS Version 12.20 Document Change Notice.
IP Adjacent Host Configuration
You can use the BCC to configure IP adjacent hosts on the BN, ASN, AN, ARN, and System 5000 platforms. For information about configuring IP adjacent hosts, see Configuring IP Services.
Telnet Passthrough
Telnet Passthrough allows centrally located technical customer personnel to monitor, control, and effect change to the operation of Sentry UPS units. By integrating Telnet Passthrough traffic onto a router-based multiprotocol backbone network, you can reduce costs by eliminating extra asynchronous lines and equipment.
20 301151-B Rev. 00
Release Notes for BayRS Version 12.20
Requirements for access to devices other than Sentry alarm systems should be communicated to Router Product Management.
IPX Support
You can use the BCC to configure IPX on Ethernet, FDDI, serial, token ring,
ATM, BRI, MCT/E1, and HSSI interfaces. For information about IPX, see
Configuring IPX Services.
BCC show Commands
BCC show commands are available for all router platforms, hardware, and protocols supported by the BCC. For information about BCC show commands, see the appropriate protocol manual.
New Hardware
BayRS Version 12.20 supports the following new hardware.
FE1/E1 WAN Adapter Module
The FE1/E1 WAN adapter module works with Bay Networks AN, ANH, and
ARN routers. It operates like a T1 CSU/DSU for E1 circuits. This adapter has an
X.21 or V.35 serial interface through which it connects to the router and a
G.703/G.704 interface through which it connects to the network.
To use the FE1/E1 WAN adapter module on the AN, ANH, or ARN router, you must upgrade the boot and diagnostic PROMs. For a complete list of boot and diagnostic PROMs for BayRS Version 12.20, see the BayRS Version 12.20
Document Change Notice.
For more information about configuring the FE1/E1 WAN adapter module, see
Configuring WAN Line Services.
301151-B Rev. 00 21
Release Notes for BayRS Version 12.20
FRE-2-060E Processor Module with Advanced Compression
Coprocessor Daughterboard
The FRE-2-060E processor module is equipped with the advanced compression coprocessor daughterboard. Although it is interoperable with existing software-based compression services, the advanced compression coprocessor daughterboard performs all compression, decompression, and compression-related functions in hardware, so that the FRE-2-060E processor does not need to perform them.
This new hardware configuration for BN platforms offers a choice of hardware compression algorithms that interoperates with FRE-3, FRE-2-060, FRE-2-040, and FRE processors and all LMI- and PCI-based link modules.
The FRE-2-060E with advanced compression coprocessor daughterboard supports hardware data compression over the following WAN interfaces:
• Multichannel E1-II (MCE1-II)
• Dual Multichannel E1 (DMCE1-II)
• Multichannel T1 (MCT1)
• Dual Multichannel T1 (DMCT1)
• Quad Multichannel T1 (QMCT1)
• Octal Synchronous (OSync)
• Quad Synchronous (QSync)
• Ethernet Synchronous Advanced Filter (ESAF)
The FRE-2-060E with advanced compression coprocessor daughterboard supports MSA compression for the following WAN protocols on BN platforms:
• Frame relay
• PPP
• ISDN PRI
The FRE-2-060E with advanced compression coprocessor daughterboard supports Hi/fn LZS compression for the following WAN protocols on BN platforms:
• PPP
22 301151-B Rev. 00
Release Notes for BayRS Version 12.20
• ISDN PRI
For information about configuring the FRE-2-060E with advanced compression coprocessor daughterboard, see Configuring Data Compression Services.
Guidelines for Working with BayRS Version 12.20
Note the following guidelines when using BayRS Version 12.20. These guidelines supplement the instructions in the Version 12.20 documentation set.
AN/ANH and ARN Guidelines
Note the following operational guidelines when using AN, ANH, or ARN routers.
Allocating Memory on ARN Routers
Although you can change the default memory allocation on other Bay Networks router platforms, the ARN platform does not support this “buffer carving” feature.
On the ARN, Site Manager does not support the Admin > Kernel Configuration option, and the Technician Interface does not support the set command for wfKernCfgParamEntry objects. Attempting to set wfKernCfgParamGlobMem on the ARN results in a warning message.
Cycling Power to the ARN
To ensure a complete power cycle, Bay Networks recommends that you wait at least 4 seconds after turning off the ARN before you turn it back on.
Caution: Cycling power to the ARN too quickly could cause an error.
DSU/CSU Test LED Remains On After Reset
The ARN DSU/CSU Test LED properly goes on when the interface enters test or loopback mode. However, the LED remains on after resetting the DSU/CSU module, even though all looping terminates and the module hardware resets.
301151-B Rev. 00 23
Release Notes for BayRS Version 12.20
Restarting the router turns the LED off. However, this action is not necessary for proper operation of the DSU/CSU interface.
Network Booting on DSU/CSU Interfaces
AN and ANH DSU/CSU interfaces do not support network booting in BayRS
Version 12.20. The ARN DSU/CSU supports network booting only over interfaces configured for 64 Kb/s Clear Channel service.
IP Fragmentation Not Supported over GRE Tunnels
IP packets will not be fragmented when encapsulated at the tunnel ingress point. If necessary, you can set MTU sizes to values large enough to prevent fragmentation on relevant interfaces on the GRE tunnel ingress router. Alternatively, you can configure your system to send MTU sizes less than the MTU sizes of the relevant interfaces on the GRE tunnel ingress router.
Creating Multiple GRE Tunnels
When creating multiple GRE tunnels dynamically, you can configure a maximum of 5 point-to-point GRE tunnels. In multipoint configurations, you can configure
64 GRE tunnels per interface.
BCC Help Not Supported on ARE Slots
When attempting to use BCC Help on an ARE slot (that is, an ATM ARE ILI pair or a Model 5782 VNR), the router returns the following message:
Help command is not available on this processor card
.
For information about BCC ATM parameters, see Configuring ATM Services.
ASN Boot and Diagnostic PROM Images
BayRS Version 12.20 includes a new boot PROM image (asnboot.exe) as well as a new diagnostic PROM image (asndiag.exe; Version 2.30). You must use these files together; in other words, when you upgrade the boot PROM, you must also upgrade the diagnostic PROM. The new boot PROM image corrects a problem with the previous boot PROM on the ASN. The previous boot PROM caused the boot/diagnostic PROM checksum to fail following a cold-start.
24 301151-B Rev. 00
Release Notes for BayRS Version 12.20
For information about upgrading boot and diagnostic PROMs for the ASN router, see Upgrading Routers from Version 7-11.xx to Version 12.00.
ATM Event Message Numbering Changed
The ATM, ATM signaling, and ATM LAN emulation log event messages have changed in BayRS Version 12.20. The ATM_SIG entity (entity #95) no longer exists as a separate entity, but has been combined with the ATM entity (entity
#78). Combining and reorganizing these entities has resulted in changes to the
ATM log event message numbers. New log events were added to the ATM_LE entity (entity #100) resulting in log event message number changes for LAN emulation, as well.
If you have defined log event traps for ATM, ATM signaling, or ATM LAN emulation, you will need to redefine them. For information, contact the Bay
Networks Technical Solutions Center.
ARN Router Not a Supported DVS Radius Client
The ARN router is not a supported DVS Radius client.
Problem Configuring NAT Dynamically
When you are configuring a local or global interface for NAT in dynamic mode, the router returns an SNMP set error. However, this error does not affect the configuration of the router.
NAT Interface Restriction
The Configuring IP Services manual states that NAT is supported over all interfaces. However, NAT is not currently supported over ATM or X.25 interfaces using Site Manager Versions 6.xx.
Support for NAT over ATM is planned for BayRS 13.10/7.10.
301151-B Rev. 00 25
Release Notes for BayRS Version 12.20
DNS Not Fully Operational
The BayRS Version 12.20 Document Change Notice provides information about the Domain Name System (DNS) client and how to configure it using Site
Manager Version 6.20. Please disregard this information; DNS is not fully operational, and should not be configured using Site Manager.
Site Manager Version 6.20 (patch release) corrects this problem by disabling the
DNS client feature. If you want to obtain a version of Site Manager 6.20, contact the Bay Networks Technical Support Center.
BayRS Version 12.20 Flash Memory Requirements
BayRS Version 12.20 software ships on the following flash memory cards:
Platform
AN/ANH
ARN
ARN
Flash Memory Required
8 MB
4 MB
8 MB
Associated Software Suites ip_access, office_suite, corp_suite ip_access office_suite, corp_suite
FT1/T1 DSU/CSU Guidelines
Note the following operational guidelines when using the FT1/T1 DSU/CSU.
Allocating DS0s
If you have an FT1/T1 DSU/CSU or E1 module and an ISDN S/T or U module installed on the same ARN, you can alternate assigned DS0 channels with unassigned channels, up to a maximum rate of 512 Kb/s (8 channels).
Caution: You cannot alternate assigned and unassigned channels across the
24 channels in a T1 line (768 Kb/s).
If you have rates above 512 Kb/s, Bay Networks recommends that you configure the DS0s contiguously, even though some noncontiguous channel configurations may work. If you have an unsupported channel configuration, the following message appears in the event log:
26 301151-B Rev. 00
Release Notes for BayRS Version 12.20
Connector COM <COM#>, Current timeslot assignment is not supported.
This message indicates an invalid assignment of DS0s for the specified connector; you should have your service provider change the T1 channel assignments. Using contiguous channel assignments addresses this problem.
FT1/T1 and ISDN Phone Line Configuration
If you configure FT1/T1 after configuring an ISDN ST or U interface, you may experience line manager faults if you have a 2B+D channel (one physical RJ-45 cable with two phone circuits) with only one phone line configured. To avoid any line manager faults, configure both phone lines.
FT1/T1 DSU/CSU Diagnostic PROM Requirements
The ARN requires diagnostic PROM (arndiag.exe) Version 2.00 or later to support the FT1/T1 DSU/CSU adapter module. The FT1/T1 hardware documentation incorrectly specifies diagnostic PROM Version 1.34 as the minimum required version.
Selecting 56K Rate Adaption on FT1/T1 DSU/CSU Lines
Rate adaption determines the number of bits and their bit positions within a time slot. The FT1/T1 logical line rate adaption is 64 Kb/s per DS0. You cannot change this rate.
Hi/fn (Stac) LZS Compression Executable
Using Hi/fn™ (Stac) LZS data compression requires the purchase of a separate
CD containing the Hi/fn LZS executable for BayRS Version 12.20 software. You must purchase this CD regardless of whether you plan to implement compression in hardware or software.
L2TP Guidelines
Note the following operational guidelines when using L2TP.
Dial Backup on a Primary Leased Line
You cannot configure dial backup service for a primary leased line that is using
L2TP, even if the dial backup line resides on a different slot than the primary line.
301151-B Rev. 00 27
Release Notes for BayRS Version 12.20
Dial Services
L2TP is not compatible with dial services. Do not enable L2TP on the same slot that you enable for a dial service, such as dial-on-demand, dial backup, or bandwidth-on-demand.
Dynamic L2TP Configuration
When you configure L2TP in dynamic mode, Site Manager can take several minutes to create the required circuits and related MIB instances.
28 301151-B Rev. 00
Release Notes for BayRS Version 12.20
Modification to an L2TP Script
The show l2tp sessions script has been modified. The script now displays the following information:
LNS Tun ID
LNS Call ID
LAC Tun ID
LAC Call ID
Calling Number
Called Number
Conn. Speed
Call Serial Number
Chan. ID
LNS tunnel ID for the L2TP session.
LNS call ID for the L2TP session.
LAC tunnel ID for the L2TP session.
LAC call ID for the L2TP session.
Phone number of the remote user.
Phone number of the router.
Speed of the connection in b/s.
Serial number assigned to the call.
Physical channel ID used in the ICCN message.
Outbound LAN Traffic Filters
When implementing outbound traffic filters for LAN protocols, note that in some configurations the filters may cause a decline in throughput performance. For
LAN circuits where the forwarding rate of the router is critical, you should monitor the throughput performance after configuring outbound LAN filters. If you notice an unacceptable performance degradation, try using inbound traffic filters to accomplish the filtering goal.
Protocol Prioritization No Call Filters and TCP Applications
Using a no call filter that applies to any TCP application can cause TCP to retransmit the filtered packet.
When two routers running a TCP application are connected using a demand line, and the demand line becomes inactive, the TCP application remains inactive.
301151-B Rev. 00 29
Release Notes for BayRS Version 12.20
If a demand line configured with a no call filter goes down, the no call filter drops any TCP packets it receives. Because TCP never receives an acknowledgment for transmitting its packets, the TCP application continues to retransmit packets until the connection eventually times out and the application stops operating.
Note: No call filters are specific to dial services. For additional information about traffic filters and protocol prioritization, see Configuring Traffic Filters
and Protocol Prioritization.
RMON and RMON2 Guidelines
Note the following operational guidelines when using RMON and RMON2.
DCM Memory Requirements for RMON2
RMON2 requires 8 MB of dynamic random access memory (DRAM) on the data collection module (DCM).
Enabling RMON on the ARN 10/100 Router
You cannot enable RMON through both the router software and the Ethernet
DCM at the same time.
You can enable RMON to operate through the router software image on the base module or on an optional Ethernet DCM (residing on an optional Ethernet parallel daughterboard).
Technician Interface Guidelines
The following sections pertain to the Technician Interface and BayRS Version
12.20 software.
Configuring NTP Using the Technician Interface
When you use the Technician Interface to configure the Network Time Protocol
(NTP), you must configure NTP on each slot on the router to ensure that NTP initializes correctly.
30 301151-B Rev. 00
Release Notes for BayRS Version 12.20
You can configure NTP on each slot by setting the following MIB variable from the Technician Interface: set wfProtocols.68.0 0xffffffff;commit
68 represents the wfNTPLoad attribute.
Setting Modem Initialization Strings Using the Technician Interface
Several AT modem commands contain a dollar sign ($) or backslash (\). The
Technician Interface uses the $ to reference a variable and the \ to prevent the substitution of a variable. If one of these symbols appears in the wfModemEntry.wfModemCfgInitString initialization command, the Technician
Interface does not set the string. For example:
[1:1]$ get wfModemEntry.wfModemCfgInitString.1.2
wfModemEntry.wfModemCfgInitString.1.2 = "ATF"
[1:1]$ set wfModemEntry.wfModemCfgInitString.1.2
"AT$SB64000";commit
Variable: Undefined Variable - SB64000
The Technician Interface interprets the command as containing an undefined variable and does not change the MIB value.
To set the MIB variable, you must add a backslash (\) in front of the symbol causing the confusion (that is, the $ or \). For example:
[1:1]$ get wfModemEntry.wfModemCfgInitString.1.2
wfModemEntry.wfModemCfgInitString.1.2 = "ATF"
[1:1]$ set wfModemEntry.wfModemCfgInitString.1.2
"AT\$SB64000";commit
X.25 PVCs
BayRS Version 12.20 software supports X.25 PVCs for X.25 IPEX Gateway services only.
301151-B Rev. 00 31
Release Notes for BayRS Version 12.20
Protocols Supported
BayRS Version 12.20 supports the following bridging/routing protocols and router configuration features:
• Advanced Peer-to-Peer Networking (APPN)
• AppleTalk and AppleTalk Update Routing Protocol (AURP)
• Asynchronous transfer mode (ATM)
• ATM Data Exchange Interface (ATM DXI)
• ATM Half Bridge (AHB)
• ATM LAN Emulation (802.3 and 802.5)
• Bandwidth Allocation Protocol (BAP)
• Binary Synchronous Communication Type 3 (BSC3)
• Bisync over TCP (BOT)
• Bootstrap Protocol (BootP)
• Border Gateway Protocol (BGP-3 and BGP-4)
• Classless interdomain routing (CIDR)
• Data compression (WCP and Hi/fn)
• Data link switching (DLSw)
• DECnet Phase IV
• Distance Vector Multicast Routing Protocol (DVMRP)
• Dynamic Host Configuration Protocol (DHCP)
• Encryption (WEP; proprietary)
• Exterior Gateway Protocol-2 (EGP-2)
• File Transfer Protocol (FTP)
• Frame relay (PVC, SVC)
• HP Probe
• Integrated Services Digital Network (ISDN)
• Interface redundancy (proprietary)
• Internet Control Message Protocol (ICMP)
32 301151-B Rev. 00
301151-B Rev. 00
Release Notes for BayRS Version 12.20
• Internet Gateway Management Protocol (IGMP)
• Internet Packet Exchange (IPX)
• Internet Protocol (IP)
• Internet Protocol Version 6 (IPv6)
• IPv6 PPP Control Protocol (CP)
• Internet Stream Protocol (ST2)
• Layer 2 Tunneling Protocol (L2TP)
• Learning Bridge
• Logical Link Control 2 (LLC2)
• Multicast OSPF (MOSPF)
• Native Mode LAN (NML)
• Network Core
• Network Time Protocol (NTP)
• Open Shortest Path First (OSPF)
• Open Systems Interconnection (OSI)
• Point-to-Point Protocol (PPP)
• Polled Asynch (PAS), also called Asynch Passthru over TCP
• Protocol prioritization
• Qualified Logical Link Control (QLLC)
• RaiseDTR dialup
• Remote Authentication Dial-In User Service (RADIUS)
• Resource Reservation Protocol (RSVP)
• Router discovery
• Router redundancy (proprietary)
• Routing Information Protocol (RIP)
• Service Advertisement Protocol (SAP)
• Simple Network Management Protocol (SNMP)
• Source Routing Bridge
33
Release Notes for BayRS Version 12.20
• Source Routing Bridge over ATM permanent virtual circuits (PVCs)
• Spanning Tree
• Switched Multimegabit Data Service (SMDS)
• Synchronous Data Link Control (SDLC)
• Telnet (inbound and outbound)
• Transmission Control Protocol (TCP)
• Transparent Bridge
• Transparent-to-Source Routing Translation Bridge
• Trivial File Transfer Protocol (TFTP)
• User Datagram Protocol (UDP)
• V.25bis dialup
• Virtual Network Systems (VINES)
• X.25 with QLLC
• Xerox Network System (XNS)
• XMODEM and YMODEM
Standards Supported
Table 6 lists the Request For Comments (RFCs) and other standards documents
with which Version 12.20 complies. BayRS Version 12.20 may support additional standards that are not listed in this table.
Table 6.
Standards Supported by Version 12.20
Standard
ANSI
T1.107b-1991
ANSI T1.404
ANSI X3t9.5
Bellcore FR-440
Description
Digital Hierarchy - Supplement to formats specifications
DS3 Metallic Interface Specification
Fiber Distributed Data Interface (FDDI)
Transport Systems Generic Requirements (TSGR)
(continued)
34 301151-B Rev. 00
301151-B Rev. 00
Release Notes for BayRS Version 12.20
RFC 768
RFC 791
RFC 792
RFC 793
RFC 813
RFC 826
RFC 827
RFC 854
RFC 855
RFC 856
RFC 857
RFC 858
Table 6.
Standard
Bellcore
TR-TSY-000009
Bellcore
TR-TSY-000010
IEEE 802.1
IEEE 802.1Q
IEEE 802.3
IEEE 802.5
IEEE 802.10
ITU Q.921
ITU Q.931
ITU X.25
Standards Supported by Version 12.20
(continued)
Description
Asynchronous Digital Multiplexes, Requirements and Objectives
Synchronous DS3 Add-Drop Multiplex (ADM 3/X) Requirements and Objectives
Logical Link Control (LLC)
IEEE 802.1Q VLAN tagging
Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
Token Ring Access Method and Physical Layer Specifications
Bridge with Spanning Tree
ISDN Layer 2 Specification
ISDN Layer 3 Specification
Interface between data terminal equipment (DTE) and data circuit-terminating equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuits
User Datagram Protocol (UDP)
Internet Protocol (IP)
Internet Control Message Protocol (ICMP)
Transmission Control Protocol (TCP)
Window and Acknowledgment Strategy in TCP
Ethernet Address Resolution Protocol
Exterior Gateway Protocol (EGP)
Telnet Protocol Specification
Telnet Option Specification
Telnet Binary Transmission
Telnet Echo Option
Telnet Suppress Go Ahead Option
(continued)
35
Release Notes for BayRS Version 12.20
Table 6.
Standard
RFC 859
RFC 860
RFC 861
RFC 863
RFC 877
RFC 879
RFC 888
RFC 894
RFC 896
RFC 903
RFC 904
RFC 919
RFC 922
RFC 925
RFC 950
RFC 951
RFC 959
RFC 994
RFC 1009
RFC 1027
RFC 1042
RFC 1058
RFC 1075
RFC 1076
Standards Supported by Version 12.20
(continued)
Description
Telnet Status Option
Telnet Timing Mark Option
Telnet Extended Options: List Option
Discard Protocol
Transmission of IP Datagrams over Public Data Networks
TCP Maximum Segment Size and Related Topics
"STUB" Exterior Gateway Protocol
Transmission of IP Datagrams over Ethernet Networks
Congestion Control in IP/TCP Internetworks
Reverse Address Resolution Protocol
Exterior Gateway Protocol Formal Specification
Broadcasting Internet Datagrams
Broadcasting Internet Datagrams in Subnets
Multi-LAN Address Resolution
Internet Standard Subnetting Procedure
Bootstrap Protocol
File Transfer Protocol
Protocol for Providing the Connectionless-mode Network Service
Requirements for Internet Gateways
Using ARP to Implement Transparent Subnet Gateways
Transmission of IP over IEEE/802 Networks
Routing Information Protocol
Distance Vector Multicast Routing Protocol (DVMRP)
Redefinition of Managed Objects for IEEE 802.3 Repeater Devices
(AN hubs only)
(continued)
36 301151-B Rev. 00
301151-B Rev. 00
Table 6.
Standard
RFC 1079
RFC 1084
RFC 1091
RFC 1108
RFC 1112
RFC 1116
RFC 1139
RFC 1155
RFC 1157
RFC 1163
RFC 1164
RFC 1166
RFC 1188
RFC 1191
RFC 1209
RFC 1212
RFC 1213
RFC 1267
RFC 1293
RFC 1294
RFC 1304
RFC 1305
RFC 1315
Release Notes for BayRS Version 12.20
Standards Supported by Version 12.20
(continued)
Description
Telnet Terminal Speed Option
BOOTP Vendor Information Extensions
Telnet Terminal-Type Option
Security Options for the Internet Protocol
Host Extensions for IP Multicasting
Appendix I. Internet Group Management Protocol
Telnet Line-mode Option
Echo Function for ISO 8473
Structure and Identification of Management Information for
TCP/IP-based Internets
Simple Network Management Protocol (SNMP)
BGP-2 (obsoleted by RFC 1267)
Application of BGP in the Internet
Internet Numbers
Proposed Standard for the Transmission of IP over FDDI
Path MTU Discovery
Transmission of IP Datagrams over SMDS
Concise MIB Definitions
MIB for Network Management of TCP/IP-based Internets
Border Gateway Protocol 3 (BGP-3; obsoletes RFC 1163)
Inverse ARP for Frame Relay
Multiprotocol Interconnect over Frame Relay (obsoleted by
RFC 1490)
Definition of Managed Objects for the SIP Interface Type
Network Time Protocol
Management Information Base for Frame Relay DTEs
(continued)
37
Release Notes for BayRS Version 12.20
Table 6.
Standard
RFC 1323
RFC 1331
RFC 1332
RFC 1333
RFC 1334
RFC 1350
RFC 1356
RFC 1376
RFC 1377
RFC 1378
RFC 1390
RFC 1403
RFC 1434
RFC 1483
RFC 1490
RFC 1552
RFC 1577
RFC 1583
RFC 1585
RFC 1634
RFC 1638
RFC 1654
RFC 1661
RFC 1662
Standards Supported by Version 12.20
(continued)
Description
TCP Extensions for High Performance
Point-to-Point Protocol (PPP; obsoleted by RFC 1661)
PPP Internet Protocol Control Protocol (IPCP)
PPP Link Quality Monitoring (obsoleted by RFC 1989)
PPP Authentication Protocols
The TFTP Protocol (Revision 2)
Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
PPP DECnet Phase IV Control Protocol (DNCP)
OSI over PPP
PPP AppleTalk Control Protocol (ATCP)
Transmission of IP and ARP over FDDI Networks
BGP OSPF Interaction
Data Link Switching: Switch-to-Switch Protocol
Multiprotocol Encapsulation over ATM AAL5
Multiprotocol Interconnect over Frame Relay (obsoletes RFC
1294)
The PPP Internetwork Packet Exchange Control Protocol (IPXCP)
Classical IP and ARP over ATM
OSPF Version 2
MOSPF: Analysis and Experience
Novell IPX over Various WAN Media (IPXWAN)
PPP Bridging Control Protocol (BCP)
Border Gateway Protocol 4 (BGP-4; obsoleted by RFC 1771)
Point-to-Point Protocol (PPP; obsoletes RFC 1331)
PPP in HDLC-like Framing
(continued)
38 301151-B Rev. 00
Table 6.
Standard
RFC 1717
RFC 1755
RFC 1757
RFC 1762
RFC 1763
RFC 1764
RFC 1771
RFC 1795
RFC 1819
RFC 1989
RFC 1990
RFC 2138
RFC 2139
RFC 2166
RFC 2205
VINES 4.11
Release Notes for BayRS Version 12.20
Standards Supported by Version 12.20
(continued)
Description
PPP Multilink Protocol (MP; obsoleted by RFC 1990)
Signaling Support for IP over ATM
Remote Network Monitoring Management Information Base
(RMON), for AN, ANH, and ARN equipped with data collection module only
PPP Banyan VINES Control Protocol (BVCP)
PPP DECnet Phase IV Control Protocol (DNCP)
PPP XNS IDP Control Protocol (XNSCP)
Border Gateway Protocol 4 (BGP-4; obsoletes RFC 1654)
Data Link Switching: Switch-to-Switch Protocol, Version 1
Internet Stream Protocol, Version 2
PPP Link Quality Monitoring (obsoletes RFC 1333)
PPP Multilink Protocol (MP; obsoletes RFC 1717)
Remote Authentication Dial In User Service (RADIUS)
RADIUS Accounting
Data Link Switching, Version 2.0, Enhancements
Resource ReSerVation Protocol (RSVP) -- Version 1 Functional
Specification
BayRS works with the Banyan VINES 4.11 standard. BayRS
Version 8.10 (and later) also supports VINES 5.50 sequenced routing.
301151-B Rev. 00 39
Flash Memory Cards Supported
You use Personal Computer Memory Card International Association (PCMCIA) flash memory cards to store the software image and the configuration files in Bay
lists the flash memory cards approved for use.
Table 7.
Size
4 MB
8 MB
16 MB
Approved Flash Memory Cards
Vendor
Advanced Micro Devices (AMD)
AMP
Centennial
Epson
IBM
Intel
AMD
Centennial
Epson
Intel
Centennial
Epson
Part Number
AMC004CFLKA-150
797262-3
797263-2
FL04M-20-11119
FL04M-20-11138
HWB401BNX2
IBM1700400D1DA-25
IMC004FLSAQ1381
AMC008CFLKA-150
AMC008CFLKA-200
AMC008CFLKA-250
AMC008DFLKA-150
AMC008DFLKA-200
AMC008DFLKA-250
FL08M-25-11119-01
FL08M-15-11119-01
FL08M-20-11138
FL08M-20-11119-01
HWB801BNX0
IMC008FLSP/Q1422
FL16M-20-11119-03
HWB161BNX2
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project