asked on

Cisco Switch: Calhoun LED Proc

Hello,

We have four identically configured Cisco Switches (2950 running 12.1(22)EA2)

One of them has a high CPU (20%) while the rest are 1%. None of them are really doing much, no traffic currently going through them. The one with a high CPU has this process to blame...

20 400615112 49492703 8094 16.95% 16.97% 16.01% 0 Calhoun LED Proc

While the others are much lower...
20 569772 59394695 9 0.00% 0.00% 0.03% 0 Calhoun LED Proc

What is this process, and any idea why it might chew up CPU? I haven't yet rebooted the switch. I'd like to understand it first. I imagine a reboot might clear it, but I'd like to know what it is first.

Thanks
Shane

ASKER CERTIFIED SOLUTION

Les Moore

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

harbor235

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

harbor235

i agree with lrmoore though, there is no direct reference to that process.

harbor235

Les Moore

>the highest percentage processes are Port Status Process and Led Control Process. It is normal behavior for these processes to be a high percentage of the total CPU utilization.
That may only apply to the -XL series, not the 2950, and I would venture to say that it is still abnormal to have two switches side by side basically idle and have one of them be that different..

shanepresley

ASKER

Thanks for the help guys. I agree, it might be normal, but these are four identical switches (even the same number of devices connected per switch), and not the XL series. But it seems like it might be related.

Anyway, I'll place a TAC ticket once we get support setup (we just got these switches a week ago). For now I'll close this question, but I'll update it once Cisco answers.

Shane

shanepresley

ASKER

Just an update after speaking with the TAC. Yes, that process manages LED lights. However, there was a known bug in my IOS with that process. Upgrading IOS fixed it.

Not sure why it affected only one switch. But all better now. THanks guys...