Dell N3028P copying running-config can take a long time.

Hello, I'm not sure what causes that. Maybe if the CPU and memory usage is heavy, it may affect this time. Maybe you can check its usage with these commands'
syntax
show process cpu
show memory cpu

pg2236-2243 https://dell.to/3RJOqY7

Regards,

Sorry I meant to post that as I had checked that. What I found is 1452 openSyncTask 44.63% 44.15% running very high especially for a switch not in production with nothing on it. I have plenty of these models in our enviornment and most of the time they run between 7-10% percent load. 

console#show process cpu

Memory Utilization Report

status KBytes
------ ----------
free 259620
alloc 772832

CPU Utilization:

PID Name 5 Secs 60 Secs
---------- ------------------- -------- --------
3 (ksoftirqd/0) 0.09% 0.04%
18 (kworker/0:1) 0.00% 0.02%
1088 (procmgr) 0.09% 0.09%
1208 osapiTimer 0.00% 0.03%
1212 socdmadesc.0 0.48% 0.25%
1213 bcmMEM_SCAN.0 0.00% 0.03%
1215 bcmIbodSync.0 0.00% 0.07%
1216 bcmL2X.0 3.79% 3.63%
1217 bcmCNTR.0 1.84% 1.50%
1222 bcmRX 0.00% 0.02%
1236 bcmLINK.0 0.58% 0.60%
1237 cpuUtilMonitorTask 0.19% 0.13%
1283 hapiBroadBufferUsag 0.09% 0.05%
1286 hapiBroadBfdCtrlTas 0.00% 0.08%
1325 snoopTask 0.00% 0.08%
1385 openrTask 0.48% 0.53%
1432 RMONTask 0.00% 0.05%
1451 StatsAppTask 0.19% 0.19%
1452 openSyncTask 44.63% 44.15%
1492 poeRead.0 0.00% 0.02%
1530 poe_monitor 0.00% 0.03%
------------------------------ -------- --------
Total CPU Utilization 52.51% 51.79%

Hi, As I can see your FW is up to date. Whilst I was researching I encountered a similar discussion on this thread https://dell.to/3QsoO0M Apart from that I couldn't find anything about that. That is interesting I would expect this process fast after the factory reset. Let's see how to community contributes.

Thanks. I reloaded the firmware image and updated the cpld again and the task that was running high seems to have resolved itself. Times for the copy have improved it only took 12 minutes this time just adding some basic information into the switch like name and contact but far from the norm. Not sure I trust this switch in production so it might just stay as a lab switch unless I can slove the issue. 

LABSWITCH#show process cpu

Memory Utilization Report

status KBytes
------ ----------
free 231080
alloc 801372

CPU Utilization:

PID Name 5 Secs 60 Secs 300 Secs
---------- ------------------- -------- -------- --------
3 (ksoftirqd/0) 0.00% 0.00% 0.01%
12 (ksoftirqd/1) 0.09% 0.01% 0.01%
1088 (procmgr) 0.09% 0.07% 0.07%
1208 osapiTimer 0.00% 0.02% 0.01%
1210 portMonTask 0.00% 0.01% 0.01%
1211 bcmINTR 0.00% 0.01% 0.00%
1212 socdmadesc.0 0.29% 0.18% 0.19%
1213 bcmMEM_SCAN.0 0.00% 0.01% 0.02%
1215 bcmIbodSync.0 0.09% 0.05% 0.04%
1216 bcmL2X.0 3.30% 3.48% 3.53%
1217 bcmCNTR.0 1.65% 1.31% 1.33%
1222 bcmRX 0.00% 0.02% 0.02%
1236 bcmLINK.0 0.58% 0.58% 0.58%
1237 cpuUtilMonitorTask 0.09% 0.13% 0.13%
1269 emWeb 0.00% 0.00% 6.42%
1283 hapiBroadBufferUsag 0.00% 0.03% 0.03%
1286 hapiBroadBfdCtrlTas 0.09% 0.10% 0.10%
1308 dot1qTask 0.00% 0.00% 0.03%
1321 umWorkerTask 0.00% 0.00% 0.12%
1324 snoopTask 0.00% 0.03% 0.02%
1335 dhcpsPingTask 0.09% 0.02% 0.00%
1383 openrTask 0.48% 0.62% 0.58%
1424 dnsRxTask 0.09% 0.01% 0.00%
1432 RMONTask 0.09% 0.07% 0.07%
1449 StatsAppTask 0.19% 0.19% 0.19%
1492 poeRead.0 0.00% 0.02% 0.02%
1549 poe_monitor 0.00% 0.01% 0.02%
------------------------------ -------- -------- --------
Total CPU Utilization 7.29% 7.11% 13.74%

JCM05,

The behavior that your describing is peculiar indeed, would you be able to check the logs and see if anything stands out. My first thought is a possible memory/flash failure, but am not certain based on the details.

Would you do me a favor and private message Erman and I the svc tag for the system, so that we can research our options?

Lastly, if you could, would you upload the logs to upload. dell . com and with the tag you provide I will be able to locate them.

Thanks.