Cause 1: The robot arm's LUN ID conflicts with an exiting device ID on the AIX operating system.
1. On the VTL Console, unfold AIX Clients. Right-click the mapped tape and choose Properties.
![]()
2. On the dialog box that is displayed, the LUN ID (0 by default) of the mapped VTL is displayed and driver IDs are displayed as 1, 2, 3, and so on.
For example, if one VTL and six drivers are mapped, the LUN ID is 0 and the driver IDs are 1, 2, 3, 4, 5, and 6.
![]()
3. Change the LUN ID to a value that is different from all mapped drivers' IDs. For example, change the ID to 7.
4. After changing the ID, run cfgmgr –v on the AIX operating system to rescan for the robot arm.
5. After the scanning is complete, run lsdev –Cc tape to display the detected VTL robot arm.
Cause 2: The robot arm's driver has not been installed on the AIX operating system.
1. Visit the VTL vendor's official website to download and install the corresponding driver.
2. After the driver is installed, run cfgmgr –v on the AIX operating system to rescan for the robot arm.
3. After the scanning is complete, run lsdev –Cc tape to display the detected VTL robot arm.
4. If the problem persists, contact R&D engineers.
----End