• November 25, 2020, 02:17:35 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: CoreSW 8006 with usually High CPU  (Read 2269 times)

0 Members and 1 Guest are viewing this topic.

Offline tieuantuan

  • Rookie
  • **
  • Posts: 8
CoreSW 8006 with usually High CPU
« on: May 06, 2014, 08:52:46 PM »
Dear All,
I so confuse that our network system using 2 Nortel 8006 as Core SW, running IST & SMLT with Access Switch 4548. Our infrastructure just like Core SW got gateway for all Vlan. But sometime, Core SW get High CPU nearly 100% . I using command " show sys perf" to indicate CPU rate.
I Also configure loop prevention by all Access Switch Port by Spanning tree, BPDU Filter, rate limit broadcast.
and on CoreSW, CP Limit all downlink port with 10000 broadcast & multicast packet.
during one month, one day we nearly 2 , 3 times Coresw got high CPU , that make all system is down for few minutes , after that, Coresw working normally, sometime CoreSW is broken, I need to reset 2 Core SW.

I wonder if software if problem, or is there anything that I can do to make issue doesn't happen again.
Thank you for sharing experience.

Offline trieudoahong

  • Jr. Member
  • **
  • Posts: 29
Re: CoreSW 8006 with usually High CPU
« Reply #1 on: May 07, 2014, 11:25:19 PM »
I suggest you check mac address table. I've got performance issue with 8006 because too many mac located on 1 switch port. Mac flooding or large broadcast domain can lead to performance issue.

Offline Dominik

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1564
    • Networkautobahn
Re: CoreSW 8006 with usually High CPU
« Reply #2 on: May 09, 2014, 01:52:08 AM »
I would also suggest that you have a Loop problem on your ERS8k.

I have not seen high CPU peaks in fact of a software related issue on SW code so far.

The most common three causes for high CPU peaks are:
1. Loop condition in the network , wich can be on L2 or L3
2. High ammount of corntrol traffic like e.g. agressivly SNMP polling of your ERS8k.
3. An active trace level on your device.

Good Luck
Itīs always the networks fault!