Unsolved
This post is more than 5 years old
5 Practitioner
•
274.2K Posts
0
3025
Discovering a VNX 7500 with ViPR
Hi:
I'm trying to discover a VNX 7500 with ViPR 2.0. Here's the some of the data on the setup. I can supply more if necessary.
- VNX 7500 block w/firmware 5.32.0.5.215
- SMI-S Provider V4.6.2 on W2K8 R2 Enterprise
- One DGC VRAID Device visible to host sd \\.\PHYSICALDRIVE1
The SMI-S Provider on the host sees the VNX. If I use the testsmiprovider to EnumerateInstanceNames (ein) of CIM_StorageVolume I get a list of the 17 LUNS on the VNX.
ViPR discovers the provider OK and lists it on the Physical Assets -> Storage Providers page. However I am never able to see the VNX on the Physical Assets -> Storage Systems page.
Any clues as to what the problem might be ? Thanks
Peter
Y1Udba1GsO12085
71 Posts
0
October 3rd, 2014 00:00
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
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 3rd, 2014 08:00
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
Velik1
36 Posts
0
October 3rd, 2014 08:00
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
you have to use SMI-S addsys command to add VNX array using management IP addresses.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 3rd, 2014 08:00
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
Y1Udba1GsO12085
71 Posts
0
October 3rd, 2014 08:00
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?
Velik1
36 Posts
0
October 3rd, 2014 09:00
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.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 3rd, 2014 09:00
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...
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 3rd, 2014 10:00
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
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 3rd, 2014 11:00
Some additional information.
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...
Y1Udba1GsO12085
71 Posts
0
October 6th, 2014 04:00
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
Velik1
36 Posts
0
October 6th, 2014 07:00
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?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 7th, 2014 09:00
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.
GBson
4 Posts
0
October 7th, 2014 09:00
I had similar issue at a customer site recently. Once you delete the storage array you cannot get VIPR to rediscover as normal. VIPR think its already there and wont rediscover it again. What you need to do is open a case with support and they can dial-in and fix for you.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
October 9th, 2014 14:00
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.]
Y1Udba1GsO12085
71 Posts
0
October 15th, 2014 06:00
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