Unsolved
This post is more than 5 years old
26 Posts
0
1818
October 21st, 2015 09:00
Storage Provider: Delete Not Allowed (want to use host name/FQDN instead of IP)
Using VIPR Controller v2.3.0.1.846, discovered Storage Provider using its IP address rather than FQDN.
I added the same provider_2, using the FQDN, now I have TWO Storage Providers for the same SMI-S server (one IP, one FQDN).
When I try to delete instance 2, the warning is: Delete not allowed. Please remove all dependent storage systems before attempting to remove a Storage Provider.
I have de-registered them, but time last time I deleted arrays from VIPR Controller, they were not discoverable again and I had to redeploy the OVF.
There is a vArray using the storage systems, but it is not in production.
Is the Remove request to remove them from ECOM (DV, remsys) or is it remove from VIPR C?
julien3192
38 Posts
0
October 22nd, 2015 05:00
I think we could modify the VIPR Database so it has the FQDN (never tested it but it should work!).
Andrew291
92 Posts
0
October 23rd, 2015 07:00
You probably could have just edited the provider discovery and changed the ip to fqdn but another suggestion that was brought up was shutting down the provider and then trying to remove one of the smi-s providers since only one would be primary at this point. Turning it back on would give it primary again and allow you to manager arrays or change name if needed.
Dbutils can also be used to remove arrays at command line level of ViPR. This removes it fully if necessary so ViPR can bring the arrays back again.
You would have to use ./dbutils delete DecommissionResource to get it back.
supersandwhich
26 Posts
0
April 6th, 2016 10:00
Storage Provider: Delete not allowed. Please remove all dependent storage systems before attempting to remove a Storage Provider.
What worked: logon to the Storage Provider/SMI-S server, cd ECIM\ECOM\bin sm_service stop ecom.exe
testsmisprovider, DV, see connect stopped, (no arrays)
go to VIPR\Physical Assets\Storage Providers - refresh, see no arrays, now you can delete the storage provider.
issue a sm_service start ecom.exe and DV again
What did not work - ,shutting down the HBA ports off in the switch to cut access to the gatekeepers
what also removes an array (not recommended): REMSYS in ecom - yes it will remove the array from the Storage Provider, but I have not found a way to get it back (addsys + ???).
julien3192
38 Posts
1
April 8th, 2016 05:00
You cannot delete a SMI-S Provider if it is the only one able to manage a Storage System. You need a new active/discovered provider in VIPR before you can delete the old and offline one.
Be very careful with remsys which is not recommended when using VIPR, especially with VNX arrays !
You will lose all the "Consistency Group" information (if you use CG in VIPR) for the managed VNX, and the only way to recover this info is addsys+restoring the symapi_db file+ECOM restart....
supersandwhich
26 Posts
0
April 12th, 2016 12:00
Hi Julian and thank you:
To clarify, there were multiple instances of the *same* SMI-S provider host in Storage Providers, but with variations of name. When I logged onto that host and stopped SMI-S using the command line, the associated arrays disappeared and I was able to delete the extra instances of that host.
This is a lab deployment right now, fortunately, but I agree, caution is required and not to do anything you don't know what the consequences are! We will be cycling things in and out of our data center, and thus VIPR, hoping to learn how to do this prior to a larger deployment.