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>

Reminder

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

upgrade

AIX Operating System Unable to Identify the VTL Robot Arm

Publication Date:  2015-07-31 Views:  41 Downloads:  0
Issue Description
Product and version information:

VTL3500 V100R002
VTL6000 V100R003
VTL6900 V100R005

An IBM 3584 VTL is created and its storage capacity is allocated to multiple SAN clients. The SAN clients run Windows and AIX operating systems. Windows-based host backup clients can detect the tape drivers and robot arms, and have access to the VTL storage space, as shown in Figure 1.

Figure 1 Allocating VTL storage capacity to multiple SAN clients




The AIX-based backup server can identify the robot arm of a field physical tape library whose model is TS3200. The AIX-based backup server fails to detect the robot arm of the VTL, although it detects the VTL driver. Figure 2 shows the detected physical tape libraries and drivers. The red areas indicate system-attached physical tape libraries and the blue area indicates drivers.

Figure 2 Identifying the physical tape libraries and drivers




After the physical tape library is removed and all devices are deleted, the AIX-based backup server fails to detect the robot arm of the VTL after device scanning, although it detects the VTL driver.
Handling Process
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.
Root Cause
Cause 1: The robot arm's LUN ID conflicts with an exiting device ID on the AIX operating system.

Cause 2: The robot arm's driver has not been installed on the AIX operating system.

END