Richard,
The firewall issue I was thinking of possibly wasn't on the Virtual Center side, but more of on the Linux side
If you review the logfile it reports in that dump - does it have any apparent reference to what exactly isn't connecting or communicating?
logStartReport(): Log Filename: /NetApp/VIBE/Report/VIBE_20080729_091209.log
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.
Hopefully this was helpful Richard,
Thanks and let us know!
Christopher