Tanti Technology

My photo
Bangalore, karnataka, India
Sandeep Kumar | Founder, Tanti Technologies At Tanti Technologies, I share practical knowledge, hands-on tutorials, and real-world solutions across Python, SQL, Docker, Kubernetes, CI/CD, AWS, Azure, Machine Learning, Generative AI, and Agentic AI. My mission is to simplify complex technologies and provide actionable insights that help developers, engineers, and businesses learn faster, build better, automate smarter, and innovate with confidence. 🚀 Learn • Build • Automate • Innovate Follow Tanti Technologies for practical technology insights and next-generation AI solutions.

Friday, 8 November 2013

How to migrating to AIX 6.1 with nimadm?



Here I have provided the steps in simplest way in the Interview perspective. If you are familiar with AIX and NIM, you can understand the below steps very easily.

1. Need Nim Master server with the 6.1 version --> "oslevel -s"

2. Master having alt_disk package installed  --> "lslpp -l bos.alt....'

3.  LPP and SPOT should be in high level (OS ver = 6.1) --> "lsnim -c resources"

4. NIMADMVG should create on the NIM master server --> "lsvg -l nimadmvg"

5. Nim master should have the space --> "check space = df -gt"

6. Client needs to define with the master --> "smitty nim"

7. Take mksysb backup of the target client server --> "mksysb"

8. RSH should be working --> "chsubserver -a -v shell -p tcp6 -r inetd"

9. Addtional disk needs to be there --> "lspv"

10. Build /etc/niminfo on the client server using --> "niminit -a master= -a name=

11. nimadm –j -c -s -l -d -Y

    FYI- The below steps are occurred while we executing the "nimadm" command

11.a) Alt disk created on the target server.
11.b) Cache FS has been created on the Nim server.
11.c) RSH has been enabled.
11.d) System config has been saved.
11.e) Migrating the package (lpp) to the new higher version.
11.f) Post Migration has been checked.
11.g) Boot logical volume has been created.
11.h) Sync the migrated higher version package from NIM server to target server.
11.i) Remove the cache filesystem on the nim server.
11.j) Bootlist has been initiated.
11.k) Clean up process has been initiated.

12. change bootlevel --> "bootlist" and reboot --> shutdown -Fr and confirm --> "oslevel -s"

13. disable the RSH  --> "chsubserver -d -v shell -p tcp6 -r inetd"

No comments:

Post a Comment