- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: P2000 G3 with Virtual Machine Manager 2012
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
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
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
тАО03-27-2013 02:31 PM
тАО03-27-2013 02:31 PM
P2000 G3 with Virtual Machine Manager 2012
So far overall this has been a bad experience. Getting the SAN to talk to VMM over SMI-S was a large pain. Credentials kept failing, even though they had complete manage rights to the SAN via all protocols. Finally got this working, not 100% sure what actually made it start talking. Still get Errors trying to create luns and refresh from VMM. Some it is VMM 2012 but the befudling part was the access denied issues with smi-s login.
Anyone else having Similiar experiences?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2013 10:19 AM
тАО04-01-2013 10:19 AM
Re: P2000 G3 with Virtual Machine Manager 2012
What is the exact error you are receiving?
Make sure credentials does not include a comma, double quote, or backslash, and can have a maximum of 19 bytes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2013 12:56 PM
тАО04-01-2013 12:56 PM
Re: P2000 G3 with Virtual Machine Manager 2012
Credentials are the default username and a 9 digit password that contains numbers and letters.
This is the latest error i got creating a Logical Unit from vmm 2012.
This is the code that runs that throws the error.
$pool = Get-SCStoragePool -ID "6833da47-63e1-4949-abeb-3a15cca6f1d2" -Name "VM`'s & Data"
New-SCStorageLogicalUnit -StoragePool $pool -DiskSizeMB 512000 -Name "test2" -Description "" -ProvisioningType "Fixed" -RunAsynchronously
Error (26135)
Creating storage logical unit TempPenta on storage pool 208000c0ff159741:00c0ff15998a000015d7485100000000 failed with error code SM_RC_GENERIC_FAILURE.
Recommended Action
Specify valid parameters for creating logical unit.
After that attempt i tried to rescan the provider and got this error
Error (26101)
Storage discovery of provider http://192.168.1.25:5988 for user manage failed from SYSCTR1.local.net with error code 2. Failed: Discovery cannot connect to namespace:CONNECT_FAILED::
Recommended Action
Specify valid provider, port and user credentials for storage discovery.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-01-2013 04:06 PM
тАО04-01-2013 04:06 PM
Re: P2000 G3 with Virtual Machine Manager 2012
IMHO, if you are getting these errors on VMM then I reckon VMM Support Forum will be the right support community where this issue will be viewed by the larger interested group. I understand VMM is connected to P2000 G3 but I can not think of anything relevant to P2000 after searching for the errors you posted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2013 01:57 PM
тАО04-04-2013 01:57 PM
Re: P2000 G3 with Virtual Machine Manager 2012
Well, the funny thing is i couldn't rescan the SAN, until I rebooted the Management Controllers on the SAN after that it scans just fine. So that really leads me to believe it's a san issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2013 11:04 AM
тАО11-27-2013 11:04 AM
Re: P2000 G3 with Virtual Machine Manager 2012
Any update on this?
New storage logical unit creation always fails in my configuration (P2000 G3 FC/SCVMM 2012).
Every time got error 26135:
Creating storage logical unit <LUN Name> storage pool 208000c0ff13d4ca:00c0ff13b9b00000aa37965200000000 on failed with error code Failed .
Recommended Action
Specify valid parameters for creating logical unit.
Is there any support for this type of MSA?
Refreshing storage pools via SCVMM take ages to finish.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-20-2013 03:28 AM
тАО12-20-2013 03:28 AM
Re: P2000 G3 with Virtual Machine Manager 2012
I'm using SCVMM 2012 R2 and have the same problem with a P2000i G3 iSCSI MSA. Adding it is no problem. I can also do a refresh, but rescan exits with:
Error (26101) Storage discovery of provider http://<IP-address>:5988 for user <user> failed from <VMMHost> with error code 2. Failed: Discovery cannot connect to namespace:CONNECT_FAILED::
Recommended Action Specify valid provider, port and user credentials for storage discovery.
In Powershell the command is Read-SCStorageProvider where the difference between "Refresh" and "Rescan" is whether the parameter "-Force" is used or not.
The P2000i has firmware TS250P002. There is a later version available, TS250P003, but it does not seem to solve this problem, because the only fix from the previous version is: "Disallow user creation using reserved user names."
Restarting the management controllers does not solve the problem for me.