Start a Conversation

Unsolved

This post is more than 5 years old

1282

January 29th, 2016 12:00

ViPR 2.3 Add Storage Provider, Add Storage System not working VNXe

Who can I talk to about the ViPR side of connecting to a Storage SMI-S Provider?

I have already consulted with some Eng resources on the vVNX (VNXe) team and they indicated that the provider for this is running on the Unisphere interface, on port 5989, username is: local/admin  ..password is configured Unisphere password.

However I have tried all combinations of adding via 'Add Storage Provider' and 'Add Storage System', along with trying different port numbers (like 5988, and 443, etc) and cannot get ViPR to discover.

The closest I can get is if I add VNXe in 'Add Storage System' with port 5989 and user: admin and Unisphere password then it says registered (check), but Status shows 'thinking' (refresh icon), but thinks forever.. (or sometimes comes back with 'broken pipe' error)..

The only other way that shows something curious is if I use 'Add Storage Provider' and add it as 'Third-party Block' then use the username 'service' and configured service password, then it comes back as green check but I don't think anything works.. I think it just checks that it successfully connects to an SSH server (that option uses port 22)..

On the storage side if I go to https:// :5989/ECOMDebug   ..the page works so I believe the SMI-S Provider is listening.

I would like to find a suitable resource to discuss the operation of this from a ViPR-side perspective as I am not able to find much documentation on connecting to VNXe / vVNX..

Any help is appreciated.

UPDATE:

This is the error I see when I attempt to add the storage appliance in what should be the proper way:

"Discovery Status

Discovery failed for VNXe urn:storageos:StorageSystem:8d96a2aa-edb0-4921-8975-f940a9d43b9b:vdc1: The POST /api/types/system/instances failed with the status code: Bad Request and the message: { "Severity" : 3, "Type" : "http://schemas.emc.com/edaa/ecom/common/error/resource_bad_request", "ErrorCode" : 404, "HTTPStatusCode" : 400, "Messages" : [ { "en" : "CimOverEdaaHttpRequest::parseBaseUri()-Base URI '/ecom/edaa/' not found" } ], "Created" : "2016-02-01T15:42:44Z", "Request" : null, "RequestorAddress" : "0:0:0:0:0:FFFF:101:15E", "RequestorIdentity" : "return from getAttr" }

"

27 Posts

March 17th, 2016 08:00

Hi oliver801 :

Could it be a version incompatibility issue? Can you share what the versions are for the VNXe and provider?

 

Thanks,

Ura

62 Posts

March 18th, 2016 03:00

I am not a VIPS specialist. What type of VNXe you want to manage? Some of our tools like for example VNX Monitoring and Reporting are able to work with VNXe1600 and VNXe3200 Arrays (VNXe "second Generation") but not with the older VNXe Arrays like VNXe 3100, VNXe 3150 and VNXe 3300.

As per VIPX Controller Support Matrix only VNXe3200 is supported.

11 Posts

March 18th, 2016 08:00

I am building a learning lab, and so I need to be able to find a suitable virtual storage appliance which can be registered with ViPR platform. ViPR ships with SMI-S support for version 1.5

I found the EMC appliance: vVNX which is a virtual storage appliance based on the VNXe 3200 platform, and it ships with onboard SMI-S 1.6 Provider, and no matter what I have tried I cannot get ViPR to register it.

I have also tried the Virtual VNX Simulator and I cannot get standalone SMI-S Providers on Linux or Windows to discover it either.

I did get Isilon Simulator to register in ViPR (connects directly on port 8080 without SMI-S), but one of the points of this lab is to play with the SMI-S as Isilon is not typical in EHC deployments I have seen so far.. I also wanted to take advantage of the FAST tiering feature available on vVNX if possible.

Yeah so the techs in vVNX development have indicated that this appliance is based on the VNXe 3200 so technically it should work with ViPR (I have seen the option for it in the drop-down menu in ViPR on the add storage array page), but it will not discover.

No Events found!

Top