📖 ~1 min read
Table of contents
Symptom & Impact
VIO client LPAR sees no vSCSI/vNIC disks and lsdev shows Defined for vscsiN.
Environment & Reproduction
Triggered after VIOS reboot, mapping change, or partition profile mismatch.
Root Cause Analysis
VIO server has not exported the backing device or mapping was removed.
Quick Triage
On VIOS, run lsmap -all to see vhostN to client mappings.
Step-by-Step Diagnosis
On client, run cfgmgr and lsdev -Cc disk to confirm vSCSI devices.
Solution – Primary Fix
On VIOS, run mkvdev -vdev hdiskN -vadapter vhostM to (re)create the mapping.
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
For SR-IOV/SEA, recheck profile via HMC and re-activate the LPAR if needed.
Verification & Acceptance Criteria
Client LPAR sees expected vSCSI/vNIC devices in Available state.
Rollback Plan
Remove the new mapping with rmvdev -vdev hdiskN on VIOS to revert.
Prevention & Hardening
Document mappings via lsmap -all snapshots and review after each VIOS update.
Related Errors & Cross-Refs
Related to HMC profile drift, MPIO path loss, and SEA failovers.
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 PowerVM VIOS administration guide for AIX 7.2 clients.
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.
