Environment
Novell Access Manager 3.1 Linux Access Gateway Appliance
Novell Access Manager 3.1 Linux based Access Gateway Service
Novell Access Manager 3.1 Windows based Access Gateway Service
Using Session Affinity feature from Access Manager 3.1 SP3
Novell Access Manager 3.1 Linux based Access Gateway Service
Novell Access Manager 3.1 Windows based Access Gateway Service
Using Session Affinity feature from Access Manager 3.1 SP3
Situation
Access Manager setup and working fine. A Linux Access Gateway (LAG) cluster was created that includes 4 members/devices spanning two geographical locations. With the new session affinity feature from Access Manager 3.1.3, we can now point web server A to LAG cluster members in one geographical location and web server B to LAG cluster members in the other geographical location.
This would work great except the global cluster requires at least one web server to be assigned. This somewhat defeats the purpose of separating the web servers.
This would work great except the global cluster requires at least one web server to be assigned. This somewhat defeats the purpose of separating the web servers.
Resolution
Add a dummy IP address for the cluster drop down entry.
Normally, when definining the Web servers you want the LAG proxy to accelerate, you select the LAG IP address from a drop down menu and specify the back end Web server IP addresses it will talk to.
The drop down menu also includes the name of the cluster, and this needs to have a Web server IP address associated with it. This is redundant and as a workaround for now, simply add a dummy IP address to the list for this cluster. The issue will be addressed in Access Manager 3.2.
Normally, when definining the Web servers you want the LAG proxy to accelerate, you select the LAG IP address from a drop down menu and specify the back end Web server IP addresses it will talk to.
The drop down menu also includes the name of the cluster, and this needs to have a Web server IP address associated with it. This is redundant and as a workaround for now, simply add a dummy IP address to the list for this cluster. The issue will be addressed in Access Manager 3.2.