📖 ~1 min read
Table of contents
Symptom & Impact
`systemctl status wickedd` reports failed and interfaces stay down after reboot.
Environment & Reproduction
Seen on SLES 16 upgrades where `/etc/sysconfig/network/ifcfg-*` had stale STARTMODE values.
Root Cause Analysis
Conflicting NetworkManager presence or invalid ifcfg keys block wickedd startup.
Quick Triage
Run `wicked show all` to see configured vs operational interfaces.
Step-by-Step Diagnosis
Inspect `journalctl -u wickedd -u wicked –since -1h` for parse errors.

Solution – Primary Fix
Disable NetworkManager (`systemctl disable –now NetworkManager`) and run `wicked ifup all`.
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
Migrate to NetworkManager fully and remove `wicked` if the deployment standard allows it.
Verification & Acceptance Criteria
All ifcfg-defined interfaces report `up` in `wicked show all` and ping succeeds.
Rollback Plan
Restore the previous `/etc/sysconfig/network` snapshot via snapper if configs were broken.
Prevention & Hardening
Pick one network stack per host (wicked OR NetworkManager) in your build profile.
Related Errors & Cross-Refs
Frequently paired with `dracut` initrd warnings about missing network modules.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SLES 16 networking with wicked reference.
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.