Link to home
Start Free TrialLog in
Avatar of Ad-Apex
Ad-ApexFlag for Afghanistan

asked on

Controller Card not displaying correctly in Windows guest OS on VMware 4.1

I have a Windows 2008R2 server running as a guest OS on VMware ESXi 4.1.  We have a controller card installed (Smart Array P212) which is used solely for the purpose of attaching a robotic tape library (Quantum Scalar i40.)  VMware sees the controller card as an "Smart Array P212" in VSphere client, but windows does not detect it properly. Instead, it lists the card as "LSI Adapter, SAS 3000 Series, 8 port with 1068" in device manager.  Additionally, Windows Device manager does not list the robotic tape library that is attached. Instead, it lists "Hewlett Packard LTO Ultrium-5 Drive" under tape devices.

I was told by the manufacturer of the Quantum Scalar i40 that the Windows server needs to list the tape library itself under "Media Changers" in device manager if I want to get this to work correctly. They suggested I upgrade the firmware for the controller card.  I went to HP, found the VMware drivers recommended for the controller card, and upgraded it using HP Smart Start. I rebooted the VMware host server and powered up the Windows system, but there is no change.

When I try to apply drivers for the card within the windows guest OS, I get an error saying it is not supported in a guest OS environment.

Is there a way to apply specific drivers for the controller card for Windows to use? How can I do this in a VMware environment? Do I need to apply the drivers through VSphere? VMware is a new experience for me so I'm not sure on how this part works. Any advice would be helpful.
Avatar of cdjc
cdjc
Flag of Canada image

http://kb.vmware.com/kb/1016407

"Note:  
As of vSphere 4.0, ESX only supports connectivity to parallel SCSI tape libraries.
VMware only supports the attaching of Parallel SCSI based tape Devices to an Adaptec SCSI Controller, see Page 20 of the Virtual Machine Backup Guide for further information"
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
You will probably have to use VMDirectPath and a dedicated PCI controller to implement this solution. You will need to dedicate the entire controller to the backup vm so that the vm OS can detect the controller, and thus the media changer.

Please check the following for any configuration issues.

*    The tape hardware must be connected to a VMWare-supported Adaptec SCSI controller.
*    The tape hardware must be SCSI ID addressed and cannot be LUN addressed.
*    The virtual and physical SCSI Id's must match each other.
*    Fiber connected tape devices are not supported.
*    Tape devices cannot be connected to RAID controllers.
*    Tape devices should not share a BUS with any other non-tape device, and should be given their own dedicated SCSI controller.
*    The SCSI controller for the guest VM should be configured as a LSI Logic SCSI card and not the BUS logic card.
*    BUS sharing must be disabled


Have you read these articles in the VMware KB.

KB article link http://kb.vmware.com/kb/1026157

http://kb.vmware.com/kb/1016407 configuring tape drives on vSphere

See http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010789 for more information on VMDirectPath I/O Passthrough.
Avatar of Ad-Apex

ASKER

Thanks to both of you. This is the best info I have seen on the subject. I will reads through all that material and come back with any questions / comments and see if this helps me out.
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
pay special attention to this kb article, to check that the host is not claiming the LUN.

KB article link http://kb.vmware.com/kb/1026157
I also note that the Smart Array P212 may not support LUN Scanning.

So this might cause you an issue also.

I believe the tape library and tape drive are on different LUNs on the i40.

Avatar of Ad-Apex

ASKER

It appears this card may not be a fit for this particular server / instance. Still checking into it.
Avatar of Mixers
Mixers

Any news on this Ad-Apex? I was told the card may not be a fit either. Before going through ordering and switching it out, was wondering if you resolved the issue.
Avatar of Ad-Apex

ASKER

Well, no real solution yet. However, I think the card is not a fit. I cannot get it to work under any circumstances. I would suggest you get a different one.
Avatar of Ad-Apex

ASKER

I plan to call VMWare directly and ge an answer on this. I'll post whatever I find.
Avatar of Ad-Apex

ASKER

Here's the latest:

I contacted a VMware tecxhnician and he sent me a link with step-by-step instructions on how to configure the card. It is something i had already found on my own, though, so it was no real help.  I took the time to make screen shots, though, so if anyone who knows VMware would like to have a look, perhaps you'll see something I am doing wrong. As a further note, when adding the P212 I selected (1:0) as the Virtual Device Node.

One thing stands out to me: the device attached to the P212 is a Scalar i40 tape library, but VSphere says "HP Serial Attached SCSI Tape".  That doesn't seem right.... any thoughts on that?

 User generated image User generated image
Avatar of Ad-Apex

ASKER

The Scalar i40 is a Multi-LUN device, and not multi target.  Because of this the robotic tape library cannot be used because VMware and the guest OS will only see the Tape drive and not the tape changer which is all part of the same unit.  This is not a problem with the card but the type of tape library.

In the illustration in my previous post called p212devices, you see the only item shown there is the Tape.  If the Scalar i40 library was multi target the tape changer would also be listed here.
Avatar of Ad-Apex

ASKER

Tell me about it! The guy that was working with me was horrible. He would just send me KB articles and say "This is how we handle tape drives." I even sent him the illustrations above and he didn't get back to me for a few days.  I finally pestered him some more and he said:  

"Sorry for the late response as I was OOTO yesterday. According to the screen shots which you uploaded the VM is configured correctly for using the tape drive."

Regardless, the interesting part is I just got it working (sort-of.)  I figured the VM could see the tape drive, so there must be a reason Backup Exec kept reporting it as offline. The reason was because the tape LOADER wasn't accessible so all I had to do in theory was manually tell the Scalar i40 to load a tape using the web interface. It worked; Backup Exec can see and use the tape.

I just have to manually load a new tape every day. It'll work for now, and I am not taking advantage of the autoloader features, but at least I can backup my server relaibly.