PIM expects packets to arrive on the reverse-path forwarding (RPF) interface - the interface used to reach the source of the multicast data. PIM also checks the RPF to learn which interface it should use to send join/prune messages. By default, PIM checks the unicast routing table to identify the RPF interface. Static multicast routes provide an alternative route table to use for the RPF check. If a static multicast route and a unicast route are available for a specific destination, PIM uses the static multicast route.
Static multicast routes let PIM be independent of unicast routing. This lets you deploy topologies in which multicast and unicast traffic flow over different paths. For example, in order to balance the traffic load, you can separate the HTTP traffic from the stock quotes traffic. You simply configure a static multicast route to the source network that specifies a next hop gateway address different from the next hop address (for the same source) in the unicast routing table.
Note - PIM is the only protocol that uses static multicast routes. |
You can configure static multicast routes through the Portal or through the CLI.
In Gaia Portal, you can add, delete, and edit static multicast routes.
To add a static multicast route:
The Add Destination Route window opens
To delete a static multicast route:
To edit a static multicast route:
The Edit Destination Route window opens.
In Gaia Clish, you can add, delete, and verify static multicast routes.
To add or delete a static multicast route:
Run this command:
set static-mroute {<
Sender_IP>/<
mask> | default}
off
nexthop gateway address <
Gateway_IP>
[priority <
priority_value>] on
off
Parameter |
Description |
---|---|
|
The address and the network mask of the multicast sender. |
|
The default gateway to use for FPF lookups. |
|
The IP address of the gateway router. |
|
Valid values are 1 through 8. Defines the order of priority in which the nexthop gateway is selected, when multiple nexthop gateways are configured. Lower priority value takes higher preference. If not priority is defined, the default value of 1 is assigned. If multiple gateways are configured with the same priority value, the one with the lower IP address takes higher preference. |
|
Installs the specified multicast static route in the routing table. |
|
Removes the specified multicast static route from the routing table. |
To verify static multicast routes:
Run this command: show static-mroute
To show static multicast routes configuration:
Run this command: show configuration static-mroute