This post is more than 5 years old
5 Posts
0
18418
January 17th, 2012 07:00
Management Plugin - Test fail with "No Route to Host"
Hi
I have installed the "Dell Management Plug-in for VMware vCenter" version 1.0.1.175 (just upgraded from 1.0.1.72) but are having trouble when registering my host in the Connection Profile using the vSphere Client.
Here's what I do:
In the vSphere Client go to Home->Management->Management Center->vserver.domain.com and create the "Connection Profile" entering my OMSA Credentials and iDRAC Credentials for 1 associated host. When I selec the "Test Connection" of my profile the "OMSA Agent" returns "Pass" but the iDRAC Protocol returns "Fail - No route to host".
Here is a snippet from the spectre_VCenter_app.log
Time[2012-01-17 14:33:03,116] TP-Processor3 INFO com.dell.pg.spectre.common.protocol.wsman.HttpConnection Message[192.168.155.11 Doing HTTP Connect(Addressing)...]
Time[2012-01-17 14:33:03,118] TP-Processor3 INFO com.dell.pg.spectre.common.protocol.wsman.HttpConnection Message[Spectre: Skipping SSL Certificate checking for this connection.]
Time[2012-01-17 14:33:03,131] TP-Processor3 INFO com.dell.pg.spectre.common.protocol.wsman.HttpConnection Message[192.168.155.11 Doing HTTP Connect Successful]
Time[2012-01-17 14:33:03,293] TP-Processor3 DEBUG com.dell.pg.spectre.common.protocol.wsman.HttpConnection Message[HTTP response: OK]
Time[2012-01-17 14:33:03,304] TP-Processor3 INFO com.dell.pg.spectre.business.profile.ConnectionProfileMgrImpl Message[System ID obtained for 192.168.155.11=565]
Time[2012-01-17 14:33:03,311] TP-Processor3 DEBUG com.dell.pg.spectre.common.protocol.wsman.SpectreAuthenticator Message[Checking if cache needes Flushing]
Time[2012-01-17 14:33:03,311] TP-Processor3 DEBUG com.dell.pg.spectre.common.protocol.wsman.SpectreAuthenticator Message[Putting Authenticator for URL: https://192.168.155.44:443/wsman]
Time[2012-01-17 14:33:03,311] TP-Processor3 INFO com.dell.pg.spectre.common.protocol.wsman.HttpConnection Message[Certificate checking is disabled for this connection.]
Time[2012-01-17 14:33:03,311] TP-Processor3 INFO com.dell.pg.spectre.common.protocol.wsman.WSManBaseCommand Message[Firing command com.dell.pg.spectre.common.protocol.command.wsman.GetIdracId]
Time[2012-01-17 14:33:03,481] TP-Processor3 INFO com.dell.pg.spectre.common.protocol.wsman.HttpConnection Message[192.168.155.44 Doing HTTP Connect(Management)...]
Time[2012-01-17 14:33:06,482] TP-Processor3 DEBUG com.dell.pg.spectre.common.protocol.wsman.HttpConnection Message[Caught IO exception: No route to host]
Time[2012-01-17 14:33:09,484] TP-Processor3 ERROR com.dell.pg.spectre.business.profile.ConnectionProfileMgrImpl Message[OutofBand Connection Test failed: com.dell.pg.spectre.commons.exception.RuntimeSpectreException: No route to host]
192.168.155.11 is the ESXi 5.0 Host Management address
192.168.155.46 is the plugin appliance (host x.11)
192.168.155.44 is the iDRAC address (host x.11)
I really don't get it, the "No Route to host" error message seems like a very general description...
There should be no problem to connect to 192.168.155.44 whatsoever, no firewalls in this mix.
When connecting to the iDRAC (192.168.155.144) using a browser there is no problem, I can logon and
all stuff is there.
Anyone got a clue of how I should proceed with this problem (It was the same problem in the 1.0.1.72 release)?
Btw, I'm a real newbie to virtualization so It's not unlikely that I've made a general error when setting things up, but I
have followed all guide's very carefully...
/Thomas
No Events found!



TompaP
5 Posts
1
January 23rd, 2012 06:00
Hello Kong
Yes, I could ping the iDRAC as well as log on to it using a browser. I have only one host in the environment so could not try on other hosts.
However, in another support issue (SCSI Controller did not recognize disks other the Dell) I was told to upgrade firmware's, which I did. The NIC-firmware, PERC-firmware and OS-Drivers were updated (iDRAC6 already had the latest version, 1.80).
I don't know if any of the firmware updates was the solution or the fact that I needed to reboot the host was the solution, but after patch/reboot both tests finished with a "Pass".
So problem solved, I'm happy again :-)
Thanks for your help.
/Thomas
Kong Yang
180 Posts
0
January 17th, 2012 19:00
Hi Thomas,
Sorry, I have not seen that particular situation in my lab. Please open a support case # so that it can go through the proper support channels. I will also ask the engineering team to see if they have encountered this in their testing.
Regards,
KongY@Dell
Kong Yang
180 Posts
0
January 20th, 2012 18:00
Thomas,
From the dev. team, please check the following:
1) Can you ping the iDRAC from the appliance? Maybe a firewall is blocking the call from going through.
2) Is this happening only on this one particular iDRAC or other ones as well?
KongY@Dell
DELL-Matthew P
70 Posts
0
January 23rd, 2012 10:00
Thomas, you will want to ping the idrac from the appliace not the browser.
Use Alt-F2 and log in as the “readonly” user with your administrator password.
Kong Yang
180 Posts
0
January 23rd, 2012 10:00
Thomas,
I'm glad that you found viable closure :) Thank you for sharing your experience with the community.
Regards,
Kong
Jimmy Wick
1 Rookie
•
49 Posts
0
August 7th, 2022 22:00
'No Route to Host' denotes a network problem, usually one which shows up when the server or host is not responding. This may happen because of network issues or because of an inappropriate setup.
Regards,
J Wick