plink is most likely not sourcing the 'nasadmin' account environment. When you ssh as the user and invoke the shell, this invokes the environment. Your best bet is to try the full path, in this case, /nas/bin/nas_version.
If you're going to use other scripts, you can always check the path to the command with which:
I am working on automation of celerra basic health check and identifying file systems that have crossed 80% and send a email. I am able to establish ssh session using python with paramiko module. When I run the command
I am getting error "bash shell cannot understand command". I am not using nasadmin user, I have created a new user with operator role. When I directly putty control station, I am able to run the commands.
umichklewis
3 Apprentice
•
1.2K Posts
0
August 11th, 2014 09:00
plink is most likely not sourcing the 'nasadmin' account environment. When you ssh as the user and invoke the shell, this invokes the environment. Your best bet is to try the full path, in this case, /nas/bin/nas_version.
If you're going to use other scripts, you can always check the path to the command with which:
[nasadmin@vnx-test1 ~]$ which nas_version
/nas/bin/nas_version
Let us know if that helps!
Karl
sangal1983
1 Message
0
August 6th, 2020 09:00
Hi,
I am working on automation of celerra basic health check and identifying file systems that have crossed 80% and send a email. I am able to establish ssh session using python with paramiko module. When I run the command
I am getting error "bash shell cannot understand command". I am not using nasadmin user, I have created a new user with operator role. When I directly putty control station, I am able to run the commands.
Could you please help me resolve this issue.
Regards,
Ranganath Sangal