VNXe and System Center 2012 intergr

Hi Mike,

ESI currently supports VNXe.  There is a VNX Management pack for System Center that I believe also supports VNXe, the documentation can be found on Powerlink.  SMI-S won't be an option for managing the VNXe in System Center 2012 so you will need to use management packs for this model.

Adrian

Hi there, is that management pack needed for SCVMM (2012) as well? Or is it only for SCOM? How about ESI? Anyone know?

Alan,

I found this question on Windows IT Pro see if this helps with your question

http://www.windowsitpro.com/article/system-center/importing-system-center-virtual-machine-manager-2012-discovery-management-pack-system-center-service-manager-2012-dependencies-142782

Hil William

Thanks for your answer. Unfortunately I don't think it will help us.

The thing is, what we want to do is classify our storage within SCVMM. SMI-S should be able to help in that regard, but it is failing. We're not talking about a monitoring scenario but rather a management-of-storage-from-scvmm-one...

We have installed the SMI-S driver, but are wondering whether there is something else we need to install?

Best regards,

Allan

Well in that case, you are fully supported :-)

I assume the SMI-S registration within VMM 2012 occurred without errors?

The first issue that many will run into is the port connection and Windows Firewall.  You will need to open the port that you are connecting through to the SMI-S Provider host (that system running the provider).  Unless you want to mess with certificates, you will end up using port 5989 - so make a new rule for that on the Provider host.

Then there's the RunAs account.  This needs to be the account used to talk to the provider itself.  It's not a Windows account, but one definied in the SMI-S Provider.  There's a default "admin" account on the provider .. and best practices would recommend that you change this accounts password, and define an additional administrator.

Once you have those two main items dealt with, registration of the SMI-S provider will result in all the defined Storage Pools and RAID Groups being displayed with the VMM 2012 storage classification area.  If that is not happening, then there's likely to be a configuration issue.

Double check for failing Jobs in the VMM 2012 environment.

Allan, the EMC SMI-S Provider as it ships today does not support the VNXe platform. The Operating Environment (OE) for the VNXe platform is different to that of the VNX, and some of required components for SMI-S support do not exist.  As a result, you will not see the VNXe platform listed under the "EMC Hardware supported by SMI-S Provider" section in the Release Notes.

While this is the current state, there is a plan to provide SMI-S support forthe VNXe platform - although this now becomes a roadmap discussion, and not something that I can provide.

However, today, as you cannot implement the SMI-S provider, you cannot implement the intergration within SCVMM 2012 that you are looking at.

Thank you for your kind responses!

I should have mentioned that we have a VNX5300 not a VNXe and this thread was one of the two closest ones I could find close to our subject.

I ran the tests suggested here:

http://blogs.technet.com/b/chrad/archive/2011/11/20/vmm-2012-how-i-got-emc-clariion-ax4-5-working-with-vmm-storage-mgmt-service.aspx

... and they come out just fine, but we're still not able to categorize the storage.

Hi again

Well, we do have the storage classification area in place in the sense, that we can choose the classification for the storage pool, but when we select the classification and click ok, it doesn't save our choice. So that next time we open up the window, the classification has been reset back to the same setting.

We've changed the default password for the admin user, but not changed users. SCVMM reports that it does have access. And firewall ports are open as well.

The error message reads:

Error (26101)

Storage discovery of provider at TCPPort 5988 for user admin failed from with error code HostTypeNotSupported .

Recommended Action

Specify valid provider, port and user credentials for storage discovery.

That may because you use the wrong port. Please use Port 5989 instead ....

But isn't the only difference that one is encrypted (5989) and the other is not (5988)? Or is there a functional difference as well?

Thanks!

Yes, that it true. Noit sure how your System is connected and wich firewall ports are opened to SMI-S Server.

RUn As Account should look like this:

An not only that, have you done the right Security Settings in your ecom configuration ?

SCVMM only uses Basic Security, thus youre settings mighjt look like this:

From Security_settting.xml, CIMRequest_AuthenticationEnabled was set to “false” to disable security.

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

*CIM Request Authentication Enabled/Disabled:

* false - ECOM will not authenticate/authorize incoming CIM requests (default)

* true  - ECOM will authenticate/authorize incoming CIM requests

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

-->

Hi again

Firewall ports are open, both 5988 and 5989. We've tried playing around with the settings, both enabling and disabling authentication. We've also tried with and without self-signed and "true" certificates.

Every now and then, we now get this error message:

Error (2912)

An internal error has occurred trying to contact an agent on the SCVMM-C01-CN1.Platon.dk server: NO_PARAM: NO_PARAM.

Unknown error (0x81051001)

Recommended Action

Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

This is from the security log on one host:

27-apr-2012 14:05:54.235 -3036-W- CSTAuthenticator: Access is denied

and this is from the cimomlog:

27-apr-2012 14:20:02.505 -3700-W- CIMOM: Exception thrown in 'OSLSProvider': com.emc.cmp.osls.api.DateTimeFormat._parseCIM():321 C:ERROR_CLASS_SOFTWARE F:ERROR_FAMILY_INVALID_PARAMETER X:ERROR_FLAG_LOGICAL Malformed DateTime Format: incorrect length

We've also seen this at an earlier point:

27-apr-2012 13:35:22.948 -1408-E- NAVSSLSocket: SSL read error: Error reading data. Error details: An error occurred as a result of an SSL protocol failure (error=140950E5). READ STATE: read header.

27-apr-2012 13:35:23.772 -868-E- NAVSSLSocket: SSL read error: Error reading data. Error details: A system call error (errno=0). READ STATE: read header.

what does dv output give you ?

Have you already setup the Clariion with testsmisprovider ?

(localhost:5988) ? dv

++++ Display version information ++++

CIM ObjectManager Name: EMC:169.254.1.217

CIMOM Version: EMC CIM Server Version 2.6.7.0.0.24

SMI-S spec version: 1.6.0

SMI-S Provider version: V4.3.2.1

SMI-S Provider Location: Proxy

SMI-S Provider Server:

Windows_NT SCVMM-C02-CN1 6.1.7601 Service Pack 1 x86_64 (64bit Libraries)

Solutions Enabler version: V7.3-1404 2.2

Firmware version information:

(Local)  CLARiiON Array CKM00120200433 (Rack Mounted VNX5300) : 5.31.0.5.704

Retrieve and Display data - 1 Iteration(s) In 0.203142 Seconds