Shutting Down the Primary Enterprise Controller

Depending on the nature of the failure that you encounter, the primary Enterprise Controller might function enough to allow you to shut down the system in an orderly manner. If this is true, take the steps necessary to complete the following:

• Run the habackup program if possible
• Stop Sun xVM Ops Center services
• Unmount LOFS mounts
• Unshare the /var/opt/sun/xvm/osp/share/allstart directory
• Release control of the storage asset that stores the /var/opt/sun/xvm directory structure
• Shut down the operating system of the failing Enterprise Controller

The steps to shut down the primary Enterprise Controller are intended to minimize damage to the primary Enterprise Controller and to the data that will transfer to the secondary Enterprise Controller. Some failures, however, might prevent you from shutting down the primary Enterprise Controller in an orderly manner. If this is true, additional procedures might be required to transfer the storage asset to the secondary Enterprise Controller. Even if it is not possible to perform these procedures, the HA failover procedure is designed to succeed.

The cron utility runs the habackup program every hour on the Enterprise Controller. To obtain a current copy of the data that it collects, run habackup before you unmount directories and release the storage asset that holds the /var/opt/sun/xvm directory structure, if possible.

If Sun xVM Ops Center services are running on the primary Enterprise Controller, stop those services before you transfer a storage asset between the two systems.

The /etc/opt/SUNWuce, /var/opt/SUNWuce, and /opt/SUNWuce directories are used as LOFS mount points for a set of directories within the /var/opt/sun/xvm directory structure. These LOFS mounts are created automatically when you install Sun xVM Ops Center. Before you release or transfer control of the storage asset that holds the /var/opt/sun/xvm directory structure, unmount these LOFS mounts.

The /var/opt/sun/xvm/osp/share/allstart directory is automatically shared when you install Sun xVM Ops Center software on an Enterprise Controller. Before you release or transfer control of the storage asset that holds the /var/opt/sun/xvm directory structure, unshare the /var/opt/sun/xvm/osp/share/allstart directory.

Many storage solutions support HA configurations in Sun xVM Ops Center. Some storage solutions allow you to release control of a storage asset, to allow a different system to use the storage asset. For example, the ZFS file system allows you to export a storage pool so that a different system can import it. The following example procedures use a Fibre Channel attached array that contains a ZFS storage pool. In this example, the primary and secondary Enterprise Controllers are both attached to the array. See Configuring Storage for High Availability for a description of the example storage solution.

Determine if the storage solution for your HA configuration allows you to release control of the storage asset that stores the /var/opt/sun/xvm directory structure. If this is true, release the storage asset before you shut down the primary Enterprise Controller.

Perform the following procedure on the primary Enterprise Controller.

To Shut Down the Primary Enterprise Controller

Caution – The following example procedure is based on the example Solaris OS-based storage solution that is described in Configuring Storage for High Availability. You must determine what specific procedures to use, depending on the storage solution that you have implemented.

1. Run the habackup program to create a current copy of the data that it collects.
   For example:

   # /opt/sun/xvm/bin/habackup
   Backup complete.
   #
   

   The habackup program successfully runs only if the Enterprise Controller services are running.
   

2. Use the proxyadm and satadm commands to check for and shut down Sun xVM Ops Center services on the primary Enterprise Controller.
   Shut down Proxy Controller services before you shut down Enterprise Controller services.
   • Solaris OS: Use the /opt/SUNWxvmoc/bin/proxyadm and /opt/SUNWxvmoc/bin/satadm commands.
   • RHEL OS: Use the /opt/sun/xvmoc/bin/proxyadm and /opt/sun/xvmoc/bin/satadm commands.
     For example:

     # /opt/SUNWxvmoc/bin/proxyadm status
     online
     # /opt/SUNWxvmoc/bin/proxyadm stop -w
     proxyadm: Shutting down proxy using SMF...
     proxyadm: Proxy services have stopped
     #
     # /opt/SUNWxvmoc/bin/satadm status
     online
     # /opt/SUNWxvmoc/bin/satadm stop -w
     satadm: Shutting down satellite using SMF...
     satadm: Satellite services have stopped
     # 
     

     In this example, both Proxy Controller and Enterprise Controller services are online. The services that the proxyadm command reports as online are associated with the Proxy Controller that is co-located with the Enterprise Controller.
     

3. Unmount the /etc/opt/SUNWuce, /var/opt/SUNWuce, and /opt/SUNWuce LOFS mounts.
   For example:

   # mount -v | grep xvm
   OpsCenter/xvm on /var/opt/sun/xvm type zfs read/write/setuid/devices/exec/xattr/atime/dev=4010002 on Mon Feb 23 07:59:22 2009
   /var/opt/sun/xvm/uce/etc.opt on /etc/opt/SUNWuce type lofs read/write/setuid/devices/dev=4010002 on Mon Feb 23 08:15:15 2009
   /var/opt/sun/xvm/uce/var.opt on /var/opt/SUNWuce type lofs read/write/setuid/devices/dev=4010002 on Mon Feb 23 08:15:15 2009
   /var/opt/sun/xvm/uce/opt on /opt/SUNWuce type lofs read/write/setuid/devices/dev=4010002 on Mon Feb 23 08:15:15 2009
   # 
   # umount /etc/opt/SUNWuce
   # umount /var/opt/SUNWuce
   # umount /opt/SUNWuce
   # mount -v | grep xvm
   OpsCenter/xvm on /var/opt/sun/xvm type zfs read/write/setuid/devices/exec/xattr/atime/dev=4010002 on Mon Feb 23 07:59:22 2009
   #
   

   In this example, the ZFS file system named OpsCenter/xvm is mounted as /var/opt/sun/xvm. The /etc/opt/SUNWuce, /var/opt/SUNWuce, and /opt/SUNWuce LOFS mounts use resources within /var/opt/sun/xvm.
   

4. Unshare the /var/opt/sun/xvm/osp/share/allstart directory.
   For example:

   # share
   -               /var/opt/sun/xvm/osp/share/allstart   ro   "Allstart Share" 
   -               /var/js   ro,anon=0   "Allstart Share" 
   -               /opt/SUNWjet   ro,anon=0   "JET Framework" 
   # unshare /var/opt/sun/xvm/osp/share/allstart
   # share
   -               /var/js   ro,anon=0   "Allstart Share" 
   -               /opt/SUNWjet   ro,anon=0   "JET Framework" 
   # 
   

   
   

5. Release control of the storage asset that stores the /var/opt/sun/xvm directory structure.
   For example, if you use ZFS to store the /var/opt/sun/xvm directory structure, you can export the ZFS pool that contains /var/opt/sun/xvm:

   # zfs list
   NAME            USED  AVAIL  REFER  MOUNTPOINT
   OpsCenter       382M   134G  1.50K  none
   OpsCenter/xvm   382M   134G   382M  legacy
   # zpool export OpsCenter
   # zpool list
   no pools available
   # zfs list
   no datasets available
   # 
   

   
   The /var/opt/sun/xvm directory unmounts automatically when you export the OpsCenter pool.

6. If it is required for your particular storage solution, physically detach the storage asset from the primary Enterprise Controller.
   
7. Shut down the operating system on the primary Enterprise Controller.
   For example, on Solaris systems, you can use the init 5 command to shut down and power off the system:

   # init 5
   

   
   

8. Disconnect the primary Enterprise Controller from the networks to which it is connected.
   If you boot the primary Enterprise Controller to make repairs, this prevents the primary Enterprise Controller from using the same IP addresses as secondary Enterprise Controller. You can temporarily assign new IP addresses to the primary Enterprise Controller if you need to attach it to your network.