All things related to multicast

[Michael Lambert <>]

Caren (and anyone else listening),

On 10 Nov 2009, at 13:55:57, Caren Litvanyi wrote:

> > hsc-1#sh ip rpf 141.142.2.55
> > RPF information for jhereg.ncsa.uiuc.edu (141.142.2.55)
> > RPF interface: GigabitEthernet1/1
> > RPF neighbor: hsc-inet-vl998.nsog.wvu.edu (10.0.6.114)
> > RPF route/mask: 157.182.0.0/16
> > RPF type: unicast ()
> > RPF recursion count: 0
> > Doing distance-preferred lookups across tables
>
> Nope.  That route/mask makes no sense for 141.142.2.55.
> I'm not that great at Ciscoese these days, but I would have
> also thought it would tell you where it got the information
> from under RPF type: unicast (), even if it were static or connected,
> let alone a routing protocol.
> I'd probably raise the white flag and open a case.  Do you
> know how it was supposed to be learning the right RPF path?
> MBGP?  Or?

Well...  A 'show ip route' yields these nuggets (uninteresting cruft  
removed):

Gateway of last resort is 10.0.6.114 to network 157.182.0.0

D*      157.182.0.0/16 [90/2816] via 10.0.6.114, 1d00h,  
GigabitEthernet1/1
D*EX 0.0.0.0/0 [170/3072] via 10.0.6.114, 1d00h, GigabitEthernet1/1

The '*' indicates a candidate default.  Huh?  Maybe this is just some  
weird EIGRPism, since the config says nothing about generating a  
default.

I'm thinking a static default mroute to the upstream interface will be  
a sufficient workaround.

Michael