what is the meaning of (timeout 30) when commit executed

[Fumiaki Tsuzuki]

Hi Experts,

I have a quick question regarding (timeout 30) and how it work during commit operation.

When I committed something with IOS NED, I encountered the below "Read timed out" error.

I think this timer came from "read-timeout 20" which is set on global-setting or device setting.

But, NSO seems to have the other timeout like (Timeout 30), what is the meaning of this timer? and how it works?

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

  *** output 13-Mar-2018::07:41:56.407 ***

-- DONE APPLY-CONFIG [7080 ms]

<< 13-Mar-2018::07:41:56.408 PREPARE OK

>> 13-Mar-2018::07:41:56.408 COMMIT 3: (Timeout 30)

-- BEGIN COMMIT

write memory

  *** input 13-Mar-2018::07:41:56.447 ***

write memory

Building configuration...

<< 13-Mar-2018::07:42:16.511 ERROR: External error in the NED implementation for device cisco-sw: Read timed out

>> 13-Mar-2018::07:42:16.531 CLOSE 3: (Pool: false)

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

Thanks,

Fumiaki

[frjansso]

I would think that would be the write timeout (/devices/device/write-timeout or /devices/global-settings/write-timeout or /devices/profiles/profile/write-timeout). Do you have any of the above set?

The timeout is simply the time the NED allows the device to take to "persist" the config changes... so for example, in some cases the "write mem" takes considerable time (minutes), you have to up this value.

[Fumiaki Tsuzuki]

Thanks Fredrik,

I didn't set any timer for "connect-timeout", "read-timeout", "write-timeout".

These values seems to be 20sec as default.

Do we have any command to change NED timeout value?

Thanks,

Fumiaki

[frjansso]

To set e.g. write timeout for a specific device, e.g. ios0:

config mode

Cisco cli: devices device ios0 write-timeout 120

J-style: set devices device ios0 write-timeout 120

commit

[Fumiaki Tsuzuki]

I changed these values to 60, and it seems to work fine, but COMMIT timeout seems not to be changed.

So, I think write-timeout and Commit timeout might be different.

From ned.trace

----------

<< 26-Mar-2018::02:16:43.839 SET_TIMEOUT

-- connect-timeout 60000 read-timeout 60000 write-timeout 60000

~snip~

Z09-3850-1#

<< 26-Mar-2018::02:16:46.157 PREPARE OK

>> 26-Mar-2018::02:16:46.158 COMMIT 0: (Timeout 30)

----------

Thanks,

Fumiaki

[frjansso]

According to the doc:

write-timeout: "The timeout in seconds used when writing data to a managed device.";

Is it still a problem, I'm thinking that it might be an error in the log... if it still doesn't work, i.e. that the timeout is actually still 30 secs, let me know.

Please note though that all these timeouts are in seconds, so 60000 seconds is a loooong time

[Fumiaki Tsuzuki]

My customer wants to know the meaning of the below output on ned.trace.

>> 26-Mar-2018::02:16:46.158 COMMIT 0: (Timeout 30)

Can we say to ignore this value?

I thought write-timeout may be just used not only for COMMIT but also any "writing action", so that this value set to 20sec as default.

By the way, ned.trace seems to show this value with msec order, so it showed as 20000 msec.

NED commit action include several steps like read device data, change device config, save config, etc.

I guessed (Timeout 30) is related for entire commit process.

Thanks,

Fumiaki