This post is more than 5 years old

2 Intern

 • 

356 Posts

10107

July 18th, 2014 07:00

VNX CLI... Commands not running

Hey,

I am having a problem running the commands that suppose to work while logged into the CLI for the VNX.  None of the commands appear to work... i.e

[nasadmin@xxxxxxxx ~]$ environment -list -all

-bash: environment: command not found

I checked the PATH, and to be honest I am not sure what the PATH should be:

when I logged in as nasadmin the PATH is the follow:

PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/nasadmin/bin:/nas/bin

when I logged in as root the PATH is the follow:

PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin

Am I looking in the right place for why non of the commands are running?  Please help.

Thank you,

9 Legend

 • 

20.4K Posts

July 18th, 2014 09:00

there is not such command as "environment", if you want to talk to VNX backend from the control station you must use naviseccli

/nas/sbin/naviseccli -h environment -list -array

3 Apprentice

 • 

1.2K Posts

July 18th, 2014 09:00

It's not just your path, there are certain environment variables that are parsed, to run some of the CLI commands.

Can you tell us which commands you're trying to run?  Are you running them directly from the CLI?  Or, are they running inside of a cronjob or script?

As dynamox posted, you'll need to run commands within naviseccli with the full path.  There's no naviseccli "shell" that you can run commands from, you have to use the full string and options.

You might also look into the NAS XML API in the Programmer's Guide, to provide more examples of command syntax and scripting.

Hope this helps!

Karl

2 Intern

 • 

356 Posts

July 18th, 2014 10:00

You guys mind adding a link to this docs?  I always seem to find the wrong guide for all the CLI commands.  But to answer your question... I am running the command directly from the CLI.

2 Intern

 • 

356 Posts

July 21st, 2014 04:00

Guys, again I did and every guide I download and try and run the example commands from they don't seem to work.

https://support.emc.com/docu41553_VNX-Command-Line-Interface-Reference-for-Block.pdf?language=en_US

I ran this command on page 377 and this was the output:

[nasadmin@ ~]$ naviseccli cache -fast -info

-bash: naviseccli: command not found

So can someone please help me find a version of the Command Line interface Reference guide for block that will work for my VNX?

FYI...EMC VNX Control Station Linux release 3.0 (NAS 7.1.56)

Thank you,

4 Operator

 • 

8.6K Posts

July 21st, 2014 04:00

Just go to support.emc.com and get both of the “command line reference guide” for VNX

9 Legend

 • 

20.4K Posts

July 21st, 2014 05:00

if you are going to run command from the control station, all commands have to start with /nas/sbin

ie: /nas/sbin/naviseccli cache -fast -info

or add /nas/sbin to your $PATH (use google to figure how to do that)

9 Legend

 • 

20.4K Posts

July 21st, 2014 08:00

no you don't have to put the entire path

[nasadmin@vnx5700 ~]$ export PATH=$PATH:/nas/sbin

[nasadmin@vnx5700 ~]$ naviseccli -h 10.230.66.19 getagent

Agent Rev:           7.32.26 (0.95)

Name:                K10

Desc:               

Node:                A-APM00112300000

Physical Node:       K10

Signature:           3283987

Peer Signature:      2965662

Revision:            05.32.000.5.206

SCSI Id:             0

Model:               VNX5700

Model Type:          Rackmount

Prom Rev:            8.50.00

SP Memory:           18432

Serial No:           APM001123000000

SP Identifier:       A

Cabinet:             SPE5

2 Intern

 • 

356 Posts

July 21st, 2014 08:00

Yep,  I opened a ticket with support.  Evidently I have to put the entire path in order for the command to run... regardless of the path being set in ENV.  That sort of sucks, but it is what it is.

Thank you,

9 Legend

 • 

20.4K Posts

July 21st, 2014 09:00

modify .bash_profile if you want that to be added everytime you login.

2 Intern

 • 

356 Posts

July 21st, 2014 09:00

dynamox,

ok i will try this.

Thank you,

2 Intern

 • 

356 Posts

July 21st, 2014 09:00

Dynamox,

It my original ENV setting are /usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/nasadmin/bin:/nas/bin

then my new settings should be:  /usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/nasadmin/bin:/nas/bin:/nas/sbin ?

Correct?

9 Legend

 • 

20.4K Posts

July 21st, 2014 10:00

vi .bash_profile

find this line

PATH=$PATH:$NAS_DB/bin

make it look like this

PATH=$PATH:$NAS_DB/bin:/nas/sbin

save the file, log off and log back in

4 Operator

 • 

8.6K Posts

July 22nd, 2014 04:00

Not entirely

Most commands that are meant to be used by normal customer administrators in the nasadmin context are in /nas/bin

Commands in /nas/sbin are typically very frequently used during installation or by customer service (often need root).

For these we assume that user is familiar with Unix. They aren’t in the default path by design.

Rainer

9 Legend

 • 

20.4K Posts

July 22nd, 2014 06:00

fair enough but remember not so long time ago you had to run setup_clariion to provision space on a Celerra box. Sounds like a typical task for any Celerra system admin yet it resides in /nas/sbin . I know where you are coming from, there are different users with different comfort levels when it comes to the CLI.

4 Operator

 • 

8.6K Posts

July 22nd, 2014 06:00

Hi dynamox,

yes – but when setup_clariion was introduced it was for EMC personal – at that time a Celerra wasn’t customer installable – you always had to include professional service for implementation

Rainer

No Events found!

Top