Deploying Virtual Connect Enterprise Manageron Microsoft Cluster Service

Note: The purpose pf these steps is to ensure that HP VCEM is working after failover.

10. You should be able to use the active system name to establish a command-line session to the

cluster HP SIM service from a client system that has an OpenSSH client installed, using SSH.

For example, an mxversion or mxgetdbinfo -a command may be issued to verify a

command-line session connection has been established.

Note: The only exception is when the group containing the HP Virtual Connect Enterprise

Manager program files (HP VCEM Group in this paper) has failed over to the other system. In

this case, a failing message indicating

WARNING: REMOTE HOST IDENTIFICATION

HAS CHANGED

appears. When that happens, simply use the name of the other system

instead.

Troubleshooting

• Problem: Error during MSA tool execution.

• Solution: Execution of MSA tools might fail due to SSH key mismatch. For proper execution of

MSA tools, perform the following:

1. Make the primary system active and execute mxagentconfig to push the ssh key to primary

system itself.

AND

2. Make secondary system active and execute mxagentconfig to push the ssh key to

secondary system itself.

• Problem: Unable to Single Sign-On to client.

• Solution: Client should have the certificate/Name of both cluster systems in it.

1. If the Trust mode is Trust By Certificate on the client, open the Web agent certificate,

cert.pem file, from both the systems and import them into client Web agent.

2. If the Trust mode is Trust By Name on the client, include both the system names in trusted

server name list.

• Problem: Unable to get the second system certificate when browsing to SMH

• Solution: Import the second system certificate on to the first system.