Preparing XML file for Vdisk or Global Spare configuration

This procedure prepares the XML file to configure a Vdisk or Global Spare. A Global Spare is a spare disk not assigned to any particular Vdisk.

Note:

This interface is not intended for general customer use and should be used only as directed by My Oracle Support.

Caution:

The order in which Vdisks, Host Volumes, Global Spares are created or deleted is important. The procedures in this section do not state or imply the order to use. The operator with site-specific knowledge has the responsibility to configure the Vdisks, Host Volumes, and Global Spares in the proper order.

1. Log into the PMAC server as admusr.
2. Copy the file example_SharedStorageConfig_Vdisks_GlobalSpares.xml to a location where you can edit it from the following directory location on the PMAC server: /usr/share/doc/TKLCsmac-config-<release_number>/examples/.
3. For the <Controller> element, enter an IP v4 address or a hostname that resolves to an IP Address. This element specifies the controller to which this configuration will be applied. You can have multiple <Controller> elements in one file. This element is required.

   Note:

   Specify only one Controller per Controller Enclosure. Each Controller Enclosure has two Controllers, but they are a redundant pair. Applying the same configuration to both would attempt to configure the Controller Enclosure twice.
4. Locate <Name> under the <Vdisk> element and enter the name for the Vdisk.
   The name will be used to reference this Vdisk when configuring the Host Volumes. You can repeat the <Vdisk> element multiple times to add multiple Vdisks.
5. (Optional) For <Owner>, enter one of the following values to specify the controller to own the virtual disk:
   • A

     Specifies that Controller A within the Controller Enclosure will be used for this Vdisk.

   • B

     Specifies that Controller B within the Controller Enclosure will be used for this Vdisk.

   • auto

     Specifies that PMAC is to automatically assign this Vdisk to a Controller. This is the default.

   Vdisks may be assigned to different Controllers to achieve static load balancing between the Controllers. If one Controller in a redundant pair fails, ownership of its Vdisks will be taken over by the surviving controller.
6. For the <RaidLevel> element, enter a value to specify the RAID level. Valid values are as follows: nraid, 0,1,3,5,6,10 and 50.
7. Under <Disks>, enter one or more <Disk> elements in the form of Enclosure_Bay. Shown here are the examples from the relevant section of the XML file:

   Note:

   Disk setup is the same for the P2000 Controller as for the MSA2324.

   <!--
               Disks are specified in form "Enclosure.Bay" as in the 
       following examples:
   
               MSA2012: 
             
                 Enclosure 0 (controller enclosure): Disks 0.0..0.X
                 Enclosure 1 (drive enclosure):      Disks 1.0..1.X
                 Enclosure 2 (drive enclosure):      Disks 2.0..2.X
   
       MSA2324, P2000 and newer: 
             
                 Enclosure 0 (controller enclosure): Disks 1.1..1.X
                 Enclosure 1 (drive enclosure):      Disks 2.1..2.X
                 Enclosure 2 (drive enclosure):      Disks 3.1..3.X
              -->
             <Disks>
               <Disk>0.0</Disk>
               <Disk>0.1</Disk>
               <Disk>0.2</Disk>
               <Disk>0.3</Disk>
             </Disks>

   RAID 10 requires a minimum of two RAID-1 sub-Vdisks each having two drives. RAID 50 requires a minimum of two RAID-5 sub-Vdisks each having three drives.
8. (Optional) Under <SpareDisks>, enter one or more <Disk> elements. The notation is the same as in Preparing XML file for Vdisk or Global Spare configuration.
   This element specifies up to four Vdisk spares to assign to a RAID 1, 3, 5, 6, 10, or 50 virtual disk.
9. (Optional) Under <GlobalSpares>, enter one or more <Disk> elements. The notation is the same as Preparing XML file for Vdisk or Global Spare configuration.
10. At this point, if you would like to combine several XML files under the <SharedStorageConfig> element, you may do so.
    To view an example of a combined XML file, see Sample combined configure storage file.
11. If necessary, upload the XML file(s) back to the PMAC server by using sftp. See Uploading files to PMAC via sftp if you need help uploading the file.
12. On the PMAC server, copy the XML file to /usr/TKLC/smac/etc/storage/.

    For instance,

    sudo /bin/cp /var/TKLC/smac/image/isoimages/home/smacftpusr/<filename> /usr/TKLC/smac/etc/storage/

13. To process the XML file, continue with the procedure Processing the XML files.

The XML file is now prepared and ready for processing.