Article ID: 112904, created on Nov 28, 2011, last review on Jun 17, 2016

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


If a Hardware Node has several IP addresses, VA uses the first one on the list for its communications.

If virtualization nodes has both frontnet and backnet IPs, VA Agent on one node may fail to communicate with other nodes unless preferred IP is set, e.g.:

1391441908: can not read reply from destination node
1391441908: can't connect to source node ($IP_ADDRESS) : can not read reply from destination node

This article describes how to configure VA Agent to use a particular IP address for communications via XML API.

NOTE: In case the node is a part of VA infrastructure and is managed through VA web interface, the IP address for communications is defined by the IP, used during node registration. It is advised to register the nodes via internal IPs to separate the traffic.


To make VA Agent use a particular IP address for Backup, Restore or other types of VA Agent internal traffic, follow the below steps.

Determine the IP address to be used as the primary VA Agent IP address, e.g.:

[hwnode@03:51:08][~]# ip a l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 20:cf:30:1d:46:2e brd ff:ff:ff:ff:ff:ff
    inet brd scope global eth0
    inet brd scope global eth0:0
    inet6 fe80::22cf:30ff:fe1d:462e/64 scope link
       valid_lft forever preferred_lft forever

Locate VA Agent configuration file (/var/opt/pva/agent/etc/vzagent.conf or /vz/pva/agent/etc/vzagent.conf)

Replace primary_address section in vzagent.conf with the desired IP address, e.g., for Linux nodes:

[hwnode@04:20:23][~]# sed '/<primary_address>/s~>.*.<\/~><\/~' -i /var/opt/pva/agent/etc/vzagent.conf

Restart VA Agent:

# pvaagent restart

NOTE: The resulting section of "vzagent.conf" should look similar to this:


NOTE2: This example describes VA Agent configuration on a Linux node, but the solution applies to Windows nodes as well.

For more information regarding VA Agent troubleshooting on Windows and Linux, refer to this article: PVA troubleshooting

Related topics

1457 I cannot migrate a VE to another node. How do I fix this?

Search Words

Broken pipe vzsock_send()

Task that performs VPS migration failed

can not read reply from destination node can not read reply from destination node can't connect to source node (xx.xx.xx.xx : can not read reply from destination node

change primary ip pva


main IP address

failed to check client configuration

Failed to connect to backup server: Can't connect: System errors : unauthorized request.

primary IP address

destination failed

d02f9caf3e11b191a38179103495106f 319940068c5fa20655215d590b7be29b 2897d76d56d2010f4e3a28f864d69223 a26b38f94253cdfbf1028d72cf3a498b 0dd5b9380c7d4884d77587f3eb0fa8ef c62e8726973f80975db0531f1ed5c6a2

Email subscription for changes to this article
Save as PDF