Backing up ldom configuration:
The Ldom configuration is essentially stored in the service
processor.
When we make some modification in the ldom configuration
like creation or removal of ldoms we must update the ldom configuration via ldm
add-config followed by ldm set-config. Note that config & spconfig
subcommands can be used interchangeably.
bash-3.00# ldm
add-config test
bash-3.00#
bash-3.00# ldm
list-config
factory-default
primaryconf- -vlans
primaryconf_17092013_pre
primaryconf_24092013
primaryconf_sp_01Apr2014
primaryconf_spconfig
primaryconf_spconfig.03April20
primaryconf-23May14
27052015
test [current]
bash-3.00# ldm
set-spconfig 27052015
bash-3.00#
bash-3.00# ldm
list-config
factory-default
primaryconf- -vlans
primaryconf_17092013_pre
primaryconf_24092013
primaryconf_sp_01Apr2014
primaryconf_spconfig
primaryconf_spconfig.03April20
primaryconf-23May14
27052015 [next poweron]
test [current]
bash-3.00# ldm
remove-config test
bash-3.00#
bash-3.00# ldm list-config
factory-default
primaryconf- -vlans
primaryconf_17092013_pre
primaryconf_24092013
primaryconf_sp_01Apr2014
primaryconf_spconfig
primaryconf_spconfig.03April20
primaryconf-23May14
27052015 [next poweron]
bash-3.00#
The configuration of an individual ldom can be backed up
in an xml via redirection of the list-constraints output for the guest domain.
bash-3.00# ldm list-constraints -x testdomain >
testdomain.xml
We can also use this config backup to deploy multiple
ldoms with the same configuration thereby saving some time. You do need to change
ldom name in the xml file.
</LDM_interface>
bash-3.00# cat testdomain.xml | grep testdomain
<Content
xsi:type="ovf:VirtualSystem_Type" ovf:id="testdomain">
bash-3.00#
For example, I changed that name testdomain to domain1 in
the xml file testdomain.xml renamed it & used it to deploy domain1. Here
are the commands:
bash-3.00# vi testdomain.xml
bash-3.00# mv testdomain.xml domain1.xml
bash-3.00# ldm add-domain -i domain1.xml
bash-3.00# ldm list-domain domain1
NAME
STATE FLAGS CONS
VCPU MEMORY UTIL
UPTIME
domain1
inactive ------ 2
1G
bash-3.00#
bash-3.00# cat domain1.xml | grep domain1
<Content
xsi:type="ovf:VirtualSystem_Type" ovf:id="domain1">
In case the primary domain is not accessible or for any other reason if you are unable to boot to desired ldom configuration from the primary domain then in that case you can change the ldom configuration from the ILOM as well using the following command:
-> set /HOST/bootmode config=configname
No comments:
Post a Comment