Configuring A Static Multicast Route - Foundry Networks FESX Manual

For example, to set up a boundary, which will deny all multicast group addresses within the 239.x.x.x IP address
range, enter commands such as the following:
FastIron SuperX Router(config)# access-list 1 deny 239.0.0.0 0.255.255.255
FastIron SuperX Router (config)# access-list 1 permit 234.0.0.0 0.255.255.255
FastIron SuperX Router(config)# interface ethernet 1/1
FastIron SuperX Router(config-if-1/1)# ip pim-sparse
FastIron SuperX Router(config-if-1/1)# ip multicast boundary 1
Syntax: [no] ip multicast boundary <access-list-num>
The <access-list-num> parameter defines the ACLs used to set-up the boundaries for multicast traffic packets.
NOTE: Extended ACLs cannot be used in this feature.

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 Layer 3 Switch 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 (see Figure 19.10), enter commands such as the following:
PIMRouterA(config)# ip mroute 1 207.95.10.0 255.255.255.0 interface ethernet 1/2
distance 1
PIMRouterA(config)# ip mroute 2 0.0.0.0 0.0.0.0 interface ethernet 2/3 distance 1
PIMRouterA(config)# write memory
Syntax: mroute <route-num> <ip-addr> interface ethernet [<slotnum>/]<portnum> | ve <num> [distance <num>]
Or
Syntax: mroute <route-num> <ip-addr> rpf_address <rpf-num>
The <route-num> parameter specifies the route number.
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 [<slotnum>/]<portnum> parameter to specify a physical port or the ve <num> parameter
to specify a virtual interface.
NOTE: The ethernet [<slotnum>/]<portnum> parameter does not apply to PIM SM.
The distance <num> parameter sets the administrative distance for the route. When comparing multiple paths for
a route, the Layer 3 Switch prefers the path with the lower administrative distance.
NOTE: Regardless of the administrative distances, the Layer 3 Switch always prefers directly connected routes
over other routes.
The rpf_address <rpf-num> parameter specifies an RPF number.
December 2005 © Foundry Networks, Inc.
Configuring IP Multicast Protocols
19 - 63