1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

drive WWN and TSM database table

Discussion in 'Tape / Media Library' started by denisl, May 20, 2007.

  1. denisl

    denisl ADSM.ORG Member

    Joined:
    Sep 12, 2002
    Messages:
    116
    Likes Received:
    0
    Does anyone know where the tape drive WWN is stored in a table I can run a sql against?

    Q DRIVE F=D shows WWN.. but not recorded in drives or paths table.. Thanks.
     
  2.  
  3. chad_small

    chad_small ADSM.ORG Moderator

    Joined:
    Dec 17, 2002
    Messages:
    2,240
    Likes Received:
    49
    Occupation:
    AIX/SAN/TSM
    Location:
    Gilbert, AZ
    From what I had been told it was because TSM was getting it from the OS. Wether that is true or its in one of the undocumented and closed tables it up for debate. It does show with the SHOW LIBRARY command also, but I'd just strip it from the Q DRIVE F=D.
     
  4. ttrinh7975

    ttrinh7975 ADSM.ORG Senior Member

    Joined:
    Apr 21, 2004
    Messages:
    485
    Likes Received:
    13
    Occupation:
    System Programmer II/ Storage Admin
    Location:
    West Coast...Beautiful California
    Drive WWN and Info

    At the command line...type in

    q drive f=d

    This will show you the drive path and drive info

    Library Name: LTO1
    Drive Name: DRIVE29
    Device Type: LTO
    On-Line: Yes
    Read Formats: ULTRIUMC,ULTRIUM
    Write Formats: ULTRIUMC,ULTRIUM
    Element: 277
    Drive State: LOADED
    Volume Name: T02178
    Allocated to:
    WWN: 50050763000DA319
    Serial Number: 6891604122
    Last Update by (administrator): DNDXD5
    Last Update Date/Time: 05/19/2007 09:22:31
    Cleaning Frequency (Gigabytes/ASNEEDED/NONE): ASNEEDED

    _____________________________

    From the OS...here's an example on AIX...

    Issue the following command to determine the /dev/rmt definitions, and save a copy of the results:

    Lscfg

    Or obtain the drives WWN’s from System Admin.


    This should result in a display that resembles the following:

    smc0 U0.1-P1-I5/Q1-W50050763004DA301-L0 IBM 3584 Library Medium Changer (FCP)
    rmt0 U0.1-P1-I5/Q1-W50050763004DA308-L0 IBM 3580 Ultrium Tape Drive (FCP)
    rmt1 U0.1-P1-I5/Q1-W50050763004DA309-L0 IBM 3580 Ultrium Tape Drive (FCP)
    rmt2 U0.1-P1-I5/Q1-W50050763004DA30B-L0 IBM 3580 Ultrium Tape Drive (FCP)
    rmt3 U0.1-P1-I2/Q1-W50050763004DA30A-L0 IBM 3580 Ultrium Tape Drive (FCP)

    Compare the above WWN’s with the library specialist and use TSM Integrated Solution Console to delete and define library, drives and paths accordingly.
     
    Last edited: May 21, 2007
  5. denisl

    denisl ADSM.ORG Member

    Joined:
    Sep 12, 2002
    Messages:
    116
    Likes Received:
    0
    I'm on RHEL4 and don't have lscfg.. That's where my problem is..

    Better yet, is there a way to guarentee device mapping in udev when the system reboots?
     
  6. baldomero83

    baldomero83 ADSM.ORG Member

    Joined:
    Feb 7, 2007
    Messages:
    84
    Likes Received:
    0
    You should be able to come up with the tape device names on RHEL4 using a similar AIX OS commands as lscfg and extract the WWN and match it with TSM q drive f=d or the show command

    with ensuring drive mapping on reboot. this is a combination of the OS and hardware device. Drive mapping is a funtion of the pathing in TSM.
    As long as there are no changes on the h/w , communication path -cabling (drive serial numbe/wwn - e.g replacement) & tape library & OS (device drive defitions changes) machine reboot should not cause issues with TSM drive/library paths, unless of course it could not communicate with the communication path due to above changes on h/w & os. If using san switch zoning this might also be another 'problem area' to check

    I think to make things easier - don't think about TSM 1st - make sure your OS definitions (wwn & serial numbers) of you drives, communication (HBA/FC) from the RHEL server to the drives are correct, in tact.
    , then you can start ensuring TSM is getting the right info from the OS.

    hope this helps...
     
  7. chad_small

    chad_small ADSM.ORG Moderator

    Joined:
    Dec 17, 2002
    Messages:
    2,240
    Likes Received:
    49
    Occupation:
    AIX/SAN/TSM
    Location:
    Gilbert, AZ
    UPDATE: A query of the DRIVES table in 8.1 now shows the WWN as a column.


    tsm: CLTTSM30>run tabcol drives

    COLNAME
    ---------------------------------
    ACS_DRIVE_ID
    ALLOCATED_TO
    CLEAN_FREQ
    DEVICE_TYPE
    DRIVE_NAME
    DRIVE_SERIAL
    DRIVE_STATE
    ELEMENT
    LAST_UPDATE
    LAST_UPDATE_BY
    LIBRARY_NAME
    ONLINE
    READ_FORMATS
    VOLUME_NAME
    WRITE_FORMATS

    WWN
     
    Last edited: Aug 31, 2017

Share This Page