- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Command View on a virtual machine
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2012 05:28 AM
06-27-2012 05:28 AM
I've installed Command View 10.0 on a Windows 2008 R2 virtual machine (vsphere 5). Command View sees one path to the EVA 8100, and it's the path to the slave controller so it can't manage the EVA. I've verifed that the virtual machine has 4 paths to the EVA (2 to the master controller and 2 to the slave controller).
I used the instructions here to setup a generic scsi connection for Command View to communicate with the EVA.
The exact message that Command View gives me is:
The storage system is not responding to management command requests in a timely manner. This may be due to a prior management command request with excessively long response time, or a communication problem. HP P6000 Command View will recover automatically when the storage system is able to respond to management commands. Management command access to the storage system does not affect host I/O.
When I click "Path Test" is when Command View reveals that it only sees one controller (the slave).
Any ideas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2012 09:49 AM - edited 06-27-2012 09:50 AM
06-27-2012 09:49 AM - edited 06-27-2012 09:50 AM
Re: Command View on a virtual machine
I didn't setup VMDirectPath. It looks like you have to dedicate an HBA to the VM...which I can't do without purchasing additional HBAs for the blade enclosure.
So unless someone can correct my understanding that you must have physical HBAs dedicated to the VM, then for me it looks like Command View on VM is a no go.
- Tags:
- HBA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2012 01:18 PM
06-27-2012 01:18 PM
Re: Command View on a virtual machine
Jeremy:
I just followed the same instructions, installed CV 10 and it worked right out of the box. I am able to fully manage the EVA it seems.
Is this a new installation? Does the ESXi server have anything else on it?
Check your zoning.
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2012 09:32 AM - edited 06-28-2012 09:34 AM
06-28-2012 09:32 AM - edited 06-28-2012 09:34 AM
Re: Command View on a virtual machine
Yes, this is a new installation of Command View on a newly created virtual server. I have an existing physical server running CV EVA 9.4 that I'm trying to replace with a virtual server.
There are other virtual servers on the ESX host. I can see all the proper paths to the EVA in vSphere so I believe the zoning is correct.
Did you dedicate physical HBAs to your virtual server or is it sharing the HBAs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2012 12:33 PM
06-28-2012 12:33 PM
SolutionPage 7 of this document lists the configurations that will work for Command View within a VM.
I have an EVA 8100 and therefore must have an HBA dedicated to the VM. Other EVA models do not have this restriction. I think this answers my question. It also explains why you may have been able to get it to work without dedicating an HBA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2012 12:37 PM
06-28-2012 12:37 PM
Re: Command View on a virtual machine
Yep, I have 2 4400's and a 6400. That would explain why my test worked flawlessley.
And yes, I did NOT set up dedicated HBA's.
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)