Article ID: 122341, created on Jul 12, 2014, last review on Feb 23, 2016

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers
  • Virtuozzo hypervisor
  • Virtual Automation


Hardware Node is shown as Offline in Virtual Automation Management Node.

Virtual Environments list is not available for the server as well.

At the same time, the host is available remotely, and containers and virtual machines are running properly.


There is no connectivity between VA MN and VA Agent on the hardware node.


Check that there is no incomplete VA MN/Agent upgrade.

Make sure that VA Agent is running on that hardware node:

~# pvaagent status
pvaagentd (pid  784701) is running...

Check that all necessary ports are not blocked by firewall on both the node and on the VA MN.

List of ports that have to be open on both hosts can be found in the following article.

To test connectivity, the following commands can be used:

  • from MN to HN on the port 4434:

    ~# openssl s_client -connect VZ_HN:4434 -cipher ADH-AES256-SHA
  • from NH to MN on the port 4534:

    ~# openssl s_client -connect VA_MN:4534 -cipher ADH-AES256-SHA
  • also, ensure that the source and target IP addresses in these connections are the same using netstat command
  • if connections can be established, the IP addresses match each other in the connections and the state is not available still, try restarting the services:

    ~# pvamn restart     ## VA MN
    ~# pvaagent restart  ## VZ HN

Search Words

node unavailable

node is grayed out

hardware node not recognized

node unmanageable

containers are not listed

PVCL105 in down state vm's are running



a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 319940068c5fa20655215d590b7be29b 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF