8.11.2 Monitoring, Validating, and Troubleshooting Exadata Storage Server Updates
The recommended way to monitor Exadata storage servers being updated is through e-mail alerts. These alerts can be set up by specifying email addresses in the -smtp_from
and -smtp_to
flags in the update utility.
If needed for troubleshooting, you can monitor update activity using less -rf patchmgr.stdout
from another terminal session or window to see raw log details from the update utility.
You can also monitor activity of the storage server by logging in to the serial console or web-based ILOM console of individual storage servers being updated 5 minutes after the update utility has started. Waiting 5 minutes allows the update utility time to reset the ILOM. Resetting the ILOM disconnects you from the ILOM web console and serial console. You can reconnect once the ILOM has been reset. By waiting 5 minutes, you avoid having to reconnect. You lose the connection during any ILOM update, and need to reconnect. The ILOM does not show any update actions. When needed it is helpful to monitor the activities of the normal cell boot, reboot, and other activities to ensure that the process is proceeding correctly.
Verify the update status after the patchmgr utility completes as follows:
Check image status and history using the imageinfo
and imagehistory
commands on each cell. A successful update to a system with high capacity or high performance drives shows output similar to the following.
Kernel version: 2.6.39-400.281.1.el6uek.x86_64 #1 SMP Fri Jun 17 20:10:16 PDT 2016 x86_64
Cell version: OSS_12.1.2.3.2_LINUX.X64_160721
Cell rpm version: cell-12.1.2.3.2_LINUX.X64_160721-1.x86_64
Active image version: 12.1.2.3.2.160721
Active image kernel version: 2.6.39-400.281.1.el6uek
Active image activated: 2016-07-21 13:04:34 -0500
Active image status: success
Active system partition on device: /dev/md5
Active software partition on device: /dev/md7
Cell boot usb partition: /dev/sdac1
Cell boot usb version: 12.1.2.3.2.160721
Inactive image version: 12.1.2.3.1.160411
Inactive image activated: 2016-04-11 19:58:28 -0700
Inactive image status: success
Inactive system partition on device: /dev/md6
Inactive software partition on device: /dev/md8
Inactive marker for the rollback: /boot/I_am_hd_boot.inactive
Inactive grub config for the rollback: /boot/grub/grub.conf.inactive
Inactive kernel version for the rollback: 2.6.39-400.128.21.el5uek
Rollback to the inactive partitions: Possible
A successful update to a system with extreme flash drives shows a similar output but has a different path for USB:
Kernel version: 2.6.39-400.281.1.el6uek.x86_64 #1 SMP Fri Jun 17 20:10:16 PDT 2016 x86_64 Cell version: OSS_12.1.2.3.2_LINUX.X64_160721 Cell rpm version: cell-12.1.2.3.2_LINUX.X64_160721-1.x86_64 Active image version: 12.1.2.3.2.160721 Active image kernel version: 2.6.39-400.281.1.el6uek Active image activated: 2016-07-21 13:04:34 -0500 Active image status: success Active system partition on device: /dev/md5 Active software partition on device: /dev/md7 Cell boot usb partition: /dev/sda1 Cell boot usb version: 12.1.2.3.2.160721 Inactive image version: 12.1.2.3.1.160411 Inactive image activated: 2016-04-11 19:58:28 -0700 Inactive image status: success Inactive system partition on device: /dev/md6 Inactive software partition on device: /dev/md8 Inactive marker for the rollback: /boot/I_am_hd_boot.inactive Inactive grub config for the rollback: /boot/grub/grub.conf.inactive Inactive kernel version for the rollback: 2.6.39-400.128.21.el5uek Rollback to the inactive partitions: Possible
Related Topics
Parent topic: Troubleshooting Software Updates on Oracle Exadata