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 SCSI (PA-RISC)
NetBackup™ SAN Client and Fibre Transport Guide

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

In this example, the following robots exist:

  • An ADIC Scalar 100 library is on a SCSI bus with an instance number of 7, SCSI ID 2, and LUN 0.

  • The robotic control for an IBM ULT3583-TL library is on the same SCSI bus at SCSI ID 3 and LUN 0.

To create SCSI robotic device files for HP-UX PA-RISC

  1. Invoke the ioscan -f command, as follows:
    ioscan -f
    Class     I  H/W Path     Driver  S/W State H/W Type  Description
    =================================================================
    ext_bus   7  0/7/0/1      c720    CLAIMED   INTERFACE SCSI C896 Fast Wide LVD
    target   10  0/7/0/1.0    tgt     CLAIMED   DEVICE
    tape     65  0/7/0/1.0.0  stape   CLAIMED   DEVICE    QUANTUM SuperDLT1
    target   11  0/7/0/1.1    tgt     CLAIMED   DEVICE
    tape     66  0/7/0/1.1.0  stape   CLAIMED   DEVICE    QUANTUM SuperDLT1
    target   12  0/7/0/1.2    tgt     CLAIMED   DEVICE
    autoch   14  0/7/0/1.2.0  schgr   CLAIMED   DEVICE    ADIC Scalar 100
    target   13  0/7/0/1.3    tgt     CLAIMED   DEVICE
    autoch   19  0/7/0/1.3.0  schgr   CLAIMED   DEVICE    IBM ULT3583-TL
    target   14  0/7/0/1.4    tgt     CLAIMED   DEVICE
    tape     21  0/7/0/1.4.0  atdd    CLAIMED   DEVICE    IBM ULT3580-TD1
    target   15  0/7/0/1.5    tgt     CLAIMED   DEVICE
    tape     19  0/7/0/1.5.0  atdd    CLAIMED   DEVICE    IBM ULT3580-TD1
  2. Examine the output for the card instance number and the SCSI ID and LUN of the robotic device, as follows:

    The card H/W Path is 0/7/0/1; the card instance number (I column) is 7. Apply the H/W Path value as a mask. The ADIC robotic device (schgr) is at SCSI ID 2, LUN 0 on this bus. The IBM robotic device (schgr) is at SCSI ID 3, LUN 0 on this bus.

  3. 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.

  4. The commands to create the device files follow. For the ADIC robot, the card instance number is 7, the target is 2, and the LUN is 0. For the IBM robot, the card instance number is 7, the SCSI ID is 3, and the LUN is 0.
    cd /dev/sctl
    /usr/sbin/mknod c7t2l0 c 203 0x072000
    /usr/sbin/mknod c7t3l0 c 203 0x073000

    If you add the robots to NetBackup manually, you specify the following for ADIC robotic control and IBM robotic control respectively:

    /dev/sctl/c7t2l0
    /dev/sctl/c7t3l0

Feedback

Was this page helpful?
Previous

Creating legacy SCSI and FCP robotic controls on HP-UX

Next

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

Feedback

Was this page helpful?