Bringing Up The Server If A Cluster Member Is Down; Bringing Up A Binary If It Is Down; Debugging A Cluster If Session Sharing Doesn't Properly Happen - Novell ACCESS MANAGER 3.1 SP1 - SSL VPN SERVER GUIDE 03-17-2010 Manual

31.18.1 Bringing Up the Server If a Cluster Member Is Down

Action: Check the Administration Console for the component that is down in the cluster member. If
the component is
openvpn
/etc/init.d/novell-sslvpn restart
You can check for the status by using the following command:
/etc/init.d/novell-sslvpn status

31.18.2 Bringing Up a Binary If It Is Down

Action: If the ,
openvpn stunnel
1 Stop the server by using the following command:
/etc/init.d/novell-sslvpn stop
2 Check whether the
openvpn
command.
If the binaries are running, kill the processes and start the server.
3 Restart Tomcat if it is not responding.
4 Check the status of the SSL VPN server.
31.18.3 Debugging a Cluster If Session Sharing Doesn't
Properly Happen
Action: Check the connectivity among the cluster members by using the following command:
netstat -anp | grep 8900
Restart Tomcat in all the machines if each cluster member doesn't have a TCP connection with other
members.
When a user is added, you can see the username in
.
members
NOTE: 8900 is the default port used for session sharing among cluster members. If a different port
is configured, for session sharing.
grep
, , or , restart SSL VPN by using the following command:
stunnel sockd
, or binaries are not running:
sockd
, , and
stunnel sockd
/var/log/messages of all cluster
binaries are still running, by using the
Troubleshooting SSL VPN Configuration 167
ps