Server not responding to ping after IP address change
by ochocobull from LinuxQuestions.org on (#5RNZ1)
Good afternoon I have a strange issue and I am sure a pretty easy fix but I am beating my head against the wall here.
I have to CentOS 7.9 servers that I setup with no problems encountered. I set them up originally with static IP address and they were able to ping the work as they normally would. At this time they would respond to pings.
I had to change the IP addresses to work with a different networking scheme but kept everything on the same network. When I did this the servers stopped responding to pings but everything else worked as it should. I can SSH into the servers and they can ping every other device on the network including the default gateway. Not sure what the problem is but I am assuming it has something to do with default routes but when I run the command "ip r" i get what I think should be the correct routes. Results are shown below. Just an FYI the reason there are two routes is that we have setup DRDM on these two machines but this problem existed even before we did that.
ip r
default via 10.xx.xx.1 dev em3 proto static metric 100
default via xxx.xxx.xxx.1 dev em2 proto static metric 101
xx.xx.xx.0/24 dev em3 proto kernel scope link src xx.xx.xx.xx metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
xxx.xxx.xxx.0/24 dev em2 proto kernel scope link src xxx.xxx.xxx.xxx metric 101
Printout from file /etc/sysconfig/network-scripts/ifcfg-em3 for reference
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="em3"
UUID="e3fcdd70-191b-463b-8f95-61855db4ffc3"
DEVICE="em3"
ONBOOT="yes"
IPADDR="10.xx.xx.xx"
PREFIX="24"
GATEWAY="10.xx.xx.1"
DNS1="xxx.xxx.xxx.xx"
DNS2="8.8.8.8"
IPV6_PRIVACY="no"
I have also changed the IP address back to the original addresses they were before thinking this might be a routing issue but got the same results. Not sure were else to look. Sorry for the easy question and if you need anything from me I would be happy to provide it. This isn't an emergency in anyway more of an annoyance actually. Thanks for all the help and have a great day.
I have to CentOS 7.9 servers that I setup with no problems encountered. I set them up originally with static IP address and they were able to ping the work as they normally would. At this time they would respond to pings.
I had to change the IP addresses to work with a different networking scheme but kept everything on the same network. When I did this the servers stopped responding to pings but everything else worked as it should. I can SSH into the servers and they can ping every other device on the network including the default gateway. Not sure what the problem is but I am assuming it has something to do with default routes but when I run the command "ip r" i get what I think should be the correct routes. Results are shown below. Just an FYI the reason there are two routes is that we have setup DRDM on these two machines but this problem existed even before we did that.
ip r
default via 10.xx.xx.1 dev em3 proto static metric 100
default via xxx.xxx.xxx.1 dev em2 proto static metric 101
xx.xx.xx.0/24 dev em3 proto kernel scope link src xx.xx.xx.xx metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
xxx.xxx.xxx.0/24 dev em2 proto kernel scope link src xxx.xxx.xxx.xxx metric 101
Printout from file /etc/sysconfig/network-scripts/ifcfg-em3 for reference
TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="em3"
UUID="e3fcdd70-191b-463b-8f95-61855db4ffc3"
DEVICE="em3"
ONBOOT="yes"
IPADDR="10.xx.xx.xx"
PREFIX="24"
GATEWAY="10.xx.xx.1"
DNS1="xxx.xxx.xxx.xx"
DNS2="8.8.8.8"
IPV6_PRIVACY="no"
I have also changed the IP address back to the original addresses they were before thinking this might be a routing issue but got the same results. Not sure were else to look. Sorry for the easy question and if you need anything from me I would be happy to provide it. This isn't an emergency in anyway more of an annoyance actually. Thanks for all the help and have a great day.