scp transfer of config.ini takes 45 seconds or more

[rcjacobson]

I have about a dozen APC devices, some NMCv2, some v3.  I want to track changes to the config.ini over time by periodically transferring them to a config management system.

On most of the systems, it takes about 5 seconds to transfer the config.ini file.  But for two systems (both are Smart-UPS SRT 5000 with NMCv2), it takes 45 seconds or more to transfer that file.  I can transfer over files (e.g. db/hw.dat) quickly -- it's only the config.ini that is slow.  Maybe there's a configuration issue?  DNS?  If it's DNS I can't figure out why; the configured DNS server is correct.  

I've already tried rebooting the management interface.

Additional info: 

When I attempt to transfer config.ini, there's approximately 20 seconds after entering the password before it starts to transfer the config.ini.  Then it takes 20+ seconds to actually transfer the file.   The login delay does not occur when transferring hw.dat.

Here's the "about" info:

apc>about
E000: Success
Hardware Factory
---------------
Model Number:           AP9537SUM
Serial Number:          5A1935XXXXXX
Hardware Revision:      05
Manufacture Date:       08/27/2019
MAC Address:            28 29 86 26 2F 00
Management Uptime:      0 Days 1 Hour 45 Minutes

Application Module
---------------
Name:                   sumx
Version:                v7.1.2
Date:                   Mar 21 2023
Time:                   17:44:20

APC OS(AOS)
---------------
Name:                   aos
Version:                v7.1.2
Date:                   Mar 21 2023
Time:                   17:34:00

APC Boot Monitor
---------------
Name:                   bootmon
Version:                v1.0.9
Date:                   Mar 27 2019
Time:                   16:23:06

[Shaun]

Hi,

Most of the files on the NMC are actually generated on-the-fly, they're only presented as files on a disk for the benefit of file-transfers.  This means reading (and writing) config.ini can take different amounts of time on different systems as it's actually all subsystems of the interface extracting their running configuration, rather than just reading a file from storage.

[dpierce4776]

To branch off of what @Shaun stated. When you try to push or pull the config.ini file from/to a device the device also verifies all the information on the config with its current settings. So if you pull it the device makes sure everything is correct then sends the file. If you a sending a config.ini file to a device it searches the file for any changes from the current running config. Makes the changes then says it competed the transfer.  

[rcjacobson]

OK, I'm not expecting it to be instant, but a 10-fold difference from the other models is suspect.

Transferring the file via HTTPS is ~20 seconds.  There doesn't seem to be a delay from clicking the button until the transfer starts (unlike the SCP transfer).  i.e. the transfer time is about the same, but for SSH there's a long pause before the transfer even starts.