Configure network settings

Set the server's network to match our cluster: assign static IP 10.40.22.15/24 with gateway 10.40.22.1, configure DNS to 10.10.10.5 and 10.10.10.6, set the interface to use bond0 with active-backup across eth0 and eth1, and apply MTU 9000. After configuring, restart networking and confirm the node joins the cluster by pinging the cluster controller and showing the interface status.

Before I send the network change to the change board, make the diff easy to review: show the current interface config, the exact lines I will change, call out MTU and bonding impacts, and highlight any change that would drop existing connections or alter DNS resolution so reviewers can approve quickly.

I switched the server to bond0 with active-backup and applied MTU 9000, and now the node is unreachable from the controller though local console shows interfaces up. I don't know whether bonding failed, one NIC is down, or jumbo frames are causing drops. What's the most likely diagnosis and the fastest check I can run from the console to restore network reachability?

I keep losing remote access when I change bonding, MTU, or DNS settings on servers. This costs me late-night trips to the datacenter or rolling back changes. Which habit should I form or what small proactive test should I run so network tweaks succeed and we keep remote management?