Protocol Independent Multicast-Sparse Mode Guidelines; Pim-Sm And Pim-Ssm Scalability - Avaya 8800 Planning And Engineering, Network Design

Configure passive interfaces only on interfaces that contain potential sources of multicast traffic. If
the interfaces are connected to networks that only have receivers, Avaya recommends that you use
a do not advertise self policy on those interfaces.
Do not attempt to disable a DVMRP interface if multicast receivers exist on that interface.
If you must support more than 512 potential sources on separate local interfaces, configure the vast
majority as passive interfaces. Ensure that only 1 to 5 total interfaces are active DVMRP interfaces.
You can also use passive interfaces to implement a measure of security on the network. For
example, if an unauthorized DVMRP router is attached to the network, a neighbor relationship is not
formed, and thus, no routing information from the unauthorized router is propagated across the
network. This feature also has the convenient effect of forcing multicast sources to be directly
attached hosts.

Protocol Independent Multicast-Sparse Mode guidelines

Protocol Independent Multicast-Sparse Mode (PIM-SM) uses an underlying unicast routing
information base to perform multicast routing. PIM-SM builds unidirectional shared trees rooted at a
Rendezvous Point (RP) router per group and can also create shortest-path trees per source.
PIM-SM navigation
•

PIM-SM and PIM-SSM scalability

• PIM general requirements
• PIM and Shortest Path Tree switchover
• PIM traffic delay and SMLT peer reboot
• PIM-SM to DVMRP connection: MBR
• Circuitless IP for PIM-SM
• PIM-SM and static RP
• Rendezvous Point router considerations
• PIM-SM receivers and VLANs
• PIM network with non-PIM interfaces
PIM-SM and PIM-SSM scalability
PIM-SM and PIM-SSM support VRF-lite. You can configure up to 64 instances of PIM-SM or PIM-
SSM.
You can configure up to 1500 VLANs for PIM.
June 2016
Protocol Independent Multicast-Sparse Mode guidelines
on page 197
on page 198
on page 200
on page 201
on page 201
on page 205
on page 205
on page 208
on page 211
on page 212
Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
197