Saving current "rules" definitions on VIO Server.

Content

To address the configuration that may change during a VIO Server update
the following procedure is recommended.

This procedure will restore the original rules/configuration captured
in the "vios_current_rules.xml" file before the VIO Update was done.

On the VIO Server, save the current configuration (vios_current_rules.xml file) before the update is run. In addition you may save the "vios_default_rules.xml" file.

A "rules -o capture" should be run to create an up to date vios_current_rules.xml file.
After that you may then continue with the "updateios" command.

After the update is complete, compare the current rules (vios_current_rules.xml file)
to the copy saved before the update. If there are differences, the original vios_current_rules.xml rules file may be imported and deployed using "rules -o ..." to reset any settings (attributes) that may have been changed by the VIO Server update.


Summary of the steps:
*) Check that all LPPs are installed correctly "lppchk".
*) Make copy of vios_current_rules.xml
*) Make copy of vios_default_rules.xml
*) Capture system configuration
*) Make copy of vios_current_rules.xml (latest settings)
*) Update the VIO Server: updateios
*) Make copy of vios_current_rules.xml (copy from after the update)
*) Compare "diff" the original and updated vios_current_rules.xml file
*) Import "vios_current_rules.xml" file from before the update if there are differences.
*) Deploy the "vios_current_rules.xml" file
*) Make copy of vios_default_rules.xml (copy from after the update)
*) Compare "diff" the original and updated vios_default_rules.xml
*) Merge Third party default rules into the vios_default_rules.xml if required.



Detailed Commands:
$ oem_setup_env
# lppchk -v [ENTER]
----> This command will report any fileset that had a problem
during install or with a past update.
If everything is in good shape it just returns to a prompt.

# exit (to exit "oem_setup_env" )

$ mkdir /home/padmin/hold

$ cp -p /home/padmin/rules/vios_current_rules.xml
/home/padmin/hold/vios_current_rules.xml_before
--> Make a copy of the vios_current_rules.xml before capturing the system settings.

$ cp -p /usr/ios/cfg/vios_default_rules.xml /home/padmin/hold/vios_default_rules.xml_before
--> Make a copy of the vios_default_rules.xml before the VIO Server update.

$ rules -o capture
--> Capture the current system settings, and place them in
--> the vios_current_rules.xml file.

$ cp -p /home/padmin/rules/vios_current_rules.xml
/home/padmin/hold/vios_current_rules.xml_capture
--> Make a copy of the current settings before doing the VIO Server update.

$ updateios -dev <dir_with_update_files> -accept -install

Note: You may have to run the "updateios -commit" if an updateios has been
run before and there are un-committed filesets.
The updateios command will report a nice message
if the "updateios -commit" is needed.


$ cp -p /home/padmin/rules/vios_current_rules.xml
/home/padmin/hold/vios_current_rules.xml_after

$ diff /home/padmin/hold/vios_current_rules.xml_capture
/home/padmin/hold/vios_current_rules.xml_after
--> If there are differences complete the remaining steps (rm, rules import, rules deploy).

$ rm /home/padmin/rules/vios_current_rules.xml
--> A copy was made earlier so the contents of the file is not lost.
--> Clear the vios_current_rules.xml files allowing a clean import of the rules.

$ rules -o import -f /home/padmin/hold/vios_current_rules.xml_capture
--> Place the "captured" rules on the updated VIO Server.

You may have to edit the "ioslevel" to match the VIO Servers new level.
cp /home/padmin/hold/vios_current_rules.xml_before
/home/padmin/hold/vios_current_rules.xml_before_ioslevel
vi /home/padmin/hold/vios_current_rules.xml_before_ioslevel
---> edit the "value" to match the VIO level
---> Line is: <Parameter name="ioslevel" value="2.2.4.21" readOnly="true">

$ rules -o deploy
--> Applies the rules that were imported in the step above.


------------------------------------------
Make a copy of the new vios_default_rules.xml file.
------------------------------------------

$ cp -p /usr/ios/cfg/vios_default_rules.xml /home/padmin/hold/vios_default_rules.xml_after
--> Make a copy of the vios_default_rules.xml from after the VIO Server update.

$ diff /home/padmin/hold/vios_default_rules.xml_after /home/padmin/hold/vios_default_rules.xml_before
--> Check for changes, if there are third party storage rules missing they can be added to the
new vios_default_rules.xml using the steps in the techdoc "EMC default rules"
which references the internal command "/usr/sbin/rulesdeploy".

Note: Do not just replace the vios_default_rules.xml file with the old file.
There may be new default values provided by the VIO Server update that are desired,
and would be lost with a simple copy command.