HP MSL6000 Tape Library & ESX Server

ali1982 · ‎02-24-2009

Hi

I am unable to get a virtual server to recognize the tape drive from an HP MSL6000 tape library. The library is connected to the ESX host via a 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI card and inside Storage Adapters on the ESX server it detects the library on path vmhba 2:0:0. I can present this to a virtual server as a SCSI device and it has a media changer but says no tape drive is connected to the library.

Does anyone know if it is possible to connect a tape libraryin this manner?

Thanks

dconvery · ‎02-24-2009

I could only find this in the backup guide. I could not find it on the HCL.

"VMware supports attaching SCSI drives to the ESX Server using Adaptec SCSI adapters. Using other adapters, such as LSI MPT-Fusion SCSI, is not supported."

http://pubs.vmware.com/vi35u2/backup/vm_bug_overview.3.10.html#966788

Dave

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

Erik_Zandboer · ‎02-24-2009

Is that card a RAID card or a non-RAID card? A RAID card will not work for sure. If it is a non-RAID card, make sure that the ID of the drive and the robot are matched inside the VM, so if your tape sits at SCSI ID4, then make sure you pass that device to the VM over for examples SCSI1:4. The same goes for the robot. Let's say the robot sits at physical SCSI ID 5, then pass it to the VM as SCSI1:5.

If you look at the device manager in Windows, do you see a tapedrive (even an unknown one) or nothing?

Visit my blog at http://erikzandboer.wordpress.com

Visit my blog at http://www.vmdamentals.com

Texiwill · ‎02-24-2009

Hello,

I attach a similar device to my servers, check out http://www.eweek.com/c/a/Virtualization/How-to-Attach-Local-Tape-Device-to-VMware-ESX-Host/ for assistance. However, if your SCSI HBA is not a non-RAID Adaptec device chances are it will not work.

Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill

ali1982 · ‎02-25-2009

Thanks for the replies, I have ordered an Adaptec card of the HCL and hopefully that will resolve the issue.

Alister

dconvery · ‎02-25-2009

Alister -

If you could, please post back once you have installed the card and confirm if it works or not.

Dave

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

ali1982 · ‎03-05-2009

I have replaced the SCSI card with a card from the HCL list and we still get the same problem, VMWare still only sees the media changer and not the drive drive of the MSL6000

Thanks

dconvery · ‎03-05-2009

Have you checked SCSI IDs? If you attach it to a Windows or Linux system is it recognized?

Dave Convery - VMware vExpert 2009

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

ali1982 · ‎03-05-2009

Hi

I have attached screen shots to show what we get as it is easier than explaining we can see the library in Vmware and attach it to a windows VM however we do not see the drive in VMKware and in windows it knows the library has a drive but is unable to communicate with it.

Thanks

Alister

dconvery · ‎03-05-2009

Tape tools "sees" the tape drive as down. Do you get the same result if you attach it to a physical machine? Check your front panel settings as well to make sure everything is set up properly.

Dave Convery - VMware vExpert 2009

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

ali1982 · ‎03-05-2009

Hi it works fine attached to a physical machine we see the drive as a seperate item in device manager but not when attached to vm

dconvery · ‎03-05-2009

Have you checked /proc to see what it lists? also, when you set it up in the VM, it should be two generic SCSI devices - one for the changer and one for the drive. And the virtual SCSI IDs should match the physical IDs.

Dave Convery - VMware vExpert 2009

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

ali1982 · ‎03-05-2009

Hi I am not sure if I am looking in the wrong place but under /proc/scsi I dont see it listed at all? Just The dell MD3000i we use for storage

# ls

aic7xxx scsi sg vmkiscsi vsa0

# vi scsi

Attached devices:

Host: scsi3 Channel: 00 Id: 00 Lun: 00

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 01

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 02

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 03

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 04

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 05

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

dconvery · ‎03-05-2009

Is there a /proc/scsi/scsi ?

Dave Convery - VMware vExpert 2009

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

ali1982 · ‎03-05-2009

Please see below and thank you for your patience

# # cd /proc/scsi/scsi

-bash: [root@FL004SV0100: command not found

# -bash: cd: /proc/scsi/scsi: Not a directory

# # cd /proc/scsi

# # dir

# aic7xxx scsi sg vmkiscsi vsa0

t@FL004SV0100 scsi]# vi /proc/scsi/scsi

Attached devices:

Host: scsi3 Channel: 00 Id: 00 Lun: 00

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 01

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 02

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 03

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 04

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 05

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

dconvery · ‎03-05-2009

OK... paste the output of these commands here:

cat /proc/scsi/scsi

cat /proc/scsi/aic7xxx

/proc/scsi/aic7xxx may be a directory, if it is give me the contents. One of the files in there should list everything.

Dave Convery - VMware vExpert 2009

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

ali1982 · ‎03-05-2009

# cat /proc/scsi/scsi

Attached devices:

Host: scsi3 Channel: 00 Id: 00 Lun: 00

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 01

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 02

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 03

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 04

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

Host: scsi3 Channel: 00 Id: 00 Lun: 05

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

# cat /proc/scsi/aic7xxx

cat: /proc/scsi/aic7xxx: Is a directory

# cd /proc/scsi/aic7xxx

# dir

1 2

ali1982 · ‎03-05-2009

# vi 1

Adaptec AIC7xxx driver version: 6.3.9

Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter

aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

Allocated SCBs: 6, SG List Length: 85

Serial EEPROM:

0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a

0x08f4 0x605d 0x2807 0x0010 0x0301 0xffff 0xffff 0xffff

0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x4a50

Target 0 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Goal: 20.000MB/s transfers (10.000MHz, offset 15, 16bit)

Curr: 20.000MB/s transfers (10.000MHz, offset 15, 16bit)

Channel A Target 0 Lun 0 Settings

Commands Queued 307

Commands Active 0

Command Openings 1

Max Tagged Openings 0

Device Queue Frozen Count 0

Target 1 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Adaptec AIC7xxx driver version: 6.3.9

Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter

aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs

Allocated SCBs: 6, SG List Length: 85

Serial EEPROM:

0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a

0x08f4 0x605d 0x2807 0x0010 0x0301 0xffff 0xffff 0xffff

0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x4a50

Target 0 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 1 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 2 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 3 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 4 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 5 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

"2" 43L, 1921C

dconvery · ‎03-05-2009

can you cat 2 as well?

Dave Convery - VMware vExpert 2009

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

ali1982 · ‎03-05-2009

# cat 2

Adaptec AIC7xxx driver version: 6.3.9

Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter

aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs

Allocated SCBs: 6, SG List Length: 85

Serial EEPROM:

0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a

0x08f4 0x605d 0x2807 0x0010 0x0301 0xffff 0xffff 0xffff

0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x4a50

Target 0 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 1 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 2 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 3 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 4 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 5 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 6 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 7 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 8 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 9 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 10 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 11 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 12 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 13 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 14 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 15 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

# cat 1

Adaptec AIC7xxx driver version: 6.3.9

Adaptec (Compaq OEM) 3960D Ultra160 SCSI adapter

aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

Allocated SCBs: 6, SG List Length: 85

Serial EEPROM:

0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a 0xcb3a

0x08f4 0x605d 0x2807 0x0010 0x0301 0xffff 0xffff 0xffff

0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x4a50

Target 0 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Goal: 20.000MB/s transfers (10.000MHz, offset 15, 16bit)

Curr: 20.000MB/s transfers (10.000MHz, offset 15, 16bit)

Channel A Target 0 Lun 0 Settings

Commands Queued 307

Commands Active 0

Command Openings 1

Max Tagged Openings 0

Device Queue Frozen Count 0

Target 1 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 2 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 3 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 4 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 5 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 6 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 7 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 8 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 9 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 10 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 11 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 12 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 13 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 14 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 15 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

#