VNX NAS CLI Command Reference Guide

This VNX NAS CLI reference guide includes command syntax samples for more commonly used commands at the top, and a list of available commands at the bottom with a brief description of their function. Here are some other posts on my blog that provide more specific examples of using some CLI commands, with additional detail and some scripting examples:

The commands need to be run from a control station login. You can connect directly to the control station with a terminal emulator (I use putty). There is no host agent for the celerra that’s similar to the Navipshere CLI.

Hi – we recently moved a celerra but now getting the following error messages after running the /nas_checkup script..
————————————-Checks————————————-
Control Station: Checking if NBS clients are started………………….. Pass
Control Station: Checking if NBS configuration exists…………………. Pass
Control Station: Checking if NBS devices are accessible……………….. Fail
Control Station: Checking if NBS service is started…………………… Fail
Control Station: Checking if NAS partitions are mounted……………….. Pass
Data Movers : Checking status……………………………………. ?
——————————————————————————–

NBS is the Network Block Service, which is a proprietary client/server protocol of VNX/Celerra for file that provides a block device (for example,
iSCSI device) management functionality over a TCP/IP connection. You can check the parameter by typing server_param server_2 -facility nbs -list, then check the settings for each parameter with server_param server_2 -facility nbs -info *param_name*. To be honest, I’m not at all familiar with NBS, if EMC support is available to you I’d recommend opening an SR. Sorry I can’t be of more help.

Great info — thanks for collecting! Very helpful. One suggestion — to allow people to be able to cut’n’paste, some of the commands were put into uppercase (probably an automatic “correction” by your blog software); for example, “Nas_fs”, “Server_stats”, and “Fs_group” are examples of commands not found (because of the initial capital letter). There are also 3 commands with syntax “..server_config” (two leading dots) instead of “.server_config” (one leading dot). For newbies, might have problem debugging what went wrong, and this is so wonderful I wanted to help you make it “perfect” 🙂

You can use -p in the command if you want to specify tcp, udp, icmp, or ip. It is not a required parameter. Here is the syntax: server_netstat movername [ -A {inet|inet6} ][ -a ][ -i ][ -r ][ -s ] [ -p {tcp|udp|icmp|ip} ]

Is there any command to view the domain controller which Celerra contacts for SID lookups? I am creating home folders by a tool and Celerra doesn’t find the newly created users when setting permissions and throws the error – ‘Error 1337 : Invalid SID structure’. It seems celerra doesn’t find users in the DC it contacts. Can we change the DC preference of Celerra for lookups?

It is possible to see which DC’s are being used by the Celerra. To view the current domain controllers visible on the data mover run this command:
.server_config server_2 -v “pdc dump”

That command will show you all of the domain controllers that the Celerra can see. It pulls the info from DNS. A successful connection to a DC will show a ‘Cnx=SUCCESS,DC request succeeded’ in the output. If you want to disable certain DC’s from being used, you can enable or disable a domain controller on the data mover with these commands:
.server_config server_2 -v “pdc enable=0.0.0.0” Enable a domain controller
.server_config server_2 -v “pdc disable=0.0.0.0” Disable a domain controller

With that said, I don’t believe there is a specific command to change the preference for lookups. That’s just my experience, however, there could be a way I’m not aware of. I’ll do a little research and post again if I find anything. Remember that the .server_config command is undocumented from EMC. If you decide to use it, I would recommend opening an SR before using the above mentioned commands on a production system, test it on a test/dev array first. Use the .server_config command at your own risk!

I don’t have any firsthand experience with the issue you’re having so I can’t say for certain that setting those parameters will help, but on the surface it does look like you’d be ok to do it. I of course don’t work for EMC so you’d need to contact them for assurance that it won’t cause another problem. I read that that changing those parameters will trigger SID-to-Name lookup attempts to the Domain Controller for any orphaned SID detected, which could cause performance problems between the Celerra and the DC, so be warned.

So in this example I wanted to add /exports/usr/how/ace to the /ace/path1 filesystem. After many attempts I found out that I can not have the initial “/” in the command. I couldn’t find this in any documentation and it was trial and error until I figured it out. Perhaps this is common knowledge but just thought I’d share.

– The source file system MUST be mounted Read-Only (what’s easier is to create a checkpoint of the FS)
– The destination file system:
….. MUST be the same size or larger than the source file system.
….. MUST also be mounted Read Only
– The ReplicatorV2 license must be enabled for nas_copy to work, that is, nas_license -create replicatorV2.

Thanks. Use nas_disk -list to view the connected LUNs. The fifth column in the output is a dash with a four digit number. This number is a hexadecimal representation of the Clariion/VNX LUN (for example, 021D = LUN 541).

What’s Happening i am new to this, I stumbled upon this I have
found It absolutely useful and it has helped me out loads.
I hope to give a contribution & aid different customers like its aided me.
Great job.