Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ SAN Client and Fibre Transport Guide
  3. Appendix B. HP-UX Specific Configuration Details
  4. About configuring legacy device files
  5. Creating legacy SCSI and FCP robotic controls on HP-UX
  6. Example of how to create a sctl device file for FCP (PA-RISC)
NetBackup™ SAN Client and Fibre Transport Guide

Example of how to create a sctl device file for FCP (PA-RISC)

The following example shows how create a sctl device file for an HP VLS9000 robot. NetBackup uses the device file for robotic control.

To create an FCP robotic device file for HP-UX PA-RISC

  1. Invoke the ioscan -f command. The following output example is edited for readability:
    ioscan -f
    Class   I  H/W Path                 Driver  S/W State  H/W Type   Description
    =============================================================================
    fc      0  0/2/0/0                  td      CLAIMED    INTERFACE  HP Tachyon XL2 Fibre 
                                                                      Channel Mass Storage 
                                                                      Adapter
    fcp     4  0/2/0/0.10               fcp     CLAIMED    INTERFACE  FCP Domain
    ext_bus 6  0/2/0/0.10.11.255.0      fcpdev  CLAIMED    INTERFACE  FCP Device Interface
    target  5  0/2/0/0.10.11.255.0.0    tgt     CLAIMED    DEVICE
    autoch  2  0/2/0/0.10.11.255.0.0.0  schgr   CLAIMED    DEVICE     HP      VLS
    tape    5  0/2/0/0.10.11.255.0.0.1  stape   CLAIMED    DEVICE     HP      Ultrium 4-SCSI
    tape    6  0/2/0/0.10.11.255.0.0.2  stape   CLAIMED    DEVICE     HP      Ultrium 4-SCSI
    tape    7  0/2/0/0.10.11.255.0.0.3  stape   CLAIMED    DEVICE     HP      Ultrium 4-SCSI
    
  2. Examine the output for the card instance number and the SCSI ID and LUN of the robotic device. In this example, the interface card instance number (the I column) is 6. If you use the card's H/W Path value as a mask (0/2/0/0.10.11.255.0), you see the following:

    • An HP VLS9000 robot is at SCSI ID 0, LUN 0.

    • Three Ultrium 4-SCSI drives are at SCSI ID 0 and LUN 1, LUN 2, and LUN 3.

  3. Determine the character major number of the sctl driver by using the lsdev command, as follows:
    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.

  4. The commands to create the device file for the HP VLS9000 robotic control are as follows. The card instance number is 6, the target is 0, and the LUN is 0.
    cd /dev/sctl
    /usr/sbin/mknod c6t0l0 c 203 0x060000

    If you add the robot to NetBackup manually, specify the following pathname for robotic control:

    /dev/sctl/c6t0l0

Feedback

Was this page helpful?
Previous

Example of how to create a sctl device file for SCSI (PA-RISC)

Next

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

Feedback

Was this page helpful?