Alteon Application Switch

Release Notes
Version 25.1.0.0
September 14, 2009

North America Radware Inc. 575 Corporate Dr., Lobby 1 Mahwah, NJ 07430 Tel: (888) 234-5763 International Radware Ltd. 22 Raoul Wallenberg St. Tel Aviv 69710, Israel Tel: 972 3 766 8666 www.radware.com

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 2 These Release Notes describe fixes for AAS version 25.1.0.0. These fixes are part of the official product code, build date September 14, 2009. Table of Contents Release Summary ............................................................................................................................ 3 Supported Platforms and Modules ................................................................................................. 3 Maintenance Fixes ........................................................................................................................... 5 Known Limitations ........................................................................................................................... 7 Installing Alteon Application Switch Operating System 25.1.0.0 ................................................ 7 Verify switch connectivity................................................................................................................ 7 Upgrading from version 22.x/23.x to 25.x ...................................................................................... 8 Upgrading from version 21.0.4 or greater...................................................................................... 8 Upgrading from a version prior to 21.0.4 ..................................................................................... 11 Installation Considerations ........................................................................................................... 13

Page 2

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 3 -

Release Summary
Release Date: September 2009 Objective: Software Minor release, addressing 54 customer and major software issues New Licensing Mechanism Rebranded to the Radware Alteon Brand Alteon Application Switch or AAS

Supported Platforms and Modules

Alteon Application Switch Operating System 25.1.0.0 is supported on the Alteon Application Switch platforms outlined in table below. All Alteon Application Switch models now have an E5 variant that contains the following enhancements: SP memory - E5 variants contain 256 MB of SP memory instead of the 128 MB present in base models. RoHS compliance - E5 variants are compliant with the European Union Restriction of Hazardous Substances (RoHS) directive. Some E5 variants also have AC and DC power options available. The E5 variant is indicated by the inclusion of an E in the model name. This version is supported by the following platforms: AAS 2208 & 2208E AAS 2216 & 2216E AAS 2424 & 2424E AAS 2424-SSL & 2424-SSL E AAS 3408 & 3408E Software base:

Name
AAS-25.1.0.0-3000AlteonOS.img AAS-25.1.0.0-3000Serial.img AAS-25.1.0.0-2000AlteonOS.img

Type
Image Binary Image Image

Description
The image file used for upgrading the Alteon Application Switch 3408 through FTP or TFTP The image file used for upgrading the Alteon Application Switch 3408 through a serial download. The image file used for upgrading the Alteon Application Switch 2000 Series through FTP or TFTP

Page 3

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 4 -

Name
AAS-25.1.0.0-2000Serial.img AAS-25.1.0.0-Boot.img AAS-25.1.0.0-Mibs.zip

Type
Binary Image Boot Image MIB

Description
The image file used for upgrading the Alteon Application Switch 2000 series through a serial download. The image file used to update the boot kernel on Alteon Application Switches running version 25.0. The Management Information Base (MIB) files that support version 25.0.

File Name
AAS-25.1.0.0-2000-AlteonOS.img AAS-25.1.0.0-2000-Serial.img AAS-25.1.0.0-3000-AlteonOS.img AAS-25.1.0.0-3000-Serial.img AAS-25.1.0.0-Boot.img

MD5 Checksum
4a51af096b51ca1e99400c0ff42f5462 1a1552b5f3858cd5f5b5c1b2b8f78827 79d4ab7a963fc5a0cb11ef899901a948 df101962d7a5d8ed84472ab2a0c85340 be7e0f7ca93704ef21d3bdc5f2998957

Note: Starting with version 25.1.0.0, Radware has integrated a new licensing mechanism. The switch supports multiple tools to help make the transition as transparent as possible. Performing an upgrade will NOT remove the previous Nortel Keys and the downgrade process will recognize them automatically. For more information, see the Alteon Application Switch Licensing Guide versions 25.1.0.0 and 24.1.0.0. Note: Radware recommends that customers upgrade their Alteon Application Switch Operating System boot image to the software version currently running on the switch. Note: ASEM 6.0 or later must be used with switches running Alteon Application Switch Operating System 25.0.0.0 or later. Attempting to manage switches running these software versions with older management software can result in errors and mis-configuration of the switch. As of 25.0.0.0, the Browser-Based Interface (BBI) has been enhanced to support the Office Communications Server (OCS) wizard configuration and support for duplication of server group entries. Note: In order to maximize configuration compatibility during upgrade, Radware does not recommend upgrading from discontinued releases like 23.x to a 25.x based release. Please perform an interim upgrade to a 24.x-based release before upgrading to a 25.x based release.

Page 4

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 5 -

Maintenance Fixes
The following is a cumulative list of bugs fixed since the release of version 25.1.0.0.0.

Item
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11.

Description
HTTP requests are looped back to the default gateway as the VIP is no longer reachable, when VIP becomes deaf after config/apply. SFP ERROR message is generated for the wrong port. The static route is not added properly to the routing table when deleting the gateway and adding the static route at the same time. The filter session mirroring VLAN ID isn't the same on the backup. Cookie insert and persistency. Allowing the cookie persistent parameter for an operationally disabled real server does not work for PBIND cookie insert mode. 2424 23.2.2 - MSS of next hop is set to 0 and should not be. After traffic hit, Layer 7 pattern matching, the ALLOW filter does not work. Adv-hc+ backup real: Configuration changing causes backup real to be deactivated. Overflow server activation syslog for an unrelated real server is generated. The secondary backup does not come up when the backup overflows. SIP via header NAT. The original IP that is embedded in the branch subfield gets NATed. Direct Access Mode (DAM) is disabled and a number of real servers are directly connected to the switch, which require health checks to pass to the other AAS. This affects the design in which the switches are connected in an ActiveBackup configuration. Since the backup AAS does server processing also for the health check packets, the Layer 2 Switch will see packets from the backup AAS with sourceMAC=VSRMAC. This causes port flapping on the Layer 2 Switch because it sees the same MAC from master and backup. Rapid Spanning tree convergence is much longer when trunk ports are configured. Unable to add a character string to real 257 if the RIP does not exist. Insert Cookie persistency does not work for operation-disabled servers. Adding or removing static route causes VIP ARP entries to be removed from the ARP table. The device panics when viewing real stats via WEBUI. Dot3internalmactransit errors were fixed. i When the switch is defined with Jumbo frames enabled, performing packet capture in God-mode (/mai/pk/cap) will result in a panic when a Jumbo frame is received. OSPF: When changing the area type from transit to stub, the switch goes into a panic. Software Panic when applying HC content more than 125 characters for some services. Page 5

Bug ID
ALT00011117 ALT00021081 ALT00021068 ALT00012375 ALT00021161 ALT00001863 ALT00011380 ALT00011232 ALT00021157 ALT00006786 ALT00008541

12.

ALT00008891

13. 14. 15. 16. 17. 18.

ALT00002333 ALT00011850 ALT00002368 ALT00010812 ALT00001553 ALT00013067 ALT00003149 ALT00009557 ALT00005911 ALT00021363 ALT00003560 ALT00010291 ALT00005308 ALT00004446

19. 20. 21.

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 6 -

Item
22. 23. 24. 25.

Description
The device is rebooted a few times with the error message "Software Panic which is running code from version 24.0.0. The device unexpectedly is rebooted after performing configuration changes. low memory issue causing the box to panic PANIC: The device crashes when receiving a packet storm on the management port SFP G-BIC causes the MP CPU to reach 100%. 1. The MP reaches 100% CPU utilization when an SFP is inserted into the unit, staying at 100% for about 15 seconds. 2. The MP reaches 100% CPU utilization when resetting the unit and SFP GBICs are inserted, staying at 100% for about 30 seconds. Memory leak causes a panic. Memory causes a panic. When the client IP is the same as the VIP in a VSR-configured AAS setup, and the IP service is configured in the virtual server with the "nonat" option enabled, the client sends the traffic to any IP (for example: telnet w.x.y.z) and then AAS receives a panic. While applying a new configuration in one of the following cases: Case #1: Changing ports 1 and 2 from LACP to the static trunk Case #2: Changing the value of a Layer 7 string The device sends the following warning: "WARNING: Packet storm detected on mgmt port!" and then panics. In version 24.0.4.0, processing Layer 7 traffic may cause a panic. When there is a high volume of DNS traffic, SP-CPU utilization goes above 90%. In version 24.0.3, there was a panic due to SP invalid memory access. Panic due to the URL_SEQ. Panic triggered by RTSP URL Hashing configured on a Virtual Server. Layer 7 SLB problem with the HTTP method type in beginning of a HTTP continuation packet. In an IPv6 VRRP Active-Standby configuration, both AASs become the Master. BBI shows Virtual Server statistics incorrectly when issuing the /cfg/slb/adv/vstat e command, Panic when viewing port current configuration. An RTS session was not created after removing one IP address from multi-net server NIC Note: The new command was added under /cfg/slb/adv/rtsiplkup. The VRRP backup returned a remote VIP when queried and gmetric local was used. On an 2424SSL platform using version 23.2.4, there was a URL SLB problem with "POST" or "MOVE" in data packet. The LACP enhancement includes support for return traffic hashing based on destination MAC and IP. Strange session age transition when AAS receives SYN retransmitted by the client during 3-way handshake. After upgrading to version 24.0.5, a panic occurred every 16 hours due to URL sequence buffer header memory corruption during the URL server processing... Page 6

Bug ID
ALT00009413 ALT00006607 ALT00008869 ALT00001680

26. 27. 28. 29.

ALT00006197

ALT00011931 ALT00008040 ALT00008910

30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45.

ALT00004718 ALT00012330 ALT00009447 ALT00003753 ALT00004898 ALT00007595 ALT00005179 ALT00021475 ALT00008704 ALT00021090 ALT00021472 ALT00021349 ALT00001487 ALT00003246 ALT00001225 ALT00019420 ALT00021303 ALT00004966 ALT00021684 ALT00004898

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 7 -

Item
46. 47. 48. 49. 50. 51. 52. 53. 54.

Description
LDAP SLB weighting of servers not working correctly. UDP Server Fragmentation does not get server processed. The session table does not work correctly with multiple reports. The SFO mirrored session remains on the new master with the maximum age after failover. The device panics when the tab key is used in /cfg/port #/fast/speed. The GE switch does not show a warning message before downgrading to a lower image. The single real server cannot be configured through the OCS wizard. From the BBI, no data validation or error message is shown. The AAS panics when receiving traffic to the BBI with 5% fragmentation (fragments sent in reverse order).

Bug ID
ALT00004511 ALT00021117 ALT00012744 ALT00001997 ALT00021346 ALT00022008 ALT00021696 ALT00021691 ALT00021404

Known Limitations
N/A For other known issues, please refer to the software limitations section of the 25.0 Release Notes, product Release Notes, and technical documentation available from the Alteon Technical Support web site at: http://www.radwareAlteon.com.

Installing Alteon Application Switch Operating System 25.1.0.0

The following procedures outline how to install the Alteon Application Switch Operating System 25.1.0.0 image on the Alteon Application Switch: "Upgrading from version 22.x/23.x to 25.x " (page 7) "Upgrading from version 21.0.4 or greater" (page 7) "Upgrading from a version prior to 21.0.4" (page 9) A separate procedure is required for switches running versions of the Alteon Application Switch Operating System earlier than 21.0.4 because the Alteon Application Switch Operating System 25.0 image size exceeds 3 MB. Versions earlier than 21.0.4 cannot directly support software downloads through TFTP of files larger than 3 MB. The Alteon Application Switch supports software downloads using TFTP, FTP, or a serial connection. The procedures in this section depict a software download using TFTP or FTP. For information on performing a serial download, refer to Appendix C - Performing a Serial Download of the Alteon Application Switch Operating System Command Reference...

Verify switch connectivity

Before attempting a software download, ensure that the application switch has connectivity to the software download server. By default, the data ports are used to connect to download servers. If the management port is to be used to connect to an FTP or TFTP server, use the following command:

Page 7

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 8 >> Main# /cfg/sys/mmgmt/tftp mgmt

To check switch connectivity to the software download server, use the m option with the ping command to contact the server. The following example illustrates a usage of this command:
>> Main# ping 120.1.1.51 -m [host 120.1.1.51, max tries 5, delay 1000 msec] 120.1.1.51: #1 ok, RTT 2 msec. 120.1.1.51: #2 ok, RTT 1 msec. 120.1.1.51: #3 ok, RTT 1 msec. 120.1.1.51: #4 ok, RTT 1 msec. 120.1.1.51: #5 ok, RTT 1 msec. Ping finished.

Upgrading from version 22.x/23.x to 25.x

The Alteon Application Switch Operating System running on image 22.x/23.x cannot be upgraded directly to a 25.1.0.0 image. To achieve maximum configuration compatibility when upgrading from a previous release of software to version 25.1.0.0, do the following: 1. Check the Alteon Application Switch image: /info/sys/general The Alteon Application Switch image details appear. If the switch image is 22.x, go to step 2. Otherwise, go to step 3. 2. Upgrade the Switch image from 22.x to 23.x. The Alteon Application Switch image is 23.x. 3. Upgrade the Switch image from 23.x to 24.x. The Alteon Application Switch image is 24.x. 4. Upgrade the switch image from 24.x to 25.x. The Alteon Application Switch image is 25.x.

Upgrading from version 21.0.4 or greater

If the version of Alteon Application Switch Operating System on the switch is 21.0.4 or greater, follow these instructions for upgrading the Alteon Application Switch: 1. Download the new Alteon Application Switch Operating System 25.0 image into the image2 slot.
>> Main# /boot/gtimg 2 Enter hostname or IP address of FTP/TFTP server: <IP or server name> Enter name of file on FTP/TFTP server: <image file name> Enter username for FTP server or hit return for TFTP server: <username> Enter password for username on FTP server: <password> <software download begins>

Page 8

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 9 2. After the software download is complete, there is confirmation for using the new image and switch reboot.
Image download complete (3931913 bytes). Writing to flash...This takes about 60 seconds. Please wait Write complete (3931913 bytes), now verifying FLASH... Verification of new image2 in FLASH successful. image2 now contains Software Version 25.1.0.0 Switch is currently set to boot image1. Do you want to change that to the new image2? [y/n]y Next boot will use new image2. Do you want to reboot the switch? [y/n] y Reset will use software "image2" and the active config block. >> Note that this will restart the Spanning Tree, >> which will likely cause an interruption in network service. Confirm reset [y/n]: y

Note: Although a switch reboot is depicted in the above example, it is not necessary to reboot the switch to store the software image. The switch does not use the new software image until the switch is rebooted. 3. Download the new Alteon Application Switch Operating System 25.0 image into the image1 slot.
>> Main# /boot/gtimg 1 Enter hostname or IP address of FTP/TFTP server: <IP or server name> Enter name of file on FTP/TFTP server: <image file name> Enter username for FTP server or hit return for TFTP server: <username> Enter password for username on FTP server: <password> <software download begins>

Note: When the Alteon Application Switch Operating System 25.0 (or later) images are mixed with images prior to 25.0 in the flash (that is, one in image1 and the other in image2), it is important to save the crash dump of the image that crashed before switching to the other image should a failure occur. This is because Alteon Application Switch Operating System images later than 22.0 use a different flash location for the crash dump.

Page 9

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 10 4. After the software download is complete, there is confirmation for using the new image and switch reboot.
Image download complete (3931913 bytes). Writing to flash...This takes about 60 seconds. Please wait Write complete (3931913 bytes), now verifying FLASH... Verification of new image1 in FLASH successful. image1 now contains Software Version 25.1.0.0 Switch is currently set to boot image2. Do you want to change that to the new image1? [y/n] y Next boot will use new image1. Do you want to reboot the switch? [y/n] y Reset will use software "image1" and the active config block. >> Note that this will restart the Spanning Tree, >> which will likely cause an interruption in network service. Confirm reset [y/n]: y

Note: It is important to reboot the switch to use the new software image. 5. Upgrade the switch boot image. The switch boot image needs to match the new software image.
>> Main# /boot/gtimg boot Enter hostname or IP address of FTP/TFTP server: <IP or server name> Enter name of file on FTP/TFTP server: <image file name> Enter username for FTP server or hit return for TFTP server: <username> Enter password for username on FTP server: <password> <software download begins>

6. After the boot image download is complete, the new boot image is automatically applied to the switch without rebooting.

Page 10

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 11 -

Upgrading from a version prior to 21.0.4

To download Alteon Application Switch Operating System 25.1.0.0, first perform an intermediary upgrade to Alteon Application Switch Operating System 21.0.4.0 (or a higher version of 21.0.x) into the image1 slot and then download Alteon Application Switch Operating System 25.1.0.0 into the image2 slot. After this is completed, the switch can be set to reboot from image2 in order to load Alteon Application Switch Operating System 25.1.0.0 Note: As an alternative, perform a serial download of the Alteon Application Switch Operating System 25.1.0.0 binary image file directly into the image1 slot.

1. Download Alteon Application Switch Operating System 21.0.4 (or a higher version of the
21.0.x software) into the image1 slot. Alteon Application Switch Operating System 21.0.4 or higher software permits a software image greater than 3 MB to be downloaded into the image2 slot only.
>> Main# /boot/gtimg 1 Enter hostname or IP address of TFTP server: <IP or server name> Enter name of file on TFTP server: <21.0.4 or later file name> <software download begins> .......

2. Select image1 for the next reboot and reset the switch.
>> Boot Options# image 1 >> Boot Options# reset

The switch should now boot with the Alteon Application Switch Operating System version downloaded in step 1.

3. In the boot options menu, download the new Alteon Application Switch Operating System
25.1.0.0 image into the image2 slot.
>> Main# /boot/gtimg 2 Enter hostname or IP address of TFTP server: <IP or server name> Enter name of file on TFTP server: <image file name> <software download begins> .......

4. Select image2 for the next reboot and reset the switch.
>> Boot Options# image 2 Next boot will use switch software image1 instead of image2 >> Boot Options# reset

Page 11

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 12 -

5. Verify that Alteon Application Switch Operating System 25.1.0.0 has been properly installed
into image2.

6. Download the new Alteon Application Switch Operating System 25.1.0.0 image into the
image1 slot.
>> Main# /boot/gtimg 1 Enter hostname or IP address of FTP/TFTP server: <IP or server name> Enter name of file on FTP/TFTP server: <image file name> Enter username for FTP server or hit return for TFTP server: <username> Enter password for username on FTP server: <password> <software download begins>

Note: When the Alteon Application Switch Operating System 25.1.0.0 (or later) images are mixed with images prior to 25.1.0.0 in the flash (that is, one in image1 and the other in image2), it is important to save the crash dump of the image that crashed before switching to the other image should a failure occur. This is because Alteon Application Switch Operating System images later than 22.0 use a different flash location for the crash dump.

7. When the software download completes, the switch will confirm that the new image is to be
used and ask whether the switch should be rebooted
Image download complete (3931913 bytes). Writing to flash...This takes about 60 seconds. Please wait Write complete (3931913 bytes), now verifying FLASH... Verification of new image1 in FLASH successful. image1 now contains Software Version 250 Switch is currently set to boot image2. Do you want to change that to the new image1? [y/n] y Next boot will use new image1. Do you want to reboot the switch? [y/n] y Reset will use software "image1" and the active config block. >> Note that this will restart the Spanning Tree, >> which will likely cause an interruption in network service. Confirm reset [y/n]: y

Page 12

Alteon Application Switch version 25.1.0.0 Release Notes

Date: September,14, 2009 Page - 13 -

8. Upgrade the switch boot image to match the new software image.
>> Main# /boot/gtimg boot Enter hostname or IP address of FTP/TFTP server: <IP or server name> Enter name of file on FTP/TFTP server: <image file name> Enter username for FTP server or hit return for TFTP server: <username> Enter password for username on FTP server: <password> <software download begins>

9. When the boot image download completes, the new boot image is automatically applied to
the switch without the need for a reboot.

Installation Considerations
Radware recommends that you upgrade from software version 22.x to 23.x before you upgrade to software version 24.0. This assures maximum configuration compatibility when upgrading from a previous release of software to version 24.0. The following should be considered when upgrading the switch software to version 24.0: Due to potential boot image incompatibilities, both the boot and software image should be upgraded when upgrading to the current version of the Alteon Application Switch Operating System. Likewise, when downgrading to an earlier version of the software from the current version, downgrade both the boot and software image. After upgrading to the current version of the Alteon Application Switch Operating System, any ports in disabled VLANs will not link up.

2009 Radware, Ltd. All Rights Reserved. Radware and all other Radware product and service names are registered trademarks of Radware in the U.S. and other countries. All other trademarks and names are the property of their respective owners. Printed in the U.S.A.

Dot3internalmactransit errors were fixed and verified for many scenarios, but due to the many possible configurations, Radware recommends testing the bug fix for your specific environment. Page 13