1.7.3 How to Save/Restore the Logical Domain Configuration Information and the OpenBoot PROM Environment Variable
1.7.3 How to Save/Restore the Logical Domain Configuration Information and the OpenBoot PROM Environment Variable
- Execute the ldm ls-spconfig command on Oracle Solaris super-user prompt to display the list of the configuration information, and then confirm the configuration information to be saved.
- The following example shows the current configuration information at test3.
| # ldm ls-spconfig factory-default test1 test2 test3 [current] |
- If the current configuration is shown as "next poweron," execute the ldm add-spconfig command to save the current configuration information. This is because the configuration information stored in the XSCF is different from that stored in the control domain.
- In the following example, the current configuration information is saved in test4 because test3 is "next poweron."
| # ldm ls-spconfig factory-default test1 test2 test3 [next poweron] # ldm add-spconfig test4 # ldm ls-spconfig factory-default test1 test2 test3 test4 [current] |
- Execute the ldm set-spconfig command to specify the configuration information to be set.
- The following example specifies test1.
| # ldm set-spconfig test1 # ldm ls-spconfig factory-default test1 [next poweron] test2 test3 |
- Execute the poweroff and poweron commands of the XSCF firmware to turn off/on the power to the physical partition.
- Before turning off the power to the system, stop the logical domain with an appropriate procedure and use the ldm unbind command to transfer it to the inactive state.
The following example shows that the power to PPAR 0 is turned off/on.
| XSCF> poweroff -p 0 XSCF> poweron -p 0 |
- Execute the ldm ls-spconfig command to confirm that the configuration information is set as specified.
- The following example shows that the current configuration information is set at test1.
| # ldm ls-spconfig factory-default test1 [current] test2 test3 |
- Execute the ldm ls-constraints -x command to save the current configuration information.
- If necessary, back up the XML file.
In the following example, the current configuration information is saved in test1.xml.
| # ldm ls-constraints -x > /test1.xml |
- Execute the more command to confirm that the configuration information is correct.
| # more /test1.xml <?xml version="1.0"?> <LDM_interface version="1.3" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instancce |
- If there are multiple pieces of configuration information to be saved, save all of them.
Repeat step 2 to step 6 to save the configuration information.
- Execute the ldm set-spconfig factory-default command to set the system to the factory default.
| # ldm set-spconfig factory-default # ldm ls-spconfig factory-default [next poweron] test1 [current] test2 test3 |
- Execute the ldm rm-spconfig command to remove all the configuration information.
| # ldm rm-spconfig test1 # ldm rm-spconfig test2 # ldm rm-spconfig test3 # ldm ls-config factory-default [next poweron] |
- Stop the logical domain to set it to the OpenBoot PROM state.
- Before turning off the power to the system, stop the logical domain with an appropriate procedure and use the ldm unbind command to transfer it to the inactive state.
| # shutdown -i0 -g0 -y |
- Check the OpenBoot PROM environment variable with the printenv command.
| {0} ok printenv Variable Name Value Default Value ttya-rts-dtr-off false false ttya-ignore-cd true true keyboard-layout reboot-command security-mode none No default security-password No default security-#badlogins 0 No default diag-switch? false false local-mac-address? true true fcode-debug? false false scsi-initiator-id 7 7 oem-logo No default oem-logo? false false oem-banner No default oem-banner? false false ansi-terminal? true true screen-#columns 80 80 screen-#rows 34 34 ttya-mode 9600,8,n,1,- 9600,8,n,1,- output-device virtual-console virtual-console input-device virtual-console virtual-console auto-boot-on-error? false false load-base 16384 16384 auto-boot? false true network-boot-arguments boot-command boot boot boot-file boot-device /pci@8000/pci@4/pci@0/pc ... disk net multipath-boot? false false boot-device-index 0 0 use-nvramrc? false false nvramrc error-reset-recovery boot boot |
- If there is any omitted section with "...," review this section.
| {0} ok printenv boot-device boot-device = /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0,0 |
- Execute the poweroff command of the XSCF firmware to turn off the power to the physical partition.
| XSCF> poweroff -p 0 |
- In accordance with the model in use, restore the configuration information of the logical domain from the XML file.
- - For the SPARC M10-1
When updating from the firmware version XCP 2043 or earlier to the firmware version XCP 2044 or later in the system with the PCI expansion unit, restore the configuration information of the logical domain from the XML file in step 14 and later.
For details on the firmware update, see the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.- For the SPARC M12-2/M12-2S/M10-4/M10-4S
When executing the setpciboxdio command to toggle the enable/disable setting for the direct I/O function of the PCI expansion unit, restore the logical domain configuration information from the XML file in step 14 and later.
For details on the setpciboxdio command, see the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual.
- Execute the showdomainconfig command of the XSCF firmware to confirm that the configuration information at the next startup of the physical partition is the factory default.
- The following example shows that the configuration information at the next startup is the factory default.
| XSCF> showdomainconfig -p 0 PPAR-ID :0 Booting config (Current) :factory-default (Next) :factory-default ---------------------------------------------------------- Index :1 config_name :factory-default domains :1 date_created:- |
- The following example shows that the configuration information at the next startup is not the factory default. In this case, execute the setdomainconfig command to set the configuration information at the next startup of the physical partition to the factory default.
| XSCF> showdomainconfig -p 0 PPAR-ID :0 Booting config (Current) :test1 (Next) :test2 : XSCF> setdomainconfig -p 0 -i 1 XSCF> showdomainconfig -p 0 PPAR-ID :0 Booting config (Current) :test1 (Next) : factory-default ---------------------------------------------------------- Index :1 config_name :factory-default domains :1 date_created:- |
- Check auto-boot? of the OpenBoot PROM environment variable to stop in the OpenBoot PROM state.
If the value is true, change it to false.
| XSCF> setpparparam -p 0 -s bootscript "setenv auto-boot? false" PPAR-ID of PPARs that will be affected:0 OpenBoot PROM variable bootscript will be changed. Continue? [y|n] :y |
- If you changed the value, check the OpenBoot PROM environment variable.
| XSCF> showpparparam -p 0 use-nvramrc :- security-mode :- bootscript : setenv auto-boot? false |
- Execute the poweron command to restart the physical partition.
| XSCF> poweron -p 0 |
- Execute the showdomainstatus command to check the status of the control domain.
Confirm that the status of the control domain is displayed as "OpenBoot Running" indicating that it is in the OpenBoot PROM state.
| XSCF> showdomainstatus -p 0 Logical Domain Name Status primary OpenBoot Running |
- Execute the console command to switch to the control domain console.
| XSCF> console -p 0 -y Console contents may be logged. Connect to PPAR-ID 0?[y|n] :y |
- Based on the record in step 11, restore the OpenBoot PROM environment variable.
- In the following example, auto-boot? is restored to true.
| {0} ok setenv auto-boot? true auto-boot? = true {0} ok printenv auto-boot? auto-boot? = true |
- Boot Oracle Solaris.
| {0} ok boot |
- With the Oracle Solaris super-user prompt, confirm that the system has started with the factory default.
| # ldm ls-spconfig factory-default [current] |
- Execute the ldm init-system command and the shutdown command to restart the control domain.
| # ldm init-system -i /test1.xml Initiating a delayed reconfiguration operation on the primary domain. All configuration changes for other domains are disabled until the primary domain reboots, at which time the new configuration for the primary domain will also take effect. # shutdown -y -g0 -i6 |
- After restarting the control domain, bind and start other logical domains.
For logical domains with dependencies, start them in the correct order.
- In the following example, both the root-domain and guest-domain are bound and started.
| # ldm bind root-domain # ldm start-domain root-domain # ldm bind guest-domain # ldm start-domain guest-domain |
- If the binding failed because an overlapping resource exists, remove the relevant resource from the logical domain.
The following example shows that an overlapping resource has been removed.
| # ldm bind root-domain No free matching I/O device for LDom root-domain, name PCIE1 # ldm start-reconf primary # ldm rm-io PCIE1 primary ------------------------------------------------------------------------------ Notice: The primary domain is in the process of a delayed reconfiguration. Any changes made to the primary domain will only take effect after it reboots. ------------------------------------------------------------------------------ |
- If you removed a resource, restart the control domain.
| # shutdown -i6 -g0 -y |
- If you removed a resource, restart the control domain and then bind and start other logical domains.
For logical domains with dependencies, start them in the correct order.
In the following example, both the root-domain and guest-domain are bound and started.
| # ldm bind root-domain # ldm start-domain root-domain # ldm bind guest-domain # ldm start-domain guest-domain |
- Execute the ldm ls command to confirm that the logical domain is operating normally.
| # ldm ls NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active -n-cv- UART 8 8G 66% 4m root-domain active -t---- 5000 8 4G 19% 29s : : |
- After restoring the configuration information, execute the ldm add-spconfig command to save the configuration information to the XSCF.
- In the following example, the configuration information of test1 has been saved to the XSCF.
| # ldm add-spconfig test1 # ldm ls-spconfig factory-default test1 [current] |
- If there are multiple pieces of configuration information to be restored, restore all of them.
Repeat step 14 to step 25 to restore the configuration information.
< Previous Page | Next Page >