Preparing XML file for Host Volume configuration

The Configure Host Volume capability configures the Host Volume on the specified server blade and creates the corresponding configuration on the Controller.

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.

Log into the PMAC server as admusr.
Copy the file example_SharedStorageConfig_HostVolume.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/.

Locate the <HostVolume> element.

The relevant section from the XML file is shown:

<HostVolume>

      <!--
        A Host may be specified by its IP address or a name that
        resolves to its IP address.
      -->
      <Host>10.2.3.1</Host>

      <VolumeMB>1300000</VolumeMB>

      <!--
        A volume can be created with the following file system types:
ext2, ext3 (default), and raw.
      -->
      <Filesystem>ext3</Filesystem>

      <MountPoint>/mnt/dbVolume</MountPoint>

      <Controller>10.2.3.4</Controller>

      <VdiskName>Vdisk2</VdiskName>

      <MountOptions>exec,ro</MountOptions>
      <!--
        The VolumeName is optional but it's recommended that you provide
        a meaningful name.  If none is provided, one will be generated
        automatically by PM&C.
      -->
      <VolumeName>FirstVolume</VolumeName>

      <LUN>20</LUN>

    </HostVolume>

For the <Host> element, enter an IP v4 address or a hostname that resolves to an IP Address. This element specifies the target server blade. You can have multiple <HostVolume> elements in one file.
For the <VolumeMB> element, enter the size in megabytes for the Volume.
For <Filesystem>, enter one of the following file system types: ext2, ext3, and raw.
If no value is specified, the default ext3 is used.
For <MountPoint>, enter the location on the host to mount the Volume.
Under <Controller>, enter the Controller IP v4 address or hostname to associate with this Host Volume.
Under <VdiskName>, enter the Vdisk name to associate with this Host Volume.
For <MountOptions>, enter one or more of the following options:
- async
  All I/O to the file system should be done asynchronously.
- atime
  Update inode access time for each access. This is the default.
- auto
  Can be mounted with the -a option.
- defaults
  Use default options: rw, suid, dev, exec, auto, nouser, and async.
- dev
  Interpret character or block special devices on the file system.
- exec
  Permit execution of binaries.
- _netdev
  The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system).
- noatime
  Do not update inode access times on this file system (for example, for faster access on the news spool to speed up news servers).
- noauto .
  Can only be mounted explicitly (i.e., the -a option will not cause the file system to be mounted).
- nodev
  Do not interpret character or block special devices on the file system.
- noexec
  Do not allow execution of any binaries on the mounted file system. This option might be useful for a server that has file systems containing binaries for architectures other than its own.
- nosuid
  Do not allow set-user-identifier or set-group-identifier bits to take effect.
- nouser
  Forbid an ordinary (for example, non-root) user to mount the file system. This is the default.
- remount
  Attempt to remount an already-mounted file system. This is commonly used to change the mount flags for a file system, especially to make a read-only file system writeable. It does not change the device or mount point.
- ro
  Mount the file system read-only.
- rw
  Mount the file system read-write.
- suid
  Allow set-user-identifier or set-group-identifier bits to take effect
- sync
  All I/O to the file system should be done synchronously.
- dirsync
  All directory updates within the file system should be done synchronously. This affects the following system calls: create, link, unlink, symlink, mkdir, rmdir, mknod and rename.
- user
  Allow an ordinary user to mount the file system. The name of the mounting user is written to mtab so that he can unmount the file system again. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line user,exec,dev,suid).
- users
  Allow every user to mount and unmount the file system. This option implies the options noexec, nosuid, and nodev (unless overridden by subsequent options, as in the option line users, exec, dev, suid).
Some of the mount options are useful only when they appear in the /etc/fstab file. The mount options apply to any file system that is being mounted (but not every file system actually honors them, for example, the sync option has an effect only for ext2, ext3 and ufs):
For <VolumeName>, enter a name.
If you do not specify a name, PMAC will generate one.
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.
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.

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/

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

The XML file is now prepared and ready for processing.