HP has advised us to install HPSIM (System Insight Manager) on a Windows
box. We're told if HPSIM is able to connect to our VMWare ESX via Snmp or
DMI or WBEM, we're able to port this Windows box into the VMWare via
network (ie either via Snmp/DMI/WBEM ports).
After installing HPSIM on the Windows server & attempting to connect to
VMWare ESX, it gave the error below :
Is DMI, Snmp & WBEM turned on by default in VMware ESX?
Though WBEM is Tcp ports 5988 & 5989 while Snmp is Udp 161+Udp 162
& they appeared to be open :
# chkconfig --list | grep -i snm
snmptrapd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
snmpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
# netstat -an | grep 161 & netstat -an | grep 162 gave:
udp 0 0 0.0.0.0:161 0.0.0.0:*
udp 0 0 0.0.0.0:162 0.0.0.0:*
# lsof | grep -i 598
. . . . .
cimserver 1998 root 6u IPv4 5916 TCP *:5988 (LISTEN)
cimserver 1998 root 9u IPv4 5917 TCP *:5989 (LISTEN)
. . . . .
# netstat -an | grep 598
tcp 0 0 0.0.0.0:5988 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5989 0.0.0.0:* LISTEN
From the Windows box, I could do successfully
"telnet esx_server 5989" &
"telnet esx_server 5988"
So WBEM is through right (not blocked by firewalls). Or is there any other
that WBEM is listening on.
Udp 161 is somehow blocked by firewall (I used a tool 'portqry' on the
Windows box to poll the ESX server & it won't allow it through.
Appreciate is someone can review the HPSIM logs (appended below) -
would opening snmp Udp 161+162 help resolve this? If so, then only
I raise a request to get the Firewall admin to permit it
We haven't got our VM VirtualCentre up yet due to some licensing issue
so we're resorting to this method to port Windows boxes into the VM ESX
==========================
==========
==========
==========
=
System Name: 172.17.3.5 (this is the VMWare ESX 3.5 server)
Status:
Complete
Exit code: 0
Stdout:
Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
The System Management Homepage is not supported on this system.
Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
Running VM Identification
The system is not a VMware ESX Host, or WBEM credentials may not be specified, s
kipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system did not respond to SNMP, verify security settings and community strin
gs.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
The system does not support SNMP.
Running HP NetServer identification.
The system does not support SNMP.
Running HP-UX SNMP identification.
The system does not support SNMP.
Running SNMP System Type Manager identification.
The system does not support SNMP.
Checking for DMI protocol support.
The system does not have Windows DMI support.
Running DMI System Type Manager identification.
The system does not have Windows DMI support.
Running HP-UX DMI identification.
The system does not have HP-UX DMI support.
Running HP/Compaq Desktop identification.
The system does not have Windows DMI support.
Running HP DMI Desktop identification.
The system does not have HP DMI Desktop support.
Running Generic DMI identification.
The system does not have Generic DMI support.
Checking for SSH protocol support.
The system supports SSH protocol
Running Storage identification.
Did not detect WBEM support on this system. Will not attempt storage identificat
ion. If this is a storage host, check WBEM credentials and make sure the provide
rs and CIMOM are operational on the host.
Storage identification completed.
Running HP Service Guard Identification.
The system is not part of HP Service Guard cluster
Checking if this system is supported by Insight Power Manager.
Insight Power Manager is not supported.
Running VM identification.
VMM Integration is not enabled, skipping VM Identification
Building system relationships.
Running limited data collection for common attribute.
Done with limited data collection, checking retrieved data.
The SSH is not configured on this system
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.
Start Free Trial
