Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
18 replies Latest Post - ‏2014-07-23T14:02:39Z by V0WR_Bill_Cooper
Pierre_LG
Pierre_LG
19 Posts
ACCEPTED ANSWER

Pinned topic ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

‏2010-04-30T13:56:51Z |
Hello all,
I have a very big issue with my new tape drives: ULTRIUM-TD4.
Well, first of all the os/400 V6R1 is seing my tape drives as 63A0 Tape Drive...

My backups and restore are working fine... but I've tried to migrate old tapes to this new tapes and I have an error.
The OS/400 says that my LTO4 is only supporting 32Kb of Block Size what is not true and my source tape has larger Block Size !!!
(My old backups were on 3590 Tape Drive and were run with Use Optimum Block Size set to *YES).

Could you help ?

Thanks,
Updated on 2012-01-25T16:37:27Z at 2012-01-25T16:37:27Z by Pierre_LG
  • QSECOFR
    QSECOFR
    55 Posts
    ACCEPTED ANSWER

    Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

    ‏2010-04-30T15:07:13Z  in response to Pierre_LG
    1) When you replaced your old tape drive with your new LTO4 drive, did you power cycle the IOA, IPL the IOP, or IPL the system?

    Do you have the required PTFS:
    2) Which release of the OS?
    3) What type of IOA?

    Do you have the latest firmware:
    4) What is the firmware on the LTO4 drive

    5) Try varying off the device description, delete the device description, power cycle the IOA, and if QAUTOCFG isnn't turned on to automatically recreate the device description, then perform a CRTDEVTAP DEVD(TAPxx) RSRCNAME(TAPxx)

    6) If using a media management program such as BRMS or Robot/save, then make sure that the device is not limited to a density or block size.

    7) If optimum blocking on the save command is set to *NO, then the drive will most likely write in 32K block sizes

    Since your type shows 63A0 instead of 3580, most likely the resource and/or device description needs to be recreated.

    Regards,
    • Brian
  • Pierre_LG
    Pierre_LG
    19 Posts
    ACCEPTED ANSWER

    Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

    ‏2010-05-02T10:11:25Z  in response to Pierre_LG
    Brian,

    Thanks for your answer and your suggestions.

    We have V6R1 with latest PTF applied and the IOA is a 5749 IOP-less adapter.

    We have IPLed the system completely and the drive are still showed as 63A0. This is not an IBM drive... this is a FC LTO4 drive from SUN.

    Best regards and thanks one more time for your help.
    • QSECOFR
      QSECOFR
      55 Posts
      ACCEPTED ANSWER

      Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

      ‏2010-05-03T14:44:34Z  in response to Pierre_LG
      63A0 is probably the correct type then. If there is a problem, then unknown types show as *TAP. Maybe contact Sun to see if the type is correct and if there are any PTFs or firmware that needs to be loaded.

      For V6R1M0, here are the latest superseded PTFs for DUPTAP:
      MF48524
      MF48525

      For your d/t5749 IOA:
      MF49237
      MF44562

      Latest cume = C0047610

      To round down the problem as being software or hardware (including microcode PTFs and firmware), you could try your DUPTAP to virtual tape.
      • Pierre_LG
        Pierre_LG
        19 Posts
        ACCEPTED ANSWER

        Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

        ‏2010-05-03T15:09:56Z  in response to QSECOFR
        Brian,
        I've done some other tests... I've connected a TS3100 on the i5 and I was able to do a DUPTAP correctly on the 3580 LTO4 Tape Drive.

        So it looks like IBM is not supporting correctly the OEM LTO4 tape drive or IBM is limiting the Block Size of non IBM Tape Drives !!!
        Because with the IBM LTO4 Tape drive, I have no issue!!!

        By the way, I have confirmation of my colleague, responsible of the Open Systems, that he has no problem to duplicate backup tapes from old technology to the Sun LTO4 tape drives !!!

        Any suggestions?

        Thanks one more time for your support.
        • QSECOFR
          QSECOFR
          55 Posts
          ACCEPTED ANSWER

          Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

          ‏2010-05-03T16:00:50Z  in response to Pierre_LG
          Here is what I found out.

          The problem is most likely with the OEM firmware. Some OEM drives are not identifying themselves correctly to the OS. When that happens, the resource will be identified as 63A0 (standard tape drive) and the system must use the lowest common denominator for block size (32K) for compatibility.
          • Pierre_LG
            Pierre_LG
            19 Posts
            ACCEPTED ANSWER

            Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

            ‏2010-05-03T19:02:48Z  in response to QSECOFR
            Thanks Brian for your reply.

            Are there any specs or documentation within IBM describing what the OS identifies SCSI replies as correct drive ?
            Do you have a list of LTO-4 OEM drives supported by the OS/400 V6R1 ?

            If the drive is seen correctly by the OS, what ressource name would it be ?

            The support of the OEM drive mentioned that they have followed the LTO-4 SCSI specs (GA32-0450-07) and they are replying 256 KB as Block Size.

            Is there any traces or logs to take on the OS/400 to forward to the IBM support ? Any contact directly in Rochester ?

            Thanks,
            • QSECOFR
              QSECOFR
              55 Posts
              ACCEPTED ANSWER

              Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

              ‏2011-04-19T19:17:35Z  in response to Pierre_LG
              Pierre,

              Q1) Are there any specs or documentation within IBM describing what the OS identifies SCSI replies as correct drive?
              A1) From what I understand, its IBM proprietary and IBM wont' release without proper authorization, but I'm not sure how OEM get a specific return to determine/send the type of drive.

              Q2) Do you have a list of LTO-4 OEM drives supported by the OS/400 V6R1 ?
              A2) IBM does not properly "test" or "support" OEM tape devices. There isn't an approved OEM list.

              Q3) If the drive is seen correctly by the OS, what resource name would it be?
              A3) Resource names can change depending on what is available, but the resource type, if the firmware is correct, should show up as the same IBM drive type -> ex. 3580-004

              Q4) The support of the OEM drive mentioned that they have followed the LTO-4 SCSI specs (GA32-0450-07) and they are replying 256 KB as Block Size. Is there any traces or logs to take on the OS/400 to forward to the IBM support ?
              A4) Tape flight recorders, IOP dump, and tapedevicedata advanced analysis macro. Should contact Support.

              Q5) Any contact directly in Rochester ?
              A5) Yes, but you would need to contact IBM Support or use proper partner avenues to contact the IBM i Tape developer.
  • V0WR_Bill_Cooper
    V0WR_Bill_Cooper
    5 Posts
    ACCEPTED ANSWER

    Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

    ‏2011-04-19T16:14:16Z  in response to Pierre_LG
    I am experiencing a problem as well. Since going to POWER6 and POWER7 with 5774 fibre channel cards that are virtualized thru the VIOS
    3 out of 4 LTO tape drives in an STK library now show up as model 63A0. Even when going into SST the Model Type shows up as 63A0. These are IBM manufactured LTO3s that Oracle is sourcing. My problem is that the tape drives sometimes become not detected after an IPL, sometimes all 4, sometimes 2 out of 4. I have to IPL multiple times to get them back. I have evened powered down. I have a POWER5 system (soon to be migrated) attached to the same tape drives thru fibre (using a 2844 IOP) that never lose connection. Any idea where to look for a solution?
    Thanks.
    • QSECOFR
      QSECOFR
      55 Posts
      ACCEPTED ANSWER

      Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

      ‏2011-04-19T19:21:23Z  in response to V0WR_Bill_Cooper
      Bill,

      Most likely, you will need to get the latest PTFs for your 5774. I briefly asked a coworker and he agreed, that with these types of issues, you should make sure that you have the latest PTFs and firmware for the following:
      • IOA
      • IOP
      • Tape library/drive
      • Backup Recovery group for IBM i OS
      • VIOS
      • fibre switch

      After any config changes, it is important that you power cycle the IOA through concurrent maintenance or IPL the IOP (if not comm or DASD).

      Regards,
      • Brian
      • V0WR_Bill_Cooper
        V0WR_Bill_Cooper
        5 Posts
        ACCEPTED ANSWER

        Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

        ‏2011-04-19T19:41:17Z  in response to QSECOFR
        Thanks for the quick reply. We are at the latest library and tape firmware levels, however those get updated fairly infrequently. In the case of the STK software, years. What is the best way to identify ptfs needed for the IOP and other hardware? Are they always included in the latest hipers or the BRMS group? I can never easliy idntify them.
        • QSECOFR
          QSECOFR
          55 Posts
          ACCEPTED ANSWER

          Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

          ‏2011-04-20T14:01:13Z  in response to V0WR_Bill_Cooper
          APARs identify the problems. PTFs Fix the problems. A PTF may fix more than one APARs.

          Search the PTF APAR database and round down by release:
          http://www-912.ibm.com/n_dir/nas4apar.nsf/nas4aparhome

          Type in your keyword such as 5774, limit the search by release and you can put "exact match" if you want, then click search. This will give a listing of the APARs and you can read and see the fixing PTFs. When you click on the cover letter for the PTF, at the top of the PTF cover letter, you can see if the PTF has been superseded by a newer PTF.

          You could also search the PTF Cover letter database, but this usually only lists the first APAR fixed and some fix over 100 apars.
          http://www-912.ibm.com/a_dir/as4ptf.nsf/as4ptfhome

          Here's an example when I search 6.1 APARs for 5774:

          Search for: "5774"
          7 documents found

          APAR Status Abstract
          93% MA39893 CLOSED PER LIC-OTHER-SRCA6000255-WAIT 576B, 5774, 577D CARDS - THE
          89% MA37037 CLOSED PER OSP-SRCA6000255-SRCA6000266-WAIT 5749 or 5774
          88% MA39789 CLOSED PER INCORROUT-SRC57XX8301 FIBER CHANNEL LOAD SOURCE FAILS TO IPL
          88% MA38349 CLOSED PER INCORROUT-SRC57XX8301 Fiber Channel load source fails to IPL
          87% MA39094 CLOSED PER LIC-INCORROUT FC5749 FC5774 FC5735 ERROR LOG CLASSIFICATIONS
          87% MA36561 CLOSED PER IPL-SRCC6004011 IPL HANG FC5737 FC5749 FC5774
          85% MA39383 CLOSED PER LIC-DISK-OTHER-WAIT CM TO POWER OFF FIBRE CHANNEL IOA
          Hope this helps
          • V0WR_Bill_Cooper
            V0WR_Bill_Cooper
            5 Posts
            ACCEPTED ANSWER

            Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

            ‏2011-06-14T18:55:32Z  in response to QSECOFR
            We are experiencing a different error on the tape drives that configure as 63A0. We are unable to restore anything from a tape created on the 3580 reporting drive to any of the 3 - 63A0 reporting drives. I can display the tape but any restore comes back with a message: CPF3769 'Data encrypted or not save data'.

            However, a tape created on the 63A0 drives can be restored on the 3580 model drive. When we look at the hardware thru IBM i Navigator we see a difference in block size and compaction. I have attached screen shots from Navigator. thanks!

            Attachments

            • QSECOFR
              QSECOFR
              55 Posts
              ACCEPTED ANSWER

              Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

              ‏2011-06-15T16:25:23Z  in response to V0WR_Bill_Cooper
              The drive is showing it can only read a block size of 32k whereas the Ultriums typically write with 256K block sizes. The block size is the maximum that it can handle at one time, so it makes sense that the 3580 can read the 63A0 since 256K can read 256K and under (240K, 64K and 32K). If the 63A0 tape drive is not really a type of 63A0, then the problem is that the tape drive is not correctly identifying itself to the Operating system. Most likely it will need a firmware update, then power cycle the IOA, and then recreate the resource and device description.

              As a temporary circumvention, the save commands allow you to turn off optimum blocking, USEOPTBLK(*NO), which will use 32K block sizes. However, your backup performance will be greatly affected.

              • Brian
              • V0WR_Bill_Cooper
                V0WR_Bill_Cooper
                5 Posts
                ACCEPTED ANSWER

                Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

                ‏2011-06-16T14:04:04Z  in response to QSECOFR
                We are putting the same type of configuration at our DR site so we are concerned about the incompatiblity. My SAN group seems to be
                concerned about the LTO 3 drives 'emulating' a 3580 device, are all LTO drives auto-configured as 3580 device type? Is there a switch setting or something even on IBM drives to signal device type? Our IBM drives in the STK library have firmware version 93G0 which was current. Thanks.
                • QSECOFR
                  QSECOFR
                  55 Posts
                  ACCEPTED ANSWER

                  Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

                  ‏2011-06-16T14:43:13Z  in response to V0WR_Bill_Cooper
                  LTO3 drives will have a resource type of 3580-003. The library will have a different resource type such as 3581, 3584, 3573, etc.

                  An IOP dump or a macro in Service Tools' Advanced Analysis could probably determine the type and what data is sent to the OS, but this would most likely need to be read by an i developer. Almost certainly, the Tape drive does not have the IBM i configuration data correct or at all in the 'inquiry' data. Check with the tape guide and/or OEM to verify the config is set correctly for IBM i.

                  *Note: I have some decent knowledge of tape devices, but I am not an expert in this area. If anyone else who comes across this thread is more familiar, then please share any useful information.
        • QSECOFR
          QSECOFR
          55 Posts
          ACCEPTED ANSWER

          Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

          ‏2011-04-20T14:03:44Z  in response to V0WR_Bill_Cooper
          The PTFs are not always included in the latest HIPERs or BRMS PTF (or the Backup Recovery Group which includes the BRMS PTF).

          Hiper stands for "High Impact or Pervasive". There are a lot of criteria for a PTF to make the Hiper list.
          • Pierre_LG
            Pierre_LG
            19 Posts
            ACCEPTED ANSWER

            Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

            ‏2012-01-25T16:37:27Z  in response to QSECOFR
            Hi Bill,

            I know this thread is 6 month old... but were you able to find a solution ?
            By the way, are you using RMLS from STK ?
            Thanks for your update.

            Best regards,
            • V0WR_Bill_Cooper
              V0WR_Bill_Cooper
              5 Posts
              ACCEPTED ANSWER

              Re: ERROR: DUPTAP on OEM ULTRIUM-TD4 Tape Drive

              ‏2014-07-23T14:02:39Z  in response to Pierre_LG

              Pierre,

              The problem was occuring because when we had a drive failure Oracle replaced the tape drive in the STK silo with

              an invalid drive, apparently there is special code they have in the drive for an IBM i. As they replaced more drives the

              same problem occurred. We needed a specialist at Oracle to diagnose the problem. There was never a problem with RMLS

              or the i, they just needed to put in the correct drives, we have since moved on to a VTL solution. Hope this helps.

               

              Bill