7210-SAS E OS 5.0R1 SOFTWARE RELEASE NOTES

Transcription

1 7210-SAS E OS 5.0R1 OCTOBER 15, SAS E OS 5.0R1 SOFTWARE NOTES These release notes are for Release 5.0R1 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 17 Enhancements on page 24 Known Limitations on page 32 Known Issues on page 35 * V5.0.R1* Alcatel-Lucent Page V5.0.R1

2 SOFTWARE UPGRADE PROCEDURES The following sections contain information for upgrading to the 5.0R1 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:\5.0r1 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 5.0R1, 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 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.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. 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. Page 4 Alcatel-Lucent

5 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 Both lines must be removed. 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 config>router>policy-options# Alcatel-Lucent Page 5

6 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 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 Page 6 Alcatel-Lucent

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

8 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 8 Alcatel-Lucent

9 RESOLVED ISSUES 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] 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] Alcatel-Lucent Page 9

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

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

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

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

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

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

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

17 NEW FEATURES 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. Alcatel-Lucent Page 17

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

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

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

21 3.0R3 SUPPORT FOR DOT1Q EXPLICIT NULL SAP The following items describe features added to 3.0 R3 of the 7210 SAS-E OS. 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 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. Alcatel-Lucent Page 21

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

23 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 23

24 ENHANCEMENTS 5.0R1 The following item describe enhancements added to 5.0 R1 of the 7210 SAS-E OS. SUPPORT MEMORY CACHE FOR ACCOUNTING LOGS Platforms Supported: 7210 SAS-E, 7210 SAS-D, 7210 SAS-X and 7210 SAS-M With this release, if user specifies use of memory cache (configured using the command configure> log> accounting-policy> log-memory), software allocates some RAM (that is,volatile memory) as a temporary storage to write accounting records. The software writes to this memory cache every collection-interval, instead of writing directly to the flash. The accounting records are moved from the temporary storage to the specified file on non-volatile memory (that is, flash) when either the rollover period expires or when temporary storage location is full. This can potentially help users to extend the lifetime of the internal flash. Please read the 7210 SAS-DE and 7210 SAS-MX Systems Management User Guide for more information. LLDP TUNNELING Platforms Supported: 7210 SAS-E, 7210 SAS-D, 7210 SAS-X and 7210 SAS-M With this enhancement tunneling of LLDP frames that use the nearest-bridge-dest-mac as destination MAC address is supported. When tunneling is enabled, using the command tunnelnearest-bridge-dest-mac, all frames received with the matching LLDP destination mac address are forwarded transparently to the remote end of the service. To forward these frames transparently, the port on which tunneling is enabled must be configured with NULL SAP and the NULL SAP must be configured in an Epipe service. Tunneling is not supported for any other port encapsulation or when using any other service. Additionally, before enabling LLDP tunneling, admin status for LLDP dest-mac nearest-bridge must be set to disabled or Tx only, using the command admin-status available under configure> port> ethernet> lldp> destmac nearest-bridge. If admin-status for dest-mac nearest-bridge is set to receive and process nearestbridge LLDPDUs (that is, if either rx or tx-rx is set) then it overrides the tunnel-nearest-bridgedest-mac command. NOTE: Transparent forwarding of LLDP frames can be achieved using the standard defined mechanism when using either nearest-non-tmpr or the nearest-customer as the destination MAC address in the LLDP frames. It is recommended that the customers use these MAC address where it is possible to conform to standards. This command allows legacy LLDP implementations that do not support these additional destinations MAC addresses to tunnel LLDP frames that use the nearest-bridge destination MAC address. IPV6 MANAGEMENT ACCESS FILTER (MAF) Release 5.0R1 supports configuring IPv6 MAF. Using "configure>system>security>management-access-filter >ipv6-filter" CLI IPv6 MAF can be configured. IPv6 MAF ACL can be used implement security policies for IPv6 traffic designed to CPU from In-band or Out of band management ports. SNMPENGINEBOOTS Platforms Supported: 7210 SAS-E, 7210 SAS-D, 7210 SAS-X and 7210 SAS-M Page 24 Alcatel-Lucent

25 Prior to this enhancement the value of snmpengineboots (in the SNMP-FRAMEWORK- MIB.mib and described in RFC3414) was always reset to a value of 1 after a full system reboot instead of incremented by 1 as specified in RFC3414. With this enhancement, the value of snmpengineboots is incremented by one after a system reboot or an snmp engineid change. If snmpengineboots reaches its maximum value ( ) it will no longer increment and remains at that value until the operator performs manual intervention by changing the snmp engineid. The value of snmpengineboots is saved in a file on the compact flash called nvsys.info. 4.0R7 There are no new enhancements added to 4.0 R7 of the 7210 SAS-E OS. 4.0R6 There are no new enhancements added to 4.0 R6 of the 7210 SAS-E OS. 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. Alcatel-Lucent Page 25