SMARTS NCM: how to increase the delay for transferring the OS image during an upgrade job?
search cancel

SMARTS NCM: how to increase the delay for transferring the OS image during an upgrade job?

book

Article ID: 331122

calendar_today

Updated On:

Products

VMware Smart Assurance

Environment

VMware Smart Assurance - NCM

Resolution

During an upgrade job, if the new OS image is quite big, NCM may timeout during the transfer.

The following can be seen in the logs:

Line 25502: Sep 16 13:07:04 966715712/softwareUpdate(67490)#3: ++++++++++++++++++++
Line 25503: Sep 16 13:07:04 966715712/softwareUpdate(67490)#3: ...o/ios/filemgmt.inc#414: ERROR > expect(session,timeout,expectPrompts);: TermSession::expect: timeout occurred (TermSession.cpp#169)
Line 25504: Sep 16 13:07:04 966715712/softwareUpdate(67490)#3: Variables:


To avoid this scenario, you can increase the timeout from default 3 minutes in the custompackage folder of the device vendor.

For example with Cisco below:

In the following path- $VOYENCE_HOME/custompackage/cisco/ios/filemgmt.inc look for the line below and make the change from 180 to 360 (or whatever value you need).

If there is no filemgmt.inc in the $VOYENCE_HOME/custompackage/cisco/ios/ directory please copy it and the complete path from the $VOYENCE_HOME/package/cisco/ios/ directory. 

expect(session,180,FileXfrProgres+s","ession,180,FileXfrProgress+","+FileXfrOk+","+FileXfrError+","+stdEnablePromptState);

This will require a restart of the device server.