Many thanks I will try again on here initially. I wondered if there was a way to submit incidents, but will phone if we get too stuck.

All switches are on the latest 6.2.1.6 FW. and I only noticed these sort of log messages since we moved from 6.1.1.7 to 6.2.1.5. and seem to appear where we have some older infrastructure attached in this case some Linksys Wireless APs. Process seems okay apart from snooptask which has always being high since install.

If the error logs were a little more helpful or if I could find a reference this would help.does anyone know what uport and BCM refer to? If it connected in any way to the stack ports? or am I better looking at Broadcom for support.

Memory Utilization Report

status     KBytes

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

free       275704

alloc      756724

CPU Utilization:

PID        Name                  5 Secs  60 Secs 300 Sec

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

3          (ksoftirqd/0)         0.00%    0.12%    0.13%

12         (ksoftirqd/1)         0.29%    0.29%    0.24%

17         (kworker/0:1)         0.00%    0.03%    0.02%

18         (kworker/1:1)         0.09%    0.03%    0.01%

1070       (procmgr)             0.09%    0.10%    0.09%

1142       (syncdb)              0.00%    0.00%    0.01%

1191       osapiTimer            0.48%    0.20%    0.08%

1198       bcmINTR               8.39%    9.99%    9.86%

1199       socdmadesc.0          0.09%    0.14%    0.14%

1200       bcmMEM_SCAN.0         0.00%    0.05%    0.06%

1202       bcmL2X.0              3.61%    3.73%    3.79%

1203       bcmCNTR.0             0.78%    0.92%    0.92%

1208       bcmRX                 1.36%    1.34%    1.32%

1209       bcmNHOP               0.00%    0.02%    0.02%

1210       bcmATP-TX             8.29%   12.61%   12.68%

1211       bcmATP-RX             0.29%    0.27%    0.21%

1221       bcmLINK.0             0.39%    0.48%    0.50%

1222       cpuUtilMonitorTask    0.09%    0.12%    0.12%

1245       dtlTask               0.29%    0.22%    0.23%

1249       hapiRxTask            0.09%    0.16%    0.15%

1256       hapiBroadBufferUsag   0.00%    0.04%    0.03%

1260       hapiBroadBfdCtrlTas   0.68%    0.20%    0.11%

1266       trafficStormControl   0.00%    0.01%    0.00%

1274       SNMPTask              0.00%    0.00%    0.02%

1284       dot1s_timer_task      0.09%    0.03%    0.01%

1285       dot1s_task            0.00%    0.00%    0.01%

1293       unitMgrTask           0.00%    0.01%    0.01%

1296       snoopTask            22.34%   28.50%   27.87%

1298       dot3ad_core_lac_tas   0.00%    0.01%    0.00%

1302       trapTask              0.00%    0.01%    0.00%

1320       spmTask               0.09%    0.01%    0.00%

1327       ipMapForwardingTask   0.00%    0.05%    0.05%

1360       openrTask             0.78%    0.75%    0.75%

1366       (ospf_app)            0.00%    0.01%    0.01%

1389       ip6MapLocalDataTask   0.09%    0.19%    0.15%

1396       lldpTask              0.39%    0.15%    0.12%

1405       isdpTask              0.00%    0.00%    0.02%

1407       RMONTask              0.09%    0.10%    0.08%

1419       StatsAppTask          1.17%    0.91%    0.93%

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

Total CPU Utilization           50.45%   62.00%   60.96%

We had an issue where the stack locked up. We are still running with switch 2 as the master and 5 as standby. The errors seem to have reduced, but I am worried if we lose power and Switch 1 becomes master again we will suffer another outage. Is there any way to check state of a remote switch? When I try and connect it reports CLI unavailable connect to master.

I saw a lot of these messages when we updated the firmware but they didn't seem to effect the switches other than numbers of logs produced.

I cannot try to revert to 6.1.1.7 as the stack is heavily in use. and also feeds off to a remote site. The errors seem to have stopped since moving management to stack member 2. Is there any way to get more information on the actual error and what it refers too?

Stack member 1 is a N2048P and we have had a few issues with these also on 6.1.1.7 with power being dropped from the POE ports.