From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Thu Jan 12 2006 - 12:18:55 GMT-3
Rionaldi -
RPs are only needed in Sparse mode. The first example is a static RP,
which you are limited it being the RP for specific groups defined by
your ACL. Also, it is my understanding that you do not want to use the
deny statement in for these ACL, since multicast has issues (some of the
experts to speak to why that is better than I). I just know that there
are issues with this and using the filter on the mapping agent.
The second is an auto-RP, which will take precedence over the statically
configured RP. The 39 and 40 are always sent dense mode.
Hope this helps.
Dave Schulz,
Email: dschulz@dpsciences.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Prio Utomo
Sent: Thursday, January 12, 2006 7:44 AM
To: ccielab@groupstudy.com
Subject: Confuse between Sparse & Dense
I read somewhere that multicast traffic transmission can be determined
as
sparse or dense not by what the interface configuration is whether ip
pim
sparse, ip pim dense, or ip pim sparse-dense.... but whether they can
find
RP or not, if can they will be sparse if not it will be dense... correct
me
if I am wrong.
I would like to know the meaning of this command then:
ip pim rp-add x.x.x.x 12
access-list 12 permit 239.1.1.1 ------> sparse ?
access-list 12 deny 239.2.2.2 ------> sparse ?
access-list 12 deny 224.0.1.39 ------> dense?
access-list 12 deny 224.0.1.40 ------> dense?
-----------------------------------------
ip pim send-rp-announce Loopback0 scope 10 group-list 45
ip pim send-rp-discovery scope 10
access-list 45 permit 224.0.0.0 0.255.255.255 ------> sparse ?
access-list 45 permit 227.0.0.0 0.255.255.255 ------> sparse ?
access-list 45 deny 225.0.0.0 0.255.255.255 ------> dense?
Regards,
rionaldi
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:48 GMT-3