The Telegraf Agent installation fails when the VM IP is 172.17.x.x.

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• The installation of the VMware Aria Operations Telegraf Agent fails on VMs where the endpoint VM's IP is in the 172.17.x.x subnet.

Environment

VMware Aria Operations 8.x

Cause

This issue is occurs when the endpoint VM's subnet is 172.17.x.x, and the default docker IP in VMware Aria Operations Cloud Proxy is 172.17.0.1.

Resolution

To resolve this issue, change the IP 172.17.0.1 to any available IP not in 172.17.x.x subnet range.

Note: Any address can be used, as long as it differs from the endpoint VM's 172.17.x.x subnet.

1. Log into the Cloud Proxy VM as root via SSH or Console.
2. Run the following command to open /etc/docker/daemon.json in a text editor:

vi /etc/docker/daemon.json

3. Using the arrow keys, navigate to the end of the "live-restore" line.
4. Type i to enter insert mode, then press Enter to insert a new line.
5. In the new line, enter the following:

 "bip": "new IP with subnet mask"

Note: The file should now look similar to the following example:
{
 "iptables": true,
 "log-opts": {"max-size": "200m", "max-file": "1"},
 "log-level": "info",
 "live-restore": true,
 "bip": "192.168.0.1/22"
}

6. Press ESC to exit insert mode.
7. Run the following command to save the changes and quit the text editor:

:wq

8. Run the following command to restart the docker service:

systemctl restart docker

9. Run the following command to reboot the Cloud Proxy VM:

reboot

10. Once the Cloud Proxy VM has completely rebooted, log back into the Cloud Proxy as root via SSH or Console.
11. Run the following command to verify that the httpd-north service is running:

systemctl status httpd-north

Note: If the service failed to start, the new IP will need to be added to /etc/httpd-north/httpd.conf.

1. Run the following command to open /etc/httpd-north/httpd.conf in a text editor:

vi /etc/httpd-north/httpd.conf

2. Type i to enter insert mode.
3. Update with new IP in all the occurrences of 172.17.0.1
4. Press ESC to exit insert mode.
5. Run the following command to save the changes and quit the text editor:

:wq

6. Run the following command to start the httpd-north service:

systemctl start httpd-north

12. Run the following commands to ensure that iptables and iproute are updated with the new IP address:

• ifconfig
• iptables -t nat -nvL
• netstat -rn

13. Run the following command to ensure ucp-controlplane-saltmaster is running:

docker ps

Note: ucp-controlplane-saltmaster should be listed in the output.

14. Wait 10-15 minutes for salt master to establish communication channels with minions.
15. From the endpoint VM, run the following commands to ensure ports 4505, 4506, and 443 of the Cloud Proxy VM are reachable:

Windows VM

Test-NetConnection Cloud-Proxy-FQDN -Port port_number

 

Linux VM

bash -c "</dev/tcp/Cloud-Proxy-FQDN/port_number"

Note: Replace port_number with one of the port numbers you want to check.

 

Example: bash -c "</dev/tcp/Cloud-Proxy-FQDN/4505"

 

You can now perform the agent install.