Avaya Business Policy Switch 2000 Software Version 1.1 Release Notes

Brand: Avaya

Model: Business Policy Switch 2000 Software Version 1.1

Category: Network switches

Type: Release Notes

Part No. 210676-C

March 2001

4401 Great America Parkway

Santa Clara, CA 95054

Release Notes for the

Business Policy Switch 2000

Software Version 1.1

*210676-C*

210676-C

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 Nortel Networks NA Inc.

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

with the terms of that license. The software license agreement is included in this document.

Trademarks

BaySecure, BayStack, Business Policy Switch 2000, Nortel Networks, the Nortel Networks logo, Optivity, and Passport

are trademarks of Nortel Networks.

Microsoft and Windows are trademarks of Microsoft Corporation.

Java is a trademark of Sun Micorsystems, Inc.

Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated.

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

Statement of Conditions

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

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

Nortel Networks NA 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.

Release Notes for the Business Policy Switch 2000: Software Version 1.1

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

New features and enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Compatibility with BayStack 450 Switch software version 4.0 . . . . . . . . . . . . . . . . . 7

QoS traffic policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

QoS and configuring filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuring using the Web-based management system . . . . . . . . . . . . . . . . . 9

EAPOL-based security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

EAPOL-based security example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Overview and terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

EAPOL dynamic VLAN assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Setting up the Authentication server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Authentication process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

EAPOL-based security configuration rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

RADIUS-based network security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring EAPOL using CI menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuring EAPOL using JDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring EAPOL using the Web-based management system . . . . . . . . . . 39

Support for the GBIC MDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Automatic PVID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

PVID/VLAN association example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Configuring Automatic PVID using CI menus . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring Automatic PVID using the Web-based management system . . . 49

Tabular port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Ability to ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4 Contents

210676-C

Improved STP Fast Learning Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

BootP menu item for a stack of only BPS 2000 switches . . . . . . . . . . . . . . . . . . . 54

Additional Web-based management operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Access to the Web-based management system using JDM . . . . . . . . . . . . . . 55

Additional Java security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

MAC address-based security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Resolved issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Version 1.1 issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Known limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Release Notes for the Business Policy Switch 2000: Software Version 1.1

Introduction

These release notes for the Nortel Networks Business Policy Switch 2000*

software version 1.1 provide information about software and operational issues

not included in the Business Policy Switch 2000 (BPS 2000) software version 1.0

and version 1.0.1 guides.

To obtain the software version 1.1, download the following files from the

Customer Support World Wide Web site:

• bps2k110.img (software file)

• bps2k110.bin (diagnostics file)

To obtain the Java* Device Manager (DM) software to manage the BPS 2000,

download the following file from the Customer Support World Wide Web site:

• JDM 5.1.0.0

These release notes provide information on version 1.1 and cover the following

topics:

• “Related publications,” next

• “New features and enhancements” on page 7

• “Resolved issues” on page 65

• “Known issues” on page 65

• “Known limitations” on page 66

Related publications

For more information about the BPS 2000 switch, refer to:

• Release Notes for the Business Policy Switch 2000 Software version 1.0.1

(part number 210676-B)

• Addendum to the Release Notes for the Business Policy Switch 2000

(part number 210676-A)

• Release Notes for the Business Policy Switch 2000 (part number 209320-A)

210676-C

• Using the Business Policy Switch 2000 (part number 208700-A)

• Using Web-Based Management for the Business Policy Switch 2000

(part number 209570-A)

• Reference for the Business Policy Switch 2000 Management Software

(part number 209322-A)

• Getting Started with the Business Policy Switch 2000 Management Software

(part number 209321-A)

• Business Policy Switch 2000 Installation Instructions

(part number 209319-A)

• Installing Media Dependent Adapters (MDAs) (part number 302403-F)

• Managing Policy Information in Optivity Policy Services for Business Policy

Switch (part number 306969-D)

• Installing Optivity Policy Services for Business Policy Switch

(part number 306972-C)

• Task Map - Installing the OPS for BPS Product Family

(part number 306976-C)

• Release Notes for Optivity Policy Services for the Business Policy Switch

Version 1.0 (part number 306975-C)

• Known Anomalies for Optivity Policy Services for the Business Policy Switch

Version 1.0 (part number 306974-C)

• Using the Optivity Quick2Config 2.2 Client Software (part number 207810-B)

• Installing and Administering Optivity Quick2Config 2.2

(part number 207809-B)

• Configuring Business Policy Switches with Optivity Quick2Config 2.2

(part number 311208-A)

• Release Notes for Optivity Quick2Config for Business Policy Switch 2000,

v.2.2.1 (part number 310621-A)

You can print selected technical manuals and release notes free, directly from the

Internet. Go to the www25.nortelnetworks.com/library/tpubs/ URL. Find the

product for which you need documentation. Then locate the specific category and

model or version for 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.

Release Notes for the Business Policy Switch 2000: Software Version 1.1

New features and enhancements

The following paragraphs describe the new features and enhancements offered

with the BPS 2000 software version 1.1:

• “Compatibility with BayStack 450 Switch software version 4.0,” next

• “QoS traffic policing” on page 7

• “EAPOL-based security” on page 15

• “Support for the GBIC MDA” on page 43

• “Automatic PVID” on page 43

• “Ability to ping” on page 54

• “Tabular port statistics” on page 53

• “Improved STP Fast Learning Mode” on page 54

• “BootP menu item for a stack of only BPS 2000 switches” on page 54

• “Additional Web-based management operation” on page 55

Compatibility with BayStack 450 Switch software

version 4.0

The software version 1.1 for the BPS 2000 is compatible with version 4.0 for the

BayStack 450 Switch.

When you are using these two switches combined in a stack configuration, ensure

that both are running the latest software version (BPS 2000 version 1.1 and

BayStack 450 version 4.0.). The Main Menu of the Console Interface (CI) menus

shows an Interoperability Software Version Number (ISVN). For the latest

releases, the ISVN is 2 for both the BayStack 450 and BPS 2000 switches.

QoS traffic policing

For more information on Quality of Service (QoS) and the BPS 2000 as well as

sample QoS configurations, refer to Using Web-Based Management for the

Business Policy Switch 2000 and Release Notes for the Business Policy Switch

2000.

210676-C

This section contains the following information on QoS traffic policing:

• “Introduction,” next

• “QoS and configuring filters” on page 9

• “Configuring using the Web-based management system” on page 9

Introduction

The BPS 2000 switch can interoperate with the Nortel Networks Optivity* Policy

Server using Common Open Policy Services (COPS). For information about

Optivity, go to the www.nortelnetworks.com/documentation URL. Find the

product for which you need documentation. Then locate the specific category and

model or version for your hardware or software product (in this case, Optivity

Network Management and IP Services section).

QoS traffic policing, which operates at ingress, provides different levels of service

to data streams through user configurable parameters. An example would be to

limit traffic entering a port to a specified bandwidth, such as 25 Kb/s (Committed

Rate). Instead of dropping all traffic that exceeds this threshold, traffic policing

allows you to configure a Committed Burst Rate to exceed the threshold

(Committed Rate), for a brief period of time, without being dropped.

The BPS 2000 filters collectively can take the following actions on a packet,

depending on your configuration:

• Pass or Drop

• Re-mark the packet when Pass is selected

— Re-mark a new DiffServ Codepoint (DSCP)

— Re-mark the 802.1p field

— Mark the Drop precedence

You must use either SNMP or the Web-based management system to configure

the traffic policing filters. You can also configure traffic classifiers without traffic

policing, in which case you choose No Metered Data in the Data Specification

field of the Meter page.

Because the number of filters available in hardware is limited, Nortel Networks

provides some design guidelines for constructing traffic policing.

Release Notes for the Business Policy Switch 2000: Software Version 1.1

QoS and configuring filters

You can install filters that will act on traffic destined for the switch itself, such as

ICMP Echo Requests (ping) and SNMP messages. If the associated action is to

drop the traffic, you can lock yourself out of the switch.

However, traffic destined for the switch and received through a port on the base

unit of a stack is not dropped even if filters targeting the traffic are installed and

drop has been specified. This behavior prevents you from completely isolating

yourself from the switch. Consider this behavior when you configure filters and

when you allocate ports for the purposes of configuring and or monitoring the

switch.

Also, please note when configuring IP filters, the Address Mask specifies the

portion of the address used to determine if that particular packet meets your filter

criteria.

Configuring using the Web-based management system

You can configure traffic policing using SNMP or the Web-based management

system. Refer to Using Web-Based Management for the Business Policy Switch

2000 for more information on using the following QoS Advanced pages: IP

Classification, Layer2 Classification, Actions, and Interface Group.

You will need to configure traffic policing using the following pages in the

following order:

1 From the main menu, choose one of the following:

• Application > QoS > QoS Advanced > Rules > IP Classification

210676-C

• Application > QoS > Advanced QoS > Rules > Layer2 Classification

2 Configure the filter and the filter group.

a The filter

b The filter group

3 Click Submit.

4 Choose Application > QoS > QoS Advanced > Actions page.

a Create and name an In-Profile Action.

b If you plan to work with metered data, create and name your own

Out-Profile Action.

5 Click Submit

Note: After configuring an IP filter, the screen may return the message:

Submit Failed!

Double-check that you have correctly entered the Destination Address

Mask and the Source Address Mask. The Address Mask specifies that

portion of the address used to determine if the packet meets the filter

criteria; the Address Mask is not a subnet mask.

If you specify a subnet address, ensure that the host portion of the

address contains a 0 value.

If you intend to identify an IP host address, ensure that the Address Mask

is 255.255.255.255.

Note: When configuring an In-Profile action you must take at least one

of the following actions:

- Change the DSCP value in the Update the DSCP field

- Choose from the Set Drop Precedence list

- Choose from the Update Priorities list

Release Notes for the Business Policy Switch 2000: Software Version 1.1

6 Choose Application > QoS > QoS Advanced > Meter.

The Meter page opens (Figure 1).

Figure 1 Meter page

7 In the Meter Creation area, create the traffic policing meters.

Note: You cannot edit Meters. To change the Meter, you must first

delete the current Meter and create the one you want.

210676-C

Table 1 describes the fields in the Meter Creation area, which you use to set

new meters.

8 View created meters in the Meter Table.

Table 2 describes the fields in the Meter Table.

Table 1 Meter Creation fields

Field Description

Name Enter the name for the filter you are creating.

Data Specification Choose from the list to install a filter with:

• No Meter Data

• Metered Data

NOTE: When you choose No Meter Data, do not complete

the Committed Rate, Committed Burst Size, or Out-Profile

Action fields in the box.

Committed Rate Use this field only if you specified metered data for this

filter (refer to Data Specification, above). Enter the

Committed Rate in kbits/second here. You can enter from

13 kbits/second to 1,700,000 kbits/second.

Committed Burst Size Use this field only if you specified metered data for this

filter (refer to Data Specification, above). Enter the

Committed Burst Size in bytes here. You can enter from

2,047 bytes to 131,071 bytes.

In-Profile Action Choose from the list the action you previously created

(using the Actions page).

Out-Profile Action Use this field only if you specified metered data for this

filter (refer to Data Specification, above). Choose from the

list the action you previously created (using the Actions

page).

Table 2 Meter Table fields

Field Description

Action Deletes that meter.

Name Displays the name of the filter.

Instance Displays the generated Meter Table index.

Data Specification Displays whether the filter is set up with Metered Data or

No Meter Data.

Committed Rate Displays the specified bandwidth, in kbits per second.

Release Notes for the Business Policy Switch 2000: Software Version 1.1

9 Click Submit.

10 Choose Applications > QoS > QoS Advanced > Devices > Interface

Configuration page to connect the desired ports to the desired filters.

11 Choose Applications > QoS > QoS Advanced > Policies.

The Policies page opens (Figure 2).

Committed Burst Displays the specified bytes allowed to exceed the

threshold set in the Committed Rate field for a brief period.

In-Profile Action Displays the action (configured on the Actions page) for

the switch to take on In-Profile traffic, which is traffic within

the Committed Rate.

Out-Profile Action Displays the action (configured on the Actions page) for

the switch to take on Out-of-Profile traffic, which is that

exceeds the Committed Rate as well as the Committed

Burst Size. This field is unused for filters with No Meter

Data defined.

Note: You cannot edit Policies. To change the Policy, you must first

delete the current Policy and create the one you want.

Table 2 Meter Table fields (continued)

Field Description

210676-C

Figure 2 Policies page

12 In the Policy Creation area, create the policy for each traffic policing filter.

Table 3 describes the fields in the Policy Creation Box, which you use to set

new policies.

Table 3 Policy Creation fields

Field Description

Policy Name Enter the name for the policy you are creating.

Filter Group Type Choose the filter group type from the list:

• IP Filter Group

• Layer2 Filter Group

Filter Group Choose the name of the filter group for which you are

creating the metering policy. (You named this filter

group(s) using the IP Classification/Layer2 Classification

page.)

Role Combination Choose the name of the Role Combination for which you

are creating the metering policy. (You named this Role

Combination on the Interface Group page.)

Release Notes for the Business Policy Switch 2000: Software Version 1.1

13 View the policies you previously created in the Policy Table.

14 Click Submit.

EAPOL-based security

This section contains the following information on EAPOL-based security:

• “Introduction,” next

• “EAPOL-based security example” on page 16

• “Overview and terms” on page 17

• “EAPOL dynamic VLAN assignment” on page 19

• “Setting up the Authentication server” on page 20

• “Authentication process” on page 20

• “System requirements” on page 22

• “EAPOL-based security configuration rules” on page 23

• “RADIUS-based network security” on page 23

• “Configuring EAPOL using CI menus” on page 24

• “Configuring EAPOL using JDM” on page 28

• “Configuring EAPOL using the Web-based management system” on page 39

Introduction

The Extensible Authentication Protocol over LAN (EAPOL)-based security

feature uses the EAP, as described in the IEEE Draft P802.1X, to allow you to set

up network access control on internal LANs.

Order Specify the order of precedence among the filter groups.

Meter Choose the name of the filter group for which you are

creating the metering policy (You named this filter group

on the Meter page.)

Table 3 Policy Creation fields (continued)

Field Description

210676-C

EAP allows the exchange of authentication information between any end station

or server connected to the switch and an authentication server (such as a RADIUS

server). The EAPOL-based security feature operates in conjunction with a

RADIUS-based server to extend the benefits of remote authentication to internal

LAN clients.

EAPOL-based security example

The following example illustrates how the BPS 2000, configured with the

EAPOL-based security feature, reacts to a new network connection:

• The switch detects a new connection on one of its ports (Figure 4).

— The switch requests a user ID from the new client (1).

— EAPOL encapsulates the user ID and forwards it to the RADIUS server

(2).

— The RADIUS server responds with a request for the user’s

password (3).

• The new client forwards an encrypted password to the switch, within the

EAPOL packet (Figure 4).

— The switch relays the EAPOL packet to the RADIUS server (4).

— If the RADIUS server validates the password (5), the new client is

allowed access to the switch and the network (6).

Release Notes for the Business Policy Switch 2000: Software Version 1.1

Figure 3 EAPOL-based security (1 of 2)

Figure 4 EAPOL-based security (2 of 2)

Overview and terms

This section provides a detailed description of EAPOL-based security, including

an overview of the components and terms used with this feature.

EAPOL_step1

RADIUS server

New client PC

Switch requests

user ID

Switch forwards

user ID to

RADIUS Server

Password?

Password request

RADIUS server

New client PC

EAPOL_step2

Encrypted password

Switch forwards

password

********

RADIUS server

New client PC

RADIUS server

Password

validated

Access to

network

approved

Client

accesses

network

New client PC

********

210676-C

Some components of EAPOL-based security are:

• Supplicant—the device applying for access to the network.

• Authenticator—software with the sole purpose of authorizing a supplicant

that is attached to the other end of a LAN segment.

• Authentication Server—a RADIUS server that provides authorization

services to the Authenticator.

• Port Access Entity (PAE)—a software entity associated with each port that

supports the Authenticator or Supplicant functionality. In the preceding

example, the Authenticator PAE resides on the switch.

• Controlled Port—any switch port with EAPOL-based security enabled.

The Authenticator communicates with the Supplicant using an encapsulation

mechanism known as EAP over LANs (EAPOL).

The Authenticator PAE encapsulates the EAP message into a RADIUS packet

before sending the packet to the Authentication Server. The Authenticator

facilitates the authentication exchanges that occur between the Supplicant and the

Authentication Server by encapsulating the EAP message to make it suitable for

the packet’s destination.

The Authenticator determines the controlled port’s operational state. After the

RADIUS server notifies the Authenticator PAE about the success or failure of the

authentication, it changes the controlled port’s operational state accordingly.

The Authenticator PAE functionality is implemented for each controlled port on

the switch. At system initialization, or when a supplicant is initially connected to

the switch’s controlled port, the controlled port’s state is set to Blocking. During

that time, EAP packets are processed by the authenticator.

When the Authentication server returns a “success” or “failure” message, the

controlled port’s state is changed accordingly. If the authorization is successful,

the controlled port’s operational state is set to Forwarding. Otherwise, the

controlled port’s state depends on the Operational Traffic Control field value in

the EAPOL Security Configuration screen.

Release Notes for the Business Policy Switch 2000: Software Version 1.1

The Operational Traffic Control field can have one of the following two values:

• Incoming and Outgoing—If the controlled port is unauthorized, frames are

not transmitted through the port; all frames received on the controlled port are

discarded. The controlled port’s state is set to Blocking.

• Incoming—If the controlled port is unauthorized, frames received on the port

are discarded, but the transmit frames are forwarded through the port.

EAPOL dynamic VLAN assignment

If EAPOL-based security is enabled on a port, and then the port is authorized, the

EAPOL feature dynamically changes the port’s VLAN configuration according to

preconfigured values, and assigns a new VLAN. The new VLAN configuration

values are applied according to previously stored parameters (based on the

user_id) in the Authentication server.

The following VLAN configuration values are affected:

• Port Membership

• PVID

• Port Priority

When the EAPOL-based security is disabled on a port that was previously

authorized, the port’s VLAN configuration values are restored directly from the

switch’s non-volatile random access memory (NVRAM).

The following exceptions apply to dynamic VLAN assignments:

• The dynamic VLAN configuration values assigned by EAPOL are not stored

in the switch’s NVRAM.

• You can override the dynamic VLAN configuration values assigned by

EAPOL; however, aware that the values you configure are not stored in

NVRAM.

• When EAPOL is enabled on a port, and you configure values other than

VLAN configuration values, those values are applied and stored in NVRAM.

210676-C

Setting up the Authentication server

This section describes how to set up your Authentication server (RADIUS server)

for EAPOL dynamic VLAN assignments. The Authentication server allows you

to configure user-specific settings for VLAN memberships and port priority.

When you log on to a system that has been configured for EAPOL authentication,

the Authentication server recognizes your user ID and notifies the switch to assign

preconfigured (user-specific) VLAN membership and port priorities to the switch.

The configuration settings are based on configuration parameters that were

customized for your user ID and previously stored on the Authentication server.

To set up the Authentication server, set the following “Return List” attributes for

all user configurations (refer to your Authentication server documentation):

• VLAN membership attributes

— Tunnel-Type: value 13, Tunnel-Type-VLAN

— Tunnel-Medium-Type: value 6, Tunnel-Medium-Type-802

— Tunnel-Private-Group-Id: ASCII value 1 to 4094 (this value is used to

identify the specified VLAN)

• Port priority (vendor-specific) attributes

— Vendor Id: value 562, Nortel Networks vendor Id

— Attribute Number: value 1, Port Priority

— Attribute Value: value 0 (zero) to 7 (this value is used to indicate the port

priority value assigned to the specified user)

Authentication process

The flowcharts shown in Figure 5 and Figure 6 describe the authentication

process.

Page is loading ...

Avaya Business Policy Switch 2000 Software Version 1.1 Release Notes

Brand: Avaya

Model: Business Policy Switch 2000 Software Version 1.1

Category: Network switches

Type: Release Notes

Download PDF

report

Avaya Business Policy Switch 2000 Software Version 1.1 Release Notes

Avaya Business Policy Switch 2000 Software Version 1.1 Release Notes

Related papers

Other documents