Network service fails to start after reboot

📖 ~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

Server boots without expected IP address, causing application and monitoring outages.

Environment & Reproduction

RHEL 7 using network.service or NetworkManager; issue appears after NIC rename or config edit.

Root Cause Analysis

Incorrect DEVICE/NAME in ifcfg files, missing ONBOOT=yes, or stale udev naming assumptions.

Quick Triage

Run ip a, systemctl status network, and verify files under /etc/sysconfig/network-scripts/.

Step-by-Step Diagnosis

Use journalctl -u network -b and nmcli dev status to map configured profiles to active NIC names.

Solution – Primary Fix

Align ifcfg-* DEVICE with actual interface, set ONBOOT=yes, then systemctl restart network.

Solution – Alternative Approaches

Manage interface via NetworkManager profile and disable legacy scripts where policy allows.

Verification & Acceptance Criteria

Interface auto-starts on reboot and remote SSH reconnects without manual intervention.

Rollback Plan

Restore previous ifcfg backups and restart network service to return known-good state.

Prevention & Hardening

Template NIC configs with predictable naming and validate changes in staging before rollout.

Related Errors & Cross-Refs

Bringing up interface failed, No suitable device found, device not present.

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

RHEL 7 Networking Guide, nmcli documentation, systemd unit troubleshooting.