All things related to multicast

[Peter John Hill <>]

Yep, we get that too. We run an msdp mesh with three cisco routers. It 
happens, but multicast does not seem to be too affected. Users can 
still see sdp's just fine. I have been pretty much ignoring the 
message. Do you see any errors in multicast itself?

Peter Hill
Network Engineer
Carnegie Mellon University

On Tuesday, June 10, 2003, at 02:48  AM, John Barlow wrote:

> There is a whole bunch of email from late in 1999 on the I2 multicast 
> wg
> list about frequest MSDP resets ("Peer reset, exceeded max output queue
> length" on Cisco gear).
>
> I have been getting frequent MSDP resets, and have lived with it for at
> least 6 months, but I want to fix it (if that is possible).
>
> What pearls of wisdom exist for finding and fixing the MSDP resets ?  
> (a
> lot of my sessions go down frequently - one example is every 40 
> seconds,
> and take 30 seconds to return - and this occurs on almost every router
> in my network).  I tried to find the MSDPMon.tar utility (see
> http://www.dante.net/pubs/dip/41/41.html) but the FTP server listed 
> does
> not accept anonymous FTP connections.
>
> I have lots of routers exhibiting the reset/flapping behaviour, chunks
> of the logs are attached at the end of this message (if that is your
> thing :-)
>
> The routers are all Cisco (7500, OSR7600, 7200), running various IOS
> releases (12.0(19)ST2, 12.2(14)ZA1, 12.0(24)S).  Most of the time
> multicast is usable, occasionally things get worse and the SA cache 
> ends
> up missing entries (see
> http://noc.aarnet.edu.au/mrtg/router/multicast.html, check out the
> lowest four graphs).  I do have potential for routing loops, but 
> notable
> in my problems is our 7200 router, connected to the Pacific North West
> Gigapop in Seattle, and that router sees MSDP flaps on the links to our
> peers:
>
> seattle#sh ip msdp summ
> MSDP Peer Status Summary
> Peer Address     AS    State    Uptime/  Reset SA    Peer Name
>                                 Downtime Count Count
> 198.32.170.43    11537 Up       1w6d     47    3864
> Abilene-PWAVE.pnw-gigapop.net
> 198.32.171.31    7474  Listen   5w5d     1362  0
> prs2-wes-GE3-0.pnw-gigapop.net
> 198.32.170.30    101   Up       00:00:48 12543 0
> prs1-wes-ge-0-1-0-0.pnw-gigapop.net
> 192.231.212.33   7570  Up       00:00:07 5627  16
> pos1-0.sccn1.broadway.aarnet.net.au
> 192.231.212.161  7570  Up       00:00:15 4182  0
> pos2-0.sccn1.manoa.aarnet.net.au
> 198.32.170.48    293   Down     7w0d     0     0
> ESNet-PWAVE.pnw-gigapop.net
> 198.32.170.46    22388 Up       00:00:37 7858  66
> TRANSPAC-PWAVE.pnw-gigapop.net
> 198.32.170.40    8075  Listen   7w0d     0     0
> MicroSoft-PWAVE.pnw-gigapop.net
> 192.231.212.18   7570  Up       00:08:15 1729  12
> nswrno2-gbe10-0-0-916.nswrno.net.au
> 198.32.170.42    7539  Listen   7w0d     0     0
> TANET2-PWAVE.pnw-gigapop.net
> 198.32.170.44    6509  Listen   7w0d     0     0     
> c4-van01.canet4.net
> 198.32.171.44    6509  Listen   7w0d     0     0     
> c4-van01.canet4.net
> 198.32.171.40    8075  Listen   7w0d     0     0
> MicroSoft-PWAVE.pnw-gigapop.net
> seattle#
>
> Amel Caldwell (from the PNWGpop) has suggested (heck, one and a half
> years ago, hmm, sorry Amel - must get around to implementing that soon
> !) that we should apply a route-map to our SA-filtering.  Is this still
> the current best-practise to help with the MSDP flapping ?  Note that
> the resets I see are not only on Cisco-Juniper connections, but all
> throughout our (all-cisco) network.
>
>
>
> Any thoughts as to what I need to do ?
>
>
> Thanks, John Barlow
> GrangeNet and AARNet
> Australia
>
>
>
>
> SCCN Sydney:
> Jun 10 15:17:14.087 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.34 going down
> Jun 10 15:17:14.087 AEST: MSDP: 192.231.212.34: Peer reset, other side
> reset
> Jun 10 15:17:16.811 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going down
> Jun 10 15:17:16.811 AEST: MSDP: 130.130.255.190: Peer reset, exceeded
> max output queue length
> Jun 10 15:17:45.704 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.34 going up
> Jun 10 15:17:57.936 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going down
> Jun 10 15:17:57.940 AEST: MSDP: 202.0.98.97: Peer reset, exceeded max
> output queue length
> Jun 10 15:18:00.148 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going up
> Jun 10 15:18:34.020 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going up
> Jun 10 15:18:38.028 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going down
> Jun 10 15:18:38.032 AEST: MSDP: 130.130.255.190: Peer reset, exceeded
> max output queue length
> Jun 10 15:19:28.797 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.34 going down
> Jun 10 15:19:28.797 AEST: MSDP: 192.231.212.34: Peer reset, other side
> reset
> Jun 10 15:19:30.165 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going up
> Jun 10 15:19:33.661 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going down
> Jun 10 15:19:33.665 AEST: MSDP: 202.0.98.97: Peer reset, exceeded max
> output queue length
> Jun 10 15:19:59.557 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.34 going up
> Jun 10 15:20:04.325 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going up
> Jun 10 15:20:22.890 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going down
> Jun 10 15:20:22.890 AEST: MSDP: 130.130.255.190: Peer reset, exceeded
> max output queue length
> Jun 10 15:20:52.970 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going down
> Jun 10 15:20:52.970 AEST: MSDP: 202.0.98.97: Peer reset, exceeded max
> output queue length
> Jun 10 15:21:00.170 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going up
> Jun 10 15:21:31.782 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going up
> Jun 10 15:21:50.447 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going down
> Jun 10 15:21:50.451 AEST: MSDP: 130.130.255.190: Peer reset, exceeded
> max output queue length
> Jun 10 15:22:27.851 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going down
> Jun 10 15:22:27.851 AEST: MSDP: 202.0.98.97: Peer reset, exceeded max
> output queue length
> Jun 10 15:22:30.191 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going up
> Jun 10 15:23:04.027 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going up
> Jun 10 15:23:11.944 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going down
> Jun 10 15:23:11.948 AEST: MSDP: 130.130.255.190: Peer reset, exceeded
> max output queue length
> Jun 10 15:23:43.412 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going down
> Jun 10 15:23:43.416 AEST: MSDP: 202.0.98.97: Peer reset, exceeded max
> output queue length
> Jun 10 15:24:00.192 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going up
> Jun 10 15:24:13.916 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going up
> Jun 10 15:24:56.309 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going down
> Jun 10 15:24:56.309 AEST: MSDP: 130.130.255.190: Peer reset, exceeded
> max output queue length
> Jun 10 15:25:12.373 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going down
> Jun 10 15:25:12.373 AEST: MSDP: 202.0.98.97: Peer reset, exceeded max
> output queue length
> Jun 10 15:25:30.209 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going up
> Jun 10 15:25:42.949 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going up
> Jun 10 15:26:27.690 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going down
> Jun 10 15:26:27.694 AEST: MSDP: 202.0.98.97: Peer reset, exceeded max
> output queue length
> Jun 10 15:26:29.758 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going down
> Jun 10 15:26:29.758 AEST: MSDP: 130.130.255.190: Peer reset, exceeded
> max output queue length
> Jun 10 15:26:41.250 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.34 going down
> Jun 10 15:26:41.250 AEST: MSDP: 192.231.212.34: Peer reset, other side
> reset
> Jun 10 15:27:00.826 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 130.130.255.190 going up
> Jun 10 15:27:01.162 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.97 going up
> Jun 10 15:27:13.494 AEST: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.34 going up
>
> SCCN Seattle:
> Jun  9 22:17:03.367 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:17:03.367 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:17:13.935 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.33 going down
> Jun  9 22:17:13.939 PDT: MSDP: 192.231.212.33: Peer reset, exceeded max
> output queue length
> Jun  9 22:17:33.523 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going up
> Jun  9 22:17:39.015 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:17:39.019 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:17:45.779 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.33 going up
> Jun  9 22:17:47.867 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:18:09.248 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:18:09.252 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:18:27.972 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:18:27.976 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:18:36.700 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:18:39.312 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going up
> Jun  9 22:19:14.500 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:19:14.504 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:19:26.604 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:19:26.608 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:19:28.656 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.33 going down
> Jun  9 22:19:28.660 PDT: MSDP: 192.231.212.33: Peer reset, exceeded max
> output queue length
> Jun  9 22:19:35.900 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:19:44.512 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going up
> Jun  9 22:19:59.636 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.33 going up
> Jun  9 22:20:29.052 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:20:29.056 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:20:31.096 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.161 going down
> Jun  9 22:20:31.096 PDT: MSDP: 192.231.212.161: Peer reset, exceeded 
> max
> output queue length
> Jun  9 22:20:31.172 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:20:31.172 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:20:38.424 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:21:01.224 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going up
> Jun  9 22:21:02.160 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.161 going up
> Jun  9 22:21:33.289 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:21:33.293 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:21:41.801 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:21:55.553 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:21:55.553 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:22:25.605 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going up
> Jun  9 22:22:31.797 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:22:31.801 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:22:40.957 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:23:14.105 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:23:14.105 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:23:24.181 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:23:24.185 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:23:32.917 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:23:44.145 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going up
> Jun  9 22:24:17.061 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:24:17.065 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:24:19.149 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:24:19.153 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:24:25.805 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:24:49.509 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going up
> Jun  9 22:25:25.610 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:25:25.614 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:25:34.782 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:25:43.838 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:25:43.842 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:26:13.870 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going up
> Jun  9 22:26:33.062 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going down
> Jun  9 22:26:33.062 PDT: MSDP: 198.32.170.30: Peer reset, exceeded max
> output queue length
> Jun  9 22:26:35.102 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.161 going down
> Jun  9 22:26:35.102 PDT: MSDP: 192.231.212.161: Peer reset, exceeded 
> max
> output queue length
> Jun  9 22:26:41.126 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.33 going down
> Jun  9 22:26:41.130 PDT: MSDP: 192.231.212.33: Peer reset, exceeded max
> output queue length
> Jun  9 22:26:42.546 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.30 going up
> Jun  9 22:27:05.250 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 198.32.170.46 going down
> Jun  9 22:27:05.254 PDT: MSDP: 198.32.170.46: Peer reset, exceeded max
> output queue length
> Jun  9 22:27:05.434 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.161 going up
> Jun  9 22:27:14.258 PDT: %MSDP-5-PEER_UPDOWN: Session to peer
> 192.231.212.33 going up
>
> GrangeNet Sydney:
> Jun 10 15:17:57.937 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going down
> Jun 10 15:17:57.937 +1000: MSDP(0): 202.0.98.98: Peer reset, other side
> reset
> Jun 10 15:18:34.022 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going up
> Jun 10 15:19:33.663 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going down
> Jun 10 15:19:33.663 +1000: MSDP(0): 202.0.98.98: Peer reset, other side
> reset
> Jun 10 15:20:04.304 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going up
> Jun 10 15:20:52.973 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going down
> Jun 10 15:20:52.973 +1000: MSDP(0): 202.0.98.98: Peer reset, other side
> reset
> Jun 10 15:21:31.786 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going up
> Jun 10 15:22:27.851 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going down
> Jun 10 15:22:27.851 +1000: MSDP(0): 202.0.98.98: Peer reset, other side
> reset
> Jun 10 15:23:04.028 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going up
> Jun 10 15:23:43.417 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going down
> Jun 10 15:23:43.417 +1000: MSDP(0): 202.0.98.98: Peer reset, other side
> reset
> Jun 10 15:24:13.921 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going up
> Jun 10 15:25:12.374 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going down
> Jun 10 15:25:12.374 +1000: MSDP(0): 202.0.98.98: Peer reset, other side
> reset
> Jun 10 15:25:42.955 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going up
> Jun 10 15:26:27.696 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going down
> Jun 10 15:26:27.696 +1000: MSDP(0): 202.0.98.98: Peer reset, other side
> reset
> Jun 10 15:27:01.161 +1000: %MSDP-5-PEER_UPDOWN: Session to peer
> 202.0.98.98 going up