Friday, 8 September 2023

Privacy Policy

Privacy Policy for UNIX TECH INFO

At UNIX TECH INFO, accessible from https://unixworld4admin.blogspot.com/, one of our main priorities is the privacy of our visitors. This Privacy Policy document contains types of information that is collected and recorded by UNIX TECH INFO and how we use it.

If you have additional questions or require more information about our Privacy Policy, do not hesitate to contact us.

This Privacy Policy applies only to our online activities and is valid for visitors to our website with regards to the information that they shared and/or collect in UNIX TECH INFO. This policy is not applicable to any information collected offline or via channels other than this website.

Consent

By using our website, you hereby consent to our Privacy Policy and agree to its terms.

Information we collect

The personal information that you are asked to provide, and the reasons why you are asked to provide it, will be made clear to you at the point we ask you to provide your personal information.

If you contact us directly, we may receive additional information about you such as your name, email address, phone number, the contents of the message and/or attachments you may send us, and any other information you may choose to provide.

When you register for an Account, we may ask for your contact information, including items such as name, company name, address, email address, and telephone number.

How we use your information

We use the information we collect in various ways, including to:

Provide, operate, and maintain our website
Improve, personalize, and expand our website
Understand and analyze how you use our website
Develop new products, services, features, and functionality
Communicate with you, either directly or through one of our partners, including for customer service, to provide you with updates and other information relating to the website, and for marketing and promotional purposes
Send you emails
Find and prevent fraud

Log Files

UNIX TECH INFO follows a standard procedure of using log files. These files log visitors when they visit websites. All hosting companies do this and a part of hosting services' analytics. The information collected by log files include internet protocol (IP) addresses, browser type, Internet Service Provider (ISP), date and time stamp, referring/exit pages, and possibly the number of clicks. These are not linked to any information that is personally identifiable. The purpose of the information is for analyzing trends, administering the site, tracking users' movement on the website, and gathering demographic information.

Google DoubleClick DART Cookie

Google is one of a third-party vendor on our site. It also uses cookies, known as DART cookies, to serve ads to our site visitors based upon their visit to www.website.com and other sites on the internet. However, visitors may choose to decline the use of DART cookies by visiting the Google ad and content network Privacy Policy at the following URL – https://policies.google.com/technologies/ads

Our Advertising Partners

Some of advertisers on our site may use cookies and web beacons. Our advertising partners are listed below. Each of our advertising partners has their own Privacy Policy for their policies on user data. For easier access, we hyperlinked to their Privacy Policies below.

Google
https://policies.google.com/technologies/ads

Advertising Partners Privacy Policies

You may consult this list to find the Privacy Policy for each of the advertising partners of UNIX TECH INFO.

Third-party ad servers or ad networks uses technologies like cookies, JavaScript, or Web Beacons that are used in their respective advertisements and links that appear on UNIX TECH INFO, which are sent directly to users' browser. They automatically receive your IP address when this occurs. These technologies are used to measure the effectiveness of their advertising campaigns and/or to personalize the advertising content that you see on websites that you visit.

Note that UNIX TECH INFO has no access to or control over these cookies that are used by third-party advertisers.

Third Party Privacy Policies

UNIX TECH INFO's Privacy Policy does not apply to other advertisers or websites. Thus, we are advising you to consult the respective Privacy Policies of these third-party ad servers for more detailed information. It may include their practices and instructions about how to opt-out of certain options.

You can choose to disable cookies through your individual browser options. To know more detailed information about cookie management with specific web browsers, it can be found at the browsers' respective websites.

CCPA Privacy Rights (Do Not Sell My Personal Information)

Under the CCPA, among other rights, California consumers have the right to:

Request that a business that collects a consumer's personal data disclose the categories and specific pieces of personal data that a business has collected about consumers.

Request that a business delete any personal data about the consumer that a business has collected.

Request that a business that sells a consumer's personal data, not sell the consumer's personal data.

If you make a request, we have one month to respond to you. If you would like to exercise any of these rights, please contact us.

GDPR Data Protection Rights

We would like to make sure you are fully aware of all of your data protection rights. Every user is entitled to the following:

The right to access – You have the right to request copies of your personal data. We may charge you a small fee for this service.

The right to rectification – You have the right to request that we correct any information you believe is inaccurate. You also have the right to request that we complete the information you believe is incomplete.

The right to erasure – You have the right to request that we erase your personal data, under certain conditions.

The right to restrict processing – You have the right to request that we restrict the processing of your personal data, under certain conditions.

The right to object to processing – You have the right to object to our processing of your personal data, under certain conditions.

The right to data portability – You have the right to request that we transfer the data that we have collected to another organization, or directly to you, under certain conditions.

If you make a request, we have one month to respond to you. If you would like to exercise any of these rights, please contact us.

Children's Information

Another part of our priority is adding protection for children while using the internet. We encourage parents and guardians to observe, participate in, and/or monitor and guide their online activity.

UNIX TECH INFO does not knowingly collect any Personal Identifiable Information from children under the age of 13. If you think that your child provided this kind of information on our website, we strongly encourage you to contact us immediately and we will do our best efforts to promptly remove such information from our records.

Changes to This Privacy Policy

We may update our Privacy Policy from time to time. Thus, we advise you to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately, after they are posted on this page.

Our Privacy Policy was created with the help of the Privacy Policy Generator.

Contact Us

If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us.

Wednesday, 16 August 2023

How to recover the Failed/Missing Paths in AIX

We may get the alerts/incidents that disk path has been Failed. When you got such kind of issues don't worry. Most of the cases disk paths will be recovered automatically.

If they were not recovered recover the failed/missing paths in AIX follow the below process.

To verify the failed or missing paths.

# lapath | grep -v Enabled
Failed hdisk9 fscsi0
Failed hdisk9 fscsi0

# lspath -l hdisk9
Failed hdisk9 fscsi0
Failed hdisk9 fscsi0
Enabled hdisk9 fscsi1
Enabled hdisk9 fscsi1

Run the configuration manager, sometime it will fix the issue. Still you are seeing failed paths then try to remove and re-enable.

# cfgmgr
# lspath -l hdisk9

To remove the path.
# rmpath -l hdisk9 -p fscsi0
paths Defined

Verify the path status whether it is removed or not. It should be in defied state.

# lspath -l hdisk9
Defined hdisk9 fscsi0
Defined hdisk9 fscsi0
Enabled hdisk9 fscsi1
Enabled hdisk9 fscsi1

Next delete the path.

# rmpath -d -l hdisk9 -p fscsi0
paths Deleted

Verify the path status whether it is deleted or not.

# lspath -l hdisk9
Enabled hdisk9 fscsi1
Enabled hdisk9 fscsi1

Run the configuration manager, mostly it will fix the issue in this step. If not re-enable the paths using chpath command.

# cfgmgr

# lspath -l hdisk9
Enabled hdisk9 fscsi0
Enabled hdisk9 fscsi0
Enabled hdisk9 fscsi1
Enabled hdisk9 fscsi1

To enable the paths, execute the below command.

# chpath -l hdisk9 -p fscsi0 -s enable

Still paths are not recovered, follow the below steps.

1. Check the VIOS mappings.

2. Check if any errors with physical FC

3. Check with Storage Team.

Thanks for reading this post, any queries please write a comment

Wednesday, 8 December 2021

AIX OS Migration from AIX 7.1 to AIX 7.2 using NIMADM through NIMSH service

In this post describes AIX migration from AIX 7.1 from AIX 7.2 using nimsh. AIX migration tool now supports nimsh service(subsystem). You no longer to use the rsh on your NIM clients. So rsh facility is dead.

AIX uses NIM Service Handler (NIMSH) to eliminate the need for rsh services during NIM client communication. The NIM client daemon (NIMSH) uses reserved ports 3901 and 3902, and it installs as part of the bos.sysmgt.nim.client fileset.

NIMADM is a facility to move the server from one operating system(AIX 7.1) to another operating system(AIX 7.2). The nimadm is an utility having more advantages to compare CD/DVD migration. In CD/DVD migration method will override /tmp, means whatever the data exist inside /tmp will removed be in new OS version.

NIMADM takes a copy of client server rootvg to spare disk(hdisk1) and simultaneously migrate the server to new OS version. This can be done without downtime and no disruption to client. mksysb backup is optional.

Minimum downtime: Once OS migration completed, downtime required for reboot the client to take into new OS version(AIX7.2). It will take 30-45min per the system.

No Outage : NIMADM is online migration, during the migration process no impact to applications and database.

Easy to Rollback: If applications/Databases are not running as easier, it very simple to rollback to old level. Just change the bootlist and reboot client server. NIMADM fails in middle whatever the changes are made in altinst_rootvg. It won't impact to original rootvg.

NIM Master take the workload, this will reduce the overhead on client

I have tested this new functionality in test environment and it is working fine. The following AIX versions and levels were installed:

NIM Master : aixnim01
OSLEVEL of NIM Master : 7200-05-01-2038
NIM Client : lpar02
OSLEVEL of NIM Client : 7100-05-07-2037
lpp_source : AIX72TL03_LPP
SPOT : AIX72TL03_SPOT
Spare disk : hdisk1

Pre-Checks and Implementation on NIM Master :

1. NIM master running AIX7.2 or latest level of Technology Level/Service Pack.
# oslevel -s

2. Same level of bos.alt_disk_install.rte fileset must be installed on NIM master rootvg and SPOT
# lslpp -l|grep -i bos.alt_disk_install.rte

3. NIM resources lpp_source and SPOT level must be same or lower version of NIM Master OS level. We won't migrate higher than NIM Master.
# lsnim -l AIX72TL03_LPP
# lsnim -l AIX72TL03_SPOT

4. Get the new disk from SAN with same or higher size of NIM master rootvg. To create nimadmvg.
# mkvg -y nimadmvg -s 256 hdisk1

5. Update ip address and client name in /etc/hosts
# vi /etc/hosts

6. Define nim client machine.
# smit nim_mkmac

7. Inactivate the rsh, if it is active. Refresh inetd subsystem.
# lssrc -ls inetd
# vi /etc/inetd.conf (Here comment the shell and save the file)
# cat /etc/inetd.conf | grep shell
#shell stream tcp6 nowait root /usr/sbin/rshd rshd

# refresh -s inetd

8. bos.alt_disk_install.rte fileset must be installed on NIM master and also in the SPOT.If not you have to add the fileset to SPOT.
# lslpp -l bos.alt_disk_install.rte
# nim -o showres AIX72TL03_LPP | grep -i bos.alt_disk_install.rte (Check on lpp_source)

# nim -o showres AIX72TL03_SPOT | grep -i bos.alt_disk_install.rte (Check on SPOT)

# nim -o cust -a filesets=bos.alt_disk_install.rte -a lpp_source=AIX72TL03_LPP AIX72TL03_SPOT (add fileset to SPOT)

Pre-Checks and Implementation on NIM Client :

9. Verify oslevel, missing filesets and commit applied filesets.
# oslevel -s
# lppchk -vm3
# instfix -i | grep ML
# instfix -i | grep SP
# installp -c all (commit applied filesets)

10. Check hardware, software and firmware levels must be support to required AIX level which you migrating.
# lsmcode -c

11. Get spare disk with same or higher size of client rootvg. If rootvg mirrored break it and use it for migration.
# lspv

If rootvg mirrored :

# bootinfo -b
# mirrorvg rootvg hdisk1
# reducevg -df rootvg hdisk1
# chpv -c hdisk1
# bootlist -m normal -o
# bootlist -ad /dev/hdisk0
# bootlist -m normal -o

12. lv names must be less than 11 characters.
# lsvg -l rootvg

13. Inactivate the rsh, if it is active. Refresh the inetd subsystem.

# lssrc -ls inetd
# vi /etc/inetd.conf (Here comment the shell and save the file)
# cat /etc/inetd.conf | grep shell
#shell stream tcp6 nowait root /usr/sbin/rshd rshd

# refresh -s inetd

14. Start the nimsh subsystem, if it is not active.
# lssrc -s nimsh
# startsrc -s inetd

15. Take the backup of system configuration files like /etc/sendmail.cf , /etc/motd, netstat -rn,vmo -a, ioo -a ...etc

16. Verify the /etc/niminfo file. NIM Master details must updated on this file. If not exist run (#smit nim) and enter NIM master details.

# cat /etc/niminfo
# smit nim (to create /etc/niminfo file)

17. Take the mksysb backup if you want to.

# mksysb -i <destination path>

Run NIMADM Command on NIM Master:

# nimadm -j <nimadmvg> -c <clientname> -s <SPOT> -l <lpp_source> -d <spare disk> -Y

# nimadm -j nimadmvg -c aixnim01 -s AIX72TL03_SPOT -l AIX72TL03_LPP -d hdisk1 -Y

# nimadm -j nimadmvg -c aixnim01 -s AIX72TL03_SPOT -l AIX72TL03_LPP -d hdisk1 -Y >> /tmp/nimadm.log & #### ----> [ To run in background ]

-j VG specified on NIM Master
-c client machine name defined in NIM Master
-l Name of lpp_source defined in NIM Master
-s Name of SPOT defined in NIM Master
-d spare disk for alternate rootvg(altinst_rootvg)
-Y Accept license

Once migration starts cache file systems create the in nimadmvg and removes the after successful migration.

The migration process will takes in 12 phases .The following is the output of 12 phases while migration is going on

Post Migration :

1. After NIMADM completed, check the bootlist and set to hdisk1 (altinst_rootvg).

# bootlist -m normal -o
# bootlist -m normal hdisk5 hdisk0

2. Inform to application/database team to stop applications/database.

3. Reboot the server and once it came up check the oslevel.

# oslevel -s
# shutdown -Fr (It will take few minutes to Power UP)
# oslevel -s
# lppchk -vm3
# instfix -i | grep ML
# instfix -i | grep SP

4. Inform to application/database team to start applications/database

NIMADM 12 Phases :

Initializing the NIM master.

Initializing NIM client aixnim01

Verifying alt_disk_migration eligibility.

Initializing log: /var/adm/ras/alt_mig/aixnim01_alt_mig.log

Starting Alternate Disk Migration.

+-----------------------------------------------------------------------------+

Executing nimadm phase 1.

+-----------------------------------------------------------------------------+

Cloning altinst_rootvg on client, Phase 1.

Client alt_disk_install command: alt_disk_copy -j -M 7.2 -P1 -d "hdisk1"

Calling mkszfile to create new /image.data file.

Checking disk sizes.

LOGICAL_VOLUME= hd11admin

FS_LV= /dev/hd11admin

Creating cloned rootvg volume group and associated logical volumes.

Creating logical volume alt_hd5.

Creating logical volume alt_hd6.

Creating logical volume alt_hd8.

Creating logical volume alt_hd4.

Creating logical volume alt_hd2.

Creating logical volume alt_hd9var.

Creating logical volume alt_hd3.

Creating logical volume alt_hd1.

Creating logical volume alt_hd10opt.

Creating logical volume alt_hd11admin.

Creating logical volume alt_lg_dumplv.

Creating logical volume alt_livedump.

Creating /alt_inst/ file system.

Creating /alt_inst/admin file system.

Creating /alt_inst/home file system.

Creating /alt_inst/opt file system.

Creating /alt_inst/tmp file system.

Creating /alt_inst/usr file system.

Creating /alt_inst/var file system.

Creating /alt_inst/var/adm/ras/livedump file system.

Generating a list of files

for backup and restore into the alternate file system...

Phase 1 complete.

+-----------------------------------------------------------------------------+

Executing nimadm phase 2.

+-----------------------------------------------------------------------------+

Creating nimadm cache file systems on volume group nimadmvg.

Checking for initial required migration space.

Creating cache file system /aixnim01_alt/alt_inst

Creating cache file system /aixnim01_alt/alt_inst/admin

Creating cache file system /aixnim01_alt/alt_inst/home

Creating cache file system /aixnim01_alt/alt_inst/opt

Creating cache file system /aixnim01_alt/alt_inst/tmp

Creating cache file system /aixnim01_alt/alt_inst/usr

Creating cache file system /aixnim01_alt/alt_inst/var

Creating cache file system /aixnim01_alt/alt_inst/var/adm/ras/livedump

+-----------------------------------------------------------------------------+

Executing nimadm phase 3.

+-----------------------------------------------------------------------------+

Syncing client data to cache ...

+-----------------------------------------------------------------------------+

Executing nimadm phase 4.

+-----------------------------------------------------------------------------+

nimadm: There is no user customization script specified for this phase.

+-----------------------------------------------------------------------------+

Executing nimadm phase 5.

+-----------------------------------------------------------------------------+

Saving system configuration files.

Checking for initial required migration space.

Setting up for base operating system restore.

/aixnim01_alt/alt_inst

Restoring base operating system.

Merging system configuration files.

Can not remove the glbd subsystem

WARNING: rmitab failed! Unable to remove "mkatmpvc" entry from /etc/inittab.

WARNING: rmitab failed! Unable to remove "atmsvcd" entry from /etc/inittab.

No such file or directory

/lpp/devices.common.IBM.atm/deinstl/devices.common.IBM.atm.rte.unconfig[76]: /etc/atm.defs: cannot open

sum: Can't open /usr/lib/hal_hfi.o

sum: Can't open /usr/hfi/hal/lib/hal_hfi.o

sum: Can't open /usr/lib/hal_hfi64.o

sum: Can't open /usr/hfi/hal/lib/hal_hfi64.o

Running migration merge method: ODM_merge Config_Rules.

Running migration merge method: ODM_merge SRCextmeth.

Running migration merge method: ODM_merge SRCsubsys.

Running migration merge method: ODM_merge SWservAt.

Running migration merge method: ODM_merge pse.conf.

Running migration merge method: privcmds_mig.

Running migration merge method: privdevs_mig.

Running migration merge method: ODM_merge vfs.

Running migration merge method: ODM_merge xtiso.conf.

Running migration merge method: ODM_merge PdAtXtd.

Running migration merge method: ODM_merge PdDv.

Running migration merge method: convert_errnotify.

Running migration merge method: passwd_mig.

Running migration merge method: login_mig.

Running migration merge method: user_mrg.

Running migration merge method: secur_mig.

Running migration merge method: RoleMerge.

Running migration merge method: methods_mig.

Running migration merge method: mkusr_mig.

Running migration merge method: methods_mig.

Running migration merge method: mkusr_mig.

Running migration merge method: group_mig.

Running migration merge method: ldapcfg_mig.

Running migration merge method: ldapmap_mig.

Running migration merge method: secvarscfg_mig.

Running migration merge method: convert_errlog.

Running migration merge method: ODM_merge GAI.

Running migration merge method: ODM_merge PdAt.

Running migration merge method: merge_smit_db.

Running migration merge method: ODM_merge fix.

Running migration merge method: merge_swvpds.

Running migration merge method: SysckMerge.

Running migration merge method: nscontrol_mig.

+-----------------------------------------------------------------------------+

Executing nimadm phase 6.

+-----------------------------------------------------------------------------+

Installing and migrating software.

Checking space requirements for installp install.

Expanding /aixnim01_alt/alt_inst/usr local filesystem.

Filesystem size changed to 5767168

Expanding /aixnim01_alt/alt_inst/var local filesystem.

Filesystem size changed to 786432

Installing software with the installp installer.

+-----------------------------------------------------------------------------+

Pre-installation Verification...

+-----------------------------------------------------------------------------+

install_all_updates: Initializing system parameters.

install_all_updates: Log file is /var/adm/ras/install_all_updates.log

install_all_updates: Checking for updated install utilities on media.

install_all_updates: Processing media.

install_all_updates: Generating list of updatable installp filesets.

#---------------------------------------------------------------------

# No filesets on the media could be used to update the currently

# installed software.

# Either the software is already at the same level as on the media, or

# the media contains only filesets which are not currently installed.

#---------------------------------------------------------------------

install_all_updates: Checking for recommended maintenance level 7200-03.

install_all_updates: Executing /usr/bin/oslevel -rf, Result = 7200-03

install_all_updates: Verification completed.

install_all_updates: Log file is /var/adm/ras/install_all_updates.log

install_all_updates: Result = SUCCESS

Restoring device ODM database.

+-----------------------------------------------------------------------------+

Executing nimadm phase 7.

+-----------------------------------------------------------------------------+

nimadm: There is no user customization script specified for this phase.

+-----------------------------------------------------------------------------+

Executing nimadm phase 8.

+-----------------------------------------------------------------------------+

Creating client boot image.

bosboot: Boot image is 57345 512 byte blocks.

Writing boot image to client's alternate boot disk hdisk1.

+-----------------------------------------------------------------------------+

Executing nimadm phase 9.

+-----------------------------------------------------------------------------+

Adjusting client file system sizes ...

Adjusting size for /

Adjusting size for /admin

Adjusting size for /home

Adjusting size for /opt

Adjusting size for /tmp

Adjusting size for /usr

Expanding /alt_inst/usr client filesystem.

Filesystem size changed to 5242880

Adjusting size for /var

Adjusting size for /var/adm/ras/livedump

Syncing cache data to client ...

+-----------------------------------------------------------------------------+

Executing nimadm phase 10.

+-----------------------------------------------------------------------------+

Unmounting client mounts on the NIM master.

forced unmount of /aixnim01_alt/alt_inst/var/adm/ras/livedump

forced unmount of /aixnim01_alt/alt_inst/var

forced unmount of /aixnim01_alt/alt_inst/usr

forced unmount of /aixnim01_alt/alt_inst/tmp

forced unmount of /aixnim01_alt/alt_inst/opt

forced unmount of /aixnim01_alt/alt_inst/home

forced unmount of /aixnim01_alt/alt_inst/admin

forced unmount of /aixnim01_alt/alt_inst

Removing nimadm cache file systems.

Removing cache file system /aixnim01_alt/alt_inst

Removing cache file system /aixnim01_alt/alt_inst/admin

Removing cache file system /aixnim01_alt/alt_inst/home

Removing cache file system /aixnim01_alt/alt_inst/opt

Removing cache file system /aixnim01_alt/alt_inst/tmp

Removing cache file system /aixnim01_alt/alt_inst/usr

Removing cache file system /aixnim01_alt/alt_inst/var

Removing cache file system /aixnim01_alt/alt_inst/var/adm/ras/livedump

+-----------------------------------------------------------------------------+

Executing nimadm phase 11.

+-----------------------------------------------------------------------------+

Cloning altinst_rootvg on client, Phase 3.

Client alt_disk_install command: alt_disk_copy -j -M 7.2 -P3 -d "hdisk1"

## Phase 3 ###################

Verifying altinst_rootvg...

Modifying ODM on cloned disk.

forced unmount of /alt_inst/var/adm/ras/livedump

forced unmount of /alt_inst/var

forced unmount of /alt_inst/usr

forced unmount of /alt_inst/tmp

forced unmount of /alt_inst/opt

forced unmount of /alt_inst/home

forced unmount of /alt_inst/admin

forced unmount of /alt_inst

Changing logical volume names in volume group descriptor area.

Fixing LV control blocks...

Fixing file system superblocks...

Bootlist is set to the boot disk: hdisk1 blv=hd5

+-----------------------------------------------------------------------------+

Executing nimadm phase 12.

+-----------------------------------------------------------------------------+

Cleaning up alt_disk_migration on the NIM master.

Cleaning up alt_disk_migration on client aixnim01.

Thanks for reading this Post

Friday, 3 December 2021

BLV Issue 0301-168 bosboot: The current boot logical volume, /dev/, does not exist on /dev/hdisk0.

This Post resolves the below BLV issue. If you got this error while creating/re-creating the boot image on rootvg disk, follow the below steps to resolve the issue.

# bosboot -ad /dev/hdisk0

0516-602 lslv: Logical volume name not entered.

Usage: lslv [-L] [-l | -m] [-n DescriptorPV] LVname

lslv: [-L] [-n DescriptorPV] -p PVname [LVname]

Lists the characteristics of a logical volume.

0301-168 bosboot: The current boot logical volume, /dev/,

does not exist on /dev/hdisk0.

Solution:

1. Check if hd5 logical volume exists on rootvg disk. If rootvg is mirrored, verify both disks.

# lsvg -p rootvg
# lsvg -l rootvg
# lspv -l hdisk0
# lspv -l hdisk1

2. Logical Volume hd5 must be on the 1st PP of the disk.

# lslv -m hd5

3. To save the base customized information and see verbose output. If it shows no boot image found on disk, next we have to remove and re-create the logical volume hd5.

# savebase -v
No boot images found on disk...

4. Remove and re-create the logical volume hd5.

# rmlv hd5

# mklv -y hd5 -t boot -a e rootvg 1 hdisk0

5. Next remove the file ipldevice under /dev and try to create the boot image on disk. If it shows the same error, then we have to boot device information on hdisk0.

# ls -lrt /dev/ipldevice*
# rm /dev/ipldevice
# ln /dev/rhdisk0 /dev/ipldevice

# bosboot -ad /dev/ipldevice ( If you got same error )

6. Verify the boot device information on hdisk0. If it displays a 1 the IPL code in the ROS on the machine running the command is capable of booting from the specified disk. Otherwise, the command displays a 0.

# bootinfo -B hdisk0 ( Show output 1 )
# ln /dev/rhd5 /dev/ipl_blv
# cd /dev ( Same major /minor numbers)

7. Now we got the same minor and major number for hdisk0.

# ls -ld /dev/ipldevice
crw------- 2 root system 13, 0 Oct 31 2019 ipldevice

# ls -ld /dev | grep -i "13, 0"
# ls -l /dev | grep "13, 0"
brw------- 1 root system 13, 0 Dec 03 12:57 hdisk0
crw------- 2 root system 13, 0 Dec 03 06:59 ipldevice
crw------- 2 root system 13, 0 Dec 03 06:59 rhdisk0
#

8. Create boot image on ipldevice. Now it will work and next try to create/ re-create boot images on hdisk0.

# bosboot -ad /dev/ipldevice

bosboot: Boot image is 53276 512 byte blocks.

# bosboot -ad /dev/hdisk0
# bosboot -ad /dev/hdisk1

Thanks for reading this post. Please comment if you like it.

Tuesday, 16 November 2021

System Resource Controller (SRC) in AIX

The full form of SRC is System Resource Controller. By Using SRC we can manage the demons, SRC commands are:

#startsrc ---> To start the Deamons/Services
#stopsrc ---> To stop the Deamon/Services
#lssrc ---> To display the Deamon/Services status.

Demons/Deamons or Services:

Demon is a process or protocal, it is running on the background of the server, the Demons or managed by the SRC commands such as (startsrc, stopsrc and lssrc). We have several deamons on Aix/Unix.

Example:

Network Deamons
Installation Deamon
Error demon
Telenet/SSH demons
NFS Demons

lssrc:

By using lssrc command we can list demons status.

#lssrc -a --> To list the all demons in the system with their status.
#lssrc -g <groupname> --> To display the group of deamons with their status.
#lssrc -g nfs --> To display all NFS group deamons status.
#lssrc -s <Demon> --> To display the single deamon status, or particular demon status.
#lssrc -s biod,

stopsrc:

By using stopsrc we can stop the deamons or services.

#stopsrc -g <groupname> --> To stop the group of deamons at a time.
#stopsrc -s <Deamon> --> To stop the single demon.

startsrc:

By startsrc we can start the Deamons.

#startsrc -g <groupname> --> To start the group of deamons at a time.
#startsrc -s <deamon> --> To start the single demon.

Restart the Deamons:

If we need any deamon restart, we have to stop the deamon and start it.

#refresh -s <demon> --> To refresh the demon

Note:

1) All Deamons are presented on /etc/services file or /etc/inetd.conf configuration files.
2) If any demons are commented (#) on above configuration files, the demons will not work.
3) Except errdemon, all demons are managed by SRC commands.

Wednesday, 30 June 2021

Dual Virtual I/O Server update/upgrade Procedure

This post explains step by step process to update Dual VIO server from one version to new version.VIOS is nothing but Virtual I/O Server.
Use dual VIOS for redundant purpose, suppose VIOS1 gone through any maintenance activity VIOS2 will take the load within fraction of seconds.So there is no much impact to client partitions(AIX,Linux and IBM i)
Tested and successfully completed this VIOS update procedure in our environment. Follow the below steps to update the VIO Server.

1. Take the configuration backup and mksysb or alternate disk back.
2. Identify the Primary and Secondary VIO server and on both VIOS SEA adapters "ha_mode" should be "auto".
3. Identify the VIOS which is in backup mode.(If VIOS2 in backup mode, update VIOS2 first).
4. Break the rootvg mirror and take the clone for quick rollback. If your VIO server with single disk take the mksysb backup.
5. Remove the all interim fixes and commit the filesets in current version.
6. On VIOS2: For safer side change SEA mode to standby and proceed with VIOS update.
7. Mount the packages downloaded NFS filesystem
8. Update the VIO Server using updateios command and wait until it completed. Next reboot the VIO Server.
9. Verify the latest VIOs version and check if any missing packages and re-mirror the rootvg.
10. On VIOS2: Change the SEA adapters mode to "auto" and proceed with other VIOS.
11. On VIOS1: Now move the sea adapters to standby mode.
12. Follow the above step 4,5,7,8 and 9.
13. Now change the SEA adapters mode to "auto".

1. Take the configuration backup and mksysb or alternate disk back.

The viosbr command creates a backup of only the VIOS configuration.
# viosbr -backup -file /tmp/<file name>

Take the mksysb backup for rootvg. It will create entire rootvg backup
# backupios -file <path to NFS location>/<file name> -mksysb

2. Identify the Primary and Secondary VIO server and on both VIOS SEA adapters "ha_mode" should be "auto".For example ent20 and ent21 are SEA adapters.
   Run the below commands on both VIOS.

# lsdev -Cc adapter|grep -i shared

# entstat -d ent20 |grep -i state
# entstat -d ent21 |grep -i state

3. Identify the VIOS which is in backup mode.(If VIOS2 is on backup mode, update VIOS2 first).

4. Break the rootvg mirror and take the clone for quick rollback. If your VIO server with single disk take the mksysb backup.

To break the rootvg mirror and create a clone for quick rollback
$ bootlist -mode normal –ls
$ unmirrorios hdisk1
# migratepv hdisk1 hdisk0     (Run as root user)
$ reducevg -rmlv rootvg hdisk1
$ alt_root_vg -target hdisk1

$oem_setup_env (to get root shell)
# bosboot -ad hdisk0 (using root shell)
# bootlist -m normal hdisk0 hdisk1 (using root shell)

5. Remove the all interim fixes and commit the filesets in current version.

To remove all interim fixes, if any installed.
$ lssw
$ updateios -remove <ifix_LABEL>
Commit existing filesets:
$ updateios –commit

6. On VIOS2: For safer side change SEA mode to standby and proceed with VIOS update.

$ chdev -dev ent20 -attr ha_mode=standby
$ chdev -dev ent21 -attr ha_mode=standby

7. Mount the packages downloaded NFS filesystem.
# mount $nim_server:/nim/$location_of_vios_patches /mnt
# cd /mnt

8. Update the VIO Server using updateios command and wait until it completed. Next reboot the VIO Server.

Run the following command to perform updating VIOS.
$ updateios -accept -install -dev /mnt -> it will install the VIOS patches

Upon successful update completion take a reboot of server   .

$ shutdown -restart

Once server came up, accept the license and check the VIOS version.

$ license -accept
$ ioslevel

9. Verify the latest VIOs version and check if any missing packages and re-mirror the rootvg.

Check consistency of currently installed filesets
# instfix –i | grep ML
# lppchk –v
$ ioslevel
Once everything confirmed, re-mirror the rootvg.

$ extendvg rootvg hdisk1
$ mirrorios hdisk1
$ bootlist -mode normal -ls (to view)
$ oem_setup_env (to get root shell)
# bosboot -ad hdisk1 (using root shell)
# bootlist -m normal hdisk0 hdisk1 (using root shell)
# exit (using root shell, to go back to VIOS shell from root shell)

10. On VIOS2: Change the SEA adapters mode to "auto" and proceed with other VIOS.
$ chdev -dev ent20 -attr ha_mode=auto
$ chdev -dev ent21 -attr ha_mode=auto

Once everything is fine and post-checks completed on VIOS2 then proceed with VIOS1.

11. On VIOS1: Move the sea adapters to standby mode and then proceed with VIOS update.

# lsdev -Cc adapter|grep -i shared

# entstat -d ent20 |grep -i state
# entstat -d ent21 |grep -i state

$ chdev -dev ent20 -attr ha_mode=standby
$ chdev -dev ent21 -attr ha_mode=standby

12. Follow the above step 4,5,7,8 and 9 on VIOS1.

Break the rootvg mirror and take the clone for quick rollback. If your VIO server with single disk take the mksysb backup.
Remove the all interim fixes and commit the filesets in current version.
Mount the packages downloaded NFS filesystem.
Update the VIO Server using updateios command and wait until it completed. Next reboot the VIO Server.
Verify the latest VIOs version and check if any missing packages and re-mirror the rootvg.

13. Now change the SEA adapters mode to "auto" and verify the SEA status.
$ chdev -dev ent20 -attr ha_mode=auto
$ chdev -dev ent21 -attr ha_mode=auto

# entstat -d ent20 |grep -i state
# entstat -d ent21 |grep -i state

Once everything is fine and post-checks completed on VIOS1. Monitor the VIO servers for sometime and Verify if any errors

VIOS Backout/Rollback Procedure :
Change the bootlist and Reboot the server with older version.

#bootlist –m normal hdisk1 hdisk0
#bootlist –m normal –o

#shutdown –Fr now
Once the server is came up, Re-mirror the rootvg .

$ extendvg rootvg hdisk1
$ mirrorios hdisk1
$ bootlist -mode normal -ls (to view)
$ oem_setup_env (to get root shell)
# bosboot -ad hdisk1 (using root shell)
# bootlist -m normal hdisk0 hdisk1 (using root shell)
# exit (using root shell, to go back to VIOS shell from root shell

Thanks for reading this post, any queries please write a comment

Tuesday, 8 June 2021

Take the rootvg backup using Alternate disk

Note: To support this blog.Please click the ads displayed in this Blog.That would be helpful for me.Continue with this post.

This method is useful to take the backup to alternate disk and no impact to original rootvg. We can easily roll back the server just by changing the bootlist.
If rootvg got corrupted or any issues after patching the server , we can easily roll back the server.

Required filesets:

bos.alt_disk_install.boot_images
bos.alt_disk_install.rte
bos.msg.en_US.alt_disk_install.rte

Flags

-B

Would specify not running bootlist after the mksysb or clone. If set, the -r flag cannot be used. Note: The -B and -X flags are mutually exclusive.

-C

Clone rootvg.

-S

Will "put-to-sleep" the volume group. This is used after a volume group "wake-up". (W).

-W disk

Used to "wake-up" a volume group for data access between the rootvg and the alternate disk rootvg.

-v new_volume_group_name disk

Used to rename the alternate disk volume group. This is especially useful when creating multiple alternate disks, on multiple volume groups,and name identification is necessary.

Examples:

To take the clone of rootvg, not change bootlist.

# alt_disk_install -B -C hdisk1

To "wake_up" an original rootvg, after booting from the new alternate disk:

alt_disk_install -W hdisk0

Illustrated Example

# lspv

hdisk0 000040445043d9f3 old_rootvg

hdisk1 00076443210a72ea rootvg

# alt_disk_install -W hdisk0

# lspv

hdisk0 000040445043d9f3 altinst_rootvg

hdisk1 00076443210a72ea rootvg

At this point, the "altinst_rootvg" volume group is varied-on and the /alt_inst file systems will be mounted.

To "put-to-sleep" a volume group that had experienced a "wake-up":

alt_disk_install -S

Illustrated Example

# lspv

hdisk0 000040445043d9f3 altinst_rootvg

hdisk1 00076443210a72ea rootvg

# alt_disk_install -S

# lspv

hdisk0 000040445043d9f3 altinst_rootvg

hdisk1 00076443210a72ea rootvg

The "altinst_rootvg" is no longer varied-on and the /alt_inst file systems are no longer mounted. If it's necessary for the "altinst_rootvg" volume group name to be changed back to "old_rootvg", this can be done with the "-v" flag.

To modify an alt_disk_install volume group name:

alt_disk_install -v alt_disk_432 hdisk2

Illustrated Example

# lspv

hdisk0 00006091aef8b687 rootvg

hdisk1 00000103000d1a78 rootvg

hdisk2 000040445043d9f3 altinst_rootvg

hdisk3 00076443210a72ea altinst_rootvg

hdisk4 0000875f48998649 None

hdisk5 000005317c58000e None

# alt_disk_install -v alt_disk_432 hdisk2

#lspv

hdisk0 00006091aef8b687 rootvg

hdisk1 00000103000d1a78 rootvg

hdisk2 000040445043d9f3 alt_disk_432

hdisk3 00076443210a72ea alt_disk_432

hdisk4 0000875f48998649 None

hdisk5 000005317c58000e None

Process to take the alternate disk backup:

1. If rootvg is mirrored, break the mirror and free up one disk then proceed to take the backup using alternate disk method.

2. Take the alternate disk backup using the command alt_disk_install without changing the bootlist of AIX server.

# alt_disk_install -B -C <hdiskX>

3. Verify the bootlist and boot image created hdiskX.

# bootlist -m normal -o
# ipl_varyon -i

To roll back the server :

1. Verify and Change the bootlist to altinst_rootvg disk(hdiskX).

# bootlist -m normal -o

# bootlist -m normal <hdiskX> hdisk0

2. Reboot the server using alternate disk(altinst_rootvg).

# shutdown -Fr now

3. Once server came back, verify whether it is booted with alternate disk or not. Make sure old disk with old_rootvg

# lspv

To remove the alternate disk backup we have execute the below command.

# alt_disk_install -X

Break the rootvg mirror and take the clone for quick rollback. If your VIO server with single disk take the mksysb backup:

To break the rootvg mirror and create a clone for quick rollback

$ bootlist -mode normal –ls

$ unmirrorios hdisk1

# migratepv hdisk1 hdisk0 (Run as root user)

$ reducevg -rmlv rootvg hdisk1

$ alt_root_vg -target hdisk1

$oem_setup_env (to get root shell)

# bosboot -ad hdisk0 (using root shell)

# bootlist -mode normal hdisk0 hdisk1 (using root shell)

Patching using alternate disk:
If rootvg is mirrored, break the mirror and free up one disk then proceed with AIX patching using alternate disk method.

# alt_disk_copy -d <altdiskname> -b update_all -l <TL Location>

# alt_rootvg_op -W -d hdisk8

# chroot /alt_inst /usr/bin/ksh

# oslevel -s

# exit

# alt_rootvg_op -S altinst_rootvg