Foundry Configuration Guide for the FESX, FSX, and FWSX
19 - 64 © Foundry Networks, Inc. December 2005
The example above configures two static multicast routes. The first route is for a specific source network,
207.95.10.0/24. If the Layer 3 Switch 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 19.10 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.
The distance parameter sets the administrative distance. This parameter is used by the software to determine the
best path for the route. Thus, to ensure that the Layer 3 Switch uses the default static route, assign a low
administrative distance value. When comparing multiple paths for a route, the Layer 3 Switch prefers the path with
the lower administrative distance.
Figure 19.10 Example multicast static routes
To add a static route to a virtual interface, enter commands such as the following:
FastIron SuperX Router(config)# mroute 3 0.0.0.0 0.0.0.0 int ve 1 distance 1
FastIron SuperX Router(config)# write memory
Tracing a Multicast Route
The Foundry implementation of Mtrace is based on “A ‘traceroute’ facility for IP Multicast”, an Internet draft by S.
Casner and B. Fenner. To trace a PIM route, use the following CLI method.
Server
Client
e1/4
207.95.7.1
Multicast group
239.255.162.1
e1/5
207.95.8.10
e4/1
207.95.6.1
e3/11
Multicast group
239.255.162.1
e1/8
207.95.8.1
e2/3
207.95.7.2
e1/2
207.95.6.2
Client
9.9.9.101
Multicast group
239.255.162.1
8.8.8.164
209.157.24.62
e6/14
PIM router D
PIM router B
PIM router C
PIM router A
To Next Page
Loading...
Need help?
General
