Re: PIM Dense mode RP issue

From: Roy Waterman <roy.waterman_at_gmail.com>
Date: Mon, 30 Nov 2009 21:56:18 +0000

Dont worry bout it :)

From what ive heard/read it was simpler easier to code things this way so
that 224.0.1.40 always appears, regardless of whether pim-sm or dm is being
used.
It has no relevance to PIM DM, its just there :)

Just ignore it.
Plenty more things to worry about in the lab :)

2009/11/30 <ron.wilkerson_at_gmail.com>

> I could never get that group to disappear. I tried to make it disappear
> but even though the routers are not configured for auto rp, that darn group
> still appears.
>
> It would be great if someone knows how to turn it off when auto rp isn't
> being used.
>
>
> -----Original Message-----
> From: Nadeem Rafi <nrafia_at_gmail.com>
> Date: Tue, 1 Dec 2009 00:46:04
> To: Cisco certification<ccielab_at_groupstudy.com>
> Subject: PIM Dense mode RP issue
>
> hi,
> i am running 3 routers on Ethernet link. all the routers are in pim dense
> mode but getting reports and messages for 224.0.1.40. As for as i know
> there
> is no RP in pim dense mode.
>
> R1
> debug ip igmp
> *Mar 1 00:33:06.571: IGMP(0): Received v2 Report on FastEthernet0/0 from
> 155.1.146.6 for 224.0.1.40
> *Mar 1 00:33:06.575: IGMP(0): Received Group record for group 224.0.1.40,
> mode 2 from 155.1.146.6 for 0 sources
> *Mar 1 00:33:06.579: IGMP(0): Cancel report for 224.0.1.40 on
> FastEthernet0/0
> *Mar 1 00:33:06.583: IGMP(0): Updating EXCLUDE group timer for 224.0.1.40
> *Mar 1 00:33:06.583: IGMP(0): MRT Add/Update FastEthernet0/0 for
> (*,224.0.1.40) by 0
>
> RSRack1R1#sh ip igmp interface
> FastEthernet0/0 is up, line protocol is up
> Internet address is 155.1.146.1/24
> IGMP is enabled on interface
> Current IGMP host version is 2
> Current IGMP router version is 2
> IGMP query interval is 60 seconds
> IGMP querier timeout is 120 seconds
> IGMP max query response time is 10 seconds
> Last member query count is 2
> Last member query response interval is 1000 ms
> Inbound IGMP access group is not set
> IGMP activity: 1 joins, 0 leaves
> Multicast routing is enabled on interface
> Multicast TTL threshold is 0
> Multicast designated router (DR) is 155.1.146.6
> IGMP querying router is 155.1.146.1 (this system)
> Multicast groups joined by this system (number of users):
> 224.0.1.40(1)
>
> RSRack1R1#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
> 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:17:48/00:02:47, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> FastEthernet0/0, Forward/Dense, 00:17:48/00:00:00
>
> RSRack1R1#sh ip pim int
>
> Address Interface Ver/ Nbr Query DR DR
> Mode Count Intvl Prior
> 155.1.146.1 FastEthernet0/0 v2/D 2 30 1
> 155.1.146.6
>
> I cannot understand this behaviour any help will be appreciated.
>
> Best Regards,
>
> Nadeem Rafi
>
>
> 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Regards
Roy
Blogs and organic groups at http://www.ccie.net
Received on Mon Nov 30 2009 - 21:56:18 ART

This archive was generated by hypermail 2.2.0 : Tue Dec 01 2009 - 06:36:29 ART