From: Rado Vasilev (decklandv@gmail.com)
Date: Thu Sep 04 2008 - 11:41:45 ART
Hi Dale,
Could you send the VRF/MDT and multicast configurations on the PE
routers and the multicast configuration on the P?
Also it'd be nice to have the output of the ``show ip pim vrf XXX
neighbor`` from both PE routers.
Rado
> Here we go again, why is SSM eluding me. I can't seem to be getting SSM
> working across my MPLS Core for building MDT, can someone give me some ideas
> to check.
>
> PE1(7600)<--->P1(6500)<--->P2(7600)<--->PE2(7600)
>
> I have "IP PIM SSM Default" configured on all four routers and ip pim sparse
> on all the interfaces, including the loopback on the PEs.
>
> I have a VRF configured on PE1 and PE2 that has unicast reachability through
> the VRF and configured with mdt default 232.1.1.1
>
> Here is my main mroute table on all the routers. It's like the MDT defaults
> aren't communicating across the core, so I can't get multicast working
> through the VRF.
>
> When I configure a static RP on P1 and point all the routers to it,
> everything works fine. Is there some nuance with SSM I'm missing because I
> don't see what I'm doing wrong compared to the examples I see everywhere?
>
> PE1#
> Sep 4 14:04:58.438: IP(0): MAC sa=9601.0202.0000 (Loopback0)
> Sep 4 14:04:58.438: IP(0): IP tos=0xC0, len=52, id=24929, ttl=255, prot=47
> Sep 4 14:04:58.438: IP(0): s=150.1.2.2 (Loopback0) d=232.1.1.1 id=24929,
> ttl=255, prot=47, len=52(52), mroute olist null
> PE1#sh 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,
> Z - Multicast Tunnel, z - MDT-data group sender,
> Y - Joined MDT-data group, y - Sending to MDT-data group
> V - RD & Vector, v - Vector
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (150.1.2.2, 232.1.1.1), 00:31:42/00:02:54, flags: sPT
> Incoming interface: Loopback0, RPF nbr 0.0.0.0, RPF-MFD
> Outgoing interface list: Null
>
> (*, 224.0.1.40), 00:32:25/00:02:48, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:32:25/00:02:48
>
>
> P1#sh 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, Z - Multicast
> Tunnel
> Y - Joined MDT-data group, y - Sending to MDT-data group
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 224.0.1.40), 00:35:00/00:02:35, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:35:00/00:02:35
> P2#sh 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,
> Z - Multicast Tunnel, z - MDT-data group sender,
> Y - Joined MDT-data group, y - Sending to MDT-data group
> V - RD & Vector, v - Vector
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 224.0.1.40), 1d18h/00:02:03, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> GigabitEthernet4/0/1, Forward/Sparse-Dense, 00:07:07/00:00:00
>
> *Sep 4 14:02:44.007: IP(0): s=150.1.5.5 (Loopback0) d=232.1.1.1 id=5434,
> ttl=255, prot=47, len=52(52), mroute olist null
> PE2#sh 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,
> Z - Multicast Tunnel, z - MDT-data group sender,
> Y - Joined MDT-data group, y - Sending to MDT-data group
> V - RD & Vector, v - Vector
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (150.1.5.5, 232.1.1.1), 00:08:46/00:02:46, flags: sPT
> Incoming interface: Loopback0, RPF nbr 0.0.0.0, RPF-MFD
> Outgoing interface list: Null
>
> (*, 224.0.1.40), 00:08:48/00:02:48, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> GigabitEthernet4/0/1, Forward/Sparse-Dense, 00:08:48/00:00:00
>
> Let me know if I can psot more information,
>
> thanks,
>
> Dale
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Oct 04 2008 - 09:26:17 ART