Some IP's Not Visible

[mark@bongo.net]

We configured our VM with two network cards, but deleted one. After that (not sure it wasn't doing it before though) we found that some network addresses on our network cannot be found. The addresses are on a different subnet, VPN'ed. We can ping them from other machines. We've never had this problem before.

When I deleted the card and discovered the problem, I noticed the network script for the old card was still there - so I deleted it - and that seemed to fix the problem. I could see the missing nodes. But now, they're disappearing again.

[root@localhost network-scripts]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000
link/ether 00:50:56:82:6f:1d brd ff:ff:ff:ff:ff:ff
[root@localhost network-scripts]# ls
ifcfg-ens160 ifdown-ippp ifdown-routes ifup ifup-ipv6 ifup-ppp ifup-tunnel
ifcfg-lo ifdown-ipv6 ifdown-sit ifup-aliases ifup-isdn ifup-routes ifup-wireless
ifdown ifdown-isdn ifdown-Team ifup-bnep ifup-plip ifup-sit init.ipv6-global
ifdown-bnep ifdown-post ifdown-TeamPort ifup-eth ifup-plusb ifup-Team network-functions
ifdown-eth ifdown-ppp ifdown-tunnel ifup-ippp ifup-post ifup-TeamPort network-functions-ipv6
[root@localhost network-scripts]#

Here's an example:

[root@localhost network-scripts]# ping 192.168.114.23
PING 192.168.114.23 (192.168.114.23) 56(84) bytes of data.
From 10.200.0.34 icmp_seq=1 Destination Host Unreachable
From 10.200.0.34 icmp_seq=2 Destination Host Unreachable
From 10.200.0.34 icmp_seq=3 Destination Host Unreachable
From 10.200.0.34 icmp_seq=4 Destination Host Unreachable
^C
--- 192.168.114.23 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4002ms
pipe 4
[root@localhost network-scripts]# ping 192.168.114.22
PING 192.168.114.22 (192.168.114.22) 56(84) bytes of data.
From 10.200.0.34 icmp_seq=1 Destination Host Unreachable
From 10.200.0.34 icmp_seq=2 Destination Host Unreachable
From 10.200.0.34 icmp_seq=3 Destination Host Unreachable
From 10.200.0.34 icmp_seq=4 Destination Host Unreachable
^C
--- 192.168.114.22 ping statistics ---
6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 5002ms
pipe 4
[root@localhost network-scripts]# ping 192.168.114.21
PING 192.168.114.21 (192.168.114.21) 56(84) bytes of data.
64 bytes from 192.168.114.21: icmp_seq=1 ttl=253 time=18.6 ms
64 bytes from 192.168.114.21: icmp_seq=2 ttl=253 time=17.4 ms
64 bytes from 192.168.114.21: icmp_seq=3 ttl=253 time=18.5 ms
64 bytes from 192.168.114.21: icmp_seq=4 ttl=253 time=22.3 ms
64 bytes from 192.168.114.21: icmp_seq=5 ttl=253 time=18.2 ms
64 bytes from 192.168.114.21: icmp_seq=6 ttl=253 time=21.4 ms
64 bytes from 192.168.114.21: icmp_seq=7 ttl=253 time=17.7 ms
64 bytes from 192.168.114.21: icmp_seq=8 ttl=253 time=20.0 ms
^C
--- 192.168.114.21 ping statistics ---
9 packets transmitted, 8 received, 11% packet loss, time 8012ms
rtt min/avg/max/mdev = 17.400/19.313/22.307/1.670 ms
[root@localhost network-scripts]#

These are all smart devices on the same subnet in close physical proximity to each other.

[mark@bongo.net]

Not sure yet, but I found that the node wasn't defined in DNS (I'm not the system administrator!). It -seems- to be working now.