Radware Alteon, Инструкция по применению

Страница: 571 / 842

Alteon Application Switch Operating System Application Guide
High Availability
Document ID: RDWR-ALOS-V2900_AG1302
571
The sync command copies the following settings to Alteon at the specified IP interface address:
• VRRP settings (including priority)
• SLB settings (including port settings)
• Filter settings (including filter port settings)
• Proxy IP settings
If you use the
sync
command, you should check the configuration on the target Alteon to ensure
that the settings are correct.
Note: When using both VRRP and GSLB, you must change the
/cfg/sys/access/wport
(Browser-Based Interface port) value of the target Alteon (the Alteon to which you are
synchronizing) to a port other than port 80 before VRRP synchronization begins.
Stateful Failover of Persistent Sessions
Alteon includes stateful failover of persistent session states, including:
• Client IP
• SSL session state
• HTTP cookie state
• Layer 4 persistent
• FTP session state
• WAP session state
For more information about the supported persistence types, see Persistence, page 583 .
Stateful failover lets you mirror Layer 7 and Layer 4 persistent transactional states on the Alteon
peers.
Note: Stateful failover is not supported in active-active mode. Also, stateful failover does not
synchronize all sessions, except persistent sessions (SSL session ID persistence and cookie-based
persistence). If a service fails in the middle of a connection, the current session is discarded, but the
new connection binds the session request correctly to the same real server.
To provide stateful failover, the state of the connection and session table must be shared between
Alteon in high availability configurations. If the Virtual Matrix Architecture (VMA) is enabled, all URL
and cookie-parsing information is stored in the session table on the last port number on Alteon.
Sharing this information between Alteons is necessary to ensure the persistent session goes back to
the same server.
Stateful failover only ensures that the client's request returns to the same server based on the
persistent session entries being shared by the master and the slave Alteon. The TCP session
information, however, is not shared.