ivan at ig
Dec 3, 2009, 6:43 AM
Post #2 of 2
(732 views)
Permalink
|
The 'Adjust Regions' process is not an issue here. The real problem is the
interrupt part of the load (49%). That means your switch handles large
amount of traffic in software. Do you use IPv6 or other features that are
not supported by hardware in you current SDM profile?
Ivan
On Monday 16 November 2009 22:14:33 Chris Lane wrote:
> Not sure what Adjust regions is. After a google search nothing turns up.
> here is my cpu output:
>
> sh proc cpu sorted | e 0.00
> CPU utilization for five seconds: 72%/49%; one minute: 69%; five
> minutes: 69%
> PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
> 56 1458890966 8848611 164876 7.50% 4.92% 4.59% 0 Adjust
> Regions
>
>
> Following another thread suggested looking at mac address table:
> sh mac-address-table count | i Space
> Total Mac Address Space Available: 4968
> --
> sh platform tcam utilization
>
> CAM Utilization for ASIC# 0 Max Used
> Masks/Values Masks/value
> s
>
> Unicast mac addresses: 784/6272 81/582
> IPv4 IGMP groups + multicast routes: 144/1152 6/26
> IPv4 unicast directly-connected routes: 784/6272 81/582
> IPv4 unicast indirectly-connected routes: 272/2176 146/1072
> IPv4 policy based routing aces: 0/0 0/0
> IPv4 qos aces: 528/528 18/18
> IPv4 security aces: 1024/1024 57/57
>
> Note: Allocation of TCAM entries per feature uses
> a complex algorithm. The above information is meant
> to provide an abstract view of the current TCAM utilization
>
> Any help would be appreciated
> Chris
> //CL
>
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
|
