Avaya 8800 Planning And Engineering, Network Design page 195

Figure 89: Load balancing with announce policies
Do not advertise self policy examples
Do not advertise self policies are easier to configure than regular announce policies, while providing
a commonly-used policy set. When you enable this feature, DVMRP does not advertise any local
interface routes to its neighbors. However, it still advertises routes that it receives from neighbors.
Because this disables the ability of networks to act as a source of multicast streams, do not enable it
on any routers that are directly connected to senders.
The following figure shows a common use of this policy. Router A is a core router that has no
senders on any of its connected networks. Therefore, it is unnecessary for its local routes to be
visible to remote routers, so Router A is configured not to advertise any local routes. This makes it
purely a transit router. Similarly, Router B is an edge router that is connected only to potential
receivers. None of these hosts are allowed to be a source. Thus, configure Router B in a similar
fashion to ensure it also does not advertise any local routes.
Figure 90: Do not advertise local route policies
Because all multicast streams originate from the data center, Router C must advertise at least some
of its local routes. Therefore, you cannot enable the do not advertise self feature on all interfaces. If
certain local routes (that do not contain sources) should not be advertised, you can selectively
enable do not advertise self policies on a per-interface basis or you can configure announce
policies.
June 2016
Distance Vector Multicast Routing Protocol guidelines
Planning and Engineering — Network Design
Comments on this document? infodev@avaya.com
195