Brocade Multi-Service IronWare Multicast Configuration Guide (Supporting R05.6.00) - Manual (Page 118)

106 Multi-Service IronWare Multicast Configuration Guide
53-1003032-02
Configuring a static multicast route
1
Configuring a static multicast route
Static multicast routes allow you to control the network path used by multicast traffic. Static
multicast routes are especially useful when the unicast and multicast topologies of a network are
different. You can avoid the need to make the topologies similar by instead configuring static
multicast routes.
NOTE
This feature is not supported for DVMRP.
You can configure more than one static multicast route. The Brocade always uses the most specific
route that matches a multicast source address. Thus, if you want to configure a multicast static
route for a specific multicast source and also configure another multicast static route for all other
sources, you can configure two static routes as shown in the examples below.
To add static routes to multicast router A (refer to Figure 15 ), enter commands such as the
following.
PIMRouterA(config)# ip mroute 207.95.10.0 255.255.255.0 ethernet 1/2 distance 1
PIMRouterA(config)# ip mroute 0.0.0.0 0.0.0.0 ethernet 2/3 distance 1
PIMRouterA(config)# write memory
Syntax: [no] ip mroute ip-addr ethernet slot/portnum|ve num [distance num]
Or
Syntax: [no] ip mroute ip-addr rpf_address rpf-num
The ip-addr command specifies the PIM source for the route.
NOTE
In IP multicasting, a route is handled in terms of its source, rather than its destination.
You can use the ethernet slot/portnum parameter to specify a physical port or the ve num
parameter to specify a virtual interface.
NOTE
The ethernet slot/portnum parameter do not apply to PIM SM.
The distance num parameter sets the administrative distance for the route. When comparing
multiple paths for a route, the Brocade prefers the path with the lower administrative distance.
NOTE
Regardless of the administrative distances, the Brocade always prefers directly connected routes
over other routes.
The rpf_address rpf-num parameter specifies an RPF number.
The example above configures two static multicast routes. The first route is for a specific source
network, 207.95.10.0/24. If the Brocade receives multicast traffic for network 207.95.10.0/24, the
traffic must arrive on port 1/2. The second route is for all other multicast traffic. Traffic from
multicast sources other than 207.95.10.0/24 must arrive on port 2/3.
Figure 15 shows an example of an IP Multicast network. The two static routes configured in the
example above apply to this network. The commands in the example above configure PIM router A
to accept PIM packets from 207.95.10.0/24 when they use the path that arrives at port 1/2, and
accept all other PIM packets only when they use the path that arrives at port 2/3.