Search <book_title>...

Veritas NetBackup™ SAN Client and Fibre Transport Guide

Last Published: 2020-09-14

Product(s): NetBackup (8.3.0.1)

Example of how to create sctl device files for FCP (Itanium)

With Fibre Channel, the hardware paths are longer than with SCSI.

In this example, the following devices are attached to the host.

An HP EML E-Series robot with four HP drives (two LTO2 and two LTO3 drives). A separate path exists for each drive pair. The robotic control is through card instance 12 (0/4/1/1.2.12.255.0).
An HP VLS 6000 robot with six drives. The robot is partitioned into two virtual libraries, three Quantum SDLT320 drives in one library and three HP LTO3 drives in the other library. Separate robotic control exists for each library.

To create FCP robotic device files for HP-UX Itanium

Invoke the ioscan -f command. The following is a command output excerpt that shows the Fibre Channel devices on a host:

ext_bus   4  0/4/1/1.2.10.255.0      fcd_vbus  CLAIMED  INTERFACE FCP Device Interface
target    7  0/4/1/1.2.10.255.0.0    tgt       CLAIMED  DEVICE
tape     18  0/4/1/1.2.10.255.0.0.0  stape     CLAIMED  DEVICE    HP Ultrium 3-SCSI
tape     20  0/4/1/1.2.10.255.0.0.1  stape     CLAIMED  DEVICE    HP Ultrium 3-SCSI
ext_bus  13  0/4/1/1.2.11.255.0      fcd_vbus  CLAIMED  INTERFACE FCP Device Interface
target    8  0/4/1/1.2.11.255.0.0    tgt       CLAIMED  DEVICE
autoch    4  0/4/1/1.2.11.255.0.0.0  schgr     CLAIMED  DEVICE    HP VLS
tape     22  0/4/1/1.2.11.255.0.0.1  stape     CLAIMED  DEVICE    QUANTUM SDLT320
tape     23  0/4/1/1.2.11.255.0.0.2  stape     CLAIMED  DEVICE    QUANTUM SDLT320
tape     24  0/4/1/1.2.11.255.0.0.3  stape     CLAIMED  DEVICE    QUANTUM SDLT320
autoch    5  0/4/1/1.2.11.255.0.0.4  schgr     CLAIMED  DEVICE    HP VLS
tape     25  0/4/1/1.2.11.255.0.0.5  stape     CLAIMED  DEVICE    HP Ultrium 3-SCSI
tape     26  0/4/1/1.2.11.255.0.0.6  stape     CLAIMED  DEVICE    HP Ultrium 3-SCSI
tape     27  0/4/1/1.2.11.255.0.0.7  stape     CLAIMED  DEVICE    HP Ultrium 3-SCSI
ext_bus  12  0/4/1/1.2.12.255.0      fcd_vbus  CLAIMED  INTERFACE FCP Device Interface
target    6  0/4/1/1.2.12.255.0.0    tgt       CLAIMED  DEVICE
autoch    1  0/4/1/1.2.12.255.0.0.0  schgr     CLAIMED  DEVICE    HP EML E-Series
tape     19  0/4/1/1.2.12.255.0.0.1  stape     CLAIMED  DEVICE    HP Ultrium 2-SCSI
tape     21  0/4/1/1.2.12.255.0.0.2  stape     CLAIMED  DEVICE    HP Ultrium 2-SCSI

Examine the output for the card instance number and the SCSI ID and LUN of the robotic device.
In this example, the following devices are attached to this host:
- The robotic control for the HP EML E-Series robot is through card instance 12 (0/4/1/1.2.12.255.0). Two of the drives are accessed through the same path, and the other two are accessed through card instance 4 (0/4/1/1.2.10.255.0).
- The robotic controls for the HP VLS 6000 robot partitions are through card instance 13. Robotic control for one partition is at SCSI ID 0 and LUN 0. Robotic control for the other partition is at SCSI ID 0 and LUN 4.
Determine the character major number of the sctl driver by using the following command:
```
lsdev -d sctl
Character     Block       Driver          Class  
  203          -1         sctl            ctl
```
The output from this command shows that the character major number for the sctl driver is 203.
The commands to create the devices file for the robotic controls are as follows:
```
cd /dev/sctl
/usr/sbin/mknod c12t0l0 c 203 0x0c0000
/usr/sbin/mknod c13t0l0 c 203 0x0d0000
/usr/sbin/mknod c13t0l4 c 203 0x0d0400
```
If you add the robots to NetBackup manually, you specify the following pathnames for robotic control. The first device file is for the HP EML E-Series robot. The second and third device files are for the VLS 6000 robot (two robotic devices).
```
/dev/sctl/c12t0l0
/dev/sctl/c13t0l0
/dev/sctl/c13t0l4
```