I'm quite sure this isn't a firewall issue because I can connect fine from my Windows laptop. I can SSH fine to the ESX servers but VIBE needs a connection to the Virtual Center server. Here's the output from the script with debugging and verbose:
# ./vibe-1.0.3.pl --verbose --debug --backup --vcip 10.254.20.59 --vcuser Administrator --sauser root --ds MC-PROD-DATA-01 --saip 10.254.20.200 Perl module NaServer (ZAPI) not available, --protocol rsh required. Perl module NaErrno (ZAPI) not available, --protocol rsh required. logStartReport(): LOG REPORT FOR VIBE logStartReport(): ----------------------------------------------------- logStartReport(): VIBE Version: 1.0.3 logStartReport(): Log Filename: /NetApp/VIBE/Report/VIBE_20080729_091209.log logStartReport(): Backup Start Time: Tue Jul 29 09:12:09 2008 runCheckArgs(): WARNING: --vcpasswd not defined on command line. Enter password for Virtual Center 10.254.20.59, user Administrator: runCheckArgs(): WARNING: --sapasswd not defined on command line. Enter password for storage appliance(s) (username for all: root): runCheckArgs(): Datastore(s) selected: MC-PROD-DATA-01 runCheckArgs(): Datastore snapshot prefix will be used (VIBE_ds_snap). runCheckArgs(): Command line arguments successful. runLogin(): Initializing connectivity to Virtual Center and storage appliances. runLogin(): Converting Virtual Center hostname to IP address ... runLogin(): Attempting to ping Virtual Center 10.254.20.59 ... runLogin(): Ping of Virtual Center 10.254.20.59 successful. runLogin(): Testing login to Virtual Center 10.254.20.59 ... runLogin(): ERROR: Virtual Center login failed -- check authentication and firewall settings! runExit(): Exiting with return code: 16
If I were in this same situation (trying to trace out this issue) I'd either sniff traffic or confirm which ports my host was attempting to connect remotely on - so as to be able to validate if it my specific host who is having a problem connecting on a port/protocol, or if I am experiencing a failure of the script itself.
Then given that, if it isn't a connection issue - we could find out whether we might be having a Perl issue with a specific module used for this.
My thought would be, that if we're experiencing a specific issue with a module, it might be bound to the "SoapFault" function, which is also referenced with the vmware script "vminfo.pl" and in a worst case scenario - testing if that script works (or fails) would be a good way to validate that particular function.
Being that we have one host (Windows) which works, and one (Linux) that does not, initially it tends to look like a host-bound issue on the Linux side.
The log file contains exactly what I posted from running the script with the verbose option, above. tcpdump shows HTTPS traffic in both directions between VIBE and the Virtual Center server. Running vminfo.pl works fine with the same credentials...
We've seen this be a problem in a couple of cases with using the wrong VI Perl Toolkit. If you aren't using 0.9 or 1.0 (preferably 1.0) then this would happen. If you try to use 1.5 you will likely have problems.
There's a new version coming out very shortly (1.0.4) which will have the 1.5 VI Perl Toolkit support included. In the meantime, you can get the 1.0 VI Perl Toolkit from: