Viewing LUN Information

Prerequisites

At least one LUN has been created on the storage system.

Procedure

1. Log in to DeviceManager.
2. Choose Provisioning > LUN.
3. View information about the LUNs in the list.

   GUIs may vary with product versions and models. The actual GUIs prevail.

   Table 7-9 LUN parameters

   Parameter	Description	Setting
   Name	Name of a LUN.	[Example] LUN001
   ID	ID of a LUN.	[Example] 1
   Health Status	Health status of a LUN.	[Example] Normal
   Running Status	Running status of a LUN.	[Example] Online
   Type	Type of a LUN. The types include: Thick LUN Thin LUN	[Example] Thick LUN
   Use Type	Use type of a LUN. The use types include: Internal: common LUN created in a local storage device. External: eDevLUN created for taking over a remote LUN. PE LUN: a LUN created for a VVol LUN in VMware software defined storage only. PE LUNs function as I/O demultiplexers to simplify the connection between VMs and VVol LUNs. VM I/Os are sent to the corresponding VVol LUN through a PE LUN. VVol LUN: provides storage space for VMware VMs.	[Example] Internal
   Description	Description of a LUN.	[Example] -
   Capacity	Capacity of a LUN, which is specified by a user during LUN creation.	[Example] 1.000 GB
   Sectors	Number of the sectors in a LUN.	[Example] 2097152
   Allocated Capacity	Capacity allocated to a LUN. The capacity includes the data capacity and metadata capacity, but does not include the data protection capacity. The metadata capacity is about 1% of the data capacity and data protection capacity.	[Example] 1.187 GB
   Owning Storage Pool	Storage pool to which a LUN belongs.	[Example] StoragePool001
   Mapping	Mapping status of a LUN, indicating whether a LUN is mapped to a host or not.	[Example] Unmapped
   Data Protection	Data protection method of a LUN.	[Example] Clone
   WWN	WWN of a LUN.	[Example] 60022a1100037eca45ae3b6100000019
   Remote WWN	WWN of a remote LUN.	[Example] —
   Takeover LUN WWN	WWN of the eDevLUN after takeover.	[Example] —
   SmartTier Policy	Data migration policies, including: Automatic relocation This policy automatically relocates data blocks based on their activity levels. Automatic relocation relies on the analysis result from I/O monitoring. Thus I/O monitoring must be enabled and the service monitoring period must be set before automatic relocation. Relocation to high-performance tier This policy is recommended for the applications (such as OLTP databases) sensitive to the response time, IOPS, and bandwidth. This policy preferentially promotes data blocks to the high-performance tier and the performance tier. If the capacity of the data blocks to be relocated is larger than the capacity of the high-performance tier (or performance tier), only data blocks with the most activities are promoted to the high performance tier (or the performance tier). Relocation to low-performance tier This policy is recommended for applications (such as file sharing) insensitive to performance. This policy preferentially demotes data blocks to the performance tier and the capacity tier, regardless of the activity levels of these data blocks. No relocation This policy does not relocate data blocks among storage tiers, and data can be relocated only when the data relocation policy is changed. NOTE: This parameter is not supported by some product versions or models. The actual GUIs prevail.	[Example] Automatic relocation
   Masquerading Status	Masquerading status can be: No Masquerading Basic Masquerading Applies to eDevLUNs, used for replacing the basic LUN information such as the VID, PID, and LUN WWN. Extended Masquerading Applies to eDevLUNs, used for replacing the basic LUN information and extended LUN information such as the SCSI protocol version, owning controller, and working controller. Inherited Masquerading Applies to local LUNs, used for inheriting the remote LUN information such as the VID, PID, and SCSI protocol version. Third-party Applies to eDevLUNs, used for taking over heterogeneous storage systems from third-party vendors online.	[Example] No Masquerading
   vStore Name	Name of the vStore to which the LUN belongs.	[Example] vStore001
   vStore ID	ID of the vStore to which the LUN belongs.	[Example] 1