HP Systems Insight Manager - Manual (Page 168)

Ports used by Systems Insight Manager.
By default, Systems Insight Manager uses sport 5989 to communicate with the WBEM server of
the systems it monitors. To use a different port for this purpose, complete the following:
1.
The wbemportlist.xml file used by Systems Insight Manager must be altered to add the
additional or alternate WBEM port to be used. The file is located in C:\Program Files\
HP\Systems Insight Manager\Config\Identification
. This example shows where
the new lines (in red) must be added to the <wbemportlist> tag in the xml file:
<?xml version='1.0' encoding='UTF-8'>
<wbemportlist>
<port id='5989' protocol='https'>
<cimnamespacelist>
<cimnamespace name='root/cimv2'/>
<cimnamespace name='vmware/esxv2'/>
<cimnamespace name='root/hpq'/>
</cimnamespacelist>
<interopnamespacelist>
<interopnamespace name='interop'/>
<interopnamespace name='root/pg_interop'/>
<interopnamespace name='root'/>
<interopnamespace name='root/emulex'/>
<interopnamespace name='root/qlogic'/>
<interopnamespace name='root/ibm'/>
<interopnamespace name='root/emc'/>
<interopnamespace name='root/smis/current'/>
<interopnamespace name='root/hitachi/dm51'/>
<interopnamespace name='root/interop'/>
<interopnamespace name='root/switc'/>
<interopnamespace name='root/cimv2'/>
</interopnamespacelist>
</port>
<port id='2718' protocol='https'>
<cimnamespacelist>
<cimnamespace name='root/cimv2'/>
</cimnamespacelist>
</port>
</wbemportlist>
2. Restart the Systems Insight Manager service.
3. Right-click the HP Systems Insight Manager service in Windows Services API, and click restart
from the dropdown menu.
Property pages
I am receiving an error when clicking the Fans link on the Property pages Configuration tab.
Solution: Upgrade to HP ProLiant WBEM Providers 2.3.
-------------------------------------------------------------
The Property pages for the VMWare ESX (Non-Embedded) operating system are not available
due to limitations in the WBEM agents.
Reporting
In advanced reporting, graph labels may not be displayed properly in the report output.
This can be caused by not having the right Asian fonts installed on the CMS and client system.
Ensure that Asian fonts for the desired locale are installed on both the CMS and client system where
the browser is installed. In addition the font can be configured to an alternate font in the <Systems
168 Troubleshooting