NSH client Sets the maximum number of seconds that a client waits when first contacting a remote server before giving up. The default value is 30 seconds. Without this option, the TCP protocol might continue to contact an offline or unavailable server for several minutes before finally giving up and reporting that a server is unavailable. This timeout mechanism is implemented within the BMC Server Automation code and does not in any way alter any system wide TCP parameters. If the operating system has an effective TCP timeout less than the value defined here, the OS value takes precedence.
that may help if the problem is connecting to the server. if it's stuck in the command execution you might want to nexec your command and have it write to a log file and then background it. you can scrape the log to look for completion or look for the pid or something like that. do that in a loop and exit the loop on completion or on a counter.