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

CIMOM running on Windows, Windows, Linux

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 40 highlights

6.11. Can HP SIM running on Windows discover a CIMOM running on Linux and vise versa? Yes, the HP SIM running on Windows discover a CIMOM running on Linux and vise versa. 6.12. I am not able to create Indication subscription through HP SIM. What could be the issue? CIMOM running on Windows: • The server on which the CIMOM is running might have firewall turned ON. Turn OFF the firewall and try again. CIMOM running on Linux: • Edit the wbemportlist.xml file and add an entry interopnamespace name="root/ msainterop"/ under interopnamespacelist and then restart HP SIM. • The server on which the CIMOM is running might have firewall turned ON. Turn OFF the firewall and try again. 6.13. What Interop and Device namespaces does this proxy provider use? Following are the Interop and Device namespaces used by this proxy provide: Windows: InterOP Namespace = /root/PG_InterOp nl Device Namespace = /root/HPQ Linux: InterOP Namespace = /root/msainterop nl Device Namespace = /root/HPQMSA 6.14. Why is there a discrepancy in the storage capacity values displayed by HP SIM (using the Proxy Provider) and the SMU/CLI of the MSA2000 G2 device itself? Currently there are two standards for displaying the capacity info: • SI standard, 1024 bytes = 1 kilo byte (KB) (base 2) • IEC standard, 1000 bytes = 1 kilo byte (KB) (base 10) By default, the SMU/CLI of the MSA2000 G2 displays the capacity information using the IEC standard while HP SIM (using the Proxy Provider) displays the capacity information using the SI standard. So the capacity information displayed by HP SIM will be less than the actual value displayed by SMU/CLI. To get the correct value, multiply the value shown by HP SIM by a factor of 1.024 for each KB or adjust the SMU/CLI settings to use base 2 notation. For example: nl The volume capacity displayed by SMU/CLI : 28.9 GB (default base 10) nl The same volume capacity displayed by HP SIM : 27.01 GB (default base 2) The correct volume capacity value is: 27.01 * 1.024 * 1.024 * 1.024 = 29 GB. nl The volume capacity displayed by SMU/CLI : 27.01 GB (after changing base to 2) 6.15. What are the MSA2000 G2 interfaces that this Proxy Provider uses for data collection? For data collection the Proxy Provider uses both SMI-S and CLI (telnet) interfaces of the MSA2000 G2 system. The Proxy Settings Manager uses SNMP interface for device discovery. Verify that all of these interfaces are enabled so the Proxy Provider can work correctly. 6.16. Can I disable telnet service on the MSA2000 G2 system? No. For data collection, the Proxy Provider needs telnet service to be running on MSA2000 G2 system. 6.17. Does this release of Proxy Providers support Life Cycle Indications? 40 Frequently asked questions

  • 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
6.11.
Can HP SIM running on Windows discover a CIMOM running on Linux and vise versa?
Yes, the HP SIM running on Windows discover a CIMOM running on Linux and vise versa.
6.12.
I am not able to create Indication subscription through HP SIM. What could be the issue?
CIMOM running on Windows:
•
The server on which the CIMOM is running might have firewall turned ON. Turn OFF the
firewall and try again.
CIMOM running on Linux:
•
Edit the
wbemportlist.xml
file and add an entry
interopnamespace name=
”
root/
msainterop
”
/
under
interopnamespacelist
and then restart HP SIM.
•
The server on which the CIMOM is running might have firewall turned ON. Turn OFF the
firewall and try again.
6.13.
What Interop and Device namespaces does this proxy provider use?
Following are the Interop and Device namespaces used by this proxy provide:
Windows:
InterOP Namespace = /root/PG_InterOp
nl
Device Namespace = /root/HPQ
Linux:
InterOP Namespace = /root/msainterop
nl
Device Namespace = /root/HPQMSA
6.14.
Why is there a discrepancy in the storage capacity values displayed by HP SIM (using the Proxy
Provider) and the SMU/CLI of the MSA2000 G2 device itself?
Currently there are two standards for displaying the capacity info:
•
SI standard, 1024 bytes = 1 kilo byte (KB) (base 2)
•
IEC standard, 1000 bytes = 1 kilo byte (KB) (base 10)
By default, the SMU/CLI of the MSA2000 G2 displays the capacity information using the IEC
standard while HP SIM (using the Proxy Provider) displays the capacity information using the
SI standard. So the capacity information displayed by HP SIM will be less than the actual value
displayed by SMU/CLI. To get the correct value, multiply the value shown by HP SIM by a factor
of 1.024 for each KB or adjust the SMU/CLI settings to use base 2 notation.
For example:
nl
The volume capacity displayed by SMU/CLI : 28.9 GB (default base 10)
nl
The same volume capacity displayed by HP SIM : 27.01 GB (default base 2)
The correct volume capacity value is: 27.01 * 1.024 * 1.024 * 1.024 = 29 GB.
nl
The volume capacity displayed by SMU/CLI : 27.01 GB (after changing base to 2)
6.15.
What are the MSA2000 G2 interfaces that this Proxy Provider uses for data collection?
For data collection the Proxy Provider uses both SMI-S and CLI (telnet) interfaces of the MSA2000
G2 system. The Proxy Settings Manager uses SNMP interface for device discovery. Verify that
all of these interfaces are enabled so the Proxy Provider can work correctly.
6.16.
Can I disable telnet service on the MSA2000 G2 system?
No. For data collection, the Proxy Provider needs telnet service to be running on MSA2000 G2
system.
6.17.
Does this release of Proxy Providers support Life Cycle Indications?
Frequently asked questions
40