Unmap lun path and optionally delete ldev service template

Document created by Hidenori Akatoki Employee on Aug 22, 2016Last modified by Takeshi Arisaka on Aug 23, 2016
Version 5Show Document
  • View in full screen mode


Pass a single ldkc:cu:ldev number to unmap and optionally delete the device.

Has received a small amount of testing in the lab so please use at your own risk.


Use this pair of templates in combination to delete logical devices:

Service TemplateDescription
HDS_raidcomDeletePathSupply a logical device number to delete all associated lun paths. Opting to delete the ldev altogether causes the service to call the HAD API to schedule the delete service for a specified number of minutes into the future; it is useful to have a safety net before removing the ldev. HCS refresh completes the service.
HDS_raidcomDeleteLdevSupply a logical device that you wish to delete. HCS refresh completes the service.



These templates are good starting points if you wish to call the HAD API from within an HAD service.



Service TemplateVersionFile (With Link)DescriptionVendor IDHAD versionCreated date
HDS_raidcomDeletePath01.00.19DownloadDelete lun paths from ldev number + optionally start ldev deletion service via HAD APIHDSV8.2.1-00Mar 27, 2016
HDS_raidcomDeleteLdev01.00.07DownloadSupply a logical device that you wish to delete.HDSV8.2.1-00Mar 27, 2016



How to use


These service templates both use raidcom, a horcm service for your chosen array is required to be running on the HAD server.


Configure both Services



Configure HDS_raidcomDeleteLdev service first since you will need the service ID in order to configure HDS_raidcomDeletePath if you wish to exercise the option of deleting the ldev.


1/ Give the service a meaningful name. Here the service name contains the serial number of the storage array that we are going to fix this service to work upon.


2/ Complete the HDvM fields as required.


3/ Complete the raidcom fields as required.


4/ This field will be completed by the user of the service, leave it blank.



HDS_raidcomDeletePath can optionally call the delete service at a specified number of minutes after the lun unmapping occurs.


1/ Give the service a meaningful name, this example is tied to serial number 53511 so we reflect this in the service name.


2/ Enter HDvM settings, often the defaults are suitable.


3/ Enter raidcom command device security details.


4/ Obtain the ldev delete service ID, you might need to update column settings in order to see this information.


5/ Service user options, lock these as you see fit. During service exec opting to delete the ldev will cause this service to schedule the delete service via HAD REST API offset by the specified number of minutes.


Running the service(s)


HDS_raidcomDeletePath: Main flow

Delete lun paths, skipped here because no paths exist:

Delete Ldev flow:


HDS_raidcomDeleteLdev automatically started by HDS_raidcomDeletePath: