Item Description Bug ID
1. The switch blocked TCP sequence zero and direct ARP request (non broadcast) packets, treating them as attack packets.
136092
2. SSL offloading with SSL reuse did not work properly on Alteon 5412 XL.
155194
3. When delayed binding was enabled, an HTTP request with malformed HTTP version parameter caused a panic.
155172
4. When performing SNMP walk of the Alteon switch MIB, the walk stopped once it reached the
agAccessNewCfgHttpsCert.0
(1.3.6.1.4.1.1872.2.5.1.1.19.4.6.0) OID.
153699
5. When a configuration included real servers with buddy servers, after Apply unnecessary notices regarding server statuses were sent.
153555
6. The virtual server status was reported via BBI as blocked when one real server went down.
153554
7. When delayed binding was enabled, an HTTP request with malformed HTTP version parameter caused a panic.
153491
8. When Alteon 5224 ports 1 and 2 are administratively disabled (/cfg/port x/dis), the links connected to Alteon 5224 ports 3 and 4 went down.
153297
9. Performing the /maint/applog/showlog command caused a vADC restart, and no panic dump was available.
153167
10. A Header Modification rule to remove the Date header did not remove the header from HTTP requests.
152927
Could not enable SSH from Telnet in 28.1.2.0. 152888 11. The upgrade from version 27 to 28 failed if the device 152803
Item Description Bug ID configuration included certificates.
12. A panic occurred on a vADC when a SAVE command was performed via SNMP.
152787
13. When Web cache redirection and server load
balancing were performed using a filter with a non-zero server port (rport), the server port was not updated in the session table resulting in a session failure.
152506
14. Even though a vADC management port was locked by the Global Administrator, the vADC management port could be deleted by pasting a script without a
management setting.
152487
15. When changing proxy IPs and virtual servers using BBI, the device panicked.
152226
16. The default SSL CPS license was incorrectly set to 500 CPS for Alteon 5224XL.
152224
17. When an interface was disabled and then enabled, OSPF did not recover after the link came back up.
152132
18. MNG-2 management port could be configured but did not work properly. Currently this port cannot be configured.
152131
19. Interface statistics showed incorrect values. 152056 20. Load balancing between device gateways using the
round robin metric did not work properly and resulted in uneven allocation.
152044
21. When attempting to reset a vADC or device, a message displayed that there was an
unapplied/unsaved configuration even through the configuration has been applied and saved
151807
22. Load balancing of WTS traffic caused a panic on the device.
151681
23. Alteon VA responded to ping to VIR only when the request came from the VLAN to which the VIR belonged.
151590
24. When configuring the NTP primary server with an empty string, a fake IPv6 address was set as the server address.
151407
25. When NTP servers were connected behind a gateway, 151406
Item Description Bug ID an NTP warning message was displaying the gateway
address instead of the NTP server IP address.
26. The device did not allow enabling egress PIP (epip) on a service when the server-side port was proxy enabled but was not assigned a PIP.
151019
27. VRRP group settings could not be configured using the BBI.
150921
28. Alteon discarded ACK packets sent by client in response to server TCP keep-alive packets.
150750
29. The XML configuration API could not be used to change a vADC configuration.
150484
30. The message sent when Alteon was shut down due to critical temperature was not accurate.
150456
31. Importing a certificate in PKCS12 format to a vADC failed with the error "Error: Failed to extract cert+key".
150376
32. When user "user” was disabled for a vADC, it could still be used to access the vADC.
150327
33. Fragmented traffic that arrived for a virtual service which was processed by the Acceleration Engine caused a device panic.
150326
34. When an Intermediate CA Certificate Group and Intermediate CA Certificate had the same name, and the group was attached to an SSL policy, Alteon sent an Intermediate CA Certificate instead.
150306
35. When querying the VRRP status using SNMP in the Global Admin context of an ADC-VX device, the state of the Virtual Routers was incorrectly reported.
149938
36. Occasionally when Alteon did not forward an RST from the client to the server, the client received packets with the real server IP as the source instead of the VIP.
149875
37. Using the BBI, the user was able to configure a different application type for a standard service port when using IE6. After device/vADC restart, the configuration of such services was erased.
149702
38. The /info/slb/gslb/geo command did not display anything.
149636
39. When the HTTP method was split across packets, 149554
Item Description Bug ID Alteon dropped the first packet which contained an
invalid method and sent an HTTP_501 error message to the client.
40. There was an inconsistency between the actual altSwBulkApply trap packet and the description in MIB file.
149539
41. Bandwidth Management did not work on IPv6 traffic in Alteon version 28.1.
149497
42. Alteon allowed using the same IP address for a vADC peer address and a Global Admin management address.
148866
43. A group could not be deleted from CLI; the following error message displayed during the apply phase:
"Unable to lock cli, no response from configuration thread!" The group still appeared in the configuration dump, but it was empty.
148726
44. On sessions for which delayed binding was performed, if a FIN packet arrived from the client immediately after HTTP request packet the switch dropped the FIN packet.
148673
45. When user authentication was performed using RADIUS, if the RADIUS servers were unavailable and the user existed in the local user data base and had backdoor enabled, Alteon asked for user/password credentials again, instead of using the credentials provided the first time.
148671
46. When persistency using cookie insert was configured, the age of the actual session entry was updated to 4 minutes instead of using the selected real server timeout value.
148661
47. When Alteon performed delayed binding, if, in addition to persistency, content hash based load-balancing (such as URL hash or WTS user hash) was configured, TCP requests retransmissions were dropped.
148649
48. When an NTP and a DNS service were configured for the same virtual server, an NTP request that arrived immediately after a DNS request was sent to the DNS server group instead of the NTP server group.
148640
Item Description Bug ID 49. The admin password could not be changed using a
SSH connection.
148469
50. Configuration synchronization failed after upgrade from 27.0.1.0 to 28.1. The remote peer reset the connection.
148214
51. When DSR VIP health checking was enabled and the health check was UDP, the health check was sent to the real server IP instead of the VIP.
148213
52. SP memory utilization could not be monitored through SNMP.
147657
53. The persistency entry age update behavior when modifying Real Server Inactivity Timeout
(/cfg/slb/real x/tmout) and when changing Virtual Service Persistency Timeout (/cfg/slb/virt x/service x/tmout) was inconsistent.
147523
54. The switch gateway was temporarily down when adding a local static route.
143262