This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
aix:nim_command [2021/12/07 11:06] manu |
aix:nim_command [2024/06/18 14:20] (current) manu |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== NIM operations ===== | ===== NIM operations ===== | ||
| + | |||
| + | - **Preview install on client for specific package:** | ||
| + | <cli prompt='>'> | ||
| + | [root@aix06] /root> nimclient -o cust -a lpp_source=LPP-AIX72TL1SP2 -a filesets=bos.rte.install -a installp_flags=-pacNYgX | ||
| + | </cli> | ||
| + | |||
| + | - **Update all packages from NIM client:** | ||
| + | <cli prompt='>'> | ||
| + | [root@aix06] /root> nimclient -o cust -a lpp_source=LPP-AIX72TL1SP2 -a fixes=update_all -a installp_flags=-acNYgX | ||
| + | </cli> | ||
| - **Boot a nim client on a ethernet interface using vlan tagging:** | - **Boot a nim client on a ethernet interface using vlan tagging:** | ||
| Line 61: | Line 71: | ||
| <cli prompt='#'> | <cli prompt='#'> | ||
| # nim -o cust -a fixes=update_all -a lpp_source=aix7100-05-08-2114 spot_7100-05-06-2028 | # nim -o cust -a fixes=update_all -a lpp_source=aix7100-05-08-2114 spot_7100-05-06-2028 | ||
| + | </cli> | ||
| + | |||
| + | - **Define a SPOT from a directory that previously had a SPOT installed in it** | ||
| + | <cli prompt='#'> | ||
| + | # /usr/lpp/bos.sysmgt/nim/methods/m_mkspot -o -a server=server -a location=location -a source=no spotname | ||
| </cli> | </cli> | ||
| Line 193: | Line 208: | ||
| lpp_aix7100-02-03_base lpp_source | lpp_aix7100-02-03_base lpp_source | ||
| </cli> | </cli> | ||
| + | |||
| + | ===== Changing the CPUID of NIM Master and NIM Clients after LPM ===== | ||
| + | |||
| + | |||
| + | ==== On the NIM Client: ==== | ||
| + | |||
| + | This document explains how to change your NIM Master or NIM Clients CPUID after you have moved it to new HW to match the system's new CPUID. | ||
| + | |||
| + | To check what CPUID the Master has for the NIM Client we can run the following command on the NIM Master: | ||
| + | <cli prompt='#'> | ||
| + | root@sentinel(/)# lsnim -l instlab163 | grep -i cpuid | ||
| + | |||
| + | cpuid = 00FF48B55C00 <---- wrong/old CPUID | ||
| + | </cli> | ||
| + | |||
| + | To check the current CPUID of the NIM Client: | ||
| + | <cli prompt='#'> | ||
| + | root@instlab163(/)# uname -a | ||
| + | AIX instlab163 2 7 00F84BE54C00 | ||
| + | </cli> | ||
| + | |||
| + | To change the CPUID on the NIM Master’s client definition to match with the actual CPUID of the nim client: | ||
| + | <cli prompt='#'> | ||
| + | root@sentinel(/)#nim -o change -a cpuid=00F84BE54C00 instlab163 | ||
| + | root@sentinel(/)# lsnim -l instlab163 | grep -i cpuid | ||
| + | cpuid = 00F84BE54C00 <---- correct CPUID | ||
| + | </cli> | ||
| + | |||
| + | We can verify connectivity: | ||
| + | <cli prompt='#'> | ||
| + | root@sentinel(/)# nim -o lslpp instlab163 | grep bos.mp | ||
| + | bos.mp64 7.2.4.0 COMMITTED Base Operating System 64-bit | ||
| + | </cli> | ||
| + | ==== On the NIM Master: ==== | ||
| + | |||
| + | To check the current system CPUID: | ||
| + | <cli prompt='#'> | ||
| + | root@sentinel(/)# uname -a | ||
| + | AIX sentinel 2 7 00FB43B94C00 | ||
| + | </cli> | ||
| + | |||
| + | To check the NIM Master definition: | ||
| + | <cli prompt='#'> | ||
| + | root@sentinel(/)# lsnim -l master | grep -i cpuid | ||
| + | cpuid = 00FB43C85B00 ß old/wrong CPUID | ||
| + | </cli> | ||
| + | |||
| + | To change the CPUID: | ||
| + | <cli prompt='#'> | ||
| + | # /usr/lpp/bos.sysmgt/nim/methods/m_chattr -a cpuid="new CPUID" master | ||
| + | </cli> | ||
| + | |||
| + | Example: | ||
| + | <cli prompt='#'> | ||
| + | root@sentinel(/)# /usr/lpp/bos.sysmgt/nim/methods/m_chattr -a cpuid="00FB43B94C00" master | ||
| + | </cli> | ||
| + | |||
| + | To verify: | ||
| + | <cli prompt='#'> | ||
| + | root@sentinel(/)# lsnim -l master | grep -i cpuid | ||
| + | cpuid = 00FB43B94C00 | ||
| + | </cli> | ||
| + | |||
| + | ===== Automaticaly restore AIX LPAR ===== | ||
| + | |||
| + | ==== Steps to install mksysb from NIM ==== | ||
| + | |||
| + | === On the NIM server === | ||
| + | |||
| + | Allocate required resource | ||
| + | <cli prompt='#'> | ||
| + | # nim -o reset -a force=yes $CLIENT_NAME | ||
| + | # nim -Fo deallocate -a subclass=all $CLIENT_NAME | ||
| + | # nim -o bos_inst -a source=mksysb -a mksysb=$MKSYSB -a spot=$SPOT -a accept_licenses=yes -a fb_script=$SCRIPTFB -a bosinst_data=$BOSINST_DATA -a boot_client=no $CLIENT_NAME | ||
| + | </cli> | ||
| + | |||
| + | Monitoring | ||
| + | <cli prompt='#'> | ||
| + | # nim -o showlog -a log_type=boot $CLIENT_NAME > $LOG | ||
| + | </cli> | ||
| + | |||
| + | === On the HMC === | ||
| + | |||
| + | Now boot the partition using a specific IP, and also give the NIM server IP to boot | ||
| + | <cli prompt='#'> | ||
| + | # Syntax | ||
| + | To retrieve a MAC address: | ||
| + | lpar_netboot -M -n [-v] [-x] [-f] [-i] [-A] -t ent [-D -s Speed-d Duplex -S Server -G Gateway -C Client -K | ||
| + | subnetmask] partition name partition profile manage system | ||
| + | |||
| + | To perform a network boot: | ||
| + | lpar_netboot [-v[-x] [-f] [-i] [-g args] [-A -D | [-D] -l phys_loc | [-D] -m maddress] -t ent [-D -s Speed-d | ||
| + | Duplex -S Server -G Gateway -C Client -K subnetmask partition_name partition_profile manage_system | ||
| + | |||
| + | </cli> | ||
| + | |||
| + | |||