No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The server cannot find drive because of LUN ID collision when VTL maps SAN client

Publication Date:  2012-10-10 Views:  118 Downloads:  0

Issue Description

When delivering VTL6000, add several clients for SAN clients, configure initiator address and distribute several drive.
Scan disk via cfgmgr on AIX, run lsdev –Cc tape and find there are some servers can find drive successfully, repeat running cagmgr, there still are several servers without drive.

Alarm Information


Handling Process

Enter VTL, Console, SAN Clients->XXX, check the drive LUN ID of the client, choose the drives which cannot be found, right-click->Properties, enter Channel Device Properties page, type LUN ID which does not exist on application server after LUN:, I suggest use large number.
Then run afgmgr to rescan on application server, run lscfg –Cc tape and it could find all the drives.

Root Cause

Because there is drive map of other VTL configured on the VTL, run lsattr -El rmt* to check the related LUN ID, and some LUN IDs are occupied, you need to modify them on VLT to solve LUN ID collision.


If some server cannot find all the drives, you should consider LUN ID.