clone_lun ‑modify

Changes the properties of an existing Clone LUN on the Oracle FS System.

SYNOPSIS

clone_lun ‑modify 
   ‑cloneLun clone‑lun‑id‑or‑fqn
   [‑name new‑name]
   [‑capacity capacity]
   [‑priority {premium | high | medium | low | archive}]
   [‑volumeGroup volume‑group‑id‑or‑fqn]
   [{‑fibreChannelAccess | ‑noFibreChannelAccess}]
   [{‑iscsiAccess | ‑noIscsiAccess}]
   [{ ‑maskedControllerPorts  /controller[/slot[/port]]
                           [, /controller[/slot[/port]]]...
    | ‑unMaskedControllerPorts /controller[/slot[/port]]
                           [, /controller[/slot[/port]]]...
    }]
   [{ ‑unmapped
    | ‑globalMapping lun‑number
    }]
   [{‑active | ‑inactive}]
   [‑clearPinnedData]
   [{‑disableRefTagChecking | ‑enableRefTagChecking}]
   [‑bootLun | ‑noBootLun]

   [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}]
   [{‑outputformat | ‑o} { text | xml }]
   [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]

DESCRIPTION

Use the clone_lun ‑modify command to change the Quality of Service (QoS) attributes for a Clone LUN to address the needs of a specific task, such as increasing the capacity that is allocated to the Clone LUN. You can also modify the mapping of a Clone LUN as well as change the Controller to which the Clone LUN is assigned.

Note: Only administrators with primary administrator, admin1, or admin2 roles are authorized to run the clone_lun -modify command.

OPTIONS

‑active

Enables the Clone LUN to be accessible and available for use immediately after the Clone LUN is modified. Enabling the Clone LUN to be accessible is the default.

‑bootLun

Identifies that the Clone LUN can be used as a boot drive in the SAN.

‑capacity

Specifies the storage space in gigabytes for the volume. The amount of space cannot be less than the current maximum capacity of the Clone LUN. This space is sometimes referred to as addressable capacity.

‑clearPinnedData

Clears any pinned data on the specified volume.

Important! Contact Oracle Customer Support to resolve any issues with the Backend SAS Interconnect, a storage condition, or both, which might be causing the pinned data. Clearing pinned data guarantees that host data is deleted permanently.

‑cloneLun

Specifies the ID or the fully qualified name (FQN) of the Clone LUN to modify.

‑disableRefTagChecking

Instructs the HBA to bypass the check of whether a host has written to a specific area of the LUN before the host reads from that same area. If this option is omitted, read-before-write error events can be generated.

‑enableRefTagChecking

Instructs the HBA to check whether a SAN host has written to a specific area of the LUN before the host reads from that area. When a host reads from a specific area before writing to that area, the Oracle FS System generates a read-before-write error event.

Note: This check is sometimes called a reference tag check and is a part of the process for ensuring data protection integrity.

‑fibreChannelAccess

Allows users to access to the volume through the Fibre Channel (FC) ports. By default, FC access is enabled.

‑globalMapping

Maps the Clone LUN globally to all hosts using the specified lun-number.

‑inactive

Renders the LUN volume invisible on the network. An inactive volume is not accessible and cannot be used by a SAN host.

‑iscsiAccess

Allows access to the modified Clone LUN through the iSCSI ports.

‑maskedControllerPorts

Restricts access to the Clone LUN through one or more Controller ports. Use the following format to mask all of the ports in a Controller, to mask all of the ports for a given Controller slot, or to mask only a specific Controller port: /⁠controller[/⁠slot[/⁠port]]

For controller, provide a string that includes the FQN or ID of the Controller.
For slot, specify the HBA slot number.
For port, specify the port number.

If you do not include this option, the Clone LUN becomes accessible on all Controller ports on the assigned node by default.

‑name

Specifies a new name for the Clone LUN. The name that you provide must be between 1 and 40 characters. Use double quotation marks around names containing one or more spaces or dashes to prevent parsing errors.

The following characters are invalid in a LUN name:

Tab
/ (slash) and \ (backslash)
. (dot) and .. (dot-dot)
Embedded tabs

Note: The clone_lun ‑modify command does not map the modified LUN if the Oracle FS System already contains a LUN with the specified name within the same volume group. You can use the clone_lun ‑modify command to map the modified Clone LUN after determining the name to assign.

‑noBootLun

Identifies that the Clone LUN cannot be used as a boot drive in the SAN. Not using the Clone LUN as a boot drive is the default.

‑noFibreChannelAccess

Disables access to the modified Clone LUN through FC ports. By default, access is enabled.

‑noIscsiAccess

Disables access to the modified Clone LUN through use of the iSCSI protocol. By default, the Clone LUN is not accessible through the iSCSI protocol.

‑priority

Assigns a priority level that determines the system response to incoming I/O requests against the Clone LUN. In general, the higher the priority level, the faster the system can respond to an access request. Valid priority levels:

premium. Indicates the highest priority for responding to requests in the processing queue. For Auto-Tier LUNs, busy LUN extents receive the highest priority when the system migrates the data to the higher-performing storage tiers.
high. Indicates the next highest priority for responding to requests in the processing queue. For Auto-Tier LUNs, busy LUN extents receive the next highest priority when the system migrates the data to the higher-performing storage tiers.
medium. Indicates an intermediate priority for responding to requests in the processing queue. For Auto-Tier LUNs, busy LUN extents receive an intermediate priority when the system migrates the data to the higher-performing storage tiers.
low. Indicates the next to lowest priority for responding to requests in the processing queue. For Auto-Tier LUNs, busy LUN extents receive the next to lowest priority when the system migrates the data to the higher-performing storage tiers.
archive. Indicates the lowest priority for responding to requests in the processing queue. For Auto-Tier LUNs, busy LUN extents receive the lowest priority when the system migrates the data to the higher-performing storage tiers.

‑unMaskedControllerPorts

Opens access to the volume through the Controller ports that were previously set to restricted access.

Specify the port using the form HBA slot number/port number. Specify the arguments in the following manner:

HBA slot number: Specifies the PCIE slot number of the HBA on which the port is located. The slot number must be 0 or greater.
port number: Identifies the port number on the HBA slot. The port number must be 0 or greater.

For example, 0/1 specifies port 1 on HBA slot 0 of the specified Controller.

‑unmapped

Prevents the Clone LUN from being detected or accessed by any SAN host.

‑volumeGroup

Specifies the FQN or the ID of the volume group to which the Clone LUN is assigned. If you do not include this option, the Clone LUN is assigned to the root level volume group.

EXAMPLE

Task

Change the name of a Clone LUN and increase the logical capacity. Change the priority to the highest processing queue setting for testing purposes, and make the Clone LUN accessible immediately.

Parameters

The fully qualified name (FQN) of the Clone LUN: /⁠user1_vg/⁠CLONE_DISK1
The new name of the Clone LUN: /⁠user1_vg/CLONE_DISK3
The size of the Clone LUN, in gigabytes: 128
The priority level: premium

$ fscli clone_lun ‑modify ‑cloneLun /⁠user1_vg/⁠CLONE_DISK1 ‑name CLONE_DISK3 ‑capacity 128 ‑priority premium