HP Serviceguard for Linux Version A.11.20.00 Deployment Guide, August 2012

NOTE: You may need to start the cluster if it is not already running. To run the cluster, go the

“Administration” menu and select “Run Cluster”.

Create Sample html content for the Package

1. Login to the cluster node that is currently running the “ws” package.

2. Create a sample content file (this command should be input on one line):

echo “<html><body> Sample Serviceguard package:

ws </body></html>” > /ws/index.html

NOTE: The sample package must be running and /ws must be mounted in order to create

the file.

Verification

Make sure the package is running on the first node, for example, eve.

Test that you can access the ws package content from your browser at the following URL,

http://<ws_ip_address>/index.html, for example:

http://16.89.84.218:80/index.html

From another browser window, go to the “Serviceguard Manager Summary” page, move the

package to the other node, for example, adam, using the “Move package” option from the

“Administration” menu. Select the node you want to move the package to.

Test that you can access the sample web page when the package is running on the other node. In

your browser, go to the following URL, http://<ws_ip_address>/index.html, for example:

http://16.89.84.218:80/index.html

Click the “Refresh” button on your browser to make sure you are still able to access the page.

Troubleshooting

This section contains a list of common errors and potential remedies.

Problem: Cannot boot off local disk after OS installation

Possible Remedy: Do not plug FC cables into servers until after the OS is installed. The standard

install process may try to place the boot partition on an external storage device if it detect that

external storage is connected.

Problem: Storage Management Utility browser interface does not display any “Manage” menu

options in the left-hand column

Possible Remedy: Refresh the browser window.

Problem: Error invoking the Serviceguard manager

Bad Gateway

The proxy server received an invalid response from an upstream

server.

Possible Remedy: The Java path for tomcat is wrong. To fix, make sure you have Java JDK 1.6 or

greater (Java 7 JDK is recommended). If not, install it. If you do not know the path to Java, you can

run the “find” command to find all java files and directories. For example “find / -name java” will

search the entire system under “/”. Look for the result under the JDK, not the JRE, for example,

/usr/java/jdk-1.6.0_13/bin/java. Then run /opt/hp/hpsmh/tomcat/bin/tomcat_cfg to input the

correct path to the Java.