📖 ~1 min read
Table of contents
Symptom & Impact
nim -o bos_inst stalls and client never reaches BOS install menu.
Environment & Reproduction
Network installs across VLANs or firewalls drop bootp/tftp.
Root Cause Analysis
NIM relies on bootp, tftp, and rsh/nfs ports being open.
Quick Triage
Tail /var/adm/ras/nimlog and check lssrc -s tftpd.
Step-by-Step Diagnosis
Use tcpdump on en0 of master for bootp request from client MAC.

Solution – Primary Fix
Re-run nim -Fo reset client then nim -o bos_inst with -a no_client_boot=no.
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
Boot client from CD/USB and point to NIM via SMS menu.
Verification & Acceptance Criteria
Client reaches BOS menu and installp progresses.
Rollback Plan
Revert NIM resource allocation with nim -o deallocate.
Prevention & Hardening
Document firewall rules: 67/68 UDP, 69 UDP, 111, NFS.
Related Errors & Cross-Refs
Often co-occurs with rpc.bootparamd or portmap restart needs.
Related tutorial: View the step-by-step tutorial for aix-7.3.
View all aix-7.3 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
IBM Docs: NIM Administration Guide.
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.