Slowly I am getting frustrated and a bit desperate...
This is the infrastructure:
[Virtual Center Server]-172.22.8.209 ----- 172.22.8.212-[ESX]-192.168.8.212 ------ 192.168.8.130-[FAS3020]-172.22.8.130-
So: we use a dedicated "Server LAN" (192.x.x.x), but the FAS3020 has also a connection to 172.22.8.0/24, the ServiceConsole Port of the ESX is 172.22.8.212
Now: if I issue on the VCenter server
cmd>rsh filername -l root:passwd version -b
I get the answer from fiilername.
Tracing the connection with pktt on the filer I can clearly see the rsh communication.
When starting vibe.exe with default ZAPI-protocol, I get the error:
ERROR: ZAPI connection to 172.22.8.130 failed!
thats why we try protocol rsh.
When running vibe with protocol rsh, then I get:
[12:08:33] Ping of storage appliance 172.22.8.130 successful.
[12:08:33] Testing shell login to storage appliance 172.22.8.130 ...
[12:08:33] Running remote shell command: version -b ...
[12:08:33] ERROR: Running 'version -b' failed: 512
Exiting with return code: 11
11 means. A NetApp API initialization call failed. Confirm the --sauser and --sapasswd options are correct
but the given sauser (root) und sapasswd are correct!
Tracing the packets on the filer shows, that there is no rsh connectin coming in.
Using wireshark on the VCenter server shows, that there is *no outgoing rsh* session!!! Yes: no single packet with proto rsh leaves the server... instead I see a lot of sslv3 traffic between VCenter server and the filer - no clue, what the systems are talking...
maybe the attached logs, used config and this description takes us a step further.
Thanks to everyone.
Markus