Discovering a VNX 7500 with ViPR

Hi,

Did you add the VNX system to the SMI-S provider using the "addsys" command while inside the testsmisprovider menu?

This is the right process to add a new storage system to your SMI-S provider.

Let us know if you still have issues.

Regards

Hi Javier:

Here is what I get from the testsmiprovider:

Built with EMC SMI-S Provider: V4.6.2

Namespace: root/emc

repeat count: 1

(localhost:5988) ? dv

++++ Display version information ++++

CIM ObjectManager Name: EMC:10.109.43.233

CIMOM Version: EMC CIM Server Version 2.7.3.6.0.11

SMI-S qualified version: 1.5.0

SMI-S Provider version: V4.6.2.9

SMI-S Provider Location: Proxy

SMI-S Provider Server:

Windows_NT dqaf3233 6.1.7601 Service Pack 1 x86_64  (64bit Libraries)

Solutions Enabler version: V7.6-1808 2.26

Firmware version information:

(Local)  CLARiiON Array APM00113804670 (Rack Mounted VNX7500) : 05.32.000.5.215

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

Please press enter key to continue...

Peter

please see this document

ViPR 2.1 - Add EMC VMAX and EMC VNX for Block Storage to ViPR

on setting up VNX through SMI-S.

specifically this line

• For VNX, the SMI-S provider host needs IP connectivity over the IP network with connections to both VNX storage processors.

you have to use SMI-S addsys command to add VNX array using management IP addresses.

Hi Javier:

Thanks for the reply.  I thought addsys was only required for out of band discovery.  The VNX in this configuration is connected in-band via FC to the server where the provider is running.

Peter

You are absolutely right. I didn't read that you had a volume assigned. In any case, I would also try adding it out of band just in case this is the issue.

If you run "dv" inside testsmisprovider, do you see your VNX listed?

Output code is 7. Success would be 0.

Could you verify whether SMI-S and VNX are the right version, based on ViPR Support Matrix

verify username/password.

Hi Velik:

Here are the results of the addsys.  The VNX still does not appear in the Physical Asset display.

Peter

Built with EMC SMI-S Provider: V4.6.2

Namespace: root/emc

repeat count: 1

(dqaf3233.lss.emc.com:5989) ? addsys

Add System {y|n} : y

ArrayType (1=Clar, 2=Symm) [1]: 1

One or more IP address or Hostname or Array ID

Elements for Addresses

IP address or hostname or array id 0 (blank to quit): 10.109.43.45

IP address or hostname or array id 1 (blank to quit): 10.109.43.46

IP address or hostname or array id 2 (blank to quit):

Address types corresponding to addresses specified above.

(1=URL, 2=IP/Nodename, 3=Array ID)

Address Type (0) [default=2]:

Address Type (1) [default=2]:

User [null]: clariion

Password [null]: clariion

++++ EMCAddSystem ++++

OUTPUT : 7

Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed

       5=Invalid Parameter

       4096=Job Queued, 4097=Size Not Supported

Note: Not all above values apply to all methods - see MOF for the method.

In 0.222642 Seconds

Please press enter key to continue...

SMI-S is 4.6.2 on the system, 4.6.2.6 in the ESSM

VNX Block is 5.32.000.5.125 on VNX, 5.32 in the ESSM

VNX username and password are correct

Some additional information. 

• OUTPUT : 7 means the system is already known by the Provider.
• The provider also knows about the remote serviceaccesspoints, output below.

Built with EMC SMI-S Provider: V4.6.2

Namespace: root/emc

repeat count: 1

(dqaf3233.lss.emc.com:5989) ? ein

Class: cim_remoteserviceaccesspoint

++++ Testing EnumerationInstanceNames: cim_remoteserviceaccesspoint ++++

Instance 0:

Clar_RemoteServiceAccessPoint.CreationClassName="Clar_RemoteServiceAccessPoint",

Name="10.109.43.45",SystemCreationClassName="Clar_StorageProcessorSystem",System

Name="CLARiiON+APM00113804670+SP_A"

Instance 1:

Clar_RemoteServiceAccessPoint.CreationClassName="Clar_RemoteServiceAccessPoint",

Name="10.109.43.46",SystemCreationClassName="Clar_StorageProcessorSystem",System

Name="CLARiiON+APM00113804670+SP_B"

Enumerate 2 instance names; repeat count 1;return data in 0.014648 seconds

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

Please press enter key to continue...

Peter, did you figure this out? I would suggest removing the LUN attached to the server and adding the VNX using addsys so it is managed out of band.

Regards

And I also want to ask this:  did you, at any point during the lifetime of your ViPR installation, DELETE that storage system using GUI or CLI or API from ViPR?

I have deleted the LUN from the VNX that the host saw and removed the zone to that host.  My ViPR instance still does not see the VNX.

When I first installed ViPR it did see the VNX in the Storage Systems display.  It was discovered out of band  Then I deleted the storage array from the GUI since I wanted to discover it inband.  The ViPR instance hasn't seen the array since then.

When I try to open a support case it indicates I can't because of the license type.  Probably because we're using it inside of EMC.

An error occurred attempting to send the support request to ConnectEMC. [Error 3001 (http: 403): This operation is forbidden due to license check failure.. Permission denied for trial license CONTROLLER.]

Hi, you can connect directly to support.emc.com and open a Service Request indicating your issue. As you said, ConnectEMC probably doesn't work from within EMC network.

Regards