📖 ~1 min read
Table of contents
Symptom & Impact
System WPAR fails to start with 0960-xxx errors or stays in ‘D’ defined state.
Environment & Reproduction
After WPAR config edit, mobility move, or filesystem change.
lswpar
startwpar wpar01
errpt | head
Root Cause Analysis
WPAR filesystems, network, or specfile are inconsistent with the global definition.
Quick Triage
Inspect WPAR state and underlying mounts.
lswpar -L wpar01
lsnfsexp
lsdev | grep wpar01
Step-by-Step Diagnosis
Check WPAR specfile and global system filesets for compatibility.
lswpar -X wpar01 > /tmp/wpar01.spec
lslpp -L | grep wpar
errpt | head

Solution – Primary Fix
Recreate the WPAR network/filesystem mappings and start it cleanly.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
stopwpar -F wpar01
rebootwpar wpar01
lswpar wpar01

Solution – Alternative Approaches
Reimport the WPAR from a specfile or rebuild it as a new system WPAR.
Verification & Acceptance Criteria
lswpar shows ACTIVE state and applications inside WPAR respond.
lswpar
clogin wpar01
lssrc -a
Rollback Plan
Stop the WPAR and rollback specfile changes if instability appears.
stopwpar -F wpar01
mkwpar -f /tmp/wpar01.spec.bak
lswpar
Prevention & Hardening
Version control WPAR specfiles and align lpp_source with global system.
Related Errors & Cross-Refs
Related to network virtualization issues, NFS mounts, and RBAC role denial.
Related tutorial: View the step-by-step tutorial for aix-7.2.
View all aix-7.2 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
IBM AIX 7.2 WPAR administration documentation.
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.