HP 2000sa HP StorageWorks MSA2000 G2 SMI-S Proxy Provider User Guide (573100-0 - Page 41

under All Storage Systems. What should I do?, restart HP SIM.

Get HP 2000sa PDF manuals and user guides View all HP 2000sa manuals
Add to My Manuals
Save this manual to your list of manuals

Page 41 highlights

This release of Proxy Providers does not support Life Cycle Indications only hardware Alert Indications are supported. 6.18. How can I increase the resolution for indication reporting? By setting the polling interval via the PSM, the indication resolution can be fine tuned. See Set indication provider polling interval, page 29. 6.19. How can I set the timeout value for CIM query? By setting the timeout value via the Proxy Settings Manager (PSM), CIM query timeout value can be controlled. SeeSet Proxy Provider timeout, page 28. 6.20. How can I enable/disable developer debug logs? By setting the proxy debug log level via the PSM, the developer debug log level can be controlled. See Set proxy provider debug log level, page 30. 6.21. The HP SIM discovery goes through without any errors but the MSA2000 system is not listed under "All Storage Systems". What should I do? Log in to the MSA2000 system and check if the field "System Name" is empty. If empty, set this field and rerun the discovery. 6.22. HP SIM cannot communicate with the CIMOM. What could be the problem? The likely reasons could be: • The CIMOM is probably not running. Please start CIMOM (see Q: 6.24. , page 41) and retry the operation. • The CIMOM is running on a non-default port (other than 5989). Please identify the port on which CIMOM is running and configure the SMI-S client to use that port instead. • The server on which the CIMOM is running might have a firewall turned ON and the firewall may be blocking some of the ports. Please turn OFF the firewall or change the firewall configuration and try again. • If the CIMOM is running on Linux, the SMI-S client may not be using the correct interop namespace. Please edit the wbemportlist.xml file and add an entry under and restart HP SIM. 6.23. PSM times out on the view command. What could be the problem? The PSM can time out for various reasons. The likely reasons are: • The CIMOM is not running. Please start CIMOM (see Q: 6.24. , page 41) and retry the operation. • The CIMOM is running but on port than the one PSM is using to communicate with it. • The MSA2000 G2 box is not reachable. 6.24. It appears that the CIMOM (cimserver) is not running. How do I start it? Use the following command to start the CIMOM: Windows service start cimserver Linux /etc/init.d/tog-pegasus start 6.25. After installation how do I figure out on which SSL port the CIMOM is running? Windows (do either a or b): MSA2000 G2 SMI-S Proxy Provider User Guide 41

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
This release of Proxy Providers does not support Life Cycle Indications only hardware Alert
Indications are supported.
6.18.
How can I increase the resolution for indication reporting?
By setting the polling interval via the PSM, the indication resolution can be fine tuned. See
Set
indication provider polling interval
, page 29.
6.19.
How can I set the timeout value for CIM query?
By setting the timeout value via the Proxy Settings Manager (PSM), CIM query timeout value
can be controlled. See
Set Proxy Provider timeout
, page 28.
6.20.
How can I enable/disable developer debug logs?
By setting the proxy debug log level via the PSM, the developer debug log level can be controlled.
See
Set proxy provider debug log level
, page 30.
6.21.
The HP SIM discovery goes through without any errors but the MSA2000 system is not listed
under "All Storage Systems". What should I do?
Log in to the MSA2000 system and check if the field "System Name" is empty. If empty, set this
field and rerun the discovery.
6.22.
HP SIM cannot communicate with the CIMOM. What could be the problem?
The likely reasons could be:
•
The CIMOM is probably not running. Please start CIMOM (see
Q: 6.24.
, page 41) and
retry the operation.
•
The CIMOM is running on a non-default port (other than 5989). Please identify the port on
which CIMOM is running and configure the SMI-S client to use that port instead.
•
The server on which the CIMOM is running might have a firewall turned ON and the firewall
may be blocking some of the ports. Please turn OFF the firewall or change the firewall con-
figuration and try again.
•
If the CIMOM is running on Linux, the SMI-S client may not be using the correct interop
namespace. Please edit the
wbemportlist.xml
file and add an entry
<interop-
namespace name="root/msainterop" />
under
<interopnamespacelist>
and
restart HP SIM.
6.23.
PSM times out on the
view
command. What could be the problem?
The PSM can time out for various reasons. The likely reasons are:
•
The CIMOM is not running. Please start CIMOM (see
Q: 6.24.
, page 41) and retry the
operation.
•
The CIMOM is running but on port than the one PSM is using to communicate with it.
•
The MSA2000 G2 box is not reachable.
6.24.
It appears that the CIMOM (cimserver) is not running. How do I start it?
Use the following command to start the CIMOM:
Windows
service start cimserver
Linux
/etc/init.d/tog-pegasus start
6.25.
After installation how do I figure out on which SSL port the CIMOM is running?
Windows (do either a or b):
MSA2000 G2 SMI-S Proxy Provider User Guide
41