All things related to multicast

[Jan Novak <>]

> > I suppose you see these problems with both 12.0(6)S and 12.0(7)S,
> > and that the spurious memory accesses only appeared with 12.0(7)S?
> 
> Out of curiousity, are you using a 7500 or a 12000?
> 

Seems everybody suffers - this is a 7507 with 12.0.6(S):

Mcast99# sh ip ms sum
MSDP Peer Status Summary
Peer Address     AS    State    Uptime/  Reset Peer Name
                                Downtime Count
212.1.195.42     8933  Up       07:19:59 448   NL
212.1.195.54     2852  Up       00:33:59 594   cz-de2.mcast.ten-155.net
157.130.21.153   704   Listen   00:00:02 13762 Tunnel32.MB1.BOS1.ALTER.NET
212.1.195.62     559   Up       00:08:59 2436  switch-de2.mcast.ten-155.net
193.174.226.201  1275  Up       00:00:00 17944 mr-stuttgart1.win-ip.dfn.de
212.1.195.58     1717  Up       00:13:26 922   renater-de2.mcast.ten-155.net
Mcast99#

2w5d: %MSDP-5-PEER_UPDOWN: Session to peer 193.174.226.201 going down
Nov  4 14:06:25.348: MSDP: 193.174.226.201: Peer reset, exceeded max output 
queue length
2w5d: %MSDP-5-PEER_UPDOWN: Session to peer 193.174.226.201 going up
2w5d: %MSDP-5-PEER_UPDOWN: Session to peer 193.174.226.201 going down
Nov  4 14:06:28.512: MSDP: 193.174.226.201: Peer reset, exceeded max output 
queue length
2w5d: %MSDP-5-PEER_UPDOWN: Session to peer 193.174.226.201 going up


Apart of that, I observed up-to 600kbit/s of MSDP traffic between two peers
 when the flapping occurs.

Jan