Transcript
MRV - CONFIDENTIAL
OptiSwitch-200,400,800,1200,2400 application revision
Release Notes For version 3.71
Product Name:
OptiSwitch®
Product No:
OptiSwitch-200,400,800,1200
Product Version:
3.71
Document Revision:
01
Date of issue:
16-Aug-04
Author:
Yuval Lange
File:
3.71 release note.doc
Optical Access Confidential
1
Revision No.
Date of Issue
01
16-Aug-04
Reason for Change
Table 1: Document Revision Control
Page of change
Section
Change in text
Table 2: Changes Since Last Document Revision
Optical Access Confidential
2
Contents 1.
INTRODUCTION .......................................................................................................................... 4
2.
NEW FEATURES , CHANGES AND ENHANCEMENTS ....................................................... 5
3.
NEW SUPPORTED MODULES ................................................................................................ 11
4.
BUG FIXES AND IMPROVEMENTS ....................................................................................... 12
5.
KNOWN LIMITATIONS ............................................................................................................ 14
Optical Access Confidential
3
1. Introduction
3.71 is the new software version for the OptiSwitch® product family. This document describes the new features and the changes made in the software revision 3.71, in respect to the official revision, 3.70.
Optical Access Confidential
4
2. New features , Changes and Enhancements 2.1. MSTP Support 2.1.1. General: Multiple Spanning Tree Protocol (IEEE 802.1S std.) is now implemented in the OptiSwitch®. IMPORTANT: MSTP is operational only when all modules are type EM2004-xx
2.1.2. MSTP Management - Cli Commands: Important Note: Since most of the STP commands are common to both STP modes (Rapid and Multi), following commands (unless it specifies specifically) configure the STP database according to the STP run-time mode. In case STP mode is disabled, those commands will refer to the default mode, which is STP Multi – 802.1s.
2.1.2.1.
Tag’s Instances Management
`st-set-tag-instance` - Creates MSTP Tag instance. Usage - `st-set-tag-instance P1 P2 [P3]` P1 – STP Identifier, any number between 1 - 4 P2 – List of tags, T1,T2,….,Tn , - for range. P3 – Instance name. `st-del-instance` - Deletes existent instance(s). Usage - `st-del-instance [P1] ` P1 – List of STP Identifiers, default is ALL. `st-modify-instance` - Modifies existent instance. Usage - `st-modify-instance P1 P2 P3 ` P1 – Type of modification: `a` - add , `d` - delete P2 – STP identifier P3 - List of tags, T1,T2,….,Tn , - for range.
Optical Access Confidential
5
2.1.2.2.
Bridge Configuration
`st-get-br-cfg` - Retrieves bridge configuration. Usage - `st-get-br-cfg [P1]` P1 – List of STP identifers or `ALL`, default is 0 - Cist configuration. With no arguments (or P1=0 - default) command will retrieve Cist information, for other valid Instance ID`s, bridge’s instance information will be displayed. `st-set-br-prio` - Sets STP instance(s) bridge priority in steps of 4096. Usage - `st-set-br-prio [P1] [p2]` P1 – Bridge priority, 0..61440 , default is 32768. P2 – List of STP identifers , default is 0 - Cist configuration. `st-set-br-maxage` - Sets STP instance(s) bridge max age. Usage - `st-set-br-maxage [P1] [p2]` P1 – Bridge standard maxage, 6..40 seconds, default is 20 seconds. P2 – List of STP identifers , default is 0 - Cist configuration. `st-set-br-hellotm` - Sets STP instance(s) bridge hello time interval. Usage - `st-set-br-hellotm [P1] [p2]` P1 – Bridge hello time interval, 1..10 seconds, default is 2 seconds. P2 – List of STP identifers , default is 0 - Cist configuration. `st-set-br-fwdel` - Sets STP instance(s) bridge forward delay. Usage - `st-set-br-fwdel [P1] [p2]` P1 – Bridge forward delay time, 4..30 seconds, default is 15 seconds. P2 – List of STP identifers , default is 0 - Cist configuration. `st-set-br-force` - Sets STP instance(s) bridge force version. Usage - `st-set-br-force [P1] [p2]` P1 – Bridge force version, force_ rapid, multi, default is multi. P2 – List of STP identifers , default is 0 - Cist configuration. `st-set-br-mst-name` - Sets MST Configuration Identifier. Usage - `st-set-mst-name [P1] ` P1 – MST Configuration Identifier, default is NULL. `st-set-br-mst-rlevel` - Sets MST Configuration revision level. Usage - `st-set-mst-rlevel [P1] ` P1 – MST Configuration revision level, default is 0. `st-set-mstp-br-cfg` - Sets MSTP bridge configuration. Usage - `st-set-mstp-br-cfg [P1] [P2] [P3] [P4] [P5] [P6] [P7] [P8] P1 – Bridge standard maxage, 6..40 seconds, default is 20 seconds. P2 – Bridge hello time interval, 1..10 seconds, default is 2 seconds. P3 – Bridge forward delay time, 4..30 seconds, default is 15 seconds. P4 - Bridge Transmit Hold Count 1..10 seconds, default is 3 seconds. P5 - Bridge Max Hops Limit 4..30 seconds, default is 14 seconds. P6 - Bridge force STP version [force_ rapid|multi], default is `multi`. P7 - MST Configuration Revision Level, default is 0.
Optical Access Confidential
6
P8 - MST Configuration Identifier, default is NULL. `st-set-mstp-msti-br-cfg` - Sets MSTP instance bridge configuration. Usage - `st-set-mstp-msti-cfg[P1] [P2] [P3]` P1 - MSTP instance identifiers, 0 - for CIST, default is 0. P2 - Bridge priority 0..61440, default is 32768. P3 - Instance name, default is NULL.
Optical Access Confidential
7
2.1.2.3.
Port Configuration
`st-get-prt-cfg` - Retrieves Port(s) bridge (Cist) and instance (Msti) configuration. Usage - `st-get-prt-cfg [P1] [p2]` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P1 – List of STP identifiers or `ALL`, default is ALL. With no arguments command will retrieve global port information, if a specific port specifies, more detailed information will be displayed. `st-set-prt-prio` - Sets the STP instance[s] port Priority (in steps of 16) Usage - `st-set-prt-prio [P1] [p2] [p3]` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 – Port priority 0..255; default : 128 P3 - List of STP identifiers; default : all `st-set-prt-pcost` - Sets the STP instance[s] internal port path-cost Usage - `st-set-prt-pcost [P1] [p2] [p3]` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 – Port path cost 1..200000000, or 0 for AUTO; default : 0 P3 - List of STP identifiers; default: all `st-set-prt-ext-pcost` - Sets the STP external port path-cost Usage - `st-set-prt-pcost [P1] [p2] [p3]` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 – Port path cost 1..200000000, or 0 for AUTO; default: 0 `st-set-prt-p2p` - Sets the STP instance[s] port admin Point to Point. Usage - `st-set-prt-p2p [P1] [p2] [p3]` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 – Either [yes|no|auto]; default : auto P3 - List of STP identifiers; default: all `st-set-prt-edge` - Sets the STP instance[s] port admin Edge. Usage - `st-set-prt-edge [P1] [p2] [p3]` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 – Either [yes|no]; default : yes P3 - List of STP identifiers; default: all `st-set-prt-hellotm` - Sets the STP port hello time. Usage - `st-set-prt-hellot [P1] [p2] [p3]` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 – Port`s Hello Time value 1..10 seconds; default: 2 P3 - List of STP identifiers; default: all `st-set-prt-mode` - set the STP instance[s] Port`s mode. Usage - `st-set-prt-mode [P1] [p2] [p3]` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 – Either {enable|disable}; default: enable P3 - List of STP identifiers; default: all
Optical Access Confidential
8
`st-set-prt-mcheck` - Force BPDU migration check (14.8.2.4). Usage - `st-set-prt-mcheck [P1] [p2] ` P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 - List of STP identifiers; default: all `st-set-mstp-prt-cfg` - Sets MSTP bridge port (CIST) configuration. Usage - `st-set-mstp-prt-cfg [P1] [P2] [P3] [P4] P1 – Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P2 – Port external path cost 1..200000000, or 0 for AUTO, default is 0. P3 – Port adminEdge: either [yes|no], deafult is `yes`. P4 – Port adminPointToPoint: either [yes|no|auto], default is `auto`. P5 – Port adminNonStp: either [stp|nonStp], default is `stp`. `st-set-mstp-msti-prt-cfg` - Sets MSTP instance port configuration. Usage - `st-set-mstp-msti-prt-cfg [P1] [P2] [P3] [P4]` P1 - MSTP instnace identifiers, 0 - for CIST, default is 0. P2 - Ports list: S1.D1-...-Sn.Dn, <..> for range; default : all P3 – Internal port`s path cost 1..200000000, or 0 for AUTO, default is 0. P4 – Port`s priority 0..255, default is 128.
Optical Access Confidential
9
2.2. Legacy STP Obsolete Legacy Spanning Tree protocol mode is no longer supported in the OptiSwitch®, Rapid Spanning Tree should be used instead for single instance spanning tree networks.
2.3. Longer Vlan Name The OptiSwitch® now supports 11 character vlan names. Not including the vlan name prefix feature.
2.4.
4K Vlans for OS1200 & OS2400 As of this version, all OptiSwitch® chassis will support 4K vlans.
2.5.
System Flows in Configuration File When using Diffserv port configuration certain port types have automatic system flows configured onto them. On interior-vpt and interior-tos ports 8 system flows are configured for each port. These flows can be modified for special purposes, and in such cases they can be saved in the uploaded tftp configuration files and downloaded into a switch as part of the regular configuration. Before getting the tftp configuration file from the switch, the user must type the command – ds-set-sys-flows-upld-mode [enable] this feature is saved in NVRAM so after setting the switch to this mode it is saved after resets.
2.6.
Enhanced Frame Generator
2.6.1. As of this version it is possible to configure two additional parameters for the internal frame generator – vlan tag and vlan vpt value (priority). These parameters will be included in the sent packets (when sent on a tag-aware port). To configure these parameters use the known set-fg-param command the new parameters are added at the end of the variable list and are optional. 2.6.2. A new command was added: get-fg-param. It retrieves the fram generator configuration parameters.
2.7. New Diffserv Port Type: Efrm-Access A new Diffserv port type is introduced – “efrm-access” it is to be used for access ports that connect to cpe-efrm equipment. Note that users who used regular “portaccess” configuration for cpe-efrm connectivity can continue to do so and do not have to reconfigure their flows.
2.8. STP Emulation Mode Enhancement When the switch is in STP emulation mode it now not only floods incoming Bpdu’s across the vlans but also responds to TCN Bpdu’s by flushing its address table.
Optical Access Confidential
10
3.
New Supported Modules EM2004-4SF3S1
4-port 100BaseFX single fiber Uplink for the OptiSwitch® Family (SM; 1310nm; 0-20km; SC). Operates with EM2004-4SF5S1 and EM2004-4T+SF5S1
EM2004-4SF5S1
4-port 100BaseFX single fiber Uplink for the OptiSwitch® Family (SM; 1550nm; 0-20km; SC). Operates with EM2004-4SF3S1 and EM2004-4T+SF3S1
Optical Access Confidential
11
4.
Bug Fixes and Improvements
4.1. Disconnecting secondary ports on etherchannel In previous versions when an EC was configured with a forced-port and the secondary port was disconnected while the forced-port was connected traffic was affected for a short period of time. This is now fixed and traffic is no longer affected in such a scenario.
4.2. ***Link down trap on etherchannel Link-down / Link-up SNMP traps would sometimes get “lost” on etherchannels with forced-port configuration. This is now fixed.
4.3. RSTP instability during software upgrade In previous versions when RSTP was enabled – trying to upgrade the firmware with ‘reset after download’ parameter set to ‘off’ – caused problems in performance of RSTP in the network during the time that the agent was copying the new firmware from RAM to FLASH. This problem is now fixed.
4.4. STP cisco compatibility flag in configuration files In STP operation there is a possibility to configure a port to be “cisco compatible” meaning it will inter-operate its STP protocol with a cisco bridge. As of this version, this flag is correctly saved in uploaded tftp configuration files and reloaded from NVRAM.
4.5. Setting vlans in mcast mode In previous versions it was possible to configure (erroneously) few vlans on ports that were not tag-aware, this is now prohibited.
4.6. Changes in SLA Tables Affect Runtime Flows In previous versions, changing the SL-to-TOS, SL-to-VPT tables values would not affect runtime flows and required a reset. As of this version, these changes take effect immediately when they are performed.
4.7. STP 24H Topology Changes In certain configuration of Spanning Tree occasional topology change notifications would appear every 24 hours, causing some instability in the network. This is now resolved.
Optical Access Confidential
12
4.8. Adding Tag Based Flows In previous versions it was not possible to configure tag-based flows for virtual vlan-access ports (non existent). This is now possible.
4.9. Non-STP Ports in Upload Configuration Files In previous versions, non-stp ports would sometimes be saved in the uploaded files as active stp ports. This is now fixed.
4.10. Special Multicast Packets when using STP In previous versions, when spanning tree was enabled, the switch would drop special multicast addresses. These addresses were in the range of 01-80-c2-00-00-02..ff. This is now fixed.
Optical Access Confidential
13
5. Known limitations 5.1.
Firmware upgrade to this version using “ app-sw-dnld” can be done from the released 3.68 version only for OS200, OS400 and OS800. For OS1200 that is possible only from version 3.70.
5.2.
SFP Digital Diagnostics readout is only valid for CWDM compliant SFP units. When get-sfp-diagnostics’ command is used for other SFP units it will produce “gibrish” on screen.
5.3.
When RSTP is enabled - configuring or deleting an Etherchannel when at least one of its ports is connected (link up) is not possible (blocked by application). If modification in Etherchannel definition is needed – first disconnect all the ports in the Etherchannel.
5.4.
GVRP protocol is not supported in this version.
5.5.
Downgrading from this version to earlier versions is not fault-proof and may require an init-nvram procedure.
5.6.
This version is only compiled for new hardware suits. Meaning JX CPU agent of higher than ‘1’ version and CX CPU agent of higher than ‘2’ version.
5.7.
Before using new modules with this version please make sure they are supported in it.
5.8.
Except for special cases, this version is not to be used with modules based on GT-48310 / GT-48320 chipsets, to make sure you are not using these old chipsets enter the command sys-stat. All modules revisions (in parenthesis) should be equal or greater than 3. This is relevant to L2 modules only; All L3 modules are supported in current software revision.
5.9.
When an etherchannel is defined with a forced-port, the forced-port should be the lowest port in the etherchannel.
Optical Access Confidential
14
