📖 ~1 min read
Table of contents
Symptom & Impact
Bonded interface fails to activate at boot with no carrier reported.
Environment & Reproduction
Common after kernel upgrades or driver firmware updates on bonded NICs.
Root Cause Analysis
Slave interfaces have wrong connection.master or mismatched MII status.
Quick Triage
Run nmcli connection show and nmcli device status.
Step-by-Step Diagnosis
Inspect /proc/net/bonding/bond0 for slave states.

Solution – Primary Fix
Reassign slaves with nmcli connection modify and bring bond up.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Switch bond mode to active-backup temporarily for diagnostic clarity.
Verification & Acceptance Criteria
ip link show bond0 shows up state and carrier is present.
Rollback Plan
Revert to previous bond config from /etc/NetworkManager/system-connections.
Prevention & Hardening
Pin bond options in configuration management and monitor mii_status.
Related Errors & Cross-Refs
Linked to switch port LACP and VLAN trunking issues.
Related tutorial: View the step-by-step tutorial for centos-stream-10.
View all centos-stream-10 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
NetworkManager bonding tutorial and team driver docs.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.