Yes I can ping itself and in zenoss it was showing the server itself being the only device up. Out of all of the services, only the zenmail / zenpop was stopped. Zenmail i figured would have died as it couldn't talk to the mail server.

I noticed that when I attacked to the zope service, I couldn't ping anything but when I was on the command line before attaching to the service I could. I hadn't a clue about attaching to the service container before running an upgrade to the system yesterday. So there's that for learning something new. After finding out that I couldn't ping inside the container, I restarted docker from the command line and it started working. I could then ping my main switch gateways. Which is shdown below. Before it would fail the pings. 

Now I rebooted the server after I started having this problem and it didn't correct the issue. So I'm not sure how restarting docker would have fixed it....

root@zenoss [~] : serviced service attach zope/0

[root@639fccad075a /]# ping 10.58.0.1

PING 10.58.0.1 (10.58.0.1) 56(84) bytes of data.

64 bytes from 10.58.0.1: icmp_seq=1 ttl=254 time=0.900 ms

64 bytes from 10.58.0.1: icmp_seq=2 ttl=254 time=0.775 ms

64 bytes from 10.58.0.1: icmp_seq=3 ttl=254 time=0.734 ms

^C

--- 10.58.0.1 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 2001ms

rtt min/avg/max/mdev = 0.734/0.803/0.900/0.070 ms

[root@639fccad075a /]# ping 10.32.0.2

PING 10.32.0.2 (10.32.0.2) 56(84) bytes of data.

64 bytes from 10.32.0.2: icmp_seq=1 ttl=63 time=0.732 ms

64 bytes from 10.32.0.2: icmp_seq=2 ttl=63 time=0.429 ms

^C

--- 10.32.0.2 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1000ms

rtt min/avg/max/mdev = 0.429/0.580/0.732/0.153 ms

[root@639fccad075a /]#