We have seen in the previous section that we can shut down and restart vPars independent of each other. The shutdown and restarts are all occurring while vpmon is still loaded in memory, managing all existing vPars. There are times when we want to restart the vmpon itself. The main reason for restarting vpmon is to perform maintenance on the underlying server/nPar, e.g., you want to add additional hardware to an existing server/nPar. In such a situation, we will need to shut down all vPars to a down state ( shutdown “h now on all vPars). This will leave us interacting directly with vpmon ; at the MON> prompt on the console. From here we can reboot/halt vpmon itself.
root @uksd3 # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================ ===== ========== ========================= ===== vPar0 Up Dyn,Auto /stand/vmunix vPar1 Down Dyn,Auto /stand/vmunix [Virtual Partition Resource Summary] CPU Num Memory (MB) CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== vPar0 1/ 5 1 2 9 0/ 0 2048 vPar1 1/ 2 1 0 6 0/ 0 2048 root @uksd3 # shutdown -h now SHUTDOWN PROGRAM 11/07/03 02:51:52 GMT Broadcast Message from root (console) Fri Nov 7 02:51:52... SYSTEM BEING BROUGHT DOWN NOW ! ! ! ... System shutdown time has arrived [MON] [MON] vPar0 has halted. MON> MON> ? Supported Commands: ? Print list of commands cat Dump contents of file to screen cbuf Dump contents of console buffer getauto Print the AUTO file help Print list of commands lifls List files in LIF directory log View the event log ls List files in a directory readdb Read a partition DB reboot Reboot system scan Scan the system toddriftreset Reset the TOD drift of all vpars vparload Load vPar vparinfo Display vPar info bootpath Display monitor boot path MON>
A REBOOT will reboot vpmon . This would give us the opportunity to interact with the boot-up of the server/n-Par via the system console. At that time, we could interrupt the boot sequence in order to manage the server/n-Par (power-cycle the server or PE the necessary hardware components ) to implement the changes that required us to reboot vpmon . To restart an nPar, we will need to use the GSP BO command.
MON> vparload -all [MON] Booting vPar1... [MON] Booting vPar0...