この製品のマニュアルセットは、偏向のない言語を使用するように配慮されています。このマニュアルセットでの偏向のない言語とは、年齢、障害、性別、人種的アイデンティティ、民族的アイデンティティ、性的指向、社会経済的地位、およびインターセクショナリティに基づく差別を意味しない言語として定義されています。製品ソフトウェアのユーザーインターフェイスにハードコードされている言語、RFP のドキュメントに基づいて使用されている言語、または参照されているサードパーティ製品で使用されている言語によりドキュメントに例外が存在する場合があります。シスコのインクルーシブランゲージに対する取り組みの詳細は、こちらをご覧ください。
このドキュメントは、米国シスコ発行ドキュメントの参考和訳です。リンク情報につきましては、日本語版掲載時点で、英語版にアップデートがあり、リンク先のページが移動/変更されている場合がありますことをご了承ください。あくまでも参考和訳となりますので、正式な内容については米国サイトのドキュメントを参照ください。
目次
This part contains the following chapters:
You can create a storage profile both at an org level and at a service-profile level. A service profile can have a dedicated storage profile as well as a storage profile at an org level.
In UCS M-Series Modular Servers, servers in a chassis can use storage that is centralized in that chassis. You can select and configure the disks to be used for storage. A logical collection of these physical disks is called a disk group. Disk groups allow you to organize local disks. The storage controller controls the creation and configuration of disk groups.
A disk group configuration policy defines how a disk group is created and configured. The policy specifies the RAID level to be used for the disk group. It also specifies either a manual or an automatic selection of disks for the disk group, and roles for disks. You can use a disk group policy to manage multiple disk groups. However, a single disk group can be managed only by one disk group policy.
A hot spare is an unused extra disk that can be used by a disk group in the case of failure of a disk in the disk group. Hot spares can be used only in disk groups that support a fault-tolerant RAID level.
A disk group can be partitioned into virtual drives. Each virtual drive appears as an individual physical device to the Operating System.
All virtual drives in a disk group must be managed by using a single disk group policy.
Applying—Creation of the virtual drive is in progress.
Applied—Creation of the virtual drive is complete, or virtual disk policy changes are configured and applied successfully.
Failed to apply—Creation, deletion, or renaming of a virtual drive has failed due to errors in the underlying storage subsystem.
Orphaned—The service profile that contained this virtual drive is deleted.
Not in use—The service profile that contained this virtual drive is in the disassociated state.
Optimal—The virtual drive operating condition is good. All configured drives are online.
Degraded—The virtual drive operating condition is not optimal. One of the configured drives has failed or is offline.
(注) |
This state does not occur if you select the always write back mode. |
Partially degraded—The operating condition in a RAID 6 virtual drive is not optimal. One of the configured drives has failed or is offline. RAID 6 can tolerate up to two drive failures.
Offline—The virtual drive is not available to the RAID controller. This is essentially a failed state.
Unknown—The state of the virtual drive is not known.
The RAID level of a disk group describes how the data is organized on the disk group for the purpose of ensuring availability, redundancy of data, and I/O performance.
Striping—Segmenting data across multiple physical devices. This improves performance by increasing throughput due to simultaneous device access.
Mirroring—Writing the same data to multiple devices to accomplish data redundancy.
Parity—Storing of redundant data on an additional device for the purpose of error correction in the event of device failure. Parity does not provide full redundancy, but it allows for error recovery in some scenarios.
Spanning—Allows multiple drives to function like a larger one. For example, four 20 GB drives can be combined to appear as a single 80 GB drive.
RAID 0 Striped—Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails.
RAID 1 Mirrored—Data is written to two disks, providing complete data redundancy if one disk fails. The maximum array size is equal to the available space on the smaller of the two drives.
RAID 5 Striped Parity—Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates.
RAID 5 distributes parity data blocks among the disks that are part of a RAID-5 group and requires a minimum of three disks.
RAID 6 Striped Dual Parity—Data is striped across all disks in the array and two sets of parity data are used to provide protection against failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored.
Other than addition of a second parity block, RAID 6 is identical to RAID 5 . A minimum of four disks are required for RAID 6.
RAID 10 Mirrored and Striped—RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates through block-level striping. RAID 10 is mirroring without parity and block-level striping. A minimum of four disks are required for RAID 10.
When you specify a disk group configuration, and do not specify the local disks in it, Cisco UCS Manager determines the disks to be used based on the criteria specified in the disk group configuration policy. Cisco UCS Manager can make this selection of disks in multiple ways.
When all qualifiers match for a set of disks, then disks are selected sequentially according to their slot number. Regular disks and dedicated hot spares are selected by using the lowest numbered slot.
The following is the disk selection process:
Iterate over all local LUNs that require the creation of a new virtual drive. Iteration is based on the following criteria, in order:
(注) |
If you specify Any as the type of drive, the first available drive is selected. After this drive is selected, subsequent drives will be of a compatible type. For example, if the first drive was SATA, all subsequent drives would be SATA. Cisco UCS Manager Release 2.5 supports only SATA and SAS. Cisco UCS Manager Release 2.5 does not support RAID migration. |
Select dedicated hot spares by using the same method as normal disks. Disks are only selected if they are in an Unconfigured Good state.
If a provisioned LUN has the same disk group policy as a deployed virtual drive, then try to deploy the new virtual drive in the same disk group. Otherwise, try to find new disks for deployment.
Some modifications that are made to the LUN configuration when LUNs are already deployed on an associated server are supported.
The following are the types of modifications that can be performed:
Creation of a new virtual drive.
Deletion of an existing virtual drive, which is in the orphaned state.
The removal of a LUN will cause a warning to be displayed. Ensure that you take action to avoid loss of data.
Some modifications to existing LUNs are not possible without destroying the original virtual drive and creating a new one. All data is lost in these types of modification, and these modifications are not supported.
RAID-level changes that do not support reconstruction. For example, RAID5 to RAID1.
Shrinking the size of a virtual drive.
RAID-level changes that support reconstruction, but where there are other virtual drives present on the same drive group.
Disk removal when there is not enough space left on the disk group to accommodate the virtual drive.
Explicit change in the set of disks used by the virtual drive.
When the following sequence of events takes place:
The LUN is successfully deployed, which means that a virtual drive is created, which uses the slot.
You remove a disk from the slot, possibly because the disk failed.
You insert a new working disk into the same slot.
For non-redundant virtual drives (RAID 0), when a physical drive is removed, the state of the virtual drive is Inoperable. When a new working drive is inserted, the new physical drive goes to an Unconfigured Good state.
For non-redundant virtual drives, there is no way to recover the virtual drive. You must delete the virtual drive and re-create it.
For redundant virtual drives (RAID 1, RAID 5, RAID 6, RAID 10) with no hot spare drives assigned, virtual drive mismatch, virtual drive member missing, and local disk missing faults appear until you insert a working physical drive into the same slot from which the old physical drive was removed.
If the physical drive size is greater than or equal to that of the old drive, the storage controller automatically uses the new drive for the virtual drive. The new drive goes into the Rebuilding state. After rebuild is complete, the virtual drive goes back into the Online state.
For redundant virtual drives (RAID 1, RAID 5, RAID 6, RAID 10) with hot spare drives assigned, when a drive fails, or when you remove a drive, the dedicated hot spare drive, if available, goes into the Rebuilding state with the virtual drive in the Degraded state. After rebuilding is complete, that drive goes to the Online state.
Cisco UCSM raises a disk missing and virtual drive mismatch fault because although the virtual drive is operational, it does not match the physical configuration that Cisco UCSM expects.
if you insert a new disk in the slot with the disk missing, automatic copy back starts from the earlier hot spare disk to the newly inserted disk. After copy back, the hot spare disk is restored. In this state all faults are cleared.
If automatic copy back does not start, and the newly inserted disk remains in the Unconfigured Good, JBOD, or Foreign Configuration state, remove the new disk from the slot, reinsert the earlier hot spare disk into the slot, and import foreign configuration. This initiates the rebuilding process and the drive state becomes Online. Now, insert the new disk in the hot spare slot and mark it as hot spare to match it exactly with the information available in Cisco UCSM.
If a hot spare drive is replaced, the new hot spare drive will go to the Unconfigured Good, Unconfigured Bad, JBOD, or Foreign Configuration state.
Cisco UCSM will raise a virtual drive mismatch or virtual drive member mismatch fault because the hot spare drive is in a state different from the state configured in Cisco UCSM.
You must manually clear the fault. To do this, you must perform the following actions:
If you insert new physical drives into unused slots, neither the storage controller nor Cisco UCSM will make use of the new drive even if the drive is in the Unconfigured Good state and there are virtual drives that are missing good physical drives.
The drive will simply go into the Unconfigured Good state. To make use of the new drive, you will need to modify or create LUNs to reference the newly inserted drive.
When you use UCSM to create a virtual drive, UCSM assigns a unique ID that can be used to reliably identify the virtual drive for further operations. UCSM also provides the flexibility to provide a name to the virtual drive at the time of service profile association. Any virtual drive without a service profile or a server reference is marked as an orphan virtual drive.
In addition to a unique ID, a name is assigned to the drive. Names can be assigned in two ways:
When configuring a virtual drive, you can explicitly assign a name that can be referenced in storage profiles.
If you have not preprovisioned a name for the virtual drive, UCSM generates a unique name for the virtual drive.
You can rename virtual drives that are not referenced by any service profile or server.
A LUN is dereferenced when it is no longer used by any service profile. This can occur as part of the following scenarios:
The LUN is no longer referenced from the storage profile
The storage profile is no longer referenced from the service profile
The server is disassociated from the service profile
The server is decommissioned
When the LUN is no longer referenced, but the server is still associated, re-association occurs.
When the service profile that contained the LUN is disassociated, the LUN state is changed to Not in use.
When the service profile that contained the LUN is deleted, the LUN state is changed to Orphaned.
Cisco UCS Manager does not support a combination of SAS and SATA drives in storage configurations.
Cisco UCS Manager Release 2.5 only supports a stripe size of 64k and more. Having a stripe size of less than 64k will result in failure when a service profile is associated.
In Cisco UCS Manager Release 2.5, the storage controller allows 64 virtual drives per controller, and up to 4 virtual drives per server, of which up to 2 virtual drives are bootable.
(注) |
Only the modular servers in Cisco UCSME-2814 compute cartridges include support for up to 4 virtual drives per server. |
You can choose to configure a disk group policy through automatic or manual disk selection. Configuring a disk group involves the following:
1. UCS-A# scope org org-name
2. UCS-A /org# create disk-group-config-policy disk-group-name
3. UCS-A /org/disk-group-config-policy* # set raid-level raid-level
4. UCS-A /org/disk-group-config-policy* # commit-buffer
This example shows how to set the RAID level for a disk group configuration policy.
UCS-A# scope org UCS-A /org # create disk-group-config-policy raid5policy UCS-A /org/disk-group-config-policy* # set raid-level raid-5-striped-parity UCS-A /org/disk-group-config-policy* # commit-buffer
Automatically or manually configure disks as part of the disk group configuration policy.
You can allow UCSM to automatically select and configure disks in a disk group.
When you create a disk group with RAID 1 policy and configure four disks for it, a RAID1E configuration is created internally by the storage controller.
1. UCS-A# scope org org-name
2. UCS-A /org# enter disk-group-config-policy disk-group-name
3. UCS-A /org/disk-group-config-policy* # enter disk-group-qual
4. UCS-A /org/disk-group-config-policy/disk-group-qual* # set drive-type drive-type
5. UCS-A /org/disk-group-config-policy/disk-group-qual* # set min-drive-size drive-size
6. UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-ded-hot-spares hot-spare-num
7. UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-drives drive-num
8. UCS-A /org/disk-group-config-policy/disk-group-qual* # commit-buffer
This example shows how to automatically configure disks for a disk group configuration policy.
UCS-A# scope org UCS-A /org # enter disk-group-config-policy raid5policy UCS-A /org/disk-group-config-policy* # enter disk-group-qual UCS-A /org/disk-group-config-policy/disk-group-qual* # set drive-type ssd UCS-A /org/disk-group-config-policy/disk-group-qual* # set min-drive-size 1000 UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-ded-hot-spares 2 UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-drives 7 UCS-A /org/disk-group-config-policy/disk-group-qual* # commit-buffer
Configure Virtual Drives.
You can manually configure disks for a disk group.
When you create a disk group with RAID 1 policy and configure four disks for it, a RAID 1E configuration is created internally by the storage controller.
1. UCS-A# scope org org-name
2. UCS-A /org# enter disk-group-config-policy disk-group-name
3. UCS-A /org/disk-group-config-policy* # create local-disk-config-ref slot-num
4. UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set role role
5. UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set span-id span-id
6. UCS-A /org/disk-group-config-policy/local-disk-config-ref *# commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
||
ステップ 2 | UCS-A /org# enter disk-group-config-policy disk-group-name | Enters disk group configuration policy mode for the specified disk group name. |
||
ステップ 3 | UCS-A /org/disk-group-config-policy* # create local-disk-config-ref slot-num | Creates a local disk configuration reference for the specified slot and enters local disk configuration reference mode. |
||
ステップ 4 | UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set role role |
|
||
ステップ 5 | UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set span-id span-id | Specifies the ID of the span group to which the disk belongs. Disks belonging to a single span group can be treated as a single disk with a larger size. The values range from 0 to 8. You can also set the Span ID as Unspecified when spanning information is not required.
|
||
ステップ 6 | UCS-A /org/disk-group-config-policy/local-disk-config-ref *# commit-buffer | Commits the transaction to the system configuration. |
This example shows how to manually configure disks for a disk group configuration policy.
UCS-A# scope org UCS-A /org # enter disk-group-config-policy raid5policy UCS-A /org/disk-group-config-policy* # create local-disk-config-ref 1 UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set role ded-hot-spare UCS-A /org/disk-group-config-policy/local-disk-config-ref* # set span-id 1 UCS-A /org/disk-group-config-policy/local-disk-config-ref *# commit-buffer
Configure Virtual Drive Properties.
All virtual drives in a disk group must be managed by using a single disk group policy.
1. UCS-A# scope org org-name
2. UCS-A /org# scope disk-group-config-policy disk-group-name
3. UCS-A /org/disk-group-config-policy* # create virtual-drive-def
4. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set access-policy policy-type
5. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set drive-cache state
6. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set io-policy policy-type
7. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set read-policy policy-type
8. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set strip-size strip-size
9. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set write-cache-policy policy-type
10. UCS-A /org/disk-group-config-policy/virtual-drive-def* # commit-buffer
11. UCS-A /org/disk-group-config-policy/virtual-drive-def* # show
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# scope disk-group-config-policy disk-group-name | Enters disk group configuration policy mode for the specified disk group name. |
ステップ 3 | UCS-A /org/disk-group-config-policy* # create virtual-drive-def | Creates a virtual drive definition and enters the virtual drive definition mode. |
ステップ 4 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set access-policy policy-type |
|
ステップ 5 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set drive-cache state |
In Cisco UCS Release 2.5, the drive cache state cannot be changed. It will remain as platform-default, irrespective of the drive cache state that you select. |
ステップ 6 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set io-policy policy-type |
|
ステップ 7 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set read-policy policy-type |
|
ステップ 8 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set strip-size strip-size | Specifies the strip size. This can be one of the following: |
ステップ 9 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set write-cache-policy policy-type |
|
ステップ 10 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # commit-buffer | Commits the transaction to the system configuration. |
ステップ 11 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # show | Displays the configured virtual drive properties. |
This example shows how to configure virtual disk properties:
UCS-A# scope org UCS-A /org # scope disk-group-config-policy raid0policy UCS-A /org/disk-group-config-policy # create virtual-drive-def UCS-A /org/disk-group-config-policy/virtual-drive-def* # set access-policy read-write UCS-A /org/disk-group-config-policy/virtual-drive-def* # set drive-cache enable UCS-A /org/disk-group-config-policy/virtual-drive-def* # set io-policy cached UCS-A /org/disk-group-config-policy/virtual-drive-def* # set read-policy normal UCS-A /org/disk-group-config-policy/virtual-drive-def* # set strip-size 1024 UCS-A /org/disk-group-config-policy/virtual-drive-def* # set write-cache-policy write-through UCS-A /org/disk-group-config-policy/virtual-drive-def* # commit-buffer UCS-A /org/disk-group-config-policy/virtual-drive-def # show Virtual Drive Def: Strip Size (KB): 1024KB Access Policy: Read Write Read Policy: Normal Configured Write Cache Policy: Write Through IO Policy: Cached Drive Cache: Enable UCS-A /org/disk-group-config-policy/virtual-drive-def #
Create a Storage Profile
You can create a storage profile at the org level and at the service-profile level.
1. UCS-A# scope org org-name
2. UCS-A /org # create storage-profile storage-profile-name
3. UCS-A /org/storage-profile* # commit-buffer
4. (任意) UCS-A /org* # enter service-profile service-profile-name
5. (任意) UCS-A /org/service-profile* # create storage-profile-def
6. UCS-A /org/service-profile/storage-profile-def* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org # create storage-profile storage-profile-name | Creates a storage profile with the specified name at the org level and enters storage-profile configuration mode. |
ステップ 3 | UCS-A /org/storage-profile* # commit-buffer | Commits the transaction to the system configuration. |
ステップ 4 | UCS-A /org* # enter service-profile service-profile-name | (任意) Enters the specified service profile. |
ステップ 5 | UCS-A /org/service-profile* # create storage-profile-def | (任意) Creates a storage profile at the service-profile level. |
ステップ 6 | UCS-A /org/service-profile/storage-profile-def* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to create a storage profile at the org level.
UCS-A# scope org UCS-A /org # create storage-profile stp2 UCS-A /org/storage-profile* # commit-buffer
This example shows how to create a storage profile at the service-profile level.
UCS-A# scope org UCS-A /org* # enter service-profile sp1 UCS-A /org/service-profile* # create storage-profile-def UCS-A /org/service-profile/storage-profile-def* # commit-buffer
Create Local LUNs
You can delete a storage profile that was created at the org level or at the service-profile level.
1. UCS-A# scope org org-name
2. UCS-A /org # delete storage-profile storage-profile-name
3. (任意) UCS-A /org # scope service-profile service-profile-name
4. (任意) UCS-A /org/service-profile # delete storage-profile-def
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org # delete storage-profile storage-profile-name | Deletes the storage profile with the specified name at the org level. |
ステップ 3 | UCS-A /org # scope service-profile service-profile-name | (任意) Enters the specified service profile. |
ステップ 4 | UCS-A /org/service-profile # delete storage-profile-def | (任意) Deletes the dedicated storage profile at the service-profile level. |
This example shows how to delete a storage profile at the org level.
UCS-A # scope org UCS-A /org # delete storage-profile stor1
This example shows how to delete a storage profile at the service-profile level.
UCS-A # scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile # delete storage-profile-def
You can create local LUNs within a storage profile at the org level and within a dedicated storage profile at the service-profile level.
1. UCS-A# scope org org-name
2. UCS-A /org # enter storage-profile storage-profile-name
3. UCS-A /org/storage-profile* # create local-lun lun-name
4. UCS-A /org/storage-profile/local-lun* # set auto-deploy {auto-deploy | no-auto-deploy}
5. UCS-A /org/storage-profile/local-lun* # set disk-policy-name disk-policy-name
6. UCS-A /org/storage-profile/local-lun* # set order order-num
7. UCS-A /org/storage-profile/local-lun* # set size size
8. UCS-A /org/storage-profile/local-lun* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
||
ステップ 2 | UCS-A /org # enter storage-profile storage-profile-name | Enters storage-profile mode for the specified storage profile. |
||
ステップ 3 | UCS-A /org/storage-profile* # create local-lun lun-name | Creates a local LUN with the specified name. |
||
ステップ 4 | UCS-A /org/storage-profile/local-lun* # set auto-deploy {auto-deploy | no-auto-deploy} | Specifies whether the LUN should be auto-deployed or not. |
||
ステップ 5 | UCS-A /org/storage-profile/local-lun* # set disk-policy-name disk-policy-name | Specifies the name of the disk policy name for this LUN. |
||
ステップ 6 | UCS-A /org/storage-profile/local-lun* # set order order-num | Specifies the order of this LUN. The order can range from 1 to 64. You can also specify that the order should be lowest-available for the system to automatically assign the lowest available order to the LUN. Multiple LUNs referenced by a storage profile must have unique names and unique orders. |
||
ステップ 7 | UCS-A /org/storage-profile/local-lun* # set size size | Specifies the size of this LUN in GB. The size can range from 1 GB to 10240 GB.
|
||
ステップ 8 | UCS-A /org/storage-profile/local-lun* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to configure a local LUN within a storage profile at the org level.
UCS-A# scope org UCS-A /org # enter storage-profile stp2 UCS-A /org/storage-profile* # create local-lun lun2 UCS-A /org/storage-profile/local-lun* # set disk-policy-name dpn2 UCS-A /org/storage-profile/local-lun* # set order 2 UCS-A /org/storage-profile/local-lun* # set size 1000 UCS-A /org/storage-profile/local-lun* # commit-buffer
This example shows how to configure a local LUN within a dedicated storage profile at the service-profile level.
UCS-A# scope org UCS-A /org* # enter service-profile stp1 UCS-A /org/service-profile* # enter storage-profile-def UCS-A /org/service-profile/storage-profile-def # create local-lun lun1 UCS-A /org/service-profile/storage-profile-def/local-lun* # set disk-policy-name dpn1 UCS-A /org/service-profile/storage-profile-def/local-lun* # set order 1 UCS-A /org/service-profile/storage-profile-def/local-lun* # set size 1000 UCS-A /org/service-profile/storage-profile-def/local-lun* # commit-buffer
Associate a Storage Profile with a Service Profile
You can use the set order command to change the local LUN visibility order to the server. This operation will reboot the server.
1. UCS-A# scope org org-name
2. UCS-A /org # enter storage-profile storage-profile-name
3. UCS-A /org/storage-profile # enter local-lun lun-name
4. UCS-A /org/storage-profile/local-lun* # set disk-policy-name disk-policy-name
5. UCS-A /org/storage-profile/local-lun # set order order-num
6. UCS-A /org/storage-profile/local-lun* # set size size
7. UCS-A /org/storage-profile/local-lun # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org # enter storage-profile storage-profile-name | Enters storage-profile mode for the specified storage profile. |
ステップ 3 | UCS-A /org/storage-profile # enter local-lun lun-name | Enters local-lun mode for the specified local LUN. |
ステップ 4 | UCS-A /org/storage-profile/local-lun* # set disk-policy-name disk-policy-name | Specifies the name of the disk policy name for this LUN. |
ステップ 5 | UCS-A /org/storage-profile/local-lun # set order order-num | Specifies the order of this LUN. The order can range from 1 to 64. You can also specify that the order should be lowest-available for the system to automatically assign the lowest available order to the LUN. |
ステップ 6 | UCS-A /org/storage-profile/local-lun* # set size size | Specifies the size of this LUN in GB. The size can range from 1 GB to 10240 GB. |
ステップ 7 | UCS-A /org/storage-profile/local-lun # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to reorder a local LUN within a storage profile at the org level.
UCS-A# scope org UCS-A /org # enter storage-profile stp1 UCS-A /org/storage-profile* # enter local-lun lun1 UCS-A /org/storage-profile/local-lun* # set disk-policy-name dpn1 UCS-A /org/storage-profile/local-lun* # set order 1 UCS-A /org/storage-profile/local-lun* # set size 10 UCS-A /org/storage-profile/local-lun* # exit UCS-A /org/storage-profile* # enter local-lun lun2 UCS-A /org/storage-profile/local-lun* # set disk-policy-name dpn2 UCS-A /org/storage-profile/local-lun* # set order 2 UCS-A /org/storage-profile/local-lun* # set size 10 UCS-A /org/storage-profile/local-lun* # exit UCS-A /org/storage-profile* # commit-buffer UCS-A /org/storage-profile # show configuration enter storage-profile stp1 enter local-lun lun1 set auto-deploy auto-deploy set disk-policy-name dpn1 set order 1 set size 10 exit enter local-lun lun2 set auto-deploy auto-deploy set disk-policy-name dpn2 set order 2 set size 10 exit set descr "" exit UCS-A /org/storage-profile # enter local-lun lun1 UCS-A /org/storage-profile/local-lun # set order 2 UCS-A /org/storage-profile/local-lun* # exit UCS-A /org/storage-profile* # enter local-lun lun2 UCS-A /org/storage-profile/local-lun* # set order 1 UCS-A /org/storage-profile/local-lun* # exit UCS-A /org/storage-profile* # commit-buffer UCS-A /org/storage-profile # show configuration enter storage-profile stp1 enter local-lun lun1 set auto-deploy auto-deploy set disk-policy-name dpn1 set order 2 set size 10 exit enter local-lun lun2 set auto-deploy auto-deploy set disk-policy-name dpn2 set order 1 set size 10 exit set descr "" exit
When a LUN is deleted, the corresponding virtual drive is marked as orphan after the virtual drive reference is removed from the server.
1. UCS-A# scope org org-name
2. UCS-A /org # enter storage-profile storage-profile-name
3. (任意) UCS-A /org/storage-profile* # show local-lun
4. UCS-A /org/storage-profile* # delete local-lun lun-name
5. UCS-A /org/storage-profile* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org # enter storage-profile storage-profile-name | Enters storage-profile mode for the specified storage profile. |
ステップ 3 | UCS-A /org/storage-profile* # show local-lun | (任意) Displays the local LUNs in the specified storage profile. |
ステップ 4 | UCS-A /org/storage-profile* # delete local-lun lun-name | Deletes the specified LUN. |
ステップ 5 | UCS-A /org/storage-profile* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to delete a LUN in a storage profile.
UCS-A # scope org UCS-A /org # enter storage-profile stp2 UCS-A /org/storage-profile # show local-lun Local SCSI LUN: LUN Name Size (GB) Order Disk Policy Name Auto Deploy ---------- ----------- ---------------- ---------------- ----------- luna 1 2 raid0 Auto Deploy lunb 1 1 raid0 Auto Deploy UCS-A /org/storage-profile # delete local-lun luna UCS-A /org/storage-profile* # commit-buffer UCS-A /org/storage-profile* # show local-lun Local SCSI LUN: LUN Name Size (GB) Order Disk Policy Name Auto Deploy ---------- ----------- ---------------- ---------------- ----------- lunb 1 1 raid0 Auto Deploy
A storage profile created under org can be referred by multiple service profiles, and a name reference in service profile is needed to associate the storage profile with a service profile.
Storage profiles can be defined under org and under service profile (dedicated). Hence, a service profile inherits local LUNs from both possible storage profiles. A service profile can have a maximum of two such local LUNs.
1. UCS-A# scope org org-name
2. UCS-A /org # scope service-profile service-profile-name
3. UCS-A /org/service-profile # set storage-profile-name storage-profile-name
4. UCS-A /org/service-profile* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
||
ステップ 2 | UCS-A /org # scope service-profile service-profile-name | Enters the specified service profile mode. |
||
ステップ 3 | UCS-A /org/service-profile # set storage-profile-name storage-profile-name | Associates the specified storage profile with the service profile.
|
||
ステップ 4 | UCS-A /org/service-profile* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to associate a storage profile with a service profile.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile # set storage-profile-name stp2
This example shows how to dissociate a service profile from a storage profile.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile # set storage-profile-name ""
Storage profiles can be defined under org and as a dedicated storage profile under service profile. Thus, a service profile inherits local LUNs from both possible storage profiles. It can have a maximum of 2 such local LUNs. You can display the details of all local LUNs inherited by a service profile by using the following command:
1. UCS-A /org/service-profile # show local-lun-ref
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A /org/service-profile # show local-lun-ref |
|
UCS-A /org/service-profile # show local-lun-ref Local LUN Ref: Profile LUN Name Admin State RAID Level Provisioned Size (GB) Assigned Size (MB) Config State Referenced Lun Deploy Name ID Drive State ---------------- ----------- ---------------------- ---------------------- -------------------- ------------ -------------- ----------- ----------- ----------- luna Online RAID 0 Striped 1 1024 Applied luna-1 luna-1 1003 Optimal lunb Online RAID 0 Striped 1 1024 Applied lunb-1 lunb-1 1004 Optimal UCS-A /org/service-profile # Local LUN Ref: Name Admin State RAID Level Provisioned Size (GB) Assigned Size (MB) Config State Referenced Lun Deploy Name ID Drive State ---------------- ----------- ---------------------- ---------------------- -------------------- ------------ -------------- ----------- ----------- ----------- lun111 Online RAID 0 Striped 30 30720 Applied lun111-1 lun111-1 1001 Optimal lun201 Online Unspecified 1 0 Not Applied
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # scope adapter adapter-id
3. UCS-A /chassis/cartridge/server/adapter # scope host-scsi host-scsi-id
4. UCS-A /chassis/cartridge/server/adapter/host-scsi # show detail expand
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope server chassis-num / cartridge-id / server-num | Enters cartridge server mode for the specified modular server in the specified chassis and cartridge. |
ステップ 2 | UCS-A /chassis/cartridge/server # scope adapter adapter-id | Enters adapter mode for the specified adapter. |
ステップ 3 | UCS-A /chassis/cartridge/server/adapter # scope host-scsi host-scsi-id | Enters host-scsi mode for the specified host-scsi. |
ステップ 4 | UCS-A /chassis/cartridge/server/adapter/host-scsi # show detail expand | Displays detailed information about the LUNs that are being used by the specified modular server. |
This example shows how to display detailed information about the LUNs that are being used by modular server 1/1/1.
UCS-A # scope server 1/1/1 UCS-A /chassis/cartridge/server # scope adapter 1 UCS-A /chassis/cartridge/server/adapter # scope host-scsi 1 UCS-A /chassis/cartridge/server/adapter/host-scsi # show detail expand Host Scsi Interface: ID: 1 Local Lun Interface: Lun Name: lun-uefi Lun Id: 1008 Lun Order: 1 Oper Lun Id: 7 Boot Dev: Disabled Lun Dn: sys/chassis-1/storage-SAS-1/vd-1008
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata}
3. UCS-A /chassis/raid-controller # set admin-state import-foreign-configuration
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope chassis chassis-num | Enters chassis mode for the specified chassis. |
ステップ 2 | UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata} | Enters RAID controller chassis mode. |
ステップ 3 | UCS-A /chassis/raid-controller # set admin-state import-foreign-configuration | Allows import of configurations from local disks that are in the Foreign Configuration state. |
This example shows how to import foreign configurations from local disks that are in the Foreign Configuration state:
UCS-A# scope chassis 1 UCS-A /chassis # scope raid-controller 1 sas UCS-A /chassis/raid-controller # set admin-state import-foreign-configuration UCS-A /chassis/raid-controller* #
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata}
3. UCS-A /chassis/raid-controller # scope local-disk local-disk-id
4. UCS-A /chassis/raid-controller/local-disk # set admin-state {clear-foreign-configuration | dedicated-hot-spare [admin-vd-id] | prepare-for-removal | remove-hot-spare | unconfigured-good | undo-prepare-for-removal}
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope chassis chassis-num | Enters chassis mode for the specified chassis. |
ステップ 2 | UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata} | Enters RAID controller chassis mode. |
ステップ 3 | UCS-A /chassis/raid-controller # scope local-disk local-disk-id | Enters local disk configuration mode. |
ステップ 4 | UCS-A /chassis/raid-controller/local-disk # set admin-state {clear-foreign-configuration | dedicated-hot-spare [admin-vd-id] | prepare-for-removal | remove-hot-spare | unconfigured-good | undo-prepare-for-removal} |
|
This example shows how to clear any foreign configuration from a local disk:
UCS-A /chassis/raid-controller/local-disk # set admin-state clear-foreign-configuration
This example shows how to specify a local disk as a dedicated hot spare:
UCS-A /chassis/raid-controller/local-disk* # set admin-state dedicated-hot-spare 1001
This example shows how to specify that a local disk is marked for removal from the chassis:
UCS-A /chassis/raid-controller/local-disk* # set admin-state prepare-for-removal
This example shows how to specify that a local disk is marked for removal as a hot spare:
UCS-A /chassis/raid-controller/local-disk* # set admin-state remove-hot-spare
This example shows how to specify that a local disk is working, but is unconfigured for use:
UCS-A /chassis/raid-controller/local-disk* # set admin-state unconfigured-good
This example shows how to specify that a local disk is no longer marked for removal from the chassis:
UCS-A /chassis/raid-controller/local-disk* # set admin-state undo-prepare-for-removal
The following operations can be performed only on orphaned virtual drives:
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata}
3. (任意) UCS-A /chassis/raid-controller # delete virtual-drive id virtual-drive-id
4. (任意) UCS-A /chassis/raid-controller # delete virtual-drive name virtual-drive-name
5. (任意) UCS-A /chassis/raid-controller # scope virtual-drive virtual-drive-id
6. UCS-A /chassis/raid-controller/virtual-drive # set admin-state delete
7. UCS-A /chassis/raid-controller/virtual-drive # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope chassis chassis-num | Enters chassis mode for the specified chassis. |
ステップ 2 | UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata} | Enters RAID controller chassis mode. |
ステップ 3 | UCS-A /chassis/raid-controller # delete virtual-drive id virtual-drive-id | (任意) Deletes the orphaned virtual drive with the specified virtual drive ID. |
ステップ 4 | UCS-A /chassis/raid-controller # delete virtual-drive name virtual-drive-name | (任意) Deletes the orphaned virtual drive with the specified virtual drive name. |
ステップ 5 | UCS-A /chassis/raid-controller # scope virtual-drive virtual-drive-id | (任意) Enters virtual drive mode for the specified orphaned virtual drive. |
ステップ 6 | UCS-A /chassis/raid-controller/virtual-drive # set admin-state delete | Deletes the orphaned virtual drive. |
ステップ 7 | UCS-A /chassis/raid-controller/virtual-drive # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to delete an orphan virtual drive by specifying the virtual drive ID.
UCS-A# scope chassis 1 UCS-A /chassis # scope raid-controller 1 sas UCS-A /chassis/raid-controller # show virtual-drive Virtual Drive: ID: 1001 Name: lun111-1 Block Size: 512 Blocks: 62914560 Size (MB): 30720 Operability: Operable Presence: Equipped Oper Device ID: 0 Change Qualifier: No Change Config State: Applied Deploy Action: No Action ID: 1002 Name: luna-1 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 1 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1003 Name: lunb-1 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 2 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1004 Name: lunb-2 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 3 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1005 Name: luna-2 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 4 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ... UCS-A /chassis/raid-controller # delete virtual-drive id 1002 Warning: When committed, the virtual drive will be deleted, which may result in data loss. UCS-A /chassis/raid-controller # commit-buffer
This example shows how to delete an orphan virtual drive by specifying the virtual drive name.
UCS-A# scope chassis 1 UCS-A /chassis # scope raid-controller 1 sas UCS-A /chassis/raid-controller # show virtual-drive Virtual Drive: ID: 1001 Name: lun111-1 Block Size: 512 Blocks: 62914560 Size (MB): 30720 Operability: Operable Presence: Equipped Oper Device ID: 0 Change Qualifier: No Change Config State: Applied Deploy Action: No Action ID: 1003 Name: lunb-1 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 2 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1004 Name: lunb-2 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 3 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1005 Name: luna-2 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 4 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ... UCS-A /chassis/raid-controller # delete virtual-drive name lunb-1 Warning: When committed, the virtual drive will be deleted, which may result in data loss. UCS-A /chassis/raid-controller # commit-buffer
This example shows how to delete an orphan virtual drive by setting the admin-state.
UCS-A# scope chassis 1 UCS-A /chassis # scope raid-controller 1 sas UCS-A /chassis/raid-controller # scope virtual-drive 1004 UCS-A /chassis/raid-controller/virtual-drive # set admin-state delete Warning: When committed, the virtual drive will be deleted, which may result in data loss. UCS-A /chassis/raid-controller/virtual-drive # commit-buffer
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata}
3. UCS-A /chassis/raid-controller # scope virtual-drive virtual-drive-id
4. UCS-A /chassis/raid-controller/virtual-drive # set name virtual-drive-name
5. UCS-A /chassis/raid-controller/virtual-drive # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope chassis chassis-num | Enters chassis mode for the specified chassis. |
ステップ 2 | UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata} | Enters RAID controller chassis mode. |
ステップ 3 | UCS-A /chassis/raid-controller # scope virtual-drive virtual-drive-id | Enters virtual drive mode for the specified virtual drive. |
ステップ 4 | UCS-A /chassis/raid-controller/virtual-drive # set name virtual-drive-name | Specifies a name for the orphan virtual drive. |
ステップ 5 | UCS-A /chassis/raid-controller/virtual-drive # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to specify a name for an orphan virtual drive.
UCS-A /chassis # scope raid-controller 1 sas UCS-A /chassis/raid-controller # scope virtual-drive 1060 UCS-A /chassis/raid-controller/virtual-drive* # set name vd1 UCS-A /chassis/raid-controller/virtual-drive* # commit-buffer
(注) |
In Cisco UCS Manager Release 2.5, you cannot configure JBOD as a boot device. |
1. UCS-A# scope org org-name
2. UCS-A /org # scope boot-policy policy-name
3. UCS-A /org/boot-policy # create storage
4. UCS-A /org/boot-policy/storage # create local
5. UCS-A /org/boot-policy/storage/local/ # create local-lun
6. UCS-A /org/boot-policy/storage/local/local-lun # create local-lun-image-path {primary | secondary}
7. UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # set lunname lun_name
8. UCS-A /org/boot-policy/storage/local/local-storage-device # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . |
ステップ 2 | UCS-A /org # scope boot-policy policy-name | Enters organization boot policy mode for the specified boot policy. |
ステップ 3 | UCS-A /org/boot-policy # create storage | Creates a storage boot for the boot policy and enters organization boot policy storage mode. |
ステップ 4 | UCS-A /org/boot-policy/storage # create local | Creates a local storage location and enters the boot policy local storage mode. |
ステップ 5 | UCS-A /org/boot-policy/storage/local/ # create local-lun | Specifies a local hard disk drive as the local storage. |
ステップ 6 | UCS-A /org/boot-policy/storage/local/local-lun # create local-lun-image-path {primary | secondary} | Specifies the boot order for the LUN that you specify. |
ステップ 7 | UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # set lunname lun_name | Specifies the name of the LUN that you want to boot from. |
ステップ 8 | UCS-A /org/boot-policy/storage/local/local-storage-device # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a boot policy named lab1-boot-policy, create a local hard disk drive boot for the policy, specify a boot order and a LUN to boot from, and commit the transaction:
UCS-A# scope org / UCS-A /org* # scope boot-policy lab1-boot-policy UCS-A /org/boot-policy* # create storage UCS-A /org/boot-policy/storage* # create local UCS-A /org/boot-policy/storage/local* # create local-lun UCS-A /org/boot-policy/storage/local/local-lun # create local-lun-image-path primary UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # set lunname luna UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # commit-buffer UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path #
ブート ポリシーをサービス プロファイルとテンプレートのうち一方、または両方に含めます。
(注) |
Preprovisioning a LUN name, claiming an orphan LUN, and deploying or undeploying a LUN result in server reboot. |
You can preprovision a LUN name or claim an orphan LUN by using the set ref-name command. Preprovisioning a LUN name or claiming an orphan LUN can be done only when the admin state of the LUN is Undeployed.
This operation will reboot the server.
1. UCS-A# scope org org-name
2. UCS-A /org# scope service-profile service-profile-name
3. UCS-A /org/service-profile# enter local-lun-ref lun-name
4. UCS-A /org/service-profile/local-lun-ref# set ref-name ref-lun-name
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# scope service-profile service-profile-name | Enters the specified service profile mode. |
ステップ 3 | UCS-A /org/service-profile# enter local-lun-ref lun-name | Enters the specified LUN. |
ステップ 4 | UCS-A /org/service-profile/local-lun-ref# set ref-name ref-lun-name | Sets the referenced LUN name. If this LUN name exists and the LUN is orphaned, its is claimed by the service profile. If this LUN does not exist, a new LUN is created with the specified name. |
If the LUN exists and is not orphaned, a configuration failure occurs.
If a LUN is already referred to and the ref-name is changed, it will release the old LUN and will claim or create a LUN with the ref-name. The old LUN is marked as an orphan after the LUN reference is removed from the server.
This examples shows how to preprovision a LUN name.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile* # enter local-lun-ref lun1 UCS-A /org/service-profile/local-lun-ref* # set ref-name lun2
You can deploy or undeploy a LUN by using the admin-state command. If the admin state of a local LUN is Undeployed, the reference of that LUN is removed and the LUN is not deployed.
This operation will reboot the server.
1. UCS-A# scope org org-name
2. UCS-A /org# scope service-profile service-profile-name
3. UCS-A /org/service-profile# enter local-lun-ref lun-name
4. UCS-A /org/service-profile/local-lun-ref# set admin-state {online | undeployed}
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# scope service-profile service-profile-name | Enters the specified service profile mode. |
ステップ 3 | UCS-A /org/service-profile# enter local-lun-ref lun-name | Enters the specified LUN. |
ステップ 4 | UCS-A /org/service-profile/local-lun-ref# set admin-state {online | undeployed} | Sets the admin state of the specified LUN to online or undeployed. If a LUN is already referred to and the admin state is set to undeployed, it will release the old LUN. The old LUN is marked as orphan after the LUN reference is removed from the server. |
This examples shows how to deploy a LUN.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile* # enter local-lun-ref lun1 UCS-A /org/service-profile/local-lun-ref* # set admin-state online
This examples shows how to undeploy a LUN.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile* # enter local-lun-ref lun1 UCS-A /org/service-profile/local-lun-ref* # set admin-state undeployed
1. UCS-A# scope org org-name
2. UCS-A /org# scope service-profile service-profile-name
3. UCS-A /org/service-profile# enter local-lun-ref lun-name
4. UCS-A /org/service-profile/local-lun-ref# set name
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# scope service-profile service-profile-name | Enters the specified service profile mode. |
ステップ 3 | UCS-A /org/service-profile# enter local-lun-ref lun-name | Enters the specified LUN. |
ステップ 4 | UCS-A /org/service-profile/local-lun-ref# set name | Renames the referenced LUN. |
This examples shows how to rename a LUN referenced by a service profile.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile* # enter local-lun-ref lun1 UCS-A /org/service-profile/local-lun-ref* # set name lun11
目次
This part contains the following chapters:
You can create a storage profile both at an org level and at a service-profile level. A service profile can have a dedicated storage profile as well as a storage profile at an org level.
In UCS M-Series Modular Servers, servers in a chassis can use storage that is centralized in that chassis. You can select and configure the disks to be used for storage. A logical collection of these physical disks is called a disk group. Disk groups allow you to organize local disks. The storage controller controls the creation and configuration of disk groups.
A disk group configuration policy defines how a disk group is created and configured. The policy specifies the RAID level to be used for the disk group. It also specifies either a manual or an automatic selection of disks for the disk group, and roles for disks. You can use a disk group policy to manage multiple disk groups. However, a single disk group can be managed only by one disk group policy.
A hot spare is an unused extra disk that can be used by a disk group in the case of failure of a disk in the disk group. Hot spares can be used only in disk groups that support a fault-tolerant RAID level.
A disk group can be partitioned into virtual drives. Each virtual drive appears as an individual physical device to the Operating System.
All virtual drives in a disk group must be managed by using a single disk group policy.
Applying—Creation of the virtual drive is in progress.
Applied—Creation of the virtual drive is complete, or virtual disk policy changes are configured and applied successfully.
Failed to apply—Creation, deletion, or renaming of a virtual drive has failed due to errors in the underlying storage subsystem.
Orphaned—The service profile that contained this virtual drive is deleted.
Not in use—The service profile that contained this virtual drive is in the disassociated state.
Optimal—The virtual drive operating condition is good. All configured drives are online.
Degraded—The virtual drive operating condition is not optimal. One of the configured drives has failed or is offline.
(注) |
This state does not occur if you select the always write back mode. |
Partially degraded—The operating condition in a RAID 6 virtual drive is not optimal. One of the configured drives has failed or is offline. RAID 6 can tolerate up to two drive failures.
Offline—The virtual drive is not available to the RAID controller. This is essentially a failed state.
Unknown—The state of the virtual drive is not known.
The RAID level of a disk group describes how the data is organized on the disk group for the purpose of ensuring availability, redundancy of data, and I/O performance.
Striping—Segmenting data across multiple physical devices. This improves performance by increasing throughput due to simultaneous device access.
Mirroring—Writing the same data to multiple devices to accomplish data redundancy.
Parity—Storing of redundant data on an additional device for the purpose of error correction in the event of device failure. Parity does not provide full redundancy, but it allows for error recovery in some scenarios.
Spanning—Allows multiple drives to function like a larger one. For example, four 20 GB drives can be combined to appear as a single 80 GB drive.
RAID 0 Striped—Data is striped across all disks in the array, providing fast throughput. There is no data redundancy, and all data is lost if any disk fails.
RAID 1 Mirrored—Data is written to two disks, providing complete data redundancy if one disk fails. The maximum array size is equal to the available space on the smaller of the two drives.
RAID 5 Striped Parity—Data is striped across all disks in the array. Part of the capacity of each disk stores parity information that can be used to reconstruct data if a disk fails. RAID 5 provides good data throughput for applications with high read request rates.
RAID 5 distributes parity data blocks among the disks that are part of a RAID-5 group and requires a minimum of three disks.
RAID 6 Striped Dual Parity—Data is striped across all disks in the array and two sets of parity data are used to provide protection against failure of up to two physical disks. In each row of data blocks, two sets of parity data are stored.
Other than addition of a second parity block, RAID 6 is identical to RAID 5 . A minimum of four disks are required for RAID 6.
RAID 10 Mirrored and Striped—RAID 10 uses mirrored pairs of disks to provide complete data redundancy and high throughput rates through block-level striping. RAID 10 is mirroring without parity and block-level striping. A minimum of four disks are required for RAID 10.
When you specify a disk group configuration, and do not specify the local disks in it, Cisco UCS Manager determines the disks to be used based on the criteria specified in the disk group configuration policy. Cisco UCS Manager can make this selection of disks in multiple ways.
When all qualifiers match for a set of disks, then disks are selected sequentially according to their slot number. Regular disks and dedicated hot spares are selected by using the lowest numbered slot.
The following is the disk selection process:
Iterate over all local LUNs that require the creation of a new virtual drive. Iteration is based on the following criteria, in order:
(注) |
If you specify Any as the type of drive, the first available drive is selected. After this drive is selected, subsequent drives will be of a compatible type. For example, if the first drive was SATA, all subsequent drives would be SATA. Cisco UCS Manager Release 2.5 supports only SATA and SAS. Cisco UCS Manager Release 2.5 does not support RAID migration. |
Select dedicated hot spares by using the same method as normal disks. Disks are only selected if they are in an Unconfigured Good state.
If a provisioned LUN has the same disk group policy as a deployed virtual drive, then try to deploy the new virtual drive in the same disk group. Otherwise, try to find new disks for deployment.
Some modifications that are made to the LUN configuration when LUNs are already deployed on an associated server are supported.
The following are the types of modifications that can be performed:
Creation of a new virtual drive.
Deletion of an existing virtual drive, which is in the orphaned state.
The removal of a LUN will cause a warning to be displayed. Ensure that you take action to avoid loss of data.
Some modifications to existing LUNs are not possible without destroying the original virtual drive and creating a new one. All data is lost in these types of modification, and these modifications are not supported.
RAID-level changes that do not support reconstruction. For example, RAID5 to RAID1.
Shrinking the size of a virtual drive.
RAID-level changes that support reconstruction, but where there are other virtual drives present on the same drive group.
Disk removal when there is not enough space left on the disk group to accommodate the virtual drive.
Explicit change in the set of disks used by the virtual drive.
When the following sequence of events takes place:
For non-redundant virtual drives (RAID 0), when a physical drive is removed, the state of the virtual drive is Inoperable. When a new working drive is inserted, the new physical drive goes to an Unconfigured Good state.
For non-redundant virtual drives, there is no way to recover the virtual drive. You must delete the virtual drive and re-create it.
For redundant virtual drives (RAID 1, RAID 5, RAID 6, RAID 10) with no hot spare drives assigned, virtual drive mismatch, virtual drive member missing, and local disk missing faults appear until you insert a working physical drive into the same slot from which the old physical drive was removed.
If the physical drive size is greater than or equal to that of the old drive, the storage controller automatically uses the new drive for the virtual drive. The new drive goes into the Rebuilding state. After rebuild is complete, the virtual drive goes back into the Online state.
For redundant virtual drives (RAID 1, RAID 5, RAID 6, RAID 10) with hot spare drives assigned, when a drive fails, or when you remove a drive, the dedicated hot spare drive, if available, goes into the Rebuilding state with the virtual drive in the Degraded state. After rebuilding is complete, that drive goes to the Online state.
Cisco UCSM raises a disk missing and virtual drive mismatch fault because although the virtual drive is operational, it does not match the physical configuration that Cisco UCSM expects.
if you insert a new disk in the slot with the disk missing, automatic copy back starts from the earlier hot spare disk to the newly inserted disk. After copy back, the hot spare disk is restored. In this state all faults are cleared.
If automatic copy back does not start, and the newly inserted disk remains in the Unconfigured Good, JBOD, or Foreign Configuration state, remove the new disk from the slot, reinsert the earlier hot spare disk into the slot, and import foreign configuration. This initiates the rebuilding process and the drive state becomes Online. Now, insert the new disk in the hot spare slot and mark it as hot spare to match it exactly with the information available in Cisco UCSM.
If a hot spare drive is replaced, the new hot spare drive will go to the Unconfigured Good, Unconfigured Bad, JBOD, or Foreign Configuration state.
Cisco UCSM will raise a virtual drive mismatch or virtual drive member mismatch fault because the hot spare drive is in a state different from the state configured in Cisco UCSM.
You must manually clear the fault. To do this, you must perform the following actions:
If you insert new physical drives into unused slots, neither the storage controller nor Cisco UCSM will make use of the new drive even if the drive is in the Unconfigured Good state and there are virtual drives that are missing good physical drives.
The drive will simply go into the Unconfigured Good state. To make use of the new drive, you will need to modify or create LUNs to reference the newly inserted drive.
When you use UCSM to create a virtual drive, UCSM assigns a unique ID that can be used to reliably identify the virtual drive for further operations. UCSM also provides the flexibility to provide a name to the virtual drive at the time of service profile association. Any virtual drive without a service profile or a server reference is marked as an orphan virtual drive.
In addition to a unique ID, a name is assigned to the drive. Names can be assigned in two ways:
When configuring a virtual drive, you can explicitly assign a name that can be referenced in storage profiles.
If you have not preprovisioned a name for the virtual drive, UCSM generates a unique name for the virtual drive.
You can rename virtual drives that are not referenced by any service profile or server.
A LUN is dereferenced when it is no longer used by any service profile. This can occur as part of the following scenarios:
The LUN is no longer referenced from the storage profile
The storage profile is no longer referenced from the service profile
The server is disassociated from the service profile
The server is decommissioned
When the LUN is no longer referenced, but the server is still associated, re-association occurs.
When the service profile that contained the LUN is disassociated, the LUN state is changed to Not in use.
When the service profile that contained the LUN is deleted, the LUN state is changed to Orphaned.
Cisco UCS Manager does not support a combination of SAS and SATA drives in storage configurations.
Cisco UCS Manager Release 2.5 only supports a stripe size of 64k and more. Having a stripe size of less than 64k will result in failure when a service profile is associated.
In Cisco UCS Manager Release 2.5, the storage controller allows 64 virtual drives per controller, and up to 4 virtual drives per server, of which up to 2 virtual drives are bootable.
(注) |
Only the modular servers in Cisco UCSME-2814 compute cartridges include support for up to 4 virtual drives per server. |
You can choose to configure a disk group policy through automatic or manual disk selection. Configuring a disk group involves the following:
1. UCS-A# scope org org-name
2. UCS-A /org# create disk-group-config-policy disk-group-name
3. UCS-A /org/disk-group-config-policy* # set raid-level raid-level
4. UCS-A /org/disk-group-config-policy* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# create disk-group-config-policy disk-group-name | Creates a disk group configuration policy with the specified name and enters disk group configuration policy mode. |
ステップ 3 | UCS-A /org/disk-group-config-policy* # set raid-level raid-level | |
ステップ 4 | UCS-A /org/disk-group-config-policy* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to set the RAID level for a disk group configuration policy.
UCS-A# scope org UCS-A /org # create disk-group-config-policy raid5policy UCS-A /org/disk-group-config-policy* # set raid-level raid-5-striped-parity UCS-A /org/disk-group-config-policy* # commit-buffer
Automatically or manually configure disks as part of the disk group configuration policy.
You can allow UCSM to automatically select and configure disks in a disk group.
When you create a disk group with RAID 1 policy and configure four disks for it, a RAID1E configuration is created internally by the storage controller.
1. UCS-A# scope org org-name
2. UCS-A /org# enter disk-group-config-policy disk-group-name
3. UCS-A /org/disk-group-config-policy* # enter disk-group-qual
4. UCS-A /org/disk-group-config-policy/disk-group-qual* # set drive-type drive-type
5. UCS-A /org/disk-group-config-policy/disk-group-qual* # set min-drive-size drive-size
6. UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-ded-hot-spares hot-spare-num
7. UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-drives drive-num
8. UCS-A /org/disk-group-config-policy/disk-group-qual* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
||
ステップ 2 | UCS-A /org# enter disk-group-config-policy disk-group-name | Enters disk group configuration policy mode for the specified disk group name. |
||
ステップ 3 | UCS-A /org/disk-group-config-policy* # enter disk-group-qual | Enters disk group qualification mode. In this mode, UCSM automatically configures disks as part of the specified disk group. |
||
ステップ 4 | UCS-A /org/disk-group-config-policy/disk-group-qual* # set drive-type drive-type |
Specifies the drive type for the disk group. You can select:
|
||
ステップ 5 | UCS-A /org/disk-group-config-policy/disk-group-qual* # set min-drive-size drive-size | Specifies the minimum drive size for the disk group. Only disks that match this criteria will be available for selection. The range for minimum drive size is from 0 to10240 GB. You can also set the minimum drive size as Unspecified. If you set the minimum drive size as Unspecified, drives of all sizes will be available for selection. |
||
ステップ 6 | UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-ded-hot-spares hot-spare-num | Specifies the number of dedicated hot spares for the disk group. The range for dedicated hot spares is from 0 to 24 hot spares. You can also set the number of dedicated hot spares as Unspecified. If you set the number of dedicated hot spares as Unspecified, the hot spares will be selected according to the disk selection process. |
||
ステップ 7 | UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-drives drive-num | Specifies the number of drives for the disk group. The range for drives is from 0 to 24 drives. You can also set the number of drives as Unspecified. If you set the number of drives as Unspecified, the number of drives will be selected according to the disk selection process. |
||
ステップ 8 | UCS-A /org/disk-group-config-policy/disk-group-qual* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to automatically configure disks for a disk group configuration policy.
UCS-A# scope org UCS-A /org # enter disk-group-config-policy raid5policy UCS-A /org/disk-group-config-policy* # enter disk-group-qual UCS-A /org/disk-group-config-policy/disk-group-qual* # set drive-type ssd UCS-A /org/disk-group-config-policy/disk-group-qual* # set min-drive-size 1000 UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-ded-hot-spares 2 UCS-A /org/disk-group-config-policy/disk-group-qual* # set num-drives 7 UCS-A /org/disk-group-config-policy/disk-group-qual* # commit-buffer
Configure Virtual Drives.
You can manually configure disks for a disk group.
When you create a disk group with RAID 1 policy and configure four disks for it, a RAID 1E configuration is created internally by the storage controller.
1. UCS-A# scope org org-name
2. UCS-A /org# enter disk-group-config-policy disk-group-name
3. UCS-A /org/disk-group-config-policy* # create local-disk-config-ref slot-num
4. UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set role role
5. UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set span-id span-id
6. UCS-A /org/disk-group-config-policy/local-disk-config-ref *# commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
||
ステップ 2 | UCS-A /org# enter disk-group-config-policy disk-group-name | Enters disk group configuration policy mode for the specified disk group name. |
||
ステップ 3 | UCS-A /org/disk-group-config-policy* # create local-disk-config-ref slot-num | Creates a local disk configuration reference for the specified slot and enters local disk configuration reference mode. |
||
ステップ 4 | UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set role role | |||
ステップ 5 | UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set span-id span-id | Specifies the ID of the span group to which the disk belongs. Disks belonging to a single span group can be treated as a single disk with a larger size. The values range from 0 to 8. You can also set the Span ID as Unspecified when spanning information is not required.
|
||
ステップ 6 | UCS-A /org/disk-group-config-policy/local-disk-config-ref *# commit-buffer | Commits the transaction to the system configuration. |
This example shows how to manually configure disks for a disk group configuration policy.
UCS-A# scope org UCS-A /org # enter disk-group-config-policy raid5policy UCS-A /org/disk-group-config-policy* # create local-disk-config-ref 1 UCS-A /org/disk-group-config-policy/local-disk-config-ref *# set role ded-hot-spare UCS-A /org/disk-group-config-policy/local-disk-config-ref* # set span-id 1 UCS-A /org/disk-group-config-policy/local-disk-config-ref *# commit-buffer
Configure Virtual Drive Properties.
1. UCS-A# scope org org-name
2. UCS-A /org# scope disk-group-config-policy disk-group-name
3. UCS-A /org/disk-group-config-policy* # create virtual-drive-def
4. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set access-policy policy-type
5. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set drive-cache state
6. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set io-policy policy-type
7. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set read-policy policy-type
8. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set strip-size strip-size
9. UCS-A /org/disk-group-config-policy/virtual-drive-def* # set write-cache-policy policy-type
10. UCS-A /org/disk-group-config-policy/virtual-drive-def* # commit-buffer
11. UCS-A /org/disk-group-config-policy/virtual-drive-def* # show
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# scope disk-group-config-policy disk-group-name | Enters disk group configuration policy mode for the specified disk group name. |
ステップ 3 | UCS-A /org/disk-group-config-policy* # create virtual-drive-def | Creates a virtual drive definition and enters the virtual drive definition mode. |
ステップ 4 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set access-policy policy-type | |
ステップ 5 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set drive-cache state |
Specifies the state of the drive cache. This can be one of the following:
重要:
In Cisco UCS Release 2.5, the drive cache state cannot be changed. It will remain as platform-default, irrespective of the drive cache state that you select. |
ステップ 6 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set io-policy policy-type | |
ステップ 7 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set read-policy policy-type | |
ステップ 8 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set strip-size strip-size | Specifies the strip size. This can be one of the following: |
ステップ 9 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # set write-cache-policy policy-type | |
ステップ 10 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # commit-buffer | Commits the transaction to the system configuration. |
ステップ 11 | UCS-A /org/disk-group-config-policy/virtual-drive-def* # show | Displays the configured virtual drive properties. |
This example shows how to configure virtual disk properties:
UCS-A# scope org UCS-A /org # scope disk-group-config-policy raid0policy UCS-A /org/disk-group-config-policy # create virtual-drive-def UCS-A /org/disk-group-config-policy/virtual-drive-def* # set access-policy read-write UCS-A /org/disk-group-config-policy/virtual-drive-def* # set drive-cache enable UCS-A /org/disk-group-config-policy/virtual-drive-def* # set io-policy cached UCS-A /org/disk-group-config-policy/virtual-drive-def* # set read-policy normal UCS-A /org/disk-group-config-policy/virtual-drive-def* # set strip-size 1024 UCS-A /org/disk-group-config-policy/virtual-drive-def* # set write-cache-policy write-through UCS-A /org/disk-group-config-policy/virtual-drive-def* # commit-buffer UCS-A /org/disk-group-config-policy/virtual-drive-def # show Virtual Drive Def: Strip Size (KB): 1024KB Access Policy: Read Write Read Policy: Normal Configured Write Cache Policy: Write Through IO Policy: Cached Drive Cache: Enable UCS-A /org/disk-group-config-policy/virtual-drive-def #
Create a Storage Profile
1. UCS-A# scope org org-name
2. UCS-A /org # create storage-profile storage-profile-name
3. UCS-A /org/storage-profile* # commit-buffer
4. (任意) UCS-A /org* # enter service-profile service-profile-name
5. (任意) UCS-A /org/service-profile* # create storage-profile-def
6. UCS-A /org/service-profile/storage-profile-def* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org # create storage-profile storage-profile-name | Creates a storage profile with the specified name at the org level and enters storage-profile configuration mode. |
ステップ 3 | UCS-A /org/storage-profile* # commit-buffer | Commits the transaction to the system configuration. |
ステップ 4 | UCS-A /org* # enter service-profile service-profile-name | (任意) Enters the specified service profile. |
ステップ 5 | UCS-A /org/service-profile* # create storage-profile-def | (任意) Creates a storage profile at the service-profile level. |
ステップ 6 | UCS-A /org/service-profile/storage-profile-def* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to create a storage profile at the org level.
UCS-A# scope org UCS-A /org # create storage-profile stp2 UCS-A /org/storage-profile* # commit-buffer
This example shows how to create a storage profile at the service-profile level.
UCS-A# scope org UCS-A /org* # enter service-profile sp1 UCS-A /org/service-profile* # create storage-profile-def UCS-A /org/service-profile/storage-profile-def* # commit-buffer
Create Local LUNs
1. UCS-A# scope org org-name
2. UCS-A /org # delete storage-profile storage-profile-name
3. (任意) UCS-A /org # scope service-profile service-profile-name
4. (任意) UCS-A /org/service-profile # delete storage-profile-def
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org # delete storage-profile storage-profile-name | Deletes the storage profile with the specified name at the org level. |
ステップ 3 | UCS-A /org # scope service-profile service-profile-name | (任意) Enters the specified service profile. |
ステップ 4 | UCS-A /org/service-profile # delete storage-profile-def | (任意) Deletes the dedicated storage profile at the service-profile level. |
This example shows how to delete a storage profile at the org level.
UCS-A # scope org UCS-A /org # delete storage-profile stor1
This example shows how to delete a storage profile at the service-profile level.
UCS-A # scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile # delete storage-profile-def
You can create local LUNs within a storage profile at the org level and within a dedicated storage profile at the service-profile level.
1. UCS-A# scope org org-name
2. UCS-A /org # enter storage-profile storage-profile-name
3. UCS-A /org/storage-profile* # create local-lun lun-name
4. UCS-A /org/storage-profile/local-lun* # set auto-deploy {auto-deploy | no-auto-deploy}
5. UCS-A /org/storage-profile/local-lun* # set disk-policy-name disk-policy-name
6. UCS-A /org/storage-profile/local-lun* # set order order-num
7. UCS-A /org/storage-profile/local-lun* # set size size
8. UCS-A /org/storage-profile/local-lun* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
||
ステップ 2 | UCS-A /org # enter storage-profile storage-profile-name | Enters storage-profile mode for the specified storage profile. |
||
ステップ 3 | UCS-A /org/storage-profile* # create local-lun lun-name | Creates a local LUN with the specified name. |
||
ステップ 4 | UCS-A /org/storage-profile/local-lun* # set auto-deploy {auto-deploy | no-auto-deploy} | Specifies whether the LUN should be auto-deployed or not. |
||
ステップ 5 | UCS-A /org/storage-profile/local-lun* # set disk-policy-name disk-policy-name | Specifies the name of the disk policy name for this LUN. |
||
ステップ 6 | UCS-A /org/storage-profile/local-lun* # set order order-num | Specifies the order of this LUN. The order can range from 1 to 64. You can also specify that the order should be lowest-available for the system to automatically assign the lowest available order to the LUN. Multiple LUNs referenced by a storage profile must have unique names and unique orders. |
||
ステップ 7 | UCS-A /org/storage-profile/local-lun* # set size size | Specifies the size of this LUN in GB. The size can range from 1 GB to 10240 GB.
|
||
ステップ 8 | UCS-A /org/storage-profile/local-lun* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to configure a local LUN within a storage profile at the org level.
UCS-A# scope org UCS-A /org # enter storage-profile stp2 UCS-A /org/storage-profile* # create local-lun lun2 UCS-A /org/storage-profile/local-lun* # set disk-policy-name dpn2 UCS-A /org/storage-profile/local-lun* # set order 2 UCS-A /org/storage-profile/local-lun* # set size 1000 UCS-A /org/storage-profile/local-lun* # commit-buffer
This example shows how to configure a local LUN within a dedicated storage profile at the service-profile level.
UCS-A# scope org UCS-A /org* # enter service-profile stp1 UCS-A /org/service-profile* # enter storage-profile-def UCS-A /org/service-profile/storage-profile-def # create local-lun lun1 UCS-A /org/service-profile/storage-profile-def/local-lun* # set disk-policy-name dpn1 UCS-A /org/service-profile/storage-profile-def/local-lun* # set order 1 UCS-A /org/service-profile/storage-profile-def/local-lun* # set size 1000 UCS-A /org/service-profile/storage-profile-def/local-lun* # commit-buffer
Associate a Storage Profile with a Service Profile
You can use the set order command to change the local LUN visibility order to the server. This operation will reboot the server.
1. UCS-A# scope org org-name
2. UCS-A /org # enter storage-profile storage-profile-name
3. UCS-A /org/storage-profile # enter local-lun lun-name
4. UCS-A /org/storage-profile/local-lun* # set disk-policy-name disk-policy-name
5. UCS-A /org/storage-profile/local-lun # set order order-num
6. UCS-A /org/storage-profile/local-lun* # set size size
7. UCS-A /org/storage-profile/local-lun # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org # enter storage-profile storage-profile-name | Enters storage-profile mode for the specified storage profile. |
ステップ 3 | UCS-A /org/storage-profile # enter local-lun lun-name | Enters local-lun mode for the specified local LUN. |
ステップ 4 | UCS-A /org/storage-profile/local-lun* # set disk-policy-name disk-policy-name | Specifies the name of the disk policy name for this LUN. |
ステップ 5 | UCS-A /org/storage-profile/local-lun # set order order-num | Specifies the order of this LUN. The order can range from 1 to 64. You can also specify that the order should be lowest-available for the system to automatically assign the lowest available order to the LUN. |
ステップ 6 | UCS-A /org/storage-profile/local-lun* # set size size | Specifies the size of this LUN in GB. The size can range from 1 GB to 10240 GB. |
ステップ 7 | UCS-A /org/storage-profile/local-lun # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to reorder a local LUN within a storage profile at the org level.
UCS-A# scope org UCS-A /org # enter storage-profile stp1 UCS-A /org/storage-profile* # enter local-lun lun1 UCS-A /org/storage-profile/local-lun* # set disk-policy-name dpn1 UCS-A /org/storage-profile/local-lun* # set order 1 UCS-A /org/storage-profile/local-lun* # set size 10 UCS-A /org/storage-profile/local-lun* # exit UCS-A /org/storage-profile* # enter local-lun lun2 UCS-A /org/storage-profile/local-lun* # set disk-policy-name dpn2 UCS-A /org/storage-profile/local-lun* # set order 2 UCS-A /org/storage-profile/local-lun* # set size 10 UCS-A /org/storage-profile/local-lun* # exit UCS-A /org/storage-profile* # commit-buffer UCS-A /org/storage-profile # show configuration enter storage-profile stp1 enter local-lun lun1 set auto-deploy auto-deploy set disk-policy-name dpn1 set order 1 set size 10 exit enter local-lun lun2 set auto-deploy auto-deploy set disk-policy-name dpn2 set order 2 set size 10 exit set descr "" exit UCS-A /org/storage-profile # enter local-lun lun1 UCS-A /org/storage-profile/local-lun # set order 2 UCS-A /org/storage-profile/local-lun* # exit UCS-A /org/storage-profile* # enter local-lun lun2 UCS-A /org/storage-profile/local-lun* # set order 1 UCS-A /org/storage-profile/local-lun* # exit UCS-A /org/storage-profile* # commit-buffer UCS-A /org/storage-profile # show configuration enter storage-profile stp1 enter local-lun lun1 set auto-deploy auto-deploy set disk-policy-name dpn1 set order 2 set size 10 exit enter local-lun lun2 set auto-deploy auto-deploy set disk-policy-name dpn2 set order 1 set size 10 exit set descr "" exit
When a LUN is deleted, the corresponding virtual drive is marked as orphan after the virtual drive reference is removed from the server.
1. UCS-A# scope org org-name
2. UCS-A /org # enter storage-profile storage-profile-name
3. (任意) UCS-A /org/storage-profile* # show local-lun
4. UCS-A /org/storage-profile* # delete local-lun lun-name
5. UCS-A /org/storage-profile* # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org # enter storage-profile storage-profile-name | Enters storage-profile mode for the specified storage profile. |
ステップ 3 | UCS-A /org/storage-profile* # show local-lun | (任意) Displays the local LUNs in the specified storage profile. |
ステップ 4 | UCS-A /org/storage-profile* # delete local-lun lun-name | Deletes the specified LUN. |
ステップ 5 | UCS-A /org/storage-profile* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to delete a LUN in a storage profile.
UCS-A # scope org UCS-A /org # enter storage-profile stp2 UCS-A /org/storage-profile # show local-lun Local SCSI LUN: LUN Name Size (GB) Order Disk Policy Name Auto Deploy ---------- ----------- ---------------- ---------------- ----------- luna 1 2 raid0 Auto Deploy lunb 1 1 raid0 Auto Deploy UCS-A /org/storage-profile # delete local-lun luna UCS-A /org/storage-profile* # commit-buffer UCS-A /org/storage-profile* # show local-lun Local SCSI LUN: LUN Name Size (GB) Order Disk Policy Name Auto Deploy ---------- ----------- ---------------- ---------------- ----------- lunb 1 1 raid0 Auto Deploy
A storage profile created under org can be referred by multiple service profiles, and a name reference in service profile is needed to associate the storage profile with a service profile.
Storage profiles can be defined under org and under service profile (dedicated). Hence, a service profile inherits local LUNs from both possible storage profiles. A service profile can have a maximum of two such local LUNs.
1. UCS-A# scope org org-name
2. UCS-A /org # scope service-profile service-profile-name
3. UCS-A /org/service-profile # set storage-profile-name storage-profile-name
4. UCS-A /org/service-profile* # commit-buffer
コマンドまたはアクション | 目的 | |||
---|---|---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
||
ステップ 2 | UCS-A /org # scope service-profile service-profile-name | Enters the specified service profile mode. |
||
ステップ 3 | UCS-A /org/service-profile # set storage-profile-name storage-profile-name | Associates the specified storage profile with the service profile.
|
||
ステップ 4 | UCS-A /org/service-profile* # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to associate a storage profile with a service profile.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile # set storage-profile-name stp2
This example shows how to dissociate a service profile from a storage profile.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile # set storage-profile-name ""
Storage profiles can be defined under org and as a dedicated storage profile under service profile. Thus, a service profile inherits local LUNs from both possible storage profiles. It can have a maximum of 2 such local LUNs. You can display the details of all local LUNs inherited by a service profile by using the following command:
1. UCS-A /org/service-profile # show local-lun-ref
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A /org/service-profile # show local-lun-ref |
Displays the following detailed information about all the local LUNs inherited by the specified service profile:
|
UCS-A /org/service-profile # show local-lun-ref Local LUN Ref: Profile LUN Name Admin State RAID Level Provisioned Size (GB) Assigned Size (MB) Config State Referenced Lun Deploy Name ID Drive State ---------------- ----------- ---------------------- ---------------------- -------------------- ------------ -------------- ----------- ----------- ----------- luna Online RAID 0 Striped 1 1024 Applied luna-1 luna-1 1003 Optimal lunb Online RAID 0 Striped 1 1024 Applied lunb-1 lunb-1 1004 Optimal UCS-A /org/service-profile # Local LUN Ref: Name Admin State RAID Level Provisioned Size (GB) Assigned Size (MB) Config State Referenced Lun Deploy Name ID Drive State ---------------- ----------- ---------------------- ---------------------- -------------------- ------------ -------------- ----------- ----------- ----------- lun111 Online RAID 0 Striped 30 30720 Applied lun111-1 lun111-1 1001 Optimal lun201 Online Unspecified 1 0 Not Applied
1. UCS-A# scope server chassis-num / cartridge-id / server-num
2. UCS-A /chassis/cartridge/server # scope adapter adapter-id
3. UCS-A /chassis/cartridge/server/adapter # scope host-scsi host-scsi-id
4. UCS-A /chassis/cartridge/server/adapter/host-scsi # show detail expand
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope server chassis-num / cartridge-id / server-num | Enters cartridge server mode for the specified modular server in the specified chassis and cartridge. |
ステップ 2 | UCS-A /chassis/cartridge/server # scope adapter adapter-id | Enters adapter mode for the specified adapter. |
ステップ 3 | UCS-A /chassis/cartridge/server/adapter # scope host-scsi host-scsi-id | Enters host-scsi mode for the specified host-scsi. |
ステップ 4 | UCS-A /chassis/cartridge/server/adapter/host-scsi # show detail expand | Displays detailed information about the LUNs that are being used by the specified modular server. |
This example shows how to display detailed information about the LUNs that are being used by modular server 1/1/1.
UCS-A # scope server 1/1/1 UCS-A /chassis/cartridge/server # scope adapter 1 UCS-A /chassis/cartridge/server/adapter # scope host-scsi 1 UCS-A /chassis/cartridge/server/adapter/host-scsi # show detail expand Host Scsi Interface: ID: 1 Local Lun Interface: Lun Name: lun-uefi Lun Id: 1008 Lun Order: 1 Oper Lun Id: 7 Boot Dev: Disabled Lun Dn: sys/chassis-1/storage-SAS-1/vd-1008
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata}
3. UCS-A /chassis/raid-controller # set admin-state import-foreign-configuration
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope chassis chassis-num | Enters chassis mode for the specified chassis. |
ステップ 2 | UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata} | Enters RAID controller chassis mode. |
ステップ 3 | UCS-A /chassis/raid-controller # set admin-state import-foreign-configuration | Allows import of configurations from local disks that are in the Foreign Configuration state. |
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata}
3. UCS-A /chassis/raid-controller # scope local-disk local-disk-id
4. UCS-A /chassis/raid-controller/local-disk # set admin-state {clear-foreign-configuration | dedicated-hot-spare [admin-vd-id] | prepare-for-removal | remove-hot-spare | unconfigured-good | undo-prepare-for-removal}
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope chassis chassis-num | Enters chassis mode for the specified chassis. |
ステップ 2 | UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata} | Enters RAID controller chassis mode. |
ステップ 3 | UCS-A /chassis/raid-controller # scope local-disk local-disk-id | Enters local disk configuration mode. |
ステップ 4 | UCS-A /chassis/raid-controller/local-disk # set admin-state {clear-foreign-configuration | dedicated-hot-spare [admin-vd-id] | prepare-for-removal | remove-hot-spare | unconfigured-good | undo-prepare-for-removal} |
Configures the local disk to one of the following states:
|
This example shows how to clear any foreign configuration from a local disk:
UCS-A /chassis/raid-controller/local-disk # set admin-state clear-foreign-configuration
This example shows how to specify a local disk as a dedicated hot spare:
UCS-A /chassis/raid-controller/local-disk* # set admin-state dedicated-hot-spare 1001
This example shows how to specify that a local disk is marked for removal from the chassis:
UCS-A /chassis/raid-controller/local-disk* # set admin-state prepare-for-removal
This example shows how to specify that a local disk is marked for removal as a hot spare:
UCS-A /chassis/raid-controller/local-disk* # set admin-state remove-hot-spare
This example shows how to specify that a local disk is working, but is unconfigured for use:
UCS-A /chassis/raid-controller/local-disk* # set admin-state unconfigured-good
This example shows how to specify that a local disk is no longer marked for removal from the chassis:
UCS-A /chassis/raid-controller/local-disk* # set admin-state undo-prepare-for-removal
The following operations can be performed only on orphaned virtual drives:
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata}
3. (任意) UCS-A /chassis/raid-controller # delete virtual-drive id virtual-drive-id
4. (任意) UCS-A /chassis/raid-controller # delete virtual-drive name virtual-drive-name
5. (任意) UCS-A /chassis/raid-controller # scope virtual-drive virtual-drive-id
6. UCS-A /chassis/raid-controller/virtual-drive # set admin-state delete
7. UCS-A /chassis/raid-controller/virtual-drive # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope chassis chassis-num | Enters chassis mode for the specified chassis. |
ステップ 2 | UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata} | Enters RAID controller chassis mode. |
ステップ 3 | UCS-A /chassis/raid-controller # delete virtual-drive id virtual-drive-id | (任意) Deletes the orphaned virtual drive with the specified virtual drive ID. |
ステップ 4 | UCS-A /chassis/raid-controller # delete virtual-drive name virtual-drive-name | (任意) Deletes the orphaned virtual drive with the specified virtual drive name. |
ステップ 5 | UCS-A /chassis/raid-controller # scope virtual-drive virtual-drive-id | (任意) Enters virtual drive mode for the specified orphaned virtual drive. |
ステップ 6 | UCS-A /chassis/raid-controller/virtual-drive # set admin-state delete | Deletes the orphaned virtual drive. |
ステップ 7 | UCS-A /chassis/raid-controller/virtual-drive # commit-buffer | Commits the transaction to the system configuration. |
This example shows how to delete an orphan virtual drive by specifying the virtual drive ID.
UCS-A# scope chassis 1 UCS-A /chassis # scope raid-controller 1 sas UCS-A /chassis/raid-controller # show virtual-drive Virtual Drive: ID: 1001 Name: lun111-1 Block Size: 512 Blocks: 62914560 Size (MB): 30720 Operability: Operable Presence: Equipped Oper Device ID: 0 Change Qualifier: No Change Config State: Applied Deploy Action: No Action ID: 1002 Name: luna-1 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 1 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1003 Name: lunb-1 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 2 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1004 Name: lunb-2 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 3 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1005 Name: luna-2 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 4 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ... UCS-A /chassis/raid-controller # delete virtual-drive id 1002 Warning: When committed, the virtual drive will be deleted, which may result in data loss. UCS-A /chassis/raid-controller # commit-buffer
This example shows how to delete an orphan virtual drive by specifying the virtual drive name.
UCS-A# scope chassis 1 UCS-A /chassis # scope raid-controller 1 sas UCS-A /chassis/raid-controller # show virtual-drive Virtual Drive: ID: 1001 Name: lun111-1 Block Size: 512 Blocks: 62914560 Size (MB): 30720 Operability: Operable Presence: Equipped Oper Device ID: 0 Change Qualifier: No Change Config State: Applied Deploy Action: No Action ID: 1003 Name: lunb-1 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 2 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1004 Name: lunb-2 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 3 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ID: 1005 Name: luna-2 Block Size: 512 Blocks: 2097152 Size (MB): 1024 Operability: Operable Presence: Equipped Oper Device ID: 4 Change Qualifier: No Change Config State: Orphaned Deploy Action: No Action ... UCS-A /chassis/raid-controller # delete virtual-drive name lunb-1 Warning: When committed, the virtual drive will be deleted, which may result in data loss. UCS-A /chassis/raid-controller # commit-buffer
This example shows how to delete an orphan virtual drive by setting the admin-state.
UCS-A# scope chassis 1 UCS-A /chassis # scope raid-controller 1 sas UCS-A /chassis/raid-controller # scope virtual-drive 1004 UCS-A /chassis/raid-controller/virtual-drive # set admin-state delete Warning: When committed, the virtual drive will be deleted, which may result in data loss. UCS-A /chassis/raid-controller/virtual-drive # commit-buffer
1. UCS-A# scope chassis chassis-num
2. UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata}
3. UCS-A /chassis/raid-controller # scope virtual-drive virtual-drive-id
4. UCS-A /chassis/raid-controller/virtual-drive # set name virtual-drive-name
5. UCS-A /chassis/raid-controller/virtual-drive # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope chassis chassis-num | Enters chassis mode for the specified chassis. |
ステップ 2 | UCS-A /chassis # scope raid-controller raid-contr-id {sas | sata} | Enters RAID controller chassis mode. |
ステップ 3 | UCS-A /chassis/raid-controller # scope virtual-drive virtual-drive-id | Enters virtual drive mode for the specified virtual drive. |
ステップ 4 | UCS-A /chassis/raid-controller/virtual-drive # set name virtual-drive-name | Specifies a name for the orphan virtual drive. |
ステップ 5 | UCS-A /chassis/raid-controller/virtual-drive # commit-buffer | Commits the transaction to the system configuration. |
1. UCS-A# scope org org-name
2. UCS-A /org # scope boot-policy policy-name
3. UCS-A /org/boot-policy # create storage
4. UCS-A /org/boot-policy/storage # create local
5. UCS-A /org/boot-policy/storage/local/ # create local-lun
6. UCS-A /org/boot-policy/storage/local/local-lun # create local-lun-image-path {primary | secondary}
7. UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # set lunname lun_name
8. UCS-A /org/boot-policy/storage/local/local-storage-device # commit-buffer
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters organization mode for the specified organization. To enter the root organization mode, type / as the org-name . |
ステップ 2 | UCS-A /org # scope boot-policy policy-name | Enters organization boot policy mode for the specified boot policy. |
ステップ 3 | UCS-A /org/boot-policy # create storage | Creates a storage boot for the boot policy and enters organization boot policy storage mode. |
ステップ 4 | UCS-A /org/boot-policy/storage # create local | Creates a local storage location and enters the boot policy local storage mode. |
ステップ 5 | UCS-A /org/boot-policy/storage/local/ # create local-lun | Specifies a local hard disk drive as the local storage. |
ステップ 6 | UCS-A /org/boot-policy/storage/local/local-lun # create local-lun-image-path {primary | secondary} | Specifies the boot order for the LUN that you specify. |
ステップ 7 | UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # set lunname lun_name | Specifies the name of the LUN that you want to boot from. |
ステップ 8 | UCS-A /org/boot-policy/storage/local/local-storage-device # commit-buffer | Commits the transaction to the system configuration. |
The following example shows how to create a boot policy named lab1-boot-policy, create a local hard disk drive boot for the policy, specify a boot order and a LUN to boot from, and commit the transaction:
UCS-A# scope org / UCS-A /org* # scope boot-policy lab1-boot-policy UCS-A /org/boot-policy* # create storage UCS-A /org/boot-policy/storage* # create local UCS-A /org/boot-policy/storage/local* # create local-lun UCS-A /org/boot-policy/storage/local/local-lun # create local-lun-image-path primary UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # set lunname luna UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path # commit-buffer UCS-A /org/boot-policy/storage/local/local-lun/local-lun-image-path #
ブート ポリシーをサービス プロファイルとテンプレートのうち一方、または両方に含めます。
(注) |
Preprovisioning a LUN name, claiming an orphan LUN, and deploying or undeploying a LUN result in server reboot. |
You can preprovision a LUN name or claim an orphan LUN by using the set ref-name command. Preprovisioning a LUN name or claiming an orphan LUN can be done only when the admin state of the LUN is Undeployed.
This operation will reboot the server.
1. UCS-A# scope org org-name
2. UCS-A /org# scope service-profile service-profile-name
3. UCS-A /org/service-profile# enter local-lun-ref lun-name
4. UCS-A /org/service-profile/local-lun-ref# set ref-name ref-lun-name
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# scope service-profile service-profile-name | Enters the specified service profile mode. |
ステップ 3 | UCS-A /org/service-profile# enter local-lun-ref lun-name | Enters the specified LUN. |
ステップ 4 | UCS-A /org/service-profile/local-lun-ref# set ref-name ref-lun-name | Sets the referenced LUN name. If this LUN name exists and the LUN is orphaned, its is claimed by the service profile. If this LUN does not exist, a new LUN is created with the specified name. |
You can deploy or undeploy a LUN by using the admin-state command. If the admin state of a local LUN is Undeployed, the reference of that LUN is removed and the LUN is not deployed.
This operation will reboot the server.
1. UCS-A# scope org org-name
2. UCS-A /org# scope service-profile service-profile-name
3. UCS-A /org/service-profile# enter local-lun-ref lun-name
4. UCS-A /org/service-profile/local-lun-ref# set admin-state {online | undeployed}
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# scope service-profile service-profile-name | Enters the specified service profile mode. |
ステップ 3 | UCS-A /org/service-profile# enter local-lun-ref lun-name | Enters the specified LUN. |
ステップ 4 | UCS-A /org/service-profile/local-lun-ref# set admin-state {online | undeployed} | Sets the admin state of the specified LUN to online or undeployed. If a LUN is already referred to and the admin state is set to undeployed, it will release the old LUN. The old LUN is marked as orphan after the LUN reference is removed from the server. |
This examples shows how to deploy a LUN.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile* # enter local-lun-ref lun1 UCS-A /org/service-profile/local-lun-ref* # set admin-state online
This examples shows how to undeploy a LUN.
UCS-A# scope org UCS-A /org # scope service-profile sp1 UCS-A /org/service-profile* # enter local-lun-ref lun1 UCS-A /org/service-profile/local-lun-ref* # set admin-state undeployed
1. UCS-A# scope org org-name
2. UCS-A /org# scope service-profile service-profile-name
3. UCS-A /org/service-profile# enter local-lun-ref lun-name
4. UCS-A /org/service-profile/local-lun-ref# set name
コマンドまたはアクション | 目的 | |
---|---|---|
ステップ 1 | UCS-A# scope org org-name | Enters the organization mode for the specified organization. To enter the root organization mode, enter / as the org-name. |
ステップ 2 | UCS-A /org# scope service-profile service-profile-name | Enters the specified service profile mode. |
ステップ 3 | UCS-A /org/service-profile# enter local-lun-ref lun-name | Enters the specified LUN. |
ステップ 4 | UCS-A /org/service-profile/local-lun-ref# set name | Renames the referenced LUN. |