Updating platform sun4v bootarchive
This blog is written from both my research and my experience.The methods I describe herein are those that I have used and that have worked for me.Reason behind using Live Upgrade for patching purpose are - 1.Create a copy of the system environment; that is, a copy of the root (/) file system2. In case something breaks after patching revert to old BE and be at stage from where started, again that doesn’t take much downtime and safe option.5.The Solaris OS Recommended Patch Cluster provides critical Solaris OS Security, Data Corruption, and System Availability fixes & hence it is advisable to patch your Solaris systems twice in a year (atleast), as per Oracle-Sun's Critical Patch Update release schedule, I prefer to execute patch cycle for my environment in end of April and sometime late October every year.Oracle-Sun CPUs are released on the Tuesday closest to the 17th of January, April, July, and October – See - my environment, I use Live Upgrade to patch our Solaris systems.This article only describes how to convert the Mila X Live CD to a WANBOOT image – it does not talk about how to use the Mila X WANBOOT image or how to set up a WANBOOT server.
Sun recommend to break the mirror and boot directly on one side of the mirror. How to Manually Update the Boot Archive on a RAID-1 (Mirror) Volume The section is located at URL :
Using OBP, you can also query and set system parameter values such as the default boot device, run tests on devices such as the network interface, and display the SCSI and SBUS devices attached to the system.
Below are the available commands in OBP OK prompt: —————————- Defines a new device alias, where alias is the new alias name and path is the physical path of the device.
Mila X is available for x86 and for SPARC machines.
Unfortunately a lot of SPARC machines reside in data centers and there is no easy access to the CDROM drive of these machines.
It is highly recommended that you do further research on this subject.