Dvmrp Scalability - Avaya 8800 Planning And Engineering, Network Design

DVMRP navigation
•

DVMRP scalability

• DVMRP design guidelines
• DVMRP timer tuning
• DVMRP policies
• DVMRP passive interfaces
DVMRP scalability
IP multicast scaling depends on several factors. Some limitations are related to the system itself (for
example, CPU and memory resources); other limitations are related to your network design.
Scaling information for DVMRP is based on test results for a large network under different failure
conditions. Unit testing of such scaling numbers provides higher numbers, particularly for the
number of IP multicast streams. The numbers specified in this section are recommended for general
network design.
No VLAN IDs restrictions exist as to what can be configured with DVMRP. You can configure up to
500 VLANs for DVMRP. If you configure more than 300 DVMRP interfaces, you require a CPU with
suitable RAM memory. You can use the 8691 SF/CPU, which has 128 MB of RAM, or the 8692 SF/
CPU, which can have up to 256 MB. You can also use the CPU Memory Upgrade Kit to upgrade to
256 MB.
Software Release 4.1 and later supports up to 1200 DVMRP interfaces. Configure most interfaces
as passive DVMRP interfaces and keep the number of active interfaces to under 80. If the number
of DVMRP interfaces approaches the 1200 interface limit, Avaya recommends that you configure
only a few interfaces as active DVMRP interfaces (configure the rest as passive).
The number of DVMRP multicast routes can scale up to 2500 when deployed with other protocols,
such as OSPF or RIP. With the proper use of DVMRP routing policies, your network can support a
large number of routes. For more information about using policies, see
page 193.
The recommended maximum number of active multicast source/group pairs (S,G) is 2000.
Avaya recommends that the number of source subnets multiplied by the number of receiver groups
not exceed 500. If you need more than 500 active streams, group senders into the same subnets to
achieve higher scalability. Give careful consideration to traffic distribution to ensure that the load is
shared efficiently between interconnected switches. For more information, see
Link Trunking considerations
June 2016
on page 191
on page 192
on page 192
on page 193
on page 196
on page 180.
Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
Distance Vector Multicast Routing Protocol guidelines
DVMRP policies on
Multicast and Multi-
191