Default Parameters for UnityLUNCapTest

Thin provisioning, also known as virtual provisioning or thin storage, is an on-demand storage allocation based on user requirements in storage area networks (SAN), centralized storage disks, and storage virtualization systems.

In thin storage, as the user consumes their allocated storage space, they are allocated more. Alternatively, when they free up space, by deleting files or transferring data, the idle space is reclaimed, repurposed and used for other workloads in need of storage.

In comparison to thin provisioning, thick provisioning (also called fat provisioning) pre-allocates storage space in anticipation of future capacity requirements. While both thin and thick provisioning are methods of storage allocation, the difference lies in how the Logical Unit Number (LUN) is configured. A storage administrator should always be up to date with the LUN configuration in their environment as well as the capacity of the LUNs. To aid administrators in figuring out the capacity of thousands of LUNs in a much shorter duration, eG Enterprise offers the UnityLUNCapTest test.

Using this test, administrators can figure out if the LUN is thin provisioned or not. Also, this test throws light on total capacity and the allocated capacity of each LUN. This way, administrators can figure out the LUN that is allocated with more storage resources. This test also helps administrators figure out the total capacity of each LUN in the storage pool.

This page depicts the default parameters that need to be configured for the UnityLUNCapTest test.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• The eG agent uses the command-line utility, UEMCli.exe, which is part of the UniSphere Management Suite, to communicate with and monitor the storage device. To enable the eG agent to invoke the CLI, configure the full path to the CLI in the UNISPHERE CLI PATH text box.

• Provide the credentials of a user possessing ‘monitor’ role to access the storage system in the USERNAME and PASSWORD text boxes.

• Confirm the Password by retyping it in the CONFIRM PASSWORD text box.

• Specify the duration (in seconds) beyond which this test should time out in the TIMEOUT text box. The default is 300 seconds.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.