From: ccie (ccie@tisolutions.biz)
Date: Fri Nov 26 2004 - 14:16:12 GMT-3
Hi Scott
Thanks for the speedy reply and excellent response
Cheers
Mark
-----Original Message-----
From: Scott Morris [mailto:swm@emanon.com]
Sent: Fri 11/26/2004 3:30 PM
To: ccie; ccielab@groupstudy.com
Cc:
Subject: RE: stub ip multicast
This is normal behavior. R1 is the last "real" PIM neighbor due to the pim
neighbor-filter. This means that it will perform the function of an IGMP
listener for downstream networks. If R1 still saw R5 as a pim neighbor,
then any received IGMP requests from that direction would be discarded.
R5 on the other hand, still needs to at least be vaguely aware of R1 on the
PIM end. Otherwise, received PIM information and multicast stuff would not
be properly processed. Don't forget about the igmp helper-address that
forwards requests from R5's ethernet-side back to R1.
HTH,
Scott Morris, MCSE, CCDP, CCIE4 (R&S/ISP-Dial/Security/Service Provider)
#4713, JNCIP, CCNA-WAN Switching, CCSP, Cable Communications Specialist, IP
Telephony Support Specialist, IP Telephony Design Specialist, CISSP
CCSI #21903
swm@emanon.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of ccie
Sent: Friday, November 26, 2004 10:04 AM
To: ccielab@groupstudy.com
Subject: stub ip multicast
Hi All
When you create a ip multicast stub using the ip pim neighbor-filter command
does it work in both directions, for example:
R5---------------------R1
R1 is configured to prevent R5 becoming a pim neighbor. Which is fine,
using the sh ip pim neighbors command R5 is not present.
But on R5 using the show ip pim neighbors R1 is present..!!!!!
Is this normal behavour
Thanks
Mark
This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:50 GMT-3