7210-SAS E OS 4.0R5 SOFTWARE RELEASE NOTES

Transcription

1 7210-SAS E OS 4.0R5 MARCH 31, SAS E OS 4.0R5 SOFTWARE NOTES These release notes are for Release 4.0R5 of the 7210 SAS-E OS software for 7210 SAS E devices. NOTE ORGANIZATION The following are the major topics covered in these Release Notes: Standard Software Upgrade Procedure on page 2 Resolved Issues on page 7 New Features on page 15 Enhancements on page 20 Known Limitations on page 27 Known Issues on page 30 * V4.0.R5* Alcatel-Lucent Page V4.0.R5

2 SOFTWARE UPGRADE PROCEDURES The following sections contain information for upgrading to the 4.0R5 software version. In particular, there are sections that describe the following: Standard Software Upgrade Procedure Procedure for performing a standard, service-affecting upgrade. Note that when upgrading from Release 1.0 or 1.1, ensure that the 7210 SAS E is not power cycled until the following upgrade procedure is completed. STANDARD SOFTWARE UPGRADE PROCEDURE This section describes the standard software upgrade procedure which is service-affecting: Each software release includes a boot loader (boot.tim) and the software image (both.tim). The boot loader initiates the loading of the 7210 SAS OS image based on the boot options file (bof.cfg) settings. The following steps describe the software upgrade process: Step 1. Backup existing images and configuration files New software loads may make modifications to the configuration file which are not compatible with older versions of the software. Note: Alcatel-Lucent recommends making backup copies of the BOOT loader (boot.tim), software image and configuration files, should reverting to the old version of the software be required. Step 2. Step 3. Copy 7210 SAS E images to cf1: The 7210 SAS E image files must be copied to the cf1: device on the 7210 SAS E node. It is good practice to place all the image files for a given release in an appropriately named subdirectory off the root, for example, cf1:\4.0r5 Copying the boot.tim and other files in a given release to a separate subdirectory ensures that all files for the release are available should downgrading the software version be necessary. Copy boot.tim to the root directory on cf1: The BOOT Loader file is named boot.tim. This file must be copied to the root directory of the cf1: device. Note: If it is not possible to overwrite cf1:\boot.tim file, Change the cf1:\boot.tim attributes using file attrib -r cf1:\boot.tim command. Page 2 Alcatel-Lucent

3 Step 4. Modify the boot options file to boot the new Image. The Boot Options File (bof.cfg) is read by the BOOT Loader and indicates primary, secondary and tertiary locations for the image file. The bof.cfg should be modified as appropriate to point to the image file for the release to be loaded. Use the bof save command to save the Boot Options File modifications. Step 5. When upgrading to Release 4.0R5, execute the admin reboot upgrade command. Allow the boot sequence to complete and verify that the card comes up. Note that, executing 'admin reboot upgrade' command system will upgrade the bootrom if required. Step 6. Upgrade the Golden BOOT Loader (only if all of the above steps were successful). After successfully booting of the new version of 7210 SAS E image, upgrade the Golden BOOT Loader by executing the admin update-golden-bootstrap cf1:/boot.tim command. Note: After upgrade to 4.0 software images, during next boot, if the user forgets the BOF password and fails to provide a correct password, after three attempts, the system prompts the user to reset the BOF password to factory default. If user accepts BOF password recovery, as a security measure, the system also resets the flash to factory defaults (that is, it removes all the files from the flash except the boot image file (cf1:\boot.tim) and Timos image file (cf1:\both.tim)) and reboots the node with the factory default settings. Refer 7210 User Guide and "BOF PASSWORD RECOVERY" in Enhancements section of this document for more details. UPGRADING FROM PRIOR S For 4.0R4 During upgrade to 4.0R4 release, the following warning message displayed can be ignored: MAJOR: CLI #1010 Saps in the system will be re-configured without Sap Indexs because Sap index file could not be located. After upgrade to 4.0R4, it is recommended to save the configuration. When the configuration is saved with 4.0R4 build, sap index file with extension.sdx is automatically generated and saved at a location where the configuration file is stored. For more information, see, "Efficient Allocation of SAP Ingress QoS Resources and Service SAP Scaling" feature in "New Features"of this document. Prior to 4.0r1 Release: Y.1731 MA NAME From 4.0R1, Y1731 MA name should be unique across the system. During upgrade to 4.0R1, if system finds duplicate names in the configuration file then upgrade to the new configuration fails. Before upgrade, it is recommended to modify the configuration file. For example, CLI "association 1 format icc-based name "abcdabcdabcd1" name "abcdabcdabcd1" should be unique across system for successful upgrade to 4.0R1. Prior to 1.0R5 release: The following router-name parameter was supported: CLI Syntax: config>router router-name The parameter values acceptable for router-name were Base and management. Alcatel-Lucent Page 3

4 The management value is no longer applicable to the 7210 SAS and has been removed in 1.0R5 and above releases. If the boot-up configuration file contains the above command parameter, it must be removed from the configuration file before upgrading to 1.1R3. Note: The following two lines typically appear as the default configuration in the configuration file: router management Both lines must be removed. Prior to 1.1R3 release: The following commands were supported: config>router>policy-options# info policy-statement name entry entry-id from no prefix-list default-action accept no preference no metric no tag no type config>router>policy-options# The following commands are no longer applicable to the 7210 SAS-E have been removed in 1.1R3 and must be removed from the configuration file before upgrading to R1.1R3 or above: prefix-list name [name...(up to 5 max)] no prefix-list preference preference no preference metric {add subtract set} metric no metric tag type no tag type type no type Prior to 1.1R3 release: The range for the table-size parameter was This value is not supported and has been restricted to 2047 from Release 1.1R3 onwards. The configuration file value must be changed to 2047 before upgrading to 1.1R3 or above. CLI Syntax: config>service>vpls$ mfib-table-size table-size Page 4 Alcatel-Lucent

5 Prior to 2.0R5 release: When upgrading from the configurations to 2.0R5 software of below type will error out at collect-stats of the sap. Refer below for mentioned configuration changes should be done before upgrading prior to 2.0R5 config:- accounting-policy 5 record service-ingress-octets default to file 5 no shutdown accounting-policy 6 shutdown record service-ingress-packets to file 6 *A:STU>config>service>vpls>sap# info statistics egress ingress counter-mode packet collect-stats accounting-policy Modifications required in configurations before upgrade *A:STU>config>service>vpls>sap# info statistics egress ingress counter-mode packet accounting-policy have been swapped from earlier config collect-stats have been swapped from earlier config Another Scenario:- Earlier Saved config:- accounting-policy 5 shutdown record service-ingress-octets Alcatel-Lucent Page 5

6 to file 5 accounting-policy 6 record service-ingress-packets default to file 6 no shutdown *A:STU>config>service>vpls>sap# info statistics egress ingress counter-mode octet collect-stats accounting-policy Configuration to be modified accounting-policy 5 shutdown record service-ingress-octets to file 5 accounting-policy 6 record service-ingress-packets default to file 6 no shutdown *A:STU>config>service>vpls>sap# info statistics egress ingress counter-mode octet accounting-policy have been swapped from earlier config collect-stats -----had been swapped from earlier config Page 6 Alcatel-Lucent

7 RESOLVED ISSUES R4.0R5 The following are specific technical issues that have been resolved in Release 4.0_R5 of SAS E OS. In previous releases, DC input fail detection was not working with certain new part numbers of 7210 SAS-E, For example: 3HE04410ABAD02. The issue is resolved in this release. [133311] From 7210 SAS 4.0R5, for record type SAA, acct-policy "collection-interval" minimum value starts from 1 minute, now ranges minutes. [132523] There existed MIB compilation issues using some of the third party tools, in this release MIB's can be compiled using some of the third party tools. [118513] R4.0R4 The following are specific technical issues that have been resolved in Release 4.0_R4 of SAS E OS. In previous releases, ingress Meter's "Total Forwarded" value was counted in "Total Dropped" when counter-mode is set to forward-drop-count, this issue is resolved in 4.0R4.[130887] In previous 4.0 releases, on execution of CLI "config system security mgmt-access-filter ip-filter entry 1 router <router-instance>", console hanged and management access to the system was blocked. This issue is resolved in 4.0R4.[130545] R4.0R3 The following are specific technical issues that have been resolved in Release 4.0_R3 of SAS E OS. Issue of dropping LLC frames, which are received on sap with control field 0x8e88, is resolved in 4.0R3.[126469] R4.0R2 The following are specific technical issues that have been resolved in Release 4.0_R2 of SAS E OS. Using 4.0R1 release, file download using SCP took more time compared to previous releases. In 4.0R2, this issue has been resolved, and file download time is similar to pre- 4.0r1 releases. [126557] In previous releases, "show eth-cfm mep" for remote mep, Rx CC showed "True" but HighestDefect showed "defremoteccm" when the remote MEP was deleted or remote port/sap was shut down. This issue has been resolved. [124981] In 4.0R1, if no ports were assigned for "uplinka-port", "uplinkb-port", and "eth-mgmt-disabled" in bof, image load from flash "cf1:\" was failing and box was not booting. This issue has been resolved in 4.0R2.[126409] R3.0R5 The following are specific technical issues that have been resolved in Release 3.0_R5 of SAS E OS. Alcatel-Lucent Page 7

8 Creating a user with all the SNMP OIDs are sent in one PDU and executing CLI "admin display-config" and "admin tech-support", or "configure system security / info", hangs CLI session. This issue has been resolved. This issue does not occur in SAS-E 1.1 and 1.0 releases. [117416] After a few hours, the 7210 SAS-E would fail to sync the system time with an NTP server. In this release, the 7210 SAS-E syncs with the server. This issue was observed with 3.0R3 and 3.0R4[118779] R3.0R3 The following are specific technical issues that have been resolved in Release 3.0_R3 of SAS E OS. In previous release, "Egress Stats" of CLI " show service id <> sap <>" did not increment on epipe service when the ingressing sap is Q1.* or QinQ with etype configured and the egressing sap can be any dot1q encapsulation other than *. This issue has been resolved. [109205] R3.0R2 The following are specific technical issues that have been resolved in Release 3.0_R2 of SAS E OS. IP In prior release, ARP resolution was not working properly when changing qinq etype to 0x9100(non default value) and clearing ARP database on a 0.* SAP in an IES service. This issue has been resolved. [109299] SYSTEM In prior release, some 7210 SAS-E and 7210 SAS-M system reported false fan alarms even when the fan module was working properly. The system would report fan failure alarm ("Fan 1 failed") followed by fan failure clear alarm ("Clear Fan 1 failure"). This issue has been resolved. [108035] In prior releases, the system used to raise an over-temperature alarm when the temperature measured by the chassis exceeded the threshold of 50C. This threshold has been increased to 58C for the 7210 SAS-E platforms (that is, 7210 SAS-E 12T 12F) to allow for an offset between aisle ambient temperature and temperature measured by the chassis. [107935] 3.0R1 FAN speed and sound oscillates when SAE-E running with 2.0R5 release. This issue has been fixed in 3.0R1. [108461] In prior release, egress mirroring was stopped for the port which is part of a lag, after port shut-/no-shut is done. This issue has been fixed. [105269] The following issue has been fixed If a SAP with 0.* encapsulation is associated with an IES service (for management) and if another SAP exists with X.* encapsulation (where X is any.1q value other than 0) belonging to the same port and associated with VPLS or Epipe service, then incoming packets with outer tag as 0 and inner tag as X are dropped. [95980] The following issue has been fixed Egress filters applied on a.1q SAP of service (A) can match packets (with the same.1q tag) of a different service (B) destined to a.1q* SAP on the same physical port. Counters Page 8 Alcatel-Lucent

9 associated with the filters are also incremented. This is applicable only in the case of an ingress SAP of service (B) having either a null or.1q* encapsulation. [84135] 2.0R5 Saving and executing configuration for any of the accounting policies to collect in a default mode (service-ingress-packets, service-ingress-octets, service-egress-packets and combined-service-ingress-egress-packets), error out issue is fixed in this release. [106949] 2.0R4 The following are specific technical issues that have been resolved in Release 2.0_R4 of SAS E OS. OAM When dot1x was enabled on an efm-enabled port, the port would go down. Now, the port state is set as expected. [98397] QOS Copy command did not work for qos network policy. This command now works.[103294] SYSTEM The 7210 showed a high CPU utilization when a faulty SFP was inserted. This has been fixed. [82605/93904]] 2.0R2 The following are specific technical issues that have been resolved in Release 2.0_R2 of SAS E OS. Pinging an IES IP interface did not work for packet sizes over 8999 bytes. This has been fixed. [98821] 1.1R8 The following are specific technical issues that have been resolved in Release 1.1_R8 of SAS E OS. Creating a 2548th filter template along with the action criteria failed. This has been fixed. [95978] Changing the meter mode from srtcm to trtcm in a SAP ingress policy did not reset the PIR value to the default. Now, the PIR value is reset to max. [96267] The tools dump system-resources command output now displays the correct usage of resources for user ACLs. [91662] 1.1R7 The following are specific technical issues that have been resolved in Release 1.1_R7 of SAS E OS. Spurious traps No NTP server available/ntp server available were being sent out at times. This has been fixed. [93106] RADIUS packets went out with system IP address as the source IP address even though a source address was configured for the RADIUS application. Now, they go out with the configured source address. [92018] Alcatel-Lucent Page 9

10 When IGMP packets received from peers were forwarded to another peer, an extra 4 bytes was added in the Layer 2 frame (the IGMP packets were successfully processed though). Now, the extra 4 bytes is not added. [91891] 1.1R6 The following are specific technical issues that have been resolved in Release 1.1_R6 of SAS E OS. ACLS Under management access filters, the src-port match-criteria cpm option has been removed as it is not supported. [87556] 1.1R4 The following are specific technical issues that have been resolved in Release 1.1_R4 of SAS E OS. SYSTEM The monitor port and monitor lag commands showed incorrect statistics. Now they show correct statistics. [83757/86347] STATISTICS/ACCOUN TING In prior releases, access-uplink-specific accounting records could be enabled for access ports, though no accounting records were being generated. From this release onward, CLI/SNMP restricts users to enable accounting only on access-uplink ports for the accessuplink-specific records. [87158] 1.1R3 The following are specific technical issues that have been resolved in Release 1.1_R3 of 7210 SAS-E OS. IGMP SNOOPING If there is a single static multicast group configured in an IGMP snooping-enabled VPLS service, the entry would get deleted if igmp-snooping were disabled and enabled again. This issue has been fixed. [82039] A second change in an MFIB size, high and low watermark configurations did not take effect. Now, the changes take effect. [83265] Tagged multicast packets on a null SAP were forwarded based on the MFIB entries. Now they are flooded within the VPLS service. [82130] MIRROR CPU generated packets such as STP, EFM, Dot1ag packets now get mirrored when configured for port egress mirroring. [70197/70305] Egress port mirroring now works on a port that is in an EFM OAM local loopback state. [71761] Now, egress mirroring stops when a port/lag is brought down by EFM OAM. [73377] SERVICES Remote aging for MACs learned by an uplink SAP is now supported. [71914] Page 10 Alcatel-Lucent

11 SYSTEM Rising and falling alarms for flash and memory usage are raised correctly, but the values reported for flash and memory usage were incorrect. This has been fixed. [75455] Upon link flaps and system bootup, the following messages were sometimes displayed: - [bcmlink.0]u=0 p=1 phyctrl_speed_get rv=-11 - [bcmlink.0]port ge1: bcm_port_update failed: Operation failed Now, they are not displayed. [74235] 1.0.R5 The following are specific technical issues that have been resolved in Release 1.0.R5 of 7210 SAS-E OS. ACLS In an Epipe service with an ingress ACL associated to a SAP on a LAG, traffic was affected during the removal and addition of LAG member ports. [81025] The system previously only allowed 1016 filter entries (template entries) to be created. Now, the system can create up to 576 filter profiles and each profile can have up to 126 entries. [76725/76674] A filter configured with an IP source or destination port configured as 0 matched all packets. Now, only those packets with port value as 0 are matched. [76828]. OAM CFM linktrace and loopback messages were forwarded between SAPs belonging to the same split horizon group. Now, the messages are not forwarded between such SAPs. [81651] Dot1ag-MEP on null ports accepted tagged CCM messages. Now they are dropped. [79496] SERVICES When SHG is configured for a group of SAPs participating in an IGMP snooping-enabled VPLS service, IGMP packets, such as queries received on one of these SAPs, were replicated to all other SAPs. Now, the queries are not replicated to other SAPs participating in the same split horizon group. [82075] The Disable Learning feature on SAPs in VPLS services now works. [74992] STP STP/L2PT PDUs with invalid LLCs on STP/L2PT-enabled ports were forwarded. Now they are dropped. [71551/82676] L2PT packets egressing on a port which is a part of a split-horizon group is fixed now. [80233] QOS SAP ingress meter counters and statistics were incremented when an Epipe service was in an operationally down state even though the traffic was dropped. Now, the counters do not increment. [83270] In a port-scheduler-policy, if the weight of a queue was modified, it affected the weight of the other queue. [80721] CLI The strict mode parameter was added in the CLI in the port-scheduler-policy policy-id context. [75364] Alcatel-Lucent Page 11

12 IP ICMP packets egressed out based on the best available route. Now, when the ping command is executed with the next-hop option, the correct egress interface is chosen. [80455] MIRROR A LAG could not be the ingress source of one mirror service and egress source of another mirror service. [73371] MANAGEMENT The persistence feature did not function if the configuration file did not have.cfg extension. [76909] SNMP did not respond at times and CPU utilization spiked when an SNMP walk was performed on the log table. This was due to log configurations collecting event information from multiple sources and directed to a single destination. [79918] The bootloader extends support for copper SFPs in 100FX (1G mode only) and dual rate SFPs. 1.0.R4 The following are specific technical issues that have been resolved in Release 1.0.R4 of 7210 SAS-E OS. SNMP A memory leak was seen when EFM OAM-related traps were generated toward an administratively shutdown management port. The leak is no longer seen. [79872] Optimization done in handling bursts of SNMP requests from SAM. As a result of this optimization, response times to syncs (SNMP walks) from SAM are improved. [78561] SYSTEM Copper ports operating in half-duplex mode (10Mbps) in some scenarios generated timing out draining packets messages. The messages are no longer generated. [79434] The show mda detail command output now displays the current MDA temperature. [77370] IP ICMP ping with TTL=1 to the system IP now works. [78993] MANAGEMENT The bootloader now prompts for uplinkb port settings if the uplinka port is not configured. [77928] During manual bootup, if uplinka or uplinkb ports are set to invalid values, the other related parameters are reset to zero. [76533] The bootloader now prompts for uplinkb port settings if the uplinka port is not configured. [77928] CLI The show dot1ag cfm-stack-table command now shows only the supported direction, down [78942] The queue weight of the port scheduler policy help text has been modified to not display the no of packets result as it is unitless. [78858] The access egress policy help text has been modified to not display no queue <queue-id>. [78371] Page 12 Alcatel-Lucent

13 The info command shows the correct output in the port>ethernet>access>egress context. [77439] OAM During system reboots, sometimes the efm-oam-dying gasp displayed the following error message on the console: semgive failed on dgaspwakeup. [79537] This error message is no longer seen. 1.0.R3 The following are specific technical issues that have been resolved in Release 1.0.R3 of 7210 SAS-E OS. QOS Meter stats now show the correct values after a roll-over. [78876] Deleting a meter in a network ingress policy now generates a trap. [77828] SYSTEM Internal loopback of port does not work when loopbacked port speed is set to 100Mb and autoneg is turned off.[113995] In Fixed Copper port when Internal loopback is enabled, port speed is set to autonegotiated speed. For SPF ports if port is not shut before loopback is configured, speed is always set to autonegotiated speed, if port is shut before loopback then speed set to 1Gbps.[114904] 7210 SAS-E when internal loopback is configured on ethernet port, packets loopbacked are also sent out on wire for SFP ports. If it is fixed, copper port fragments of packets are sent out on wire. [113355/14600] When the BOF configuration was modified, the associated trap referenced an invalid object. This has been corrected to send the right object. [79245] The mac-address allocation for LAG has been adjusted to be within the chassis range. The new allocation also removes the conflict between the chassis base address and the MAC address of the first port of the MDA. [79216,79186] As a result of this change, it is required to upgrade the boot loader (boot.tim) to version 1.0.R3. It is also strongly recommended to upgrade the golden boot loader to the same version after successful upgrade of the boot.tim. To upgrade the golden boot loader to the new version, use the admin updategoldenbootstrap cf1:/boot.tim command after having booted with the new boot.tim. 1.0.R2 The following are specific technical issues that have been resolved in Release 1.0.R2 of 7210 SAS-E OS. IP Re-assembly of fragmented packets sent by the 7210 SAS-E failed on Linux and Solaris whereas Windows was able to re-assemble. This issue is fixed. [77805] Alcatel-Lucent Page 13

14 QOS SNMP walk on taccessegressfcentry would result in elements with wrong OIDs. This has been fixed. [77608] sapingqosmeterid under sapingqosmeterstatsentry now has the correct data type, INTEGER. [77673] SNMP walk on sapingqosmeterstatsentry results in an incomplete walk when uplink SAP is configured. This has been fixed. [77662] Page 14 Alcatel-Lucent

15 NEW FEATURES 4.0R5 There are no new features added to 4.0 R5 of the 7210 SAS-E OS. 4.0R4 The following items describe features added to 4.0 R4 of the 7210 SAS-E OS. EFFICIENT ALLOCATION OF SAP INGRESS QOS RESOURCES AND SERVICE SAP SCALING In previous releases of 7210 SAS, SAP ingress QoS resources must be configured with values in powers of 2 (example - 4, 8, 16, 32, 64 up to platform limit), potentially leading to inefficient allocation of available resources. With release 4.0R4, users can allocate SAP ingress QoS resources in multiples of 2 (example - 2, 4, 6, 8, 10, 12, 14., up to platform limit). With this users can allocate the available resources more efficiently. This allows for increase of service SAP numbers with 4.0R4 on 7210 SAS-E when minimum amount of QoS resources are used per SAP. In release 4.0R4, the SAP ingress default policy has been changed to allocate only 2 classification resources and single (1) meter (that is, num-qos-resources is set to a value of 2 by default). With the default policy only a single FC is defined and it uses meter 1 (the only meter) to meter all traffic types (that is, unicast, broadcast, multicast, and unknown-unicast). Additionally the use of multipoint keyword has been deprecated, except for use with meter 11. This allows users to use any meter with any traffic type allowing for efficient use of meters. If meter 11 is created by the user explicitly, then the system uses meter 11 for broadcast, unknownunicast and multicast traffic types. The system creates an additional index file by the name '<config-file-name>.sdx' at the same location where config file is located. This file needs to be preserved across a reboot. It is used by the system to guarantee allocation of resources to all the SAPs on a reboot. If the system does not find the file, it continues with booting up but there are no guarantees that the configuration file will execute successfully. From 4.0R4, 7210 SAS-E supports increased number of access SAPs. More details are available in the 7210 SAS QoS Guide. SAA FOR CFM/Y.1731 Service Assurance Agent (SAA) now supports the scheduling and accounting for loopback, linktrace and Y.1731 two-way-delay. SAA-specific CFM loopback, linktrace and DM functions support send-count, interval, timeout, forwarding class and continuous mode. Existing CFM OAM commands are now extended to support send-count and interval natively from this release. The SAA results may be monitored using configured event thresholds, including jitterevent, latency-event, and loss-event. SAA results can also be stored in accounting files. 4.0R3 There are no features added to 4.0 R3 of the 7210 SAS-E OS. Please refer to the Enhancement Section for any changes. Alcatel-Lucent Page 15

16 4.0R2 There are no features added to 4.0 R3 of the 7210 SAS-E OS. Please refer to the Enhancement Section for any changes. 4.0R1 The following items describe features added to 4.0 R1 of the 7210 SAS-E OS. IPV6 SUPPORT FOR OOB INTERFACES The 7210 SAS provides support for use of IPv6 with the out-of-band ethernet management port. This allows for use of IPv6 addressing and IPv6 networks for management of the node. Refer 7210 user guide for more details. 3.0R6 The following items describe features added to 3.0 R6 of the 7210 SAS-E OS. 24V SUPPLY SUPPORT With this release, 7210 SAS-E supports +24V power supply. This allows users the choice of using a +24V DC power source to power the node. Users can use two +24V power supplies in a redundant configuration. DC power source failure detection is supported. AC power supply use along with DC (+24V or -48V) power supply is supported from 3.0R6 release. Configured DC power supply type (+24V or -48V) is displayed using snmp MIB object "tmnxchassispowersupplyassigneddctype". Note: A mix of +24V DC and -48V power supplies must not be used together in the same chassis. 3.0R5 The following items describe features added to 3.0 R5 of the 7210 SAS-E OS. MULTIPLE SPANNING TREE PROTOCOL (MSTP) The Multiple Spanning Tree Protocol (MSTP) extends the concept of the IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) by allowing grouping and associating VLANs to Multiple Spanning Tree Instances (MSTI). Each MSTI can have its own topology, enabling load balancing by providing multiple forwarding paths. At the same time, the number of STP instances running in the network is significantly reduced as compared to Per VLAN STP (PVST) mode of operation. Network fault tolerance is also improved because a failure in one instance (forwarding path) does not affect other instances. The 7210 SAS implementation of Management VPLS (mvpls) is used to group different VPLS instances under single RSTP instance. Introducing MSTP into the mvpls allows interoperating with traditional Layer 2 switches in access network and provides an effective solution for dual homing of many business Layer 2 VPNs into a provider network. PORT INTERNAL LOOPBACK With this release, 7210 SAS-E supports port internal loopback feature. This feature enables an internal PHY/MAC loopback. With the internal loopback configuration, packets that Page 16 Alcatel-Lucent

17 egress out of that port (or SAPs created on that port) are looped back into the node instead of being transmitted on to the line/wire. The packet that ingress the system after the loop back are mapped to the same SAP on which the packet was sent out, as if its being received from another device connected to the port and is processed as per the service configuration for that SAP. A internal loopback on the port is expected to be used with a external third-party Ethernet test device. They can be used to diagnose problems with the service provisioning or for testing end-to-end performance metrics for the service. It is highly recommended that this command be used only for testing a VLL service. The source/destination MAC address swap is not done. Hence, its use in a VPLS service will potentially lead to rapid MAC address movement from one port to another. It is not required to insert an SFP/XFP into the device OR plugin the ethernet cable in case of fixed copper ports for the loopback to be functional. This command affects all the services provisioned on the port, since packets are looped back and sent out back to the sender. It is expected to be used only with a VLL service. It is recommended to turn off Layer 2 and IP control protocols (like xstp, LACP, EFM, 802.1x, LLDP, OSPF, etc.) on the device where the loopback command is executed and also on the peer device to avoid unnecessary protocol behavior (for example, protocol flaps due to time-out, etc.). 3.0R3 The following items describe features added to 3.0 R3 of the 7210 SAS-E OS. SUPPORT FOR DOT1Q EXPLICIT NULL SAP In this release, 7210 SAS-E allows for use of dot1q Explicit null SAP. It is allowed for use when the svc-sap-type is set to either 'dot1q' or 'null-star '. dot1q explicit null SAPs accept untagged or priority tagged packets. These SAPs can be used for either providing data service or in a 'mvpls' service. Additionally, in this release, 0.* SAP created on an access-uplink port can be used in a VPLS, EPIPE service, or in an IES service in 7210 SAS-E. A 0.* SAP is used to accept untagged or priority tagged packets. This feature is supported on the 7210 SAS-E in current release. It is already supported on the 7210 SAS-M and 7210 SAS-X in previous release. 3.0R1 The following items describe features added to 3.0 R1 of the 7210 SAS-E OS. G.8032 ITU-T G.8032 specification - version 1: defines protocol mechanisms to provide ethernet ring protection to enable deployment of resilient Ethernet Layer 2 networks. G.8032 (ETHring) is built on Ethernet OAM and is also referred to as Ring Automatic Protection Switching (R-APS). ETH-rings are supported only on VPLS SAPs (for VPLS Service). VPLS services supporting Eth-rings enables rings for core network or access network resiliency. ETH-ring multi-homing into other ETH-rings or VPLS PEs is not supported in the current release. ETH-rings offer fast resiliency for Ethernet services leveraging ring Alcatel-Lucent Page 17

18 topologies for any single link or node failure. By configuring multiple ETH-rings instances on the same physical topology, G.8032 can utilize all link resources in a ring. LLDP IEEE 802.1ab standard defines a protocol and management elements suitable for advertising information to stations attached to the same IEEE 802 LAN or LAN emulation for the purpose of populating physical or logical topology and device discovery management information databases. The protocol facilitates the identification of stations connected by IEEE 802 LANs/MANs, their points of interconnection, and access points for management protocols. For Provider Networks, it means automatic discovery of their internal Ethernet connectivity. Emulation and logical topology wording is applicable to the case of a customer bridge (enterprise/carrier of carrier use case) connected to a Provider Network offering a transparent LAN Emulation service to their customers. It helps the customer bridges detect misconnection by an intermediate Provider by offering a view of the customer topology where the Provider Service is represented as a LAN interconnecting these customer bridges. IEEE 802.1ab LLDP support will allow SAM to auto discover Ethernet link topology and to rapidly troubleshoot miss-connectivity like cross linked cables, port connectivity. 2.0R2 The following items describe features added to 2.0 R2 of the 7210 SAS-E OS. OUT-OF-BAND ETHERNET MANAGEMENT PORT 7210 SAS-E platforms supports 10/100 Base-T ethernet management port. This port is available for out-of-band management of the node. Note: To use Ethernet management port boot.tim image version should be 2.0R2 or greater. GENERATION OF Y.1731 AIS MESSAGE ON PORT DOWN This feature provides an optional capability that allows the 7210 SAS-E to generate Y.1731 AIS messages based on the port's operational state. By default, MEP exchanges CCM messages with the peer MEPs associated with it and generates AIS messages only when the CFM defect/fault detected on the MEP is of higher priority than the user configured defect. With this feature, the system tracks the operational state of the port on which a Down MEP is configured and sends out AIS messages when the port operational state changes to down. Through appropriate configuration, it allows the operator to disable generation of CCMs for the MEP and instead use only the port's operational state for generation of AIS messages. 2.0R1 The following items describe features added to 2.0 R1 of the 7210 SAS-E OS. ALARM INPUTS The 7210 SAS-E platform supports alarm inputs (dry contact input) that allows the operator to monitor and report changes in the external environment (such as temperature changes, door open/close, etc.). It supports 4 alarm inputs pins. Page 18 Alcatel-Lucent

19 IP INTERFACES IN A VPLS SERVICE The 7210 SAS-E supports IP interfaces in a VPLS service. IP interfaces in VPLS services provide only a host IP interface (non-routable). Only IP ping and IP traceroute applications are supported for this IP interface. It is primarily designed for use to verify service availability during service activation and/or during normal service use by using IP ping utility. DIGITAL DIAGNOSTICS FOR SFPS Digital Diagnostics Monitoring is a capability of some SFPs and XFPs where the transceiver module maintains information about its working status in device registers including: - Temperature - Supply voltage (for SFPs) - TX bias - TX output power - RX received optical power The transceiver is also programmed at the factory with Warning and Alarm thresholds for Low and High conditions of the above that can generate system events. The show port port-id detail command has been augmented to display the DDM data at the console, and the DDM data is accessible through SNMP for use with RMON threshold monitoring if traps are desired for custom thresholds. Y.1731 Y.1731 is defined by ITU-T. It is built on top of the IEEE 802.1ag, but it has more functionalities compared to the former, such as AIS, performance monitoring, etc. In this release, the following Y.1731 functionalities are supported: - ETH-CCM - ETH-LB - ETH-LT - ETH-RDI - ETH-AIS - ETH-TST - ETH-DM including one-way and two-way delay measurements. Software timestamps are used for delay measurement. QINQ ETHERTYPE The QinQ Ethertype can be set to encapsulate QinQ packets sent out by the node and for processing QinQ packets received by the node. This value can be set per port. The port Ethernet encapsulation type should be set to qinq to use this. It provides the ability to interoperate with other QinQ bridges/switches that use proprietary Ethertype for QinQ encapsulation. A set of three unique QinQ Ethertypes are user-configurable. The default value is set to 0x8100. Alcatel-Lucent Page 19

20 ENHANCEMENTS 4.0R5 There are no new enhancements added to 4.0 R5 of the 7210 SAS-E OS. 4.0R4 The following item describe enhancement added to 4.0 R4 of the 7210 SAS-E OS. AUTO-INIT ENHANCEMENT In previous releases, only priority tagged DHCP requests were sent out. With this release, In autoinit mode, DHCP requests are sent out by the node are in two formats. The system attempts to interact with the DHCP server in these two formats, one after another, if necessary. Initially the DHCP requests are sent out with a priority VLAN tag (VLAN ID = 0, Dot1p PCP bits set to 7). If no response is received from the DHCP server during the above request period, DHCP requests are sent out with no VLAN tag (a.k.a. null-tagged packets). This is supported on all platforms. NOTE: The above enhancement requires 4.0R4 "boot.tim".. 4.0R3 The following items describe enhancements added to 4.0 R3 of the 7210 SAS-E OS. SNMP DYING-GASP TRAP In release 4.0 R3, 7210 SAS-E support generation of SNMP dying gasp trap on power failure. By default, the system generates EFM OAM dying gasp message. The user needs to explicitly configure the system to send out an SNMP trap on loss of power to the node. Generation of SNMP dying gasp trap is mutually exclusive to use of EFM OAM dying gasp message. For details, please refer to the 7210 SAS-D/E System Management Guide. INPUT/OUTPUT DC POWER FAILURE TRAP From release 4.0R3, the software is capable of generating two traps, a separate one for DC power source failure (tmnxeqpowerinputfailure) and another for DC power supply failure (tmnxeqpoweroutputfailure). In releases prior to 3.0R8, the system generated a single trap (viz. tmnxeqpowersupplyfailure). From release 4.0R3, by default only the trap identified by the name tmnxeqpowersupplyfailure is generated. The new traps, that is, event-name (viz. tmnxeqpowerinputfailure and tmnxeqpoweroutputfailure) are optional and are suppressed by default. User needs to explicitly enable the generation of the new traps using the CLI command 'configure log event-control chassis event-name event-number generate'. The old trap (viz. tmnxeqpowersupplyfailure) will continue to be generated along with the new traps until user explicitly suppresses the generation using the CLI command 'configure log event-control chassis event-name event-number suppress'. In prior releases, on a power source failure along with the trap the Critical LED would glow RED. From release 4.0R3, additionally the status LED will blink when a power source failure is detected. Irrespective of which feed failed, the status LED will blink at the same rate. Page 20 Alcatel-Lucent

21 TRAP GENERATION FOR EXCEEDING INVALID LOGIN ATTEMPTS A SNMP trap is generated by the device when the login attempts exceed the configured threshold for radius/tacacs/local user. The threshold can be configured using the CLI parameter 'count' in the command config> system> security> password> attempts <count> [time <minutes1>] [lockout <minutes2>]. tmnxuserloginmaxattempts trap is generated when a user failed to authenticate in more than permitted number of retires through telnet or console. tmnxsshuserloginmaxattempts trap is generated when a user failed to authenticate in more than permitted number of retires through SSH. Generation of the trap can be suppressed, if need be, using the config>log> event-control command. By default, the device will generate the trap whenever the event is raised. The trap will carry information about the user ID, source IP address of the client used for the login attempt 4.0R2 The following items describe enhancements added to 4.0 R2 of the 7210 SAS-E OS. DOWN MEP SCALING In 7210 SAS-E, using the command send-ais-on-port-down, users can enable AIS messages to be sent out of client MEP when a failure is detected on the port on which the server MEP (Down MEP) is configured. This allows for notification of failure associated with the server MEP without use of CFM CCM messages. With this feature turned on, AIS messages are sent out of access or access-uplink SAPs at the configured level to peer devices, when the system detects port failure. The peer devices are expected to take appropriate action on receiving the AIS message. In release 4.0R2, to allow for higher scaling of server MEPs (Down MEP) in conjunction with use of send-ais-on-port-down, MEPs can be created using pre-defined levels 0, 1, 3, and 7. When using this capability, it is recommended to disable CFM CCM messages on all the MEPs in use. Additionally, users must exercise care to limit the number of AIS messages that the system generates. The number of AIS messages generated per given interval is directly proportional to the number of services with send-ais-on-port-down feature turned on in the system, the number of client MEPs configured in each of the service (that is, the numbers of SAPs in the services), and the number of levels that the AIS messages need to be sent out on. TRAP GENERATION WHEN FILE LIMIT THRESHOLD IS CROSSED From release 4.0R2, a warning message is displayed on the console and trap (tmnxrootdirfull) is generated if the number of files and directories in the root directory crosses the threshold limit of 80. Warning will be generated for every new file or directory created after threshold limit is exceeded. This limit is applicable only for files and directories created in the root directory on cf1:\. There is no restriction on the number of files and directories created in the sub-directory. The number of files in the root directory might also increment by issuing the command admin save or bof save. When this event is displayed it is expected that the user will cleanup the root directory and remove unnecessary files and directories or move them to a sub-directory created under the root-directory to ensure that the number of entries (files or directories) in the root directory is below the limit. No warning is generated when the number of files and directories comes down below the threshold Alcatel-Lucent Page 21

22 FORWARD/DROP COUNT FOR SAP METER STATS From release 4.0 R2, 7210 SAS-E supports forward and drop count for sap meter stats. In previous releases, Sap per Meter stats displayed packets and octets count "For.InProf" and "For.OutProf". From 4.0R1 supports Sap per Meter stats "Total Forwarded" and "Total Dropped", packets and octets count per sap. By default InProf/OutProf counts are displayed, for displaying Forwarded/Dropped count "sap>statistics>ingress>counter-mode"should be configured to "forward-drop-count". If the counter mode is specified as "forward-drop-count", one counter counts the forwarded packets and octets received on ingress of a SAP meter and another counts the dropped packets. The forwarded count is the sum of in-profile and out-of-profile packets/octets received on SAP ingress. The dropped count is count of packets/octets dropped by the policier. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policier if it exceeds the configured PIR rate. The InProf count and OutProf count is not individually available when operating in forward-drop-count mode. It is supported in VPLS, Epipe SAPs. For more details please refer the 7210 Services user guide. 4.0R2 release also supports display of sap based "Ingress Drop Stats". Software calculates and displays "Ingress Drop Stats" based on values obtained from sap "Ingress Stats" and meter's InProf/OutProf or Forwarded/Dropped. sap "Ingress Drop Stats" is not included in the accounting records. 4.0R1 The following items describe enhancements added to 4.0 R1 of the 7210 SAS-E OS. IP MTU SUPPORT ON IES INTERFACES This feature allows the user to set the IP MTU to use for an IES IP interface. IP MTU ensures that the IP packets sent out of the IP interface are less than the IP MTU specified. Users configure IES IP interface on access-uplink ports for in-band management of the node. With this feature operator can specify the IP MTU to use for CPU generated IP packets (e.g. SNMP, FTP, etc.), making it possible to use different MTU (possibly smaller MTU value than the port MTU) for management traffic and service traffic that share the same port. It is available for use on 7210 SAS-E, 7210 SAS-D and 7210 SAS-M (access-uplink mode only). CONFIGURABLE PERIOD FOR WRITING ACCOUNTING RECORDS TO FLASH With this enhancement, users have an option to configure the collection-interval for different accounting records supported in The collection-interval determines how frequently the system polls for counters to generate accounting records that are written to flash. Users can configure values other than the default value based on the how frequently they need to gather performance statistics for different service entities. Use of bigger value for collection-interval, can reduce the number of writes and frequency of writes to the flash. It is available on all 7210 platforms. ENABLE/DISABLE OF MANAGEMENT / CONSOLE PORTS In release 4.0, 7210 devices support the capability to disable console. In remote deployments, this provides the operator with additional security measure. Operator can disable the use of console to prevent access to the box by a malicious user. Use of console access is not available only when the Timos image is booted. It is always available for use when the bootloader image is executing. Page 22 Alcatel-Lucent

23 It is available on all 7210 platforms. STORING OF SAA RESULTS IN FLASH OAM SAA test results can be saved in a file on the compact flash card, and the standard available file policy can be used to define how long the file is open/closed when 5620 SAM is informed to retrieve the file, similar to how accounting works. SAA TCAs and ad-hoc (nonscheduled/non-cron) results are sent as usual. Once the OAM SAA test results are put on the compact flash card and the file is closed, a trap is sent to the SNMP trap receiver that may then opt to obtain the file and process it as desired. This feature is available on 7210 platforms. BOF PASSWORD RECOVERY From release 4.0 onwards, the default BOF password can be modified by the user. To edit the BOF parameters, user needs to provide the correct password. If the user forgets the password and fails to provide a correct password after three attempts, the system prompts the user to reset the BOF password to factory default. As a security measure, to prevent a malicious user from using it to gain access to the configuration files, when the password is reset to default, the system also resets the flash to factory defaults (i.e. it removes all the files from the flash except for the boot image file (cf1:\boot.tim) and Timos image file (cf1:\both.tim)) and reboots the node with the factory default settings. The node is rebooted after the password is reset, to boot up with the factory default settings. After bootup, the user needs to setup the box using the same steps as used to boot the box the first time when it was received from the factory. User can use the factory default password password to edit the BOF parameters after the bootup subsequent to reboot and choose to change the password again. NOTE: It is highly recommended that user does not rename cf1:\boot.tim and cf1:\both.tim, if the system needs to retain them during the password recovery procedure. Additionally, it is highly recommended that the user takes a backup of all the image files, configuration files and other data. COMPATIBLE BOOT LOADER In prior releases, due to incompatible bootrom and bootloader, certain versions of bootrom did not load certain versions of the bootloader, resulting in a boot loop, which would mean a RMA of the affected device. The bootloader version (that is, boot.tim) supplied with release 4.0, is compatible with all previous versions of bootrom. It is recommended to perform a upgrade of the bootloader to latest version supplied with release 4.0 image 3.0R1 The following items describe enhancements added to 3.0 R1 of the 7210 SAS-E OS. RSTP FORWARDING IN HARDWARE This enhancement is available from 2.0R1 release. RSTP packets with one or more tags received on a null SAP or RSTP packets received with two or more tags on a Dot1q SAP or RSTP packets received with three or more tags on a QinQ SAP are forwarded in hardware. In prior releases, forwarding of such RSTP packets was done in software. Note that RSTP packets with null tag received on a null SAP or RSTP packets received with a single on Dot1q SAP or RSTP packets received with two tags on a QinQ SAP are processed locally, if STP is enabled. Alcatel-Lucent Page 23