This discussion is archived
6 Replies Latest reply: Nov 26, 2012 12:56 PM by rdoogan RSS

persistent tape binding OEL 5.8 +  OSB 10.4.0.1.0

946181 Newbie
Currently Being Moderated
HI,

I'm having trouble getting persistent tape binding to work in OEL with a SL3000 library. I've consulted Doc 971386.1 and must be having some syntax issues in /etc/udev/rules.d/50-udev.rules.

I understand the 'nst' entries are not needed.

Can someone send a sample showing how the strings below for a STK library and a tape drive should look?

Do I need to edit anything inbetween {} ?

Do I need all four lines for the changer and three lines per tape drive?

# type 8 devices are "Medium Changers"
KERNEL=="sg*", IMPORT{parent}=="ID_*"
KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="8", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -g -u -x -s %p -d $tempnode"
KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="8", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -g -u -x -a -s %p -d $tempnode"
KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="8", ENV{ID_SERIAL}=="?*", SYMLINK+="tape/by-id/$env{ID_BUS}-$env{ID_SERIAL}"

# type 1 devices are "Tape Drives"
KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="1", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -g -u -x -s %p -d $tempnode"
KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="1", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -g -u -x -a -s %p -d $tempnode"
KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="1", ENV{ID_SERIAL}=="?*", SYMLINK+="tape/by-id/$env{ID_BUS}-$env{ID_SERIAL}"

Thanks!
Jason
  • 1. Re: persistent tape binding OEL 5.8 +  OSB 10.4.0.1.0
    948089 Newbie
    Currently Being Moderated
    Jason,
    My rules file looks as follows. This is showing the serial numbers instead of the scsi-ID to the master server via the media server. (I hope this is making sense) My lib is SL8500, which is similar to yours. Server is on RHEL5.6
    I am working on solving this for my environment and thus in research stages of my project of making persistent binding happen when the hba vendor doesn't the utility to do it (as does qlogic with sansurfer). Anyway, here is what i have - that is working for me.

    $ cat /etc/udev/rules.d/26-my-tapedrive-persistence.rules

    KERNEL=="st*[0-9]|nst[0-9]*", SUBSYSTEM=="scsi_tape", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -u -g -x -a -s %p -d $tempnode"
    KERNEL=="nst*[0-9]", SUBSYSTEM=="scsi_tape", ENV{ID_SERIAL}=="3500104f000bf8ee0", SYMLINK+="fc-$ENV{ID_SERIAL}-st%n"
    KERNEL=="nst*[0-9]", SUBSYSTEM=="scsi_tape", ENV{ID_SERIAL}=="3500104f000bf8ed4", SYMLINK+="fc-$ENV{ID_SERIAL}-st%n"

    ACSSS]> cmd_proc_shell "display drive * -f serial_num wwn" |grep "1 0 1 "
    1 0 1 6 1068056471 50.01.04.f0.00.bb.8e.e0
    1 0 1 7 1068056466 50.01.04.f0.00.bb.8e.d4
    ...
    ---
    I also edited /etc/scsi_id.config, to white list things
    options=-g 0x83
    ----
    the ID_SERIAL was revealed by the command: scsi_id -p 0x83 -u -g -x -s /class/scsi_tape/nst0
    ---- ---- ---- ---- ---- ---- ---- ---- ----
    I hope this helps.
    ---------------------------------

    by the way, a friend got the following ID_SERIAL on his server, thus his rules file is slightly different:

    1.find ID_SERIAL
    # scsi_id -u -g -s /class/scsi_tape/nst0
    3600110e0026268000302000000000002

    # scsi_id -p 0x83 -u -g -x -s /class/scsi_tape/nst0
    ID_VENDOR=HP
    ID_MODEL=Ultrium_2-SCSI
    ID_REVISION=F44W
    ID_SERIAL=3600110e0026268000302000000000002
    ID_TYPE=tape
    ID_BUS=scsi

    3. cat /etc/udev/rules.d/20-pers-drive-names.rules
    KERNEL=="st*[0-9]|nst[0-9]*", SUBSYSTEM=="scsi_tape", ENV{ID_SERIAL}=="", \
    IMPORT{program}="scsi_id -u -g -x -a -s %p -d $tempnode"

    KERNEL=="nst*[0-9]", SUBSYSTEM=="scsi_tape", \
    ENV{ID_SERIAL}=="3600110e0026268000302000000000002", SYMLINK+="fc-$ENV{ID_SERIAL}-st%n"
  • 2. Re: persistent tape binding OEL 5.8 +  OSB 10.4.0.1.0
    rdoogan Journeyer
    Currently Being Moderated
    With OEL5.8 the /etc/udev/rules.d/50-udev.rules file will provide everything you need right out of the bag. Of course it will create nst entries as well, which we don't need, so to be tidy we can just remove those lines, so we see only sg entries in /dev/tape/by-id.

    So my section of this file looks like :

    SUBSYSTEM!="scsi_tape", GOTO="persistent_storage_tape_end"
    # by-path (parent device path)
    #KERNEL=="st*[0-9]|nst*[0-9]", IMPORT{program}="path_id %p"
    #KERNEL=="st*[0-9]", ENV{ID_PATH}=="?*", SYMLINK+="tape/by-path/$env{ID_PATH}"
    #KERNEL=="nst*[0-9]", ENV{ID_PATH}=="?*", SYMLINK+="tape/by-path/$env{ID_PATH}"
    LABEL="persistent_storage_tape_end"

    # type 8 devices are "Medium Changers"
    KERNEL=="sg*", IMPORT{parent}=="ID_*"
    KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="8", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -g -u -x -s %p -d $tempnode"
    KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="8", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -g -u -x -a -s %p -d $tempnode"
    KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="8", ENV{ID_SERIAL}=="?*", SYMLINK+="tape/by-id/$env{ID_BUS}-$env{ID_SERIAL}-changer"

    # type 1 devices are "Scsi Tape"
    KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="1", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -g -u -x -s %p -d $tempnode"
    KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="1", ENV{ID_SERIAL}=="", IMPORT{program}="scsi_id -g -u -x -a -s %p -d $tempnode"
    KERNEL=="sg*", SUBSYSTEM=="scsi_generic", SYSFS{type}=="1", ENV{ID_SERIAL}=="?*", SYMLINK+="tape/by-id/$env{ID_BUS}-$env{ID_SERIAL}-sg"

    And this provides links such as :

    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03d87-changer -> ../../sg10
    lrwxrwxrwx 1 root root 9 Jul 12 22:14 scsi-3500104f000b03d97-sg -> ../../sg2
    lrwxrwxrwx 1 root root 9 Jul 12 22:14 scsi-3500104f000b03d9a-sg -> ../../sg3
    lrwxrwxrwx 1 root root 9 Jul 12 22:14 scsi-3500104f000b03d9d-sg -> ../../sg4
    lrwxrwxrwx 1 root root 9 Jul 12 22:14 scsi-3500104f000b03da0-sg -> ../../sg5
    lrwxrwxrwx 1 root root 9 Jul 12 22:14 scsi-3500104f000b03da3-sg -> ../../sg6
    lrwxrwxrwx 1 root root 9 Jul 12 22:14 scsi-3500104f000b03da6-sg -> ../../sg7
    lrwxrwxrwx 1 root root 9 Jul 12 22:14 scsi-3500104f000b03da9-sg -> ../../sg8
    lrwxrwxrwx 1 root root 9 Jul 12 22:14 scsi-3500104f000b03dac-sg -> ../../sg9
    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03daf-sg -> ../../sg62
    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03db2-sg -> ../../sg63
    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03db5-sg -> ../../sg64
    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03db8-sg -> ../../sg65
    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03dbb-sg -> ../../sg66
    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03dbe-sg -> ../../sg67
    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03dc1-sg -> ../../sg68
    lrwxrwxrwx 1 root root 10 Jul 12 22:14 scsi-3500104f000b03dc4-sg -> ../../sg69


    These are from an FC attached SL3000 library. So the udev rules show you the WWN on the fibre port, which you can easily link up to the correct drive using the SLC.

    In the case of physical media I wouldn't advise linking your devices to the actual serial number on the drive, as then you have to reconfigure that when you swap the drive out due to a hardware fault. Virtual Tape Libraries will show you the serial number in udev and that is fine as a virtual drive will never fail.

    Thanks

    Rich
  • 3. Re: persistent tape binding OEL 5.8 +  OSB 10.4.0.1.0
    975760 Newbie
    Currently Being Moderated
    Hi Rich,

    I also have a problem of tape library changer and tape device paths change after rebooting the server of disconnect FC cables of server side or tape library side. Please see below information.

    Before system reboot
    [root@hgcbk01 ~]# ls -l /dev/tape/by-id
    total 0
    lrwxrwxrwx 1 root root 9 Nov 21 11:40 scsi-3500104f000cc193e-changer -> ../../sg8
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 scsi-3500104f000cc1948-nst -> ../../nst0
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc1948-sg -> ../../sg2
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc1948-st -> ../../st0
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 scsi-3500104f000cc194b-nst -> ../../nst1
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc194b-sg -> ../../sg3
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc194b-st -> ../../st1
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 scsi-3500104f000cc194e-nst -> ../../nst2
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc194e-sg -> ../../sg4
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc194e-st -> ../../st2
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 scsi-3500104f000cc1951-nst -> ../../nst3
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc1951-sg -> ../../sg5
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc1951-st -> ../../st3
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 scsi-3500104f000cc1954-nst -> ../../nst4
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc1954-sg -> ../../sg6
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc1954-st -> ../../st4
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 scsi-3500104f000cc1957-nst -> ../../nst5
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc1957-sg -> ../../sg7
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 scsi-3500104f000cc1957-st -> ../../st5
    [root@hgcbk01 ~]# ls -l /dev/tape/by-path
    total 0
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 pci-0000:30:00.0-fc-0x500104f000cc1949:0x0000000000000000-nst -> ../../nst0
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 pci-0000:30:00.0-fc-0x500104f000cc1949:0x0000000000000000-st -> ../../st0
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 pci-0000:30:00.0-fc-0x500104f000cc194c:0x0000000000000000-nst -> ../../nst1
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 pci-0000:30:00.0-fc-0x500104f000cc194c:0x0000000000000000-st -> ../../st1
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 pci-0000:30:00.0-fc-0x500104f000cc194f:0x0000000000000000-nst -> ../../nst2
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 pci-0000:30:00.0-fc-0x500104f000cc194f:0x0000000000000000-st -> ../../st2
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 pci-0000:30:00.1-fc-0x500104f000cc1952:0x0000000000000000-nst -> ../../nst3
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 pci-0000:30:00.1-fc-0x500104f000cc1952:0x0000000000000000-st -> ../../st3
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 pci-0000:30:00.1-fc-0x500104f000cc1955:0x0000000000000000-nst -> ../../nst4
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 pci-0000:30:00.1-fc-0x500104f000cc1955:0x0000000000000000-st -> ../../st4
    lrwxrwxrwx 1 root root 10 Nov 21 11:38 pci-0000:30:00.1-fc-0x500104f000cc1958:0x0000000000000000-nst -> ../../nst5
    lrwxrwxrwx 1 root root 9 Nov 21 11:38 pci-0000:30:00.1-fc-0x500104f000cc1958:0x0000000000000000-st -> ../../st5
    [root@hgcbk01 ~]# sg_map -i -x
    /dev/sg0 0 2 0 0 0 /dev/sda LSI MR9261-8i 2.12
    /dev/sg1 7 0 0 0 5 /dev/scd0 TEAC DV-W28SS-V 1.0B
    /dev/sg2 1 0 1 0 1 /dev/nst0 HP Ultrium 5-SCSI I5BS
    /dev/sg3 1 0 2 0 1 /dev/nst1 HP Ultrium 5-SCSI I5BS
    /dev/sg4 1 0 3 0 1 /dev/nst2 HP Ultrium 5-SCSI I5BS
    /dev/sg5 2 0 0 0 1 /dev/nst3 HP Ultrium 5-SCSI I5BS
    /dev/sg6 2 0 1 0 1 /dev/nst4 HP Ultrium 5-SCSI I5BS
    /dev/sg7 2 0 2 0 1 /dev/nst5 HP Ultrium 5-SCSI I5BS
    /dev/sg8 1 0 0 0 8 STK SL500 1468
    /dev/sg9 9 0 0 0 0 /dev/sdb ORACLE SSM PMAP
    [root@hgcbk01 ~]#

    After system reboot
    [root@hgcbk01 ~]# ls -l /dev/tape/by-id
    total 0
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc193e-changer -> ../../sg3
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 scsi-3500104f000cc1948-nst -> ../../nst1
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc1948-sg -> ../../sg4
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc1948-st -> ../../st1
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 scsi-3500104f000cc194b-nst -> ../../nst2
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc194b-sg -> ../../sg5
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc194b-st -> ../../st2
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 scsi-3500104f000cc194e-nst -> ../../nst3
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc194e-sg -> ../../sg6
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc194e-st -> ../../st3
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 scsi-3500104f000cc1951-nst -> ../../nst0
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc1951-sg -> ../../sg2
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc1951-st -> ../../st0
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 scsi-3500104f000cc1954-nst -> ../../nst4
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc1954-sg -> ../../sg7
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc1954-st -> ../../st4
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 scsi-3500104f000cc1957-nst -> ../../nst5
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc1957-sg -> ../../sg8
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 scsi-3500104f000cc1957-st -> ../../st5
    [root@hgcbk01 ~]# ls -l /dev/tape/by-path
    total 0
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 pci-0000:30:00.0-fc-0x500104f000cc1949:0x0000000000000000-nst -> ../../nst1
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 pci-0000:30:00.0-fc-0x500104f000cc1949:0x0000000000000000-st -> ../../st1
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 pci-0000:30:00.0-fc-0x500104f000cc194c:0x0000000000000000-nst -> ../../nst2
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 pci-0000:30:00.0-fc-0x500104f000cc194c:0x0000000000000000-st -> ../../st2
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 pci-0000:30:00.0-fc-0x500104f000cc194f:0x0000000000000000-nst -> ../../nst3
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 pci-0000:30:00.0-fc-0x500104f000cc194f:0x0000000000000000-st -> ../../st3
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 pci-0000:30:00.1-fc-0x500104f000cc1952:0x0000000000000000-nst -> ../../nst0
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 pci-0000:30:00.1-fc-0x500104f000cc1952:0x0000000000000000-st -> ../../st0
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 pci-0000:30:00.1-fc-0x500104f000cc1955:0x0000000000000000-nst -> ../../nst4
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 pci-0000:30:00.1-fc-0x500104f000cc1955:0x0000000000000000-st -> ../../st4
    lrwxrwxrwx 1 root root 10 Nov 21 12:10 pci-0000:30:00.1-fc-0x500104f000cc1958:0x0000000000000000-nst -> ../../nst5
    lrwxrwxrwx 1 root root 9 Nov 21 12:10 pci-0000:30:00.1-fc-0x500104f000cc1958:0x0000000000000000-st -> ../../st5
    [root@hgcbk01 ~]# sg_map -i -x
    /dev/sg0 0 2 0 0 0 /dev/sda LSI MR9261-8i 2.12
    /dev/sg1 7 0 0 0 5 /dev/scd0 TEAC DV-W28SS-V 1.0B
    /dev/sg2 2 0 0 0 1 /dev/nst0 HP Ultrium 5-SCSI I5BS
    /dev/sg3 1 0 0 0 8 STK SL500 1468
    /dev/sg4 1 0 1 0 1 /dev/nst1 HP Ultrium 5-SCSI I5BS
    /dev/sg5 1 0 2 0 1 /dev/nst2 HP Ultrium 5-SCSI I5BS
    /dev/sg6 1 0 3 0 1 /dev/nst3 HP Ultrium 5-SCSI I5BS
    /dev/sg7 2 0 1 0 1 /dev/nst4 HP Ultrium 5-SCSI I5BS
    /dev/sg8 2 0 2 0 1 /dev/nst5 HP Ultrium 5-SCSI I5BS
    /dev/sg9 9 0 0 0 0 /dev/sdb ORACLE SSM PMAP
    [root@hgcbk01 ~]#

    Server Model: Sun Server X3-2L
    Operating System: Oracle Enterprise Linux 5 Update 8 64 Bit
    Tape Library: Sun StorageTek SL500
    Tape Drive: 6x HP LTO-5 8Gb FC
    SAN Switch: Brocade 300 with 24x 8Gb SFP
    SAN Switch Zoning: One-to-One device zone (each zone has 1 storage device and 1 server device)
    Backup Software: Oracle Secure Backup 10.0.4.0

    I can found a document ID 971386.1 of Internal Support Portal. The document mentioned how to create persistent bindings for device. But unfortunately, I don't know how to edit and change the parameters of the file /etc/udev/rules.d/50-udev.rules for activate the persistent bindings for device.

    Could you teach me how can I perform the persistent bindings for device? or give me the /etc/udev/rules.d/50-udev.rules sample how to change the parameters in the file? If persistent bindings works, can we perform the persistent bindings for device with customized order? Please see below for sample.

    [root@hgcbk01 ~]# sg_map -i -x
    /dev/sg0 0 2 0 0 0 /dev/sda LSI MR9261-8i 2.12
    /dev/sg1 7 0 0 0 5 /dev/scd0 TEAC DV-W28SS-V 1.0B
    /dev/sg2 1 0 1 0 1 /dev/nst0 HP Ultrium 5-SCSI I5BS <-- SL500 0,1,1,9 (Drive 1)
    /dev/sg3 1 0 2 0 1 /dev/nst1 HP Ultrium 5-SCSI I5BS <-- SL500 0,1,2,9 (Drive 2)
    /dev/sg4 1 0 3 0 1 /dev/nst2 HP Ultrium 5-SCSI I5BS <-- SL500 0,2,1,9 (Drive 3)
    /dev/sg5 2 0 0 0 1 /dev/nst3 HP Ultrium 5-SCSI I5BS <-- SL500 0,2,2,9 (Drive 4)
    /dev/sg6 2 0 1 0 1 /dev/nst4 HP Ultrium 5-SCSI I5BS <-- SL500 0,2,3,9 (Drive 5)
    /dev/sg7 2 0 2 0 1 /dev/nst5 HP Ultrium 5-SCSI I5BS <-- SL500 0,2,4,9 (Drive 6)
    /dev/sg8 1 0 0 0 8 STK SL500 1468 <-- SL500 controller fc1 (fc 1)
    /dev/sg9 ? ? ? ? 8 STK SL500 1468 <-- SL500 controller fc1 (fc 2) <-- coming new FC port
    /dev/sg10 9 0 0 0 0 /dev/sdb ORACLE SSM PMAP

    Thanks.

    Regards,
    Chi
  • 4. Re: persistent tape binding OEL 5.8 +  OSB 10.4.0.1.0
    rdoogan Journeyer
    Currently Being Moderated
    Like I said above, if you're running OEL5.8 the udev rules will do everything for you already (they didn't in previous releases). So there is no need to edit the rules file, unless you're like me and want to keep it clean and tidy and only map the sg entries.

    From your list I can see that you have the persistent maps already, so basically you're all sorted.

    Instead of specifying a /dev/sg entry in your device configuration, use the /dev/tape/by-id entry. For example, for your robot you would do this (I'm assuming that your library is known to OSB as "SL500")

    obtool chdev -a hgcbk01:/dev/tape/by-id/scsi-3500104f000cc193e-changer SL500

    Thanks

    Rich
  • 5. Re: persistent tape binding OEL 5.8 +  OSB 10.4.0.1.0
    975760 Newbie
    Currently Being Moderated
    Hi Rich,

    Thanks for your reply and teach.

    I have another question. The device name will be changed after power cycle the tape library. Is this normal behavior of the Linux OS? In the Solaris OS, the device path will be remained even the tape library was inoperable, FC cable was disconnected and system rebooted.

    Regards,
    Chi
  • 6. Re: persistent tape binding OEL 5.8 +  OSB 10.4.0.1.0
    rdoogan Journeyer
    Currently Being Moderated
    For device name, I assume you mean the /dev/sg entry. Yes those are allowed to change based on how the kernel detects the devices. The same will happen to the sgen devices on Solaris too, but there you don't have udev to control it, so that is a bigger problem.

    Thanks

    Rich

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points