Configuration Guide - IP Multicast(V800R002C01_01)

8/10/2019 Configuration Guide - IP Multicast(V800R002C01_01)

1/344


2/344


3/344


4/344


5/344


6/344


7/344


8/344


9/344


10/344


11/344


12/344


13/344


14/344


15/344


16/344


17/344


18/344


19/344


20/344


21/344


22/344


23/344


24/344


25/344


26/344


27/344


28/344


29/344


30/344


31/344


32/344


33/344


34/344


35/344


36/344


37/344


38/344


39/344


40/344


41/344


42/344


43/344


44/344


45/344


46/344


47/344


48/344


49/344


50/344


51/344


52/344


53/344


54/344


55/344


56/344


57/344


58/344


59/344


60/344


61/344


62/344


63/344


64/344


65/344


66/344


67/344


68/344


69/344


70/344


71/344


72/344


73/344


74/344


75/344


76/344


77/344


78/344


79/344


80/344


81/344


82/344


83/344


84/344


85/344


86/344


87/344


88/344


89/344


90/344


91/344


92/344


93/344


94/344


95/344

Join-Prune 3686 0 0 0

State-Refresh 0 0 0 0

BSR 0 0 0 0

3.8 Configuring PIM BFDAfter detecting a fault on the peer, BFD immediately notifies the PIM module to trigger a newDR election rather than waits until the neighbor relationship times out. This shortens the periodduring which multicast data transmission is discontinued and thus improves the reliability of multicast data transmission.

Applicable Environment

Generally, if the current DR in a shared network segment is faulty, other PIM neighbors triggersa new round of DR election only after the neighbor relationship times out. The duration that datatransmission is interrupted is not shorter than the timeout period of the neighbor relationship.Generally, it is of second level.

BFD features fast detection of faults, and is up to the millisecond level. BFD can detect statusesof PIM neighbors in the shared network segment. When BFD detects that a peer is faulty, BFDimmediately reports it to PIM. PIM then triggers a new round of DR election without waitingfor the timeout of the neighbor relationship. This shortens the duration of interruption of datatransmission and e nhances the reliability of the network.

PIM BFD is also applicable to the assert election in a shared network segment. It can fast respondto the fault of the interface that wins the assert election.

Pre-configuration Tasks

Before adjusting other PIM parameters, complete the following tasks:

l Configuring a unicast routing protocol to ensure normal unicast routing on the network l Configuring PIM-SMl Enabling BFD Globally

Configuration Procedures

You can choose to perform some of the following configuration tasks (except "Checking theConfiguration") according to the applicable environment.

3.8.1 Enabling PIM BFDEnable PIM BFD on the devices that set up a PIM neighbor relationship.

ContextNOTE

This function is applicable to NBMA interfaces and broadcast interfaces rather than MTunnel interfaces.

Do as follows on PIM routers that set up the neighbor relationship:

HUAWEI NetEngine5000E Core Router Configuration Guide - IP Multicast 3 PIM Configuration

Issue 01 (2011-10-15) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

85


96/344

Procedure

Step 1 Run:system-view

The system view is displayed.

Step 2 Run:interface interface-type interface-number

The interface view is displayed.

Step 3 Run: pim bfd enable

PIM BFD is enabled.

By default, PIM BFD is disabled.

----End

3.8.2 (Optional) Adjusting BFD ParametersYou can adjust PIM BFD parameters as required. PIM BFD parameters include the minimuminterval for sending and receiving PIM BFD packets and the local detection multiplier.

Context

Do as follows on two PIM routers that set up the neighbor relationship:

ProcedureStep 1 Run:

system-view

The system view is displayed.

Step 2 Run:interface interface-type interface-number

The interface view is displayed

Step 3 Run: pim bfd { min-tx-interval tx-value | min-rx-interval rx-value | detect-multiplier

multiplier-value } *

PIM BFD parameters are adjusted.

PIM BFD parameters include the minimum interval for sending PIM BFD messages, theminimum interval for receiving PIM BFD messages, and the local detection multiple.

By default, the min-tx-interval value is 100 ms, the min-rx-interval value is 100 ms, and thedetect-multiplier value is 3.

When the BFD parameters configured for other protocols are the same as those configured for PIM, the configurations of the PIM BFD parameters are affected.

----End



86


97/344

3.8.3 Checking the ConfigurationAfter PIM BFD is configured, you can run the command to check information about PIM BFDsessions.

Procedurel Run the following commands to check information about a PIM BFD session.

display pim [ vpn-instance vpn-instance-name | all-instance ] bfd session statistics display pim [ vpn-instance vpn-instance-name | all-instance ] bfd session

[ interface interface-type interface-number | neighbor neighbor-address ] *

----End

Example

Run the display pim all-instance bfd session command, and you can view the information aboutPIM BFD sessions. For example:

display pim all-instance bfd session All-instance: Total 4 BFD sessions Created VPN-Instance: public net Total 4 BFD sessions Created Ethernet6/2/2 (10.1.2.2): Total 2 BFD sessions Created Neighbor ActTx(ms) ActRx(ms) ActMulti Local/Remote State 10.1.2.3 20 20 5 8756/8652 Up 10.1.2.4 30 30 3 8754/8423 Up Ethernet2/0/0 (10.20.1.20): Total 2 BFD sessions Created Neighbor ActTx(ms) ActRx(ms) ActMulti Local/Remote State

10.20.1.30 30 30 5 8327/8891 Up 10.20.1.40 50 50 3 8358/8942 Up

3.9 Maintaining PIMMaintaining PIM involves resetting PIM statistics, monitoring PIM running status, anddebugging PIM.

3.9.1 Clearing Statistics of PIM Control MessagesIf you need to re-collect the statistics about PIM control messages, you can reset the existent

statistics. Note that the statistics cannot be restored after you reset them. This operation does notaffect normal running of PIM.

Context

CAUTION

Statistics of PIM control messages on an interface cannot be restored after you clear them. So,confirm the action before you use the command.



87


98/344

Procedure

Step 1 After confirming that you need to clear statistics about PIM control messages, run the resetpim [ vpn-instance vpn-instance-name | all-instance ] control-message counters [ interface

interface-type interface-number ] command in the user view.----End

3.9.2 Monitoring the Running Status of PIMYou can monitor the PIM running by checking unicast routes, the BSR, and the RP used by PIM,statistics about PIM control messages, and information about PIM neighbors and the PIM routingtable.

Context

In routine maintenance, you can run the following commands in any view to view the runningof PIM.

Procedurel Run the display pim [ vpn-instance vpn-instance-name | all-instance ] claimed-route

[ source-address ] command in any view to check information about the unicast routes used by PIM.

l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] bsr-info commandin any view to check information about the BSR in the PIM-SM domain.

l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] control-message counters [ interface interface-type interface-number | message-type message-type ] * command in any view to check statistics about PIM control messages.

l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface[ interface-type interface-number ] [ verbose ] command in any view to check informationabout the PIM interface.

l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] neighbor[ neighbor-address | interface interface-type interface-number ] [ verbose ] command inany view to check information about the PIM neighbor.

l Run the display pim routing-table command in any view to check information about thePIM routing table.

display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table [ group-address [ mask { group-mask-length | group-mask } ] ] [ source-address [ mask { source-mask-length | source-mask } ] ] [ outgoing-interface include { interface-type interface-number | register | none } ] [ fsm ]

display pim routing-table [ group group-address [ mask { group-mask-length | group-mask } ] ] source source-address [ mask { source-mask-length | source-mask } |outgoing-interface include { interface-type interface-number | register } ] [ fsm ]

l Run the display pim [ vpn-instance vpn-instance-name | all-instance ] rp-info [ group-address ] command in any view to check information about the RP serving the multicastgroup.

----End



88


99/344

3.10 Configuration ExamplesConfiguration examples are provided to tell you how to construct a basic PIM network andconfigure basic functions of PIM.

3.10.1 Example for Configuring PIM-SM Intra-domain MulticastIn an AS with reachable unicast routes, you can enable basic functions of PIM-SM so that hostscan receive multicast data from any multicast source.

Networking Requirements

CAUTION

For the NE5000E, the interface is numbered as slot number/card number/interface number. For the NE5000E cluster, the interface is numbered as chassis ID/slot number/card number/interfacenumber. The slot number is chassis ID/slot ID.

It is required to deploy multicast services on the ISP network shown in Figure 3-4 . The integratedInterior Gateway Protocol (IGP) has been deployed on the network. The unicast routes work normally so that routers can access the Internet. In such a scenario, hosts on the network requireto receive the Video On Demand (VOD) information through multicast services.

Figure 3-4 Networking diagram for configuring PIM-SM intra-domain multicast

RouterA Ethernet

Ethernet

Source

Ethernet

RouterBRouterC

PIM-SM

RouterD

Leaf networks

Receiver HostA

Receiver HostB

N1

N2

GE2/0/0

POS1/0/0

GE2/0/0POS2/0/0

POS2/0/0

GE1/0/0

GE3/0/0

POS1/0/0

POS3/0/0

POS1/0/0

POS1/0/0

POS4/0/0

POS2/0/0RouterE

POS3/0/0

POS4/0/0

Device Interface IP Address Device Interface IP Address

Router A POS 1/0/0 192.168.9.1/24 Router D POS 1/0/0 192.168.4.2/24

POS 3/0/0 192.168.1.1/24 POS 2/0/0 192.168.1.2/24

GE 2/0/0 10.110.1.1/24 POS 4/0/0 10.110.4.1/24

Router B POS 1/0/0 192.168.2.1/24 GE 3/0/0 10.110.5.1/24

GE 2/0/0 10.110.2.1/24 Router E POS 1/0/0 192.168.3.2/24

Router C POS 2/0/0 192.168.3.1/24 POS 2/0/0 192.168.2.2/24



89


100/344

GE 1/0/0 10.110.2.2/24 POS 3/0/0 192.168.9.2/24

POS 4/0/0 192.168.4.1/24

Configuration NotesWhen configuring PIM-SM intra-domain multicast, pay attention to the following points:

l PIM-SM and IGMP need to be enabled in sequence on the interfaces connecting therouters to hosts. That is, enable PIM-SM first and then IGMP.

l If the static RP need be used, you need to configure a same static RP on all the routers.l If hosts want to receive multicast data from specific sources, enable PIM-SSM. You must

ensure that the SSM group address ranges set on all the routers are the same.

Configuration RoadmapThe ISP network access the Internet. To simplify service expansion, you can configure PIM-SMto provide multicast services on the network.

1. Configure an IP address for each interface on the routers and configure a unicast routing protocol.

2. Enable multicast routing on all the multicast routers.

3. Enable PIM-SM on all the interfaces of multicast routers.

4. Enable IGMP on the interface that directly connects the router to hosts.

5. Configure an RP. On a PIM-SM network, the RP is a root node of an RPT. It isrecommended to configure the RP on the router with more multicast flow branches. Asshown in Figure 3-4 , Router E is configured as an RP.

6. (Optional) Configure BSR boundaries on the interfaces connected to the Internet. Bootstrapmessages cannot pass t hrough the BSR boundaries and each BSR serves only the localPIM-SM domain. In this manner, multicast services can be controlled effectively.

7. (Optional) Set the same SSM group address range on all the routers. In this manner, themulticast router in the PIM-SM domain provides services only for the multicast groups inthe SSM group address range.

Data PreparationTo complete the configuration, you need the following data:

l Multicast group addressl Multicast source addressl SSM group address range

Procedure

Step 1 Configure an IP address for each interface on the routers and configure a unicast routing protocol.The detailed configuration procedures are not mentioned here.

Step 2 Enable the multicast function on all the routers and enable PIM-SM on each interface.

# Take Router E as an example. Configurations on Router A, Router B, Router C, and Router D are similar to those on Router E and hence are not mentioned here.



90


101/344

[~RouterE] multicast routing-enable[~RouterE] interface pos 1/0/0[~RouterE-Pos1/0/0] pim sm [~RouterE-Pos1/0/0] quit[~RouterE] interface pos 2/0/0[~RouterE-Pos2/0/0] pim sm

[~RouterE-Pos21/0/0] quit[~RouterE] interface pos 3/0/0[~RouterE-Pos3/0/0] pim sm [~RouterE-Pos3/0/0] quit[~RouterE] interface pos 4/0/0[~RouterE-Pos4/0/0] pim sm [~RouterE-Pos4/0/0] commit[~RouterE-Pos4/0/0] quit

Step 3 Enable IGMP on the interfaces connected with hosts.

# Take Router A as an example. Configurations on Router B and Router C are similar to thoseon Router A and hence are not mentioned here.

[~RouterA] interface gigabitethernet 2/0/0[~RouterA-GigabitEthernet2/0/0] igmp enable[~RouterA-GigabitEthernet2/0/0] igmp version 3[~RouterA-GigabitEthernet2/0/0] commit[~RouterA-GigabitEthernet2/0/0] quit

Step 4 Configure an RP.NOTE

You can configure both the static RP and BSR RP or either of them. If both the static RP and BSR RP areconfigured, the BSR RP is preferred. You can configure the static RP to be used preferentially by specifyingthe keyword preferred in the static-rp rp-address command.

The following shows how to configure both the static RP and BSR RP, with the BSR RP being preferredand the static RP being the backup.

# Configure a BSR RP. You need to perform the following configurations on one or severalrouters in the PIM-SM domain. Here, take Router E as an example to show how to set the servicerange of the RP and how to configure the C-BSR and the C-RP.

[~RouterE] acl number 2000[~RouterE-acl4-basic-2000] rule permit source 225.1.1.0 0.0.0.255[~RouterE-acl4-basic-2000] quit[~RouterE] pim [~RouterE-pim] c-bsr pos 2/0/0[~RouterE-pim] c-rp pos 2/0/0 group-policy 2000 priority 0[~RouterE-pim] commit[~RouterE-pim] quit

# Configure a static RP. You can perform the following configurations on all multicast routers.Take Router E as an example. Configurations on Router A, Router B, Router C, and Router Dare similar to those on Router E and hence are not mentioned here.

[~RouterE] pim [~RouterE-pim] static-rp 192.168.4.1[~RouterE-pim] commit[~RouterE-pim] quit

Step 5 (Optional) Configure a BSR boundary on the interface connecting Router D to the Internet.[~RouterD] interface pos 4/0/0[~RouterD-Pos4/0/0] pim bsr-boundary[~RouterD-Pos4/0/0] commit[~RouterD-Pos4/0/0] quit

Step 6 (Optional) Set the SSM group address range.



91


102/344

# Set the SSM group address range to 232.1.1.0/24 on all the routers. Take Router E as anexample. Configurations on Router A, Router B, Router C, and Router D are the same as thoseon Router E and hence are not mentioned here.

[~RouterE] acl number 2001

[~RouterE-acl4-basic-2001] rule permit source 232.1.1.0 0.0.0.255[~RouterE-acl4-basic-2001] quit[~RouterE] pim [~RouterE-pim] ssm-policy 2001[~RouterE-pim] commit[~RouterE-pim] quit

Step 7 Verify the configuration.

# Run the display pim interface command to view information about the PIM interfaces on therouters. For example, information about the PIM interface on Router E is as follows:

display pim interfaceVPN-Instance: public netInterface State NbrCnt HelloInt DR-Pri DR-AddressPos1/0/0 up 1 30 1 192.168.3.2Pos3/0/0 up 1 30 1 192.168.9.2Pos4/0/0 up 1 30 1 192.168.4.2Pos2/0/0 up 1 30 1 192.168.2.2

# Run the display pim bsr-info command to view information about the BSRs on the routers.For example, information about the BSRs on Router D and Router E is as follows. Informationabout the C-BSR on Router E is also displayed.

display pim bsr-info VPN-Instance: public net Elected AdminScope BSR Count: 0 Elected BSR Address: 192.168.2.2 Priority: 0 Hash mask length: 30

State: Accept Preferred Scope: Not scoped Uptime: 02:08:57 Expires: 00:01:15 C-RP Count: 1 display pim bsr-info VPN-Instance: public net Elected AdminScope BSR Count: 0 Elected BSR Address: 192.168.2.2 Priority: 0 Hash mask length: 30 State: Elected Scope: Not scoped Uptime: 02:25:03 Next BSR message scheduled at: 00:00:57 C-RP Count: 1 Candidate AdminScope BSR Count: 0 Candidate BSR Address: 192.168.2.2 Priority: 0 Hash mask length: 30 State: Elected Scope: Not scoped Wait to be BSR: 0

# Run the display pim rp-info command to view information about the RPs on the routers. For example, information about the RPs on Router D andRouter E is as follows:

display pim rp-info VPN-Instance: public net PIM-SM BSR RP information: Group/MaskLen: 225.1.1.0/24

RP: 192.168.2.2 Priority: 0



92


103/344

Uptime: 02:27:17 Expires: 00:02:15 PIM SM static RP information: Static RP: 192.168.4.1 display pim rp-info VPN-Instance: public net

PIM-SM BSR RP information: Group/MaskLen: 225.1.1.0/24 RP: 192.168.2.2 (local) Priority: 0 Uptime: 02:27:27 Expires: 00:02:03 PIM SM static RP information: Static RP: 192.168.4.1 (local)

# Run the display pim routing-table command to view information about the PIM routing tableson the routers. Host A needs to receive the data for multicast group 225.1.1.1/24 and host Bneeds to receive the data sent from source 10.110.5.100/24 to group 232.1.1.1/24. For example,information about the PIM routing tables on Router D andRouter E is as follows:

display pim routing-table

VPN-Instance: public net Total 0 (*, G) entry; 2 (S, G) entries

(10.110.5.100, 225.1.1.1) RP: 192.168.2.2 Protocol: pim-sm, Flag: SPT LOC ACT UpTime: 00:57:20 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: NULL RPF prime neighbor: 10.110.5.100 Downstream interface(s) information: Total number of downstreams: 1 1: Pos2/0/0 Protocol: pim-sm, UpTime: 00:57:20, Expires: 00:03:02

(10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: LOC UpTime: 00:31:21 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: NULL RPF prime neighbor: 10.110.5.100 Downstream interface(s) information: Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-ssm, UpTime: 00:31:21, Expires: 00:03:09 display pim routing-table

VPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry

(*, 225.1.1.1) RP: 192.168.2.2 (local) Protocol: pim-sm, Flag: WC UpTime: 00:21:40 Upstream interface: register Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Pos3/0/0 Protocol: pim-sm, UpTime: 00:21:40, Expires: 00:02:43

(10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:18:44

Upstream interface: Pos4/0/0 Upstream neighbor: 192.168.4.2



93


104/344

RPF prime neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-ssm, UpTime: 00:18:44, Expires: 00:02:43

----End

Configuration Filesl Configuration file of Router A

#sysname RouterA#multicast routing-enable#acl number 2001 rule 5 permit source 232.1.1.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0001.00#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.1.1 255.255.255.0 pim sm igmp enable igmp version 3 isis enable 1#interface Pos1/0/0 undo shutdown link-protocol ppp ip address 192.168.9.1 255.255.255.0 pim sm

isis enable 1#interface Pos3/0/0 undo shutdown link-protocol ppp ip address 192.168.1.1 255.255.255.0 pim sm isis enable 1#pim ssm-policy 2001 static-rp 192.168.4.1#return

l Configuration file of Router B#sysname RouterB#multicast routing-enable#acl number 2001 rule 5 permit source 232.1.1.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0002.00#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.2.1 255.255.255.0 pim sm

igmp enable igmp version 3



94


105/344

isis enable 1#interface Pos1/0/0 undo shutdown link-protocol ppp ip address 192.168.2.1 255.255.255.0

pim sm isis enable 1#pim ssm-policy 2001 static-rp 192.168.4.1#return

l Configuration file of Router C#sysname RouterC#multicast routing-enable#acl number 2001 rule 5 permit source 232.1.1.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0003.00#interface GigabitEthernet1/0/0 undo shutdown ip address 10.110.2.2 255.255.255.0 pim sm igmp enable igmp version 3 isis enable 1#interface Pos2/0/0 undo shutdown

link-protocol ppp ip address 192.168.3.1 255.255.255.0 pim sm isis enable 1#pim ssm-policy 2001 static-rp 192.168.4.1 #return

l Configuration file of Router D#sysname RouterD#multicast routing-enable#acl number 2001 rule 5 permit source 232.1.1.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0004.00#interface GigabitEthernet3/0/0 undo shutdown pim sm isis enable 1 ip address 10.110.5.1 255.255.255.0# interface Pos1/0/0 undo shutdown

link-protocol ppp ip address 192.168.4.2 255.255.255.0



95


106/344

pim sm isis enable 1#interface Pos2/0/0 undo shutdown link-protocol ppp

ip address 192.168.1.2 255.255.255.0 pim sm isis enable 1#interface Pos4/0/0 undo shutdown link-protocol ppp ip address 10.110.4.1 255.255.255.0 pim bsr-boundary pim sm isis enable 1#pim ssm-policy 2001 static-rp 192.168.4.1#return

l Configuration file of Router E#sysname RouterE#multicast routing-enable#acl number 2000 rule 5 permit source 225.1.1.0 0.0.0.255#acl number 2001 rule 5 permit source 232.1.1.0 0.0.0.255#isis 1

network-entity 10.0000.0000.0005.00#interface Pos1/0/0 undo shutdown link-protocol ppp ip address 192.168.3.2 255.255.255.0 pim sm isis enable 1#interface Pos2/0/0 undo shutdown link-protocol ppp ip address 192.168.2.2 255.255.255.0 pim sm isis enable 1#interface Pos3/0/0 undo shutdown link-protocol ppp ip address 192.168.9.2 255.255.255.0 pim sm isis enable 1# interface Pos4/0/0 link-protocol ppp ip address 192.168.4.1 255.255.255.0 pim sm isis enable 1#pim ssm-policy 2001

static-rp 192.168.4.1 c-bsr Pos2/0/0



96


107/344

c-rp Pos2/0/0 group-policy 2000#return

3.10.2 Example for Configuring a PIM-SM BSR AdministrativeDomain

On a PIM-SM network where a dynamic RP is used, configuring a BSR administrative domainenables C-BSRs to serve groups in a specified group address range.


CAUTION


As shown in Figure 3-5 , multicast services are deployed on the ISP network. An IGP has beendeployed to ensure that unicast routes are available. The ISP network is connected to the Internet.The router must be properly configured so that the hosts on the network can receive VODinformation in multicast mode.

Figure 3-5 Networking diagram for configuring a PIM-SM BSR administrative domain

RouterA Ethernet

Ethernet

Source

Ethernet

RouterBRouterC

PIM-SM

RouterD

Leaf networks

Receiver HostA

Receiver HostB

N1

N2

GE2/0/0

POS1/0/0

GE2/0/0POS2/0/0

POS2/0/0

GE1/0/0

GE3/0/0

POS1/0/0

POS3/0/0

POS1/0/0

POS1/0/0

POS4/0/0

POS2/0/0RouterE

POS3/0/0

POS4/0/0

Device Interface IP Address

Router A POS 1/0/0 192.168.9.1/24

POS 3/0/0 192.168.1.1/24

GE 2/0/0 10.110.1.1/24

Router B POS 1/0/0 192.168.2.1/24

GE 2/0/0 10.110.2.1/24

Router C POS 2/0/0 192.168.3.1/24

GE 1/0/0 10.110.2.2/24

Router D POS 1/0/0 192.168.4.2/24

POS 2/0/0 192.168.1.2/24



97


108/344

POS 4/0/0 10.110.4.1/24

GE 3/0/0 10.110.5.1/24

Router E POS 1/0/0 192.168.3.2/24

POS 2/0/0 192.168.2.2/24

POS 3/0/0 192.168.9.2/24POS 4/0/0 192.168.4.1/24

Precautions

When configuring a PIM-SM BSR administrative domain, note the following points:

l Unicast routes on the network must be reachable because multicast routing depends onunicast routing.

l Multicast routing needs to be enabled on all routers.l PIM-SM needs to be enabled on the interfaces connecting routers, the inte rface direct ly

connecting the router to the multicast source, and the interface directly connecting therouter to hosts.

l If a static RP is used, the static RP configurations on all the routers must be the same.l IGMP of a supported version needs to be run on the router directly connected to hosts. PIM-

SM and IGMP need to be enabled in sequence (that is, first PIM-SM and then IGMP) onthe interface directly connected to hosts; otherwise, the PIM-SM function fails to beconfigured.

l If users need to receive data sent by a specified multicast source, PIM-SSM needs to beenabled and the same SSM group address range needs to be configured on all the routers.

Configuration Roadmap

The ISP network access the Internet. To simplify service expansion, you can configure PIM-SMto provide multicast services on the network.


2. Enable multicast routing on all routers providing multicast services.



5. Configure RPs. An RP is the root node of an RPT on a PIM-SM network. Setting an RPon the router that has more branches, for example, Router E in Figure 3-5 , is recommended.

6. (Optional) Set a BSR boundary on the interface connected to the Internet. Bootstrapmessages cannot pass through the BSR boundary. Therefore, the BSR serves only aspecified PIM-SM domain. This increases multicast controllability.

7. (Optional) Configure the same SSM group address range on each router. This enables themulticast routers in the PIM-SM domain to provide services only for multicast groups inthe SSM group address range.

Data Preparation

To complete the configuration, you need the following data:



98


109/344

l Multicast group address (225.1.1.1/24)l Multicast source address (10.110.5.100/24)l SSM group address range (232.1.1.0/24)

Procedure

Step 1 Configure an IP address for each interface on the routers and configure a unicast routing protocol.

Step 2 Enable multicast on each device and PIM-SM on each interface of the devices.

# Enable multicast on each router and PIM-SM on each interface of the routers. Theconfigurations of Router B, Router C, Router D, and Router E are similar to those on Router A,and are not provided here.

[~RouterA] multicast routing-enable[~RouterA] interface gigabitethernet 2/0/0[~RouterA-GigabitEthernet2/0/0] pim sm [~RouterA-GigabitEthernet2/0/0] quit[~RouterA] interface pos 1/0/0[~RouterA-Pos1/0/0] pim sm [~RouterA-Pos1/0/0] quit[~RouterA] interface pos 3/0/0[~RouterA-Pos3/0/0] pim sm [~RouterA-Pos3/0/0] commit[~RouterA-Pos3/0/0] quit

Step 3 Enable IGMP on the interface directly connected to hosts. The configuration details are not provided here.

Step 4 Configure RPs.NOTE

You can choose to configure both a static RP and a dynamic RP, or only one of them. When both a staticRP and a dynamic RP are configured, the dynamic RP is preferred. You can enable the static RP to be

preferred by setting the keyword preferred in the static-rp rp-address command.

In this example, a static RP and a dynamic RP are configured. The dynamic RP is preferred, and the staticRP functions as the backup of the dynamic RP.

# Configure a dynamic RP. Perform the following configurations on one or more routers in thePIM-SM domain. On Router E, set the range of groups severed by the RP and locations of C-BSRs and C-RPs.

[~RouterE] acl number 2005[~RouterE-acl-basic-2005] rule permit source 225.1.1.0 0.0.0.255[~RouterE-acl-basic-2005] quit[~RouterE] pim [~RouterE-pim] c-bsr pos 3/0/0[~RouterE-pim] c-rp pos 3/0/0 group-policy 2005 priority 0[~RouterE-pim] commit[~RouterE-pim] quit

# Configure a static RP on all multicast routers. In this example, perform the followingconfigurations on Router A, Router B, Router C, Router D, and Router E. The configurationsof Router B, Router C, Router D, and Router E are similar to those on Router A, and are not

provided here.

[~RouterA] pim [~RouterA-pim] static-rp 192.168.2.2[~RouterA-pim] commit[~RouterA-pim] quit

Step 5 (Optional) Configure a BSR boundary on the interface that connects Router D to the Internet.



99


110/344


111/344

VPN-Instance: public netPIM-SM BSR RP information:Group/MaskLen: 225.1.1.0/24

RP: 192.168.9.2Priority: 0Uptime: 00:45:13

Expires: 00:02:17PIM SM static RP information:

Static RP: 192.168.2.2

# Run the display pim routing-table command to check the PIM routing table on each router.Host A wants to receive data for multicast group 225.1.1.1/24, and Host B wants to receive datasent by multicast source 10.110.5.100/24 to multicast group 232.1.1.1/24. The command outputis as follows:

display pim routing-tableVPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry(*, 225.1.1.1) RP: 192.168.9.2 Protocol: pim-sm, Flag: WC UpTime: 00:13:46 Upstream interface: Pos1/0/0,

Upstream neighbor: 192.168.9.2 RPF neighbor: 192.168.9.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/0/0, Protocol: igmp, UpTime: 00:13:46, Expires:-(10.110.5.100, 225.1.1.1) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:00:42 Upstream interface: Pos3/0/0 Upstream neighbor: 192.168.1.2 RPF neighbor: 192.168.1.2

Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/0/0 Protocol: pim-sm, UpTime: 00:00:42, Expires:- display pim routing-tableVPN-Instance: public net Total 0 (*, G) entry; 2 (S, G) entries (10.110.5.100, 225.1.1.1) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:00:42 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: 10.110.5.100 RPF neighbor: 10.110.5.100 Downstream interface(s) information: Total number of downstreams: 1 1: Pos2/0/0 Protocol: pim-sm, UpTime: 00:00:42, Expires:-(10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:01:20 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: 10.110.5.100 RPF neighbor: 10.110.5.100 Downstream interface(s) information: Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-ssm, UpTime: 00:01:20, Expires:- display pim routing-tableVPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry

(*, 225.1.1.1) RP: 192.168.9.2 (local)



101


112/344

Protocol: pim-sm, Flag: WC UpTime: 00:13:16 Upstream interface: Register Upstream neighbor: 192.168.4.2 RPF neighbor: 192.168.4.2 Downstream interface(s) information:

Total number of downstreams: 1 1: Pos3/0/0 Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22(10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:01:22 Upstream interface: Pos4/0/0 Upstream neighbor: 192.168.4.2 RPF neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-ssm, UpTime: 00:01:22, Expires:- display pim routing-table VPN-Instance: public net Total 1 (S, G) entry (10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:01:25 Upstream interface: Pos2/0/0 Upstream neighbor: 192.168.3.2 RPF neighbor: 192.168.3.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet1/0/0 Protocol: igmp, UpTime: 00:01:25, Expires:-

----End

Configuration Filesl Configuration file of Router A#sysname RouterA#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.1.1 255.255.255.0 pim sm

igmp enable igmp version 3#interface Pos3/0/0 undo shutdown link-protocol ppp ip address 192.168.1.1 255.255.255.0 pim sm#interface Pos1/0/0 undo shutdown link-protocol ppp ip address 192.168.9.1 255.255.255.0 pim sm#ospf 1

area 0.0.0.0 network 10.110.1.0 0.0.0.255



102


113/344

network 192.168.1.0 0.0.0.255 network 192.168.9.0 0.0.0.255#pim ssm-policy 2000 static-rp 192.168.2.2

#return

l Configuration file of Router B#sysname RouterB#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.2.1 255.255.255.0 pim sm

igmp enable igmp version 3#interface Pos1/0/0 undo shutdown link-protocol ppp

ip address 192.168.2.1 255.255.255.0 pim sm#ospf 1 area 0.0.0.0 network 10.110.2.0 0.0.0.255 network 192.168.2.0 0.0.0.255#pim

ssm-policy 2000 static-rp 192.168.2.2#return

l Configuration file of Router C#sysname RouterC#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#interface GigabitEthernet1/0/0 undo shutdown ip address 10.110.2.2 255.255.255.0 pim sm

igmp enable igmp version 3#interface Pos2/0/0 undo shutdown link-protocol ppp ip address 192.168.3.1 255.255.255.0 pim sm#ospf 1 area 0.0.0.0 network 10.110.2.0 0.0.0.255 network 192.168.3.0 0.0.0.255

#pim



103


114/344

ssm-policy 2000 static-rp 192.168.2.2#return

l Configuration file of Router D

#sysname RouterD#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#interface GigabitEthernet3/0/0 undo shutdown ip address 10.110.5.1 255.255.255.0 pim sm#interface Pos4/0/0 undo shutdown link-protocol ppp ip address 10.110.4.1 255.255.255.0 pim sm pim bsr-boundary#interface Pos2/0/0 undo shutdown

link-protocol pppip address 192.168.1.2 255.255.255.0

pim sm#interface Pos1/0/0 undo shutdown link-protocol ppp

ip address 192.168.4.2 255.255.255.0 pim sm

#ospf 1 area 0.0.0.0 network 10.110.4.0 0.0.0.255 network 10.110.5.0 0.0.0.255 network 192.168.1.0 0.0.0.255 network 192.168.4.0 0.0.0.255#pim ssm-policy 2000 static-rp 192.168.2.2#return

l Configuration file of Router E#sysname RouterE#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#acl number 2005 rule 5 permit source 225.1.1.0 0.0.0.255#interface Pos1/0/0 undo shutdown link-protocol ppp

ip address 192.168.3.2 255.255.255.0 pim sm

#interface Pos2/0/0



104


115/344

undo shutdown link-protocol ppp ip address 192.168.2.2 255.255.255.0 pim sm#interface Pos3/0/0

undo shutdown link-protocol ppp

ip address 192.168.9.2 255.255.255.0 pim sm#interface Pos4/0/0 undo shutdown link-protocol ppp

ip address 192.168.4.1 255.255.255.0 pim sm#ospf 1 area 0.0.0.0 network 192.168.3.0 0.0.0.255 network 192.168.2.0 0.0.0.255 network 192.168.9.0 0.0.0.255 network 192.168.4.0 0.0.0.255#pim ssm-policy 2000 static-rp 192.168.2.2

c-bsr Pos3/0/0 c-rp Pos3/0/0 group-policy 2005 priority 0#return

3.10.3 Example for Configuring PIM-SM SecurityTo prevent malicious packet attacks, you can configure various filtering policies, for example,setting a valid source address range or a valid C-RP address range, to improve the security of the PIM network.


CAUTION


It is required to deploy multicast services on the ISP network shown in Figure 3-6 . The integratedIGP is deployed on the network to implement normal unicast routing. In such a scenario, youcan configure filtering policies on the routers to improve the security of the multicast network so that hosts can receive secure and reliable multicast data.



105


116/344

Figure 3-6 example for configuring PIM-SM security

RouterA Ethernet

Ethernet

Source

Ethernet

RouterBRouterC

PIM-SM

RouterD

Leaf networks

Receiver HostA

Receiver HostB

N1

N2

GE2/0/0

POS1/0/0

GE2/0/0POS2/0/0

POS2/0/0

GE1/0/0

GE3/0/0

POS1/0/0

POS3/0/0

POS1/0/0

POS1/0/0

POS4/0/0

POS2/0/0RouterE

POS3/0/0

Device Interface IP Address Device Interface IP AddressRouterA POS 1/0/0 192.168.9.1/24 RouterD POS 1/0/0 192.168.4.2/24

POS 3/0/0 192.168.1.1/24 POS 2/0/0 192.168.1.2/24

GE 2/0/0 10.110.1.1/24 GE 3/0/0 10.110.5.1/24

RouterB POS 1/0/0 192.168.2.1/24 RouterE POS 1/0/0 192.168.3.2/24

GE 2/0/0 10.110.2.1/24 POS 2/0/0 192.168.2.2/24

RouterC POS 2/0/0 192.168.3.1/24 POS 3/0/0 192.168.9.2/24

GE 1/0/0 10.110.2.2/24 POS 4/0/0 192.168.4.1/24

Configuration NotesWhen configuring PIM security, pay attention to the following points:


l The range of multicast groups that each C-RP serves and the valid C-RP address range can be set only on the C-BSR.

l Source address-based and BSR address-based filtering policies need be configured on allthe routers.

l Policies for filtering Register messages need be configured on all C-RPs.l Policies for filtering Join/Prune messages are commonly configured on the last-hop

routers.


Configure PIM-SM to implement the multicast functions on the network. The filtering policiesof ensuring PIM network security include setting the valid ranges of the source address, BSR address, and RP address, and filtering Register messages, Join/Prune message, and PIMneighbors.





106


117/344


4. Enable IGMP on the routers connected to hosts.

5. Configure C-BSRs and C-RPs if the BSR RP needs to be used.

6. Set the range of multicast groups that each C-RP serves on the C-BSR.

7. Create a policy for filtering Register messages on the C-RP to avoid the attacks of theRegister messages carrying illegal multicast source information.

8. Create source address-based filtering policies on all the routers to deny all the multicast packets from illegal sources.

9. Create BSR address-based filtering policies on all the routers to avoid BSR spoofing.

Data Preparation


l Multicast group addressl IP address of the multicast sourcel ACL rules for defining various filtering policies

Procedure



# Take Router A as an example. Configurations on Router B, Router C, Router D, and Router E are similar to those on Router A and hence are not mentioned here.

[~RouterA] multicast routing-enable[~RouterA] interface gigabitethernet 2/0/0[~RouterA-GigabitEthernet2/0/0] pim sm [~RouterA-GigabitEthernet2/0/0] quit[~RouterA] interface pos 1/0/0[~RouterA-Pos1/0/0] pim sm [~RouterA-Pos1/0/0] quit[~RouterA] interface pos 3/0/0[~RouterA-Pos3/0/0] pim sm [~RouterA-Pos3/0/0] commit[~RouterA-Pos3/0/0] quit

Step 3 Enable IGMP on the interfaces connected to hosts.


[~RouterA] interface gigabitethernet 2/0/0[~RouterA-GigabitEthernet2/0/0] igmp enable[~RouterA-GigabitEthernet2/0/0] igmp version 3[~RouterA-GigabitEthernet2/0/0] commit[~RouterA-GigabitEthernet2/0/0] quit

Step 4 Configure C-BSRs and C-RPs.

# Configure a C-BSR and a C-RP on Router E.

[~RouterE] pim [~RouterE-pim] c-bsr pos 2/0/0[~RouterE-pim] c-rp pos 2/0/0

[~RouterE-pim] commit[~RouterE-pim] quit



107


118/344

Step 5 Set the range of multicast groups that each C-RP serves and the valid C-RP address range onthe C-BSR.

# Set the range of multicast groups that each C-RP serves and the valid C-RP address range onRouter E.

[~RouterE] acl number 3000[~RouterE-acl4-advance-3000] rule permit ip source 192.168.2.2 0 destination225.1.1.0 0.0.0.255[~RouterE-acl4-advance-3000] quit[~RouterE] pim [~RouterE-pim] crp-policy 3000[~RouterE-pim] commit[~RouterE-pim] quit

Step 6 Create a policy for filtering Register messages on the C-RP.

# Create a policy for filtering Register messages on Router E.

[~RouterE] acl number 3001[~RouterE-acl4-advance-3001] rule permit ip source 10.110.5.0 0.0.0.255destination 225.1.1.0 0.0.0.255[~RouterE-acl4-advance-3001] quit[~RouterE] pim [~RouterE-pim] register-policy 3001[~RouterE-pim] commit[~RouterE-pim] quit

Step 7 Create source address-based and BSR address-based filtering policies on all the routers.

# Take Router E as an example. Configurations on Router A, Router B, Router C, and Router D are similar to those on Router E and hence are not mentioned here.

[~RouterE] acl number 2000[~RouterE-acl4-basic-2000] rule permit source 10.110.5.0 0.0.0.255[~RouterE-acl4-basic-2000] quit[~RouterE] acl number 2001[~RouterE-acl4-basic-2001] rule permit source 192.168.2.0 0.0.0.255[~RouterE-acl4-basic-2001] quit[~RouterE] pim [~RouterE-pim] source-policy 2000[~RouterE-pim] bsr-policy 2001[~RouterE-pim] commit[~RouterE-pim] quit


# Run the display pim bsr-info command to view information about the BSR on the router. TheBSR address matches the filtering rule. For example, information about the BSRs on Router DandRouter E is as follows:

display pim bsr-info VPN-Instance: public net Elected AdminScope BSR Count: 0 Elected BSR Address: 192.168.2.2 Priority: 0 Hash mask length: 30 State: Accept Preferred Scope: Not scoped Uptime: 21:56:56 Expires: 00:02:01 C-RP Count: 1 display pim bsr-info VPN-Instance: public net Elected AdminScope BSR Count: 0 Elected BSR Address: 192.168.2.2

Priority: 0 Hash mask length: 30



108


119/344

State: Elected Scope: Not scoped Uptime: 21:57:15 Next BSR message scheduled at: 00:00:14 C-RP Count: 1 Candidate AdminScope BSR Count: 0

Candidate BSR Address: 192.168.2.2 Priority: 0 Hash mask length: 30 State: Elected Scope: Not scoped Wait to be BSR: 0

# Run the display pim rp-info command to view information about the RPs on the routers. TheRP address matches the filtering rule. For example, information about the RPs on Router DandRouter E is as follows:

display pim rp-info VPN-Instance: public net PIM-SM BSR RP infomation: Group/MaskLen: 224.0.0.0/4 RP: 192.168.2.2 Priority: 0 Uptime: 01:27:21 Expires: 00:02:11 display pim rp-info VPN-Instance: public net PIM-SM BSR RP infomation: Group/MaskLen: 224.0.0.0/4 RP: 192.168.2.2 (local) Priority: 0 Uptime: 01:29:10 Expires: 00:02:20

# Run the display pim routing-table command to view information about the PIM routing tableson the routers. Hosts can receive multicast data from a valid multicast source. Multicast source10.110.5.100 sends multicast data and Host A needs to receive the data for multicast group225.1.1.1/24 and host B needs to receive the data for group 225.1.1.2/24. For example,information about the PIM routing tables on Router D andRouter E is as follows:


VPN-Instance: public net Total 0 (*, G) entry; 2 (S, G) entries

( 10.110.5.100 , 225.1.1.1) RP: 192.168.2.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:57:20 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: 10.110.5.100 RPF prime neighbor: 10.110.5.100 Downstream interface(s) information: Total number of downstreams: 1 1: Pos2/0/0 Protocol: pim-sm, UpTime: 00:57:20, Expires: 00:03:02

( 10.110.5.100 , 225.1.1.2) RP: 192.168.2.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 01:56:45 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: 10.110.5.100 RPF prime neighbor: 10.110.5.100 Downstream interface(s) information: Total number of downstreams: 1

1: Pos1/0/0 Protocol: pim-sm, UpTime: 01:56:45, Expires: 00:02:43



109


120/344


VPN-Instance: public net Total 2 (*, G) entries; 1 (S, G) entry

(*, 225.1.1.1)

RP: 192.168.2.2 (local) Protocol: pim-sm, Flag: WC UpTime: 00:21:40 Upstream interface: register Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Pos3/0/0 Protocol: pim-sm, UpTime: 00:21:40, Expires: 00:02:43

(*, 225.1.1.2) RP: 192.168.2.2 (local) Protocol: pim-sm, Flag: WC UpTime: 00:21:40 Upstream interface: register Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-sm, UpTime: 00:21:40, Expires: 00:02:43

( 10.110.5.100 , 225.1.1.2) RP: 192.168.2.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 01:56:45 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: 192.168.4.2 RPF prime neighbor: 192.168.4.2 Downstream interface(s) information:

Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-sm, UpTime: 01:56:45, Expires: 00:02:43

----End


#sysname RouterA#multicast routing-enable#acl number 2000 rule 5 permit source 10.110.5.0 0.0.0.255#acl number 2001 rule 5 permit source 192.168.2.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0001.00#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.1.1 255.255.255.0 pim sm igmp enable igmp version 3

isis enable 1#



110


121/344


122/344

isis enable 1 pim sm igmp enable igmp version 3#interface Pos2/0/0

ip address 192.168.3.1 255.255.255.0 pim sm isis enable 1#pim bsr-policy 2001 source-policy 2000#return

l Configuration file of Router D#sysname RouterD#multicast routing-enable#acl number 2000 rule 5 permit source 10.110.5.0 0.0.0.255#acl number 2001 rule 5 permit source 192.168.2.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0004.00#interface GigabitEthernet3/0/0 undo shutdown ip address 10.110.5.1 255.255.255.0 pim sm isis enable 1#

interface Pos1/0/0 undo shutdown link-protocol ppp ip address 192.168.4.2 255.255.255.0 pim sm isis enable 1#interface Pos2/0/0 undo shutdown link-protocol ppp ip address 192.168.1.2 255.255.255.0 pim sm isis enable 1#pim bsr-policy 2001 source-policy 2000#return

l Configuration file of Router E#sysname RouterE#multicast routing-enable#acl number 2000 rule 5 permit source 10.110.5.0 0.0.0.255#acl number 2001 rule 5 permit source 192.168.2.0 0.0.0.255

#acl number 3000



112


123/344

rule 5 permit ip source 192.168.2.2 0 destination 225.1.1.0 0.0.0.255#acl number 3001 rule 5 permit ip source 10.110.5.0 0.0.0.255 destination 225.1.1.0 0.0.0.255#isis 1

network-entity 10.0000.0000.0005.00#interface Pos1/0/0 link-protocol ppp ip address 192.168.3.2 255.255.255.0 pim sm isis enable 1#interface Pos2/0/0 undo shutdown link-protocol ppp ip address 192.168.2.2 255.255.255.0 pim sm isis enable 1#interface Pos3/0/0 undo shutdown link-protocol ppp ip address 192.168.9.2 255.255.255.0 pim sm isis enable 1#interface Pos4/0/0 undo shutdown link-protocol ppp ip address 192.168.4.1 255.255.255.0 pim sm isis enable 1#pim bsr-policy 2001

register-policy 3001 source-policy 2000 c-bsr Pos2/0/0 crp-policy 3000 c-rp Pos2/0/0#return

3.10.4 Example for Configuring SPT Switchover in a PIM-SMDomain

An RP performs an SPT switchover after receiving the Register message and a receiver's DR performs an SPT switchover after receiving the first multicast data packet. To perform an SPTswitchover only after the rate of multicast data packets reaches the upper threshold, configurethe conditions for triggering an SPT switchover.


CAUTION




113


124/344

As shown in Figure 3-7 , multicast services are deployed on the ISP network. An IGP has beendeployed to ensure that unicast routes are available. The ISP network is connected to the Internet.The router must be properly configured so that the hosts on the network can receive VODinformation in multicast mode.

Figure 3-7 Networking diagram for configuring SPT switchover in a PIM-SM domain

RouterA Ethernet

Ethernet

Source

Ethernet

RouterBRouterC

PIM-SM

RouterD

Leaf networks

Receiver HostA

Receiver

HostB

N1

N2

GE2/0/0

POS1/0/0

GE2/0/0POS2/0/0

POS2/0/0

GE1/0/0

GE3/0/0

POS1/0/0

POS3/0/0

POS1/0/0

POS1/0/0

POS4/0/0

POS2/0/0RouterE

POS3/0/0

POS4/0/0

Device Interface IP Address

Router A POS 1/0/0 192.168.9.1/24

POS 3/0/0 192.168.1.1/24

GE 2/0/0 10.110.1.1/24

Router B POS 1/0/0 192.168.2.1/24

GE 2/0/0 10.110.2.1/24

Router C POS 2/0/0 192.168.3.1/24

GE 1/0/0 10.110.2.2/24

Router D POS 1/0/0 192.168.4.2/24

POS 2/0/0 192.168.1.2/24

POS 4/0/0 10.110.4.1/24

GE 3/0/0 10.110.5.1/24

Router E POS 1/0/0 192.168.3.2/24

POS 2/0/0 192.168.2.2/24

POS 3/0/0 192.168.9.2/24

POS 4/0/0 192.168.4.1/24

Precautions

When configuring the SPT switchover in a PIM-SM domain, note the following points:

l Unicast routes on the network must be reachable because multicast routing is based onunicast routing.

l Multicast routing needs to be enabled on all routers.l

PIM-SM needs to be on the interfaces connecting routers, interface directly connecting therouter to the multicast source, and interface directly connecting the router to hosts.



114


125/344

l If a static RP is used, the static RP configurations on all the routers must be the same.l IGMP of a supported version needs to be run on the router directly connected to hosts. PIM-

SM and IGMP need to be enabled in sequence (that is, first PIM-SM and then IGMP) onthe interface directly connected to hosts; otherwise, the PIM-SM function fails to be

configured.l When users need to receive data sent by a specified multicast source, PIM-SSM needs to

be enabled and the same SSM group address range needs to be configured on all therouters.


The ISP network access the Internet. To simplify service expansion, you can configure PIM-SMto provide multicast services on the network.


2. Enable multicast routing on all routers providing multicast services.

3. Enable PIM-SM on all interfaces of multicast routers.


5. Configure RPs. An RP is the root node of an RPT in a PIM-SM network. Setting an RP onthe router that has more branches, for example, Router E in Figure 3-7 , is recommended.

6. (Optional) Set a BSR boundary on the interface connected to the Internet. Bootstrapmessages cannot pass through the BSR boundary. Therefore, the BSR serves only this PIM-SM domain. This increases multicast controllability.

7. (Optional) Configure the SSM group address range on each router. This enables themulticast routers in the PIM-SM domain to provide services only for multicast groups withaddresses being in the SSM group address range.

Data Preparation


l Multicast group address (225.1.1.1/24)l Multicast source address (10.110.5.100/24)l SSM group address range (232.1.1.0/24)

Procedure


Step 2 Enable multicast on each device and PIM-SM on each interface of the devices.

# Enable multicast on each router and PIM-SSM on each interface of the Routers. Theconfigurations of Router B, Router C, Router D, and Router E are similar to those on Router A,and are not provided here.

[~RouterA] multicast routing-enable[~RouterA] interface gigabitethernet 2/0/0[~RouterA-GigabitEthernet2/0/0] pim sm [~RouterA-GigabitEthernet2/0/0] quit[~RouterA] interface pos 1/0/0

[~RouterA-Pos1/0/0] pim sm [~RouterA-Pos1/0/0] quit



115


126/344

[~RouterA] interface pos 3/0/0[~RouterA-Pos3/0/0] pim sm [~RouterA-Pos3/0/0] quit

Step 3 Enable IGMP on the interface directly connected to hosts. The configuration details are not provided here.

Step 4 Configure RPs.NOTE

You can choose to configure both a static RP and a dynamic RP, or only one of them. When both a staticRP and a dynamic RP are configured, the dynamic RP is preferred. You can enable the static RP to be

preferred by setting preferred in the static-rp rp-address command.

In this example, a static RP and a dynamic RP are configured. The dynamic RP is preferred, and the staticRP functions as the backup of the dynamic RP.

# Configure a dynamic RP. Perform the following configurations on one or more routers in thePIM-SM domain. On Router E, set the range of groups severed by the RP and locations of C-

BSRs and C-RPs.[~RouterE] acl number 2005[~RouterE-acl-basic-2005] rule permit source 225.1.1.0 0.0.0.255[~RouterE-acl-basic-2005] quit[~RouterE] pim [~RouterE-pim] c-bsr pos 3/0/0[~RouterE-pim] c-rp pos 3/0/0 group-policy 2005 priority 0

# Configure a static RP on all multicast routers. In this example, perform the followingconfigurations on Router A, Router B, Router C, Router D, and Router E. The configurationsof Router B, Router C, Router D, and Router E are similar to those on Router A, and are not

provided here.

[~RouterA] pim [~RouterA-pim] static-rp 192.168.2.2

Step 5 (Optional) Configure a BSR boundary on the interface that connects Router D to the Internet.[~RouterD] interface pos 4/0/0[~RouterD-Pos4/0/0] pim bsr-boundary[~RouterD-Pos4/0/0] quit

Step 6 (Optional) Set an SSM group address range.

# Set the SSM group address range to 232.1.1.0/24 on all routers. The configurations of Router B, Router C, Router D, and Router E are similar to those on Router A, and are not providedhere.

[~RouterA] acl number 2000[~RouterA-acl-basic-2000] rule permit source 232.1.1.0 0.0.0.255[~RouterA-acl-basic-2000] quit[~RouterA] pim [~RouterA-pim] ssm-policy 2000


# Run the display pim interface command to check PIM interfaces on each router. For example,the information about PIM interfaces on Router C is displayed as follows:

display pim interfaceVPN-Instance: public netInterface State NbrCnt HelloInt DR-Pri DR-Address

GE1/0/0 up 0 30 1 10.110.2.2 (local)Pos2/0/0 up 1 30 1 192.168.3.1



116


127/344

# Run the display pim bsr-info command to check BSR information on each router. For example, the BSR information on Router A and Router E (C-BSR information is also displayedon Router E) is displayed as follows:

display pim bsr-info

VPN-Instance: public net Elected AdminScope BSR Count: 0 Elected BSR Address: 192.168.9.2 Priority: 0 Hash mask length: 30 State: Accept Preferred Scope: Not scoped Uptime: 01:40:40 Expires: 00:01:42 C-RP Count: 1 display pim bsr-infoVPN-Instance: public net Elected AdminScope BSR Count: 0 Elected BSR Address: 192.168.9.2 Priority: 0 Hash mask length: 30 State: Elected Scope: Not scoped Uptime: 00:00:18 Next BSR message scheduled at :00:01:42 C-RP Count: 1 Candidate AdminScope BSR Count: 0 Candidate BSR Address is: 192.168.9.2 Priority: 0 Hash mask length: 30 State:Elected Scope: Not scoped

Wait to be BSR: 0

# Run the display pim rp-info command to check RP information on each router. For example,the RP information on Router A is displayed as follows:

display pim rp-infoVPN-Instance: public net

PIM-SM BSR RP information:Group/MaskLen: 225.1.1.0/24

RP: 192.168.9.2Priority: 0Uptime: 00:45:13Expires: 00:02:17

PIM SM static RP information:Static RP: 192.168.2.2

# Run the display pim routing-table command to check the PIM routing table on each router.Host A needs to receive data for multicast group 225.1.1.1/24, and Host B needs to receive datasent by multicast source 10.110.5.100/24 to multicast group 232.1.1.1/24. The command outputas follows:

display pim routing-tableVPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry(*, 225.1.1.1) RP: 192.168.9.2 Protocol: pim-sm, Flag: WC UpTime: 00:13:46 Upstream interface: Pos1/0/0,

Upstream neighbor: 192.168.9.2 RPF neighbor: 192.168.9.2 Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/0/0,

Protocol: igmp, UpTime: 00:13:46, Expires:-(10.110.5.100, 225.1.1.1)



117


128/344

RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:00:42 Upstream interface: Pos3/0/0 Upstream neighbor: 192.168.1.2 RPF neighbor: 192.168.1.2

Downstream interface(s) information: Total number of downstreams: 1 1: GigabitEthernet2/0/0 Protocol: pim-sm, UpTime: 00:00:42, Expires:- display pim routing-tableVPN-Instance: public net Total 0 (*, G) entry; 2 (S, G) entries (10.110.5.100, 225.1.1.1) RP: 192.168.9.2 Protocol: pim-sm, Flag: SPT ACT UpTime: 00:00:42 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: 10.110.5.100 RPF neighbor: 10.110.5.100 Downstream interface(s) information: Total number of downstreams: 1 1: Pos2/0/0 Protocol: pim-sm, UpTime: 00:00:42, Expires:-(10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:01:20 Upstream interface: GigabitEthernet3/0/0 Upstream neighbor: 10.110.5.100 RPF neighbor: 10.110.5.100 Downstream interface(s) information: Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-ssm, UpTime: 00:01:20, Expires:- display pim routing-tableVPN-Instance: public net Total 1 (*, G) entry; 1 (S, G) entry

(*, 225.1.1.1) RP: 192.168.9.2 (local) Protocol: pim-sm, Flag: WC UpTime: 00:13:16 Upstream interface: Register Upstream neighbor: 192.168.4.2 RPF neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Pos3/0/0 Protocol: pim-sm, UpTime: 00:13:16, Expires: 00:03:22(10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:01:22 Upstream interface: Pos4/0/0 Upstream neighbor: 192.168.4.2 RPF neighbor: 192.168.4.2 Downstream interface(s) information: Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-ssm, UpTime: 00:01:22, Expires:- display pim routing-table VPN-Instance: public net Total 1 (S, G) entry (10.110.5.100, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:01:25 Upstream interface: Pos2/0/0 Upstream neighbor: 192.168.3.2 RPF neighbor: 192.168.3.2 Downstream interface(s) information:

Total number of downstreams: 1



118


129/344

1: GigabitEthernet1/0/0 Protocol: igmp, UpTime: 00:01:25, Expires:-

----End


#sysname RouterA#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.1.1 255.255.255.0 pim sm

igmp enable igmp version 3#interface Pos3/0/0 undo shutdown link-protocol ppp ip address 192.168.1.1 255.255.255.0 pim sm#interface Pos1/0/0 undo shutdown link-protocol ppp ip address 192.168.9.1 255.255.255.0 pim sm#

ospf 1 area 0.0.0.0 network 10.110.1.0 0.0.0.255 network 192.168.1.0 0.0.0.255 network 192.168.9.0 0.0.0.255#pim ssm-policy 2000 static-rp 192.168.2.2#return

l Configuration file of Router B#sysname RouterB#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.2.1 255.255.255.0 pim sm

igmp enable igmp version 3#interface Pos1/0/0 undo shutdown link-protocol ppp

ip address 192.168.2.1 255.255.255.0 pim sm



119


130/344

#ospf 1 area 0.0.0.0 network 10.110.2.0 0.0.0.255 network 192.168.2.0 0.0.0.255#

pim ssm-policy 2000 static-rp 192.168.2.2#return

l Configuration file of Router C#sysname RouterC#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#interface GigabitEthernet1/0/0 undo shutdown ip address 10.110.2.2 255.255.255.0 pim sm

igmp enable igmp version 3#interface Pos2/0/0 undo shutdown link-protocol ppp ip address 192.168.3.1 255.255.255.0 pim sm#ospf 1 area 0.0.0.0 network 10.110.2.0 0.0.0.255

network 192.168.3.0 0.0.0.255#pim ssm-policy 2000 static-rp 192.168.2.2#return

l Configuration file of Router D#sysname RouterD#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#interface GigabitEthernet3/0/0 undo shutdown ip address 10.110.5.1 255.255.255.0 pim sm#interface Pos4/0/0 undo shutdown link-protocol ppp ip address 10.110.4.1 255.255.255.0 pim bsr-boundary pim sm#interface Pos2/0/0 undo shutdown

link-protocol pppip address 192.168.1.2 255.255.255.0



120


131/344

pim sm#interface Pos1/0/0 undo shutdown link-protocol ppp

ip address 192.168.4.2 255.255.255.0

pim sm#ospf 1 area 0.0.0.0 network 10.110.4.0 0.0.0.255 network 10.110.5.0 0.0.0.255 network 192.168.1.0 0.0.0.255 network 192.168.4.0 0.0.0.255#pim ssm-policy 2000 static-rp 192.168.2.2#return

l Configuration file of Router E#sysname RouterE#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#acl number 2005 rule 5 permit source 225.1.1.0 0.0.0.255#interface Pos1/0/0 undo shutdown link-protocol ppp

ip address 192.168.3.2 255.255.255.0

pim sm#interface Pos2/0/0 undo shutdown link-protocol ppp ip address 192.168.2.2 255.255.255.0 pim sm#interface Pos3/0/0 undo shutdown link-protocol ppp

ip address 192.168.9.2 255.255.255.0 pim sm#interface Pos4/0/0 undo shutdown link-protocol ppp

ip address 192.168.4.1 255.255.255.0 pim sm#ospf 1 area 0.0.0.0 network 192.168.3.0 0.0.0.255 network 192.168.2.0 0.0.0.255 network 192.168.9.0 0.0.0.255 network 192.168.4.0 0.0.0.255#pim ssm-policy 2000 static-rp 192.168.2.2

c-bsr Pos3/0/0

c-rp Pos3/0/0 group-policy 2005 priority 0#



121


132/344

return

3.10.5 Example for Configuring PIM-SSM MulticastIn an AS with reachable unicast routes, you can configure basic PIM-SSM functions so thathosts can receive multicast data from a specified multicast source.


CAUTION


It is required to deploy multicast services on the ISP network shown in Figure 3-8 . The integratedIGP is deployed on the network to implement normal unicast routing. Hosts on the network thenneed to join source-specific multicast groups.

Figure 3-8 Networking diagram for configuring PIM-SSM multicast

Source

EthernetRouterA

PIM-SSM

RouterB

Leaf networks

Ethernet

Receiver HostA

RouterC

GE2/0/0 GE2/0/0POS1/0/0 POS1/0/0

POS1/0/0 POS2/0/0

Device Interface IP Address Device Interface IP Address

RouterA POS 1/0/0 192.168.2.1/24 Router C POS 1/0/0 192.168.4.2/24

GE 2/0/0 10.110.1.2/24 GE 2/0/0 10.110.2.1/24

RouterB POS 1/0/0 192.168.2.2/24

POS 2/0/0 192.168.4.1/24

Configuration Notes

When configuring PIM-SSM multicast, pay attention to the following points:



122


133/344


l You must ensure that the SSM group address ranges set on all the routers are the same.l An RP need not be configured on the PIM-SSM network.


Configure PIM-SSM to implement source-specific multicast on the network.




4. Enable IGMP on the routers connected to hosts.

5. Set the same SSM group address range on all the routers.

Data Preparation


l IP address of the multicast sourcel SSM group address range

Procedure

Step 1 Configure an IP address for each interface on the routers and configure a unicast routing protocol.The detailed configuration procedure is not mentioned here.



[~RouterA] multicast routing-enable[~RouterA] interface gigabitethernet 2/0/0[~RouterA-GigabitEthernet2/0/0] pim sm [~RouterA-GigabitEthernet2/0/0] quit[~RouterA] interface pos 1/0/0[~RouterA-Pos1/0/0] pim sm [~RouterA-Pos1/0/0] commit[~RouterA-Pos1/0/0] quit

Step 3 Enable IGMP on the interfaces connected to hosts.

# Enable IGMP on the interface connecting Router C to the host and set the IGMP version to 3.

[~RouterC] interface gigabitethernet 2/0/0[~RouterC-GigabitEthernet2/0/0] igmp enable[~RouterC-GigabitEthernet2/0/0] igmp version 3[~RouterC-GigabitEthernet2/0/0] commit[~RouterC-GigabitEthernet2/0/0] quit

Step 4 Set SSM group address ranges.

# Set the SSM group address range to 232.1.1.0/24 on all the routers. Take Router A as an

example. Configurations on Router B and Router C are the same as those on Router A and henceare not mentioned here.



123


134/344

[~RouterA] acl number 2000[~RouterA-acl4-basic-2000] rule permit source 232.1.1.0 0.0.0.255[~RouterA-acl4-basic-2000] quit[~RouterA] pim [~RouterA-pim] ssm-policy 2000[~RouterA-pim] commit

[~RouterA-pim] quit


# Host A needs to receive the data sent from source 10.110.1.1/24 to group 232.1.1.1/24. Runthe display pim routing-table command to view information about the PIM routing tables onthe routers. The display on Router A and Router B is as follows:



(10.110.1.1, 232.1.1.1) Protocol: pim-ssm, Flag: LOC

UpTime: 00:02:13 Upstream interface: GigabitEthernet2/0/0 Upstream neighbor: 10.110.1.1 RPF prime neighbor: 10.110.1.1 Downstream interface(s) information: Total number of downstreams: 1 1: Pos1/0/0 Protocol: pim-ssm, UpTime: 00:02:13, Expires: 00:03:17 display pim routing-table


(10.110.1.1, 232.1.1.1) Protocol: pim-ssm, Flag: UpTime: 00:09:15 Upstream interface: Pos1/0/0 Upstream neighbor: 192.168.2.1 RPF prime neighbor: 192.168.2.1 Downstream interface(s) information: Total number of downstreams: 1 1: Pos2/0/0 Protocol: pim-ssm, UpTime: 00:09:15, Expires: 00:03:13

----End


#sysname RouterA#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0001.00#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.1.2 255.255.255.0 pim sm isis enable 1

#interface Pos1/0/0



124


135/344

undo shutdown link-protocol ppp ip address 192.168.2.1 255.255.255.0 pim sm isis enable 1#

pim ssm-policy 2000#return

l Configuration file of Router B#sysname RouterB#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0002.00#interface Pos1/0/0 undo shutdown link-protocol ppp ip address 192.168.2.2 255.255.255.0 pim sm isis enable 1#interface Pos2/0/0 undo shutdown link-protocol ppp ip address 192.168.4.1 255.255.255.0 pim sm isis enable 1#

pim ssm-policy 2000#return

l Configuration file of Router C#sysname RouterC#multicast routing-enable#acl number 2000 rule 5 permit source 232.1.1.0 0.0.0.255#isis 1 network-entity 10.0000.0000.0003.00#interface GigabitEthernet2/0/0 undo shutdown ip address 10.110.2.1 255.255.255.0 pim sm igmp enable igmp version 3 isis enable 1#interface Pos1/0/0 undo shutdown ip address 192.168.4.2 255.255.255.0 pim sm isis enable 1#

pim ssm-policy 2000



125


136/344

#return


Issue 01 (2011-10-15) Huawei Proprietary and ConfidentialCopyright Huawei Techno

Configuration Guide - IP Multicast(V800R002C01_01)

Documents

Transcript of Configuration Guide - IP Multicast(V800R002C01_01)