From: ccie2be (ccie2be@nyc.rr.com)
Date: Sun May 01 2005 - 17:54:54 GMT-3
Long,
When pim is enabled on an interface, that interface is either in the
outgoing interface list (OIL) or it isn't.
In the case of downstream pim neighbors with receivers over a multipoint
interface (physical or sub, it doesn't matter), a mcast traffic flow will
either go to all downstream neighbors or none because of the above point.
But, suppose you want mcast traffic to go to just one downstream spoke
neighbor?
That's where ip pim nbma comes in. Now, instead of the interface either
being on the OIL or not, the OIL will include a reference to the particular
spoke that should be getting mcast traffic.
There's a bit more to this, but if you remember this, you'll be OK.
HTH, Tim
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Long
Kwok
Sent: Sunday, May 01, 2005 3:02 PM
To: ccielab@groupstudy.com
Subject: Multicast "ip pim nbma-mode" Scenarios
The "ip pim nbma-mode" from what I understand is used to change the
queuing mechanism on a frame-relay configured interface , and to also
change the way that a hub router with multicast enabled reacts to
dense-mode receivers prune messages ? So then exactly in what scenarios
is ip pim nbma-mode required ? Would it be safe to say if I have a
partially meshed frame-relay topology with say R1 the hub and R2 through
R6 possible receivers , would you always put ip pim nbma-mode on R1's
serial interface , in either sparse or sparse-dense mode ?
TIA , Long
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:56 GMT-3