Zenoss ZenTech Community

So I've noticed a problem with Core 5.0.6 and changing IPs.
Installation works like it should, I can get everything up and running and monitoring just fine; but when I change the IP on the host, Zenoss stops being able to ping anything at all.

Here is my process after installation and initial configuration are complete:
1. systemctl stop serviced
2. change host IP and restart network
3. edit /etc/hosts to update the IP
4. systemctl start serviced
5. Add the new IP to the hosts tab in control center, and make sure RabbitMQ, zenmail, zensyslog and zentrap are all pointing to the "new" host

All the processes then start fine and are running and passing the health check. However, when I add or ping any device other than the host itself, Zenoss cannot ping anything. I can ping from the CentOS command line, but once I attach to Zenoss.core, I can't ping anything other than the host IP.

Anyone seen this before Is there another config file I might need to adjust I've been messing around in Zenoss.core but have yet to find a fix.

Subject:	Since nobody has offered any
Author:	[Not Specified]
Posted:	2015-10-21 13:58

Since nobody has offered any insight, and this is also occurring on 5.0.7, I have created a ticket on jira.zenoss.com:
https://jira.zenoss.com/browse/ZEN-20604

Subject:	Issue Resolved
Author:	[Not Specified]
Posted:	2015-12-11 11:30

I figured this out finally. It wasn't a Zenoss issue persay, more of a lack of Docker understanding. In order for Docker containers to have network connectivity beyond the Linux host itself, IP forwarding must be enabled. It turns out, when I used nmtui to change the IP of my host, the IP forwarding was being disabled. To check this, run the sysctl net.ipv4.ip_forward command. 0 means disabled, 1 means enabled. To enable, run:sysctl -w net.ipv4.ip_forward=1

Subject:	5.0.6 Changing Host IPs
Author:	[Not Specified]
Posted:	2015-09-30 15:52

5.0.6 Changing Host IPs