Alcatel-Lucent. Service Access Switch Release 6.0 Rev S A S - D O S S o f t w a r e R e l e a s e N o t e s

Transcription

1 Alcatel-Lucent Service Access Switch Release 6.0 Rev S A S - D O S S o f t w a r e R e l e a s e N o t e s V6.0.R V6.0.R5 Alcatel-Lucent Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright 2014 Alcatel-Lucent. All rights reserved.

2 Table of Contents Table of Contents Upgrade from prior releases Upgrade to 5.0R1 from prior releases Upgrade to 4.0R4 or later from prior releases Resolved Issues Resolved in R4.0R Resolved in R4.0R Resolved in R4.0R Resolved in R4.0R Resolved in R4.0R Resolved in R4.0R Resolved in R4.0R Resolved in R3.0R Resolved in R3.0R New Features Release 6.0R Release 6.0R Release 6.0R Release 6.0R Release 6.0R Release 5.0R Release 5.0R Release 5.0R Release 5.0R Release 5.0R Release 5.0R Release 4.0R Release 4.0R Release 4.0R Release 4.0R Release 4.0R Release 4.0R Release 3.0R Release 3.0R Release 3.0R Enhancements Release 6.0R Release 6.0R Release 6.0R Release 6.0R Release 6.0R Release 5.0R SAS OS Software Release Notes i

3 Table of Contents Release 5.0R Release 5.0R Release 5.0R Release 5.0R Release 5.0R Release 4.0R Release 4.0R Release 4.0R Release 4.0R Release 4.0R Release 4.0R Release 4.0R Known Limitations Known Issues ii 7210 SAS OS Software Release Notes

4 These release notes are for Release 6.0R5 of the 7210-SAS D OS software for 7210 SAS D 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 6 New Features on page 14 Enhancements on page 34 Known Limitations on page 42 Known Issues on page 47 Page 1

5 7210-SAS D OS 6.0R5 Software Release Notes SOFTWARE UPGRADE PROCEDURES The following sections contain information for upgrading to the 6.0R5 software version. In particular, there are sections that describe the following: Standard Software Upgrade Procedure Procedure for performing a standard, service-affecting upgrade. 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 (both.tim) and configuration files, should reverting to the old version of the software be required. Step 2. Copy 7210 SAS D images to cf1: The 7210 SAS D image files both.tim must be copied to the cf1: device on the 7210 SAS D node. Note: The 7210 SAS-D of 64MB flash (part numbers 3HE05676AAAA01, 3HE05676ABAA01, 3HE05677AAAA01, 3HE05677ABAA01 and 3HE06537AAAA01) can accommodate one set of boot.tim and both.tim files, the users are required to overwrite existing files with new files in cf1.with the Enhanced 7210 SAS-D (SAS-D with 128MB flash) supported from 4.0R6, more than one set of boot.tim and both.tim files can be stored on flash. Step 3. 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. Page 2 Alcatel-Lucent

6 7210 SAS-D OS 6.0R5 Software Release Notes 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. 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 6.0R5, execute the admin reboot upgrade command. Note that, executing 'admin reboot upgrade' command system will upgrade the bootrom if required. Allow the boot sequence to complete and verify that the card comes up. Upgrade the Golden BOOT Loader (only if all of the above steps were successful). After successfully booting of the new version of 7210 SAS D 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 (i.e. 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

7 7210-SAS D OS 6.0R5 Software Release Notes 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 or later release, the following warning message displayed can be ignored: Page 4 Alcatel-Lucent

8 7210 SAS-D OS 6.0R5 Software Release Notes 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, "Efficent Allocation of SAP Ingress QoS Resource" 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 or later, 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. Alcatel-Lucent Page 5

9 7210-SAS D OS 6.0R5 Software Release Notes RESOLVED ISSUES NOTE: Issues marked as MI might have had a minor impact but did not disturb network traffic Issues marked as MA might have had a major impact on the network and might have disturbed traffic Issues marked as CR were critical and might have had a significant amount of impact on the network RESOLVED IN R6.0R5 The following are specific technical issues that have been resolved in Release 6.0R5 of the 7210 SAS-D OS. Change in operation state of service entity, that is, SAP or SDP flap, required removal and addition of port loopback configuration for Testhead or loopback functionality to work. This issue is resolved in 7210 SAS 6.0R3 release. [ MA] The state of the Tacacs+ server no longer goes down when the user abruptly terminates the session without logging off. This issue was only observed when tacacs accounting was configured. [ MI] If CPU targeted IP/UDP fragmented packet has 0x0401 value at offset 22, it was dropped in previous releases. If an SNMP request packet is fragmented and matches this, synchronization with SAM can fail. This is resolved in 6.0R5. [ MA] From 6.0R5 release, the "slope-policy" attached to an access-uplink port is reflected under "config->port>access>uplink>egress>pool" even when the "slope-policy" is applied under "config>port->network->egress->pool". RESOLVED IN R6.0R4 The following are specific technical issues that have been resolved in Release 6.0R4 of the 7210 SAS-D OS. When RVPLS receives ARP packets with a mismatch in "src.mac.address", L2 and ARP header, the ARP packets did not get processed in the previous release of 7210-SAS-D. This issue is resolved in 7210 SAS 6.0R4 release. [ MI] In previous releases of 7210 SAS, if the user configured a retention period for accounting records greater than the default value, during a system reboot, the accounting files that has the actual retention period greater than the default retention period were deleted. This issue is resolved in 7210 SAS 6.0R4 release. [ MI] In previous 7210 SAS 6.0 releases, telnet, ftp, ssh, radius, and tacplus were egressing on NC queue. This issue is resolved in 7210 SAS 6.0R4 release and these packets take h1 egress queue. [ MI] In previous releases of 7210 SAS 6.0, the "show port <port-id> optical" output was not displayed. This issue is resolved in 7210 SAS 6.0R4 release. [ MI] Page 6 Alcatel-Lucent

10 7210 SAS-D OS 6.0R5 Software Release Notes RESOLVED IN R6.0R3 The following are specific technical issues that have been resolved in Release 6.0R3 of the 7210 SAS-D 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] In previous releases, 7210 SAS-D with STP configuration, while the root port comes up post operationally down, a transient traffic loop was occuring in some cases. This issue is resolved in 7210 SAS 6.0R3 release. [ MI] In previous release of 7210 SAS 6.0, in 7210 SAS-D, for SAP ingress mirroring, when more than two mirror destinations were configured, console message appears and mirroring was not working for the third and fourth mirror destination. From 7210 SAS 6.0R3 release, CLI allows configurations only for two mirror destination. [157051] RESOLVED IN R6.0R2 The following are specific technical issues that have been resolved in Release 6.0R2 of the 7210 SAS-D OS. If IES SAP or Network IP Interface configured with the VLAN-ID which is in use by VLAN range SAP on the same port, system allowed this configuration. From 7210 SAS 6.0R2 release, the CLI does not allow use of duplicate VLAN ID. [ MA] With 7210 SAS 6.0R1 release, on boot-up, SAPs which have a ToD policy attached to them stayed operationally down for the first 6 minutes after reboot. This issue is not seen when such a configuration file is loaded after the system boots up. This issue is resolved in 6.0R2. [ MI] In Meter override, meter mode was changing to "no mode" from trtcm1 when only CIR is specified in the rate command with no PIR, this issue is resolved. [ MI] RESOLVED IN R6.0R1 The following are specific technical issues that have been resolved in Release 6.0R1 of the 7210 SAS-D OS. 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] Profile parameter [profile {in out}] for all the Eth-CFM SAA tests (Loopback, Linktrace, 2DM, and 2SLM) was not supported in previous releases and CLI command has been removed in release 6.0R1. An entry in the output of "show system lldp neighbor" incorrectly shows 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 error messages on reboot or upgrade. From release 6.0R1 using SNMP "default-action next-policy" is not allowed to configure. [ MI] Alcatel-Lucent Page 7

11 7210-SAS D OS 6.0R5 Software Release Notes In previous releases, CLI show output and MIB query incorrectly shows service-mtu value for VPLS/Epipe service. In release 6.0R1 "service-mtu" value is displayed as NA. [ 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 updates properly in this release. [61271-MI] ETH-CFM RDI was not generated for defmacstatus, This issue is not found in release 6.0R1. [98332-MI] RESOLVED IN R5.0R6 The following are specific technical issues that have been resolved in Release 5.0R6 of 7210 SAS-D OS. For In-band connections, NTP offset values for 7210 SAS-D was high in 5.0 releases compared to previous 7210 SAS-D releases. This issue is resolved. [154169] RESOLVED IN R5.0R5 The following are specific technical issues that have been resolved in Release 5.0R5 of 7210 SAS-D OS. If ingress mirroring of a LAG member port in mirror service A and egress mirroring of the same LAG member port in mirror service B is configured and one of the configurations is removed, an invalid configuration could have occurred when the user proceeds with mirror configuration on the parent LAG port. This issue has been resolved. [138875] Packets transmitted out of a port which is part of LAG subgroup and is in standby mode. This issue has been resolved. [154032] 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] IOM: UNUSUAL_ERROR: "remove_three_way_link_svp_dvp: Other sap endpoint does nt exist!" is seen when loopback with mac swap configuration was removed from a port while the other end point is in shutdown state on an epipe service. This has been resolved. [157035] From release 5.0R5, Cmplx #1 output in "tools dump system-resources" command is not displayed. [156040] RESOLVED IN R5.0R4 The following are specific technical issues that have been resolved in Release 5.0R4 of 7210 SAS-D 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] 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] Page 8 Alcatel-Lucent

12 7210 SAS-D OS 6.0R5 Software Release Notes RESOLVED IN R5.0R3 The following are specific technical issues that have been resolved in Release 5.0R3 of 7210 SAS-D OS. In 5.0R3 release of SAS-M, a fix is provided to prevent the high CPU issue when DDM register read fails. An error message is displayed, if DDM read fails. [109294] UP MEP did not converge if port qinq etype configured was other than 0x8100 and 0x9100. Local MEP shows "bdefrdiccm" and remote MEP goes in to "bdefremoteccm". This issue is resolved in 5.0R3. [142892] 7210 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. In earlier releases, occasional non transmission of PTP packet due to egress NC queue congestion on 7210 node which is acting as a PTP BC clock, resulted in PTP slaves connected to this BC node not recovering the clock correctly. This issue is resolved in 5.0R3. [147414] With earlier releases it was recommended to configure 7210 node in network such that 7210 receives 1588 packets directly instead of receiving through TC node. Using 5.0R3 release 7210 node can receive 1588 packets through TC node. [150309] From release 5.0R1, filter configuration can be used to drop IGMP control packets on SAP ingress. [139887] 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] An asterisk "*" indicating an unsaved configuration is displayed after the command ">config>system>res-prof>ing-internal-tcam# qos-sap-ingress-resource 1" is executed through reboot or config exec. Additionally "Changes Since Last Save:" field in "show system information" command output is shown "Yes". This has been resolved now. [148944] RESOLVED IN R5.0R2 The following are specific technical issues that have been resolved in Release 5.0R2 of 7210 SAS-D OS. In previous release, If ipv4 and ipv6 servers configured for radius, in case ipv4 server is not responding then 7210 was not communicating with ipv6 radius server. Issue is resolved in 5.0R2. Workaround was, not to configure ipv4 source address for radius application or not configuring ipv4 or ipv6 source address for radius application. This issue is also not seen if only ipv6 source address is configured for radius application. [146182] 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] Log events for changes to "configure system resource-profile" CLI context were not generated, issue is resolved in 5.0R2. [146911] Alcatel-Lucent Page 9

13 7210-SAS D OS 6.0R5 Software Release Notes Node lost management and console access when node receives malformed Tacacs authresponse. This issue is resolved in 5.0R2. [148054] In earlier releases, for dot1q and QinQ enacps, dot1p priority bits are always transmitted with 0 value when a 2DM & 1DM request packet issued with priority field set. This issue is resolved in 5.0R2. [130049] From release 5.0R2, Dot1ag 2dm and 1DM packets are sent with default priority of 7, in earlier releases default priority was 0. [143576] When UP MEP were scaled, Eth-cfm tests (lt,lb,2dm,1dm,slm) were not working for VPLS service in case MAC FDB is full or MAC learning disabled. Issue is resolved in 5.0R2. [145435] In release 5.0R1, multiple remote MEPs under one association with ccm-interval 100ms configuration fails, issue is resolved in 5.0R2. [149509] In earlier releases, SAP ingress qos policy with IP criteria applied on SAP, ingress non IP traffic classified to DSCP value "be" and corresponding fc. From release 5.0R1, non IP payload is classified to "default-fc". [151005] When an egress filter (ip or mac) is applied to the qinq SAP, the SAP statistics show double the number of packets actually egressing SAP. This issue is resolved in 5.0R2. [150205] RESOLVED IN R5.0R1 The following are specific technical issues that have been resolved in Release 5.0R1 of 7210 SAS-D OS. In previous releases SyncE active ref flaps if standby ref port flaps. This issue is resolved in 5.0R1. [143748] In previous releases "debug sync-if-timing force-reference ref" was not selecting the intended port internally. This issue is resolved in 5.0R1. [144146] 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] On 0.* epipe sap when the TPID of the packets received are not matching the qinq etype configured on the port, packets were not forwarded. In 5.0R1 this issue is resolved and packets will be forwarded over egress port. [144771] In release 5.0R1, IPv6 ACL 64-bit mode supports only source and destination IPv6 address match, other match options which are not supported were blocked in CLI and snmp. [144609] In previous release, invalid delay measurement values were observed for CFM 2DM tests, if static mac address is configured or updated after MEP is admin up. Issue is resolved in 5.0R1. [142162] Page 10 Alcatel-Lucent

14 7210 SAS-D OS 6.0R5 Software Release Notes RESOLVED IN R4.0R7 The following are specific technical issues that have been resolved in Release 4.0_R7 of SAS D OS. In previous releases, the console message was displayed when EFM "remote loopback" or "local loopback" on L2 Uplink port initiated, this issue is resolved in 7210 SAS 4.0R7. [136466] RESOLVED IN R4.0R6 The following are specific technical issues that have been resolved in Release 4.0_R6 of SAS D 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] RESOLVED IN R4.0R5 The following are specific technical issues that have been resolved in Release 4.0_R5 of SAS D OS. When the port is configured with loopback mac-swap on one SAP, traffic on other SAPs, where traffic src-mac, dst-mac did not match configured values are also looped back. The issue is resolved in this release. [132308] During boot-up time, false alarm in log-99 and 100 as "Power supply 1 output failure" with single DC PEM. The issue is resolved in this release. [133998] Static mrouter configured on SAP was not working after igmp-snooping shut or no-shut in a service. The issue is resolved in this release. [130663] 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] RESOLVED IN R4.0R4 The following are specific technical issues that have been resolved in Release 4.0_R4 of SAS D OS. In previous releases, when snooping is enabled on an access-uplink port, learned multicast traffic impacted the unicast meter instead of multicast meter. This issue has been resolved.[127139] In previous releases, G.8032 took around ms to recover after the links were restored. In 4.0R4, this issue is resolved and revertive time is sub 50 ms.[130977] Alcatel-Lucent Page 11

15 7210-SAS D OS 6.0R5 Software Release Notes In previous 4.0 releases, on execution of CLI "config system security mgmt-access-filter ip-filter entry 1 router <router-instance>", the console hanged and management access to the system was blocked. This issue has been resolved.[130545] RESOLVED IN R4.0R3 The following are specific technical issues that have been resolved in Release 4.0_R3 of SAS D OS. In previous releases, TACACS authenticated CLI users experienced slow response in some cases. This issue has been resolved.[122799] In case of IGMP enabled services having saps on same port, if igmp snooping is shutdown in one service, igmp data forwarding stopped on other service. This issue has been resolved in 4.0R3.[123370] Issue of dropping LLC frames, which are received on sap with control field 0x8e88, has been resolved in 4.0R3.[126469] In previous release, tsasqosnotifyprefix and tmnxsassysmibnotifyprefix objects under timetrasasnotifyprefix had same OID of dying gasp was wrongly shown as qos notify. Tis issue has been resolved in 4.0R3.[128625] RESOLVED IN R4.0R2 The following are specific technical issues that have been resolved in Release 4.0_R2 of SAS D 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-mgmtdisabled" in bof, image load from flash "cf1:\" was failing and box was not booting. This issue has been resolved in 4.0R2.[126409] RESOLVED IN R4.0R1 The following are specific technical issues that have been resolved in Release 4.0_R1 of SAS D OS. In previous release, Tagged BPDUs on a null SAP were forwarded by the software. In 4.0R1, hardware forwards tagged BPDUs [109624] RESOLVED IN R3.0R6 The following are specific technical issues that have been resolved in Release 3.0_R6 of SAS D OS. In previous release, Delay computed by Y DM OAM tool shows variations in results. In this release issue has been fixed. For 1-DM to provide accurate results, it is required to have NTP clocks on the nodes to be synchronised.[119670] Page 12 Alcatel-Lucent

16 7210 SAS-D OS 6.0R5 Software Release Notes RESOLVED IN R3.0R5 The following are specific technical issues that have been resolved in Release 3.0_R5 of SAS D OS. CLI 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 the CLI session. This issue is resolved now. [117416] After a few hours, the 7210 would fail to sync the system time with an NTP server. In this release, the 7210 SAS-D syncs with the Server. This issue was observed with 3.0R4 [118779] A CLI session might have remained logged in beyond its idle-timeout period if the user improperly terminated the CLI session by closing the session window while a multi-output CLI command (that is, the "monitor" command) was in progress. This issue has been resolved.[111704] SERVICES If 2 saps are configured on a port, where one sap has a single level mep and other sap has multiple levels of mep, eth-cfm was not converging. For example, if sap-1 is configured with mep level 1, and sap-2 is configured with mep level 1 and 4, sap-1 level 1 and sap-2 level 4 meps will not converge. Workaround: If sap-1 and sap-2 are configured with both mep level 1 and 4, eth-cfm will converge. This issue has been resolved. [114386] Vlan Tag was not getting changed as per egress encap when port 1/1/7 and lag-1 were part of the same service. Similar issue was seen with combination used in same service (Port 1/1/8 and lag-2), (Port 1/1/9 and lag-3) and (Port 1/1/10 and lag-4). This issue has been resolved. [116731] SYSTEM Fiber SFP 100FX LX or BX type is supported. [114461] Alcatel-Lucent Page 13

17 7210-SAS D OS 6.0R5 Software Release Notes NEW FEATURES 6.0R5 The following items describe features added to 6.0 R5 of the 7210 SAS-D OS. EPIPE OPER STATE DECOUPLING Platforms Supported: 7210 SAS-M (in both access-uplink and network mode), 7210 SAS-D and 7210 SAS-T. In 7210 SAS release 6.0R5, the user can now configure a single SAP in an Epipe that allows the operational state of the Epipe to remain up, even when the SAP enters a failed operational down state. There is no indication that the service is unable to forward transit traffic when this condition is active. This is only applicable to Epipes that exclude alternate egress points (for example: MC-LAG with ICB). LAG SAPs are supported. For more information, see the 7210 SAS Services user guide. VLAN RANGE SAP IN VPLS SERVICE Platforms Supported: 7210 SAS-M (only access-uplink mode), 7210 SAS-D and 7210 SAS-T Currently, the 7210 SAS platforms support use of Dot1q range SAPs with only Epipe services in either network/mpls mode or access-uplink/l2 mode. Dot1q range SAPs allow operators to transport a range of VLANs by providing similar service treatment to all of the VLANs configured in the range. It eases service configuration and allows operators to scale the number of VLANs that can be handled by the node. When MPLS mode is deployed in ring topology, operators have the option of using different redundancy mechanisms such as FRR, primary/secondary LSPs, Active/Standby PWs and others. To improve Epipe service availability, while no such option is available in prior releases to protect Epipe service in L2 mode when deployed in ring topology. The R5 release allows operators to deploy Epipe services in a ring topology when using L2 mode, by emulating an Epipe service using a VPLS service with G8032 protection and at the same time provides the benefits of using dot1q range SAPs. Even though a VPLS service is used for this, it is expected that the user should ensure through configuration that it is a point-to-point service. This can be achieved by configuring a VPLS service with an access dot1q range SAP used for customer handoff on one node in the ring and an access dot1q range SAP for customer handoff in an VPLS service on another node (i.e. at the other end of the Epipe), such that are only two endpoints for the service in the network. On the node where the service originates, in addition to the access dot1q range SAP, the service needs to be configured with access-uplink SAPs on the two G.8032 ring ports. The G.8032 mechanism is used to for breaking the loop in the ring and VPLS service protection. The intermediate nodes on the ring will need to use VPLS service with access-uplink SAPs on the ring ports and use the same G.8032 instance for protection as the one used for service protection on the originating node. The VPLS service with dot1-range SAPs use svc-sap-type of dot1q-range and supports the following functionality in comparison to a normal VPLS service. Page 14 Alcatel-Lucent

18 7210 SAS-D OS 6.0R5 Software Release Notes Allows user to define an access dot1q range SAPs, which specifies a group of VLANs which receive similar service treatment, i.e. forwarding behavior, SAP ingress QoS treatment and SAP (behavior similar to that available in Epipe service). In an epipe service, 7210 does not check if the inner tag received on a Q1.* SAP is within the range of the configured VLANs, when the packet is sent out of the dot1q range SAP. This is true for VPLS services too. It is up to operators to make sure they do not mix services. G.8032 mechanism can be used for loop detection in ring network and service protection. A separate VPLS service representing the G.8032 control instance must be configured and its state must be associated with this service. Support for xstp is not available. Broadcast, Unknown Unicast and Multicast (BUM) traffic is flooded in the service Learning is enabled on the service, by default, to avoid the need to flood the service traffic out of one of the ring ports, after network MAC addresses are learnt. User has an option to disable learning per service. MAC limiting is available per service and is not available per SAP CFM OAM support is available. Only UP MEPs can be configured on the dot1q range SAP in the service using a primary VLAN and used for fault management and performance management using the CFM/Y.1731 OAM tools. Support for Down MEPs and MIPs are not available. BPDU translation and L2PT support is not available L2 control protocol (L2CP) tunneling support is not available IGMP snooping and MVR is not supported. Note: For more information, see the 7210 SAS Services user guide. DRY CONTACTS (ALARM INPUT) USING CONSOLE PORT Platforms Supported: 7210 SAS-D. With this release, 7210 SAS-D provides an option to configure the console port as an alarm input pin. A single alarm-input pin can be enabled for use with the console port, allowing operators to monitor external events and alert the operator. The RXD and TXD pins of the console input are used to provide a single alarm input pin functionality. These pins of the console port are used by software to detect external events. The operating system detects an open or a close circuit and triggers an alarm and logs it when an event is detected. By default, the console port does not provide alarm input pin functionality. The CLI command "configure> system> alarm-contact-input" is used to enable the use of console port as an alarm input pin. After this command is executed, the console port can no longer be used as a console port, and the system generates a log message to convey this restriction. Additionally, user needs to configure the alarm-contact-input parameters for console, by using the CLI command "configure> system> alarm-contact-input console-1". NOTE: The user should enable a SSH/Telnet session before enabling console as an alarm-input. Once the alarm-input functionality is enabled for the console, the user can access the node using the SSH/Telnet session. For more information, please refer to the 7210 SAS-D,E Basic System Configuration user guide. Alcatel-Lucent Page 15

19 7210-SAS D OS 6.0R5 Software Release Notes 6.0R4 There are no new features added to 6.0 R4 of the 7210 SAS-D OS. 6.0R3 There are no new features added to 6.0 R3 of the 7210 SAS-D OS. 6.0R2 The following items describe features added to 6.0 R1 of the 7210 SAS-D 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. Page 16 Alcatel-Lucent

20 7210 SAS-D OS 6.0R5 Software Release Notes 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. 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. Y.1564 TESTHEAD 7210 SAS-M network mode and 7210 SAS-D node from 6.0R2 release supports service configuration test for user configured rate and measurement of delay, delay variation and loss with the testhead OAM tool. Note, 7210 SAS-M access-uplink mode supports testhead OAM tool from 5.0R4 release testhead OAM tool supports bi-directional measurement and it can generate test traffic for only one service at a given time. Testhead OAM tool can be used to perform out-of-service tests for VPLS and Epipe services. It can validate if the user specified rate (only CIR support is available in this release) is available and compute the delay, delay variation and loss for the service under test at the specified rate. It is capable of generating traffic up to 1G rate. User needs to dedicate the resources of a front-panel port for use with testhead feature. Additionally, port loopback with mac-swap must be used at both ends and all services or SAPs on the test port will need to be shutdown before using the testhead. For more information, see 7210 SAS-MX OAM and Diagnostics Guide. NOTE: The user must configure resources for ACL MAC criteria in ingress-internal-tcam using the command config>system> resource-profile> ingress-internal-tcam> acl-sap-ingress> macmatch- enable. Additionally they must allocate resources to egress ACL MAC or IPv4 or IPv6 64-bit criteria (using the command config>system> resource-profile> egress-internal tcam>acl-sap-egress> mac-ipv4-match-enable or mac-ipv6-64bit-enable or mac-ipv4-matchenable). Testhead tool uses resources from these resource pools. If no resources are allocated to these pools or no resources are available for use in these pools, then testhead will fail to function. Testhead needs a minimum of about 4 entries from the ingress-internal-tcam pool and 2 entries from the egress-internal-tcam pool. If user allocates resources to egress ACLs IPv6 128-bit match criteria (using the command config> system> resource-profile> egress-internal-tcam> acl-sap-egress> ipv6-128bit-matchenable), then testhead fails to function. 6.0R1 The following items describe features added to 6.0 R1 of the 7210 SAS-D OS. Alcatel-Lucent Page 17

21 7210-SAS D OS 6.0R5 Software Release Notes QOS POLICY OVERRIDE Platforms Supported: 7210 SAS-D, 7210 SAS-M (in both access-uplink and network mode) and 7210 SAS-X. In release 6.0R1, 7210 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-D, 7210 SAS-M and 7210 SAS-X Quality of Service User Guides. SSH WITH IPV6 Platforms Supported: 7210 SAS-D, 7210 SAS-M (in both access-uplink and network mode) and 7210 SAS-X. In release 6.0R1, SSH command used for remote management of the node securely, is available with IPv6. For more information, see 7210 SAS-D and 7210 SAS-M/X System Management User Guides. DHCP SNOOPING AND RELAY (BETA ONLY) Platforms Supported: 7210 SAS-D, 7210 SAS-M (in both access-uplink and network mode) and 7210 SAS-X. With release 6.0R1, 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 operator s 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. Page 18 Alcatel-Lucent

22 7210 SAS-D OS 6.0R5 Software Release Notes 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. 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. TWO WRED SLOPES Platforms Supported: 7210 SAS-D and 7210 SAS-M in both access-uplink and network mode. In earlier releases, 7210 SAS-M (both access-uplink and network mode) and 7210 SAS-D supported three slopes per egress queue. The three slopes were: TCP high-priority slope used for in-profile TCP packets. TCP low-priority slope used for out-of-profile TCP packets and Non-TCP slope used for all other packets. With this, it was not possible to differentiate between in-profile or out-of-profile packets for certain non-tcp traffic flows, like MPLS LSR traffic on 7210 SAS-M network ports, packets with more than 2 tags on 7210 SAS-D access-uplink ports. Thus, all such traffic would be treated the same way by WRED policies. With release 6.0R1, the user is provided an option to use only two slopes per egress queue. If user enables this feature, all the queues in the system use two slopes for all traffic flows (in other words, traffic is not differentiated as TCP or non-tcp with respect to WRED processing). The two slopes are high-priority slope for all in-profile traffic and low-priority slope for all out-ofprofile traffic. With this, the user can provide differentiated QoS treatment for the traffic flows mentioned in the example above, that is, for MPLS LSR traffic on network ports on 7210 SAS- M and packets with more than two tags on 7210 SAS-D access-uplink ports, by using the WRED policy parameters to prioritize in-profile traffic over out-of-profile traffic. For more information, see the 7210 SAS-D and 7210 SAS-M Quality of Service User Guides. DOT1X TUNNELING Platforms Supported: 7210 SAS-D and 7210 SAS-M in access-uplink mode. With the release 6.0R1, an option is provided to forward dot1x frames received on the port transparently to the remote end of the service. To forward dot1x 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, dot1x protocol must be disabled on the port (using the command "configure> port> ethernet> dot1x> port-control force-auth") before dot1x tunneling can be enabled using this command. If dot1x is configured to use either forceunauath or auto, then dot1x tunneling cannot be enabled. For more information, see 7210 SAS-D/E and 7210 SAS-M/X Interfaces User Guides. Alcatel-Lucent Page 19

23 7210-SAS D OS 6.0R5 Software Release Notes 5.0R6 There are no new features added to 5.0 R6 of the 7210 SAS-D OS. 5.0R5 There are no new features added to 5.0 R5 of the 7210 SAS-D OS. 5.0R4 There are no new features added to 5.0 R4 of the 7210 SAS-D OS. 5.0R3 There are no new features added to 5.0 R3 of the 7210 SAS-D OS. 5.0R2 The following items describe features added to 5.0 R2 of the 7210 SAS-D OS. FAULT PROPAGATION AND OAM MAPPING Platforms Supported: 7210 SAS-X, 7210 SAS-M network and access-uplink mode, and 7210 SAS-D. Operators typically deploy many different technologies in the network. These technologies use specific notification methods to indicate or clear faults between peers. There is no native single approach for end-to-end Operation, Administration & Management (OAM). The fault mapping and propagation feature provides the mediation function to bridge the gap between different technologies and provide end-to-end OAM without requiring the operator to select a single OAM tool to run across the entire network. The mapping function is used to communicate and clear faults between the different OAM functions on the same node for a point-to-point service. Starting from 5.0R2, Epipe service can link and propagate or clear faults between endpoints using ETH-CFM with CCM and PseudoWire (PW) with LDP status bits. For instance, an Epipe service could span across the network using Ethernet access (CFM used for OAM), pseudowire (T-LDP status signaling used for OAM), and Ethernet access (CFM used for OAM or Link Loss Forwarding (LLF) used to propagate fault). Different Ethernet OAM strategies should not overlap the span of each other in order to avoid conflicts that can lead to fault propagation in the direction toward the original fault, a false positive, or worse, a deadlock condition that may require the operator to modify the configuration to escape the condition. For example, overlapping Link Loss Forwarding (LLF) and ETH-CFM fault propagation could cause these issues, as could using ETH-RDI as an ETHCFM fault trigger. Page 20 Alcatel-Lucent