Item | Description | Bug ID |
|---|---|---|
1. | In an SLB environment with delayed binding forceproxy and cookie insert persistency, when running traffic with a cookie header, a 503 service unavailable message was returned without serving the request. | DE37403 (prod00262228, prod00262097) |
2. | In a Layer 3 environment, Alteon did not forward DHCPOFFER packets to the client. | prod00261697 |
3. | From SNMP or WBM, after performing a Revert Apply, when the xforward command was executed via the CLI, the delayed binding force proxy settings were not set for a service. | prod00261792 |
4. | After performing an Apply of the DNS server and health check configuration and then reverting to the same, a panic occurred. | DE37280 |
5. | In a DNS environment, Alteon stopped sending health checks with the destination as the hostname, while it worked when the destination was an IP address. | prod00261966 |
6. | HTTP/2 traffic was not handled correctly, and Alteon closed the connection during HTTP/2 handshake. | DE37186 |
7. | In an SLB environment, shutting down the real server in a group (/cfg/slb/group x/shut) caused the current running traffic on the server to stop when only the new traffic should have stopped. | DE37043 |
8. | In an SLB environment, after shutting the connection to a real server in a server group, and then enabling that real server in the group, although the real server moved to the UP state, the new connections were not accepted. | DE37040 |
9. | Using APSolute Vision, in Monitoring > Application Delivery > GSLB > Remote Real Virtual Servers, the following configuration error was returned: mib: gslbStatRemEnhRealServerIpVer not found | DE36993 |
10. | In an SLB environment, when a real server was overloaded and its health check was edited, although the real server status was changed to UP, it was counted as a non-active real server. | DE36774 |