1 Answer
- Newest
- Most votes
- Most comments
0
This has been solved.
Turns out that there was a script that on startup changed the default gateway to that of the loadbalancer for some reason. This meant that even a simple ping to 1.1.1.1 or 8.8.8.8 would return zero packets.
route -v was able to display this to me.
It was then a case of establishing which of the start up script had been altered to do this and commenting out the changes to the network configuration and then rebooting a checking ping/routing table to see if the network issues were resolved.
Then it was a simple case of attaching an EIP to each host and upgrading via YUM.
answered 4 years ago
Relevant content
- asked 2 years ago
- asked 2 months ago
- asked 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 9 months ago