2.0.R6 Release Notes

7210-SAS E OS 2.0_R6JANUARY-25-2011

7210-SAS E OS 2.0_R6SOFTWARE RELEASE NOTES

These release notes are for Release 2.0_R6 of the 7210 SAS-E OS software for 7210 SAS E devices.

RELEASE NOTE ORGANIZATION

The following are the major topics covered in these Release Notes:• Standard Software Upgrade Procedure on page 2• Resolved Issues on page 7• New Features on page 13• Enhancements on page 15• Known Limitations on page 18• Known Issues on page 21

*93-0270-06 V2.0.R6*

93-0270-06 V2.0.R6Alcatel-Lucent Page 1

7210 SAS-E OS 2.0_R6 Software Release Notes

SOFTWARE UPGRADE PROCEDURES

The following sections contain information for upgrading to the 2.0_R6 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.

STANDARDSOFTWAREUPGRADE

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.

Step 2. 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:\2.0R6 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.

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.

Step 4. Modify the boot options file to boot the new ImageThe 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 2.0_R6, execute the admin reboot upgrade command.

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.

Page 2 Alcatel-Lucent


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.

UPGRADING FROMPRIOR RELEASES

IMPORTANT NOTE: The following lists necessary boot-up configuration file changes.Prior to 1.0R5 release: The following router-name parameter was supported:

CLI Syntax: config>router router-name

The parameter values acceptable for router-name were Base and management.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 managementexit

Both lines must be removed.

Prior to 1.1R3 release: The following commands were supported:config>router>policy-options# info ----------------------------------.... policy-statement name entry entry-id from no prefix-list default-action accept no preference no metric no tag no type exit exit...----------------------------------config>router>policy-options#

The following commands are no longer applicable to the 7210 SAS-E have been removed in 1.1R3 and must be removed from the configuration file before upgrading to R1.1R3 or above:

prefix-list name [name...(up to 5 max)]no prefix-list

Alcatel-Lucent Page 3


preference preferenceno preference

metric {add|subtract|set} metricno metric

tag typeno tag

type typeno type

Prior to 1.1R3 release: The range for the table-size parameter was 1 — 2048. 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 upgradingprior to 2.0R5 config:-accounting-policy 5 record service-ingress-octets

default to file 5 no shutdown exit accounting-policy 6 shutdown record service-ingress-packets to file 6 exit*A:STU>config>service>vpls>sap# info ----------------------------------------------statisticsegressexitingresscounter-mode packetexitexit

collect-stats accounting-policy 6----------------------------------------------

Modifications required in configurations before upgrade

*A:STU>config>service>vpls>sap# info ----------------------------------------------statistics



egressexitingresscounter-mode packetexitexit

accounting-policy 6 ----- have been swapped from earlier configcollect-stats ----- have been swapped from earlier config----------------------------------------------

Another Scenario:-

Earlier Saved config:-accounting-policy 5 shutdown record service-ingress-octets to file 5 exit accounting-policy 6 record service-ingress-packets

default to file 6 no shutdown exit*A:STU>config>service>vpls>sap# info ----------------------------------------------statisticsegressexitingresscounter-mode octetexitexit

collect-statsaccounting-policy 5----------------------------------------------

Configuration to be modified accounting-policy 5 shutdown record service-ingress-octets to file 5 exit accounting-policy 6 record service-ingress-packets

default to file 6 no shutdown exit*A:STU>config>service>vpls>sap# info ----------------------------------------------statistics



egressexitingresscounter-mode octetexitexit

accounting-policy 5 -----have been swapped from earlier configcollect-stats -----had been swapped from earlier config----------------------------------------------



RESOLVED ISSUES

RESOLVED IN2.0R6

The following are specific technical issues that have been resolved in Release 2.0_R6 of 7210-SAS E OS.

ACL • 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 increments. This is applicable only in the case of an ingress SAP of service (B) having either a null or .1q* encapsulation. This issue has been resolved. [84135]

MIRROR • 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]

SERVICES • 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. This issue has been resolved. [95980]

SYSTEM • In prior release, few 7210 SAS-E and 7210 SAS-M platforms, the 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-termperature 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 (i.e. 7210 SAS-E 12T 12F) to allow for an offset between aisle ambient temperature and temperature measured by the chassis. [107935]

• FAN speed and sound oscillates when SAE-E running with 2.0R5 release. This issue has been fixed in 2.0R6 7210 OS. [108461]

RESOLVED IN2.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]

RESOLVED IN2.0R4


OAM • When dot1x was enabled on an efm-enabled port, the port would go down. Now, the port state is set as expected. [98397]

QOS • Copy command did not work for qos network policy. This command now works.[103294]



SYSTEM • The 7210 showed a high CPU utilization when a faulty SFP was inserted. This has been fixed. [82605/93904]]

RESOLVED IN2.0R2

The following are specific technical issues that have been resolved in Release 2.0_R2 of 7210-SAS E OS.• Pinging an IES IP interface did not work for packet sizes over 8999 bytes. This has been

fixed. [98821]

RESOLVED IN1.1R8

The following are specific technical issues that have been resolved in Release 1.1_R8 of 7210-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]

RESOLVED IN1.1R7

The following are specific technical issues that have been resolved in Release 1.1_R7 of 7210-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]

RESOLVED IN1.1R6


ACLS • Under management access filters, the src-port match-criteria cpm option has been removed as it is not supported. [87556]

RESOLVED IN1.1R4


SYSTEM • The monitor port and monitor lag commands showed incorrect statistics. Now they show correct statistics. [83757/86347]



STATISTICS/ACCOUNTING

• 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 access-uplink-specific records. [87158]

RESOLVED IN1.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]

RESOLVED IN1.0.R5

The following are specific technical issues that have been resolved in Release 1.0.R5 of 7210 SAS-E OS.

ACLS • In an Epipe service with an ingress ACL associated to a SAP on a LAG, traffic was affected during the removal and addition of LAG member ports. [81025]

• The system previously only allowed 1016 filter entries (template entries) to be created. Now, the system can create up to 576 filter profiles and each profile can have up to 126 entries. [76725/76674]

• A filter configured with an IP source or destination port configured as 0 matched all packets. Now, only those packets with port value as 0 are matched. [76828].



OAM • CFM linktrace and loopback messages were forwarded between SAPs belonging to the same split horizon group. Now, the messages are not forwarded between such SAPs. [81651]

• Dot1ag-MEP on null ports accepted tagged CCM messages. Now they are dropped. [79496]

SERVICES • When SHG is configured for a group of SAPs participating in an IGMP snooping-enabled VPLS service, IGMP packets, such as queries received on one of these SAPs, were replicated to all other SAPs. Now, the queries are not replicated to other SAPs participating in the same split horizon group. [82075]

• The Disable Learning feature on SAPs in VPLS services now works. [74992]

STP • STP/L2PT PDUs with invalid LLCs on STP/L2PT-enabled ports were forwarded. Now they are dropped. [71551/82676]

• L2PT packets egressing on a port which is a part of a split-horizon group is fixed now. [80233]

QOS • SAP ingress meter counters and statistics were incremented when an Epipe service was in an operationally down state even though the traffic was dropped. Now, the counters do not increment. [83270]

• In a port-scheduler-policy, if the weight of a queue was modified, it affected the weight of the other queue. [80721]

CLI • The strict mode parameter was added in the CLI in the port-scheduler-policy policy-id context. [75364]

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 as well as the other SFPs listed in “” on page 26.

RESOLVED IN1.0.R4




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.

RESOLVED IN1.0.R3


QOS • Meter stats now show the correct values after a roll-over. [78876]• Deleting a meter in a network ingress policy now generates a trap. [77828]



SYSTEM • 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 updategolden-bootstrap cf1:/boot.tim command after having booted with the new boot.tim.

RESOLVED IN1.0.R2


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]



NEW FEATURES

RELEASE2.0R2

The following items describe features added to 2.0 R2 of the 7210 SAS-E OS.

OUT-OF-BANDETHERNET

MANAGEMENT PORT

• 7210 SAS-E and all its variant platforms supports 10/100 Base-T ethernet management port. This port is available for out-of-band management of the node.

GENERATION OFY.1731 AIS

MESSAGE ON PORTDOWN

• 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.

RELEASE2.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 AVPLS 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.

DIGITALDIAGNOSTICS FOR

SFPS

• Digital Diagnostics Monitoring is a capability of some SFPs and XFPs where the transceiver module maintains information about its working status in device registers including:- Temperature- Supply voltage (for SFPs)- TX bias- TX output power- RX received optical power

The transceiver is also programmed at the factory with Warning and Alarm thresholds for Low and High conditions of the above that can generate system events.



The show port port-id detail command has been augmented to display the DDM data at the console, and the DDM data is accessible through SNMP for use with RMON threshold monitoring if traps are desired for custom thresholds.

Y.1731 • Y.1731 is defined by ITU-T. It is built on top of the IEEE 802.1ag, but it has more functionalities compared to the former, such as AIS, performance monitoring, etc. In this release, the following Y.1731 functionalities are supported: - ETH-CCM- ETH-LB- ETH-LT- ETH-RDI- ETH-AIS- ETH-TST- ETH-DM including one-way and two-way delay measurements.

Software timestamps are used for delay measurement.

QINQ ETHERTYPE • The QinQ Ethertype can be set to encapsulate QinQ packets sent out by the node and for processing QinQ packets received by the node. This value can be set per port. The port Ethernet encapsulation type should be set to qinq to use this. It provides the ability to interoperate with other QinQ bridges/switches that use proprietary Ethertype for QinQ encapsulation. A set of three unique QinQ Ethertypes are user-configurable. The default value is set to 0x8100.



ENHANCEMENTS

RELEASE2.0R6

The following items describe enhancements added to 2.0 R6 of the 7210 SAS-E OS.

RSTP FORWARDINGIN HARDWARE

• This enhancement is available from 2.0R1 release. RSTP packets with one or more tags received on a null SAP, or RSTP packets received with two or more tags on a Dot1q SAP, or RSTP packets received with three or more tags on a QinQ SAP are forwarded in hardware. In prior releases, forwarding of such RSTP packets was done in software. Note that RSTP packets with null tag received on a null SAP or RSTP packets received with a single on Dot1q SAP, or RSTP packets received with two tags on a QinQ SAP are processed locally, if STP is enabled.

SAP INGRESSMATCH CRITERIACLASSIFICATION

ENTRIES SCALING

• From release 2.0R1, sap-ingress qos policy supports 64 match entry criteria and max of 72 classifiers per sap-ingress qos policy.

RELEASE2.0R4


DC POWER SOURSE[-48V] FAILURE

DETECTION

• This enhancement introduces the capability to detect DC power source failure. 7210 chassis allows two DC power sources to be connected to the chassis. With this feature enhancement, the system detects if the DC power source has failed and raises a critical alarm (the Critical LED is lit and the Critical Alarm output pin is triggered). The alarm is cleared if the DC power source is restored. This enhancement is supported only on the new revision of the 7210 SAS-E hardware [3HE04410AAAC, 3HE04410ABAC]. There is no user configuration required to enable this feature. The software enables this feature automatically by detecting the capability of the hardware platform.

RELEASE2.0R2


SUPPORT FORMICROSECOND

TIMER GRANULARITYFOR OAM AND SAA

TOOLS

• In earlier releases, the system could not compute and display packet round-trip times and packet delay for values less than 10millisecond. With this feature enhancement, from the current release, the system will compute and display packet round-trip times and packet delay for values less than 10 millisecond. Most of the OAM tools and SAA tools have been updated to provide display microsecond time intervals.

RELEASE2.0R1




EGRESS QUEUESTATISTICS

• A counter can be enabled to count the total number of forwarded packets on an egress queue. These counters can be associated with any queue on any port for monitoring. Eight counters per node is available for use.

IGMPV3 SUPPORTFOR IGMP

SNOOPING IN AVPLS SERVICE

• Prior releases supported IGMPv1 and v2 snooping for a VPLS service. IGMP snooping in a VPLS service now supports IGMPv3. 7210 SAS-E now supports (S,G) records for multicast replication.

SUPPORT FORPROCESSING PVST

PACKETS

• The node supports processing of PVST packets received on a QinQ SAP, the packet is processed appropriately to update STP states and PVST BPDUs are sent out of that SAP.

INCREASE IN SAPAND SERVICE

SCALING

• The number of SAPs and services available for use has been improved. This allows the user to aggregate more services per node. The user is provided with an option to allocate QoS resources per SAP according to service requirements and to balance this with service scaling requirements.

RELEASE1.1R7

The following items describe enhancements added to 1.1.R7 of the 7210 SAS-E OS.

EGRESS SAPSTATISTICS

• Support has been added to obtain the count of packet sent out of a SAP in 7210-E. CLI commands are available to enable and disable the counter based on requirements. Additionally, support for new accounting records is available. Refer to the 7210-SAS-E OS Services Guide for relevant CLI commands.

RELEASE1.1.R6

The following items describe enhancements added to 1.1.R6 of the 7210 SAS-E OS.

LINK LOSSFORWARDING

• The 7210 SAS E now supports Link Loss Forwarding in an Epipe service. Link Loss forwarding enables fault propagation between the two NULL SAPs in an Epipe service. Refer to the 7210-SAS E OS Services Guide for the relevant CLI commands.

RELEASE1.1R3

• This release supports the configuration of up to 24 SAPs in a single VPLS service.

RELEASE1.0.R5

The following sections describe new enhancements added since 1.0 R4 to 1.0 R5 of 7210 SAS-E OS



EGRESS PORT RATE-LIMITING

• This feature allows the device to limit the traffic that egresses through a port to a value less than the available link bandwidth. This is useful when connecting the 7210 to a transport network, with limited bandwidth availability.

RELEASE1.0.R4

The following sections describe new enhancements added since 1.0 R3 to 1.0 R4 of 7210 SAS-E OS

IGMP SNOOPING • The 7210 SAS-E now supports IGMP snooping. When IGMP snooping is enabled in the VPLS context, a multicast record (*,g) is created for each multicast stream entering the VPLS context. Each stream will only be sent to each SAP where either a multicast router exists or a host exists that has requested to receive the stream (known as a receiver). The 7210 SAS-E supports snooping of IGMPv1 and IGMPv2 control messages only. On an IGMP Snooping enabled VPLS service, all IGMPv3 packets are dropped.

• The 7210 SAS-E supports a multicast forwarding size of up to 1024 entries. Although the CLI and MIB support up to 2047, it is recommended not to go beyond 1024 entries.Refer to the 7210 SAS-E OS Services Guide for the relevant CLI commands.

RELEASE1.0.R3

The following items describe enhancements added from 1.0.R1 to 1.0.R3 of the 7210 SAS-E OS.

EFM OAM - DYINGGASP

• 7210 SAS-E sends out a dying gasp message on all the ports configured in the access uplink mode and on which EFM is enabled when the device loses power. About 6 dying gasp messages are sent out one after another. The system does not provide for any user configuration options for this. Dying gasp message allows the service provider to unambiguously determine the reason for non-availability of the service.7210 SAS-E generates an event trap on receiving a dying gasp message from an EFM OAM peer.

10K MAC TABLESIZE

• Up to a maximum of 10K MAC system wide table size or for a single VPLS service is now supported.



KNOWN LIMITATIONS

• Egress SAP statistics and egress ACLs/filters cannot be enabled on a SAP when the port on which it is created has a default SAP configured.

• Packets with CRC errors are accounted for in the ingress meter calculations. [80966] • Packets discarded as the result of a discard-unknown-source and discard-unknown

configuration are accounted for in the ingress meter calculations. [84842] • Meter buckets are re-initialized when the rate value is modified. Rate values are modified

by explicitly changing the rate values using the appropriate CLI command or by changing the adaptation-rule used. [84395]

• Packets that get dropped due to egress queue drops are mirrored when port egress mirroring is enabled.

• Packets that get dropped due to egress filters are mirrored when port egress mirroring is enabled.

• Accounting records can only count packets or octets at a given time. This is configurable by the user. The configuration is also used to change the behavior for statistics collection.

• The monitor service id service-id sap sap-id rate command displays statistics in either packet or octet mode based on the accounting record configured. The utilization rate shows the appropriate values only when operating in octet mode.

• Dual rate SFPs (3HE04116AA and 3HE04117AA) connected to GigE SFP require autonegotiation to be disabled to operate in 1G mode. [78737]

• Layer 4 load balancing for broadcast, multicast and unlearned unicast traffic is not supported. [72425]

• Egress packets being mirrored are tagged with an internal service VLAN ID (this VLAN ID might not match the SAP tags and is only significant internally to the 7210 SAS-E). [70198]

• A mirrored packet contains the internal service VLAN ID (that is significant internally to the 7210 SAS-E) when ingress mirroring is configured for an IES SAP. [75852]

• SAP ingress meters (counters) are incremented for packets dropped by a filter on that SAP. [70878]

• If the system IP address is not configured, RADIUS user authentication will not be attempted for in-band RADIUS servers unless a source address entry for RADIUS exists.

• SNMP access cannot be authorized for users by the RADIUS server. RADIUS can be used to authorize access to a user by FTP, console, or both.

• If the first server in the list cannot find a user the server will reject the authentication attempt. In this case, the 7210 node does not query the next server in the RADIUS server list and denies access. If multiple RADIUS servers are used, the software assumes they all have the same user database.

• In an Epipe service, traffic is not switched if Source MAC is Multicast or Broadcast address [71437]

• The system accepts packets with sizes exceeding the port MTU by 4 bytes if the packet is VLAN tagged. [75221]

• Tagged BPDUs on a null SAP are forwarded by the software. [71656]



• A MAC will not age out as long as STP BPDUs from that source are received, although data traffic is not present. [71658]

• Copper ports cannot operate in 1Gig mode with autonegotiation disabled. [75345]• If the TACACS+ start-stop parameter option is enabled for accounting, every command

will result with two commands in the accounting log.• If TACACS+ is first in the authentication order and a TACACS+ server is reachable, the

user will be authenticated for access. If the user is authenticated, the user can access the console and has the rights assigned to the default TACACS+ authenticated user template config>system>security>user-template tacplus_default. Unlike RADIUS, TACACS+ does not have fine granularity for authorization to define if the user has only console or FTP access. The 7210 SAS OS supports a default template for all TACACS+ authenticated users.

• If TACACS+ is first in the authentication order and the TACACS+ server is not reachable, the authorization for console access for the user is checked against the user’s local or RADIUS profile if configured. If the user is not authorized in the local/RADIUS profile, the user is not allowed to access the box.

• Note that inconsistencies can arise depending on certain combinations of local, RADIUS and TACACS+ configurations. For example, if the local profile restricts the user to only FTP access, the authentication order is TACACS+ before local, the TACACS+ server is up and the TACACS+ default user template allows console access, an authenticated TACACS+ user will be able to log into the console using the default user template because TACACS+ does not provide granularity in terms of granting FTP or console access. If the TACACS+ server is down, the user will be denied access to the console as the local profile only authorizes FTP access. [39392]

• If a source-address entry is configured for in-band RADIUS servers, the source address (IP address) is used as the NAS IP address, otherwise the IP address of the system interface is used.

• default.cfg is a file name reserved by the system. Do not create a file with this name in the root directory. [76972]

• For a LAG configuration with more than one port, if a meter configuration does not specify a CBS value, some packets may be marked yellow and be treated accordingly when buffer management begins.The solution is to increase the CBS setting whenever the CIR configured for the meter is greater than 1Gbps. For a LAG with two ports, a CBS value of 64Kbits is recommended. [72497]

• For a LAG configuration with more than one port, every other jumbo frame is dropped. The solution is to increase the MBS from the default value of 128Kbits to 144Kbits. [73552]

• In an ingress MAC filter policy, the etype and frame-type match criteria do not match packet fields in those packets received with more than one VLAN tag. [72839]

• In an ingress IP filter policy, Layer 3 and Layer 4 match criteria (such as, src-ip, dst-ip, srcport, dst-port, etc.) do not match packet fields in those packets received with more than one VLAN tag. [72839]

• MACs that are already learned do not age out after a filter is added to drop packets from those MACs. [73370]



• There is a small difference in the actual rate of traffic egressing out of a port for a given egress rate limit value. The difference in the actual rate is affected by the size of the packet. For example, it is noted that for an egress rate limit value of 40Mbps, the difference is approximately 2Kbps to 150Kbps for packets sizes between 100 bytes to 9212 bytes.

• MAC or IP filters applied on a SAP in an IGMP snooping-enabled VPLS service will not be able to block IGMP control packets. [80612]



KNOWN ISSUES

The following are specific technical issues and limitations that exist in Release 2.0_R6 of 7210 SAS-E OS. The topics are arranged alphabetically.

ACLS • For SAPs, if egress filter and egress statistics are enabled together then egress filter counters cannot be used to obtain count of packets matching the egress filter entry. However, egress filter functions appropriately. If the user needs to obtain a count of packets matching the egress filter entry, the egress statistics must be disabled with the no packets-forwarded-count command in the SAP context where the egress filters are in use. [93524]

• When an equal amount of resources are used by an egress IP filter and MAC filter, the system resources consumed are not properly displayed in the tools dump system-resources output. [91662]

• Ingress and egress filters do not block STP packets when STP is enabled in a service. [75921]

• IPv6-based filters are not supported. [71857]• IP filter match criteria option-present cannot be used to match packet fields for traffic on

IES interfaces. [73188]• A mgmt-access-filter with a deny-host-unreachable action sends “Destination Net

Unreachable” instead. [73676]• Filter logging is not supported. [73135] • A filter entry action value configured as action should force the filter to pick up the default

action configured for the filter. This does not work. It is recommended to explicitly configure the action for each filter entry. [76620]

• An egress filter applied to drop all traffic on a port also drops EFM loopback traffic. [82782]

CLI • There are some unsupported CLI and CLI options displayed in the CLI command set. • Some of the show, monitor, and tools CLI command output displays unsupported fields and

modules.• The output of the tools dump command is not aligned properly when issued from a Telnet

session. [76876]

IGMP SNOOPING • When more than 2047 (S,G) joins are received in a scaled setup, it might result in hash collisions in the multicast forwarding. In such cases, learned groups can be removed/added back, with messages appearing on the console. (95345)

• On an IGMP snooping-enabled VPLS service, the 7210 SAS-E does not support multicast forwarding statistics. The show service id service-id mfib statistics command output will always show zero value counters. [81173]

IP • The CLI commands under the context config>router for the management routing-instance are not supported. [101636]

• DNS packets do not use the source IP configured for DNS applications. [75420]



• IP packets with options are not forwarded. • IP packets that need fragmentation are not forwarded. However, if the ARP is not resolved

for the next-hop, only the first packet is fragmented and sent out as soon as the ARP is resolved. Only CPU-generated packets are fragmented. [76353]

• Performing an SNMP GET on an interface description may not return the correct description of that interface if the same CLI command was used to create the interface and its description (for example, configure router interface interface-name description description-string). This is not an issue if the interface was created first, followed by the description. [65622]

• The show router interface command output incorrectly truncates the Port/SapId field for any interface when the string length of this field is more than 14 characters. [66751]

• 7210 SAS-E does not support secondary IP interfaces. However, these are configurable through SNMP, and should be avoided. [76848].

• The ping ip-address detail command should report the interface on which the ping reply was received. This information does not display in the output. [76887]

MANAGEMENT • If the source-address is configured for NTP, and if the system is rebooted with an older time set (using the admin set-time command), NTP takes a few iterations to synchronize for the first time. [86897]

• SNTP broadcast packets are not processed when they are received with an all-ones address. They are processed if they are received with sub-net broadcast address. [73662]

• When a static route is configured in the BOF, if the next-hop IP address specified, and it belongs to the same subnet as the destination IP address specified in the static route, then the node will not continue to boot. [73876]

• LACP flaps when starting an SSH server (no shutdown of SSH server). [75648]• SNMP operations on some unsupported SNMP MIBs might succeed.• There is currently no show command to display the current values of password hash

settings. [32747]• When logged in with the Telnet client supplied with Windows and issuing an SSH

command to a remote server, an unexpected carriage return may be sent causing the SSH connection to fail. [50657]

• An asterisk “*” indicating an unsaved configuration change may not be displayed after changing some of the parameters under some contexts such as the system and log contexts, (for example, *A:ALU-7210>config>system or A:ALU-7210>config>log). Additionally, the Change Since Last Save field in the show system information command output may not be updated. [61271]

• The CLI allows the user to specify a TFTP location for the destination for the admin save and admin debug-save commands which will overwrite any existing file of the specified name. [18554]

• SNMP walk of vRtrConfEntry shows the vpls-management and management instance as active even though these are not currently supported. [76832]



• SNMP query of the following operational rates does not return the correct values. The value returned is 0. CLI reports correct operational values. [76853].- tAccessEgressQueueOperPIR - tAccessEgressQueueOperCIR.

• The system becomes unresponsive and reboots when the file version check boot.tim command is issued simultaneously from multiple Telnet sessions. Simultaneous execution of this command should be avoided. [76543].

• If an ongoing FTP is aborted, the console and Telnet become unresponsive for a duration that depends on the size of the file being transferred. [76734, 74294]

• The 7210 SAS-E does not support storing more than 500 events for log destination’s memory and SNMP. Although the CLI and MIB allows up to 1024 to be configured, it is recommended not to exceed 500.

MIRROR • Log events are not generated for mirror application. [72100]• Ingress QoS policies applied for forwarded traffic will also be reflected on its mirrored

traffic. [73951]

OAM • A linkdown trap sent due to LLF has the ifOperStatus value set to up. [91172]• ICMP pings with higher packet sizes sent at higher rates will fail. [77611] • Under a heavy load condition, CFM/EFM/LACP may flap due to any of the following

triggers [74223]:- Executing a clear fdb or a show fdb command.- Transferring large files using FTP onto the flash.- Mac moves occur at a rate of approximately 40 macs/sec.

• CFM packets generated from the CPU are assigned to FC BE. Hence, there may be CFM flaps if the egress BE queue is congested.

• The minimum dead-interval time supported for an EFM OAM session is 2 seconds.• OAM DNS lookups do not work correctly unless the full DNS name is provided. [54239,

54689]• If a Dot1x unauthenticated port is put in efm loop-back, the data that should be looped

back is dropped. [76340]• Efm oam sessions may flap under the following conditions:

- Using the lowest transmit interval 500 ms, and 1s timeout, and- STP packets that need to be forwarded in the slow-path (CPU-based forwarding) are

incoming at a rate >64kbps, and - The CPU utilization is > 80% [76129]

QOS • If a port on which egress-rate port limiting is enabled and is mirrored on the egress, then for packets less than 768 bytes, the rate of traffic seen on the mirror destination port is not the same as that on the mirrored source port. [83168]

• When the queue on egress is within the CBS limit, the allocation of buffers is purely based on packet arrival time regardless of the packet’s in-profile or out-profile state. This can



sometimes cause unequal distribution of queue’s CIR/PIR to the various ingressing traffic using the same queue. As a workaround, configure an aggressive slope policy for yellow packets. [74730]

• The keyword max in the meter command configuration does not set the rate properly. The semantics of this keyword should set the metered rate to the maximum rate applicable to the interface over which the SAP attached to the meter is created. However, max sets the rate to 2Gbps. Use the applicable numeric value instead. [75845].

• The maximum entry-id value for the IP/MAC-criteria in the SAP ingress policy context is restricted to 63 although the CLI allows up to 64. Entry-id 64 should not be specified. [76790/76964]

RADIUS • In defining RADIUS Vendor Specific Attributes (VSAs), the TiMetra-Default-Action parameter is required even if the TiMetra-Cmd VSA is not used. [13449]

SERVICES • When a ARP request is received for an address configured for an IP interface in a VPLS service, the first ARP reply is sent to all the SAPs, instead of the SAP on which the request arrived. (94288)

• Flushing out 2047 groups learned in a single VPLS service (by executing a shut on igmp-snooping command) can cause Dot1ag to flap under loaded CPU conditions. [84904]

• Packets larger than port MTU are learned and are accounted for by rate limiters. However, they are dropped as expected. [73497]

• When all the member ports of a LAG are removed and added back, the “Ingress Packets rcvd” count for a SAP on that LAG, belonging to an Epipe service, is reset to zero [73439]

• Dot1p priority is not preserved for RSTP packets forwarded by the node (for example doubly tagged STP packets received on a SAP). The dot1p is remarked to 7. Additionally, these packets are not matched against egress filter policies. [71855/75921]

• MAC address learning rate is slow for certain sized packets. The average learning rate is approximately 200 MAC addresses per second. The learning rate for packets with sizes of 80 and 260 have been determined to be lower than this average. [77067]

• When disable learning is enabled on a SAP and if the VPLS service to which this SAP belongs is shutdown, packets are forwarded to the CPU. This can affect MAC learning in other VPLS services. [82787]

STP • If an ingress CPU forwarded RSTP/L2PT/PVST packet rate exceeds 64kbps, RSTP flaps. [73189]

• If a large number of MAC addresses exists in the VPLS FDB and the entire FDB is flushed and relearned, there may be a period of when RSTP BPDUs are not sent. A partial workaround is to configure fdb-table-size limits. [40532]

SYSTEM • Applying large router policy configurations (2000 to 3000+ lines) at one time, can cause protocols such as LACP, EFM, to flap. [83787]

• The number of files in the root directory is limited to 100. As a possible workaround, create a directory in the root directory and use that to save/store files. [75227]



• The statistics and the utilization rate displayed by the monitor port rate CLI command for a given time interval does not match the actual count and rate received by the system in that time interval. [83757]

• In certain scenarios (such as Cu SFP connected to Fixed Cu), the show port command does not display the MDI/MDX value as expected. Functionality is not affected. [76765]

• Rising and falling alarms for flash and memory usage are raised correctly, but the values reported for flash and memory usage are incorrect. [75455]

• In certain scenarios, traffic drops are seen during source learning when copper ports are operating in half duplex modes. Once learned, there are no other observed drops. [75875]

• When the show service fdb-mac command is executed through the console while the MDA is initializing (and when traffic is coming into the box), a software crash could occur. To avoid this anomaly, wait until the MDA is initialized and the ports are up before issuing the command. [74051]

• When the password aging option is enabled, the reference time is the time of the last boot, not the current time. The password expiry will also be reset on every reboot. [64581]

• The system time MIB object stiDateAndTime is the UTC time and should not include the time zone offset in SNMP get and set requests. [66553]

• During auto-config, if a DHCP relay packet for an unrelated DHCP session is received by the system, the system may be non-responsive. [76811].

• The link state of fixed copper ports remain in their current state even after a system reboot is initiated, but traffic is not forwarded. They are initialized during system startup. [76466]

• Control protocols may flap when the file copy command is initiated, using FTP, from the system if the specified FTP server is not reachable. This happens under loaded CPU conditions. Before initiating the file copy command using FTP, verify that the FTP server is reachable. [76566].

• Inserting and removing SFPs in rapid succession cause the following message to display on the CLI session. SFP/XFP Checksums do not match.If this message is seen, execute a shutdown command followed by a no shutdown command on the offending port to resolve the issue. [76935].

• The system saves core dumps at the URL specified in the BOF, while coming up. Specifying a remote location as a core file destination has two issues. - If a remote URL is specified, and if the uplinkA cannot be brought up, saving the core

dump may not succeed, even if uplinkB is up. - If uplinkA’s BOF is configured to use DHCP, the IP address acquired by DHCP is not

released by the system after saving the core file.Thus, it is recommended to configure the core file destination to be the local flash (cf1). [76764, 76736].

• During an auto-boot through DHCP when a ping-address is used in the BOF, the system may enter an inconsistent state during the ping-check phase. This was observed only once during which the user was viewing certain debug commands. [76858]

• When using 100FX SFPs, autonegotiation should be disabled. [99132]



HARDWARE • The USB interface is not supported on the 7210 SAS-E in this release.• Only one of the two port LEDs is used to indicate port status and link activity. If the LED is

lit steady it indicates link up. If the LED is blinking it indicates link activity.


Documents

2.0.R6 Release Notes