Cannot discover ESX server in HP-SIM

[Jason Morrin]

Please can someone help me with a query I have. I have built two ESX servers which were built seperately . The first server was discovered in HP-SIM without any problems however I cannot seem to discover the second server at all . I ran a discovery using the same IP Range which seems to process and detect mahines in that range however once it finishes I cannot see any sign of it in All Systems ? I have unzipped and installed the hp agents the same way on both ESX hosts and just dont know why only one server is being discovered. I can ping the management station from the host and vice versa. Please can someone help me out here I am at a total loss now ??

[Rob Buxton]

See a similar post. Check that port 2301 has been opened. Use esxcfg-firewall -q
You should also see ports 2381 & 280 opened.
the command
esxcfg-firewall -o 2301,tcp,in,HPSIM
will open 2301 which is not opened by the install but is needed for identification to work on the new 8.0.0a agents.
The other thing to recheck is the snmpd.conf file.

[Jason Morrin]

Hi Rob , thanks for the reply , I ran the esxcfg-firewall query command and got the following on both ESX hosts.

Opened ports:

hpim : port 2381 tcp.in
sim-cert : port 280 tcp.out

Do these ports not get opened by default at the start of the agent installation ? Either way I ran the command to open the ports and ran another discovery , still no sign of the second ESX server in All Systems in SIM ?

I checked and compaired both snmpd.conf files and used vi to slightly edit the undiscovered ESX box. (The only difference was an extra management station IP entry and an entry for localhost which was set to 127.0.0.1 on the discovered system) I then restarted the snmp service from the following directory /etc/rc.d/init.d (hope that is the correct way of restarting the snmp service). I still cannot get this system to be recognised in insight manager after attempting this , its very frustrating , have you got any other suggestions ? Thanks for your help on this matter

[Jason Morrin]

Just thought I would mention that the agents I have installed are: hpmgmt-7.9.1-vmware3x.tgz

[Robert Brooks_1]

I don't think it should make a difference, but what version of ESX? I've successfully used the V7.9.1 agents on ESX V3.5. I haven't tried using the V8 agents.


-- Rob

[danail denev]

Hi Jason,

is the SMH work fine locally on the VMware Server?

You can temporary switch the firewall on the VMware off, to check if it is the cause of the problem.

[Jason Morrin]

yeah I have also installed ESX 3.5 Update 1

I have ran out of ideas , both hosts are identical and the hp agents were installed the exact same way , it does seem to be taking a bit longer to run the discoveries and it says its processed 2 items , are there any other locations in SIM that they may be located ??

[sandeep_raman]

perhaps the esx server is discovered as unknown/unmanaged and in the general settings for discovery, unknown/unmanaged option is unchecked. hence its not listed in sim.

mxnode -ld esx server ip - this command will list the server if it is discovered in sim

if it does and is discovered as unknown/unmanaged,
match the discovery settings like the one i have attached and discover the node. now it would list the server as unknown/unmanaged

let me know how it goes

/srh

[Rob Buxton]

The ports 2381 and 280 get opened by the install.
You need to manually open 2301.
HPSIM : port 2301 tcp.in
sim-cert : port 280 tcp.out
hpim : port 2381 tcp.in
I have the above and identification works.
Some have recommended re-closing 2301 after the identification. I haven't as I don't believe it's a risk here.

[Jason Morrin]

Hi all ,

I have tried all the suggestions but I just wanted to point out that I didnt need manually open up the additional port on the first ESX server?

SRH , I had tried ticking the unknown and unmanaged options as you suggested previously but never ticked the "any system that matches the above filter" option , I set this option and ran another discovery . I really thought this was going to work but Im afraid it did not.

Here is the mxnode info from both the non-working and working systems , any ideas ?

C:\>mxnode -ld 172.23.10.41
System name: 172.23.10.41
Host name: 172.23.10.41
IP addresses: 172.23.10.41
OS name:
OS revision:
OS revision text:
OS vendor:
Protocols:
GUID: 000000163504bca400000003000000e7
Device type: Unmanaged
Device subtype: None
Model:
Added by: MCNAMARA_DOMAIN\administrator
Added on: 27-Jun-2008 16:26:24
Modified by: winscribe\mxadmin
Modified on: 27-Jun-2008 16:26:24
Monitoring: Not suspended
OS description:
Preferred node name: 172.23.10.41
System description:
Location:
System name locked: No
System attributes locked: No
discovery.source: Ping
(Begin Contract and Warranty data)
(Asset Data)
Asset number:
Product ID:
Customer Serial number:
Country code: IE
Entitlement type:
Entitlement ID:
Obligation ID:
(End Contract and Warranty data)
Contract Warranty data monitoring: Not set


C:\>mxnode -ld 172.23.10.42
System name: gbh-esx01
Host name: gbh-esx01.mcnamara_domain.local
IP addresses: 172.23.10.42
OS name: LINUX
OS revision: 3
OS revision text: Kernel Release: 2.4.21-47.0.1.ELvmnix
OS vendor:
Protocols: SNMP:1.0 SSH:SSH-2.0-OpenSSH_3.6.1p2
GUID: 000000163504bca400000003000000e3
Device type: Cluster
Device subtype: None
Model: ProLiant DL380 G5
Added by: winscribe\mxadmin
Added on: 27-Jun-2008 18:02:56
Modified by: winscribe\mxadmin
Modified on: 03-Jul-2008 16:07:04
Monitoring: Not suspended
OS description: Linux - VMware ESX Server
Preferred node name: gbh-esx01
System description: Linux gbh-esx01.mcnamara.local 2.4.21-47.0.1.ELvmnix #1 Tue
Mar 18 18:07:00 PDT 2008 i686
Location: room1 (edit snmpd.conf)
System name locked: No
System attributes locked: No
compaq.security.ssosupport: 0
hp.SIM: true
discovery.source: Ping
(Begin Contract and Warranty data)
(Asset Data)
Asset number:
Product ID: 430029Ã 425
Customer Serial number:
Country code: IE
Entitlement type:
Entitlement ID:
Obligation ID:
(End Contract and Warranty data)
Contract Warranty data monitoring: Not set

[Jason Morrin]

Just thought I would mention that I have turned off the firewall using the allow commands for both incoming and outgoing as well

[Ervinck Kevin]

two other suggestions:

-make sure the dns-name of your ESX is entered in DNS, try to add it via Discovery 'Manual' and add the hostname of the ESX server.

try to close and re-open the firewall rule for port 2301 tcp. (-c and -o).

[wendling]

Hello,
I have exactly the same probleme. Has somebody found a solution for this?
(Esx 3.5 hpsim agent 810)

Thank's
Gérard

[Derek_56]

Jason,

I'd say you are still having some issue with the firewall (or maybe network ACL?) SIM isn't seeing *ANY* protocols from that host: "Protocols: " Even if the homepage isn't getting through, you should at least see SNMP or OpenSSH in that list.
Either that or it cannot communicate with the HOST at all. What status is the node in SIM? Is it a blue question mark, green for normal or red critical?

[marsh_1]

jason,

to follow up dereks post, you mention in the original question that you are able to ping each way , if your default discovery setting is for icmp do you at least have an entry in hp sim for that ip address ?
forgetting agents for the moment, you can test snmp connectivity by using snmptrap etc on the linux side, i take it you have'nt changed the default ports 161/162 ? and any of a number of freeware snmp monitors for windows.
if that goes ok you know that the system is being blocked by an hp sim setting/filter, it's not network/firewall related and that normal connectivity means such as icmp and snmp are working ok (double check snmp strings both ends)
do you have any entries in the hp sim logs for this system.


good luck