9 Replies Latest reply on Oct 21, 2015 8:24 AM by MikelPham

    StorageTek SL150 and ESXi 5.0/Cisco UCS Compatible !

    MikelPham

      Hi everybody,

      My system has a configuration like below:

      • Blade Server: UCS B200 M2 (Model: N20-B6625-1) with mezzazine card M81KR
      • Host OS: VMWare ESXi 5.0.0 - 623680
      • VM-to-TAPE Connection: <(Windows Server 2008 R2 SP1) on an ESXi5.0> Blade Server --> Chassis --> Extender (FEX) --> Fabric Interconnect (UCS 6248UP) --> SAN Switch (Cisco MDS 9100) --> TAPE StorageTek SL150


      I searched on google to find any possible solution and have concluded 2 methods:


      Method 1: Add the TAPE driver like a SCSI device on VM


      I followed this guide http://www.boche.net/blog/index.php/2008/10/27/connect-a-fibre-attached-tape-device-to-a-vm-on-esx/

      But the diffrerence between the above guide and my real testing case is:

        • the guide: Perform a scan on the fibre HBA cards on host (it is an physical host with QLogic HBA Driver) to discover the fibre tape device. In this case, I’ve got an HP MSL5026 autoloader containing a robotic library and two tape drives
        • my real testing case: scan the fibre HBA cards on host (it is an Cisco UCS B200 M2 with Cisco VIC FCoE HBA Driver), i've got only 2 Tape HP Driver (cannot discover the Robotic Library-Media Changer) like images below:

      1.jpg

       

      2.jpg

       

      3.jpg

       

      Additional Symptoms are the log on ESXi host when the Robotic Device is unclaimed, ESXi host only recognizes 2 HP Fibre Channel Tape. Below is the output of esxcli storage command:

       

      fc.20000025b500006f:20a10025b500006f-fc.500104f000d80990:500104f000d80991-naa.500104f000d80990

        UID: fc.20000025b500006f:20a10025b500006f-fc.500104f000d80990:500104f000d80991-naa.500104f000d80990

        Runtime Name: vmhba1:C0:T4:L0

        Device: naa.500104f000d80990

        Device Display Name: HP Fibre Channel Tape (naa.500104f000d80990)

        Adapter: vmhba1

        Channel: 0

        Target: 4

        LUN: 0

        Plugin: NMP

        State: active

        Transport: fc

        Adapter Identifier: fc.20000025b500006f:20a10025b500006f

        Target Identifier: fc.500104f000d80990:500104f000d80991

        Adapter Transport Details: WWNN: 20:00:00:25:b5:00:00:6f WWPN: 20:a1:00:25:b5:00:00:6f

        Target Transport Details: WWNN: 50:01:04:f0:00:d8:09:90 WWPN: 50:01:04:f0:00:d8:09:91

       

      fc.20000025b500006f:20a10025b500006f-fc.500104f000d80990:500104f000d80991-

        UID: fc.20000025b500006f:20a10025b500006f-fc.500104f000d80990:500104f000d80991-

        Runtime Name: vmhba1:C0:T4:L1

        Device: No associated device

        Device Display Name: No associated device

        Adapter: vmhba1

        Channel: 0

        Target: 4

        LUN: 1

        Plugin: (unclaimed)

        State: dead

        Transport: fc

        Adapter Identifier: fc.20000025b500006f:20a10025b500006f

        Target Identifier: fc.500104f000d80990:500104f000d80991

        Adapter Transport Details: Unavailable or path is unclaimed

        Target Transport Details: Unavailable or path is unclaimed

       

      fc.20000025b500006f:20b10025b500006f-fc.500104f000d80993:500104f000d80994-naa.500104f000d80993

        UID: fc.20000025b500006f:20b10025b500006f-fc.500104f000d80993:500104f000d80994-naa.500104f000d80993

        Runtime Name: vmhba2:C0:T4:L0

        Device: naa.500104f000d80993

        Device Display Name: HP Fibre Channel Tape (naa.500104f000d80993)

        Adapter: vmhba2

        Channel: 0

        Target: 4

        LUN: 0

        Plugin: NMP

        State: active

        Transport: fc

        Adapter Identifier: fc.20000025b500006f:20b10025b500006f

        Target Identifier: fc.500104f000d80993:500104f000d80994

        Adapter Transport Details: WWNN: 20:00:00:25:b5:00:00:6f WWPN: 20:b1:00:25:b5:00:00:6f

        Target Transport Details: WWNN: 50:01:04:f0:00:d8:09:93 WWPN: 50:01:04:f0:00:d8:09:94

       

      2015-09-30T05:28:32.892Z cpu13:21107491)WARNING: VMW_SATP_ALUA: satp_alua_getTargetPortInfo:91:Could not find target port group ID for path "vmhba1:C0:T4:L1" - Not found (195887107)

      2015-09-30T05:28:32.892Z cpu13:21107491)WARNING: NMP: nmp_SatpClaimPath:2093:SATP "VMW_SATP_ALUA" could not add  path "vmhba1:C0:T4:L1" for device "naa.500104f000d80990". Error Not found

      2015-09-30T05:28:32.892Z cpu13:21107491)WARNING: ScsiPath: 4561: Plugin 'NMP' had an error (Not found) while claiming path 'vmhba1:C0:T4:L1'.Skipping the path.

      2015-09-30T05:28:32.892Z cpu13:21107491)ScsiClaimrule: 1329: Plugin NMP specified by claimrule 65535 was not able to claim path vmhba1:C0:T4:L1. Busy

      2015-09-30T05:28:32.892Z cpu13:21107491)ScsiClaimrule: 1554: Error claiming path vmhba1:C0:T4:L1. Busy.

       

      esxcli storage core device list

       

      naa.500104f000d80990

        Display Name: HP Fibre Channel Tape (naa.500104f000d80990)

        Has Settable Display Name: true

        Size: 0

        Device Type: Sequential-Access

        Multipath Plugin: NMP

        Devfs Path: /vmfs/devices/genscsi/naa.500104f000d80990

        Vendor: HP

        Model: Ultrium 5-SCSI

        Revision: Y5BS

        SCSI Level: 6

        Is Pseudo: false

        Status: on

        Is RDM Capable: true

        Is Local: false

        Is Removable: true

        Is SSD: false

        Is Offline: false

        Is Perennially Reserved: false

        Thin Provisioning Status: unknown

        Attached Filters:

        VAAI Status: unknown

        Other UIDs: vml.0201000000500104f000d80990556c74726975

       

      naa.500104f000d80993

        Display Name: HP Fibre Channel Tape (naa.500104f000d80993)

        Has Settable Display Name: true

        Size: 0

        Device Type: Sequential-Access

        Multipath Plugin: NMP

        Devfs Path: /vmfs/devices/genscsi/naa.500104f000d80993

        Vendor: HP

        Model: Ultrium 5-SCSI

        Revision: Y5BS

        SCSI Level: 6

        Is Pseudo: false

        Status: on

        Is RDM Capable: true

        Is Local: false

        Is Removable: true

        Is SSD: false

        Is Offline: false

        Is Perennially Reserved: false

        Thin Provisioning Status: unknown

        Attached Filters:

        VAAI Status: unknown

        Other UIDs: vml.0201000000500104f000d80993556c74726975

       

      Reference URL:

        http://www.gabesvirtualworld.com/changing-satp-claimrules-specific-storage-configurations/

        https://nordischit.wordpress.com/2012/05/31/sxi-5-hp-p212-and-lto-5-tape-drive-goes-offline/


      Method 2: Configure VMDirectPath I/O pass-through devices on the VM to passthrough FC Device to the VM

       

      I followed this guide:

      http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010789

      I have Create 2 news vHBA Card on Cisco UCS Manager and follow the guide:

       

      41.jpg

       

      42.jpg

       

      43.jpg

       

      But the strange things that at the step of: When the devices are selected, they are marked with an orange icon. Reboot for the change to take effect. After rebooting, the devices are marked with a green icon and are enabled --> Reboot the ESXi host but when i login again, nothing changed when the orange icon and the warning: This device is pasthrough capable but not running in passhrough mode

      is still appear (just as if the ESXi host is never rebooted !!!)


      4.jpg


      So that i cannot add PCI device on VM to passthrough new HBA.


      In conclusion:

      Would you give me some clue or idea to connect my Oracle TAPE StorageTek SL150 with my Windows Server 2008 Virtual Machine:

      • Method1 or Method2 support for my case, is it possible to deploy and work (with infrastructure includes: ESXi 5.0; Cisco UCS BM200 M2, TAPE Oracle StorageTek SL150) ?
      • If any Method1 or Method2 is possible and is the right choice, is there any misconfiguration in my case so that i can make everything work correctly ?

       

      I'm very appreciated for you help

      Sincerely !

      Mikel.