Item Description Bug ID
1. In version 28.1.8.40, when uploading the configuration with a private key, the key extraction failed because the
passphrase was not parsed correctly. prod00174411 2. In version 28.1.8.20, the redirection filter with client
proxy processing enabled did not work. prod00174272 3. When a SIP service with no SIP parsing was used,
various configuration additions (such as adding a filter, adding Layer 7 parsing for other services, disabling
local DAM) caused session failures on that SIP service. prod00174120 4. HSRP tracking did not work-- the priority was not
increased. prod00173856
5. When some services used the legacy delayed binding and some used forceproxy, under stress, the HTTP 503 error message could appear on the proxied
session due to server selection failure. prod00173770 6. Using the BBI, when configuring the intermediate
certificate name, the device panicked. prod00173754
Item Description Bug ID 7. After switching to verbose 1 mode, a service
configured in verbose 2 mode was erroneously
changed to basic-slb. prod00173750
8. When the scpadmin user on a TACACS server had the same password as the scpadmin on the device, logging in with the scpadmin user caused 100% CPU usage.
In addition, it was not possible to login with any username that had the same password as the
scpadmin user. prod00173687
9. Least connection load balancing on a real server port (rmetric) did not work with SLB IPv6-to-IPv4. All of the requests were load balanced to the first rport of the
server. prod00173370
10. SIP load balancing did not work when DAM was
enabled globally and disabled under the service. prod00173282 11. The SNMP Trap Source IP setting was not taken into
account and was not set as the trap source. Instead, the first interface that was UP was considered to be the
trap source. prod00173274
12. On traffic matching the IPv4 redirect filter with proxy processing enabled on the port, and no PIP address defined, Half NAT was not performed. Half NAT was performed correctly for the same configuration
processing IPv6 traffic. prod00173219
13. When the device rebooted with an expired certificate in its configuration, after the reboot all the configuration
remained in pending state. prod00172948
14. In session dumps collected via SNMP, the EAcc and
Acc flags were missing. prod00172918
15. Sessions collected via SNMP were not showing correctly when session entries were deleted or aged
during the collection process. prod00172917
16. On the 5224 platform, incorrect temperature thresholds
were displayed. prod00172904
17. In an ADC-VX environment, creating or changing Layer 2 configuration items such as trunks or VLANs caused
all the VIPs on the VADCs to stop function for up to 30 prod00172709
Item Description Bug ID seconds.
18. It was not possible to delete session entries by using
the slbOperSessionDelete SNMP SET command. prod00172596 19. Because in version 27.x, the default protocol for DNS
and SIP services was changed from TCP to UDP, after upgrading from version 26.x to 28.x, configuration
changes in the protocol setting occurred. prod00172595 20. Using the Chrome browser, Alteon did not release the
TCP connection created by opening HTTPS
management to the device via a data port. prod00172310 21. Removed the /boot/udefquit command on
console/telnet/ssh because rebooting the device from the console using Shift + Ctrl + "-" is not supported on
OnDemand Switch platforms. prod00172213
22. Using BBI or APSolute Vision, it was not possible to export a configuration with private keys. It is now
possible on HTTPS and SNMPv3 connections. prod00172196 23. Virtual service statistics did not display the content
based-service rules statistics when the service port
was different than 80. prod00172059
24. When accessing the device via BBI using the non-default OPER user, the Class Of Service is displayed
as USER instead of OPER. prod00172057
25. After an SNMP request to 802.1AB LLDP OIDs, VRRP
flip flopped. prod00171983
26. After configuration sync, the order of the virtual services section in the configuration dump was
different in the sending peer than in the received peer. prod00171762 27. In a VRRP pair configuration with DNSSSEC enabled,
configuration sync could cause both peers to be set
with keyslave enabled. prod00171761
28. After executing the /stats/sp/c +[tab] command in the
fourth Telnet/SSH session, the device crashed. prod00171758 29. In version 28.1.8.30, a revert apply with an interface
address change could cause the device to hang. prod00171609 30. The BPDU frame length for RSTP and MSTP BPDUs
was incorrect -- Alteon indicates a frame 14 bytes prod00171399
Item Description Bug ID longer.
31. Using BBI, when a real server or virtual server was added to the GSLB metric, the preference value was set to 0. Now you can define network preferences
values using BBI. prod00171391
32. In a VRRP owner configuration, editing or deleting the interface IP address or VIR address did not update the
interface MAC address to the base MAC address. prod00169623 33. After applying configuration changes that affected the
routing table, the device sometimes panicked. prod00169133 34. Due to unnecessary validation during boot-up, the
vADC configuration was not applied automatically and instead moved to “diff”. Manual apply was then
required to make it active.
prod00162680/
prod00170875 35. It was not possible to delete an IPv6 management
interface. prod00160336
36. When an apply command was performed in parallel with a configuration change done from another CLI interface, the CPU utilization increased.
prod00156307
37. When the passphrase configured for certificate sync contained an "!" character, the configuration was not
loaded after reboot. prod00171765
38. When force proxy was used, the default BWM contract (ID 1024) did not work, as well as application
acceleration capabilities and SSL acceleration. prod00171616 39. When Alteon inserted an x-forwarded-for header and
dbind is set to enabled, a client request corruption occurred.
When dbind is set to force-proxy, this client request
corruption does not occur. prod00171441
40. If one of the ports in a trunk was down, the trunk was declared down for port teaming.
In this version, the trunk is now considered up for port
teaming if at least one trunk port is up. prod00171252 41. Alteon did not process the HTTP CONNECT method.
After a service with application acceleration configured
received the CONNECT method, the service closed the prod00171244
Item Description Bug ID connection by sending [FIN,PSH,ACK] to the client.
42. When rport load-balancing was used with pbind cookie and dbind force proxy, virtual server statistics were
incorrect prod00171178
43. When receiving multiple GET requests in the same TCP session that matched both cookie persistency and URL SLB and that were designated to different real servers, the persistence sessions that were created were not removed from the session table, causing the
session table to fill up prod00170976
44. On a device with an ADoS license and DoS attack enabled on the port, ICMP type 3 packets (destination port unreachable) where considered as ICMPLEN DOS
attacks, causing the MP CPU to reach 100%. prod00170909 45. After migrating from the 2424 platform to the 5412
platform, WTS load-balancing did not work. This happened because of the difference between the CPU chips used in each platform and the way the IP
addresses are stored in memory. prod00170776
46. With GSLB set to enabled, HTTP access set to disabled, and wport set to 80, it was not possible to
apply a configuration. prod00170745
47. When real server backup with preemption were disabled, because an apply causes a server to either go up or down, when the backup server health check arrived before the primary server health check, the backup took over even though the primary was still alive.
prod00170723, prod00170456 48. The command description for importing and exporting a
certificate component was improved prod00170462 49. In a configuration with the same real server with
preemption disabled was associated to multiple groups that function in different virtual services, if the primary server failed, the backup server took over only in one group.
prod00170454, prod00170317 50. Configuring real server backup with preemption
disabled created tje following problems:
1. Preemption disabled did not work for some real servers (depending on their index).
prod00170453, prod00170067
Item Description Bug ID 2. If the primary server came up before the backup (for
the first time after reboot), and the server went down then up again, preemption acted as if it was enabled.
51. After failover, on the ex-Master, the status of some primary servers with backup preemption disabled changes to operator DISABLED and backup server took over.
prod00170451
52. Using a redirect filter, if a real server with preemption enabled failed, its backup real server took over and acted as if preemption was disabled when the primary real server came back up (traffic was still sent to the
backup server even though the primary was up). prod00170374 53. Network class deletion was not synced to a peer
switch. prod00170347
54. backup group real server showed in service info output as "group dis, up" and no traffic sent to that real
although the backup group was up.
This happened when the primary group went down and the backup group became active and then 2 more groups were added using the same real server from
the backup group prod00170175
55. In an ADC-VX environment, MSTP/RTSP was not
working. prod00169943
56. In a vADC environment, a tsdump command caused a VRRP to flip flop (meaning that the backup became master and after a short time became the backup again) and all services defined on that vADC went
down. prod00169942
57. Throughput information showed much higher values
than the actual throughput. prod00169940
58. When an IP fragment ping was sent to a VIR, VIP, or VSR, the interface MAC address was used as the
source MAC of the ping reply. prod00169338
59. When the IP address of a VIP was changed, the ARP entry with the old VIP address was not removed even though there was no other VR with the same address
as the old VIP. prod00169334
Item Description Bug ID 60. On an OnDemand Switch 3 platform, traffic from
source TCP ports 4 or 5 displayed incorrectly in the session table, as follows:
1. Aged-out sessions still appeared in the session dump
2. Live sessions were displayed incorrectly as BWM sessions. Their source IP addresses and ingress ports
appeared as 0. prod00169037
61. SLB VIP was added automatically to the OSPF
database and distributed to the peers even though the default route redistribution was configured (no host
redistribution defined). prod00168364
62. When entering a new virtual service menu without changing anything under that menu, Alteon considered it as a configuration change even though diff was
empty. prod00167509
63. Wrong FAN failure Syslog messages were sent while the tsdmp showed FAN OK.
prod00153747/
prod00153290 64. In a vADC environment, after importing a configuration
without its private key, even though the apply was successful after the import it was not possible to
access the server certificate menu. prod00156551 65. In DSR mode, ICMP health checks were sent to real
server IP rather than to sending it to the loopback
address (the VIP IP address) prod00170244
66. SIP session entry was not aged properly in a case where INVITE reuses a session that was already
deleted/moved to fastage. prod00169941
67. Network mask of localnet was not displayed properly prod00169609 68. When using configuration with multiple interfaces, the
device became inaccessible, within 5 minutes from upgrade to 28.1.8.20
prod00169565, prod00169455, prod00169458 69. SNMP Get/GetNext request to 1.3.6.1.2.1.2.2.1.3.x
caused the Alteon to enter freeze state. Reboot was
needed to exit this state. prod00169455
70. BPDUs of disabled VLAN were flooded on all ports. prod00169555 71. Alteon device sometimes panicked after applying prod00169333
Item Description Bug ID configuration changes that affected routing table.
72. HTTP traffic affected by vADC SSL CPS limit. prod00169253 73. After running SNMP traffic for some time, all
management activities became inaccessible due to a memory leak
prod00169141, prod00169111 74. SNMP services became down after upgrade. That
happened due to a changed added in SMTP Health check in version 28.1.8.10.
Now, SMTP HC made common for both IPV4 and IPV6, meaning that SMTP HC will send a "vrfy" even if there is no content is configured. Some SMTP servers does not reply to "vrfy" since they are waiting for additional data and therefore can be considered as
down prod00169052
75. vADC reset occured when accessed a virtual service of
type ''service ip''. prod00169012
76. In a URL redirect from HTTP to HTTPs setting, GET request without the host header caused the device to
crash prod00168862
77. When adding PIP for port range via BBI, an error
message appeared prod00168757
78. Passive cookie persistency with rport load-balancing, when the cookie is not found and the client request is within the same TCP connection, rport persistency was
not maintained prod00168751
79. Health Check Script above 156 caused the virtual
service to go down for several seconds prod00168588 80. HTTP content class and http modification did not work
together when both made a decision according to
HOST header prod00168515
81. SIP outbound call was not working prod00168443
82. It was not possible to define Script health check
between 64 to 256 prod00168271
83. nonat on RTSP virtual service was not working. prod00166915 84. Some syslog messages on management port were
missing,
No message was sent after the management IPv6 prod00166720
Item Description Bug ID gateway address and therefore it was thought to be not
UP
85. In hot-standby environment, when there are more than 256 VSRs, the following syslog message appeared in
the backup: "vrrp: received incorrect addresses" prod00165484 86. Querying the vADC interface using a 64-bit counter
MIB returned a value of 0. prod00162440
87. A change in the Layer 3 configuration caused the
default gateway status to flap. prod00168365
88. After upgrade, the pending configuration message displayed even though no pending configuration existed.
prod00167780
89. With the TACACS+ command login enabled, after executing an Alteon global command (such as save, apply, or diff. Alteon sometimes crashed.
prod00167541
90. When a hot-standby port was not part of VLAN assigned to the vADC, it was not tracked for VRRP priority.
prod00167398
91. An IPv6 VIP responded with the incorrect source MAC
address. prod00167397
92. In a DNS hostname configuration using regular expressions, uppercase characters were always changed to lowercase.
prod00167326
93. On a 4408 platform, sometimes a FAN status alert was
sent for non-existing fans. prod00167173
94. When a Layer 7 DNS string was configured to match at the end of the chain (using the $ symbol), if the string existed twice in the DNS query, it was considered to be no match.
prod00167152
95. Alteon dropped broadcast ARP replies with a unicast
target MAC address. prod00167139
96. In an ADC-VX environment, the OID of
vadcStateVrrpMaster / vadcStateVrrpBackup trap was incorrect.
prod00167105
97. The TACACS usernames did not display in the login
syslog message. prod00166917
98. In an ADC-VX environment, in the BBI dashboard the prod00166916
Item Description Bug ID SSL CPS information was incorrect.
99. On a 4408 platform, during upgrade a “file missing”
error message displayed. prod00166885
100. The SNMP trap for link up and link down was not clear
and did not indicate the port number and its state. prod00166805 101. When the Technical Support dump was issued via SSH
and the terminal immediately closed without writing the output, Alteon would sometimes crash.
prod00166745
102. In a vADC, when its two CUs were located on the same SP core (with a different HAID),a VRRP advertisement conflict occurred .
prod00166743
103. After issuing the "session clear" command, sessions that were removed on the master were not cleared on the backup.
prod00166740
104. NTP requests were not sent from an IPv6 management
port. prod00166538
105. Using BBI, when exporting all VX and vADC configurations, the vADC configurations were not restored properly.
prod00166537
106. On a 5224 platform using BBI, the displayed
management IP was different than the one configured in CLI.
prod00166536
107. The Spain daylight savings timezone was incorrect. prod00166534 108. An IPv6 VR did not reply to ICMPv6 requests. prod00166453 109. ICMPv6 router advertisements were not dropped by
the deny filter. prod00166448
110. Configuration synchronization was not working prod00166199 111. Redirection filters did not work correctly when proxy
was enabled on the port and the filter was defined with rport, even though no proxy IP was configured in the filter.
prod00165876
112. OSPF static/fixed selective route redistribution using
route maps did not work. prod00165847
113. Latency occurred due to a high port reuse rate. prod00165578 114. In a VRRP hot-standby configuration, when the ISL link
went down, the IP interface also went down on the prod00165487
Item Description Bug ID backup vADC.
115. Script health checks were not allowed for an IP type
virtual service. prod00164543
116. In a VRRP hot-standby configuration, when the master vADC panicked (booted up very quickly), the failover was not performed properly.
prod00162893
117. After importing a file that contains more than one
certificate, Alteon crashed. prod00160343
118. The SNMP trap for link up/down did not indicate the related port number.
prod00167018
119. Using RTSP SLB, TRCP and RTP sessions were not cleared from the session table on
time.
prod00166549
120. On a 5412 platform, when manually disabling an SFP copper port, the link did not go
down on the peer switch.
prod00166339
121. When multiple VIPs used the same real server, in the traffic that returned to the client
that caused a session failure, the real server IP to VIP translation was wrong.
prod00166243
122. On an Alteon 10000 platform, an irrelevant reboot log appeared.
prod00166207
123. Rarely, after upgrading to version 28.1.5.0, an HTTP 1.0 request from a proxy caused
the device to crash.
prod00166193, prod00166980
124. In a filter with session table caching disabled and tunable hash based on the source or
destination IP, group redirection did not occur.
prod00165795
125. When setting the backup group for a group with no real server, an unclear message
displayed.
prod00165506
126. When the request header was larger than 16K, SSL decryption failed.
prod00165389
127. When DSR was configured, many sessions were created for a single HTTP request,
prod00165358
Item Description Bug ID causing the session table to fill up even though the load
was minimal.
128. BWM statistics sent to an SMTP server configured on a data port caused a device panic.
prod00165357
129. On an Alteon 5412 platform with 32GB memory, a client request that reached 50K TPS
caused the device to crash.
prod00165275
130. When compression was used along with multiplexing, an HTTP 1.0 client, and server
keep-alive, transactions did not finish because a FIN was not sent by the server.
prod00165251, prod00166979
131. SSHv2 management connection did not work with a Sun Solaris client.
prod00165231
132. SSH management on data port caused a device panic. prod00165216 133. When a second HTTPS request arrived on an existing
TCP session, Alteon sent the
request to the same real server selected for the first HTTPS request without checking if there was a new URL SLB match.
prod00165016
134. Using BBI, configuring port mirroring caused the Alteon device to panic.
prod00164932
135. In a redirect filter with session caching disabled, when all the real servers were down,
the packets were dropped instead of being forwarded to the default route
prod00164910
136. When SNMPv1 and v2 where disabled, Alteon answered SNMPv1 requests with an
error message instead of not answering at all.
prod00164896
137. The td-config and shared maintenance debug commands were available in normal mode instead of being available only in god mode.
prod00164787
138. CISCO PVST and BPDU frames were not always tagged when sent out from a tagged
port.
prod00164731
139. Alteon did not forward BPDU frames in VX mode. prod00164710
Item Description Bug ID 140. In a GSLB environment, when more than 10 VIPs were
Item Description Bug ID 140. In a GSLB environment, when more than 10 VIPs were