All things related to multicast

["Marshall Eubanks" <>]

On Wed, 23 Jul 2003 14:37:18 -0400
 "Marshall Eubanks" 
<>
 wrote:
> On Wed, 23 Jul 2003 13:29:33 -0400
>  Alan Crosswell 
> <>
>  wrote:
> > Try again
> > 
> 
> Well, I now have MBGP
> 

Everthing seems to be working now. Since it took a little while,
Alan and I thought we might share the highlights :

The border router had the MCT mbgp announcements all along.
(The missing announcements to the outside mentioned and fixed below,
while an error, did not cause reception problems.) However, the
_internal_ routers at Columbia did not have MBGP information 
as the gateway / border
router was not set up to MBGP peer with them. This meant that

- things worked if you were directly attached to the border router
- things worked if a multicast was sourced in I2, as the default
route was the unicast route to I2, which was the same as the multicast
one, and RPF passed.
- things did NOT work if the multicast was sourced from I1, as
the default (unicast) route pointed out Broadwing and RPF would fail.
- all internal routers showed NoNeg (for No Negotiation I think)
with the neighbor (the gateway router) if you did a  

show ip mbgp sum 

on them. If you reset them, it would show "Active" for a few seconds, then
revert to "NoNeg" in the State/PfxRcd column.

Also, since there was internal load balancing, all of the internal routers
had to be set to be MBGP peers with the gateway before things worked
reliably.

It works well now...

Thanks for Bill Owens for assistence - any mistakes here are my own.

Marshall



> multicasttech-1>show ip mbgp 160.39.246.225 
> BGP routing table entry for 160.39.0.0/16, version 2172744
> Paths: (1 available, best #1, table NULL)
> Flag: 0x208
>   Not advertised to any peer
>   3356 11537 3754 14
>     63.210.25.153 from 63.210.25.153 (209.244.2.157)
>       Origin IGP, metric 0, localpref 100, valid, external, best
> multicasttech-1> 
> 
> But I still cannot get my groups.
> 
> Do you have anything up so that I can see if I can get from Columbia to
> MCT ?
> 
> Marshall
> 
> 
> 
> > -------- Original Message --------
> > Subject: Re: [Fwd: Columbia - Multicasttech multicast failure (?)]
> > Date: Wed, 23 Jul 2003 12:45:57 -0400
> > From: Johan M. Andersen 
> > <>
> > To: Alan Crosswell 
> > <>
> > CC: Network Operations Center 
> > <>
> > References: 
> > <>
> > 
> > Think this is fixed. Under 'router bgp 14' on nn2k-gw, there is an
> > address-family ipv4 multicast
> > stanza. this stanza had no networks listed in it. I added
> > network 128.59.0.0
> > network 160.39.0.0
> > 
> > Old:
> > nn2k-gw#sh ip mbgp 160.39.0.0
> > % Network not in table
> > nn2k-gw#sh ip mbgp 128.59.0.0
> > % Network not in table
> > 
> > Current:
> > nn2k-gw#sh ip mbgp 128.59.0.0
> > BGP routing table entry for 128.59.0.0/16, version 28857
> > Paths: (1 available, best #1, table Default-MBGP-Routing-Table)
> >    Advertised to non peer-group peers:
> >    199.109.5.6
> >    Local
> >      0.0.0.0 from 0.0.0.0 (128.59.0.6)
> >        Origin IGP, metric 0, localpref 100, weight 32768, valid, 
> > sourced, local, best
> > nn2k-gw#sh ip mbgp 160.39.0.0
> > BGP routing table entry for 160.39.0.0/16, version 28862
> > Paths: (1 available, best #1, table Default-MBGP-Routing-Table)
> > Flag: 0x820
> >    Not advertised to any peer
> >    Local
> >      0.0.0.0 from 0.0.0.0 (128.59.0.6)
> >        Origin IGP, metric 0, localpref 100, weight 32768, valid, 
> > sourced, local, best
> > 
> > Does this look right to you?
> > 
> > /johan
> > 
>