C H A P T E R

C H A P T E R 10

SMS Utilities

This section discusses the SMS backup, configuration, restore and version utilities. For information and examples of these utilities, refer to the System Management Services (SMS) 1.2 Reference Manual and online man pages.

SMS Backup Utility

smsbackup creates a cpio (1) archive of files that maintain the operational environment of SMS.

Note - This utility runs on the SC and does not replace the need for routine and timely backups of SC and domain operating systems; and domain application data.

Whenever changes are made to the SMS environment, for example, by adding boards to or removing boards from a domain, you must run smsbackup again in order to maintain a current backup file for the system controller.

The name of the backup file is smsbackup.X.X.cpio - where X.X represents the active version from which the backup was taken.

smsbackup saves all configuration, platform configuration database, SMS, and log files. In other words, SMS saves everything needed to return SMS to the working state it was in at the time the backup was made.

Backups are not performed automatically. Whenever changes are made to the SMS environment, a backup should be performed. This process can be automated by making it part of root cron job run at periodic intervals depending on your site requirements.

The backup log file resides in /var/sadm/system/logs/smsbackup . You must specify the target location when running smsbackup .

Note - The target location must be a valid UFS file system directory. You cannot perform smsbackup to a tmp file system directory.

Whenever you run smsbackup , you will receive confirmation that it succeeded or be notified that it failed.

You must have superuser privileges to run smsbackup . For more information and examples, refer to the smsbackup man page.

Restore SMS backup files using the smsrestore (1M) command.

SMS Restore Utility

smsrestore restores the operational environment of the SMS from a backup file created by smsbackup (1M). You can use smsrestore to restore the SMS environment after the SMS software has been installed on a new disk or after hardware replacement or addition. Failover should be disabled and SMS stopped before smsrestore is performed. Refer tothe "Stopping and Starting SMS" section of the System Management Services (SMS) 1.2 Installation Guide and Release Notes .

If any errors occur, smsrestore writes error messages to /var/sadm/system/logs/smsrestore .

Note - This utility runs on the SC and does not restore SC operating system, domain operating system or domain application data.

smsrestore cannot restore what you have not backed up. Whenever changes are made to the SMS environment, for example, by shutting down a domain, you must run smsbackup in order to maintain a current backup file for the system controller.

You must have superuser privileges to run smsrestore . For more information and examples, refer to the smsrestore man page.

SMS Version Utility

smsversion (1M) administers adjacent, co-resident installations of SMS under the same operating environment. Adjacent meaning you can use smsversion to switch between version SMS1.1 and SMS1.2 (assuming both are installed), but you cannot use smsversion to switch between SMS1.1 and a version of SMS following 1.2.

When you upgrade to the next sequential release of SMS (for example, 1.1 to 1.2), SMS must be stopped before running smsversion . Refer to "Stopping and Starting SMS" in the System Management Services (SMS) 1.2 Installation Guide and Release Notes . smsversion backs up important system and domain information and switches to the target SMS version.

Note - This utility runs on the SC and does not replace the need for routine and timely backups of the SC and domain operating system; and domain application data.

You can switch back to the previous sequential SMS version (for example, 1.2 to 1.1) at a later time. smsversion permits unlimited 2-way SMS version-switching between sequential co-resident installations on the same operating environment.

Note - Switching between non-sequential releases is not supported. Switching between sequential SMS versions across Solaris operating environments (for example, Solaris 8 and Solaris 9) is not supported. Once you upgrade from Solaris 8: SMS 1.1 or SMS 1.2 to Solaris 9: SMS 1.2 you cannot go back without also re-installing the earlier operating system version. This version of SMS 1.2 will not work under the Solaris 8 operating environment and the Solaris 8 version of SMS 1.2 will not work under Solaris 9.

Without options, smsversion displays the active version and exits when only one version of SMS is installed.

If any errors occur, smsversion writes error messages to /var/sadm/system/logs/smsversion .

You must have superuser privileges to run smsversion . For more information and examples, refer to the smsversion man page.

Upgrade Flow

Note - The upgrade flow which follows is not applicable under this initial release of Solaris 9. Two adjacent co-resident versions are not available under Solaris 9.

Switch between two adjacent, co-resident installations of SMS as follows:

On the main SC:

Make certain your configuration is stable and backed up using smsbackup .

Being stable means the following commands should not be running: smsconfig , poweron , poweroff , setkeyswitch , cfgadm , rcfgadm , addtag , deletetag , addboard , moveboard , deleteboard , setbus , setdefaults , setobpparams , setupplatform , enablecomponent or disablecomponent .
Deactivate failover using setfailover off .

On the spare SC:

Run /etc/init.d/sms stop .
Run smsversion . .
Run smsrestore .
If necessary, run smsconfig -m and reboot.

Only run smsconfig -m if you changed your network configuration using smsconfig -m after creating the smsbackup you just restored.

On the main SC:

Stop SMS using /etc/init.d/sms stop .

On the spare SC:

If smsconfig -m was run, reboot otherwise run /etc/init.d/sms start .

When the SC comes up it will become the main SC.

On the former main SC:

Repeat steps 4-6 and 8.

On the new main SC:

Activate failover using setfailover on .

For more information refer to the System Management Services (SMS) 1.2 Installation Guide and Release Notes .

SMS Configuration Utility

smsconfig configures the MAN networks, modifies the hostname and IP address settings used by the MAN daemon, mand (1M) and administers domain directories access control lists (ACLs).

UNIX Groups

smsconfig configures the UNIX groups used by SMS to describe user privileges. SMS uses a default set of UNIX groups installed locally on each SC. smsconfig allows you to customize those groups using the -g option. smsconfig allows you to add users to groups using the -a option and remove users from groups using the -r option.

For information and examples on adding, removing, and listing authorized users, refer to the System Management Services (SMS) 1.2 Installation Guide and Release Notes and smsconfig (1M) man page.

Access Control List (ACL)

Traditional UNIX file protection provides read, write and execute permissions for the three user classes: file owner, file group, and other. In order to provide protection and isolation of domain information, access to each domain's data is denied to all unauthorized users. SMS daemons, however, are considered authorized users and will have full access to the domain file systems. For example:

sms-esmd --needs to read the blacklist files in each domain directory $SMSETC/config/[A-R]
sms-osd --needs to read from and write to the bootparamdata file in each domain: $SMSVAR/data/[A-R]
sms-dsmd --need to write to hpost logs for every domain $SMSVAR/adm/[A-R]/post

smsconfig sets the ACL entries associated with the domain directories so that the domain administrator has full access to the domain. A plus sign (+) to the right of the mode field indicates the directories that have ACL defined.

domain_id:sms-user:> ls -al

total 6

drwxrwxrwx   2 root     bin          512 May 10 12:29 .

drwxrwxr-x  23 root     bin         1024 May 10 12:29 ..

-rw-rw-r--+  1 root     bin          312 May  4 16:15 blacklist

To add a user account to the ACL, the user must already belong to a valid SMS group as described in the System Management Services (SMS) 1.2 Installation Guide and Release Notes .

Note Note - UFS file system attributes, such as the ACL, are supported in UFS file systems only. If you restore or copy directories with ACL entries into the /tmp directory, all ACL entries will be lost. Use the /var/tmp directory for temporary storage of UFS files and directories.

Network Configuration

For each network, smsconfig can singularly set one or more interface designations within that network. By default, smsconfig steps through the configuration of all three internal, enterprise networks.

To configure an individual network, append the net_id to the command line. Management networks net_id s are designated I1 , I2 , and C .

Configure a single domain within an enterprise network by specifying both the desired domain and its net_id . A domain can be excluded from the I1 management network by using the word NONE as the net_id .

Note Note - Once you have configured or changed the configuration of the MAN network you must reboot the SC in order for the changes to take effect.

You must have superuser privileges to run smsconfig . For more information and examples, refer to the System Management Services (SMS) 1.2 Installation Guide and Release Notes , smsconfig man page and see Management Network Services .

MAN Configuration

smsconfig -m does the following:

Creates /etc/hostname.scman[01]
Creates /etc/hostname.hme0 and/or /etc/hostname.eri1 according to inputs to the External Network(s) prompts of smsconfig
Updates /etc/netmasks and / etc/hosts
Sets OBP variable local-mac-address?=true (default is false).

For more information on smsconfig refer to the smsconfig(1M) man page and see Management Network Services .