Results 1 to 3 of 3
  1. #1
    Member
    Join Date
    Sep 2004
    Location
    Warsaw, Poland
    Posts
    39
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Default Control and Data Path Failover on TSM 6.3/RHEL 6.3 and TS3310 - ANR8840E and ANR8962E

    Hi,

    I'm implementing TSM 6.3 on RHEL 6.3 on TS3310.
    I ran into some problems since RHEL 6.3 does not seem to be 100% supported by lin_tape(d) - 1.73 and 1.74 mentiones only 6.2 but i managed to get it working.
    I have DPF and CPF. I set up lin_tape to work with alt pathing for both IBMchangerX and IBMtapeXX.

    To make SANDISCOVERY work I had to install HBAAPI - IBM has it for Qlogic HBAs only for RHEL5 but I found this API in HP's site

    During fabric failure testing, the system survived this, but during recovery I had kernel panic. It was on generic RH 6.3 kernel and 1.73 lin_tape. Upgrade to latest kernel and 1.74 lin_tape helped.
    lin_taped seems to claim drives properly and I get only some kernel oops in /var/log/messages.

    But after such operation TSM does not see the changer (and drives suposingly too)
    q san sees the hardware. But during the startup (yes I tried windows-style refreshing reboot ) I get those messages allover my actlog:

    ANR8962E Unable to find path to match the serial number defined for library C2-TPL01.
    ANR8962E Unable to find path to match the serial number defined for library C2-TPL01.
    ANR8962E Unable to find path to match the serial number defined for library C2-TPL01.
    ANR8840E Unable to open device /dev/IBMchanger0 with error number 2 and PVRRC 2839.
    ANR8441E Initialization failed for SCSI library C2-TPL01.

    Any ideas how to assure DPF/CPF working?
    Or refresh paths from Q SAN discovered information? It is supposed to happen automatically.

    I've found a little discrepancy between Q SAN and my configuration (that worked before san failure test):

    Here is the join between TSM, system device and serial number:
    ANS8000I Server command: 'select DESTINATION_NAME, DEVICE, DRIVE_SERIAL from paths, drives where DESTINATION_NAME=DRIVE_NAME'
    DRV01 /dev/IBMtape0 1068066927
    DRV02 /dev/IBMtape1 1068066681
    DRV03 /dev/IBMtape2 1068068824
    DRV04 /dev/IBMtape3 1068068828
    DRV05 /dev/IBMtape4 1068067790
    DRV06 /dev/IBMtape5 1068065374
    DRV07 /dev/IBMtape16 1068068829
    DRV08 /dev/IBMtape6 1068063256
    DRV09 /dev/IBMtape7 1068067802
    DRV10 /dev/IBMtape10 1068068774

    And here is Q SAN output

    tsm: C2-TSM01>q san

    Device Vendor Product Serial Number Device
    Type
    -------- -------- ---------------- ---------------------- --------------------
    DRIVE IBM ULT3580-TD5 1068066927 /dev/sg3;/dev/st0;
    DRIVE IBM ULT3580-TD5 1068066681 /dev/sg13;/dev/st4;
    DRIVE IBM ULT3580-TD5 1068068774 /dev/sg18;/dev/st7;
    DRIVE IBM ULT3580-TD5 1068068824 /dev/sg27;/dev/st8;
    DRIVE IBM ULT3580-TD5 1068068828 /dev/sg78;/dev/st17;
    DRIVE IBM ULT3580-TD5 1068066927 /dev/sg9;/dev/st2;
    DRIVE IBM ULT3580-TD5 1068066681 /dev/sg17;/dev/st6;
    DRIVE IBM ULT3580-TD5 1068068774 /dev/sg28;/dev/st9;
    DRIVE IBM ULT3580-TD5 1068068824 /dev/sg29;/dev/st10;
    DRIVE IBM ULT3580-TD5 1068068828 /dev/sg79;/dev/st18;
    DRIVE IBM ULT3580-TD5 1068067802 /dev/sg4;/dev/st1;
    DRIVE IBM ULT3580-TD5 1068068829 /dev/sg11;/dev/st3;
    DRIVE IBM ULT3580-TD5 1068067790 /dev/sg16;/dev/st5;
    LIBRARY IBM 3576-MTL 000001322088_LLA /dev/sg22;/dev/chan-
    ger-sg22;
    DRIVE IBM ULT3580-TD5 1068065374 /dev/sg72;/dev/st13;
    DRIVE IBM ULT3580-TD5 1068063256 /dev/sg80;/dev/st19;
    DRIVE IBM ULT3580-TD5 1068067802 /dev/sg56;/dev/st11;
    DRIVE IBM ULT3580-TD5 1068068829 /dev/sg57;/dev/st12;
    DRIVE IBM ULT3580-TD5 1068067790 /dev/sg74;/dev/st14;
    LIBRARY IBM 3576-MTL 000001322088_LLA /dev/sg75;/dev/chan-
    ger-sg75;/dev/chan-
    ger;
    DRIVE IBM ULT3580-TD5 1068065374 /dev/sg76;/dev/st15;
    DRIVE IBM ULT3580-TD5 1068063256 /dev/sg77;/dev/st16;

  2. #2
    Member
    Join Date
    Sep 2004
    Location
    Warsaw, Poland
    Posts
    39
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Default

    It looks that for some reasons lin_tape was nod loaded during the startup, it caused lin_taped fail to start. When I modprobed lin_tape and stsrted lin_tape my Q SAN looks like this:

    Device Vendor Product Serial Number Device
    Type
    -------- -------- ---------------- ---------------------- --------------------
    DRIVE IBM ULT3580-TD5 1068066927 /dev/IBMtape0
    DRIVE IBM ULT3580-TD5 1068066681 /dev/IBMtape4
    DRIVE IBM ULT3580-TD5 1068068774 /dev/IBMtape7
    DRIVE IBM ULT3580-TD5 1068068824 /dev/IBMtape8
    DRIVE IBM ULT3580-TD5 1068068828 /dev/IBMtape17
    DRIVE IBM ULT3580-TD5 1068066927 /dev/IBMtape0
    DRIVE IBM ULT3580-TD5 1068066681 /dev/IBMtape4
    DRIVE IBM ULT3580-TD5 1068068774 /dev/IBMtape7
    DRIVE IBM ULT3580-TD5 1068068824 /dev/IBMtape8
    DRIVE IBM ULT3580-TD5 1068068828 /dev/IBMtape17
    DRIVE IBM ULT3580-TD5 1068067802 /dev/IBMtape1
    DRIVE IBM ULT3580-TD5 1068068829 /dev/IBMtape3
    DRIVE IBM ULT3580-TD5 1068067790 /dev/IBMtape5
    LIBRARY IBM 3576-MTL 000001322088_LLA /dev/IBMchanger0
    DRIVE IBM ULT3580-TD5 1068065374 /dev/IBMtape13
    DRIVE IBM ULT3580-TD5 1068063256 /dev/IBMtape16
    DRIVE IBM ULT3580-TD5 1068067802 /dev/IBMtape1
    DRIVE IBM ULT3580-TD5 1068068829 /dev/IBMtape3
    DRIVE IBM ULT3580-TD5 1068067790 /dev/IBMtape5
    LIBRARY IBM 3576-MTL 000001322088_LLA /dev/IBMchanger0
    DRIVE IBM ULT3580-TD5 1068065374 /dev/IBMtape13
    DRIVE IBM ULT3580-TD5 1068063256 /dev/IBMtape16

    I've noticed device name change

    And actlog has those messages:
    ANR8975I Found new path for C2-TSM01 and target name DRV02 old path
    /dev/IBMtape1 new path /dev/IBMtape4. Path information is updated.
    ANR8975I Found new path for C2-TSM01 and target name DRV03 old path
    /dev/IBMtape2 new path /dev/IBMtape8. Path information is updated.
    ANR8975I Found new path for C2-TSM01 and target name DRV04 old path
    /dev/IBMtape3 new path /dev/IBMtape17. Path information is updated.
    ANR8975I Found new path for C2-TSM01 and target name DRV05 old path
    /dev/IBMtape4 new path /dev/IBMtape5. Path information is updated.
    ANR8975I Found new path for C2-TSM01 and target name DRV06 old path
    /dev/IBMtape5 new path /dev/IBMtape13. Path information is updated.
    ANR8975I Found new path for C2-TSM01 and target name DRV07 old path
    /dev/IBMtape16 new path /dev/IBMtape3. Path information is updated.
    ANR8975I Found new path for C2-TSM01 and target name DRV08 old path
    /dev/IBMtape6 new path /dev/IBMtape16. Path information is updated.
    ANR8975I Found new path for C2-TSM01 and target name DRV09 old path
    /dev/IBMtape7 new path /dev/IBMtape1. Path information is updated.
    ANR8975I Found new path for C2-TSM01 and target name DRV10 old path
    /dev/IBMtape10 new path /dev/IBMtape7. Path information is updated.
    ANR8439I SCSI library C2-TPL01 is ready for operations.

    Now I have to figure out why lin_tape stuff does not get loaded on startup.

    Sorry for posting such a simple problem

  3. #3
    Newcomer
    Join Date
    Oct 2009
    Posts
    11
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hi, make sure that lin_tape is configured to start in your runlevels.
    chkconfig lin_tape on

Similar Threads

  1. How to implement Control Path Failover in TS3310 Tape library
    By anandgmenon in forum Tape / Media Library
    Replies: 5
    Last Post: 03-21-2012, 12:05 PM
  2. TS3500 - Control Path Failover
    By GregE in forum Tape / Media Library
    Replies: 1
    Last Post: 04-22-2010, 03:07 PM
  3. Control Path Failover on EMC VTL
    By Sunhillow in forum VTL - Virtual Tape Library
    Replies: 0
    Last Post: 01-29-2008, 09:08 AM
  4. Control Path failover
    By rchoudarapu in forum Tape / Media Library
    Replies: 0
    Last Post: 10-29-2007, 08:44 AM
  5. 3584 failover of a library control path
    By vreinen in forum Tape / Media Library
    Replies: 0
    Last Post: 05-16-2003, 06:11 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •