[nsp] high cpu load on 2651

[Jim Littlefield]

No, the 802.1q trunking could actually be removed...it was being used 
when we were tunneling voice...only VLAN 1 traffic is passing over the link.

Thanks for the CPU spike comment; I will have to remember that one.


Temkin, David wrote:

>One thing to note - I see you're doing 802.1q...
>
>Are there VLANs on the trunk to your switch that aren't defined on the
>router but are allowed on the trunk?  We've seen 20-30% CPU spikes
>because of this because apparently the router CPU switches this traffic
>before discarding it (bug or feature?)
>
>
>
>-----Original Message-----
>From: cisco-nsp-bounces at puck.nether.net
>[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jim Littlefield
>Sent: Tuesday, January 13, 2004 10:19 AM
>To: cisco-nsp at puck.nether.net
>Subject: Re: [nsp] high cpu load on 2651
>
>
>Beprojects.com wrote:
>
>  
>
>>With what config and what packet size?
>> 
>>
>>    
>>
>
>We originally wanted to tunnel voice traffic (using a pair of Rad boxes)
>
>for a remote PBX across a 45MB/s link; packet size was 40 bytes. We have
>
>since moved the voice to a dedicated T1, but the 2651's still 
>occasionally run out of CPU with normal day-to-day traffic. We put a 
>Packeteer on one side to look for anything unusual, but nothing "funny" 
>showed up.
>
>Here is a config from one of the routers:
>
>version 12.2
>service timestamps debug datetime localtime
>service timestamps log datetime localtime
>service password-encryption
>!
>hostname pvd-gw
>!
>logging buffered 4096 debugging
>!
>memory-size iomem 15
>clock timezone EST -5
>clock summer-time EDT recurring
>ip subnet-zero
>ip cef
>!
>ip multicast-routing
>ipx routing 000b.fdd8.6ba0
>!
>voice call carrier capacity active
>!
>mta receive maximum-recipients 0
>!
>buffers small permanent 85
>buffers small max-free 122
>buffers small min-free 25
>buffers middle permanent 40
>buffers middle max-free 57
>buffers middle min-free 12
>buffers big permanent 65
>buffers big max-free 92
>buffers big min-free 19
>buffers verybig permanent 13
>buffers verybig max-free 18
>buffers verybig min-free 3
>!
>stun peer-name 192.168.254.134
>stun protocol-group 1 basic
>stun protocol-group 2 basic
>stun remote-peer-keepalive
>!
>interface Loopback0
> ip address 192.168.254.134 255.255.255.255
>!
>interface FastEthernet0/0
> no ip address
> load-interval 30
> speed 100
> full-duplex
> fair-queue
> hold-queue 250 in
>!
>interface FastEthernet0/0.1
> encapsulation dot1Q 1 native
> ip address 192.168.128.1 255.255.255.0
> ip pim dense-mode
> ip cgmp
> ipx encapsulation NOVELL-ETHER
> ipx network 358
>!
>interface FastEthernet0/0.252
>!
>interface Serial0/0
> bandwidth 1536
> ip address 192.168.254.130 255.255.255.252
> ipx network 360
> service-module t1 timeslots 1-24
>!
>interface FastEthernet0/1
> bandwidth 46080
> ip address 192.168.254.2 255.255.255.128
> ip accounting output-packets
> ip hello-interval eigrp 100 1
> ip hold-time eigrp 100 3
> load-interval 30
> speed 100
> full-duplex
> ipx network 359
>!
>router eigrp 100
> redistribute connected
> redistribute static
> network 192.168.252.0
> network 192.168.254.0
> no auto-summary
> no eigrp log-neighbor-changes
>!
>router rip
> redistribute eigrp 100 metric 3
> network 192.168.128.0
>!
>ip classless
>ip route 192.168.252.0 255.255.255.248 192.168.254.129 200
>no ip http server
>!
>ipx router eigrp 200
> network 359
> network 360
>!
>ipx router rip
> no network 360
> no network 359
>!
>snmp-server community public RO
>snmp-server enable traps tty
>call rsvp-sync
>!
>mgcp profile default
>!
>dial-peer cor custom
>!
>end
>
>
>  
>


-- 
Jim Littlefield            "I have a red sign on my door. It says, 
                            'If this sign is blue, you're moving
                            too fast.'" - Steven Wright