SSH , Powershell , VNX???

scottbrindley · 2016-12-19T15:08:13.000Z

I am working on way to script the process of shrinking a CIFS share on VNX, which means creating a new smaller share; copying data from the old to new ; un-mounting the filesystems ; renaming the files systems ; deleting the old and mounting the new.

I know there is a Powershell Module for EMC but this needs to be able run from a Win 7 PC, so have found away of doing this by importing a SSH module into PS then connect to the VNX. I have accomplished this but when I try to list file pools it fails.

The code I have used is :-

$SshResults = Invoke-SshCommand -InvokeOnAll -Command ‘uname -a’ - This work and show details of the connection and works.

$SshFiles = Invoke-SshCommand -ComputerName $CSIP -Command /nas/sbin/nas_fs - This fails with this message ‘had an error:bash: /nas/sbin/nas_pool: No such file or directory’

If you use /nas/bin/nas_fs or /nas_fs you get the same error.

If you add -list -all parameters you get Invoke-SshCommand : A parameter cannot be found that matches parameter name ‘list’

If you try ‘/nas/bin/nas_pool -list -all’ , you receive this error ‘had an error:bash: /nas/sbin/nas_pool: No such file or directory’

mattmcnabb · 2016-12-19T15:16:46.000Z

Any reason why you can’t run the module on your Windows 7?

Also, please remember to use the code button as described in the forum sticky post when posting code here:

codebutton.png800×628 90.4 KB

scottbrindley · 2016-12-19T15:23:24.000Z

The EMC module on runs on x64 hardware , we have it installed on server but for DR purposes it needs to be able to run from a standalone computer.

mattmcnabb · 2016-12-19T15:27:06.000Z

Not sure how much help I can offer, but maybe this will clarify a bit?

$SshFiles = Invoke-SshCommand -ComputerName $CSIP -Command /nas/sbin/nas_fs -  This fails with this message 'had an error:bash: /nas/sbin/nas_pool: No such file or directory'

This is an error returned from bash and so I’m not certain if anyone in this forum will be able to help troubleshoot this portion of your question.

If you add -list -all parameters you get Invoke-SshCommand : A parameter cannot be found that matches parameter name 'list'

This happens because Powershell is interpreting these as parameters to Invoke-SshCommand - there’s nothing to let it know that this should be part of the bash command.

If you try  '/nas/bin/nas_pool -list -all' , you receive this error  'had an error:bash: /nas/sbin/nas_pool: No such file or directory'

Back to the first one - this is returned by bash so you may need to troubleshoot exactly why this command isn’t working, but I’m not certain this is actually a PowerShell issue.

mattmcnabb · 2016-12-19T15:30:50.000Z

scottbrindley:

The EMC module on runs on x64 hardware , we have it installed on server but for DR purposes it needs to be able to run from a standalone computer.

Is this the module?

https://community.emc.com/docs/DOC-8561

It states it’s available for both windows 7 architectures. Sorry if this is not the right documentation - I’m not familiar with the EMC module at all.

EDIT: Sorry, I think I found it here:

https://community.emc.com/docs/DOC-17664

It does say that it requires x64 architecture - maybe it would be simpler to find a 64-bit machine to run this from?

scottbrindley · 2016-12-20T08:54:26.000Z

That’s the one , this is the error you get when installing it on a x64 Win 7 machine. I would use navisphere cli but this doesn’t do all I need.

mattmcnabb · 2016-12-21T02:19:49.000Z

scottbrindley:

That’s the one , this is the error you get when installing it on a x64 Win 7 machine. I would use navisphere cli but this doesn’t do all I need.

Interesting… The PDF from that link doesn’t state that the powershell toolkit has to be installed on a server OS. It just says Windows x64

scottbrindley · 2016-12-21T08:42:35.000Z

I know , that’s the frustrating part hence why I took this path.

scottbrindley · 2016-12-23T13:07:09.000Z

Look at , I need to get Powershell to tell Bash to change directories in order to be able to execute the relevant VNX commands.