Login
- Table of Contents
-
- H3C S9500 Operation Manual-Release2132[V2.03]-04 IP Multicast Volume
- 00-1Cover
- 01-Multicast Overview
- 02-Multicast Routing and Forwarding Configuration
- 03-IGMP Snooping Configuration
- 04-IGMP Configuration
- 05-PIM Configuration
- 06-MSDP Configuration
- 07-IPv6 Multicast Routing and Forwarding Configuration
- 08-MLD Snooping Configuration
- 09-MLD Configuration
- 10-IPv6 PIM Configuration
- 11-Multicast VLAN Configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 02-Multicast Routing and Forwarding Configuration | 221.72 KB |
Table of Contents
Chapter 1 Multicast Routing and Forwarding Configuration
1.1 Multicast Routing and Forwarding Overview
1.1.1 Introduction to Multicast Routing and Forwarding
1.3 Configuring Multicast Routing and Forwarding
1.3.1 Enable IP Multicast Routing
1.3.2 Configuration Prerequisites
1.3.3 Configuring Multicast Static Routes
1.3.4 Configuring a Multicast Route Match Rule
1.3.5 Configuring Multicast Load Splitting
1.3.6 Configuring Multicast Forwarding Range
1.3.7 Configuring Multicast Forwarding Table Size
1.4 Displaying and Maintaining Multicast Routing and Forwarding
1.5.1 Multicast Static Route Configuration
1.6 Troubleshooting Multicast Routing and Forwarding
1.6.1 Multicast Static Route Failure
1.6.2 Multicast Data Fails to Reach Receivers
Chapter 1 Multicast Routing and Forwarding Configuration
When configuring multicast routing and forwarding, go to the following sections for information you are interested in:
l Multicast Routing and Forwarding Overview
l Configuring Multicast Routing and Forwarding
l Displaying and Maintaining Multicast Routing and Forwarding
l Troubleshooting Multicast Routing and Forwarding
& Note:
The term "router" in this document refers to a router in a generic sense or an S9500 series routing switch running an IP routing protocol.
1.1 Multicast Routing and Forwarding Overview
1.1.1 Introduction to Multicast Routing and Forwarding
In multicast implementations, multicast routing and forwarding are implemented by three types of tables:
l Each multicast routing protocol has its own multicast routing table, such as PIM routing table.
l The information of different multicast routing protocols forms a general multicast routing table.
l The multicast forwarding table is directly used to control the forwarding of multicast packets.
A multicast forwarding table consists of a set of (S, G) entries, each indicating the routing information for delivering multicast data from a multicast source to a multicast group. If a device supports multiple multicast protocols, its multicast routing table will include routes generated by multiple protocols. The device chooses the optimal route from the multicast routing table based on the configured multicast routing and forwarding policy and installs the route entry into its multicast forwarding table.
1.1.2 RPF Mechanism
When creating multicast routing table entries, a multicast routing protocol uses the reverse path forwarding (RPF) mechanism to ensure multicast data delivery along the correct path.
The RPF mechanism enables devices to correctly forward multicast packets based on the multicast route configuration. In addition, the RPF mechanism also helps avoid data loops caused by various reasons.
I. Implementation of the RPF mechanism
Upon receiving a multicast packet that a multicast source S sends to a multicast group G, the device first searches its multicast forwarding table:
1) If the corresponding (S, G) entry exists, and the interface on which the packet actually arrived is the incoming interface in the multicast forwarding table, the device forwards the packet to all the outgoing interfaces.
2) If the corresponding (S, G) entry exists, but the interface on which the packet actually arrived is not the incoming interface in the multicast forwarding table, the multicast packet is subject to an RPF check.
l If the result of the RPF check shows that the RPF interface is the incoming interface of the existing (S, G) entry, this means that the (S, G) entry is correct but the packet arrived from a wrong path and is to be discarded.
l If the result of the RPF check shows that the RPF interface is not the incoming interface of the existing (S, G) entry, this means that the (S, G) entry is no longer valid. The device replaces the incoming interface of the (S, G) entry with the interface on which the packet actually arrived and forwards the packet to all the outgoing interfaces.
3) If no corresponding (S, G) entry exists in the multicast forwarding table, the packet is also subject to an RPF check. The device creates an (S, G) entry based on the relevant routing information and using the RPF interface as the incoming interface, and installs the entry into the multicast forwarding table.
l If the interface on which the packet actually arrived is the RPF interface, the RPF check is successful and the device forwards the packet to all the outgoing interfaces.
l If the interface on which the packet actually arrived is not the RPF interface, the RPF check fails and the device discards the packet.
II. RPF check
The basis for an RPF check is a unicast route or a multicast static route. A unicast routing table contains the shortest path to each destination address, while a multicast static routing table lists the RPF routing information defined by the user through static configuration. A multicast routing protocol does not rely on a particular type of unicast routes; instead, it relies on the existing unicast routing information or multicast static routes in the device to create multicast routing entries.
When performing an RPF check, the device searches its unicast routing table and multicast static routing table at the same time. The specific process is as follows:
1) The device first chooses an optimal route from the unicast routing table and multicast static routing table:
l The device automatically chooses an optimal unicast route by searching its unicast routing table, using the IP address of the “packet source” as the destination address. The outgoing interface in the corresponding routing entry is the RPF interface and the next hop is the RPF neighbor. The device considers the path along which the packet from the RPF neighbor arrived on the RPF interface to be the shortest path that leads back to the source.
l The device automatically chooses an optimal multicast static route by searching its multicast static routing table, using the IP address of the “packet source” as the destination address. The corresponding routing entry explicitly defines the RPF interface and the RPF neighbor.
2) Then, the device selects one from these two optimal routes as the RPF route. The selection is as follows:
l If configured to use the longest match principle, the device selects the longest match route from the two; if these two routes have the same mask, the route selects the route with a higher priority; if the two routes have the same priority, the device selects the multicast static route.
l If not configured to use the longest match principle, the device selects the route with a higher priority; if the two routes have the same priority, the device selects the multicast static route.
& Note:
The above-mentioned “packet source” can mean different things in different situations:
l For a packet traveling along the shortest path tree (SPT) from the multicast source to the receivers or to the rendezvous point (RP), “packet source” means the multicast source.
l For a packet traveling along the rendezvous point tree (RPT) from the RP to the receivers, “packet source” means the RP.
l For a bootstrap message from the bootstrap router (BSR), “packet source” means the BSR.
For details about the concepts of SPT, RPT and BSR, refer to PIM Configuration in the IP Multicast Volume.
Assume that unicast routes exist in the network and no multicast static routes have been configured on Switch C, as shown in Figure 1-1. Multicast packets travel along the SPT from the multicast source to the receivers. The multicast forwarding table on Switch C contains the (S, G) entry, with POS 5/1/1 as the RPF interface.
l When a multicast packet arrives on POS 5/1/1 of Switch C, as the interface is the incoming interface of the (S, G) entry, the switch forwards the packet to all outgoing interfaces.
l When a multicast packet arrives on POS 5/1/2 of Switch C, as the interface is not the incoming interface of the (S, G) entry, the switch performs an RPF check on the packet: The switch searches its unicast routing table and finds that the outgoing interface to Source (the RPF interface) is POS 5/1/1. This means the (S, G) entry is correct and packet arrived along a wrong path. The RPF check fails and the packet is discarded.
1.1.3 Multicast Static Route
A multicast static route is an important basis for RPF checks. With a multicast static route configured on a device, the device searches the unicast routing table and the multicast static routing table simultaneously in an RPF check, chooses the optimal unicast RPF route and the optimal multicast static route respectively from the routing tables, and uses one of them as the RPF route after comparison. Depending on the application environment, a multicast static route has the following two functions:
I. Changing an RPF route
Typically, the topology structure of a multicast network is the same as that of a unicast network, and multicast traffic follows the same transmission path as unicast traffic does. By configuring a multicast static route for a given multicast source, you can change the RPF route so as to create a transmission path for multicast traffic different from that for unicast traffic.
Figure 1-2 Multicast static route
When no multicast static route is configured, Switch C’s RPF neighbor on the path back to Source is Switch A. In this case, the multicast information from Source travels along the path from Switch A to Switch C, which is the unicast route between the two devices. With a static route configured on Switch C and Switch B as Switch C’s RPF neighbor on the path back to Source, the multicast information from Source travels from Switch A to Switch B and then to Switch C, as shown in Figure 1-2.
II. Creating an RPF route
When a unicast route is blocked, multicast traffic forwarding is stopped due to lack of an RPF route. By configuring a multicast static route for a given multicast source, you can create an RPF route so that a multicast routing entry is created to guide multicast traffic forwarding.
Figure 1-3 Creating an RPF route
As shown in Figure 1-3, the RIP domain and the OSPF domain are unicast isolated from each other. When no multicast static route is configured, the hosts (Receivers) in the OSPF domain cannot receive the multicast packets sent by the multicast source (Source) in the RIP domain. After you configure a multicast static route on Switch C and Switch D, specifying Switch B as the RPF neighbor of Switch C and specifying Switch C as the RPF neighbor of Switch D, the receivers can receive multicast data sent by the multicast source.
& Note:
l A multicast static route only affects RPF check; it cannot guide multicast forwarding. Therefore, a multicast static route is also called an RPF static route.
l A multicast static route is effective only on the multicast router on which it is configured, and will not be advertised throughout the network or redistributed to other routers.
1.2 Configuration Task List
Complete these tasks to configure multicast routing and forwarding:
|
Task |
Remarks |
|
Required |
|
|
Required |
|
|
Optional |
|
|
Optional |
|
|
Optional |
|
|
Optional |
|
|
Optional |
1.3 Configuring Multicast Routing and Forwarding
1.3.1 Enable IP Multicast Routing
Before configuring any Layer 3 multicast functionality, you must enable IP multicast routing.
Follow these steps to enable IP multicast routing:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enable IP multicast routing |
multicast routing-enable |
Required Disable by default |
Caution:
IP multicast does not support the use of secondary IP address segments. Namely, multicast can be routed and forwarded only through primary IP addresses, rather than secondary addresses, even if configured on interfaces.
For details about primary and secondary IP addresses, refer to IP Addressing Configuration in the IP Services Volume.
1.3.2 Configuration Prerequisites
Before configuring multicast routing and forwarding, complete the following tasks:
l Configure a unicast routing protocol so that all devices in the domain are interoperable at the network layer.
l Enable PIM (PIM-DM or PIM-SM).
Before configuring multicast routing and forwarding, prepare the following data:
l The maximum number of downstream nodes for a multicast forwarding table entry
l The maximum number of routing entries in a multicast forwarding table
l The multicast forwarding range
1.3.3 Configuring Multicast Static Routes
Follow these steps to configure a multicast static route
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Configure a multicast static route |
ip rpf-route-static source-address { mask | mask-length } [ protocol [ process-id ] ] [ route-policy policy-name ] { rpf-nbr-address | interface-type interface-number } [ preference preference ] [ order order-number ] |
Required No multicast static route is configured by default. |
Caution:
When configuring a multicast static route, you cannot designate an RPF neighbor by specifying an interface (by means of the interface-type interface-number command argument combination) if the interface type of that device is VLAN-interface; instead, you can designate an RPF neighbor only by specifying an address (rpf-nbr-address).
1.3.4 Configuring a Multicast Route Match Rule
In RPF route selection, the device chooses an optimal route from the multicast static routing table and the unicast routing table respectively, and then selects the superior route from these two routes. RPF route selection falls into two cases:
l If the device is configured to use longest match for RPF route selection, then:
1) The device selects the longest match route from the two routes;
2) If these routes have the same mask, the route with a higher priority will be selected;
3) If these routes have the same priority, the multicast static route will be selected.
l If the device is not configured to use longest match for RPF route selection, then:
1) The route with a higher priority will be selected;
2) If these routes have the same priority, the multicast static route will be selected.
Follow these steps to configure a multicast route match rule:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Configure the device to use the longest match principle for RPF route selection |
multicast longest-match |
Optional The route with the highest priority is selected as the RPF route by default |
1.3.5 Configuring Multicast Load Splitting
Follow these steps to configure multicast load splitting:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Configuring multicast load splitting |
multicast load-splitting { source | source-group } |
Required Disabled by default |
1.3.6 Configuring Multicast Forwarding Range
You can configure a forwarding boundary specific to a particular multicast group on all interfaces that support multicast forwarding. A multicast forwarding boundary sets the boundary condition for the multicast groups in the specified range. If the destination address of a multicast packet matches the set boundary condition, the packet will not be forwarded. Once a multicast boundary is configured on an interface, this interface can no longer forward multicast packets (including packets sent from the local device) or receive multicast packets.
Follow these methods to configure a multicast forwarding range:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter interface view |
interface interface-type interface-number |
— |
|
Configure a multicast forwarding boundary |
multicast boundary group-address { mask | mask-length } |
Required No forwarding boundary by default |
& Note:
Currently, S9500 series routing switches support multicast forwarding boundary configuration in VLAN interface view and POS interface view.
1.3.7 Configuring Multicast Forwarding Table Size
If the configured maximum number of multicast forwarding table entries is smaller than the current value, the forwarding entries in excess are not immediately deleted; instead they will be deleted by the multicast routing protocol running on the device. The device will no longer create new multicast forwarding entries until the number of existing multicast forwarding entries comes down below the configured value.
If the configured maximum number of downstream nodes for a single multicast forwarding entry is smaller than the current number, the downstream nodes in excess are not deleted immediately; instead they must be deleted by the multicast routing protocol. The device will no longer create new multicast forwarding entries for newly added downstream nodes until the number of existing downstream nodes comes down below the configured value.
Follow these steps to configure the multicast forwarding table size:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Configure the maximum number of routing entries in the multicast forwarding table |
multicast forwarding-table route-limit limit |
Optional 512 by default |
|
Configure the maximum number of downstream nodes for a single multicast forwarding table entry |
multicast forwarding-table downstream-limit limit |
Optional 128 by default |
1.4 Displaying and Maintaining Multicast Routing and Forwarding
|
To do... |
Use the command... |
Remarks |
|
View the multicast boundary information |
display multicast boundary [ group-address [ mask | mask-length ] ] [ interface interface-type interface-number ] |
Available in any view |
|
View the multicast forwarding table information |
display multicast forwarding-table [ group-address [ mask { mask | mask-length } ] | source-address [ mask { mask | mask-length } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { { include | exclude | match } { interface-type interface-number | register } } | statistics | slot slot-id ] * [ port-info ] |
Available in any view |
|
Available in any view |
||
|
View the multicast routing table information |
display multicast routing-table [ group-address [ mask { mask | mask-length } ] | source-address [ mask { mask | mask-length } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { { include | exclude | match } { interface-type interface-number | register } } ] * |
Available in any view |
|
View the information of the multicast static routing table |
display multicast routing-table static [ config ] [ source-address { mask-length | mask } ] |
Available in any view |
|
View the RPF route information of the specified multicast source |
display multicast rpf-info source-address [ group-address ] |
Available in any view |
|
Clear forwarding entries from the multicast forwarding table |
reset multicast forwarding-table { { group-address [ mask { mask | mask-length } ] | source-address [ mask { mask | mask-length } ] | incoming-interface { interface-type interface-number | register } } * | all } |
Available in user view |
|
Clear routing entries from the multicast routing table |
reset multicast routing-table { { group-address [ mask { mask | mask-length } ] | source-address [ mask { mask | mask-length } ] | incoming-interface { interface-type interface-number | register } } * | all } |
Available in user view |
Caution:
l The reset command clears the information in the multicast routing table or the multicast forwarding table, and thus may cause failure of multicast transmission.
l When a routing entry is deleted from the multicast routing table, the corresponding forwarding entry will also be deleted from the multicast forwarding table.
l When a forwarding entry is deleted from the multicast forwarding table, the corresponding route entry will also be deleted from the multicast routing table.
1.5 Configuration Examples
1.5.1 Multicast Static Route Configuration
I. Network requirements
l All switches in the network support IP multicast.
l Switch A, Switch B and Switch C run OSPF, and have no unicast routes to Switch D.
l Receiver can receive the multicast data from Source 1 through the path Switch A – Switch B – Switch C.
l Perform the following configuration so that Receiver can receive multicast data from Source 2, which is out of the OSPF domain, through Switch C.
II. Network diagram
Figure 1-4 Network diagram for multicast route configuration
III. Configuration procedure
& Note:
Only the commands related to multicast static route configuration are listed in the configuration procedure.
1) Configure the interface IP addresses and unicast routing protocol for each switch
Configure the IP address and subnet mask for each interface as per Figure 1-4. The detailed configuration steps are omitted here.
Enable OSPF on Switch A, Switch B and Switch C. Ensure the network-layer interoperation among the switches. Ensure that the switches can dynamically update their routing information by leveraging the unicast routing protocol. The specific configuration steps are omitted here.
2) Enable IP multicast routing, and enable PIM on each interface
# Enable IP multicast routing on Switch C, and enable PIM-DM on each interface.
<SwitchC> system-view
[SwitchC] multicast routing-enable
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] pim dm
[SwitchC-Vlan-interface100] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] igmp enable
[SwitchC-Vlan-interface200] pim dm
[SwitchC-Vlan-interface200] quit
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] pim dm
[SwitchC-Vlan-interface300] quit
The configuration on Switch A, Switch B and Switch D is similar to the configuration on Switch C. The specific configuration steps are omitted here.
3) Configure a multicast static route
# Configure a multicast static route on Switch C, specifying Switch D as its RPF neighbor on the route to Source 2.
[SwitchC] ip rpf-route-static 10.220.5.0 255.255.255.0 192.168.3.2
4) Verify the configuration
# Before the above-mentioned multicast static route is configured, Receiver can multicast data from Source 1, but cannot receive multicast data from Source 2. Use the display multicast rpf-info command to view the RPF routes to Source 1 and Source 2 respectively on Switch C.
[SwitchC] display multicast rpf-info 10.110.5.100
RPF information about source 10.110.5.100:
RPF interface: Vlan-interface100, RPF neighbor: 10.110.1.1
Referenced route/mask: 10.110.5.0/24
Referenced route type: igp
Route selection rule: preference-preferred
Load splitting rule: disable
[SwitchC] display multicast rpf-info 10.220.5.100
As shown above, Switch C does not have an RPF route to Source 2.
# After the multicast static route is configured, use the display multicast rpf-info command to view the RPF route to Source 2 again on Switch C.
[SwitchC] display multicast rpf-info 10.220.5.100
RPF information about source 10.220.5.100:
RPF interface: Vlan-interface300, RPF neighbor: 192.168.3.2
Referenced route/mask: 10.220.5.0/24
Referenced route type: multicast static
Route selection rule: preference-preferred
Load splitting rule: disable
As shown above, an RPF route to Source 2 has been established on Switch C.
1.6 Troubleshooting Multicast Routing and Forwarding
1.6.1 Multicast Static Route Failure
I. Symptom
The physic status and link layer status of interfaces are both up, but the multicast static route fails.
II. Analysis
l If the multicast static route is not configured or updated correctly to match the current network conditions, the route entry and the configuration information of a multicast static route do not exist in the multicast routing table.
l If the optimal route if found, the multicast static route may also fail.
III. Solution
1) Use the display multicast routing-table static config command to view the configuration information of multicast static routes to verify that a multicast static route has been correctly configured.
2) In the configuration, you can use the display multicast routing-table static command to view the multicast static route information to verify that a multicast static route has been correctly configured.
3) Check the next hop interface type of the multicast static route. If the interface is a VLAN interface, you can specify an RPF neighbor only by providing its IP address (rpf-nbr-address) rather than an interface type and interface number (interface-type interface-number).
4) Check that the multicast static route matches the specified routing protocol. If a protocol was specified when the multicast static route was configured, enter the display ip routing-table command to check if an identical route was added by the protocol.
5) Check that the multicast static route matches the specified routing policy. If a routing policy was specified when the multicast static route was configured, enter the display route-policy command to check the configured routing policy.
1.6.2 Multicast Data Fails to Reach Receivers
I. Symptom
The multicast data can reach some intermediate devices but fails to reach the last hop device.
II. Analysis
If a multicast forwarding boundary has been configured through the multicast boundary command, any multicast packet will be kept from crossing the boundary.
III. Solution
1) Use the display pim routing-table command to check whether the corresponding (S, G) entries exist on the device. If so, the device has received the multicast data; otherwise, the device has not received the data.
2) Use the display multicast boundary command to view the multicast boundary information on the interfaces. Use the multicast boundary command to change the multicast forwarding boundary setting.
3) In the case of PIM-SM, use the display current-configuration command to check the BSR and RP information.
