7210-SAS E OS 6.0R3 SOFTWARE RELEASE NOTES

Transcription

1 7210-SAS E OS 6.0R3 AUGUST 31, SAS E OS 6.0R3 SOFTWARE NOTES These release notes are for Release 6.0R3 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 9 New Features on page 20 Enhancements on page 31 Known Limitations on page 41 Known Issues on page 46 * V6.0.R3* Alcatel-Lucent Page V6.0.R3

2 SOFTWARE UPGRADE PROCEDURES The following sections contain information for upgrading to the 6.0R3 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:\6.0r3 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. Step 5. Step 6. Note: 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. When upgrading to Release 6.0R3, 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. 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. After upgrade to 4.0 or later 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. Alcatel-Lucent Page 3

4 UPGRADE FROM PRIOR S UPGRADE TO 5.0R3 FROM PRIOR S FILTERS In release 5.0R3, the ACL TCAM allocation scheme has been modified to accomodate support for IPv6 classification. As a part of this change, software allocates only one (1) additional entry for every chunk of resources allocated for use of ACLs. In previous releases configuration if all ACL entries are used up, it is recommended to modify config file such that IP or MAC ACL entries configured are multiple of 255. This change is required if all the TCAM entries are used up, irrespective of IPv6 classification. For example: If 768 entries of MAC ACL configured, delete 3 MAC ACL entries before upgrade to 5.0R3. If 512 entries of IP ACL configured, delete 2 IP ACL entries before upgrade to 5.0R3. UPGRADE TO 5.0R1 FROM PRIOR S ACCOUNTING RECORD NUMBERS In 5.0R1 release following accounting numbers are modified, new numbers are shown in ( ) netinfingressoct(52), netinfingresspkt(53), combinednetinfingress(54), accessegresspkt(55), accessegressoct(56), combinedaccessegress(57), combinednetegress(58), combinedsvcegress(59), combinedsvcinegpkt(60), combinednetinegpkt(61) NON SUPPORTED CLI In previous releases 7210 SAS was allowing to configure non supported feature CLI's. In 5.0R1 some of the non supported CLI's are removed. In previous releases if user had configured non supported feature CLI, configuration will error out during upgrade to 5.0R1 release. It is recommended to check for non supported CLI by loading config file with 5.0R1 and remove non supported CLI s from config file before final upgrade. TACACS+ From 5.0R1 tacacs+ "single-connection" option is deprecated. During upgrade following warning message displayed WARNING: CLI Line:xx "single-connection" This command has been deprecated. SPLIT HORIZON GROUP NAME During upgrade to 5.0R1, if "split-horizon-group <group-name>" CLI, where <group-name> configured with name having spaces, config file execution will error out during upgrade. Workaround is to edit the config file before upgrading to ensure split horizon group names are with double quotes or no space(s) in the group name. Page 4 Alcatel-Lucent

5 LOGGING In 5.0, as part of log-id config (configure>log>log-id <num>) needs to have from change. This is necessary for the box to generate config change logger/trap messages, modify configuration file accordingly. UPGRADE TO 4.0R4 OR LATER FROM PRIOR S SAP INGRESS QOS 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. 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 The following router-name parameter was supported: CLI Syntax: config>router router-name The parameter values acceptable for router-name were Base and management. 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 exit Both lines must be removed. Alcatel-Lucent Page 5

6 PRIOR TO 1.1R3 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 exit exit 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: Prior to 2.0R5 release: config>service>vpls$ mfib-table-size table-size 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 Page 6 Alcatel-Lucent

7 to file 5 no shutdown exit accounting-policy 6 shutdown record service-ingress-packets to file 6 exit *A:STU>config>service>vpls>sap# info statistics egress exit ingress counter-mode packet exit exit collect-stats accounting-policy Modifications required in configurations before upgrade *A:STU>config>service>vpls>sap# info statistics egress exit ingress counter-mode packet exit exit 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 to file 5 exit accounting-policy 6 record service-ingress-packets default to file 6 no shutdown exit *A:STU>config>service>vpls>sap# info Alcatel-Lucent Page 7

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

9 RESOLVED ISSUES R6.0R3 The following are specific technical issues that have been resolved in Release 6.0R3 of SAS E OS. In previous release of 7210 SAS 6.0, an option to enable relaying of plain bootp messages in DHCP relay for IES/VPRN/RVPLS service was not available. This issue is resolved in 7210 SAS 6.0R3 release. [ MI] For MVR user, VPLS SAP Egress SAP stats were not incremented when multicast data traffic was egressing. This issue is resolved in 7210 SAS 5.0 release. [136684] R6.0R2 The following are specific technical issues that have been resolved in Release 6.0R2 of SAS E OS. Extra VLAN tags get added to the data traffic egressing out of the dot1q-preserve service sap, if on the same port, dot1q mirror destination SAPs exists. [ MA] In release 5.0, the ARP resolution fails, if source MAC of ARP response packet received contains 4th byte as "0x59" or 0x06 (For example, 4c:5f:d2:59:0f:52). This issue is resolved. [ MA] An entry in the output of "show system lldp neighbor" will incorrectly show the System Name with additional characters, if the System Name of the previous entry is longer [ MI] Static route /0 configured in bof.cfg was not working. This issue is resolved. [ MI] In previous release, SNMP allowed to configure unsupported CLI "default-action nextpolicy" under policy-statement. This causes the configuration to display an error message on reboot or upgrade. From 5.0R7, using SNMP "default-action next-policy" is not allowed to configure. [ MI] An asterisk ( * ), indicating an unsaved configuration change, is now correctly displayed after changing some of the parameters in the configure>system and configure>log contexts, among others. Additionally, the Change Since Last Save field in the show system information output now updates properly. [61271] In previous releases, CLI show output and MIB query incorrectly shows service-mtu value for VPLS/Epipe service. In release 6.0R2 "servicemtu" value is displayed as NA [ MI] Egress mirroring stops for a port lag after source port lag is shut and no shut only with Epipe service, this issue is resolved in 6.0. [ MI] R5.0R7 The following are specific technical issues that have been resolved in Release 5.0R7 of SAS E OS. Extra VLAN tags get added to the data traffic egressing out of the dot1q-preserve service sap, if on the same port, dot1q mirror destination SAPs exists. [ MA] Alcatel-Lucent Page 9

10 In release 5.0, the ARP resolution fails, if source MAC of ARP response packet received contains 4th byte as "0x59" or 0x06 (For example, 4c:5f:d2:59:0f:52). This issue is resolved. [ MA] An entry in the output of "show system lldp neighbor" will incorrectly show the System Name with additional characters, if the System Name of the previous entry is longer [ MI] Static route /0 configured in bof.cfg was not working. This issue is resolved. [ MI] In previous release, SNMP allowed to configure unsupported CLI "default-action nextpolicy" under policy-statement. This causes the configuration to display an error message on reboot or upgrade. From 5.0R7, using SNMP "default-action next-policy" is not allowed to configure. [ MI] An asterisk ( * ), indicating an unsaved configuration change, is now correctly displayed after changing some of the parameters in the configure>system and configure>log contexts, among others. Additionally, the Change Since Last Save field in the show system information output now updates properly. [61271] R5.0R6 There are no specific technical issues that have been resolved in Release 5.0R6 of SAS E OS. R5.0R5 The following are specific technical issues that have been resolved in Release 5.0R5 of SAS E OS. L2 packet of type was dropped, when the payload starts with 0x8809.This has been resolved. On a system, with number of ports are part of split horizon group, in random cases STP packet received on root port which is not part of split horizon group did not get forwarded out of a one of the split horizon port. This resulted in RSTP convergence issue. This has been resolved. [155629] From release 5.0R5, Cmplx #1 output in "tools dump system-resources" command is not displayed. [156040] Earlier versions of 7210 SAS-E Release Notes section " 4.0R1 Enhancements", mentioned that "IP MTU SUPPORT ON IES INTERFACES" is supported. In this version of release notes, it is modified as ""IP MTU SUPPORT for IES interface (per port configuration)". R5.0R4 The following are specific technical issues that have been resolved in Release 5.0R4 of SAS E OS. When using the TACACS+ server for authorization commands could be authorized in certain cases when they should be blocked. This issue has been resolved. [153403] Page 10 Alcatel-Lucent

11 In previous 5.0 releases, when snmpbulk request was made on IPv6FilterEntry or IPv6FilterParamsEntry, node returned No_Such_Name as error status in the response PDU. This issue is resolved in 5.0R4. [147459] 7210 SAS-E from release 5.0R2, if "file-id" location parameter is configured as "no location"(default value), accounting-policy operationally stays down and accounting records were not written to cf1 by default. User was required to configure proper location as cf1 or uf1 for writing accounting records. This issue is corrected in release 5.0R4 so that if "no location" (default value) configured for "file-id", by default accounting records are written to cf1. [154637] R5.0R3 The following are specific technical issues that have been resolved in Release 5.0R3 of SAS E OS node drops ETH-VSM PDU s if received ETH-VSM PDU is of same or lesser level of the configured MEP, whereas higher level ETH-VSM PDU s are transparently forwarded. System instability issue when attempting to change the password of a TACACS user when the user s password expires is resolved from 5.0R1 release. [152166] R5.0R2 The following are specific technical issues that have been resolved in Release 5.0R2 of SAS E OS. When mirror sap is q.*, egress sap stats of mirror sap were not incrementing, this issue resolved in 5.0R2. [147032] If "split-horizon-group <group-name>" CLI, where <group-name> configured with name having a space at the beginning (or) end (or) more than one contiguous space in port split horizon group name, config file execution will error out during upgrade. Cases of split horizon group name containing single space (can appear multiple times separated by a character) is resolved in release 5.0R2. In case of previous release, workaround is to edit the config file before upgrading to ensure split horizon group names are with double quotes or no space(s) in the group name. [142324] Node lost management and console access when node receives malformed Tacacs authresponse. Issue is resolved in 5.0R2. [148054] In previous releases, when igmp snooping was enabled, learned multicast traffic classified to unicast meter instead of multicast meter. This issue got resolved in 7210 SAS-E 5.0R2 release. [149972] R5.0R1 The following are specific technical issues that have been resolved in Release 5.0R1 of SAS E OS. From Release 5.0R1 "show card detail" displays "Last bootup reason". If 7210 SAS is power cycled "Last bootup reason" displayed as "power cycle", for any other reason, "Last bootup reason" displayed as "hard boot". [101378] Alcatel-Lucent Page 11

12 From release 5.0R1 config load fails if there is mimatch in config and index file, following message displayed on console: MINOR: SVCMGR #2093 Mismatch in Index file and Config File In such case, deleting index file and re-loading will load config file. [142700] R4.0R7 The following are specific technical issues that have been resolved in Release 4.0_R7 of SAS E OS. In the previous 7210 SAS 4.0 releases, when the power is off, the "critical" LED glows. In the current release, when the power is off, the "critical" LED turns off and "Major" LED turns on. [139218] R4.0R6 The following are specific technical issues that have been resolved in Release 4.0_R6 of SAS E OS. In 7210 SAS 4.0R6, a fix is provided to prevent the high CPU issue, if the inserted Copper SFP is faulty (PHY read fail). An error message is displayed, if SFP read fails. [130324] In previous releases, when the ingress statistics mode of a SAP is set to forward-dropcount, in the output of the command monitor service id <> sap <> rate" the values shown against "For. InProf" and "For. OutProf". In 7210 SAS 4.0R6, this issue is resolved and the values are shown against "Total Forwarded" and "Total Dropped". [134878] The system reboots automatically after 500 days of uptime due to wrapping of internal counter which was resolved in 7210 SAS 4.0R1. [135164] 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] Page 12 Alcatel-Lucent

13 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. 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] Alcatel-Lucent Page 13

14 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 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. Page 14 Alcatel-Lucent

15 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] 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] Alcatel-Lucent Page 15

16 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] 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] Page 16 Alcatel-Lucent

17 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] 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] Alcatel-Lucent Page 17

18 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] 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] Page 18 Alcatel-Lucent

19 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] 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] Alcatel-Lucent Page 19

20 NEW FEATURES 6.0R3 There are no new features added to 6.0 R3 of the 7210 SAS-E OS. 6.0R2 The following items describe features added to 6.0 R2 of the 7210 SAS-E OS. DHCP SNOOPING AND RELAY Platforms Supported: 7210 SAS-D, 7210 SAS-M (in both access-uplink and network mode), 7210 SAS-X and 7210 SAS-E. With release 6.0R2, 7210 SAS supports DHCP snooping in a VPLS service and DHCP relay for L3 services (that is, RVPLS, IES and VPRN services). DHCP snooping and DHCP relay supports insertion of option-82. DHCP relay also takes care of forwarding the DHCP requests to the configured DHCP server. In residential networks, client devices (such as a routed home gateway) uses Dynamic Host Configuration Protocol (DHCP) to dynamically obtain their IP address and other network configuration information. Additionally, 7210 autoinit procedure uses DHCP to dynamically obtain the BOF file used for first-time booting of the system (along with IP address required to retrieve the BOF file, the configuration file and the Timos software image from the network). The option-82 insertion functionality provided by DHCP relay and snooping, allows the operator to identify the DHCP client and to trust the DHCP request, so that the operators DHCP server can assign appropriate IP address and other parameters needed for operation of the client device. NOTE: DHCP relay for RVPLS services is supported on 7210 SAS-D and 7210 SAS-M in accessuplink mode. DHCP relay for VPRN services is supported on 7210 SAS-M network mode and 7210 SAS-X. DHCP relay for IES services is supported on 7210 SAS-D, 7210 SAS-M (both accessuplink mode and network mode) and 7210 SAS-X. DHCP snooping for VPLS services is supported on 7210 SAS-D, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-X. Some of the restrictions that apply to the feature are: DHCP relay and snooping is supported only for SAPs on access ports and hybrid ports. DHCP snooping is not supported on SDPs in 7210 SAS-M and 7210 SAS-X network mode. DHCP relay is supported for IES service in a RVPLS service and DHCP snooping is not supported for SAPs in an RVPLS service. DHCP snooping is not supported for PBB services. Plain Bootp messages are forwarded without any modification in a VPLS service, even if DHCP snooping is enabled. Page 20 Alcatel-Lucent

21 Plain Bootp messages are not processed by 7210 and dropped in IES and VPRN services. For more information, see 7210 SAS-D, 7210 SAS-M and 7210 SAS-X Services User Guides. QOS POLICY OVERRIDE In release 6.0R2, 7210 SAS-E platforms support QoS policy override commands for SAP ingress QoS policy. This feature allows users to use few SAP ingress policy templates and modify specific parameters per SAP, if required. User can override the following SAP ingress meter parameters - CIR, PIR, CBS, and MBS; on all the supported platforms. For more information, see 7210 SAS-E Quality of Service User Guides. SSH WITH IPV6 In release 6.0R2, SSH command used for remote management of the node securely, is available with IPv6 on 7210 SAS-E. For more information, see 7210 SAS-E System Management User Guides. 5.0R7 There are no new features added to 5.0 R7 of the 7210 SAS-E OS. 5.0R6 There are no new features added to 5.0 R6 of the 7210 SAS-E OS. 5.0R5 The following items describe features added to 5.0 R5 of the 7210 SAS-E OS VWM CWDM MANAGEMENT Platforms Supported: 7210 SAS-E, SAS-M, and SAS-X 1830 VWM CWDM Passive Optical device can be used in point-to-point or ring deployments to multiplex multiple CWDM channels over a single fiber. This allows the operator to either reuse existing fiber or use a single fiber to meet the requirements for ever increasing demand for service bandwidth. Up to 8 fixed CWDM channels can be multiplexed over single fiber using this unit. From 5.0R5 release, 7210 SAS-E, 7210 SAS-M and 7210 SAS-X platforms, support management of the 1830 VWM flexible CWDM clip-on device. It supports retrieving inventory management (For example: Part numbers, manufacturing dates, firmware revision and others) information from the clip-on device and displaying it using the show commands VWM clip-on device can be connected to the 7210 platform using the USB interface. Only one 1830 VWM CWDM clip-on device can be connected to the USB interface on 7210 SASE, 7210 SAS-M and 7210 SAS-X. Each of these clip-on devices is identified using the shelf-id set using the rotary dial provided on the device. To aid inventory management, user must configure the vwm-shelf-id of the clip-on device attached to the USB interface using the 7210 configuration commands. The vwm-shelf-id must match the shelf ID set using the rotary dial on the clip-on device uses the configured vwm-shelf-id to communicate with the clip-on Alcatel-Lucent Page 21

22 device. If these shelf IDs do not match, 7210 will not communicate to the device and does not provide any information about the device cannot detect a mismatch between the configured vwm-shelf-id and the shelf ID set on the rotary dial raises an event or log to alert user about possible mismatch in configuration of shelf IDs when it is unable to communicate with the configured vwm-shelf-id. For more information, see 7210 SAS-MX and 7210 SAS-DE Basic System Configuration Guide. Note: The vwm-shlef controller should be inserted on to optical shelf bay prior to powering the controller through USB cable. Should not remove or insert vwm-shelf-controller on to shelf bay while USB power is connected. Removing and inserting vwm-shelf- line cards without powering down controller may show Amber LED on line cards. While vwm-shelf is equipped with vwm-controller and its Line cards, powering the shelf using USB port, vwm-shelf takes around 10secs to get ready. 5.0R VWM CWDM MANAGEMENT (BETA ONLY) The following items describe features added to 5.0 R4 of the 7210 SAS-E OS. Platforms Supported: 7210 SAS-E, SAS-M, SAS-X 1830 VWM CWDM Passive Optical device can be used in point-to-point or ring deployments to multiplex multiple CWDM channels over a single fiber. This allows operator to either reuse existing fiber or use a single fiber to meet the requirements for ever increasing demand for service bandwidth. Up to 8 fixed CWDM channels can be multiplexed over single fiber using this unit. From 5.0R4 release, 7210 SAS-E, 7210 SAS-M and 7210 SAS-X platforms, support management of the 1830 VWM flexible CWDM clip-on device. It supports retrieving inventory management (For example: Part numbers, manufacturing dates, firmware revision and others) information from the clip-on device and displaying it using the show commands VWM clip-on device can be connected to the 7210 platform using the USB interface. Only one 1830 VWM CWDM clip-on device can be connected to the USB interface on 7210 SAS- E, 7210 SAS-M and 7210 SAS-X. Each of these clip-on devices is identified using the shelf-id set using the rotary dial provided on the device. To aid inventory management, user must configure the vwm-shelf-id of the clip-on device attached to the USB interface using the 7210 configuration commands. The vwm-shelf-id must match the shelf ID set using the rotary dial on the clip-on device will use the configured vwm-shelf-id to communicate with the clip-on device. If these shelf IDs do not match, 7210 will not communicate to the device and will not provide any information about the device cannot detect a mismatch between the configured vwm-shelf-id and the shelf ID set on the rotary dial will raise an event or log to alert user about possible mismatch in configuration of shelf IDs when it is unable to communicate with the configured vwm-shelf-id. For more information, see 7210 SAS-MX and 7210 SAS-DE Basic System Configuration Guide. Page 22 Alcatel-Lucent

23 5.0R3 The following items describe features added to 5.0 R3 of the 7210 SAS-E OS. IPV6 ACLS From 7210 SAS 5.0R3, support is available for IPv6 ACLs on SAP ingress on 7210 SAS-E. IPv6 ACLs is supported on SAP ingress in Epipe and VPLS service is implemented in the hardware and can process packets at line-rate. IPv6 ACLs allows the operators to match on the IPv6 header fields and implement security policies. The 7210 operators typically use in-band management since most of the devices are in remote installations. With support for IPv6 OOB management available on 7210 operators who prefer to use IPv6 in-band management can use an external loop and transport the IPv6 OOB management traffic using a Epipe or a VPLS service. In such a scenario, operators can use ACLs to match on IPv6 packet header fields and restrict management access of the node to a list of trusted remote peers. Note: In release 5.0R3 the ACL tcam allocation scheme has changed and user needs to take action during upgrade, refer "Upgrade from prior releases" section of this document. Before using the IPv6 ACLs, the users need to configure appropriate amount of resources using the CLI commands under "config> system> resource-profile". The number of resources available when 64-bit IPv6 addresses and 128-bit IPv6 addresses are used as the match criteria is different. For more information, see the 7210 SAS-E Router Configuration Guide for IPv6 match criteria supported and the 7210 SAS-E Basic Systems Configuration guide for use of the resource-profile CLI commands. 5.0R2 The following items describe features added to 5.0 R2 of the 7210 SAS-E OS. SUPPORT USB STORAGE Platforms Supported: 7210 SAS-E, and 7210 SAS-M. From 5.0R2 release 7210 SAS-M and E platforms support USB interface which provides storage functionality. It supports USB version 1.1. It allows the use of USB sticks providing them an alternate storage location with larger capacity than the internal flash. The USB storage device is identified as uf1: by the system and supports DOS file system similar to internal compact file system. The USB storage device can be used to store Timos images, configuration files, accounting records, and log files. The BOF file can point to images on USB and be used to load Timos images and configuration files. During bootup, the system USB storage cannot be used to load boot.tim (that is, the bootloader). Hence, the bootloader required to boot the device must not be stored on the USB (uf1). Following USB models from Sandisk are supported: Cruzer Fit size 4GB and 8GB Cruzer Blade size 4GB and 8GB For more information, see the 7210 SAS-M,E Basic System Configuration User Guide. Alcatel-Lucent Page 23

24 5.0R1 The following items describe features added to 5.0 R1 of the 7210 SAS-E OS. MULTICAST VLAN REGISTRATION (MVR) Platforms Supported: 7210 SAS-E, 7210 SAS-D, 7210 SAS-X and 7210 SAS-M in accessuplink mode only Multicast VLAN registration (MVR), allows operators to use a single network wide multicast VLAN (or a VPLS service) to deliver multicast traffic in the aggregation and access network and distribute the multicast traffic to subscribers using the VLANs specific to the subscribers. Use of single multicast VLAN saves bandwidth and eases operations. MVR must be used in conjunction with IGMP snooping. It uses the IGMP join and leave messages to determine the subscribers who are interested to receive a particular multicast stream. NOTE: In this release, support for MVR has been included for 7210 SAS-M access-uplink node. Support for MVR on 7210 SAS-M network mode is already available from prior releases. Please check the 7210 SAS-D,E Services user guide, 7210 SAS-M Services user guide and 7210 SAS-X Services guide for more information. IPV4/IPV6 SAP INGRESS QOS CLASSIFICATION Platforms Supported: 7210 SAS-D, 7210 SAS-E, 7210 SAS-X and 7210 SAS-M (both network and access-uplink mode) With this release, IPv4 and IPv6 classification criteria is supported for SAP ingress QoS classification. With this release, support for IPv4 criteria has been extended to include IPv4 source address, IPv4 destination address, TCP/UDP source and destination port numbers and IP protocol. IPv6 classification entries can use IPv6 source address, IPv6 destination address, TCP/UDP source and destination port numbers, IPv6 next header field and IPv6 DSCP. More details of support of IPv4 and IPv6 classification criteria is available in the 7210 SAS-D,E, 7210 SAS-M and 7210 SAS-D QoS user guide, along with information about resource usage for different match criteria. NOTE: Before using SAP ingress QoS IPv6 classification criteria, users need to configure appropriate amount of resources using the CLI commands under "config> system> resourceprofile>ingress-internal-tcam> qos-sap-ingress". Please read the 7210 SAS-D,E and 7210 SAS-M,X Basic System Configuration guide for more information on use of the resource-profile CLI commands. DOT1Q MIRROR DESTINATION Platforms Supported: 7210 SAS-E, 7210 SAS-D, 7210 SAS-X and 7210 SAS-M in both access-uplink and network mode In prior releases, 7210 devices supported only local mirroring with the capability to use a NULL SAP as the mirror destination. With this release, support has been added for using a dot1q SAP or a Q1.* SAP as a mirror destination. This allows for sharing of a common uplink port to transport both mirrored traffic and service traffic. QoS policies can be specified for mirrored traffic so that users can apply appropriate policies for both service traffic and mirrored traffic. Page 24 Alcatel-Lucent

25 On 7210 SAS-E, 7210 SAS-M and 7210 SAS-X, before using a Dot1q SAP or Q1.* SAP as a mirror destination, the user must dedicate the resources of front-panel port for use with this feature using the command config> system> loopback-no-svc-port. No services can be configured on this port. On 7210 SAS-D, the software uses the resources associated with an internal port for mirror application. Please read the 7210 SAS-D,E and 7210 SAS-M,X OAM and Diagnostics User guide and Interfaces User Guide for more information. 4.0R7 There are no new features added to 4.0 R7 of the 7210 SAS-E OS. 4.0R6 The following items describe features added to 4.0 R6 of the 7210 SAS-E OS. SYNTHETIC LOSS MEASUREMENT (SLM) Synthetic loss measurement provides a mechanism for operators to proactively trend packet loss for service based MEPs. The standards specify a single-ended mechanism that allows the operator to run on-demand and proactive tests to determine in, out loss and unacknowledged packets. This approach can be used between peer MEPs in both point to point and multipoint services. Only remote MEP peers within the association and matching the uni-cast destination responds to the SLM packet. Both on-demand and SAA support is available. Note: The 7210 SAS uses pre-standard OpCodes 54 (Synthetic Loss Reply) and 55 (Synthetic Loss Message) for the purpose of measuring loss using synthetic packets. SLM is supported on all 7210 SAS platforms. SLM uses hardware-based Rx timestamp and software-based Tx timestamp on 7210 SAS-D, 7210 SAS-M (access-uplink and network mode), and 7210 SAS-X. The 7210 SAS-E uses software-based Rx and Tx timestamp. 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. Alcatel-Lucent Page 25