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
BayStack, Business Policy Switch 2000, Nortel Networks, the Nortel Networks logo, and Optivity Policy Services
are trademarks of Nortel Networks.
Adobe and Acrobat 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.
210676-P
Introduction
3
These release notes for the Nortel Networks* Business Policy Switch 2000
*
software version 2.0.5 provide information about software and operational issues
not included in the Business Policy Switch 2000 (BPS 2000) software version 2.0
guides.
To obtain the software version 2.0.5, download the following files from the
Customer Support World Wide Web site:
•bps2k205_16.img (software file)
•bps2kdiag_2053.bin (diagnostics file)
You must download the diagnostics file as well as the software file.
Note: When you are downloading with a mixed (or Hybrid) stack,
ensure that a BPS 2000 switch is Unit 1 and is the base unit. Ensure that
you do not interrupt the download process; do not detach either the
power cord or any of the network connections during download.
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:
•DM 5.5.3—You must upgrade the JRE software, which is on the web site, to
version 1.3.0 at this time also.
Note: Ensure that you have upgraded to the BPS 2000 software v2.0 or
later version when you use the BPS 2000-1GT, BPS 2000-2GT, or BPS
2000-2GE MDA. You must upgrade to the BPS 2000 software v2.0 or
later version whether you are using a standalone BPS 2000, a stack of
pure BPS 2000, or a mixed stack.
Release Notes for the Business Policy Switch 2000 Software Version 2.0.5
4 Stack Operational Mode after reset
Note: When you create a policy that references shaping parameters, the
802.1p and Drop Precedence values must be changed either by using the
system defaults or explicitly by the action.
These release notes provide information on version 2.0.5 and cover the following
topics:
•“Stack Operational Mode after reset,” next
•“Upgrading software” on page 5
•“Compatibility with BayStack 450 switches” on page 8
•“Documentation correction” on page 9
•“New features and enhancements” on page 10
•“Unknown multicast frame handling enhancement” on page 12
•“New Device Manager features” on page 12
•“Enhanced Web-based management features” on page 18
•“Enhancements to the console interface” on page 19
•“New and enhanced NNCLI commands for version 2.0.5” on page 20
•“Resolved issues” on page 33
•“Known issues” on page 36
•“Known limitations” on page 39
•“Related publications” on page 41
•“How to get help” on page 42
Stack Operational Mode after reset
When you reset the BPS 2000 switch to factory default settings, the Stack
Operational Mode will not be reset. You must be especially aware of this when
moving the switch between different stacks. For example, if you are working with
a stack in Hybrid mode and you move that switch to a Pure BPS 2000 stack or a
standalone configuration, you will have to manually set the Stack Operational
Mode, even if you reset the switch to factory defaults.
210676-P
The original documentation erroneously states that the Stack Operational Mode
resets to a default value when you reset the switch to factory defaults.
Upgrading software
Note: Use the Command Line Interface (CLI), console interface (CI)
menus, or the Web-based management system to upgrade to software
version 2.0.5. For detailed instructions, refer to Using the Business
Policy Switch 2000 Version 2.0, Reference for the Business Policy Switch
2000 Command Line Interface Software Version 2.0, and Using
Web-based Management for the Business Policy Switch 2000 Software
Version 2.0.
You use one of the management systems to upgrade or downgrade software. You
follow a different procedure depending on whether you are using a Pure BPS 2000
stack or a Hybrid stack.
Upgrading software 5
The stacking software compatibility requirements are as follows:
•Pure BPS 2000 stack—All units must be running the same software version.
•Pure BayStack 450 stack—All units must be running the same software
version.
•Hybrid stack:
— All BPS 2000 units must be running the same software version.
— All BayStack 410 units must be running the same software version.
— All BayStack 450 units must be running the same software version.
— All software versions must have the identical ISVN.
This section discusses the following topics:
•“Upgrading software in a Pure BPS 2000 stack,” next
•“Upgrading software in a Hybrid stack” on page 6
Release Notes for the Business Policy Switch 2000 Software Version 2.0.5
6 Upgrading software
Upgrading software in a Pure BPS 2000 stack
To download, or upgrade, software in a Pure BPS 2000 stack:
1Download the operational software, or agent, image.
2Download the diagnostics image.
However, if you are currently using software version 1.0, 1.0.1, or 1.1, you must
upgrade to software version 1.1.1 before upgrading to version 2.0.5.
Upgrading software in a Hybrid stack
The physical order of the units and the unit numbering in the Hybrid stack does
not affect the upgrading process at all. In addition, the cabling order regarding
upstream/downstream neighbors does not affect the process.
Note: Once you begin the upgrading process, do not interrupt the
process at all. Interrupting the downloading (or upgrading) process may
cause loss of connectivity.
210676-P
Before you attempt to download new software (or upgrade software) to a Hybrid
(mixed) stack, you must ensure that the Interoperability Software Version
Numbers (ISVN) are identical. That is, the ISVN number for the BayStack 450
switch and BayStack 410 switch must have the same ISVN as the BPS 2000. If
the ISVNs are not the same, the stack does not operate. The ISVNs and the
accompanying software release are:
•ISVN 1
— BayStack 410 or Bay Stack 450—version 3.1
— BPS 2000—versions 1.0 and 1.0.1
•ISVN 2
— BayStack 410 or BayStack 450—versions 4.0, 4.1 and 4.2.
— BPS 2000—versions 1.1, 1.1.1, 1.2, 2.0, and 2.0.5
Upgrading software 7
This section describe the steps for the following software upgrades:
•“Upgrading software when ISVN is 2,” next
•“Upgrading software when ISVN is 1” on page 7
Upgrading software when ISVN is 2
To upgrade a Hybrid stack to BPS 2000 software version 2.0.5 when the ISVN
numbers of the units are 2:
1Download the BPS 2000 image file.
The system resets.
2Download the BPS 2000 diags file.
The system resets.
Note: Once you begin the upgrading process, do not interrupt the
process at all. Interrupting the downloading (or upgrading) process may
cause loss of connectivity.
Upgrading software when ISVN is 1
To upgrade a Hybrid stack to BPS 2000 software version 2.0.5 when the ISVN
numbers of the units are 1:
1Download the BPS 2000 image file and the BayStack 450/410 file
simultaneously.
Note: If you do not download both the BPS 2000 and BayStack 410/450
images simultaneously, the stack may not form.
The system resets.
2Download the other BayStack 450 image file.
The system resets.
3Download the BPS 2000 diags file.
The system resets.
Release Notes for the Business Policy Switch 2000 Software Version 2.0.5
8 Compatibility with BayStack 450 switches
4Validate that the ISVN on both the BPS 2000 and the BayStack are 2.
Note: Once you begin the upgrading process, do not interrupt the
process at all. Interrupting the downloading (or upgrading) process may
cause loss of connectivity.
Compatibility with BayStack 450 switches
The BPS 2000 software version 2.0.5 is compatible with BayStack* 450 software
versions 4.0, 4.1 and 4.2.
You can stack the BPS 2000 up to 8 units high. There are two types of stacks:
•Pure BPS 2000 —This stack has only BPS 2000 switches. It is sometimes
referred to as a pure stack. The stack operational mode for this type of stack is
Pure BPS 2000 Mode.
•Hybrid—This stack has a combination of BPS 2000 switches and BayStack
450 and/or BayStack 410 switches. It is sometimes referred to as a mixed
stack. The stack operational mode for this type of stack is Hybrid Stack.
210676-P
All BPS 2000 switches in the stack must be running the identical version of
software, and all the BayStack switches must be running the identical version of
software.
When you are working with a mixed stack, you must ensure that the
Interoperability Software Version Numbers (ISVN) are identical. That is, the
ISVN number for the BayStack 450 switch and BayStack 410 switch must have
the same ISVN as the BPS 2000. If the ISVNs are not the same, the stack does not
operate. The ISVNs and the accompanying software release are:
•ISVN 1
— BayStack 410 or Bay Stack 450—version 3.1
— BPS 2000—versions 1.0 and 1.0.1
•ISVN 2
— BayStack 10 or BayStack 450—versions 4.0, 4.1 and 4.2
— BPS 2000—versions 1.1, 1.1.1, 1.2, 2.0, and 2.0.5
Documentation correction 9
In sum, the stacking software compatibility requirements are as follows:
•Pure BPS 2000 stack—All units must be running the same software version.
•Pure BayStack 450 stack—All units must be running the same software
version.
•Hybrid stack:
— All BPS 2000 units must be running the same software version.
— All BayStack 410 units must be running the same software version.
— All BayStack 450 units must be running the same software version.
— All software versions must have the identical ISVN.
To find out which version of the BPS 2000 software is running, use the Console
Interface (CI) menus or the Web-based management system:
•CI menus—From the main menu of the Console, choose Systems
Characteristics menu. The software currently running is displayed in
sysDescr.
•Web-based management system—Open the System Information page, which
is under Administration on the main menu. The software currently running is
displayed in the sysDescription field.
Refer to Appendix B of the Using the Business Policy Switch 2000 Software Version 2.0 for complete information on interoperability and compatibility
between the BPS 2000 and BayStack switches.
Although the BPS 2000 software version 2.0.5 is compatible with BayStack 450
software versions 4.0 and 4.1, when you operate a mixed stack of BPS 2000 and
BayStack 450 switches, some of the BayStack 450 software version 4.1 and 4.2
enhancements may not be accessible.
Documentation correction
Autonegotiation can be enabled on every supported fiber optic MDA except the
BPS2000-2GE MDA. The previous documentation for BPS 2000 erroneously
states that you cannot enable autonegotiation for any fiber optic port.
Release Notes for the Business Policy Switch 2000 Software Version 2.0.5
10 New features and enhancements
New features and enhancements
The following new features and enhancements are offered with the BPS 2000
software version 2.0.5:
•Support for Far End Fault Indication (FEFI)—When a fiber optic
transmission link to a remote device fails, the remote device indicates the
failure and the port is disabled. To use FEFI, you must enable autonegotiation
on the port.
Note: FEFI will not work with the BPS 2000-2GE MDA because the
BPS 2000-2GE MDA does not support autonegotiation.
•Increased support from 40 to 150 RMON alarms
•CLI support for RMON—See “New and enhanced NNCLI commands for
version 2.0.5” on page 20for a description of the new commands.
•SNMP support for downloading ASCII configuration files
•Settable Multicast MAC address for Spanning Tree Groups (STG)
— Refer to “New and enhanced NNCLI commands for version 2.0.5” on
page 20 for instructions on using this feature using the CLI.
— Refer to “Enhanced Web-based management features” on page 18 for
instructions on using this feature with Web-based management.
— Refer to “Enhancements to the console interface” on page 19 for
instructions on using this feature with the console interface.
•SNMP support for downloading diagnostics—See“New Device Manager
features” on page 12.
•Device Manager enhancements—See“New Device Manager features” on
page 12 for a description of the enhancements.
•Support for IGMP FAST LEAVE in Hybrid mode
•Unknown multicast frame handling enhancement
— Refer to “Unknown multicast frame handling enhancement” on page 12
for explanation of this feature.
— Refer to “New and enhanced NNCLI commands for version 2.0.5” on
page 20 for instructions on using this feature using the CLI.
•BPS 2000-2GE MDA laser turned off when port disabled
210676-P
New features and enhancements 11
•CLI enhancement for clearing Common Open Policy Services (COPS) server
table—See“New and enhanced NNCLI commands for version 2.0.5” on
page 20 for a description of the new command.
•Cannot enter broadcast address for MAC DA filtering
•CLI enhancement for saving configuration to NVRAM—See “New and
enhanced NNCLI commands for version 2.0.5” on page 20 for a description
of the new command.
•CLI enhancement for removing all VLANs—See“New and enhanced NNCLI
commands for version 2.0.5” on page 20 for a description of the new
command.
•BPS 2000 Image If Newer option added to the software download menu—If a
newer image file is found, it will be downloaded and the switch will reset
when the download process finishes successfully. Support for this feature has
been added to the CLI, console, SNMP and Web-management.
The following new features and enhancements are offered with the BPS 2000
software version 2.0:
•Enhancement to BootP mode—Beginning with software version 2.0, the
BootP or Last Address mode of BootP will always BootP for its IP
configuration, regardless of whether a configured IP address is present, when
the Stack BootP Mac Address Type is set to Base Unit Mac Address. If BootP
is successful, the retrieved IP parameters are used by the switch or stack. The
retrieved IP parameters are copied to the Last BootP IP parameters and
overwrite any user-configured IP parameters. This feature applies only to a
standalone BPS 2000 unit or to a stack consisting only of BPS 2000 units with
the Stack Operational Mode set to Pure BPS 2000 Stack.
•Support for BPS 2000-1GT, BPS 2000-2GT, and BPS 2000-2GE MDAs
•QoS rate shaping
•No longer need to configure QoS meters if not metering traffic
•Improved QoS Wizard Web configuration pages
•QoS Quick Config Web configuration pages
•QoS filtering of multiple VLANs per Layer 2 filter
•Configurable VID for tagged STP BPDUs
•IP address for each switch in a stack
•MAC destination address (DA) filtering
•Port naming
Release Notes for the Business Policy Switch 2000 Software Version 2.0.5
12 Unknown multicast frame handling enhancement
•QoS policy enable or disable
•Enhanced Web QoS error reporting
Unknown multicast frame handling enhancement
By default, unknown multicast traffic is flooded to all ports in a VLAN. In
situations where there is a multicast transmitter that is not doing IGMP and there
are no multicast receivers, the traffic transmitted by the transmitter is flooded.
The new IGMP unknown mcast no flood CLI commands included in software
version 2.0.5 allow you to send all unknown multicast traffic to IGMP static
router ports only. This traffic will not be forwarded to dynamically discovered
mrouter ports. If you want to forward unknown unicast traffic to certain ports
only, you can set those ports as static mrouter ports.
•When disabled, BPS 2000 will treat unknown multicast traffic like broadcast
traffic (flood). This is the default behavior.
•User setting for the unknown mcast no flood feature will be stored in
NVRAM. In a stack, if settings on different units differ, Base Unit setting will
take precedence. This feature can be enabled or disabled at any time.
•In a mixed BPS 2000/BayStack 450 stack, the unknown mcast no flood
feature, if enabled, will take effect only on BPS 2000s. BayStack 450s will
still flood unknown multicast traffic. Enabling this feature is not
recommended in a mixed BPS 2000/BayStack 450 stack.
•It is suggested that this feature be used when IGMP snooping is enabled.
Refer to “IGMP CLI commands” on page 31 for a description of the new IGMP
CLI commands for the unknown mcast no flood feature.
New Device Manager features
This section discusses the new Device Manager features included in software
version 2.0.5 and covers the following topics:
•“Device status within a stack,” next
•“The management VLAN ID” on page 14
210676-P
New Device Manager features 13
•“Base unit IP address” on page 15
•“IP addresses for the stack” on page 15
•“Designating the diagnostics file” on page 16
•“Downloading the ASCII config file” on page 16
Device status within a stack
The Device Manager will display devices that are down in a stack (Figure 1).
Figure 1 Device view
Release Notes for the Business Policy Switch 2000 Software Version 2.0.5
Loading...
+ 30 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.