No
YesInformation
If a Hardware Node has several IP addresses, PVA uses the first one on the list for its communications.This article describes how to configure PVA Agent to use a particular IP address for communications via XML API.
To make PVA Agent use a particular IP address for Backup, Restore or other types of PVA Agent internal traffic, follow the below steps.
Resolution
-
Determine the IP address to be used as the primary PVA 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 127.0.0.1/8 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 192.168.55.33/24 brd 192.168.55.255 scope global eth0
inet 10.55.67.1/24 brd 10.55.67.255 scope global eth0:0
inet6 fe80::22cf:30ff:fe1d:462e/64 scope link
valid_lft forever preferred_lft forever
-
Locate PVA Agent configuration file, e.g.,
/var/opt/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~>.*.<\/~>192.168.55.33<\/~' -i /var/opt/pva/agent/etc/vzagent.conf | grep primary_address
-
Restart PVA Agent:
pvaagent restart
...............
<default_remote>
<default_timeout>360000</default_timeout>
<connect_timeout>20</connect_timeout>
<startup_timeout>10</startup_timeout>
<child_connect_timeout>20</child_connect_timeout>
<child_inactivity_timeout>300</child_inactivity_timeout>
</default_remote>
<primary_address>192.168.55.33</primary_address>
......................
NOTE: This example describes PVA Agent configuration on a Linux node, the solution applies to Windows nodes as well.
Additional information
For more information regarding PVA Agent troubleshooting on Windows and Linux, refer to this article:6981: "PVA troubleshooting"