Page 1
BayRS Version 15.4.2.0
Part No. 308663-15.4.2.0 Rev 00
May 2003
600 Technology Park Drive
Billerica, MA 01821-4130
Release Notes for BayRS Version 15.4.2.0
Page 2
Copyright © 2003 Nortel Networks
All rights reserved. May 2003.
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 presen ted without express or
implied warranty. Users must take full responsibil ity for their applications of any products speci fied in this document.
The information in this document is proprietary to Nortel Networks Inc.
The software described in this document is furnished under a license ag reement and may only be used in accordan ce
with the terms of that license. The software license agreement is included in this document.
Trademarks
Nortel Networks, the Nortel Networks logo, the Globemark, Unified Networks, and AN, BCN, BLN, BN, BayRS,
BCC, and Passport are trademarks of Nortel Networks.
Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated.
Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated.
Cisco is a trademark of Cisco Technology, Inc.
FireWall-1 is a trademark of Check Point Software Technologies Ltd.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation.
NetWare is a trademark of Novell, Inc.
UNIX is a trademark of X/Open Company Limited.
CERT is a trademark of Carnegie Mellon Software Engineering Institute.
An asterisk after a name denotes a trademarked item.
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 clau se at FAR 52.227-19.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves the
right to make changes to the products described in this document without noti c e.
Nortel Networks Inc. does not assume any liability th at may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
Portions of the cod e in this software product ma y 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 do cumentation, 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, Be rkeley. 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 IMP L IED 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 discl osure (that may incorporate by reference certain limitations and notices imposed
by third parties).
ii 308663-15.4.2.0 Rev 00
Page 3
Nortel Networks Inc. Software License Agreement
This Software License Agreement (“License Agreement”) is between you, the end-user (“Customer”) and Nortel
Networks Corporation and its subsidiaries and affiliates (“Nortel Networks”). PLEASE READ THE FOLLOWING
CAREFULLY. YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE
THE SOFTWARE. USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE
AGREEMENT. If you do not accept these terms and conditions , return the Software, unused and in the original
shipping container, within 30 days of purchase to obtain a credit for the full purchase price.
“Software” is owned or licen sed by Nor tel Networks, its parent or one of its subsidiaries or affiliate s , and is
copyrighted and licensed, not sold. Software consists of machine-readable instructions, its components, data,
audio-visual content (such as images, text, recordings or pictures) and related licensed materials including all whole or
partial copies. Nort el Networks grants you a lice nse to use the Software only in the country where you acquired the
Software. You obtain no rights other than those granted to you under this License Agreement. Y ou are responsible for
the selection of the Software and for the installation of, use of, and results obtained from the Software.
1. Licensed Use of Software. Nortel Networks grants Cust omer a nonexclusive license to use a copy of the
Software on only one machine at any one time or to the extent of the activation or authorized usage level, whichever is
applicable. To the extent Software is furnished for use with designated hardware or Customer furnished equipment
(“CFE”), Customer is granted a nonexclusive license to use Software only on such hardware or CFE, as applicable.
Software contains trade secrets and Customer agrees to treat Software as confidential information using the same care
and discretion Customer uses with its o wn similar informati on that it does not wish to disclose, publish o r disseminate.
Customer will ensure that an yone who u ses the Software does so only i n compliance with the terms of this Agre ement.
Customer shall not a) use, copy, modify, transfer or distribute the Software except as expressly authorized; b) reverse
assemble, reverse compile, reverse engineer or otherwise translate the Software; c) create derivative works or
modifications unless expressly authorized; or d) sublicense, rent or lease the Software. Licensors of intellectual
property to Nortel Netw orks are bene fici aries of this pro vision. Upon termination or breach of the license b y Customer
or in the event designated hardware or CFE is no longer in use, Customer will promptly return the Software to Nortel
Networks or certify its destruction. Nortel Networks may audit by remote polling or other reasonable means to
determine Customer’s Software activation or usage levels. If suppliers of third party software included in Software
require Nortel Networks to include add itiona l o r different terms, Customer agrees to abide by such terms provided by
Nortel Networks with respect to such third party software.
2. Warranty. Except as may be otherwise expressly agreed to in writing between Nortel Networks and Customer,
Software is provid ed “AS IS” without any warranties (cond itions) of any kind. NORTEL NETWORKS DISCLAIMS
ALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT. Nortel Networks is not obligated
to provide support of a n y k ind fo r t he S oftware. Some jurisdictions do not allo w exclusion of implied warranties, and,
in such event, the above exclusions may not apply.
3. Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS
BE LIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b)
LOSS OF, OR DAMAGE TO, CUSTOMER’S RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR
SAVINGS), WHETHER IN CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT
OF YOUR USE OF THE SOFT WARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE
BEEN ADVISED OF THEIR POSSIBILITY. The forgoing limitations of remedies also apply to any developer and/or
supplier of the Soft ware . Suc h d eveloper and/or supplier is an inte nd e d bene ficiary of this Section. Some jurisdi cti on s
do not allow the se limitations or exclusions and, in such event, they may not apply.
308663-15.4.2.0 Rev 00 iii
Page 4
4. General
a. If Customer is the United States Gove rnment, the following paragraph shall apply: All Nortel Networks
Software available under this License Agreement is commercial computer software and commercial
computer s oftw are docum ent ation and, in the ev en t Soft wa re is li cen sed fo r or on behal f of t he Un ited S tat es
Government, the respective rights to the software and software documentation are governed by Nortel
Networks standard commercial license in accordance with U.S. Federal Regulations at 48 C.F.R. Sections
12.212 (for non-DoD en tities) and 48 C.F.R. 227.7202 (for DoD entities).
b. Customer may terminate the license at any time. Nortel Networks may terminate the license if Customer
fails to comply with the terms and conditions of this license. In either event, upon termination, Customer
must either return the Software to Nortel Networks or certify its destruction.
c. Customer is responsible for payment of any taxes, including personal property taxes, resulting from
Customer’ s use of the So ftware. Custome r agrees to comply with all applicable laws includin g all applica ble
export and import laws and r egulations.
d. Neither party may bring an action, regardless of form, more than two years after the cause of the action
arose.
e. The terms an d conditions of this License Agree ment form the complete and exclusive agreement between
Customer and Nortel Networks.
f. This License Agreement is governed by the laws of the country in which Customer acquires the Software. If
the Software is acquired in the United States, t hen this License Agreement is governed by the laws of the
state of New York.
iv
308663-15.4.2.0 Rev 00
Page 5
Contents
Preface
Hard-Copy Technical Manuals .......................................................................................... xi
How to Get Help ............................................................................................................... xi
Release Notes for BayRS Version 15.4.2.0
Upgrading to Version 15.4.2.0 ...........................................................................................2
Upgrading ATM Configurations ...................................................................................2
Cell Scrambling Default Changes for DS1/E1 and DS3/E3 ........................................2
Upgrading DVMRP Configurations ..............................................................................3
Upgrading FireWall-1 Configurations ..........................................................................3
Upgrading IP Route Filters ..........................................................................................6
Upgrading L2TP Configurations ..................................................................................6
Upgrading OSPF Configurations .................................................................................7
Upgrading Static Forwarding Policy Filters ..................................................................7
SNMP CERT Advisory ....... ...... ....... ...... ....... ...... ....... ............................................. ...... ......8
Known Anomaly .................................................................................................................8
NAT .............................................................................................................................8
BCC Guidelines .................................................................................................................8
BCC and BayRS Compatibility ....................................................................................9
Setting the Impedance Value for the Passport 2430 ...................................................9
Creating FTP from the BCC ........................................................................................9
Deleting Interfaces with the BCC ................................................................................9
Memory Requirements ..............................................................................................10
Platforms Supported .................................................................................................10
Interfaces Supported .................................................................................................10
Protocols Supported .................................................................................................11
Identifying Board Types .................. ....... ............................................. ...... ....... ...... ....12
AN and ANH Board Types ..................................................................................12
ARN Board Types ...............................................................................................15
308663-15.4.2.0 Rev 00 v
Page 6
ASN Board Types ...............................................................................................16
BLN and BCN Board Types ................................................................................16
Passport 2430 Board Types ...............................................................................18
Passport 5430 Board Types ...............................................................................19
System 5000 Board Types ..................................................................................20
Technician Interface Guidelines ......................... ............................................. ....... ...... ....20
Disabling a Protocol Using the TI Command Only ....................................................20
show ip routes Displays Partial Information in the Technician Interface ..................21
General Guidelines ..........................................................................................................21
Using Both Site Manager and the BCC .....................................................................21
AN/ANH and ARN Guidelines ...................................................................................21
DSU/CSU Test LED Remains On After Reset ....................................................21
Network Booting on DSU/CSU Interfaces ..........................................................22
ARN Router Not a Supported DVS RADIUS Client ............................................22
ATM Guidelines .........................................................................................................22
ATM Half Bridge Support ....................................................................................22
Deleting ATM from a Router If Signaling Is Enabled ...........................................23
Failover and Load Balancing for ATM VCs Not Supported .................................23
Aggregate Limitations for Sustainable Cell Rate ................................................23
ATM Routing Engine Performance and Scaling for PVC Environments .............23
Setting Buffer Sizes and Global/Local Memory .........................................................24
BayRS Router Buffer Sizes and Options ............................................................24
Setting Buffer Sizes on Specified Routers ..........................................................25
Allocating Global/Local Memory on BayRS Routers ..........................................26
Embedded Web Server Guidelines ...........................................................................27
Using the Embedded Web Server to Transfer Files ............................................27
Accessing the Embedded Web Server Using Internet Explorer .........................27
Dial Services Guideline .............................................................................................27
DLSw Guideline ........................................................................................................28
MPLS Guideline ........................................................................................................28
NAT Guidelines ........................ ...... ....... ...... ....... ...... ....... ...... ....................................28
Configuring NAT Dynamically .............................................................................28
ISP Mode Not Supported by NAT .......................................................................28
Configuring Bidirectional NAT .............................................................................29
Protocols/Configurations Not Supported by Bidirectional NAT ...........................29
vi
308663-15.4.2.0 Rev 00
Page 7
OSPF Guidelines ......................................................................................................30
Traffic Filters Guidelines ............................................................................................30
Downloading Internet Routes from an ISP ................................................................31
Interoperability with Non-Compliant Implementations of PIM ...................................32
Fragment Tagging in Bootstrap Messages .........................................................32
Non-Compliant Router Drops RP Advertisement with Zero Prefix .....................32
Incorrect Computation of Checksum of PIM Register Messages .......................33
Routers Ignore RP Priority and Hash Value During RP Selection ......................33
CES and TDM on Passport 5430 Only .....................................................................33
MPOA and VRRP over LANE Support ......................................................................33
FRE-2 DRAM Requirements ....................... ....... ...... ....... ...... ...... ....... ...... ....... ...... ....34
BayRS Bandwidth Broker for Differentiated Services ...............................................34
Event Database .........................................................................................................34
BayRS Flash Memory Requirements ........................................................................35
Configuring PU 4 and SDLC Link Stations ...............................................................35
Creating Multiple GRE Tunnels .................................................................................35
Protocol Prioritization No Call Filters and TCP Applications .....................................36
Support for Strata-Flash Card ...................................................................................36
Adding SDLC Changes Serial Parameter Settings ...................................................36
IPv6 Supported on ATM PVCs ..................................................................................37
Configuring RADIUS Servers ....................................................................................37
Configuring Frame Relay PVCs with Site Manager ..................................................38
VRRP Guidelines ......................................................................................................39
Operating Limitations and Cautions ................................................................................39
APPN ........................................................................................................................39
ARN 10MB Ethernet Base Module – MTU for 802.1Q Tagging ................................40
ATM ...................... ................................................................. .................................... 40
BCC ...........................................................................................................................41
BGP ...........................................................................................................................41
Deleting a Hybrid Mode Permanent Virtual Circuit (PVC) .........................................41
Differentiated Services ..............................................................................................41
DLSw — SDLC Fast and Slow Poll Timer Defaults ...................................................42
DLSw/APPN Boundary Port Use with AS400s and Others ......................................42
DSQMS ............................. .......................................................... .............................. 42
DVMRP – Use with Multinetted IP Interfaces ............................................................42
308663-15.4.2.0 Rev 00 vii
Page 8
FireWall-1 ....................................... .......................................................... ................. 43
Flash Compaction or Extensive File Management Use on ARE ...............................43
GRE ..........................................................................................................................43
Hot-Swapping Link Modules .....................................................................................44
IPsec ......................................................................................................................... 44
IP Services ........... ....... ...... .............................................. ...... ...... ....... ...... .................44
ISDN-BRI – Configuring B Channels on the ARN and Passport 2430 .....................44
MIBs ............................ .......................................................... .................................... 44
NAT Services ................................. ....... ...... ....... ............................................. ...... ....45
OSI .................................... ................................................................. .......................47
Passport 2430 and Passport 5430 ............................................................................47
RADIUS ............................. ....... ...... ....... ...... ............................................. ....... ...... ....48
RIP Export Filters ......................................................................................................49
Sync .......................................................................................................................... 49
SYSLOG ...................................................................................................................49
TFTP .........................................................................................................................49
Unnumbered IP Interfaces .................................................... ...... ....... ...... ....... ...... ....50
WAN Encryption ........................................................................................................50
WCP ............................ ................................ ................................ .......................... ....50
WCP for PPP Multilink ........................................................................................50
Adding Bandwidth on Demand Disables WCP Data Compression ....................50
Using Hardware Compression with Small Packets Causes Latency ..................50
Protocols Supported ........................................................................................................51
Standards Suppor t ed ........................... ....... ...... ....... ...... ....... ..........................................54
Flash Memory Cards Supported .....................................................................................59
viii
308663-15.4.2.0 Rev 00
Page 9
Tables
Table 1. DVMRP Parameter Defaults Changed ........................................................3
Table 2. BCC Board Types: AN and ANH Modules ................................................12
Table 3. BCC Board Types: ARN Modules .............................................................15
Table 4. BCC Board Types: ASN Modules .............................................................16
Table 5. BCC Board Types: BLN and BCN Modules ..............................................16
Table 6. BCC Board Types: Passport 2430 Modules ..............................................18
Table 7. BCC Board Types: Passport 5430 Modules ..............................................19
Table 8. BCC Board Types: System 5000 Modules ................................................20
Table 9. ATM Group Mode Service Record ............................................................24
Table 10. ATM Direct Mode Service Record .............................................................24
Table 11. BayRS Router Buffer Sizes and Options ..................................................25
Table 12. BayRS Flash Memory Requirements . ...... ............................................. ....35
Table 13. Default Settings for Serial Parameters without SDLC ...............................37
Table 14. Default Settings for Serial Parameters with SDLC ....................................37
Table 15. Standards Supported by Version 15.4.2.0 ................................................54
Table 16. Approved Flash Memory Cards ................................................................59
308663-15.4.2.0 Rev 00 ix
Page 10
Page 11
The Nortel Network s* BayRS* Version 15.4.2.0 is a softwa re release tha t includes
bug fixes added since BayRS Version 15.4.1.0. These release notes contain
guidelines for using BayRS Version 15.4.2.0.
Hard-Copy Technical Manual s
You can print selected technical manuals and release notes free, directly from the
Internet. Go to the www.nortelnetworks.com/documentation URL. Find the
product for which you n eed d ocume nta ti on. The n l ocat e t he s pec ific category and
model or version fo r your hardware or software product. Use Adobe* Acrobat
Reader* to open the manuals and release notes, search for the sections you need,
and print them on most standard printers. Go to Adobe Systems at the
www.adobe.com URL to download a free copy of the Adobe Acrobat Reader.
Preface
You can purchase printed books and documentation sets from Vervante. To order
printed documentation, go to Vervante at the www.vervante.com/nortel URL.
How to Get Help
If you purchased a service contract for your Nortel Networks product from a
distributor or authorized reseller, contact the technical support staff for that
distributor or reseller for assistance.
308663-15.4.2.0 Rev 00 xi
Page 12
Release Notes for BayRS Version 15.4.2.0
If you purchased a Nortel Ne tw orks s ervic e prog ram, contac t one o f the following
Nortel Networks Technical Solutions Centers:
Technical Solutions Center Telephone
Europe, Middle East, and Africa (33) (4) 92-966-968
North America (800) 4NORTEL or (800) 466-7835
Asia Pacific (61) (2) 9927-8800
China (800) 810-5000
Additional information about the Nortel Networks Technical Solutions Centers is
available from the www.nortelnetworks.com/help/contact/global URL.
An Express Routing Code (ERC) is a vailable for many Nortel Networks produc ts
and services. When you use an ERC, your call is routed to a technical support
person who specialize s in suppor ting tha t product or servi ce. To locate an ERC for
your product or service, go to the http://www130.nortelnetworks.com/cgi-bin/
eserv/common/essContactUs.jsp UR L.
xii
308663-15.4.2.0 Rev 00
Page 13
Release Notes for
BayRS Version 15.4.2.0
This document contains the latest information about Nortel Networks BayRS
Version 15.4.2.0, including information on the following topics:
Topic Page
Upgrading to Version 15.4.2.0 2
SNMP CERT Advisory 8
Known Anomaly 8
BCC Guidelines 8
Technician Interface Guidelines 20
General Guidelines 21
Operating Limitations and Cautions 39
Protocols Supported 51
Standards Supported 54
Flash Memory Cards Supported 59
308663-15.4.2.0 Rev 00 1
Page 14
Release Notes for BayRS Version 15.4.2.0
Upgrading to Version 15.4.2.0
To upgrade BayRS to Version 15.4.2.0, see Upgrading Routers to BayRS Version
15.xx, in your upgrade package. In addition, read the following sections.
Upgrading ATM Configurations
If you are upgrading fr om a BayRS v ersi on earl ier t han 12.20 and you de f in ed log
event traps for asynchron ous transfe r mode (ATM), ATM signaling, or ATM LAN
emulation, you must redefine these traps.
The ATM, ATM signaling, and ATM LAN emulation log event messages changed
in BayRS Version 12.20. The ATM_SIG entity (entity #95) no longer exists as a
separate entity. We have combined the ATM_SIG entity with the ATM entity
(entity #78). Combining and reorganizing these entiti es resulted in changes to the
ATM log event mess age numbers. We added new log e v ents to the ATM_LE entity
(entity #100), result ing in log event message number changes for LAN emulation
as well.
You can view the new and modified ATM log event messages in the event
database on the BayRS Online Library CD, or on the World Wide Web at this
URL:
http://www25.nortelnetworks.com/library/tpubs/events/
Cell Scrambling Default Changes for DS1/E1 and DS3/E3
For pre-15.x ver sions of BayRS, the default f or the cell scra mbling param eter is
set to On for DS1/E1 and DS3/E3 modules. However, the default for this
parameter has been changed to Off for all BayRS 15.x versions. If you are
upgrading from a pre-15.x v ersion (fo r example, 14.2 0) of BayRS you will need to
set this parameter to On to activate cell scrambling.
See Configuring ATM Services for additional information for setting this
parameter using the BCC or Site Manager.
2 308663-15.4.2.0 Rev 00
Page 15
Upgrading DVMRP Configurations
In BayRS Version 15.1.0.0 and later, the default values for two DVMRP timer
parameters have been changed to conform with the latest RFC for DVMRP
(draft-ietf-admire- dvmrp-v3-10). Table 1
new default values.
Table 1. DVMRP Parameter Defaults Changed
Parameter Name Default Value (in seconds)
Site Manager BCC
Garbage Timeout unconfirmed-route-timeout 340 260
Route Expiration Timeout route-expiration-timeout 200 140
DVMRP timers must be the same throughout the network. Therefore, if your
DVMRP network changes—for example, if you add a DVMRP router running
Version 15.1.0.0 (or later) to the network, or if you create a Version 15.1.0.0 (or
later) configuration file that contains DVMRP— make sure that the values for the
timer parameters match the ones already configured for the network as a whole.
Release Notes for BayRS Version 15.4.2.0
lists the pa rameters with their old and
Version
Earlier Than
15.1.0.0
15.1.0.0 and
later
Upgrading FireWall-1 Configurations
Complete the following steps only if you are upgrading FireWall-1* from a
BayRS version earlier than 13.20. If you are running Firewall-1 from BayRS
Version 13.20 or later, you do not have to complete these steps during your
upgrade to BayRS Version 15.4.2.0.
Note: Firewall-1 is not supported on the Passport* 2430 and Passport 5430
platforms.
1. Familiarize yourself with the Bay Command Console (BCC*).
Starting with BayRS Version 13.20, FireWall-1 no longer supports Site
Manager as a configuration tool. You must use the BCC to manage and
configure FireWall-1. For basic information about using the BCC, see Using
the Bay Command Console (BCC).
308663-15.4.2.0 Rev 00 3
Page 16
Release Notes for BayRS Version 15.4.2.0
2. Make sure that you will not lose acc ess to your router.
When you upgrade to BayRS Version 15.4.2.0, once you boo t your rou ter, the
Version 15.4.2.0 software invokes the default Fi reWall-1 secu ri ty pol i c y. This
default security policy drops all attempts at communication with the router.
If you manage a router at a remot e loca tion, y ou will no longe r be abl e to g ain
access to the router through the WAN connection. Before you upgrade, make
sure that you can gain access to the router by dialing in through the console
port, or that there is someone at the remote location who can configure the
router.
3. Reboot the router with BayRS Version 15.4.2.0, using an existing
configurat ion file.
4. Use the BCC to reenable FireWall-1 on each IP interface.
To reenable FireWall-1 on each IP interface, use the BCC to navigate to the
prompt for the slot/connector on which you have configured the IP interface
(for example,
box; eth 2/2). Then enter:
ip address
ip_address
address_mask
<ip_address>
mask
<address_mask>
is the IP address you have assi gned to the interface.
is the mask associated with the IP address.
The prompt for the IP interface appears.
For example, the following command invokes the prompt for IP interface
2.2.2.2/255.0.0.0 (which h as b een c onfigured on Ethernet slot 2, connector 2) :
ethernet/2/2# ip address 2.2.2.2 mask 255.0.0.0
ip/2.2.2.2/255.0.0.0#
At the promp t for the IP interface, enter the following command to reenable
FireWall-1:
firewall
The firewall prompt appears.
For example, the following command reenables FireWall-1 on the IP interface
2.2.2.2/255.0.0.0:
ip/2.2.2.2/255.0.0.0# firewall
firewall/2.2.2.2#
5. To use FireWall-1 on more than 32 circuits, set the policy index number
for each IP interface.
4 308663-15.4.2.0 Rev 00
Page 17
Release Notes for BayRS Version 15.4.2.0
The policy index allows multiple circuits to share the same instance of
FireWall-1. You can have up to 32 instances of FireWall-1, with many circuits
making up each FireWall-1 instance. All cir cuits in a grouping must share the
same security policy.
By default, the policy index for a circuit is equal to the circuit number. If you
are using FireWall-1 on fewer than 33 circuits, you do not have to use policy
indexes.
If you are using FireWall-1 on more than 32 circuit s, gr oup ci rc uits that share
the same security policy. Then, set the policy index on each circuit in a group
to the same value.
For examp le, supp ose you w ant to use FireWall-1 on 40 circu its. Th e f irs t f i ve
circuits share one securi ty pol ic y; the ne xt 35 sha re a di f fer ent s ecur ity p olic y.
Using the BCC, assign p olic y i nde x 1 to the first five circu its and p oli c y inde x
2 to the next 35 circuits. You then have a total of 40 firewall circuits on the
router, with two policy index values and two security policies.
Note: If you do not use policy index values and you configure more than 32
circuits on the route r, all IP forwarding is d isabl ed o n circ uits afte r the 32nd. If
you use policy index values, but configure more than 32 policy index
groupings, all circuits assigned policy indexes after the 32nd will have all IP
forwarding disabled. The router logs warning messages that can help you
determine whether you have any circuits on which all IP forwarding is
disabled.
The Check Point log viewer treats circuits that share a policy index as one
circuit.
If you are running FireWall-1 on more than 32 circuits and you therefore nee d
to set the policy index value, use the BCC to navigate to the firewall prompt,
as described in step 4. Then enter:
policy-index
is the index value, from 1 to 1023.
value
<value>
For example, the following command sets the policy index to 1:
firewall/2.2.2.2# policy-index 1
firewall/2.2.2.2#
6. Save the configuration file and reboot the router.
308663-15.4.2.0 Rev 00 5
Page 18
Release Notes for BayRS Version 15.4.2.0
7. Reinstall the security policy.
Since you previously defined a security policy (using the earlier version of
BaySecure FireWall-1), you do not nee d to def ine it ag ain. Ho we v er , y ou must
reinstall it in on the router. For com plete instructions on how to install the
security policy, see your Check Point FireWall-1 documentation.
If you want to install different security policies for different policy indexes,
use the Check Point FireW all-1 command line interface to enter the following
command:
fw load ../conf/
<config_file>
For example, the following command specifies that the system install the
security polic y in t he configuration file drop_ftp on policy index number 1 on
the router named asn1:
fw load ../conf/drop_ftp pol1@asn1
Upgrading IP Route Filters
If you have configured IP route filters and then disabled those filters (rather than
deleted them), when you upgrade to Version 15.4.2.0 from a version earlier than
14.00, the filters will be re-enabled. You must disable the filters again after the
upgrade is complete. If you do not want to use the filters, you might want to
consider deleting them before you upgrade to Version 15.4.2.0.
Upgrading L2TP Configurations
If you have a BayRS Version 12.10 configuration file that includes L2TP
operating on a router using BayRS Version 15.4.2.0, the router automatically
upgrades the assigned user network addresses to L2TP IP interface addresses.
L2TP IP interface addresse s 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.
pol
<policy_index_number>@<router_name>
6 308663-15.4.2.0 Rev 00
Page 19
The user networ k address es assig ned to Versi on 12.10 app ly to th e enti re rout er. In
Version 15.4.2.0, 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 will not be able to upgrade every slot
from a Version 12.10 configuration to a Version 15.4.2.0 configuration. For slots
that exceed the number of assigned user network addresses, you must manually
configure L2TP IP interface addresses. To do this, delete L2TP from the slot, and
then configure a new L2TP interface. Each slot must have L2TP IP interface
addresses.
If the number of configured L2TP slots is less than or equal to the number of
configured assigned user network addresses, the router automatically converts all
assigned user network addresses to L2TP IP addresses.
Upgrading OSPF Configurations
When you upgrade BayRS from releases earlier than Version 12.20, there must
not be an open shortest path first maximum transmission unit (OSPF MTU)
interface mismatch. If a mismatch exists, adjacencies will not form between
upgraded routers. All the OSPF routers forming adjacencies on a segment
(broadcast, point-to-point [PPP], Point-to-Multipoint, or nonbroadcast
multi-access [NBMA]) should have the same OSPF MTU size. You configure the
OSPF MTU size through the MTU Siz e paramete r in the OSPF Interf aces windo w
in Site Manager.
Release Notes for BayRS Version 15.4.2.0
BayRS Versions 14.00 and later comply wit h RFC 2328, which r equires the OSPF
MTU size feature.
Upgrading Static Forwarding Policy Filters
Internet Group Management Protocol (IGMP) static forwarding policy filters that
you created in versions earlier than Site Manager Version 7.20 will not work
correctly using Site Manager Version 7.20 or later. To use these IGMP static
forwarding poli cy f ilte rs, you must re-cr eate th em. F or inf ormati on about creati ng
IGMP static forwarding policy filters, see Configuring IP Multicasting and
Multimedia Services.
308663-15.4.2.0 Rev 00 7
Page 20
Release Notes for BayRS Version 15.4.2.0
SNMP CERT Advisory
BayRS Version 15.3 a nd later inclu de fixes for SNMP CERT* Adviso ry
CA-2002-03 for all suppo rt ed BayRS router platforms. BayRS is not impacted by
the trap attacks identified in the CERT Advisory but is impacted due to SNMP v1
request att acks. Site Ma nager Versi on 15.3 and later also include fixes for SNMP
CERT Advisory CA-2002-03. Site Manager provisioning is not impacted as a
result of the CER T Adv isory. Site Manager Tr ap Monitor is impac ted and the f ixes
are provided in the Site Manager Version 15.3 and later.
Known Anomaly
The following anomaly exists for BayRS 15.4.2.0. Nortel Networks aims to
resolve these anomalies in the near future.
NAT
Anomaly: Bidirectional NAT is not functional if you use a Passport 2430 as the
NAT router.
ID: Q00064004-04
Description: The Passport 2430 router is not supported as a NAT router for
bidirectional NAT.
Workaround: For BayRS Version 14.20 or later, do not use the Passport 2430
router as a NAT router with bidirectional NAT configured.
BCC Guidelines
The BCC is a command-line interface for configuring Nortel Networks devices.
Before using the BCC, see the following guidelines for using the software and the
platforms, protocols, interfaces, and hardware modules that the BCC supports.
8 308663-15.4.2.0 Rev 00
Page 21
Release Notes for BayRS Version 15.4.2.0
BCC and BayRS Compatibility
Starting with BayRS Version 14.00, the BCC software version number matches
that of BayRS. For e x ampl e, t he version for both the BCC and BayRS is 15.4.2.0.
We have made this change to help y ou al ign versions of the BCC with versions of
BayRS.
Setting the Impedance Value for the Passport 2430
The Passport 2430 c an acco mmodate ei ther BNC (req uires 75 ohm i mpedan ce) or
RJ45 (requires 120 ohm impedance) connectors. You can use the BCC to set the
impedance-value attribute to either 75 ohms or 120 ohms.
To set the impedance value on the FE1 interface, go to the FE1 prompt (for
example,
box; fe1) and enter:
impedance-value
value
is one of the following:
rj45-120-ohms (default)
bnc-75-ohms
<value>
For example, the following command sets the impedance value to 75 ohms for
this interfa ce on the router:
fe1/1/1# impedance-value bnc-75-ohms
fe1/1/1#
Creating FTP from the BCC
From the BCC, if you create FTP on the router, then delete it and re-create it, the
BCC faults. In this case, you must restart the BCC and create FTP on the router
again.
Deleting Interfaces with the BCC
Before using the BCC to dele te an interface, make sure that you did not use Site
Manager to configure the interface with a protocol that the BCC does not
recognize. If you did, use Site Manager to delete the interface.
308663-15.4.2.0 Rev 00 9
Page 22
Release Notes for BayRS Version 15.4.2.0
Memory Requirements
To use the BCC, each slot on the router must have:
• 16 MB of dynamic RAM (DRAM)
• 2 MB of free memory 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 the following message. In this case, you must use Site Manager
instead of the BCC to configure the router.
**Error** Unable to load bcc command from file system.
Loadable Module: bcc.exe
Platforms Supported
The BCC runs on AN*, ANH, ARN, ASN, Pass port 2430, Passport 5430, System
5000, and BN* platforms incl uding ARE, FRE-2, and FRE-4 processor modules.
Interfaces Supported
You can use BCC commands to configure the following interfaces:
•ATM
•Console
• DCM
• DSU/CSU
•Ethernet
• FDDI
• FE1
• FT1
• HSSI
• ISDN/BRI
•MCE1/MCT1
• Serial (synchronous)
• Token ring
• Virtual (referred to in Site Manager as Circuitless IP)
10 308663-15.4.2.0 Rev 00
Page 23
Table 2 through Table 8 on pages page 12 through 20 list the link and net modu les
that the BCC supports.
Protocols Supported
You can use BCC commands to configure the following protocols and services:
• Access (multiuser access accounts)
• ARP
•ATM
• BGP (including accept and announce policies)
• Data compression (WCP and Hi/fn)
• Dial backup
• Dial-on-demand
• DLSw
• DNS
•DSQMS
• DVMRP (including accept and announce policies)
• Frame relay (multilink not supported)
• FTP
• GRE
• HTTP
•IGMP
• IP (including accept policies, adjacent hosts, static routes, and traffic filt ers)
• IPX (including static-netbios-route)
•IPXWAN
• LLC2
•MPOA
•NAT
• NHRP
•NTP
• OSPF (including accept and announce policies)
• PPP (certain line parameters only; no multiline or multilink supported)
• Prop rietary Standard Point-to- Point
• RADIUS
Release Notes for BayRS Version 15.4.2.0
308663-15.4.2.0 Rev 00 11
Page 24
Release Notes for BayRS Version 15.4.2.0
• RIP (including accept and announce policies)
• Router discovery (RDISC)
•SDLC
•SNMP
• Source route bridge
• Spanning tree
•Syslog
•Telnet
• TFTP
• Transparent Bridge
• VRRP (Virtual Router Redundancy Protocol)
Identifying Board Types
Table 2 through Table 8 identify the board type pa ram e ter values displayed by th e
BCC.
Note: You cannot use BCC commands to configure an X.25 PAD or V.34
console modem daughterboard for the ARN router. Use Site Manager to
configure these daughterboards.
Inserting a daugh terboard into an AN ba se modul e redef ines i ts module ID and
board type.
AN and ANH Board T ypes
Table 2
Table 2. BCC Board Types: AN and ANH Modules
BCC Board Type
andeds 1033 AN-ENET (2 Ethernet ports, 2 serial ports)
andedsg 1050 ANH-8 (2 Ethernet ports, 2 serial ports) and an 8-port Ethernet
andedsh 1035 ANH-12 (2 Ethernet ports, 2 serial ports) and a 12-port Ethernet
12 308663-15.4.2.0 Rev 00
lists the AN and ANH board types.
Technician
Interface or MIB
Module ID Description
hub active for the first Ethernet port
hub
Page 25
Release Notes for BayRS Version 15.4.2.0
Table 2. BCC Board Types: AN and ANH Modules
Technician
Interface or MIB
BCC Board Type
andedst 1034 AN-ENET (2 Ethernet ports, 2 serial ports, 1 token ring port)
andst 1037 AN-TOKEN (2 serial ports, 1 token ring port)
andsti 1038 AN-TOKEN with ISDN (2 serial ports, 1 token ring port)
ansdsedst 1041 AN-ENET/TOKEN (1 Ether net port, 2 serial ports, 1 token ring
anseds 1024 AN-ENET (1 Ethernet port, 2 serial ports) with 16 MB DRAM
ansedsc 1090 AN-ENET with CSU/DSU (2 Ethernet ports, 2 serial ports)
ansedsf 1100 AN-ENET with T1/FT1 (2 Ethernet ports, 2 serial ports)
ansedsg 1047 ANH-8 (1 Ethernet port, 2 serial ports) and an 8-port Ethernet
ansedsgc 1094 ANH-8 with CSU/DSU (1 Ethernet port, 2 serial ports) and an
ansedsgf 1108 ANH-8 with T1/FT1 (1 Ethernet port, 2 serial ports) and an 8 -port
ansedsgi 1051 ANH-8 with ISDN (1 Ethernet port, 2 serial ports) and an 8-port
ansedsgj 1127 AN-ENET (1 Ethernet port, 2 serial ports, 1 fractional E1 port)
ansedsgjx 1137 AN-ENET (1 Ethernet port, 2 serial ports, 1 fractional E1 port)
ansedsgx 1048 ANH-8 with DCM (1 Ethernet port, 2 serial ports) and an 8-port
ansedsh 1026 ANH-12 (1 Ethernet port, 2 serial ports) and a 12-port Ethernet
ansedshc 1093 ANH-12 with CSU/DSU (1 Ethernet port, 2 serial ports) and a
ansedshf 1106 ANH-12 with T1/FT1 (1 Ethernet port, 2 serial ports) and a
ansedshi 1029 ANH-12 with ISDN (1 Ethernet port, 2 serial ports) and a 12-port
ansedshj 1125 AN-ENET (1 Ethernet port, 2 serial ports, 1 fractional E1 port)
Module ID Description
port)
hub
8-port Ethernet hub
Ethernet hub
Ethernet hub
and an 8-port Ethernet hub
and an 8-port Ethernet hub and DCM
Ethernet hub
hub
12-port Ethernet hub
12-port Ethernet hub
Ethernet hub
and a 12-port Ethernet hub
(continued)
308663-15.4.2.0 Rev 00 13
Page 26
Release Notes for BayRS Version 15.4.2.0
Table 2. BCC Board Types: AN and ANH Modules
Technician
Interface or MIB
BCC Board Type
ansedshjx 1136 AN-ENET (1 Ethernet port, 2 serial ports, 1 fractional E1 port)
ansedsj 1119 AN-ENET (1 Ethernet port, 2 serial ports, 1 fractional E1 port)
ansedsjx 1133 AN-ENET (1 Ethernet port, 2 serial ports, 1 fractional E1 port)
ansedst 1025 AN-ENET/TOKEN (1 Ethernet port, 2 serial ports, 1 token ring
ansedstc 1092 AN-ENET/TOKEN wi th CSU/ DSU (1 Eth ernet port, 2 serial ports,
ansedsti 1028 AN-ENET/TOKEN with ISDN (1 Ethernet port, 2 serial ports,
ansedstj 1123 AN-ENET (1 Ethernet port, 2 serial ports, 3 fractional E1 ports)
ansedstjx 1135 AN-ENET (1 Ethernet port, 2 serial ports, 3 fractional E1 ports)
ansedstx 1058 AN-ENET/TOKEN with DCM (1 Ethernet port, 2 serial ports,
ansedsx 1055 AN-ENET with DCM (2 Ethernet ports, 2 serial ports)
ansets 1030 AN-ENET (1 Ethernet port, 3 serial ports) with 16 MB DRAM
ansetsg 1049 ANH-8 (1 Ethernet port, 3 serial ports) and an 8-port Ethernet
ansetsh 1032 ANH-12 (1 Ethernet port, 3 serial ports) and a 12-port Ethernet
ansetst 1031 AN- ETS (1 Ethernet port, 3 serial ports, 1 token ring port)
antst 1039 AN-TOKEN (3 serial ports, 1 token ring port)
Module ID Description
and a 12-port Ethernet hub and DCM
with 16 MB DRAM
with 16 MB DRAM and DCM
port) with 16 MB DRAM
1 token ring port )
1 token ring port)
with 16 MB DRAM
with 16 MB DRAM and DCM
1 token ring port) with 16 MB DRAM
hub
hub
(continued)
14 308663-15.4.2.0 Rev 00
Page 27
Release Notes for BayRS Version 15.4.2.0
ARN Board Types
Table 3
lists the ARN board types.
Table 3. BCC Board Types: ARN Modules
Technician
Interface or MIB
BCC Board Type
arn7sync 8873 ARN Seven-Port Serial Expansion Module
arndcsu 8768 ARN 56/64K DSU/CSU Adapter Module
arne7sync 8872 ARN Seven-Port Serial Expansion Module, with 1 Ethernet Port
arnentsync 8864 ARN Ethernet and Tri-Serial Expansion Module
arnfe1 8780 E1/FE1 DSU/CSU Adapter Module
arnft1 8776 T1/FT1 DSU/CSU Adapter Module
arnis 8784 ARN ISDN BRI S/T Adapter Module
arnisdnu 8800 ARN ISDN BRI U Adapter Module
arnmbenx10 8896 ARN Ethernet Base Module xxMB DRAM with DCM
arnmbsen 8720 ARN Ethernet Base Module with 0, 4, 8, 16, or 32 DRAM
arbnbsfetx 8728 ARN 10/100BASE-TX Ethernet Module
arnmbsfefx 8729 ARN 100BASE-FX Ethernet Module
arnmbstr 8704 ARN Token Ring Base Module with 0, 8, 16, or 32 MB DRAM
arnpbenx10 8928 ARN Ethernet Expansion Module with DCM
arnpbtenx10 8960 ARN Ethernet and Tri-Serial Expansion Module with DCM
arnsenet 8832 ARN Ethernet Port Expansion Module
arnssync 8736 ARN Serial Adapter Module
arnstkrg 8816 ARN Token Ring Expansion Module
arntrtsync 8880 ARN Token Ring and Tri-Serial Expansion Module
arntsync 8848 ARN Tri-Serial Po rt Expansion Module
Module ID Description
308663-15.4.2.0 Rev 00 15
Page 28
Release Notes for BayRS Version 15.4.2.0
ASN Board Types
Table 4
lists the ASN board types.
Table 4. BCC Board Types: ASN Modules
Technician
Interface or MIB
BCC Board Type
asnqbri 2560 Quad BRI Net Module
denm 1280 Dual Port Ethernet Net Module
dmct1nm 2944 Dual Port MCT1 Net Module
dsnm1n 1540 Dual Port Synchronous Net Mod ule
dsnm1nisdn 1588 ISDN BRI/Dual Sync Net Module
dtnm 2048 Dual Port Token Ring Net Module
mce1nm 2816 MCE1 Net Module
mmasmbdas 1833 Hybrid PHY B FDDI Net Module
mmfsddas 1793 Multimode FDDI Net Module
qsyncm 1664 Quad Port Synchronous Net Module
se100nm 2304 100BASE-T Ethernet Net Module
shssinm 3584 HSSI Net Module
smammbdas 1825 Hybrid PHY A FDDI Net Module
smfsddas 1801 Single Mode FDDI Net Module
spex 512 SPEX Net Module
spexhsd 769 SPEX Hot Swap Net Module
Module ID Description
BLN and BCN Board T ypes
Table 5
Table 5. BCC Board Types: BLN and BCN Modules
BCC Board Type
atmcds3 5120 AG13110115 ATM DS-3
atmce3 5121 AG13110114 ATM E3
16 308663-15.4.2.0 Rev 00
lists the BLN* and BCN* board types.
Technician
Interface or MIB
Module ID
Site Manager
Model Number Description
Page 29
Release Notes for BayRS Version 15.4.2.0
Table 5. BCC Board Types: BLN and BCN Modules
Technician
Interface or MIB
BCC Board Type
atmcoc3mm 4608 AG13110112 ATM STS-3/STM-1 MMF
atmcoc3sm 4609 AG13110113 ATM STS-3/STM-1 SMF
comp 4353 AG2104037 Octal Sync with 32-context compression
comp128 4354 AG2104038 Octal Sync with 128-context compression
de100 4864 50038 100BASE-T Ethernet
dst416 40 5740 Dual Sync with token ring
dtok 176 5710 Dual token ring
enet3 132 5505 Dual Ethernet
esaf 236 5531 Dual Sync Dual Ethernet with 2-CAM filters
esafnf 232 5431 Dual Sync Dual Ethernet without hardware
gigenet 6400 Gigabit Ethernet-SX link module
gigenetlx 6401 Gigabit Ethernet-LX link module
mce1ii120 190 AG2111002 120-ohm Dual Port Multichannel E1 (MCE1-II)
mce1ii75 188 A G2111004 75-ohm Dual P ort Multichanne l E1 (MCE1-II) f or
mct1 168 5945 Dual Port MCT1
osync 4352 5008 Octal Sync
qef 164 5950 Quad Ethernet with hardware filters
qenf 162 5450 Quad Ethernet without hardware filters
qmct1db15 5377 AG2111007 Quad Port MCT1 DB15
qmct1ds0a 5378 AG2104052 Quad Port MCT1 DB15 with DS0A
qtok 256 50021 Quad token ring
shssi 225 5295 HSSI
smce1ii120 191 AG21110 01 120-ohm Single P ort Multichannel E1 (MCE1-II)
Module ID
Site Manager
Model Number Description
daughterboard
daughterboard
5532 Dual Sync Dual Ethernet with 6-CAM filters
filters
for ISDN PRI and Leased Line
75-ohm Leased Line
for ISDN PRI and Leased Line
(continued)
308663-15.4.2.0 Rev 00 17
Page 30
Release Notes for BayRS Version 15.4.2.0
Table 5. BCC Board Types: BLN and BCN Modules
Technician
Interface or MIB
BCC Board Type
smce1ii75 189 AG2111003 75-ohm Single Port Multichannel E1 (MCE1-II)
smct1 169 5944 Single Por t MCT1
sqe100 6144 Quad 100BASE-TX link module
sqe100fx 6145 Quad 100BASE-FX link module
sse 118 5410 Single Sync with Ethernet
sync 80 5280 Quad Sync
wffddi1m 193 5943 Hybrid FDDI with single mode on connector B
wffddi1mf 197 5949 Hybrid FDDI with single mo de on connector B
wffddi1s 195 5942 Hybrid FDDI with single mode on connector A
wffddi1sf 199 5948 Hybrid FDDI with single mode on connector A
wffddi2m 192 5930 Multimode FDDI
wffddi2mf 196 5946 Multimode FDDI with hardware filters
wffddi2s 194 5940 Single Mode FDDI
wffddi2sf 198 5947 Single Mode FDDI with hardware filters
Module ID
Site Manager
Model Number Description
for 75-ohm Leased Line
and with hardware filters
and with hardware filters
(continued)
Passport 2430 Board Types
Table 6
Table 6. BCC Board Types: Passport 2430 Modules
BCC Board Type
arndcsu 8768 56/64K DSU/CSU Module
arnfe1 8780 E1/FE1 DSU/CSU Adapter Module
arnft1 8776 T1/FT1 DSU/CSU Adapter Module
arnisdns 8784 ARN ISDN BRI S/T Adapter Module
arnisdnu 8800 ARN ISDN BRI U Adapter Module
18 308663-15.4.2.0 Rev 00
lists the Passport 2430 board types.
Technician
Interface or MIB
Module ID Description
Page 31
Release Notes for BayRS Version 15.4.2.0
Table 6. BCC Board Types: Passport 2430 Modules
Technician
Interface or MIB
BCC Board Type
arnmbsfetx 8728 10BASE-TX Second Ethernet Module
arnssync 8736 ARN Serial Adapter Module
arnv34 8752 ARN V34 Modem Module
Module ID Description
Passport 5430 Board Types
Table 7
lists the Passport 5430 board types.
Table 7. BCC Board Types: Passport 5430 Modules
Technician
Interface or MIB
BCC Board Type
arndcsu 8768 56/64K DSU/CSU Module
arnfe1 8780 E1/FE1 DSU/CSU Adapter Module
arnft1 8776 T1/FT1 DSU/CSU Adapter Module
arnisdns 8784 ARN ISDN BRI S/T Adapter Module
arnisdnu 8800 ARN ISDN BRI U Adapter Module
arnssync 8736 ARN Serial Adapter Module
arnv34 8752 ARN V34 Modem Module
ds1e1atm 8160 DS1/E1 ATM
ds3e3atm 8161 DS3/E3 ATM
fbrmbdfen 8000 FBR Ethernet Module
pmcqsync 8321 Quad Serial PMC Module
Module ID Description
308663-15.4.2.0 Rev 00 19
Page 32
Release Notes for BayRS Version 15.4.2.0
System 5000 Board Types
Table 8
lists the System 5000 board types.
Table 8. BCC Board Types: System 5000 Modules
Technician
Interface or MIB
BCC Board Type
asnqbri 2560 Router Quad Port ISDN BRI Net Module
atm5000bh 524544 Centillion Multiprotocol Engine
denm 1280 Router Dual Ethernet Net Module
dmct1nm 2944 Router Dual Port MCT1 Net Module
dsnm1n 1540 Router Dual Synchronous Net Module
dtnm 2048 Router Dual Token Ring Net Module
iqe 1408 5380 Ethernet Router Module
mce1nm 2816 Router MCE1 Net Module
mmasmbdas 1833 Router Hybrid PHY B FDDI Net Module
mmfsddas 1793 Router Multimode FDDI Net Module
qsyncnm 1664 Router Quad Port Synchronous Net Module
se100nm 2304 Router 100BASE-T Ethernet Net Module
shssinm 3584 Router HSSI Net Module
smammbdas 1825 Router Hybrid PHY A FDDI Net Module
smfsddas 1801 Router Single Mode FDDI Net Module
Module ID Description
Technician Interface Guidelines
The Technician Interface (TI) is an alter native command-line interface for
configuring Nortel Networks devices. Before using the Technician Interface, see
the following guidelines.
Disabling a Protocol Using the TI Command Only
You should avoid disabling a protocol using a mib set in Technician Interface to
the wfProtocols MIB as th is can cau se une xpected re sults. If you are usi ng TI, you
should disable protocol s using t he disab le TI command onl y. You can also disable
protocols using Site Manager or BCC.
20 308663-15.4.2.0 Rev 00
Page 33
Release Notes for BayRS Version 15.4.2.0
show ip routes Displays Partial Information in the Technician Interface
For a router conf i gurat ion enco mpass ing IP equa l co st rout es, the s how ip routes
command in Technician Interface displays partial information only.
When using the Technician Interface, you must use the following command to
retrieve all equal- cost routes and show the complete routing table information:
ip routes -A
General Guidelines
The following guidelines supplement the instructions in the BayRS
documentation set.
Using Both Site Manager and the BCC
You can use either Site Manager or the BCC to manage Nortel Networks routers.
If you want to use both tools, follow these guidelines:
• Do not try to use both Sit e Man age r and the BCC to manage a single router at
the same time. You are prohibited from doing so with a lock-out mechanism.
• Site Manager cannot understand traffic filters you configured using the BCC.
• Site Manager configuration files that contain the / (forward slash) character in
any of the ASCII text input s (for ex ample, Unnumbered CCT Name) cause an
error when viewed in the BCC using the
error halts printing of the text parameter at the / character and displays the
message "Too many BCC ID values" at the end of the display. To
prevent this problem, do not use the / character when entering ASCII text for
parameters in Site Manager.
show config -all command. This
AN/ANH and ARN Guidelines
Follow these guidelines when using AN, ANH, or ARN routers.
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.
308663-15.4.2.0 Rev 00 21
Page 34
Release Notes for BayRS Version 15.4.2.0
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.
ARN Router Not a Supported DVS RADIUS Client
The ARN router is not a supported DVS RADIUS client.
ATM Guidelines
Follow these guidelines when configuring ATM:
ATM Half Bridge Support
BayRS supports ATM Half Bridge (AHB).
Note: ATM Half Bridge (AHB) is not suppor ted on either th e Passport 2430 or
Passport 5430.
Please be aware that some users, operating under certain conditions, may
encounter issues such as the following:
• Whe n AHB caches an unsecure host that it learned via ARP, the associated
idle time is 0. The idle time remains at 0 and does not ag e correctly.
• When you boot a router running AHB, the ARE slot logs a fault message.
• When you reset the AHB, it stops forwarding traffic out of the AHB port.
• If you configure AHB on an ATM null PVC, the router may crash.
• If you configure AHB and add a PVC to the router while another system is
sending a ping message to your ro uter , the ARE slot may crash and may be gin
executing the cold start hardware diagnostics.
22 308663-15.4.2.0 Rev 00
Page 35
Release Notes for BayRS Version 15.4.2.0
Deleting ATM from a Router If Signaling Is Enabled
Do not delete ATM from a router if you enabled signaling on an ATM circuit.
Otherwise, Site Manager, the BCC, or the Technician Interface will restart after a
few minutes.
Failover and Load Balancing for ATM VCs Not Supported
You can configure multiple ATM virtual circuits (VCs) to the same destination
address. However, this kind of configuration does not provide load balancing or
failover support.
Aggregate Limitations for Sustainable Cell Rate
The aggre gate sustainable cell rate (SCR) for all PVCs configured should not
exceed 353207 cells per second for ARE OC-3 SONET/SDH ILI pairs. It is
advisable to set SCR to less than that to ensure there is sufficient bandwidth for
any SVCs that may also be configured on this interface. The SCR is set at the
Xmit Sustainable Cell Rate (cells/s) parameter using Site Manager and at the scr
parameter using the BCC.
ATM Routing Engine Performance and Scaling f or PVC Environments
The results in Table 9
and Table 10 reflect the performance of the ARE as the
number of PVCs increased us ing the foll o wing PVC acc ess me thods, r espect i v ely :
• ATM Group Mode: multiple PVCs per service re cord
• ATM Direct Mode: single PVC per service record
These ARE performance figures are based on unid ir ect ional 128-byte UDP traffic
to ensure that each PVC shared an equal amount of load. All PVC configurations
were tested using one ATM slot with an OC3-MM interface (155 Mbsp).
Note: Performance results may vary from router to router depending on how
your network is configured.
308663-15.4.2.0 Rev 00 23
Page 36
Release Notes for BayRS Version 15.4.2.0
ATM Group Mode Service Record
Table 9 lists the maximum number of PVCs that could be configured at the
specified throughput rate using the ATM group-mode access method.
Table 9. ATM Group Mode Service Record
Throughput Rate Maximum Number of PVCs Tested
90 Mbps
100
ATM Direct Mode Service Record
Table 10 lists the maximum number of PVCs that could be configured at the
specified thoughtful rate using the ATM direct-mode access method.
Table 10. ATM Direct Mode Service Record
Throughput Rate Maximum Number of PVCs Tested
90 Mbps
65 Mbps 40
45 Mbps 60
30 Mbps 80 to 100
20
Setting Buffer Sizes and Global/Local Memory
BayRS Router Buffer Sizes and Options
Table 11
not buffers can be resized and to what size(s) they can be set. The table also
indicates whether global/local memory allocation (memory carving) is available
by router, as configured.
lists the default buffer sizes for BayRS routers and indicates whether or
24 308663-15.4.2.0 Rev 00
Page 37
Release Notes for BayRS Version 15.4.2.0
For more information se e, “Setting Buff er Sizes on Spec if ied Routers” on pag e 25
and “Allocating Global/Local Memory on BayRS Rout ers” on page 26.
Table 11. BayRS Router Buffer Sizes and Options
Router
BN/FRE2-040 5 KBs No Yes
BN/FRE2-060 5 KBs No No
BN/FRE2-060E 5 KBs No N o
BN/FRE4 5 KBs No No
BN/ARE 10 KBs Yes - 5, 6, 7, 8, or
*AN/ANH 1824 bytes Yes - 4800 bytes Yes
*AN/ANH with token ring 4800 bytes No Yes
ARN 1824 bytes Yes - 4800 bytes No
ARN with token ring 4800 bytes No No
ASN 5 KBs No Yes
Passport 2430 5 KBs No No
Passport 5430 5 KBs No No
System 5000/Ethernet 5 KBs No Yes
System 5000/token ring 5 KBs No Yes
System 5000/VNR (5782) 10 KBs Ye s - 5, 6, 7, 8, or
Default Buffer
Size
Set Buffer Size?
9 KBs
9 KBs
Set Local/Global
Memory?
No
No
*Flash-based AN/ANH only.
Setting Buffer Sizes on Specified Routers
You can set buffer sizes on the following BayRS routers by setting a MIB variable
using the Technician Interface:
• BN/ARE
• System 5000/VNR
308663-15.4.2.0 Rev 00 25
Page 38
Release Notes for BayRS Version 15.4.2.0
• Non-Token-Ring AN
• Non-Token-Ring ARN Routers
By default, AN and ARN routers (without token ring modules installed) initialize
with a buffer size of 1824 bytes, which prevents these routers from accepting
packets larg er t han 1824 bytes. To allow the non-to ken-ring AN or ARN router to
accept larger packets, you can increase the buffer size by setting the MIB variable
wfKernCfgParamEntry.wfKernCfgParamBufSize to 4800. You can also increase
the buffer size for the BN/ARE and System 5000/VNR using this procedure.
For complete instructions on using the Technician Interfac e to set MIB variables,
see Using Technician Interface Software. The following exampl e shows
Technician Interface commands you might use to reset the MIB variable
wfKernCfgParamEntry.wfKernCfgParamBufSize to 4800 for a non-token ring
AN router:
set wfKernCfgParamEntry.wfKernCfgParamDelete.1 1
set wfKernCfgParamEntry.wfKernCfgParamBufSize.1 4800
commit
set wfKernCfgParamEntry.wfKernCfgParamDelete.1 2
commit
save config 2:config
reset 1
To set the buffer size back to its default of 1824 bytes, issue the following
command:
set wfKernCfgParamEntry.wfKernCfgParamBufSizeReset.1 1
commit
Allocating Global/Local Memory on BayRS Routers
You can change the default memory allocation (between global and local) on the
following rout er s:
• AN/ANH
• ASN (flash-based only)
• BN (FRE2-040 only)
• System 5000 (with Ethernet or token ring only)
You can use either Site Manager or Technician Interface to allocate global/local
memory on these routers:
26 308663-15.4.2.0 Rev 00
Page 39
Release Notes for BayRS Version 15.4.2.0
• Site Manager: Select Administration > Kernel Configuration option
• Technician Interface: Enter
Note: This “memory carving” feature is not available on the ARN, Passport
2430, Passport 5430, BN (with FRE2-60, FRE2-060E, or FRE4), or System
5000 with VNR (5782) configured.
Embedded Web Server Guidelines
Follow these guidelines when using the embedded web server:
Using the Embedded Web Server to Transfer Files
When you use the embedded Web server to transfer file s to or from the router,
HTTP (Hypertext Transfer Protocol) encapsulates the data . You do not need to be
concerned with selecting a file format (text or binary, for example) the way you
would if you were using FTP (File Transfer Protocol) or TFTP (Trivial File
Transfer Protocol) to transf er the files.
For exampl e, to trans fer an imag e f ile to th e router, use your browser’s default file
format type to transfer th e file to the router’s flash memory. The file arrives at the
router as an image file from which you can boot the router.
set command for wfKernCfgParamEntry object
Accessing the Embedded Web Server Using Internet Explorer
When you access the embedded Web server using Microsoft Internet Explorer
Version 4.72.2106.8, the file page is blank. However, Internet Explorer Version
4.72.3110.8 works correctly. We suggest that you upgrade to Version 4.72.3110.8
or later.
Dial Services Guideline
Dial backup services do not stay up on a Passport 2430 or ARN with an FT1 line
configured for Bay Standard PPP protocol unless you first enable Remote
Loopback Detection on the logical line. See "Chapter 8: Configuring FT1
Services" chapter in Configuring WAN Line Services for more information on
enabling remote loopback detection.
308663-15.4.2.0 Rev 00 27
Page 40
Release Notes for BayRS Version 15.4.2.0
DLSw Guideline
To establish connectivity for NetBIOS Clients where DLSw is configured and
attached to a switched environment, enter the following command st ring using the
Technician Interface:
set wfLlcInterfaceEntry.24.
Within your set command you must specify the Ethernet
DLSw router where the clients are attached. You sh ould also set the value for the
MIB attribute to “2” to force the encapsulation of broadcast packets in the to ken
ring format.
MPLS Guideline
BayRS does not support Multiprotocol Label Switching (MPLS). The former
implementation of MPLS in BayRS (Versions 13.10 through 15.1.0.0) was based
on an early draft of the specification developed by the IETF MPLS working
group. This implementation has been removed from BayRS since it is not
compliant with RFC 3031 and did not interoperate with standard MPLS
implementations.
NAT Guidelines
Follow these guidelines when configuring NAT:
Configuring NAT Dynamically
<circuit number>
2;commit
<circuit number>
on the
When you configur e 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.
ISP Mode Not Supported by NAT
NAT does not support the ISP mode feature. ISP mode is a BayRS global IP
parameter that allows you to enable the BGP soloist and disable IP forwarding
caches. By default, ISP mode is disabled in BayRS.
28 308663-15.4.2.0 Rev 00
Page 41
Release Notes for BayRS Version 15.4.2.0
Configuring Bidirectional NAT
For multidomai n NAT to work, in addition to configuring bidirectional NAT on
the router, you must:
1. Configure RIP2 on the NAT router interfaces and on each router with
which the NAT router will be exchanging routing updates. Otherwise,
you must configure static routes or a combination of RIP2 and static
routes.
2. Install Domain Name System (DNS) server on a machine that is running
UNIX or Windows NT and that ha s acces s to the NAT rout er. DNS server
software is available from third-party suppliers and may be included
with your operating system software.
3. Configure BayRS DNS proxy on each interface of a NAT router to be
used for dynamic bidirectional translation. You do not need to configure
DNS proxy for a static bidirectional network address translation.
4. Configure B ayRS DNS client on each device that will be initiating traffic
in the domains of your multidomain NAT configuration.
Protocols/Configurat ions Not Supported by Bidirectional NAT
• OSPF
• BGP
• IPsec on the same interfaces configured for bidirectional NAT
•BayRS ECMP
308663-15.4.2.0 Rev 00 29
Page 42
Release Notes for BayRS Version 15.4.2.0
OSPF Guidelines
If you are using Open Shortest Path First (OSPF) services, pl ease keep the
following guidelines in mind:
• As of BayRS Version 14.00, the OSPF backup soloist feature is no longer
supported.
• According to RFC 2328, the cost of an OSPF route to an aggreg at ed gr oup of
networks should be the distance to the furthest network in the group. A new
MIB parameter, wfOspfAggrUseMaxCost, allows you to determine how to
summarize the subnets using the area range. To use the furthest cost in the
routing table, set this MIB to 1 (Enable). If you accept the def ault, 2 (Disable),
the OSPF route cost is represented as the shortest path to a network within the
aggregated group of networks.
• When OSPF is configured on a synchronous PPP interface using Site
Manager, the interface type is set to Point-to-point rather than to the actual
default, Broadcast.
• When an OSPF routing table contains two routes with the same network
number (LSID), and one of the rout es is unr eacha ble and th e other r oute has a
32-bit networ k mas k, o nly the route with the 32-bit network mask will appear
when you en ter the
show ospf lsdb command in BCC.
Traffic Filters Guidelines
Follow these guidelines when configuring traffic filters:
• If you apply a traffic filter to a multinetted interface (that is, an interface with
more than one IP address), the traffic filt er might not work correctly. To
ensure that the filter works correctly, you must assign the same filter to all of
the IP addresses on the interface.
• Site Manager cannot understand traffic filters that you configured using the
BCC.
• When implementing outbound traffic filters for LAN protocols, in some
configurations the filters might cause a decline in throughput performance.
For LAN circu its where the forwarding rate of the router is critical, monitor
the throughput performance after configuring outbound traffic filters. If you
notice an unacceptable performance degradation, try using inbound traffic
filters.
30 308663-15.4.2.0 Rev 00
Page 43
Release Notes for BayRS Version 15.4.2.0
• If you use Site Manager or the BCC to configure IP traffic filters with
precedence values that are higher than the number of traffic filters configured,
you might reach the maximum precedence value before you create the
maximum number of filt ers . Wh en yo u re ach the maximum precedence value
of 31 traffic filters, the router generates an error if you try t o configure a filter
with a precedence of 32. The system does not place you in extended filtering
mode.
For example, if y ou create the following five traffic filters, an error occurs
when you create the fifth filter:
Filter 1 precedence = 28
Filter 2 precedence = 29
Filter 3 precedence = 30
Filter 4 precedence = 31
Filter 5 precedence = 32 (error occurs here)
As a workaround, you can take one of the following actions:
-- Reassign the precedence value of traffi c filters 1 through 5 to lower
values.
-- Use the T ec hnician Inte rface to t urn on exten ded f iltering mode a nd let the
system assign precedence values to additional traffic filters on the IP
interface.
Downloading Internet Routes from an ISP
To minimize the time required to download routes from an Internet service
provider (ISP), adjust two IP global parameters. Use the BCC to set the
routing-table-indexes value to 10000 and the routing-table-deviation value to 50,
as follows:
ip#routing-table-indexes 10000
ip#routing-table-deviation 50
See Configuring IP, ARP, RARP, RIP, and OSPF Services for more information
about these commands.
308663-15.4.2.0 Rev 00 31
Page 44
Release Notes for BayRS Version 15.4.2.0
Interoperability with Non-Compliant Implementations of PIM
This section describes compatibility issues that exist when running Protocol
Independent Multicast (PIM) in a network that consists of both Nortel Networks
routers and non-compl iant implementations of PIM on routers.
Note: The term “non-compliant router” is used in the following sections to
indicate routers (such as Cisco* routers) that run implementations of PIM that
do not comply with all el ements of RFC 2362.
Nortel Networks routers can be configured for compatibility with non-standard
implementations of PI M at the RFC2362 Non- Compatib ilit y paramet er using Sit e
Manager. For additional information see “Enabling and Disabling Router
Compatibil ity with RFC 23 62” in Configuring IP Multicasting and Multimedia
Services.
Fragment Tagging in Bootstrap Messag es
In a PIM network in which Nortel Networks and non-compliant routers
interoperate, a non-compliant router sends bootstrap packets that contain a
fragment tag set to a zero value. When the Nortel Networks router receives these
packets, it treats them as duplicate packets and immediately drops them.
To enable a Nortel Networks router to accept bootstrap packets from a
non-compliant router, select the PIM_BSR_ZERO_FRAGMENT_TAG option at
the RFC2362 Non-Compatibility parameter using Site Manager.
Non-Compliant Router Drops RP Advertisement with Zero Prefix
If you configu re a non-complia nt router to serv e as the boot strap rout er (BSR) and
you configure a N ortel Networks router to serve as an RP router for a PIM
domain, the non-compliant router drops any RP advertisement packet it receives
from the RP router that contains a zero group prefix count. As a result, the
non-compliant rou ter cannot advert ise RP set info rmatio n to all PIM rou ters in the
domain.
To ensure that the non-compliant router sends advertisement messages to all
multicast group ranges using address 224.0.0.0/4, select the
PIM_RP_ZERO_PREFIX_COUNT option at the RFC2362 Non-Compatibility
parameter using Site Manager. Selecting this option sends non-zero prefix count
in RP advertisement messages.
32 308663-15.4.2.0 Rev 00
Page 45
Release Notes for BayRS Version 15.4.2.0
Incorrect Computation of Checksum of PIM Register Messages
By default, Nortel Networks routers computes checksum on the PIM header only.
Compatibility issues arise when Nort el Networks routers intero perate with
non-compliant routers which compute checksum on the PIM header and data
portion of the packet.
To enable checksum compatibility with a non-compliant router, select the
PIM_REGISTER_CHECKSUM option at the RFC2362 Non-Compatibility
parameter using Site Manager.
Routers Ignore RP Priori ty and Hash Value During RP Selection
You configure mu lt ip le RPs responsibl e for the same or overlapping gro up ranges
in a PIM domain. For RPs r esponsibl e for the same g roup ra nges, a non-c ompliant
router sele cts the first RP on the RP list, regardless of the RP priority and hash
value. For RPs responsible for overlapping group ranges, a non-compliant router
selects the router with the most specific group range, regardless of the RP priority
and hash value.
As a workaround, con f igure only on e RP rout er for each u nique g rou p range . This
allows th e Nort el Net works rout er an d t he non -comp liant r outer to s elect the sa me
RP.
CES and TDM on Passport 5430 Only
The following features and parameters are supported for the Passport 5430 only:
• Circu it Emulation Services (CES)
• Time Division Multiplexing (TDM)
• Traffic Shaping parameters: Service Category, AAL Type, VBR Type,
Congestion indicatio n, Cell los s priority, Initial and Mini mum Cell Rates, Cell
rate increase and decrease factors
MPOA and VRRP over LANE Support
BayRS Version 15.4.2.0 does not support running both Virtual Router
Redundancy Protocol ( VRRP) and Mult i-Prot ocol Ov er ATM (MPOA) ov er LAN
Emulation (LANE).
308663-15.4.2.0 Rev 00 33
Page 46
Release Notes for BayRS Version 15.4.2.0
FRE-2 DRAM Requirements
The FRE-2 processor card requires a minimum of 16 MB DRAM.
BayRS Bandwidth Broker for Differentiated Services
To implement a differentiated se rv ice s network using a BayRS bandwidth broker,
you must install the BayRS Bandwidth Broker, also known as the policy server,
software on a PC running Microsoft* Windows NT* 4.0. The Nortel Networks
router that communicates with the bandwidth broker must be operating with
BayRS Version 13.20 or later software.
To download the policy server software and learn how to configure it:
1. Go to the Router Management Labs page at the following URL:
http://www.nortelnetworks.com/rml.
2. Click on So ftware Solutions.
3. If you are a registered user, enter your email address. If not, register.
You see a list of solutions for which you can download software.
4. Scroll through the list to locate the Policy Server.
From here you can download the software and the user manual.
Event Database
You can view the event database on the World Wide Web and the BayRS Onli ne
Library CD . To access the event database on the World Wide Web, go to:
http://www25.nortelnetworks.com/library/tpubs/events/
To access the event database on the BayRS Online Library CD, follow the
instructions in the CD booklet.
The event database includes a search facility that allows you to sort events by
entity number, event number, severity , and text of the event message. For example,
you can list only the warning messages for the IPX entity.
34 308663-15.4.2.0 Rev 00
Page 47
BayRS Flash Memory Requirements
BayRS software ships the following software suites (Table 12) on flash memory
cards for each platform listed:
Table 12. BayRS Flash Memory Requirements
Platform Flash Memory Required Associated Software Suites
AN/ANH 16 MB corp_suite, ip_access, office_suite
ARN 8 or 16 MB corp_suite, ip_access, office_suite
ASN 16 MB corp_suite, lan_suite, system_suite,
BN 16 or 32 MB atm_suite, corp_suite, corpfre2_suite,
Passport 2430 16 MB corp_suite, ip_access, office_suite
Passport 5430 32 MB corp_suite, ip_access, office_suite
System 5000 16 MB corp_suite, lan_suite, syste m_sui te,
Release Notes for BayRS Version 15.4.2.0
wan_suite
lan_suite, system_ su ite, vnr_suite,
wan_suite
vnr_suite, wan_suite
Configuring PU 4 and SDLC Link Stations
If you use PU 4 devices with Synchronous Data Link Contr ol (SDLC) and modulo
128, set the SDLC parameters MAXOUT and M AXIN to 127. You see these
parameters in the SDLC Link Station Configuration window. For instructions on
setting these parameters, see Configuring SDLC Services.
Creating Multiple GRE Tunnels
When creating multiple GRE tunnels dynamically , you ca n c onfigure a maximum
of five point-to-point GRE tunnels. In multipoint configurations, you can
configure 64 GR E tunnels per interface.
308663-15.4.2.0 Rev 00 35
Page 48
Release Notes for BayRS Version 15.4.2.0
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 connected.
If a demand line configur ed with a no cal l f ilter goe s do wn, the no call f i lter drops
the TCP packet th at matches the no cal l f i lter rule. Because TCP ne v e r rec ei v es a n
acknowledgment that the packet was dropped, the TCP application continues to
retransmit that packet until the connection times out and the application stops
operating.
Note: No call filters are specific to dial services . For additional i nformation
about traffic filters and protocol prioritization, see Configuring Traffic Filters
and Protocol Prioritization.
Support for Strata-Flash Card
BayRS supports the Strata-Flash card on AN, ANH, ARN, ASN, and BN routers.
For details about flash cards, see “Flash Memory Cards Supported” on page
page 59
.
Adding SDLC Changes Serial Parameter Settings
When you configure SDLC on a serial interface, the router software automatically
changes the values for the following serial parameters:
• cable type
• clock source
• internal clock speed
• signal mode
36 308663-15.4.2.0 Rev 00
Page 49
Release Notes for BayRS Version 15.4.2.0
Defaults for serial parameters, without SDLC, are listed in Table 13.
Table 13. Default Settings for Serial Parameters without SDLC
Parameter Default Setting
cable type null
clock source external
internal clock speed clk64k
signal mode balanced
After you add SDLC to an interf ace, the settings for the serial parameters change.
The new settings are listed in Table 14
Table 14. Default Settings for Serial Parameters with SDLC
Parameter Default Setting
cable type rs232
clock source internal
internal clock speed clk19200
signal mode unbalanced
.
IPv6 Supported on ATM PVCs
BayRS supports IPv6. You can configure IPv6 using Site Manager on an ATM
PVC interface.
Configuring RADIUS Servers
To enable RADIUS authentication for multilevel access or to use vendor-specific
attributes (VSAs), you must configure the BSAC RADIUS server with the
following files:
• bayrs.dct
• vendor.ini
• dictiona.dcm
308663-15.4.2.0 Rev 00 37
Page 50
Release Notes for BayRS Version 15.4.2.0
These files loa d at server startu p and enable the server to recognize the
vendor-specific RADIUS clients. You can locate these files in the bsac directory
on the BayRS Router and Si te Manager Software update CD.
• To configure a Nortel Networks RADIUS server, copy the three files to the
directory that you define at installation time (typically C:\RADIUS\Service).
• T o con figure a non-Nortel Networks RADIUS server, use the bayrs.dct file as
a reference to chang e the e xisting RADIUS dictio nary. Because bayrs.dct is in
the format of some popular RADIUS servers, you might be able to use it as a
direct replaceme nt for the e xisting RADIUS dictionar y . Fo r more info rmation,
see the vendor’s documentation.
Note: To use RADIUS with IP utilities such as FTP, NTP, HTTP, and Telnet,
your RADIUS server must support VSAs.
The RADIUS dictionary file (bayrs.dct) defines the Nortel Networks
vendor- specific attrib utes. The Norte l Networks v endor ID is 1 584, as allocat ed by
the Internet Assigned Numbers Authority. Use this ID in the heade r when using
VSAs.
For more information on See this document
RADIUS
BaySecure Access Control BaySecure Access Control Administration Guide (for
Multilevel Access
Configuring RADIUS
your specific platform: UNIX*, NetWare*, or Windows
NT)
Using the Bay Command Console (BCC)
Configuring Frame Relay PVCs with Site Manager
When creating a new PVC or moving a PVC out of the Frame Relay defa ult
service record in Site Ma nag er, the circuit name must be filled in or BCC will not
recognize the PVC.
38 308663-15.4.2.0 Rev 00
Page 51
Release Notes for BayRS Version 15.4.2.0
VRRP Guidelines
Follow these guidelines when configuring VRRP:
• You must first configure an IP address before you can configure a VRRP
interface to associate with that specific IP address.
• If you have VRRP configured on the router and you want to delete the
associated IP address, you must first delete VRRP before deleting the
associated IP address. Failure to do so r esults in an u nforced pani c on the
router which causes other protocols to go down and come back up.
• Bridging and VRRP should not be configured on the same physical port.
For additio nal i nfo rmat ion on configuring VRRP, see Conf i gur ing VRRP Services
and BayRS Version 15.4.0.0 Docu mentation Change Notice.
Operating Lim ita tions and Cautions
Be aware of the following limitations and cautions when using BayRS 15.4.2.0.
APPN
The following limitations exist for APPN services in BayRS:
• The value conf ig ure d for the Advanced Peer-to-Pe er Networking (APPN) TG
Number parameter in Site Manager is not being used; the TG number on a
link station is being auto-negotiated.
• A ping from an Advanced Peer-to-Peer Networking (APPN) network node
(NN) or end node (EN) may fail to reach the remote end nodes if the ENs are
located downstream from branch network nodes (BrNNs) and connect to the
BrNNs over connection networks.
• When an APPN router with high performance routing (HPR) enabled
experiences heavy traffic, it restarts.
• If Advanced Peer-to-Peer Networking (APPN) traffic ingress and egress
points are configured on different slots on a BN router, then the number of
APPN transactions processed per minute is significantly lower than when all
APPN traffic is restricted to a single slot. However, you can reconfigure the
BN to run APPN on only one slot as a workaround to this limitation.
308663-15.4.2.0 Rev 00 39
Page 52
Release Notes for BayRS Version 15.4.2.0
ARN 10MB Ethernet Base Module – MTU for 802.1Q Tagging
When you configure VLAN tagging on the ARN 10MB Ethernet Base Module,
the MTU for the interface is set to 1518 bytes for packets on this line. Although
the Ethernet Base Module supports tagged packets, it does not support 802.1Q
tagged frames of greater than 1518 bytes (1514 plus 4-byte tag). However, there
are other Ethernet interfaces (for example, Ethernet and Tr i-Serial Expansion
Module or the 10/100-TX UTP Base Module) with an MTU of 1522 which
support the maximum size tagged packet (1518 plus 4-byte tag).
You may have
to correct for this by reducing the MTU set for the other tagged hosts on the
LAN attached to the 10BT motherboard Ethernet port to 1518 bytes.
ATM
The following limitations exist for ATM services in BayRS:
• Failover and lo ad balancing for ATM VCs is not supporte d. You can configure
multiple ATM virtual circuits (VCs) to the same destination addre ss.
However, this kind of configuration does not provide load balancing or
failover support.
• The ATM traffic parameter maximum burst size (MBS) is not supported.
• Differentiated Services Queue Management and Scheduling (DSQMS) is not
supported in ATM.
• Using the BCC to delete an ATM inter f ac e or a s er v ic e r eco rd with more than
570 PVCs can cause a watchdog timeout on the router. To prevent this from
occurring on configurations with more than 570 PVCs, use Site Manager to
delete the interface, or use the BCC to delete the PVCs before you delete the
ATM interface.
• If there is a loss of signal to a r outer du ring a pe riod of hea vy traffic, the ATM
interface on the router might stop functioning. If the ATM interface stops
functioning, you must reboot the router to recover.
• On the ARE, BayRS does not release virtual channel connections when they
time out. To maintain the availability of VCCs for new activities, configure a
LAN emulation client (LEC) other than the router to release the inactive
VCCs.
• Setting ATM signal ports on a Switch and Router Conflict
40 308663-15.4.2.0 Rev 00
Page 53
BCC
BGP
Release Notes for BayRS Version 15.4.2.0
• If you are using a switch with ATM signal ports set to V3.1, be sure to set the
signaling setting on the router to V3.1 to prevent a conflict between the two
devices. If you accept the default setting of V3.0 for the router, the router
faults repeatedly unt il you change the set ti ng to V3.1.
If a context is deleted and re-created in the same BCC source file, unexpected
results may occur. The create/delete MIB is set to deleted when issuing the
deletion, but it is not reset to created when re-configuring the context.
The following limitations exist for BGP services in BayRS:
• If you specify a router interface address as the BGP peer address and that
address is included in the network list for an announce policy configured on
that router, BGP will not announce that network to a BGP peer, even if the
remote peer is configured to accept that network from the peer. To ensure that
the router announces the network, set the local peer to a router address that
does not fall in the network range of an announce policy. For example, if the
local router interface 2.2.5.1 falls within the range specified by the network
list of an announce policy, use a different interface as the local BGP peer.
• Attempts to source a BCC config file with BGP peers configured fail while
using the command: peer <local>/<remote> as <value>. When this error
occurs, the
not a local IP address." However, the following workaround is available. You
can prev ent this probl em by rear ranging t he commands in the source input f ile
to make sure that the IP addr esses are con figured before the BGP peers.
router displays the message "BGP PEER Config Error. LOCAL is
Deleting a Hybrid Mode Permanent Virtual Circuit (PVC)
If you configur e SRB on a r outer, do not delete hybrid mod e PVCs. Othe rwise, all
slots will restart.
Differentiated Services
You can configure differentiated services on no more than one IP address of a
multinetted IP interface.
308663-15.4.2.0 Rev 00 41
Page 54
Release Notes for BayRS Version 15.4.2.0
DLSw — SDLC Fast and Slow Poll Timer Defaults
If you have a ro uter performin g SDLC to LLC con v ersion, an d you use the def ault
values for the SDLC parameters Fast Poll Timer and Slow Poll Timer, SDLC
controller performance is degraded. To avoid this problem, change the Fast Poll
Timer to 200 and the Slow Poll Timer to 400. Changing these settings improves
performance for both single- and dual-switch DLSw configurations in which the
router acts as an SDLC primary device. Depending on the number of SDLC
controllers you are s uppor t ing , you may n eed to increase or dec rea se the number s
to improve controller response time and router performance.
DLSw/APPN Boundary Port Use with AS400s and Others
Do not configur e any explicit APPN adjacent link stations on the DLSw/APPN
boundary (VCCT) port, unless you are certain that the adjacent link station (for
example, an AS400) will not a ttempt to con nect to t he APPN node. Oth erwise, th e
DLSw/APPN boundary (VCCT) function fails to operate correctly and the router
might restart.
DSQMS
The following limitations exist for DSQMS services in BayRS:
• Queue starvation can occur despite priority-time-quantum settings. Queues
with the same priority level and priority-time-quantum sett ings may
nevert heless experience queue starvation if one of the queues is
bandwidth-heavy.
To address this condition you can configure traffic policing for the
bandwidth-heavy traffic flow to an acceptable rate for its assigned DSQMS
Priority Queue. Configure traffic policing before the DSQMS outbound
interface to c ontrol UDP as well as TCP flows.
• DSQMS is not supported with Protocol Priority Queuing (PPQ).
DVMRP – Use with Multinetted IP Interfaces
You cannot use the BayRS Version 15.4.2.0 implementation of Distance Vector
Multicast Routing Protoc ol (DVMRP) with circuits with multinetted interfaces
(that is, interfaces with more than one IP address) .
42 308663-15.4.2.0 Rev 00
Page 55
FireWall-1
Release Notes for BayRS Version 15.4.2.0
The following problems can occur while using FireWall-1 services in BayRS:
• Check Point Log Viewer displays the incorrect time which is appr oximately
one hour behind. For example, if the correct time is 12:17, the Log Viewer
displays the time as 11:17. Log events from the management station (or fw
daemon) display the correct time.
• Check Point Log Viewer incorrectly reports that a router has stopped logging.
You can ignore the “Stopped Logging” message whenever the logging
continues uninterrupted.
• You cannot define an address range for source and destination addresses fo r a
FireWall-1 Security policy.
• You cannot disable FireWall-1 dynamically using the BCC even though the
legal values for the state object of firewall are listed as enabled and disabled.
• FireWall-1 is not supported for the Passport 2430 or Passport 5430.
• Running the GUI version of Pa cket Capture (UNIX or W indo ws) connecte d to
an interface with Firewall-1 services configured may result in tag violations
on several slots.
Flash Compaction or Extensive File Management Use on ARE
Do not perform a flash compaction or extensive file management on a busy or
production ARE module. Doing so may cause a fault in the module.
GRE
If a Generic Routing Enca psulation (GRE) tunnel is configured with an incorrect
remote physical IP address, and the IP address is then corrected, th e GRE tunnel
does not come up as expected. This condition occurs when you configure a GRE
tunnel using either the BCC or Site Manager.
Howev er , the follo wing workaro und is a vai lable. To change the remote ph ysical IP
address to a valid IP address for a GRE tunnel, first delete and then re-create the
adjacent host entry (IP ) or the static host entry (IPX) for that connection.
308663-15.4.2.0 Rev 00 43
Page 56
Release Notes for BayRS Version 15.4.2.0
Hot-Swapping Link Modules
Attempts to remove and reinsert (hot-swap) a link module without first powering
down the router can cause a fault to occur. Following the fault, the slot does
recover. When a link module is hot-swapped, the protocols must reset, so there is
no additional downtime caused by the fault. However, you can prevent this router
fault by disablin g the int erfaces on the slot befor e remo ving the l ink module . After
reinsertin g the link modu le you can then reenable the interfaces on th e slot.
IPsec
If you change the setting of the router’s Internet Protocol Security (IPsec) feature
(MIB variable wfIpIntFCfgEnableSecurity) from Disabled to Enabled, the router
loses its IP connection. You must reboot the router to recover.
IP Services
If you disable the IP directe d broadcast fea ture while conf iguring a ro uter , a global
reset of IP occurs, resulting in a temporary outage and the closing of all IP utility
sessions such as TCP and Telnet.
ISDN-BRI – Configuring B Channels on the ARN and Passport 2430
The ARN and Passport 2430 can use only three B channels. If you select 2B + D
service for one BRI interface, you must use 1B + D service for the second
interface.
MIBs
• The MIB-II ifIndex is incorrect after you delete a circuit, causing problems
with Omniview. The router creates MIB-II at tr ibutes when you create circuits
on the router plat form. The MIB-II attributes include the ifNumber, which is
the number of network inter faces (regardless of their current s tate) present on
the system, and the ifIndex, which is a uniqu e value for each interface (the
ifIndex value is in the range from 1 through the value of ifNumber).
44 308663-15.4.2.0 Rev 00
Page 57
• If a router receives a Breath of Life (BofL) packet, the router considers it an
NAT Services
The following limitations and cautions exist for NAT services in BayRS:
• NAT does not operate in IP ISP Mode. To avoid this problem you should
Release Notes for BayRS Version 15.4.2.0
If you dynamically delete a circuit on the router, the MIB-II attribute
ifNumber decreases by 1. If you check the IfIndex, the result will be
noncontiguous. When the router is polled for ifNumber, it shows the correct
value but when the ifIndex is polled, ther e is a chance that there are
indexes/circuits outside the correct range.
The result is that SNMP management stations such as Omniview will display
an error.
unknown protocol. The router increments the MIB entry that tracks unknown
protocols each time an interface receives a BofL packet,
wfIfEntry.wfIfInUnknownProtos. However, you can d isa bl e Bof L packets for
the interface as a workaround to this problem.
disable the global IP ISP mode parameter.
• NAT and IPsec cannot int eroperate wi th ov erlapping so urce IP addres s ranges,
because NAT takes precedence. IPsec cannot process a source address that is
also in a NAT address range. However, the following workarounds are
available:
For UNIX systems, you can separate IP hosts on the networks into two
groups: a NAT-only group and an IPsec-only group. You can then use the
multinetted interfaces or two network interface cards on a host to establish
these two logical groups on one physical host.
You can also conf ig ure NAT and IPsec on diff erent de vi ces s o tha t one Bay RS
router runs IPsec and another BayRS router runs NAT.
• If you are using BayRS version 14.20 or later, you must use version 14.20 or
later of the nat.bat script file.
• NAT cannot handle more than 600 dynamic translatio ns at an int er- packet rate
of less than 10 milliseconds. For inter-packet rates of 10 milliseconds or
greater, NAT successfully handles 1500 dynamic translations per slot. These
performance thresholds pertain to the BN, BLN, and Passport 5430 routers
with 64 MB processor cards installed.
308663-15.4.2.0 Rev 00 45
Page 58
Release Notes for BayRS Version 15.4.2.0
• If you are using NAT and FireWall-1 on the same router, the FTP application
does not work correctly using port 20.
• When disabled, the NAT Install Private Address feature does not block
advertisement of private addresses within a unidirectional NAT environment.
This feature is set using Site Manager (Install Private Address) or the BCC
(visible-private-ad dress). In orde r to prevent a NAT private address from
being advertised into the NAT public domain, a RIP announce policy filter or
an OSPF announce policy filter must be configured (depending on which
routing protocol is used).
The following two sections describe how to configure RIP and OSPF
announce policy filters for unidirectional NAT:
Configuring a RIP Announce Policy Filter for Unidirectional NAT
Configure a RIP announce policy filter to ignore the networks in the private
domain. Using Site Manager (or the BCC), create a RIP announce policy and
set the Acti on parameter to Ignore. You should then specif y matching criteria
for the RIP announce policy by entering the NAT private networks in the
Networks list and entering the IP address of the NAT public interface in the
Outbound Interfaces list.
For additional information on configuring RIP announce policies, see
Configuring IP, ARP, RARP, RIP, and OSPF Services.
Configuring an OSPF Announce Policy Filter for Unidirectional NAT
Do not configure OSPF on the NAT private interface(s). Otherwise, you will
not be able to prevent the advertisement of private networks into the OSPF
domain because these routes will be considered OSPF internal routes. OSPF
announce policy filters apply only to OSPF external routes.
For NAT to work with OSPF, the NAT router must be configured as an OSPF
ASBR (Autonomous System Border Router). As an OSPF ASBR, the NAT
priv a te net works are injected into the OSPF domai n as OSPF external routes.
To prevent this, an OSPF announce policy filter must be configured on the
NAT router. Using Site Manager (or the BCC), create an OSPF announce
policy and set the Action parameter to Ignore. You should then specify
matching criteria for the OSPF announce policy by entering the NAT private
networks in the Networks list.
For additional information on configuring OSPF announce policies, see
Configuring IP, ARP, RARP, RIP, and OSPF Services.
46 308663-15.4.2.0 Rev 00
Page 59
OSI
You cannot filter OSI over X.25 with a user-defined filter.
Passport 2430 and Passport 5430
The following limitations exist on the Passport 2430 and/or Passport 5430
platforms:
• RMON and Mini-RMON are not supported in the Passport 2430. RMON is
not supported on the Passport 5430.
• Passport 5430 does not support any LAN emulation services (LANE or
MPOA).
• Passport 2430 does not support ATM, except for ATM DXI.
Release Notes for BayRS Version 15.4.2.0
• Hi/fn* LZS*
Passport 5430 pl atforms. Ho we ve r , Hi/ fn data compres sion is sup ported on al l
other BayRS platforms.
• If you want to run either of the following protocols/configurations on the
Passport 2430, you must upgrade the router to 32 MB of dynamic RAM
(DRAM):
– Advanced Peer-to-Peer Networking (APPN)
– IP with MTU size greater than 2048 bytes on the Passport 2430
• Passport 5430 Ethernet fl ow control on the 10/100 Ethernet module does not
function correctly when the flow control pause time in the received MAC
control frame is set to 65535 (the default value). When the router receives a
control frame with a pause time value of 65535, it begins retransmitting data
prematurely. However, the following workaround is available. Reset the Flo w
Control Pause Time parameter in Site Manager, or the fc -pause-time
parameter in the BCC, to a value from 32 through 65534.
• The BCC CES admin-status parameter d oes not w ork on t he P asspo rt 5430 . If
you attempt to disable the CES PVC using the BCC admin-status down
command, the CES circuit continues to pass traffic. However, the following
workaround is available. To disable the CES PVC, go back one level in the
BCC and enter state disabled. To reenable the CES PVC, go back one level
and enter state enabled.
data co mpression i s not support ed on eithe r the P assport 2430 or
308663-15.4.2.0 Rev 00 47
Page 60
Release Notes for BayRS Version 15.4.2.0
• The Passport 2430 second Ethernet adapter module supports 10Mbps line
speeds only. The interface does not support 100Mbps line speed,
auto-negoti ation, full duple x mo de, or PPP over Ethernet (Payee). The seco nd
Ethernet adapter module must be installed on slot one of the Passport 2430
only.
• The following limitations exist for the Passport 5430 with the Quad Serial
PMC module installed:
– Unsupported protocols i nclude A O T, BOT, SMDS, and ATMDXI, and X.25.
– Quad Serial PMC module is not designed to be configurable using the
inst_pp5430.bat script file.
– In a configur ation where an Ethernet interface forwards data to all four
serial interfaces of the Quad Serial PMC module at rates of 2 MB/second per
port, the Ethernet interface stops. This issue does not occur at lower traffic
rates. However, the supportable performance level has not yet been
determined. Nortel Networks is investigating this issue in search of a fix that
will support full rate use.
– If you set up back-to-back configuration on a Passport 5430 with a Quad
Serial PMC module installed, yo u must set t he interna l clock spee d to rates no
greater than 128Kbs per second.
RADIUS
The following limitations and cautions exist for RADIUS services in BayRS:
• Setting the debug message level for RADIUS enables you to specify the
amount of information contained in the messages logged by a device. When
an authorized user sets the debug message level to high, debug messages
containing the server secret (password) are logged by the device. Because any
user can view the mes sage l og, thi s coul d potentia lly c ompromi se the secur ity
of your network. If you have to set the debug message level to high for debug
purposes, be sure to complete the following steps to reset the debug message
level and remove the server secret from the log following your debug:
1. Using either the BCC or the Technician Interface, set the debug
message level to no-debug (default) for the device.
2. Clear the l og to remove instances of the server secret that could
potentially be viewed by users with any and all access privileges.
48 308663-15.4.2.0 Rev 00
Page 61
• Cutting and pasting BCC commands to configure RADIUS entries on the
router may cause a fault in RADIUS to occur. This fault is caused by the
timing delays introduced when commands are copied across the network to
the router interface. To prevent this fault, use the BCC
enter RADIUS entries on multiple slots.
RIP Export Filters
Setting the From Protocols parameter for a RIP export filter to any value other
than the “Any” option causes the filter to fail. Consequently, the RIP export route
filter does not work if you specify any of the following options: RIP, EGP, OSPF,
Direct, Static, or BGP-3. To avoid this problem, be sure to use the “Any” option
when configuring all RIP export filters.
Sync
If the cable is remov e d fro m any synchronous port except octal sync on a BN, the
router gives no indication of the problem and the link remains active. The
configured WAN protocol closes all connections when the synchronous lin e driv er
detects connection signal lost. To prevent this problem, enable the Sync Polling
parameter (Configuration Manager -> Edit Line -> Edit Sync Parameters).
Release Notes for BayRS Version 15.4.2.0
source command to
SYSLOG
The status of syslog changes to down when you set the slot-lower-bound and
slot-upper-bound parameters to the same value (same slot) on a BN router
platform. Both syslog and filter logging terminate operation. However, the
following workaround is available. Do not set the slot-lower-bound and
slot-upper-bound parameters to the same value.
TFTP
If you try to use the Router File Manager to TFTP a file to the router from a
Windows directory that includes long names and spaces, the transfer fails. To
prevent this problem, move the file you want to send to a directory with a simple
name of no more than 15 bytes and no space characters.
308663-15.4.2.0 Rev 00 49
Page 62
Release Notes for BayRS Version 15.4.2.0
Unnumbered IP Interfaces
You cannot use the disable and enable scripts on unnumbered IP interfaces. The
scripts do not allow an interface IP address format specifying both the IP address
0.0.0.0 and the circuit number. However, you can use Site Manager or the
Technician Interface to disable unnumbered IP interfaces.
WAN Encryption
DES-40 WAN Encryption Option (WEP) or DES-56 WEP are no longer
supported on any BayRS platform. However, BayRS will support backward
compatibility with earlier versions of BayRS that are currently running WEP. We
recommend that you use Internet Protocol Security ( I Psec) services for security.
WCP
WCP for PPP Multilink
If you configure an existing PPP/WCP non-multilink circuit for multilink (on
BayRS Ve rsion 12.10 or later) and the CC P Type parameter is set to CCP, WCP
must be deleted and re-added to the circuit to negotiate WCP above the bundle.
See Configuring Data Compression Services for additional information.
Adding Bandwidth on Demand Disables WCP Data Compression
Adding Bandwidth on Demand to a PRI circuit disables WCP data compression.
The call comes up and traffic flows, but WCP never creates a VC and does not
compress traf fic.
Using Hardware Compression with Small Packets Causes Latency
When the traffic pattern on at least one line of a multilink bundle is primarily
small packet s (i.e., 64 bytes), using hardware compression will res ult in latency.
To avoid this problem, use software compression or remove any lines with this
traffic type from the multilink bundle.
50 308663-15.4.2.0 Rev 00
Page 63
Protocols Supported
BayRS Version 15.4.2.0 supports the following bridging/routing protocols and
router configuration features:
• Advanced Peer-to-Peer Networking (APPN)
•AppleTalk
• Asynchronous transfer mode (ATM)
• AT M Data Exchang e 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)
and AppleTalk Update Routing Protocol (AURP)
Release Notes for BayRS Version 15.4.2.0
• Border Gateway Protoc ol (BGP-3 and BGP-4)
• Circuit Emulation Services (CES) for Passport 5430 only
• Classless interdomain routing (CIDR)
• Data compression (WCP and Hi/fn)
• Data link switching (DLSw)
• DECnet Phase IV
• Differentiated services (except on ATM)
• Distance Vector Multicast Routing Protocol (DVMRP)
• Dynamic Host Configuration Protocol (DHCP)
• Exterior Gateway Protocol-2 (EGP-2)
• File Transfer Protocol (FTP)
• Frame relay (PVC, SVC)
• HP Probe
• Hypertext Transfer Protocol (HTTP)
• Integrated Services Digital Network (ISDN)
308663-15.4.2.0 Rev 00 51
Page 64
Release Notes for BayRS Version 15.4.2.0
• Interface redundancy (proprietary)
• Internet Control Message Protocol (ICMP)
• Internet Gateway Management Prot ocol (IGMP)
• Internet Key Exchange (IKE)
• Int ernet Packet Exchange (IPX)
• Internet Protocol (IP)
• Internet Protocol Version 6 (IPv6)
• Internet Stream Protocol (ST2)
• IP Security (IPsec)
• IPsec Encapsulating Security Payload (ESP)
• IPv6 PPP Control Protocol (IPv6CP)
• Layer 2 Tunneling Protocol (L2TP)
• Learning bridge
• Logical Link Control 2 (LLC2)
• Multicast OSPF (MOSPF)
• Multiprotocol Over ATM (MPOA)
• Native Mode LAN (NML)
• Network Time Protoc ol (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 (RDISC)
52 308663-15.4.2.0 Rev 00
Page 65
Release Notes for BayRS Version 15.4.2.0
• Router redundancy (proprietary)
• Routing Information Protocol (RIP)
• Service Advertisement Protocol (SAP)
• Simple Network Management Protocol (SNMP)
• Source route bridging (SRB)
• Source route bridging over ATM permanent virtual circuits (PVCs)
• Spanning tree
• Switched Multimegabit D ata Service (SMDS)
• Synchronous Data Link Control (SDLC)
• Telnet (inbound and outbound)
• Time Division Multiplexing (TDM) for Passport 5430 only
• 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 (VIN ES)
• Virtual Router Redundancy Protocol (VRRP)
• X.25 with QLLC
• Xerox Network System (XNS)
• XMODEM and YMODEM
308663-15.4.2.0 Rev 00 53
Page 66
Release Notes for BayRS Version 15.4.2.0
Standards Supported
Table 15 lists the Requests For Comments (RFCs) and other standards docu me nts
with which Version 15.4.2.0 complies. BayRS Version 15.4.2.0 might support
additional standards that are not liste d in this table.
Table 15. Standards Supported by Version 15.4.2.0
Standard Description
ANSI
T1.107b-1991
ANSI T1.404 DS3 Metallic Interface Specification
ANSI X3t9.5 Fiber Distributed Data Interface (FDDI)
Bellcore FR-440 Transport Sys tems Generic R equirements (TSGR)
Bellcore
TR-TSY-000009
Bellcore
TR-TSY-000010
FIPS 46-2 Data Encryption Standard (DES)
FIPS 81 DES Modes of Operation (ECB, CBC)
IEEE 802.1 Logical Link Control (LLC)
IEEE 802.1Q IEEE 802.1Q VLAN tagging
IEEE 802.3 Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
IEEE 802.5 Token Ring Access Method and Physical Layer Specifications
IEEE 802.1D Spanning Tree Bridges
ITU Q.921 ISDN Layer 2 Specification
ITU Q.931 ISDN Layer 3 Specification
ITU X.25 Interface between data terminal equipment (DTE) and data circuit-terminating
RFC 768 User Datagram Protocol (UDP)
RFC 791 Internet Protocol (IP)
RFC 792 Internet Control Message Protocol (ICMP)
RFC 793 Transmission Control Protocol (TCP)
RFC 813 Window and Acknowledgment Strategy in TCP
RFC 826 Ethernet Address Resolution Protocol
Digital Hierarchy -- Supplement to formats specifications
Asynchronous Digital Multiplexes, Requirements, and Objectives
Synchronous DS3 Add-Drop Multiplex (ADM 3/X) Requirements and Objectives
equipment (DCE) for terminals operating in the packet mode and connected to
public data networks by dedicated circuits
54 308663-15.4.2.0 Rev 00
Page 67
Release Notes for BayRS Version 15.4.2.0
Table 15. Standards Supported by Version 15.4.2.0
Standard Description
RFC 827 Exterior Gateway Protocol (EGP)
RFC 854 Telnet Protocol Specification
RFC 855 Telnet Option Specification
RFC 856 Telnet Binary Transmission
RFC 857 Telnet Echo Option
RFC 858 Telnet Suppress Go Ahead Option
RFC 859 Telnet Status Option
RFC 860 Telnet Timing Mark Option
RFC 861 Telnet Extended Options: List Option
RFC 863 Discard Protocol
RFC 877 Transmission of IP Datagrams over Public Data Networks
RFC 879 TCP Maximum Segment Size and Related Topics
RFC 888 "STUB" Exterior Gateway Protocol
RFC 894 Transmission of IP Datagrams over Ethernet Networks
RFC 896 Congestion Control in IP/TCP Internetworks
RFC 903 Reverse Address Resolution Protocol
RFC 904 Exterior Gateway Protocol Formal Specification
RFC 919 Broadcasting Internet Datagrams
RFC 922 Broadcasting Internet Data grams in Subnets
RFC 925 Multi-LAN Address Resolution
RFC 950 Internet Standard Subnetting Procedure
RFC 951 Bootstrap Pr otocol
RFC 959 File Transfer Protocol
RFC 994 Protocol for Providing the Connectionless-Mode Network Service
RFC 1009 Requirements for Internet Gateways
RFC 1027 Using ARP to Implement Transparent Subnet Gateways
RFC 1042 Transmission of IP over IEEE/802 Networks
RFC 1058 Routing Information Protocol
RFC 1075 Distance Vector Multicast Routing Protocol (DVMRP)
RFC 1076 Redefin iti on of Mana ged Objec ts for IEEE 802.3 Repeater Devices (AN hubs only)
(continued)
308663-15.4.2.0 Rev 00 55
Page 68
Release Notes for BayRS Version 15.4.2.0
Table 15. Standards Supported by Version 15.4.2.0
Standard Description
RFC 1079 Telnet Terminal Speed Option
RFC 1084 BOOTP Vendor Information Extensions
RFC 1091 Telnet Terminal-Type Option
RFC 1108 Security Options for the Internet Protocol
RFC 1112 Host Extensions for IP Multicasting
Appendix I, Internet Group Management Protoco l
RFC 1116 Telnet Line-Mode Option
RFC 1139 Echo Function for ISO 8473
RFC 1155 Structure and Identification of Management Information for
TCP/IP-based Internets
RFC 1157 Simple Network Managemen t Protocol (SNMP)
RFC 1163 BGP-2 (obsoleted by RFC 12 67)
RFC 1164 Application of BGP in the Internet
RFC 1166 Internet Numbers
RFC 1188 Proposed Standard for the Transmission of IP over FDDI
RFC 1191 Path MTU Discovery
RFC 1209 Transmission of IP Datagrams over SMDS
RFC 1212 Concise MIB Definitions
RFC 1213 MIB for Network Management of TCP/IP-Based Internets
RFC 1267 Border Gateway Protocol 3 (BGP-3; obsoletes RFC 1163)
RFC 1293 Inverse ARP for Frame Relay (obsoleted by RFC 2390)
RFC 1294 Multiprotocol Interconnect over Frame Relay (obsoleted by
RFC 1490 and RFC 2427)
RFC 1304 Definition of Managed Objects for the SIP Interface Type
RFC 1305 Network T ime Protocol
RFC 1321 The MD5 Mes s age – Digest Algorithm
RFC 1323 TCP Extensions for High Performance
RFC 1331 Point-to-Point Protocol (PPP; obsoleted by RFC 1661)
RFC 1332 PPP Internet Protocol Control Protocol (IPCP)
RFC 1333 PPP Link Quality Monitoring (obsoleted by RFC 1989)
RFC 1334 PPP Authentication Protocols
(continued)
56 308663-15.4.2.0 Rev 00
Page 69
Release Notes for BayRS Version 15.4.2.0
Table 15. Standards Supported by Version 15.4.2.0
Standard Description
RFC 1350 The TFTP Protocol (Revision 2)
RFC 1356 Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode
RFC 1376 PPP DECnet Phase IV Control Protocol (DNCP)
RFC 1377 OSI over PPP
RFC 1378 PPP AppleTalk Control Protocol (ATCP)
RFC 1390 Transmission of IP and ARP over FDDI Networks
RFC 1403 BGP OSPF Interaction
RFC 1434 Data Link Switching: Switch-to-Switch Protocol
RFC 1483 Multiprotocol Encapsulation over ATM AAL5
RFC 1490 Multiprotocol Interconnect over Frame Relay (obsoletes RFC 1294, obsoleted by
RFC 2427)
RFC 1541 Dynamic Host Configuration Protocol
RFC 1552 The PPP Inter network Packet Exchange Control Protocol (IPXCP)
RFC 1577 Classical IP and ARP over ATM
RFC 1585 MOSPF: Analysis and Experience
RFC 1634 Novell IPX over Various WAN Media (IPXWAN)
RFC 1638 PPP Bridging Control Protocol (BCP)
RFC 1654 Border Gateway Protocol 4 (BGP-4; obsoleted by RFC 1771)
RFC 1661 Point-to-Point Protocol (PPP; obsoletes RFC 1331)
RFC 1662 PPP in HDLC-like Framing
RFC 1717 PPP Multilink Protocol (MP; obsoleted by RFC 1990)
RFC 1755 Signaling Support for IP over ATM
RFC 1757 Remote Netw ork Monito ring Management Inf ormation Base (RMON) f or AN, ANH ,
and ARN equipped with data collection module only
RFC 1762 PPP DECnet Phase IV Control Protocol (DNCP)
RFC 1763 PPP Banyan VINES Control Protocol (BVCP)
RFC 1764 PPP XNS IDP Control Protocol (XNSCP)
RFC 1771 Border Gateway Protocol 4 (BGP-4; obsoletes RFC 1654)
RFC 1795 Data Link Switching: Switch-to-Switch Protocol, Version 1
RFC 1819 Inter net Stream Pr otocol, Version 2
RFC 1974 PPP Stac LZS Compression Protocol
(continued)
308663-15.4.2.0 Rev 00 57
Page 70
Release Notes for BayRS Version 15.4.2.0
Table 15. Standards Supported by Version 15.4.2.0
Standard Description
RFC 1989 PPP Link Quality Monitoring (obsoletes RFC 1333)
RFC 1990 PPP Multilink Protocol (MP; obsoletes RFC 1717)
RFC 2068 HTTP Version 1.1
RFC 2069 An extension to HTTP: Digest Access Authentication
RFC 2104 HMAC: Keyed-Hashing for Message Authentication
RFC 2115 Management Information Base for Frame Relay DTEs Using SMIv2
RFC 2138 Remote Authentication Dial-In User Service (RADIUS)
RFC 2139 RADIUS Accounting
RFC 2166 Data Link Switching, Version 2.0, Enhancements
RFC 2205 Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification
RFC 2328 OSPF Version 2
RFC 2338 Virtual Router Redundancy Protocol
RFC 2385 Protection of BGP Sessions via the TCP MD5 Signature Option
RFC 2390 Inverse Address Resolution Protocol (obsoletes RFC 1293)
RFC 2403 Use of HMAC-MD5-96 within ESP and AH
RFC 2404 Use of HMAC-SHA-1-96 within ESP and AH
RFC 2405 ESP DES-CBC Cipher Algorithm with Explicit IV
RFC 2406 IP Encapsulating Security Payload (ESP)
RFC 2407 Internet IP Security Domain of Interpretation for ISAKMP
RFC 2409 Internet Key Exchange (IKE)
RFC 2410 NULL Encr yption Algorithm and Its Use with IPsec
RFC 2427 Multiprotocol Interconnect ov er Frame Relay (obsol ete s RF C 1 294 and RFC 1490)
RFC 2451 ESP CBC-Mode Cipher Algorithms
VINES 4.11 BayRS works with the Banyan VINES 4.11 standard. BayRS Version 8.10 (and
later) also supports VINES 5.50 sequenced routing.
(continued)
58 308663-15.4.2.0 Rev 00
Page 71
Flash Memory Cards Supported
You use Personal Computer Memory Card International Association (PCMCIA)
flash memory cards to store the software image and th e configuration files in
Nortel Networks routers.
Note: The Passport 2430 and 5430 platforms support 5-volt flash memory
cards only. All other BayRS router platforms support both the 5-volt and
12-volt flash memory cards. See “
page 35
for the flash memory requirements by platform.
Release Notes for BayRS Version 15.4.2.0
BayRS Flash Memory Requirements” on
Table 16
Table 16. Approved Flash Memory Cards
Size Vendor Part Number
4 MB Advanced Micro Devices (AMD) AMC004CFLKA-150
lists the flash memory cards approved for use.
AMP 797262-3
797263-2
Smart Modular (Centennial) FL04M-20-11119
FL04M-20-11138
Epson HWB401BNX2
IBM IBM1700400D1DA-25
Smart Modular (Intel) IMC004FLSA
308663-15.4.2.0 Rev 00 59
Page 72
Release Notes for BayRS Version 15.4.2.0
Table 16. Approved Flash Memory Cards
Size Vendor Part Number
8 MB Advanced Micro Devices (AMD) AMC008CFLKA-150
Smart Modular (Centennial) FL08M-25-11119
Smart Modular (Centennial)
Strata-Flash
Epson HWB801BNX0
Smart Modular (Intel) IMC008FLSP
16 MB Epson HWB161BNX2
Smart Modular (Centennial)
Strata-Flash
Smart Modular (Centennial) FL16M-20-11119
32 MB Smart Modular (Centennial) FL32M-20-11119
Smart Modular (Centennial)
Strata-Flash
AMC008CFLKA-200
AMC008CFLKA-250
AMC008DFLKA-150
AMC008DFLKA-200
AMC008DFLKA-250
FL08M-15-11119
FL08M-20-11138
FL08M-20-11119
FL08M-20-11736-J5
FL16M-20-11736-J5
FL32M-20-11736-J5
60 308663-15.4.2.0 Rev 00
Loading...