Item Description Bug ID
1. When cookie insert for persistency and Layer 7 string matching were configured in an HTTPS offloading service, and the traffic did not contain any matching cookie or string, a server was selected instead of
responding with HTTP error 503 (server unavailable). prod00162602 2. With a heavy load of HTTP "Connection: close" traffic
and connection management enabled, software panic sometimes occurred when several responses were
sent from the server for one request. prod00162148 3. When the port command was retransmitted, Active
FTP load balancing did not work properly. prod00162078 4. Under certain circumstances, unpredictable behavior
occurred with certificate management (such as loss of keys, unable to connect via SSH, the diff flash holds
the configuration after reboot, and so on). prod00161974 5. When a client HTTPS request did not match any of the
strings assigned to the real servers, after Alteon reset
no response was received and SSL terminated. prod00161818 6. When the GSLB network IP version was not manually
defined, the proximity GSLB worked incorrectly. prod00161647 7. The redundant capability of setting an SNMP service
with TCP protocol was removed. prod00161584
Item Description Bug ID 8. The configuration apply command generated incorrect
and irrelevant VRRP syslog messages. prod00161579 9. Transferring a large file using an HTTPS service took
much longer compared to an HTTP service, because a
small TCP window size was set. prod00161459
10. For virtual services configured with SSL offloading where the front-end and back-end ports are the same, the service back-end port on the backup device was
changed during configuration synchronization. prod00161446 11. Using VRRP with stateful failover configured, when the
backup device booted up after upgrading to version
28.1.5, the master device rebooted repeatedly. prod00161442 12. In version 28.1.5.0, when X-Forwarded-For was using
with dbind enabled, the sequence number on the
second get request to server was incorrect. prod00161266 13. In version 28.1.2.0, an image upgrade via HTTP
transport caused a panic. prod00161254
14. In BBI, a clear operation in SLB monitoring cleared the
session table instead of clearing SLB statistics prod00161019 15. In an HTTP persistency configuration, the path was
added to the cookie header even though it was not
configured in the pbind cookie insert configuration. prod00161011 16. The connection splicing statistic was not updated with
dbind forceproxy. prod00161007
17. Alteon panicked when "host:" string was not found in
the URI of a request. prod00160900
18. The RADIUS secret password was synced during
configuration sync. prod00160668
19. When all the real servers in a group and backup group were down, the virtual server information displayed the
backup group as disabled. prod00160637
20. On Alteon with SSL acceleration card, a very heavy
load can cause a switch panic prod00160610
21. The swkey (license information) command did not
display the installed default throughput license. prod00160459 22. A non-updated Geo database was used, causing Geo
IP resolution for a DNS query to be incorrect. prod00160397
Item Description Bug ID 23. In certain cases, out-of-order fragments traffic with
proxy IP configured caused the device to crash. prod00160348 24. After upgrading from version 28.0 to 28.1, an apply
failed due to a certificate synchronization error, even
though no certificate was configured. prod00160341 25. Active FTP load balancing did not work properly when
PORT command retransmission occurs. prod00160294 26. On a virtual service with both caching and compression
policies, when compression was set disabled, caching
also stopped working prod00160249
27. After USB recovery, redundant message appeared
before the login prompt prod00159887
28. On on Alteon 5224, STP and LACP packets that were received on ports without a VLAN tag configured were
dropped. prod00159860
29. In a vADC hot-standby configuration with Layer 4 switch port tracking enabled, resetting the master vADC caused the backup vADC to take over only until
the master vADC started again. prod00159834
30. session matched on redirect filter with Linklb and FTPA enabled where created with ageing 0 and got
disconnected quickly prod00159775
31. On 4408/4408-XL devices, throughput license information showed irrelevant value when default
throughput license was installed prod00159763 32. It was possible to set the default gateway address to a
virtual server and PIP. prod00159741
33. In a vADC, server responses with the destination MAC of a different vADC were not processed and were then
dropped. prod00159723
34. During image download on VX, LACP trunks where blocked for about 2 minutes causing network traffic
instability prod00159550
35. When persistent entry exists but corresponding real server was down or disabled, Alteon answered with HTTP Error 503 (Service unavailable) instead of
selecting new server prod00159531
Item Description Bug ID 36. When TCP based health checks (i.e HTTP, FTP) were
configured for UDP based services, TCP port health
check was performed instead of ICMP prod00159427 37. The ADC-VX MIB-II did not support 64-bit counters.
ADC-VX interfaces were incorrectly displayed as
10/100 instead of Gigabit or 10Gigabit. prod00159381 38. In curtain cases, Direct Server Return (nonat enabled)
caused switch panic prod00159357
39. SSL session failed after configuration apply due to
certificate synchronization prod00159323
40. BBI showed incorrect user login information when login-in from the same host with different users which
has the same COS prod00159298
41. PIP statistics update of VLAN based PIP, caused the
vADC to crash prod00159297
42. In an ADC-VX environment, XL devices were not
indicated as XL in CLI displays. prod00159257 43. Switch panicked when real comes back up causing the
backup real servers to become disabled prod00158835 44. Navigation option between the Virtual Servers BBI
pages was missing prod00158669
45. After disabling connection management functionality in
a service, a persistency problem occurred. prod00158650 46. Active FTP load balancing did not work properly
because of the wrong adjustment to the sequence
number prod00158622
47. When static route is not covered by localnet, default gateway will be used. Removed confusing warning
message appeared in such cases prod00158609 48. Update of server certificate name via BBI was not
possible prod00158590
49. Active FTP load balancing did not work properly due to
wrong adjustment of the sequence number prod00158572 50. Certain SNMP traps caused the device to crash prod00158525 51. Virtual server current session statistics, showed
strange value via BBI prod00158470
Item Description Bug ID 52. It was not possible to disable SSL offloading for a VIP
via BBI prod00158456
53. Responses from Virtual Server were linked to the same port of the trunk and therefore limit the
throughput to 1 Gbps. This happened since the trunk load balancing algorithm used only source IP instead of
source IP + destination IP prod00158403
54. Enable "IP TOS matching" on a filter through BBI also
enabled the "IP Option Matching" prod00158281 55. Empty trunk name appeared in the configuration dump
caused failure in restoring configuration prod00158111 56. On a 5412 platform, TACACS+ authentication caused
the device to crash.
prod00157976
57. In BBI, the Alteon-VX dashboard did not work.
Also, HTTP request over management port with an empty Host header caused the device to crash
prod00157799
58. VRRP flap occurred when uploading tech support dump or viewing real servers information on backup
vADC1. prod00157771
59. On 4408 and 4416 devices, the putdumps maintenance command failed.
prod00157731
60. On a 5412 platform, the device crashed with a link load balancing configuration with fragmented traffic.
prod00157666
61. In CLI and BBI displays, an Alteon 4408 device with an SSL card was not identified as 4408XL.
prod00157617
62. Heavy load caused Alteon to sent irrelevant trap
(OCSP related) prod00157309
63. When "regex" or "none" where incorrectly defined as the HTTP modification element, a panic occurred.
prod00157033
64. The default compression license for 5224XL was changed from 500 Mbps to 1Gbps.
prod00157011
65. On device startup, a duplicate SNMP temperature trap was sent where one of the messages had incorrect information.
prod00156974
66. When only one power supply was installed in a dual power supply device, an SNMP trap reporting this problem was not generated.
prod00156903
Item Description Bug ID 67. After upgrading to version 28.1.5, all vADCs went down
and their image statuses were displayed as Incompatible.
prod00156868
68. In SNMP traps sent on data port, the wrong agent-address was included, and the incorrect OID was reported in slbCurCfgRealServerOid.0
prod00156813
69. In a vADC environment, when the syslog default port was configured on a management port, the source IP address of the syslog packets was the ADC-VX management IP instead of the vADC management IP.
prod00156720
70. Persistency break sometime occurred when a cookie arrived to an SP which did not contain the persistent
entry of that cookie prod00156706
71. During configuration sync, port number was replaced
with port allies causing a problem in VRRP failover prod00156661 72. When all primary servers were configured as disabled,
the backup servers moved from the blocked to the up state when one of the backup servers was disabled
operationally. prod00156636
73. In certain cases, active FTP LB with client NAT did not work.
prod00156619
74. When VLAN based PIP was configured, no PIP statistics were generated.
prod00156548
75. An Apply generated incorrect and irrelevant VRRP syslog messages.
prod00156531
76. In a vADC, a user with CoS set to user was unable to enable or disable the real servers that were assigned to him, while the l3oper user was able to do enable or
disable real servers that were not assigned to him. prod00156384 77. After upgrading from version 28.0 to 28.1, an apply
failed when VRRP hot-standby was configured.
prod00156344
78. The string "v4" was mistakenly added to the SMTP hostname in the configuration dump.
prod00156070
79. False fan traps were sent on a vADC. prod00155948 80. When a vADC was down, BPDUs in corresponding
VLAN were not blocked.
prod00155824
81. After upgrading from version 27.0.x to 28.1.2.x, An prod00155794
Item Description Bug ID apply failed when X-ForwardedFfor configured for a
service.
82. Throughput license is up to 16 Gbps for the 5224 and 5224XLplatforms. This was incorrectly stated in previous release notes.
prod00155691
83. After upgrade from 27.0.2.0 to 28.1.2.0 with dbind disabled and X-Forward-For enabled, after changing dbind to enabled on a service, an error message was issued, and the device crashed.
prod00155689
84. A vADC panic caused the SYS LED to turn red. Only rebooting the device turned the LED back to green.
prod00154297
85. During the upgrade process of a cluster, after one device was upgraded from version 28.0. to 28.1, the cluster changed to the VRRP Master-Master state.
prod00153379
86. A link UP was reported on port with the Copper SFP module inserted, even though the cable was not connected.
prod00152580
87. vADC throughput statistic was shown in MB rather than
Mbps prod00152104
88. When attempting to reset a vADC or device, a
message is issued that there is an unapplied/unsaved configuration even though the configuration was applied and saved.
prod00151807
89. An NTP server IP address could not be deleted (set to default 0.0.0.0 value).
prod00151632
90. After SSH login, the SSH management session sometimes hangs.
prod00151316
91. In dbind forceproxy service, If the client delayed in sending the FIN,ACK to Alteon as a response to FIN, the session entry was aged in slow aging rather than
fast aging prod00151145
92. After applying system configuration changes, incorrect SLB log messages were issued.
prod00151057
93. When an IPv4 VRRP group was enabled, it was possible to define an IPv6 VSR. This caused the IPv6 VSR to be unreachable.
prod00150485
94. When connection management was enabled and prod00141402
Item Description Bug ID egress PIP was configured (as recommended), Alteon
still required the ingress PIP address to be configured.