wg-multicast - Re: So we need some scoping for non-global I2 multicast groups

Subject: All things related to multicast

List archive

Re: So we need some scoping for non-global I2 multicast groups

From: Mark Fullmer <>
To: David Meyer <>
Cc: "Kevin C. Almeroth" <>, , ,
Subject: Re: So we need some scoping for non-global I2 multicast groups
Date: Thu, 15 Jul 1999 14:48:09 -0400

> It's not obvious that this is the right thing to do yet
> folks...

I don't think anyone will agree that blacklisting the groups
of the day with many active sources and receivers is a good solution,
especially since it's unclear what the underlying problem(s) are, but
without the SA filters in place there are times I can't even
get a telnet session to our border router.

MSDP Peer Status Summary
Peer Address AS State Uptime/ Reset Peer Name
Downtime Count
204.147.128.141 145 Up 01:31:46 1889 cs.dng.vbns.net
164.107.2.49 159 Up 1d10h 121 kc2-lo0.net.ohio-state.edu
192.88.192.33 11537 Up 1w0d 2 abilene.ohio-gigapop.net

Note the reset count.

99-07-15-06-00-00:MSDP Source-Active Cache - 3984 entries
99-07-15-06-15-00:MSDP Source-Active Cache - 8320 entries
99-07-15-06-30-00:MSDP Source-Active Cache - 8552 entries

..

99-07-15-13-45-00:MSDP Source-Active Cache - 9359 entries
99-07-15-14-00-00:MSDP Source-Active Cache - 3239 entries
99-07-15-14-15-00:MSDP Source-Active Cache - 4026 entries

This is all from 204.147.128.141. Is Kevin on this list?

Out of 1798 current active sources, 1405 reply to ping. Many that
don't have something in the path that replies with some type of
unreachable message (filters).

Another datapoint

0500/29 16624663.608 (hums44.cohums.ohio-state.edu) 128.146.134.46 224.0.1.35
0600/29 16624664.616 (hums44.cohums.ohio-state.edu) 128.146.134.46 224.0.1.22
0700/30 16624664.700 (hums44.cohums.ohio-state.edu) 128.146.134.46 224.0.1.35
0700/29 16624664.700 (hums44.cohums.ohio-state.edu) 128.146.134.46 224.0.1.35
0800/30 16624665.580 (hums44.cohums.ohio-state.edu) 128.146.134.46 224.0.1.22
0800/29 16624665.580 (hums44.cohums.ohio-state.edu) 128.146.134.46 224.0.1.22
0900/30 16624665.796 (hums44.cohums.ohio-state.edu) 128.146.134.46 224.0.1.35
0600/30 16624740.376 (hums54.cohums.ohio-state.edu) 128.146.134.81 224.0.1.35
286E/4 16624714.644 (gozon.eng.ohio-state.edu) 128.146.232.68 224.0.1.24

It looks like this could be addressed with msdp ttl scoping.

--
mark

RE: So we need some scoping for non-global I2 multicast groups, (continued)
- RE: So we need some scoping for non-global I2 multicast groups, Wallace, Steven S, 07/14/1999
  - RE: So we need some scoping for non-global I2 multicast groups, Hugh LaMaster, 07/14/1999
    - Re: So we need some scoping for non-global I2 multicast groups, Dino Farinacci, 07/15/1999
  - Re: So we need some scoping for non-global I2 multicast groups, Mark Fullmer, 07/14/1999
    - Re: So we need some scoping for non-global I2 multicast groups, Hugh LaMaster, 07/16/1999
      - Re: So we need some scoping for non-global I2 multicast groups, Mark Fullmer, 07/18/1999
        
        Re: So we need some scoping for non-global I2 multicast groups, Hugh LaMaster, 07/19/1999
        
        Re: So we need some scoping for non-global I2 multicast groups, Guy T Almes, 07/20/1999
- Re: So we need some scoping for non-global I2 multicast groups, Kevin C. Almeroth, 07/15/1999
  - Re: So we need some scoping for non-global I2 multicast groups, David Meyer, 07/15/1999
    - Re: So we need some scoping for non-global I2 multicast groups, Mark Fullmer, 07/15/1999
      - Re: So we need some scoping for non-global I2 multicast groups, Kevin Thompson, 07/15/1999
- Re: So we need some scoping for non-global I2 multicast groups, ken lindahl, 07/15/1999
  - Re: So we need some scoping for non-global I2 multicast groups, Kevin Thompson, 07/16/1999
  - Message not available
    - Re: So we need some scoping for non-global I2 multicast groups, Mark Fullmer, 07/18/1999

List archive

Re: So we need some scoping for non-global I2 multicast groups