Consider moving this discussion to VNX Support Forum ( Select Move from Actions).

Are you getting any error while adding LUNs to ~filestorage ?

Tried a rescan (server_devconfig server_2 -c -s -a ) ?

how did you configure that raid group, VNX/Celerra is very particular to raid group layout. If it does not have the right number of drives, LUNs will not be detected.

thanks for your answer. rescanning the system solved the issue

I first tried in a 5+1 Raid 5 but then changed to 4+2 Raid 6 for the BP

Thanks

I couldn't help but notice that in the response you marked as correct, it only referenced server_2.  If you didn't already, it is important that all data movers have visibility to the same LUNs *including the standby*.  Seeing that you own a VNX 5300 which only supports 2 data movers, you'll also want to rerun the command to scan the standby data mover (server_3).

Now... you will probably suggest that everything is working fine; however, what you run the risk of is the data mover failover aborting if you don't also scan the standby data mover with each new LUN you present via the ~filestorage storage group.  It needs to have visibility to the same set of LUNs as all others.

On the other hand, if you were to rescan from the GUI, this will rescan every data mover for you.  Via CLI, you have to call each individually; however, that is a common theme (GUI vs CLI) that the CLI provides more granularity.  Just to mention it, in the past we supported: "server_devconfig ALL", but "ALL" is no longer supported in conjunction with "-create" (or "-c" for short). 

Via Unisphere, you could have also scanned as follows which would scan all data movers for you:

1) Storage

2) Under File Storage (along the side) > Rescan Storage Systems

Personally when I present LUNs to the data movers, my preferred order of operations is as follows (using a basic model with 2 X-Blades in a primary/standby relationship):

1) Even before I start my work (before I add the new LUNs to the ~filestorage storage group), I make sure the current configuration is healthy.

nas_storage -c -a   (short for:-check -all)

Firstly, note that it is a different command.  If it simply returns "done" then no errors were identified.  Of course if there are any errors reported (such as "Missing paths to SPA (or SPB)", you resolve those first, and you aren't left wondering if any issues that are encountered during the rescan may or may not have been preexisting issues.  Start with a healthy baseline.

2) server_devconfig server_3 -c -s -a

I personally prefer to do the rescan on the standby first.  Why?  While I don't expect issues, but let's say something did happen on the rescan and it causes the data mover to crash (yes unlikely but possible).  Well... I did the rescan on the standby data mover and there will be no interruption to production.  Only once I confirm the rescan succeeded, then I move onto the primary data mover:

3) server_devconfig server_2 -c -s -a

4) nas_storage -c -a

Okay, so it is overkill, but I like to finish it off just as I started

Thanks Chris for pointing this out. I just meant to remind the command.