Richard Burdette wrote:
> 
> Just before I got your reply, I finally found a document on CCO
> that explained that I had to have the 'ip pim rp-address ...'
> configured on both routers which I did.  No I'm not seeing the
> earlier problem about not being able to join the Auto-RP router.

Unless you are interested in practicing with Auto-RP, I would just turn it
off.  It certainly isn't necessary or beneficial in your configuration. 
Static RP will do just fine.  I would remove any Auto-RP config from both
routers (at the very least until you get things working statically).

> 
> As I was seeing before, I can see the multicast entry in the
> mroute table on the RP sever, but it is Pruned by the looks of
> it and it is not sending out the serial port to the other
> router...
> 
> What could it be now?

It would help if we knew the IP scheme of your setup.  Maybe even configs. 
But start with static RP and see what that does for you.

> 
> 2620 Mroute
> 
> 2620#sho ip mroute
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C
> - Connected,
>        L - Local, P - Pruned, R - RP-bit set, F - Register flag,
>        T - SPT-bit set, J - Join SPT, M - MSDP created entry,
>        X - Proxy Join Timer Running, A - Candidate for MSDP
> Advertisement,
>        U - URD, I - Received Source Specific Host Report, s -
> SSM
> Outgoing interface flags: H - Hardware switched
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
> 
> (*, 239.255.255.250), 00:18:05/00:03:13, RP 10.1.1.1, flags: S
>   Incoming interface: Null, RPF nbr 0.0.0.0
>   Outgoing interface list:
>     Serial0/0, Forward/Sparse-Dense, 00:18:05/00:03:13
> 
> (*, 224.0.1.40), 19:06:50/00:00:00, RP 10.1.1.1, flags: SJCL
>   Incoming interface: Null, RPF nbr 0.0.0.0
>   Outgoing interface list:
>     Serial0/0, Forward/Sparse-Dense, 00:55:50/00:02:57
>     FastEthernet0/0, Forward/Sparse-Dense, 19:06:50/00:02:45
> 
> (*, 239.192.47.232), 00:00:04/00:02:59, RP 10.1.1.1, flags: SP
>   Incoming interface: Null, RPF nbr 0.0.0.0
>   Outgoing interface list: Null
> 
> (10.1.1.2, 239.192.47.232), 00:00:06/00:02:59, flags: PT
>   Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0
>   Outgoing interface list: Null
> 
> 2514 Mroute
> 
> 2514#sho ip mroute
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C
> - Connected,
>        L - Local, P - Pruned, R - RP-bit set, F - Register flag,
>        T - SPT-bit set, J - Join SPT, M - MSDP created entry,
>        X - Proxy Join Timer Running, A - Candidate for MSDP
> Advertisement,
>        U - URD, I - Received Source Specific Host Report, s -
> SSM
> Outgoing interface flags: H - Hardware switched
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
> 
> (*, 239.255.255.250), 00:19:03/00:01:59, RP 10.1.1.1, flags: SJC
>   Incoming interface: Serial0, RPF nbr 20.1.1.1
>   Outgoing interface list:
>     Ethernet0, Forward/Sparse-Dense, 00:19:03/00:01:59
> 
> (*, 224.0.1.40), 00:34:45/00:00:00, RP 10.1.1.1, flags: SJCL
>   Incoming interface: Serial0, RPF nbr 20.1.1.1
>   Outgoing interface list:
>     Ethernet0, Forward/Sparse-Dense, 00:34:45/00:02:03
> 
> As you can see the 2620 is aware of the multicast stream from
> FE0/0, but it's Pruned and it's not putting it ouot to the 2514?




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=61972&t=61950
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to