I am running the Dell Image of Vmware Esxi 5.1 U3 which includes OpenManage 7.4. I have verified that it is running by 'esxcli vib software list'. I have the OWSM DWS on a Windows 8.1 client. I have verified the username/password. When I attempt to login I get "Login Failed: Connection Error". I have the checkbox "Ignore certificate warnings" enabled.
I see there are a lot of similar issues on this thread and there is even a known issue listed in the 5.1 u3 release notes that is supposed to be addressed.
I called into support and was told that the OWSM Client piece must be on a guest VM of the Vmware physical server I am trying to connect to. From what I have researched I don't believe this to be the case.
Can anyone confirm? Is this possibly the cause of my issue?
Verify that the following ESXi services are running:
# /etc/init.d/wsman status
openwsmand is running
# /etc/init.d/sfcbd status
sfcbd is running
# /etc/init.d/sfcbd-watchdog status
sfcbd is running.
# /etc/init.d/hostd status
hostd is running.
Verify that the following ESXi services are set to start automatically:
# chkconfig --list | grep -E 'wsman|sfcbd|hostd'
hostd on
sfcbd-watchdog on
sfcbd on
wsman on
Verify that the OMSA dataeng service is running:
# /usr/lib/ext/dell/srvadmin/bin/dataeng status
dsm_sa_datamgrd (pid 1985920 ) is running
dsm_sa_eventmgrd (pid 1986005 ) is running
Verify that port 443 is open
telnet esxi-ip 443
* Modify ESXi firewall if necessary: esxcli network firewall get|load|refresh|set|unload or use vSphere Client GUI
Solution for XP/2003 known limitation mentioned in the Systems Management Guide
You cannot log on to OMSA installed on ESXi 5.0 when Distributed Web Server (DWS) is installed on Windows Server 2003 and Windows XP. This is due to winhttp limitation on these operating systems and security enhancement on WSMAN on ESXi 5.0.
*DWS = Distributed Web Server, i.e. OMSA on Windows
1. Edit the file /etc/vmware/hostd/config.xml
2. Locate the ... tags in the file
3. Within the vmacore element, locate the ... tags
4. Within the ssl element, add the following element: HIGH:RC4-SHA:RC4-MD5
5. Save the file and restart hostd (/sbin/services.sh restart)
Thanks for your response. I went through your list. What I did notice is that I don't seem to have a /usr/lib/ext/dell/srvadmin directory so it would appear I am missing the OMSA binaries. Everything else is there -- port 443 responds to telnet, all of the ESXI services show as running.
Is the Windows box on the same subnet as the ESXi host? Do the firewall rules allow for connections? Would you be able to test with a laptop on the same switch as the server? If you have a Windows server on the same subnet you could install the Windows version of OMSA and use the web tools on there to try and see if it can connect. You may want to try to install OMSA on a VM on that host and see if it can connect with the web tools.
DELL-Josh Cr
Community Manager
•
9699 Posts
•
43744 Points
2738
0
Posted January 9th, 2015 15:00
Hi,
Here are some steps to try. Was the host rebooted after the install?
Verify that UserVars.CIMvmw_OpenManageProviderEnabled is enabled
vSphere Client > ESXi Host > Configuration > Software > Advanced Settings > UserVars >
User.Vars.CIMvmw_OpenManageProviderEnabled = 1
* Should also be listed in /etc/vmware/esx.conf
/advUserOptions/options[0018]/default = "1"
/advUserOptions/options[0018]/description = "Enable or disable the CIM vmw_OpenManage provider"
/advUserOptions/options[0018]/hidden = "false"
/advUserOptions/options[0018]/max = "1"
/advUserOptions/options[0018]/min = "0"
/advUserOptions/options[0018]/name = "CIMvmw_OpenManageProviderEnabled"
/advUserOptions/options[0018]/type = "int"
Restart the ESXi management services
/sbin/services.sh restart
Verify that the OMSA binaries are present:
# ls /usr/lib/ext/dell/srvadmin/
bin lib sbin var
Verify that /bootbank/OpenMana.v00 is present:
# ls /bootbank/OpenMana.v00
/bootbank/OpenMana.v00
Verify that /bootbank/boot.cfg contains OpenMana.v00
# cat /bootbank/boot.cfg
bootstate=0
kernel=tboot.b00
kernelopt=no-auto-partition
modules=b.b00 --- useropts.gz --- k.b00 --- a.b00 --- ata-pata.v00 --- ata-pata.v01 --- ata-pata.v02 --- ata-pata.v03 --- ata-pata.v04 --- ata-pata.v05 --- ata-pata.v06 --- ata-pata.v07 --- block-cc.v00 --- ehci-ehc.v00 --- s.v00 --- ima-qla4.v00 --- ipmi-ipm.v00 --- ipmi-ipm.v01 --- ipmi-ipm.v02 --- misc-cni.v00 --- misc-dri.v00 --- net-be2n.v00 --- net-bnx2.v00 --- net-bnx2.v01 --- net-cnic.v00 --- net-e100.v00 --- net-e100.v01 --- net-enic.v00 --- net-forc.v00 --- net-igb.v00 --- net-ixgb.v00 --- net-nx-n.v00 --- net-r816.v00 --- net-r816.v01 --- net-s2io.v00 --- net-sky2.v00 --- net-tg3.v00 --- ohci-usb.v00 --- sata-ahc.v00 --- sata-ata.v00 --- sata-sat.v00 --- sata-sat.v01 --- sata-sat.v02 --- sata-sat.v03 --- scsi-aac.v00 --- scsi-adp.v00 --- scsi-aic.v00 --- scsi-bnx.v00 --- scsi-fni.v00 --- scsi-hps.v00 --- scsi-ips.v00 --- scsi-lpf.v00 --- scsi-meg.v00 --- scsi-meg.v01 --- scsi-meg.v02 --- scsi-mpt.v00 --- scsi-mpt.v01 --- scsi-mpt.v02 --- scsi-qla.v00 --- scsi-qla.v01 --- uhci-usb.v00 --- OpenMana.v00 --- imgdb.tgz --- state.tgz
build=5.0.0-0.3.474610
updated=7
Verify that the following ESXi services are running:
# /etc/init.d/wsman status
openwsmand is running
# /etc/init.d/sfcbd status
sfcbd is running
# /etc/init.d/sfcbd-watchdog status
sfcbd is running.
# /etc/init.d/hostd status
hostd is running.
Verify that the following ESXi services are set to start automatically:
# chkconfig --list | grep -E 'wsman|sfcbd|hostd'
hostd on
sfcbd-watchdog on
sfcbd on
wsman on
Verify that the OMSA dataeng service is running:
# /usr/lib/ext/dell/srvadmin/bin/dataeng status
dsm_sa_datamgrd (pid 1985920 ) is running
dsm_sa_eventmgrd (pid 1986005 ) is running
Verify that port 443 is open
telnet esxi-ip 443
* Modify ESXi firewall if necessary: esxcli network firewall get|load|refresh|set|unload or use vSphere Client GUI
Solution for XP/2003 known limitation mentioned in the Systems Management Guide
You cannot log on to OMSA installed on ESXi 5.0 when Distributed Web Server (DWS) is installed on Windows Server 2003 and Windows XP. This is due to winhttp limitation on these operating systems and security enhancement on WSMAN on ESXi 5.0.
*DWS = Distributed Web Server, i.e. OMSA on Windows
1. Edit the file /etc/vmware/hostd/config.xml
2. Locate the ... tags in the file
3. Within the vmacore element, locate the ... tags
4. Within the ssl element, add the following element:
HIGH:RC4-SHA:RC4-MD5
5. Save the file and restart hostd (/sbin/services.sh restart)
The config.xml file should have this entry:
…
false
true
/lib/
HIGH:RC4-SHA:RC4-MD5
…
WinRM command to test OMSA
winrm i SendCmd cimv2/DCIM_OEM_DataAccessModule?__cimnamespace=root/dcim/sysman+InstanceID=DCIM_OEM_DataAccessModule1 @{CommandAndArguments="daname=hipda omacmd=getsummary"} -r:https://%1:443/wsman -u:%2 -p:%3 -skipCNcheck -skipCAcheck -skipRevocationcheck -a:Basic -encoding:utf-8
- Replace %1 with ESXi IP
- Replace %2 with ESXi Username (root)
- Replace %2 with ESXi Password