From: Jeff Andiorio (jandiorio@gmail.com)
Date: Wed Mar 11 2009 - 10:18:38 ARST
I am viewing from my phone so I apologize if I missed this. what is
the interface config on r3, vlan 3? are there actual client joining
the groups? I am not able to lab this right now, but I would expect
to see a connected mroute on r3 fr he group.
post the config.
thanks.
jeff
On 3/11/09, naveen M S <navin.ms@gmail.com> wrote:
> Group,
>
> I've been pulling my hairs for almost an hour and no luck. Any pointers to
> whatz going wrong here ? Here is my setup and task details.
>
> *Setup:*
> R5-----+
> / |
> / |
> / |
> vlan3--R3 +----SW2--vlan8
> \ |
> \ |
> \ |
> R1-----+
>
> R1 is RP for groups in range 224.0.0.0/5
> R5 is RP for groups in range 232.0.0.0/5
> SW2 is the MA for all groups
>
> *Task:*
> Vlan-3 on R3 has clients for groups 224.24.24.24 and 232.32.32.32
> Multicast server in vlan-8 is sending traffic for these 2 groups.
> A ping from SW2 (sourced from vlan-8) to these 2 groups must be replied by
> R3.
>
> *Problem:*
> Ping to 224.24.24.24 and 232.32.32.32 fails from SW2 (source ip = vlan-8).
> Am suspecting the RPF failure on R3. A traceroute from R3 to vlan-8 gets
> load balanced between R1 and R5. Configured a static mroute such that R3
> uses R1 as Next Hop towards the vlan-8 source, but no luck.
>
> Rack1R3# *show run | inc mroute*
> ip mroute 156.1.8.0 255.255.255.0 156.1.13.1
>
> Rack1R3# *traceroute 156.1.8.8*
>
> Type escape sequence to abort.
> Tracing the route to 156.1.8.8
>
> 1 156.1.35.5 28 msec
> 156.1.13.1 28 msec
> 156.1.35.5 24 msec
> 2 156.1.18.8 32 msec
> 156.1.58.8 28 msec *
>
> Rack1R3# *show ip route eigrp | ^D*
> D 156.1.8.0/24 [90/2586112] via *156.1.35.5*, 02:11:15,
> Virtual-Access2
> [90/2586112] via *156.1.13.1*, 02:11:15,
> Virtual-Access3
>
> Rack1R3#* show ip pim rp mapping*
> PIM Group-to-RP Mappings
>
> Group(s) 224.0.0.0/5
> RP 150.1.1.1 (?), v2v1
> Info source: 150.1.8.8 (?), elected via Auto-RP
> Uptime: 00:19:29, expires: 00:02:21
> Group(s) 232.0.0.0/5
> RP 150.1.5.5 (?), v2v1
> Info source: 150.1.8.8 (?), elected via Auto-RP
> Uptime: 00:19:29, expires: 00:02:19
> Rack1R3#
> Rack1R3# *show 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
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 224.0.1.39), 00:18:50/stopped, RP 0.0.0.0, flags: D
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Virtual-Access3, Forward/Sparse, 00:18:50/00:00:00
> Virtual-Access2, Forward/Sparse, 00:18:50/00:00:00
>
> (150.1.1.1, 224.0.1.39), 00:00:45/00:02:22, flags: PT
> Incoming interface: Virtual-Access3, RPF nbr 156.1.13.1
> Outgoing interface list:
> Virtual-Access2, Prune/Sparse, 00:00:46/00:02:13
>
> (150.1.5.5, 224.0.1.39), 00:18:51/00:02:11, flags: T
> Incoming interface: Virtual-Access2, RPF nbr 156.1.35.5
> Outgoing interface list:
> Virtual-Access3, Forward/Sparse, 00:18:51/00:00:00
>
> (*, 224.0.1.40), 00:19:18/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Virtual-Access3, Forward/Sparse, 00:19:18/00:00:00
> Virtual-Access2, Forward/Sparse, 00:19:18/00:00:00
> Loopback0, Forward/Sparse, 00:19:18/00:00:00
>
> (150.1.8.8, 224.0.1.40), 00:18:53/00:02:11, flags: LT
> Incoming interface: Virtual-Access2, RPF nbr 156.1.35.5
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:18:53/00:00:00
> Virtual-Access3, Prune/Sparse, 00:02:58/00:00:04
>
> Rack1R3#
> Rack1R3#* show ip pim interface *
>
> Address Interface Ver/ Nbr Query DR DR
> Mode Count Intvl Prior
> 150.1.3.3 Loopback0 v2/S 0 30 1
> 150.1.3.3
> 156.1.35.3 Virtual-Template1 v2/S 0 30 1
> 0.0.0.0
> 156.1.35.3 Virtual-Access2 v2/S 1 30 1
> 0.0.0.0
> 156.1.13.3 Virtual-Template2 v2/S 0 30 1
> 0.0.0.0
> 156.1.13.3 Virtual-Access3 v2/S 1 30 1
> 0.0.0.0
> Rack1R3#
>
>
> Rack1SW2#* traceroute 156.1.13.3*
>
> Type escape sequence to abort.
> Tracing the route to 156.1.13.3
>
> 1 156.1.18.1 0 msec 0 msec 8 msec
> 2 156.1.13.3 25 msec * 25 msec
> Rack1SW2#
> Rack1SW2# *show ip pim interface *
>
> Address Interface Ver/ Nbr Query DR DR
> Mode Count Intvl Prior
> 156.1.58.8 Vlan58 v2/S 1 30 1
> 156.1.58.8
> 156.1.18.8 Vlan18 v2/S 1 30 1
> 156.1.18.8
> 156.1.8.8 Vlan8 v2/S 0 30 1
> 156.1.8.8
> 150.1.8.8 Loopback0 v2/S 0 30 1
> 150.1.8.8
> Rack1SW2#
> Rack1SW2# *ping 224.24.24.24 source 156.1.8.8 repeat 5*
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 224.24.24.24, timeout is 2 seconds:
> Packet sent with a source address of 156.1.8.8
> *.....*
> Rack1SW2#
> Rack1SW2# *ping 232.32.32.32 source 156.1.8.8 repeat 5*
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 232.32.32.32, timeout is 2 seconds:
> Packet sent with a source address of 156.1.8.8
> *.....*
> Rack1SW2#
>
>
> 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 : Mon Apr 06 2009 - 06:44:04 ART