cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
87
Views
2
Helpful
6
Replies
Highlighted
Cisco Employee

StarOS copy command

 

Hi folks,

 

 

I’m trying to execute an FTP image copy into a StarOS device and ran into an issue that relates to the length of the copy command.

 

 

From the NCS-CLI below it looks like the command fails and I see a read-timeout when the file-path is long but succeeds when the path is short.

 

So the question is:

 

    • Is the command waiting for a user prompt and then times out?  Or

    • Is there a limitation in the length of the copy command / filename?

 

Irrespective of the above, the command seems to work when run from the device as shown below. So looks like this is a limitation in the NED.

 

Has anyone experienced this issue in the past? Appreciate your inputs.

 

 

From NSO-CLI:

 

 

admin@ncs# devices device vpc live-status exec copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2 /flash/production.20-2.64719.qvpc-si.qcow2

 

Error: Network Element Driver error ned_cmd for device vpc: read timeout

 

admin@ncs# devices device vpc live-status exec copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2 /flash/qvpc-si-20-2.qcow2

 

Error: Network Element Driver error ned_cmd for device vpc: read timeout

 

admin@ncs# devices device vpc live-status exec copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/qvpc-si-19.3.4.63957.qcow2 /flash/qvpc-si-19-3.qcow2        

 

Error: Network Element Driver error ned_cmd for device vpc: read timeout

 

admin@ncs#

 

admin@ncs# devices device vpc live-status exec copy ftp://giri:cisco123@10.84.46.64/home/giri/qvpc-20-2-si.bin /flash/qvpc-20-21-si.bin

 

result

 

Wednesday August 24 21:27:05 IST 2016

 

********************************************************************************

 

Transferred 132205056 bytes in 0.001 seconds (129106500.0 KB/sec)

 

 

 

From Device:

 

 

[local]NOI-S57-SPG-03# copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2 /flash/production.20-2.64719.qvpc-si.qcow2

 

Wednesday August 24 22:39:24 IST 2016

 

********************************************************************************

 

Transferred 141033472 bytes in 0.001 seconds (137728000.0 KB/sec)

 

 

NSO Trace:

 

 

-- Found staros device --

 

<< 24-Aug-2016::12:11:40.013 CONNECTED 0

 

>> 24-Aug-2016::12:11:40.017 IS_ALIVE 0

 

<< 24-Aug-2016::12:11:40.019 IS_ALIVE true

 

>> 24-Aug-2016::12:11:40.019 COMMAND copy([{['http://tail-f.com/ned/cisco-staros-stats'|

 

  args],

 

  [<<"ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2">>,

 

  <<"/flash/production.20-2.64719.qvpc-si.qcow2">>]}])

 

-- command(vpc) - copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2 /flash/production.20-2.64719.qvpc-si.qcow2 --

 

autoconfirm

 

 

  *** input 24-Aug-2016::12:11:40.078 ***

 

autoconfirm

 

Wednesday August 24 22:41:19 IST 2016

 

[local]NOI-S57-SPG-03#

 

 

  *** output 24-Aug-2016::12:11:40.078 ***

 

copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2 /flash/production.20-2.64719.qvpc-si.qcow2

 

 

  *** input 24-Aug-2016::12:12:12.249 ***

 

copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2 /flash/prod

 

  1. uction.20-2.64719.qvpc-si.qcow2

 

Wednesday August 24 22:41:19 IST 2016

 

********************************************************************************

 

Transferred 141033472 bytes in 0.001 seconds (137728000.0 KB/sec)

 

<< 24-Aug-2016::12:12:12.250 ERROR: Network Element Driver error ned_cmd for device vpc: read timeout

 

>> 24-Aug-2016::12:12:43.179 CLOSE 0: (Pool: discard)

 

<< 24-Aug-2016::12:12:43.180 CLOSED

 

 

 

6 REPLIES 6
Highlighted
Cisco Employee

 

What are your timeouts ?? If you look at the timestamps in the NSO trace,  NSO sent the command, but it was 32 seconds before the command was echo’ed back to NSO from StarOS? If your timeouts are set to 30 seconds, you might try increasing to 60 seconds or more just as a test?

 

 

  *** output 24-Aug-2016::12:11:40.078 ***

 

copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2 /flash/production.20-2.64719.qvpc-si.qcow2

 

 

  *** input 24-Aug-2016::12:12:12.249 ***

 

copy ftp://giri:cisco123@10.84.46.64/var/www/html/vpc/images/upgrade/production.20-2.64719.qvpc-si.qcow2 /flash/prod

 

uction.20-2.64719.qvpc-si.qcow2

 

Highlighted
Cisco Employee

 

Chris,

 

 

I set the device timeout to 100s & still the same.

 

The weird thing is that the file is copied over from the FTP server.. I see it on the device flash…Just that the NSO cli prompt doesn’t return back & times out.

 

 

Thanks,

 

Giri

Highlighted
Cisco Employee

 

My next guess would be the CRLF that is inserted into the response. Can you set the terminal width in StarOS to something larger or is that specific to an SSH session? Or some other way to make it not wrap onto new line?

 

  Chris Clark

Highlighted
Cisco Employee

 

 

Hi,

 

 

We are using NED 4.2.2:

 

 

admin@ncs# show packages package package-version

               PACKAGE

NAME          VERSION

----------------------

cisco-staros  4.2.2

admin@ncs#

 

 

Highlighted
Cisco Employee

 

Umm, strange...

 

But as far as I checked the code, if you use 4.2.2 you should see this format
in the trace log:

 

-- Found staros device: version = 15.0 (54314) --

 

What you pasted looks like from 4.2 or older.

 

-- Found staros device --

  Regards,
Tomo

Highlighted
Cisco Employee

 

Tomonobu / Chris,

 

 

You were right. This issue IS fixed in the new StarOS NED v4.2+

 

The problem was with the CDB where it still seemed to have a reference to the older StarOS NED even though the “show version” command was showing v4.2.2

 

I wiped out my CDB and now the read-timeout issue is no longer happening and the copy is successful.

 

 

Thanks for your inputs.

 

Content for Community-Ad
Cisco Community October 2020 Spotlight Award Winners
This widget could not be displayed.