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.

Thursday, 7 November 2013

NIM - RTE Installation

RTE Installation


Run Time Environment Install (RTE) install of a NIM client system using the manual initiation method. It can be used to install AIX on a system where AIX is not currently installed. Default is to install the contents of the BOS.autoi bundle; the user can specify additional bundles or file sets to be installed.

Required Steps:

1)      Define a client on NIM Master.
2)      Prepare NIM Master to supply RTE install resources to a client system
3)      Initiate a manual install from NIM client

Requires a minimum set of resources:
lpp_source
spot

1)      Define a client on NIM Master.


 Make the entry of the client IP and hostname on the /etc/hosts file of the NIM server
            # cat /etc/hosts

10.135.0.173        PACS_CDR_KOLKATA_HA
(IP Address)   (Machine Name)

      Define the machine.
# smit nim








 







PACS_CDR_KOLKATA_HA:
class          = machines
type           = standalone
connect        = shell
platform       = chrp
netboot_kernel = mp
if1            = PACS_NIM PACS_CDR_KOLKATA_HA 0
cable_type1    = tp
Cstate         = BOS installation has been enabled
prev_state     = ready for a NIM operation
Mstate         = not running
boot           = boot
mksysb         = PACS_CDR_KOLKATA_HA_mksysb
nim_script     = nim_script
spot           = PACS_CDR_KOLKATA_HA_SPOT
control        = master

Client Machine is ready for installation on the NIM Server






2. Prepare NIM Master to supply RTE install resources to a client system



#smit nim_bosinst
Select a TARGET for the operationà 

PACS_CDR_KOLKATA_HA machines       standalone

Select the installation TYPE   Ã 
rte- Install from installation images
mksysb - Install from a mksysb
spot- Install a copy of SPOT resource

Select rte –Install from Installation images

The lpp_source to use for the installation

PACS_CDR_KOLKATA_HA_LPPSOURCE     resources       lpp_source

The SPOT to use for the installation

PACS_CDR_KOLKATA_HA_SPOT     resources       spot

Select the MKSYSB to use for the installation

PACS_CDR_KOLKATA_HA_mksysb     resources       mksysb






 


# lsnim -l PACS_CDR_KOLKATA_HA
PACS_CDR_KOLKATA_HA:
class          = machines
type           = standalone
connect        = shell
platform       = chrp
netboot_kernel = mp
if1            = PACS_NIM PACS_CDR_KOLKATA_HA 0
cable_type1    = tp
Cstate         = BOS installation has been enabled
prev_state     = ready for a NIM operation
Mstate         = not running
boot           = boot
mksysb         = PACS_CDR_KOLKATA_HA_mksysb
nim_script     = nim_script
spot           = PACS_CDR_KOLKATA_HA_SPOT
control        = master

# cat /etc/bootptab | grep -i tftpboot
           PACS_CDR_KOLKATA_HA:bf=/tftpboot/PACS_CDR_KOLKATA_HA:ip=10.135.0.173:ht=ethernet:sa=10.135.0.178:sm=255.255.255.0:

Client Machine is ready for installation on the NIM Server


3. Initiate a manual install from NIM client 

Starting the Installation on client:

            Take the console of the machine through HMC

            Start the client LPAR on SMS mode
            Select --- 2.   Setup Remote IPL (Initial Program Load)

  

Select --- NIC Adapters  ( e.g  2.  Port 1 - IBM 4 PORT PCIe 10/10  U78C0.001.DBJP321-P2-C1-T1  e41f13fafcf1 )

Select Internet Protocol Version.        1.   IPv4 - Address Format 123.231.111.222 

Select Network Service.   1.   BOOTP


Set Network parameters IP Parameters


Ping Success – Means nim server is accessible from the client, hence cable and lan is correct.

 if Ping Success Start the machine from network boot
           
 Select Boot Options



Multiboot -- 1.   Select Install/Boot Device


Select Device Type -->  6.   Network


Select Network Service. -->   1.   BOOTP


Select Device --> DBJP321-P2-C1-T1

Select Task -->  2.   Normal Mode Boot

BOOTING----------->>>>>>>>>>>>


You can change the disk selections form the above 2nd options --    2 Change/Show Installation Settings and Install


    1 Disk(s) where you want to install ...... hdisk1        - Note if mksysb image is taken from un mirrored root vg, else we have to select 2 disks               


Select the disk
            >>>  1  hdisk0   08-00-00        286102   none            Yes    No
            >>>  2  hdisk1   09-00-00        286102   none            Yes    No

Select -->  >>> 0 Install with the settings listed above.




Installation Running, check the same on Server
bash-3.2# lsnim -l PACS_CDR_KOLKATA_HA
PACS_CDR_KOLKATA_HA:
   class          = machines
   type           = standalone
   connect        = shell
   platform       = chrp
   netboot_kernel = mp
   if1            = PACS_NIM PACS_CDR_KOLKATA_HA 0
   cable_type1    = tp
   Cstate         = Base Operating System installation is being performed
   prev_state     = BOS installation has been enabled
   Mstate         = in the process of booting
   info           = BOS install 16% complete : 12% of mksysb data restored.
   boot           = boot
   image_data     = PACS_CDR_KOLKATA_HA_image
   mksysb         = PACS_CDR_KOLKATA_HA_mksysb
   nim_script     = nim_script
   spot           = PACS_CDR_KOLKATA_HA_SPOT
   cpuid          = 00F6F6B04C00
   control        = master
   Cstate_result  = success
bash-3.2#


No comments:

Post a Comment