[f-nsp] Multicast causing high CPU

Alexey Kouznetsov foundry-list at kouznetsov.com
Fri Mar 13 05:12:06 EDT 2009


There are totally no IP ROUTING. Only MCAST ROUTING and L2 switching. Now I
have added no icmp redirects. but as far as here are no IP routing traffic,
there are no icmp redirect generates and no any CPU changes seen. Also I
already have
 no ip source-route
in the config
There are no RIP, no OSPF. only MBGP routing protocol.
# egrep '^router' config
router dvmrp
router pim
router msdp
router pim
router bgp

in bgp router no any unicast active neighbors. only for address-family ipv4
multicast
we already have
ip multicast-perf
in our config for at list last year. (switch was rebooted after this command
added)

Same as we already added

mcast-hw-replic-oar
ip multicast hardware-drop
in config and it was reboted after such commands added. No any changes seen.

Also I tried to add
router pim
+ hardware-drop
and no any changes seen.

/Alexey
2009/3/12 Dimitar Kosadinov <kgb at bginfo.net>

> always use "no ip icmp redirect" !!!
> this safe Your CPU :)
> I dont sure Your multicast problem is this, but just use it. This reflect
> to OLD RIPv1 based routing only, I sure you dont use rip.
> try use "ip multicast-perf"  too / need reload btw to see changes /
> sorry for my bad english
>
>
> On Thu, 12 Mar 2009 11:40:57 +0300
> Alexey Kouznetsov <foundry-list at kouznetsov.com> wrote:
>
>  > ip router-id added.
> > Looks like no any changes
> > "ip icmp redirect"
> > Looks like this is defauls
> > because command is not shown in config. but if i add no ip icmp redirect,
> > then I see the command in show run.
> >
> > 2009/3/10 Jeroen Wunnink <jeroen at easyhosting.nl>
> >
> > > Not sure where I heared this before, but did you try setting a 'ip
> > > router-id <ip address>' ?
> > > I recall somewhere that setting this solves several CPU related
> utilization
> > > problems on the bigiron.
> > >
> > >
> > > Alexey Kouznetsov wrote:
> > >
> > >>
> > >> Something like 70 Mbit untill visible on TV losts coming (at this
> point we
> > >> have > 95% CPU load). as long as packet size here ~1300 bytes, then it
> less
> > >> then 10K PPS.
> > >>  Here are some VE interfaces assigned to user's vlans. Each VE
> interface
> > >> have only 1 IP address assigned
> > >>  like
> > >>  -----
> > >> interface ve 1
> > >>  ip address 10.10.31.2/24 <http://10.10.31.2/24>
> > >>  ip pim-sparse
> > >> -----
> > >>  and
> > >> -----
> > >> interface ve 11
> > >>  ip address a.b.c.110/30
> > >>  ip pim-sparse
> > >>  ip pim border
> > >>  management-ip-disable
> > >> -----
> > >> for interfase where Mcast come from.
> > >>   /Alexey
> > >>
> > >
> > > --
> > >
> > > Met vriendelijke groet,
> > >
> > > Jeroen Wunnink,
> > > EasyHosting B.V. Systeembeheerder
> > > systeembeheer at easyhosting.nl
> > >
> > > telefoon:+31 (035) 6285455              Postbus 48
> > > fax: +31 (035) 6838242                  3755 ZG Eemnes
> > >
> > > http://www.easyhosting.nl
> > > http://www.easycolocate.nl
> > >
> > >
> > >
> > > _______________________________________________
> > > foundry-nsp mailing list
> > > foundry-nsp at puck.nether.net
> > > http://puck.nether.net/mailman/listinfo/foundry-nsp
> > >
> >
>
>
> --
>  <kgb at bginfo.net>
>  _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20090313/a53d58a1/attachment.html>


More information about the foundry-nsp mailing list