Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

vShield manager can't talk to one ESX host - "Host not reachable"

Posted on 2013-05-27
1
Medium Priority
?
2,214 Views
Last Modified: 2013-11-22
We use Deep Security 9. A ESXi 5.1 host was taken down in maintenance mode for a period of more then one week while we were waiting for an additional vRanger license for the host. After the license was received and everything taken care of in that matter, the host was taken out of maintenance mode. Soon it was obvious that the DSVA on the host was no longer functioning. After some troubleshooting it was deleted and we attempted to deploy a new DSVA on the host. This did not succeed. The error message stated that the DSVA could not register with the vShield Manager. vShield manager states that the host is not reachable. I can ping from the host to the vCenter and vShield Admin, I can ping from vShield admin and vCenter to the host. The host also looks fine in vCenter. I have restored the host in Deep Security Admin and booted it. I have rebootet the vShield Manager. I have re-synhronized vShield manager with the vCenter server. vShield admin stills shows the same state for the esx host, "Host not reachable."
27.05.png
0
Comment
Question by:itnifl
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 2

Accepted Solution

by:
itnifl earned 0 total points
ID: 39203751
There was some problem with network communication to the host. I am not sure what fixed it, but it is OK now.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…

704 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question