ESX 3.5 There is no System Management Homepage for "IP address"

[Brian Proteau]

After upgrading to ESX 3.5 Update 1, I upgraded to the latest HP Management Agents as I was told I'd need version 8.0X to support ESX version 3.5.

Eveything works fine except when trying to access the SMH page directly from HPSIM. When I do I get this message "There is no System Management Homepage for 'IP address'"

Logging in directly to https://server:2381 works fine. It's only through the Health Status link in HPSIM where it fails.

I tried updating to SMH version 2.1.12-200 but it still isn't working. Any ideas?

[David Claypool]

See the release notes for the 8.0 agents at http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=1121516&swItem=MTX-07643839dc4a4495b741d2640c&prodNameId=3288134&swEnvOID=2077&swLang=8&taskId=135&mode=4&idx=2

[Brian Proteau]

Sorry this doesn't help. I have read the release notes. What exactly in it do you think address my issue?

[Rob Buxton · Accepted solution]

I'm seeing the same issue on all of my ESX Servers from HPSIM.
I cannot jump directly from the HW Icon, it just brings up the System Page. From there if I go to the Health Status I get:
Properties: ourserver.ourco.nz

Property Pages are unavailable for this managed system.

Cause: Property Pages may not be defined for this
Operating System type or the system may be acting as a
WBEM storage proxy and has not had the native CIMOM
identified.

Resolution: Check the SIM release notes for supported
operating systems. For systems running as a storage
proxy, enter credentials for the native (non-proxy) WBEM
CIMOM on this managed system and re-identify the system.

On a Windows Server with PSP 8 there was a wbem/snmp setting we needed to change to get all of the data. I've not seen anything similar on the ESX SMH though.

[sandeep_raman]

what david was referring to in the release notes was the firewall ports if i'm not wrong.

* run these commands on the esx console

esxcfg-firewall -o 2301,tcp,in,WaWServer
esxcfg-firewall -o 2301,udp,in,WaWServer

* identify the node in sim and check if smh comes up

/srh

[kvelayutham]

Hi,


With latest SMH release, few additional ports also required to be opened.. use the following commands to enable those ports.


esxcfg-firewall -o 161,tcp,in,SNMP

esxcfg-firewall -o 161,udp,in,SNMP

esxcfg-firewall -o 2301,tcp,in,WaWServer

esxcfg-firewall -o 2301,udp,in,WaWServer

esxcfg-firewall -o 162,tcp,out,SNMP_TRAP

esxcfg-firewall -o 162,udp,out,SNMP_TRAP

esxcfg-firewall -o 5988,tcp,in,WBEM

esxcfg-firewall -o 5988,udp,in,WBEM


Regards,
k.velayutham

[Brian Proteau]

Thanks for everyones assistance. For the record this is what fixed the "Health Status" link in HPSIM for me.

(1) Enable port 2301 incoming (this is a temporary change)

esxcfg-firewall -o 2301,tcp,in,HPSIM

(2) Identify the ESX Server within HPSIM (Options -> Identify Systems...)

(3) Disable port 2301 incoming. I read where you do not want port 2301 to be open past this stage as it is an insecure connection

esxcfg-firewall -c 2301,tcp,in

[sandeep_raman]

after closing the port once smh link came up in sim, did you re-identify the node to see if the smh link is still there

/srh

[Brian Proteau]

I may not completely follow what your wanting me to do. I followed the instructions here:

http://www.astroarch.com/wiki/index.php/HPSIM_and_ESX

I only did the "Identify ESX Server" section because that's all I needed.

Now that the port is closed I don't think Identify System will work. I assume that's why it's opened prior to Identify System in the instuctions and then closed.

[sandeep_raman]

thats right, there is a daily system identification task which is enabled by default and the next time it runs on the esx node smh link may not show up. it would be interesting to know what is the security concern if 2301 port is left open

/srh

[sandeep_raman]

forgot to mention, its a pretty cool mini how-to in the link you provided :)

[Brian Proteau]

Yes. I found that link in the VMware community forums.

I may check that with the author about his concerns about that port. He may just be super security consious or paranoid however; if it works with it closed, I don't mind leaving it closed.

Regarding your question about "re-identfication" with the port closed, I'll leave it as is over the next few days to see if anything changes.

I'll post results here.

[Santhosh Ramesh]

Are you using the installer script to install the 8.0x agents package on ESX 3.5? This script takes care of opening all the required ports to enable communication...

[Brian Proteau]

Yes I'm using the script. The original issue appears to be an abnormality. Since my intitial 8.0X installation, I've done several 8.0X installations on ESX 3.5 servers and all have worked without requiring the additional steps outlined above.