d.Reboot the EFCM server. Repeat Step 1 through 3. If the connection is still down, proceed to Step e.

e.Stop and restart the service for the management server. Repeat Step 1 through 3. If the connection is still down, proceed to Step f.

f.Reboot the management server. Repeat Step 1 through 3. If the connection is still down, proceed to Step g.

g.If none of the above steps have restored the connection, see the support matrix for your edition to determine if the EFCM and switch versions are all supported. Contact technical support for further information.

CIM_ERR_FAILED When Trying to Activate a Zone Set Using McDATA

SWAPI

When the user tries to activate a zone set using McDATA SWAPI, the operation may return CIM_ERR_FAILED with one of the following detailed messages:

Cannot activate zone set. SWAPI Handle is not valid for fabric

Cannot activate zone set. Active zone set information is out of date for fabric

There is no active SWAPI connection for fabric Fabric is not in the cache

These error messages indicate that the SWAPI connection to the EFCM managing the fabric is no longer valid, or the active zone information was changed on the fabric without using the management server. The management server does not activate a zone set under these conditions.

To fix this problem, use the Test button on the discovery screen to check the status of the SWAPI connection. If necessary, re-discover the EFCM to re-establish the SWAPI connection.

Once the connection is working, the provisioning operation should succeed. If it continues to fail because the active zone set information is out of date, run Discovery Data Collection for this element to update the zoning information. See ”Discovery Data Collection” on page 153 for more information.

Communicating with HiCommand Device Manager Over SSL

By default, the management server communicates with HiCommand Device Manager through a nonsecure connection. You can configure the management server so that it communicates with HiCommand Device Manager over a secure socket layer (SSL) connection by doing one of the following:

•Use HTTPS in the discovery address - Prepend https:// to the discovery address to force the connection to HTTPS mode, for example, https://192.168.1.1, where 192.168.1.1 is the IP address of the host running HiCommand Device Manager. Use this option if you have one HiCommand Device Manager that you want to communicate through a secure connection (SSL) and another that you want to communicate through a nonsecure connection.

•Modify an internal property - Change the value of the cimom.provider.hds.useSecureConnection to true, as described in the following steps. Use this option if you want all connections to HiCommand Device Manager to be secure (SSL).

412 Troubleshooting