procedure to delete and recreate storage pools

did you create any file systems ? If not you can use "nas_disk -l" to list all devices Celerra knows about. There should be an "n' in the "inuse" column. You need to delete these disks first (except the ones the say root_disk): nas_disk -delete [[-perm]|[-unbind]]. This command will delete these disks from Celerra and unbind them in Navisphere.

See this pdf for supported configuration for NX4

http://corpusweb130.corp.emc.com/ns/common/post_install/Configure_storage_Non_FC.pdf

delete simply deletes them from Celerra perspective, at this point you can go into Navisphere and unbind them manually ...or you can append -unbound to nas_disk command which will also unbound them in Clariion.

Ok. So I did the nas_disk -l and saw all my disks, with exception of the first 6 were N for "in use".   I did a nas_disk -delete d7 -perm and then d8 etc.. until I removed all the non-used disks.

I ran the disk provisioning wizard again and it immediately completed all the tasks and never asked me to configure anything.  I did another nas_disk -l and all the non-used disks were back.  I repeated the nas_disk -delete again and cleared them out.

I went into Navisphere express and my disk pools were still there so I go rid of there, except for Disk Pool 1.  I then re-ran the disk provisioning wizard and it again immediately completed the process.

What am I missing here?  Do I need to do the -unbind too?  I thought the -perm deleted and did unbind.

After I deleted the disk pools and it ran through the provisioning wizard quickly the second time, the disks were showing as 'unbound' in the hardware screen on Unisphere.

I ran the provisioning wizard again and it came up correctly this time and allowed me to configure how I wanted the disks provisioned.  I proceeded and it is now Successful on the 'Verifying Config' and 'Configuring Storage'.   Its on the 'Binding' section with 4 hours and 59 seconds left.   Seems alot longer than when I did it the first time.   I hope there is nothing wrong.  No errors as of yet.

when you bind LUNs for the very first time it's called fast-bind , if you delete and re-create RG/LUNs ..it's going to be a regular bind operation but that should not stop you from using the storage.

That is normal - Binding a disk for the first time uses quick-bind which is faster

fast bind ..not quick bind