![](/images/new-backgrounds/1143853/143853187x1.webp)
Creating a Transparent Volume
Transparent volumes cannot be used in further volume hierarchies.
Tape devices must be virtualized as transparent volumes.
You can take a physical disk and its existing configured storage data and convert it to a directly accessible, or transparent, virtual volume using the CLI command volume create transparent. A transparent volume is ready for direct host exposure. Please refer to “Volume Exposure & Security,” page 107.
Certain vendor storage devices have
This is useful if you have a functioning and fully configured RAID module that you want to use ’as is’. All RAID configurations will be maintained in the transparent volume.
volume create transparent
You need to define two parameters to create a transparent volume:
SWITCH | PARAMETER | DEFINITION | STATUS | EXAMPLE |
|
|
|
|
|
| VOLUME ALIAS | OPTIONAL | Trans1 | |
|
| ALIAS FOR THE | DEFAULT: |
|
|
| VOLUME | STORAGE ALIAS |
|
DISK ALIAS | ALIAS GIVEN TO | MANDATORY | Disk1 | |
|
| THE DISK DURING |
|
|
|
| DISK AUTO- |
|
|
|
| DISCOVERY |
|
|
|
|
|
|
|
If you are working in
a
Example:
In Figure 36, page 89, the logical unit, LUN0 on Disk 1, is converted directly to a virtual transparent volume, Transparent 1. This RAID device has only one LUN. For each LUN configured on a RAID device, the V- Switch registers a disk. Therefore, a RAID device with five LUNs will appear to the
volume create transparent –vol Trans1 –d Disk1
88 | SANRAD |