RHEL 7 NetworkManager overwriting static ifcfg network settings

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Static IP changes revert unexpectedly after reboot or network service restart. Systems may come online with wrong gateway or DNS, causing outages for dependent applications and management access.

Environment & Reproduction

Occurs when administrators edit ifcfg files directly while NetworkManager manages the connection profile. Reproduce by manual file edits followed by systemctl restart NetworkManager or interface bounce.

Root Cause Analysis

NetworkManager treats profile data as authoritative and can regenerate ifcfg content. Manual edits outside nmcli or nm-connection-editor may be overwritten during state reconciliation.

Quick Triage

Check whether interface is NM-managed, list profiles with nmcli, and compare active profile parameters to ifcfg files. Review journalctl -u NetworkManager for profile rewrite events.

Step-by-Step Diagnosis

Capture current profile, reconcile static IP, gateway, and DNS values, and verify autoconnect behavior. Determine whether legacy network service scripts conflict with NetworkManager ownership.

Solution – Primary Fix

Apply network configuration via nmcli, align ifcfg with profile settings, then reload or restart through systemctl. If legacy service tooling is required, disable conflicting management paths carefully.

Solution – Alternative Approaches

Lock configuration with automation, migrate fully to nmcli-managed profiles, or in controlled legacy environments disable NetworkManager for specific interfaces and use service network workflows.

Verification & Acceptance Criteria

After reboot, interface settings must persist exactly and route/DNS checks must match baseline. journalctl should show no unexpected profile rewrites and dependent services should reconnect successfully.

Rollback Plan

Restore backed-up ifcfg and profile exports, restart network stack, and confirm reachability. Revert management method changes if unexpected dependencies break connectivity.

Prevention & Hardening

Adopt one network management method per interface, enforce change templates, and validate post-restart state. Maintain firewalld and SELinux network policy alignment with static addressing plans.

Related Errors & Cross-Refs

Related incidents include intermittent DNS failure after reboot and route disappearance on interface renew. Cross-reference nmcli profile ownership and legacy network service hooks.

Related tutorial: View the step-by-step tutorial for rhel-7.

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Use RHEL 7 NetworkManager and nmcli documentation, plus internal network standard operating procedures. Include examples for static profile persistence and rollback controls.