Avaya BayRS Version 13.20 Release Notes

Brand: Avaya

Model: BayRS Version 13.20

Category: Gateways/controllers

Type: Release Notes

Release Notes for BayRS

Version 13.20

Part No. 301151-D Rev 00

May 1999

BayRS Version 13.20

Site Manager Software Version 7.20

BCC Version 4.20

301151-D Rev 00

Bay Networks, Inc.

4401 Great America Parkway

Santa Clara, CA 95054

The information in this document is subject to change without notice. The statements, configurations, technical data,

and recommendations in this document are believed to be accurate and reliable, but are presented without express or

implied warranty. Users must take full responsibility for their applications of any products specified in this document.

The information in this document is proprietary to Bay Networks, Inc.

The software described in this document is furnished under a license agreement and may only be used in accordance

with the terms of that license. A summary of the Software License is included in this document.

Trademarks

ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FRE, LN, Optivity, PPX, Quick2Config, and Bay Networks are

registered trademarks and Advanced Remote Node, ANH, ARN, ASN, BayRS, BaySecure, BayStack, BayStream,

BCC, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN, FN, IPAutoLearn, PathMan, RouterMan, SN, SPEX,

Switch Node, and System 5000 are trademarks of Bay Networks, Inc.

Microsoft, MS, MS-DOS, Win32, Windows, and Windows NT are registered trademarks of Microsoft Corporation.

All other trademarks and registered trademarks are the property of their respective owners.

Restricted Rights Legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph

(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer

software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in

the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

Statement of Conditions

In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the

right to make changes to the products described in this document without notice.

Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or

circuit layout(s) described herein.

rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the

above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising

materials, and other materials related to such distribution and use acknowledge that such portions of the software were

developed by the University of California, Berkeley. The name of the University may not be used to endorse or

promote products derived from such portions of the software without specific prior written permission.

SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR

IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

In addition, the program and information contained herein are licensed only pursuant to a license agreement that

contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed

by third parties).

301151-D Rev 00

iii

Bay Networks, Inc. Software License Agreement

NOTICE: Please carefully read this license agreement before copying or using the accompanying software or

installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement).

BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF

THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS

UNDER WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these

terms and conditions, return the product, unused and in the original shipping container, within 30 days of purchase to

obtain a credit for the full purchase price.

1. License Grant. Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal,

nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single

authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup

purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in

support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend

to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other

Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software

License Agreement that accompanies such software and upon payment by the end user of the applicable license fees

for such software.

2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws.

Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any

revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any

copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use

for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user manuals

or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or transfer

the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and its

licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise

disclose to any third party the Software, or any information about the operation, design, performance, or

implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however,

Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s facility,

provided they have agreed to use the Software only in accordance with the terms of this license.

3. Limited warranty. Bay Networks warrants each item of Software, as delivered by Bay Networks and properly

installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function

substantially as described in its accompanying user manual during its warranty period, which begins on the date

Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole

remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be

included in a future Software release. Bay Networks further warrants to Licensee that the media on which the

Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days

from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is

returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not

apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility

for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained

from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the

Licensee’s requirements, b) that the Software will operate in the hardware or software combinations that the Licensee

may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the

operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot

be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered,

except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product,

resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE

FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL

OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of

301151-D Rev 00

its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or

altered files, data, or programs.

4. Limitation of liability. IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY

COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL

DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR

PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN

IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT

SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT

EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.

5. Government Licensees. This provision applies to all Software and documentation acquired directly or indirectly by

or on behalf of the United States Government. The Software and documentation are commercial products, licensed on

the open market at market prices, and were developed entirely at private expense and without the use of any U.S.

Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or

disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial

Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this license for civilian

agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS

252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.

6. Use of Software in the European Community. This provision applies to all Software acquired for use within the

European Community. If Licensee uses the Software within a country in the European Community, the Software

Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the

examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such

intended examination of the Software and may procure support and assistance from Bay Networks.

7. Term and termination. This license is effective until terminated; however, all of the restrictions with respect to

Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the

Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information

shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if

Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason,

Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay

Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.

8. Export and Re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data

or information without first obtaining any required export licenses or other governmental approvals. Without limiting

the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first

obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert

any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports

are restricted or embargoed under United States export control laws and regulations, or to any national or resident of

such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any

military end user or for any military end use, including the design, development, or production of any chemical,

nuclear, or biological weapons.

9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent

jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement

will be governed by the laws of the state of California.

Should you have any questions concerning this Agreement, contact Bay Networks, Inc., 4401 Great America Parkway,

P.O. Box 58185, Santa Clara, California 95054-8185.

LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND

AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS

AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND

LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND

COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS

AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY

NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN

EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.

301151-D Rev 00

Contents

Preface

Bay Networks Technical Publications ............................................................................... xi

How to Get Help ...............................................................................................................xii

Release Notes for

BayRS Version 13.20

Upgrading to Version 13.20 ...............................................................................................2

Upgrading FireWall-1 Configurations ..........................................................................2

Preventing Spoofing with FireWall-1 .....................................................................5

Upgrading ATM Configurations ...................................................................................6

Upgrading L2TP Configurations ..................................................................................6

Upgrading OSPF Configurations .................................................................................7

Upgrading the BCC Help File ......................................................................................7

Upgrading Static Forwarding Policy Filters ..................................................................7

New Features ....................................................................................................................8

BCC Support for Additional Protocols and Services ...................................................8

BCC Enhancements ....................................................................................................8

BCC Multilevel Access ................................................................................................9

FireWall-1 Enhancements ...........................................................................................9

SNMP View-Based Access Control ............................................................................9

OSPF NSSAs ............................................................................................................10

Backup Gateways and Load Balancing for Bay Dial VPN Services ..........................10

IP Security (IPsec) ....................................................................................................10

Priority Queuing Over ATM and HSSI Lines .............................................................11

Differentiated Services ..............................................................................................11

PIM Sparse Mode .....................................................................................................11

HTTP Server Enhancements ....................................................................................12

Getting Help ........................................................................................................12

Troubleshooting Features ...................................................................................12

301151-D Rev 00

Administration Features ......................................................................................12

ATM WAN SVCs ........................................................................................................13

Multicast Migration Tools ...........................................................................................13

DVMRP Policies ........................................................................................................13

ATM UNI 4.0 Support ................................................................................................13

BGP-4 TCP MD5 Message Authentication ...............................................................14

BGP-4 Confederations ..............................................................................................14

RADIUS Enhancements ............................................................................................15

DLSw RSVP Support ................................................................................................15

OSA-2 ATM Adapter Support for SNA Connectivity ..................................................15

L2TP Framed Route Support and Other Enhancements ..........................................15

BN Console Slot Election ..........................................................................................16

VRRP Enhancements ...............................................................................................16

FRE-4-PPC Processor for BN ...................................................................................16

Documentation Reorganization for ATM and IP ........................................................16

BCC Guidelines ...............................................................................................................18

Deleting Interfaces with the BCC ..............................................................................18

Sending BCC Feedback ............................................................................................18

Platforms Supported .................................................................................................18

Interfaces Supported .................................................................................................18

Protocols Supported .................................................................................................19

Identifying Board Types .............................................................................................21

General Guidelines ..........................................................................................................30

Cisco Compatibility Issues Using PIM .......................................................................30

Fragment Tagging in Bootstrap Messages .........................................................30

Cisco Drops RP Advertisement Messages with Zero Prefix Count ....................30

Routers Ignore RP Priority and Hash Value During RP Selection ......................31

IPsec 3DES Performance Considerations ................................................................31

Renaming the FireWall-1 Redundant Management Scripts ......................................32

NAT Synchronous Not Operational ...........................................................................33

BayRS Bandwidth Broker for Differentiated Services ...............................................33

Event Database .........................................................................................................33

Quick2Config .............................................................................................................34

SunOS 4.1.4 Support for Site Manager ....................................................................34

Year 2000 Compliance ..............................................................................................34

301151-D Rev 00

vii

Frame Relay Multilink Not Supported ........................................................................34

8 MB Flash Not Supported for BN Platform ..............................................................34

Protocol Statistics for MPLS ......................................................................................35

AN/ANH and ARN Guidelines ...................................................................................35

Allocating Memory on ARN Routers ...................................................................35

DSU/CSU Test LED Remains On After Reset ....................................................35

Network Booting on DSU/CSU Interfaces ..........................................................36

ARN Router Not a Supported DVS RADIUS Client ..................................................36

BayRS Version 13.20 Flash Memory Requirements .................................................36

Configuring PU 4 and SDLC Link Stations ...............................................................36

Creating Multiple GRE Tunnels .................................................................................37

IPsec Executable .......................................................................................................37

Adding the IPsec File to the BayRS 13.20 Base Kernel .....................................37

NAT Guidelines .........................................................................................................37

Configuring NAT Dynamically .............................................................................37

Deleting NAT from a Router ................................................................................37

Entering a Global Range ....................................................................................38

Outbound LAN Traffic Filters .....................................................................................38

Protocol Prioritization No Call Filters and TCP Applications .....................................38

Support for Strata-Flash Card ...................................................................................39

WEP Executable .......................................................................................................39

X.25 PVCs .................................................................................................................39

IPv6 Supported on ATM PVCs ..................................................................................39

Configuring RADIUS Servers ....................................................................................40

Operating Limitations .......................................................................................................41

Restriction When Deleting ATM from a Router if Signaling Is Enabled .....................41

Restriction if Signal Ports Settings on a Switch and Router Conflict .........................41

Restriction When Creating FTP from the BCC .........................................................41

Restriction When Deleting a Hybrid Mode Permanent Virtual

Circuit (PVC) .............................................................................................................41

Restriction When Using DLSw/APPN Boundary Port with AS400s and

Other Adjacent Link Stations .....................................................................................41

Restriction When Virtual Channel Connections (VCCs) Become Inactive ................42

Restriction When Performing Flash Compaction or Extensive File

Management on ARE Module ...................................................................................42

viii

301151-D Rev 00

Restriction When Accessing the Embedded Web Server Using

Microsoft Internet Explorer ........................................................................................42

Restriction for SNMP View-Based Access Control ...................................................43

Protocols Supported ........................................................................................................43

Standards Supported ......................................................................................................47

Flash Memory Cards Supported .....................................................................................51

301151-D Rev 00

Tables

Table 1. BCC Board Types: AN and ANH Modules ................................................22

Table 2. BCC Board Types: BLN and BCN Modules ..............................................25

Table 3. BCC Board Types: ASN Modules .............................................................27

Table 4. BCC Board Types: ARN Modules .............................................................28

Table 5. BCC Board Types: System 5000 Modules ................................................29

Table 6. Standards Supported by Version 13.20 ....................................................47

Table 7. Approved Flash Memory Cards ................................................................52

301151-D Rev 00

Preface

BayRS Version 13.20 is a software release that includes new features added since

BayRS Version 13.10. These release notes contain guidelines for using BayRS

Version 13.20.

Bay Networks Technical Publications

You can now print Bay Networks technical manuals and release notes free,

directly from the Internet. Go to support.baynetworks.com/library/tpubs/. Find the

Bay Networks product for which you need documentation. Then locate the

specific category and model or version for your hardware or software product.

Using Adobe Acrobat Reader, you can open the manuals and release notes, search

for the sections you need, and print them on most standard printers. You can

download Acrobat Reader free from the Adobe Systems Web site,

www.adobe.com.

You can purchase Bay Networks documentation sets, CDs, and selected technical

publications through the Bay Networks Collateral Catalog. The catalog is located

on the World Wide Web at support.baynetworks.com/catalog.html and is divided

into sections arranged alphabetically:

• The “CD ROMs” section lists available CDs.

• The “Guides/Books” section lists books on technical topics.

• The “Technical Manuals” section lists available printed documentation sets.

Make a note of the part numbers and prices of the items that you want to order.

Use the “Marketing Collateral Catalog description” link to place an order and to

print the order form.

Release Notes for BayRS Version 13.20

xii

301151-D Rev 00

How to Get Help

If you purchased a service contract for your Bay Networks product from a

distributor or authorized reseller, contact the technical support staff for that

distributor or reseller for assistance.

If you purchased a Bay Networks service program, contact one of the following

Bay Networks Technical Solutions Centers:

Technical Solutions Center Telephone Number

Billerica, MA 800-2LANWAN (800-252-6926)

Santa Clara, CA 800-2LANWAN (800-252-6926)

Valbonne, France 33-4-92-96-69-68

Sydney, Australia 61-2-9927-8800

Tokyo, Japan 81-3-5402-7041

301151-D Rev 00

Release Notes for

BayRS Version 13.20

This document contains the latest information about Bay Networks

BayRS

™

Version 13.20, including information on the following topics:

Topic Page

Upgrading to Version 13.20 -2

New Features -8

BCC Guidelines -18

General Guidelines -30

Operating Limitations -41

Protocols Supported -43

Standards Supported -47

Flash Memory Cards Supported -51

Release Notes for BayRS Version 13.20

301151-D Rev 00

Upgrading to Version 13.20

To upgrade BayRS to Version 13.20, or to upgrade Site Manager software to

Version 7.20, see Upgrading Routers to BayRS Version 13.xx, in your upgrade

package. Also, read the following sections for additional upgrading information.

Upgrading FireWall-1 Configurations

To upgrade FireWall-1 in BayRS Version 13.20, complete the following steps:

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, refer to

Using the Bay Command Console (BCC).

Make sure that you will not lose access to your router.

When you upgrade to BayRS Version 13.20, once you boot your router, the

Version 13.20 software invokes the default FireWall-1 security policy. This

default security policy drops all attempts at communication with the router.

If you manage a router at a remote location, you will no longer be able to gain

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.

Reboot the router with BayRS Version 13.20, using an existing

configuration file.

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>

mask

<address_mask>

ip_address

is the IP address you have assigned to the interface.

address_mask

is the mask associated with the IP address.

The prompt for the IP interface appears.

Release Notes for BayRS Version 13.20

301151-D Rev 00

For example, the following command invokes the prompt for IP interface

2.2.2.2/255.0.0.0 (which has been configured 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#

Once you are at the prompt 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#

To use FireWall-1 on more than 32 circuits, set the policy index number

for each IP interface.

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 circuits 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 need to use policy

indexes.

If you are using FireWall-1 on more than 32 circuits, group circuits that share

the same security policy. Then, set the policy index on each circuit in a group

to the same value. For example, suppose you want to use FireWall-1 on 40

circuits. The first five circuits share one security policy; the next 35 share a

different security policy. Using the BCC, assign policy index 1 to the first five

circuits and policy index 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 router, all IP forwarding is disabled on circuits after 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 if you have any circuits on which all IP forwarding is disabled.

Release Notes for BayRS Version 13.20

301151-D Rev 00

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 need

to set the policy index value, use the BCC to navigate to the firewall prompt,

as described in step 4. Then enter:

policy-index

<value>

value

is the index value, from 1 to 1023.

For example, the following command sets the policy index to 1:

firewall/2.2.2.2# policy-index 1

firewall/2.2.2.2#

Save the configuration file and reboot the router.

Reinstall the security policy.

Since you previously defined a security policy (using the earlier version of

BaySecure FireWall-1), you do not need to define it again. However, you must

reinstall it in on the router. For complete 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 FireWall-1 command line interface to enter the following

command:

fw load ../conf/

<config_file>

pol

<policy_index_number>

<router_name>

For example, the following command specifies that the security policy in the

configuration file drop_ftp be installed on policy index number 1 on the router

named asn1:

fw load ../conf/drop_ftp pol1@asn1

Release Notes for BayRS Version 13.20

301151-D Rev 00

Preventing Spoofing with FireWall-1

You can configure FireWall-1 to eliminate the possibility of spoofing, that is,

someone violating the firewall by sending a packet with a source address from

within the network. To configure FireWall-1 to eliminate spoofing, complete the

following steps:

Make sure that each firewalled interface has a unique policy index

number. For best results, make sure that each circuit has a unique policy

index number.

For example, suppose your router has three Ethernet interfaces to LANs

protected by the firewall and one frame relay synchronous firewalled

connection that includes multiple PVCs. Each Ethernet interface must have a

unique policy index number. You may assign the same policy index number to

each of the frame relay PVCs if necessary, although configuring the interfaces

in this way allows each frame relay interface to spoof the other frame relay

interfaces.

Enter the BCC show command,

show firewall interfaces

, to note the

policy index number for each router circuit.

In the Check Point user interface, click on Manage Network Objects.

Highlight the defined router object (you may need to create a router) and

click Edit.

Click on the Interfaces tab.

Click on SNMP Get. (Ignore the outdated pop-up message.)

Highlight a circuit and click on Edit.

In the Name field, type

pol

In the Num field, type the policy index number of the circuit (which you

noted from the BCC show command in step 2).

10.

Repeat steps 7 through 9 for each firewalled circuit.

For more information about preventing spoofing, refer to your Check Point

documentation.

Release Notes for BayRS Version 13.20

301151-D Rev 00

Upgrading ATM Configurations

If you are upgrading from a BayRS version earlier than 12.20 and you defined log

event traps for 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, but has been combined with the ATM entity (entity #78).

Combining and reorganizing these entities resulted in changes to the ATM log

event message numbers. New log events were added to the ATM_LE entity (entity

#100), resulting in log event message number changes for LAN emulation as well.

You can view the new and modified ATM log event messages in the event

database on the World Wide Web, or on the BayRS Online Library Version 13.20

CD.

Upgrading L2TP Configurations

If you have a BayRS Version 12.10 configuration file that includes L2TP

operating on a router using BayRS Version 13.20, the router automatically

upgrades the assigned user network addresses to L2TP IP interface addresses.

L2TP IP interface addresses are internal to the router. When communicating with

the remote user, the router associates the user’s IP address with an L2TP IP

interface address that you configure.

The user network addresses assigned to Version 12.10 apply to the entire router. In

Version 13.20, each slot has a unique L2TP IP address. Consequently, if the

number of configured L2TP slots is greater than the number of configured

assigned user network addresses, the router will not be able to upgrade every slot

from a Version 12.10 configuration to a Version 13.20 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, 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.

Release Notes for BayRS Version 13.20

301151-D Rev 00

Upgrading OSPF Configurations

When you upgrade BayRS from releases earlier than Version 12.20, there must

not be an 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, PPP, Point-to-Multipoint, or NBMA) should have the same

OSPF MTU size. You configure the OSPF MTU size through the MTU Size

parameter in the OSPF Interfaces window in Site Manager.

BayRS Versions 12.20 and later comply with RFC 2178, which requires the OSPF

MTU size feature.

Upgrading the BCC Help File

The following information updates instructions relating to the BCC Help file

mentioned in Upgrading Routers to BayRS Version 13.xx.

If you received a flash card with the BayRS 13.20 (BCC 4.20) image, it should

also contain the BCC Help file, bcc.help. The BCC looks for this file name as

soon as you enter the first

help

command after booting the router using

the new Version 13.20 image.

If the bcc.help file is not already on the default volume in the router, you must

transfer it from the BayRS Version 13.20 software CD to that volume. The BCC

Help file on the BayRS software CD has the name bcc_help. In the process of

transferring that file to the router, be sure to rename it as bcc.help. (The Version

13.20 router software is not configured by default to recognize the file name

bcc_help.)

Upgrading Static Forwarding Policy Filters

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.

To use these IGMP static forwarding policy filters, you must re-create them. For

information about creating IGMP static forwarding policy filters, see Configuring

IP Multicasting and Multimedia Services.

Release Notes for BayRS Version 13.20

301151-D Rev 00

New Features

The following sections provide brief descriptions of the new features in BayRS

Version 13.20.

BCC Support for Additional Protocols and Services

With Version 13.20, you can now configure these additional protocols and

services using the BCC:

• DLSw (data link switching) over token ring, FDDI, and Ethernet

• GRE (Generic Routing Encapsulation)

• MPOA/NHRP (Multiprotocol Over ATM/Next Hop Resolution Protocol)

• Dial services compression

• Transparent bridging

• Spanning tree

• Source route bridging

• NAT (Network Address Translation)

• FireWall-1

• SDLC (Synchronous Data Link Control)

• LLC2 (Logical link control) over token ring, FDDI, and Ethernet

• VRRP (Virtual Router Redundancy Protocol)

• RADIUS

• DVMRP accept, announce, and unicast accept policies

BCC Enhancements

The BCC now checks user input for configurable parameter values, ensuring that

new values are within allowable ranges.

Page is loading ...

Avaya BayRS Version 13.20 Release Notes

Brand: Avaya

Model: BayRS Version 13.20

Category: Gateways/controllers

Type: Release Notes

Download PDF

report

Avaya BayRS Version 13.20 Release Notes

Avaya BayRS Version 13.20 Release Notes

Related papers

Other documents