Create a Physical Disk

Define the attributes to allocate the storage resources necessary to create the physical disk.

Prerequisites:
  • Oracle FS System login credentials with Administrator 1 privileges.

  • The Oracle FS System where the physical disk is created has been added and has been registered with the Oracle VM environment.

Note: The Oracle FS System refers to physical disks as LUNs.
  1. In the Oracle VM Manager, select the Storage tab.
  2. From the available SAN servers in the navigation tree, select the Oracle FS System upon which you want to create the physical disk.
  3. Select Physical Disks from the Perspective: drop-down list in the toolbar at the top of the content area of the page.
  4. In the toolbar at the top of the content area of the page, click the Create Physical Disk plus sign (+) icon.
  5. In the Create Physical Disk dialog, enter the following:
    Volume Group
    Choose a volume group to which the physical disk is associated, if needed.
    Important! The volume group attribute cannot be modified at a later time.
    Name
    Identifies the name that is assigned to a physical disk for administrative purposes. Physical disk names must be unique across the Oracle FS System and must be 82 or fewer UTF characters (255 or fewer ASCII characters).
    Size
    Specifies the capacity of the physical disk in GB.
    Extra Information
    Specifies the priority level of the physical disk. The field is a free-form text area that accepts one <option>:<value> pair on each line in the following format:
    <option>:<value>
    .
    .
    .
    <option>:<value>
    Example:
    accessBias:random 
    ioBias:write 
    storageclass:stathd
    StorageDomain:/SD1
    
    Important! Use line endings to separate <option>:<value> pairs from each other. If the option has no <value> argument associated with it, provide only the option name.

    The following options can be specified:

    accessBias
    Identifies the expected access pattern to the LUN: sequential, random, or mixed.
    addressableCapacity or capacity
    Defines the actual amount of storage that is assigned to a logical volume. An allocated capacity can grow to and possibly exceed by a small amount the addressable logical capacity.
    allocatedCapacity
    Specifies the amount of space, in gigabytes, that the Oracle FS System sets aside for a LUN. This number can be less than the amount that you specify for the addressable logical capacity for the LUN using the ‑capacity option. When the allocated capacity is less than the space that is requested for ‑capacity, the system creates what is called a thinly provisioned LUN.
    cloneCapacity
    Identifies the capacity that is allocated for Clone LUNs.
    copyPriority
    Identifies which of the following settings to use to control the impact on performance when you copy or migrate data from one location to another: auto, low, or high.
    maskedSlammerPorts (Axiom)
    maskedControllerPorts (Oracle FS System)
    Prevents LUN access through specific Slammer ports. Identify the ports to mask by specifying port-name values. The port-name is the fully qualified name (FQN) of a port that you can obtain by running the slammer ‑list or controller ‑list CLI command. The format of the FQN is /⁠<Slammer name>/⁠CU<x>/⁠Port<y>, where <Slammer name> is the name of the Slammer or Controller, <x> is either 0 or 1, and <y> can be 0 through 15. If you do not specify this option, the LUN becomes accessible on all Slammer or Controller ports on the assigned CU by default. The maskedSlammerPorts or maskedControllerPorts option can only be specified along with the slammerNode or controller option.
    ioBias
    Identifies the typical read‑write ratio: read, write, or mixed.
    matchTierQos
    If this is specified, none of the repository QoS values are allowed.
    profile
    Identifies the ID or fully qualified name (FQN) of the QoS performance profile that should be applied when creating the LUN. When creating a LUN, do not specify the profile option if you are specifying the redundancy, accessBias, or ioBias options.
    raidLevel
    Cannot be used along with the redundancy, accessBios, ioBios, or profile options. Specify raid5, raid10, raid6, or default.
    readAhead
    Cannot be used along with the redundancy, accessBios, ioBios, or profile options. Specify normal, aggressive, conservative, or default.
    redundancy
    Identifies how many mirror copies of the original data are stored online. The default is 1.
    repositoryAccessBias
    Cannot be used with the redundancyRaidLevel option. Specify sequential, random, or mixed and can use used mixed case values.
    repositoryIOBias
    Cannot be used with the redundancyRaidevel option. Specify read, write, or mixed and can use used mixed case values.
    repositoryPriority
    Specify premium, high, medium, low, or archive.
    repositoryRaidLevel
    Cannot be used with the repositoryRedundancy, repositoryAccessBios, or redundancyioBios options. Specify raid5, raid10, radi6, or default.
    repositoryRedundancy
    Cannot be used with the redundancyRaidLevel option. Specify 1 or 2.
    slammerNode (Axiom)
    controller (Oracle FS System)
    Identifies the CU to which the LUN is assigned. If you do not specify this option, the storage system selects the CU automatically.
    storageClass
    Identifies the type of physical storage to use for the LUN. If the storage system has two or more Storage Classes, you must specify the Storage Class for the storage system to use.
    storageDomain
    Identifies the Storage Domain in which the LUN should be created. If this option is not provided, the system uses the default Storage Domain. A storage domain is required when working with an Oracle FS System.
    suppressConservativeMode (Axiom)
    conservativeMode (Oracle FS System)
    Prevents the storage system from entering conservative mode for the specified LUN.
    Caution
    In conservative mode, data is written to disk before the write operation completes (write through). If conservative mode is suppressed, the system does not enable write through when a CU fails. If the remaining CU fails, any data that has not been written to the drives is lost. Because data could be lost, using the ‑noConservativeMode option or the ‑suppressConservativeMode option is not recommended.
    Note: A Storage Class must be specified if the storage system has more than one Storage Class.

    For detailed information about each of these options, refer to the Oracle Flash Storage System CLI Reference. For a full list of only the fscli ‑lun options, enter fscli ‑lun ‑add ‑help on a command line.

    Description
    Enter up to 4096 characters to describe the Oracle FS System physical disk. This option is an Oracle VM Manager option.
    Shareable
    Select to make the physical disk available to share across virtual machines. This option is an Oracle VM Manager option.

    For more information about sharing disks, refer to the Oracle VM documentation on the Oracle Technical Network (http://docs.oracle.com).

    Thin Provision
    Select to create the physical disk as a thin‑provisioned LUN. The default value is selected. This option is an Oracle VM Manager option.

    Refer to the Oracle FS System Oracle Flash Storage System Administrator’s Guide for more information about thin provisioning.

  6. Click OK.
    Result:The newly created physical disk appears in the Physical Disks table in the content area of the page.

Before the physical disk can be used, you must present it as a Physical Disk to an access group.

For more information about creating a physical disk, refer to the information about creating LUNs in the Oracle Flash Storage System Administrator’s Guide.