Installation Manual

Troubleshooting410
NOTE: The management server does not accept a period longer than its default setting. lf you set
the cimom.CimXmlClientHttpConnectTimeout property to more than 20 seconds on
Windows or three minutes and 45 seconds on Unix systems, the management server ignores the
values of this property and reverts back to the default settings.
To modify the default time-out:
1. Access the management server.
2. Select Options > Storage Essentials > Manage Product Health, and then click Advanced in the
Disk Space tree.
3. Click Show Default Properties at the bottom of the page.
4. Copy the cimom.CimXmlClientHttpConnectTimeout property you want to modify.
5. Return to the Advanced page.
6. Paste the copied text into the Custom Properties box.
7. Make your changes in the Custom Properties box. Make sure the property is not commented out
by removing the hash (#) symbol in front of the property.
8. To modify the time-out period, set the cimom.CimXmlClientHttpConnectTimeout
property to the number of milliseconds you want. For example, to change the time-out period to
200 ms, set the cimom.CimXmlClientHttpConnectTimeout property, as shown in the
following example:
cimom.CimXmlClientHttpConnectTimeout
=200
9. When you are done, click Save.
“CIM_ERR_FAILED” Message
If you are in a McDATA environment where the EFC Manager Service Processor is managing
multiple switches, it is possible that the management server will send SWAPI requests faster than
the EFC Manager Service Processor can handle them. The management server may detect this as a
failed connection and take corrective action. When this happens, you are shown a
“CIM_ERR_FAILED” message whenever the management server tries to access the McDATA
switches and directors.
The management server then attempts to reconnect to the EFCM by creating a new SWAPI
connection. EFCM versions 8.x and later have five SWAPI connections available. EFCM versions
7.1.3 and later but before version 8.x have three SWAPI connections available. If the
management server reconnects successfully, a reconnect event is generated, and no further action
is necessary.
If the management server cannot reconnect to the EFCM, another event is generated with a severity
of Major. If this happens, any Discovery Data Collection operation the management server
performs involving switches on that EFCM fails.
To prevent the “CIM_ERR_FAILED” messages, increase the delay between the management server’s
SWAPI calls to EFCM, as described in the following steps: