Thank you for the update.
Everything is good from the environment perspective and we do regular patching every month. During the bulk patch activity where server reboot activity is performed we want some kind of validation. What those would be, As per my understanding one is mount point, second is services status, 3rd is uptime and 4th is oslevel. I hope those are sufficient. Is IBM having anything readily available to monitor those things with some script? or how can we achieve this.
------------------------------
Manoj Kumar
------------------------------
Original Message:
Sent: Tue December 02, 2025 04:36 AM
From: Ian Bellinfantie
Subject: How and what to validate after AIX server reboot
Dear Manoj
Before deciding to reboot, understand what is running on your AIX system and whether it can withstand a reboot . Are there any applications that need to be stopped before a reboot ? Are there any applications already in a failed state and need fixing before a reboot ? Are there any pending changes that will put the system into a different unexpected state after reboot ?
Then for a successful reboot , you need to fully understand the state of your operating system . Which will give you a list of what to check after a reboot .
For example , you may want to schedule a test reboot before you make multiple updates to verify that the system is operating successfully . Then you can be sure if your updates caused a failure to reboot .
Check your console log for errors reported to identify errors you can ignore or want to fix .
Always create an alt_disk clone as a backup and back out if the updates have unintended results .
Check compatibility of running software with the intended updated AIX level and get confirmation from software vendors .
Examine the current AIX error log for problems that need fixing before a reboot .
Compare your lpar virtualization settings in the profile with the running virtualization settings . These can change if the lpar is stopped and restarted instead of rebooted . Someone could have made changes that only come into effect after a reboot , but they never rebooted .
You should already have a regular job in your environment to capture the system configuration of filesystem and devices configured . Ensure this is upto date to compare after the upgrade . Capture network configurations that could change after an update . Soft NFS mounts that need to be manually mounted . Capture system ODM device customisations that have been tuned for performance that also can change after an update and reset to the default . You will have to ensure these customisations are put back after the update or check if they are no longer appropriate or required.
A fully managed environment will have the scripts and processes in place to check the system before and after reboot .
I hope this helps
Original Message:
Sent: 12/1/2025 3:01:00 AM
From: Manoj Kumar
Subject: How and what to validate after AIX server reboot
Hi Team,
We have to apply bulk patches and reboot during single maintenance window(reboot). During reboot we validate file system before reboot and after reboot.
What else we should validate after reboot. and is there any shell script readily available for all those monitoring stuff. Like we have to validate services status as well. or whether server reboot was done or not. Please suggest if there is other way to do that. Thanks.
------------------------------
Manoj Kumar
------------------------------