Nimbostratus"Initialize-F5.iControl" command in Powershell times-out and is unusable. Logging in through the web interface is slow as well but eventually succeeds. We need to use Powershell for our automation, how can I extend the timeout period in Powershell ?
Currently the timeout is controlled by the lower level .Net web service proxy code generated by the .wsdl files. Essentially the PowerShell library is just a wrapper around the iControl library for .Net and I don't believe it's exposed there.
I'll dig into the source and see if I can get the tcp connect timeout exposed to the external API and if so, try to get a patch build put out.
I'll keep you posted...
-Joe
