PIM-SM inter-domain multicast configuration

Network requirements

As shown in Figure 39, OSPF runs within AS 100 and AS 200 and BGP runs between them. Each PIM-SM domain has at least one multicast source or receiver.

Set up MSDP peering relationships between the RPs in the PIM-SM domains to share multicast source information among the PIM-SM domains.

Figure 39: Network diagram

Table 10: Interface and IP address assignment

Device

Interface

IP address

Device

Interface

IP address

Switch A

Vlan-int103

10.110.1.2/24

Switch D

Vlan-int104

10.110.4.2/24

Switch A

Vlan-int100

10.110.2.1/24

Switch D

Vlan-int300

10.110.5.1/24

Switch A

Vlan-int200

10.110.3.1/24

Switch E

Vlan-int105

10.110.6.1/24

Switch B

Vlan-int103

10.110.1.1/24

Switch E

Vlan-int102

192.168.3.2/24

Switch B

Vlan-int101

192.168.1.1/24

Switch E

Loop0

3.3.3.3/32

Switch B

Loop0

1.1.1.1/32

Switch F

Vlan-int105

10.110.6.2/24

Switch C

Vlan-int104

10.110.4.1/24

Switch F

Vlan-int400

10.110.7.1/24

Switch C

Vlan-int102

192.168.3.1/24

Source 1

10.110.2.100/24

Switch C

Vlan-int101

192.168.1.2/24

Source 2

10.110.5.100/24

Switch C

Loop0

2.2.2.2/32

Configuration procedure

  1. Assign an IP address and subnet mask to each interface according to Figure 39. (Details not shown.)

  2. Configure OSPF on all the switches in the ASs. (Details not shown.)

  3. Enable IP multicast routing, enable PIM-SM on each interface, and configure a PIM-SM domain border:

    # On Switch A, enable IP multicast routing.

    <SwitchA> system-view
    [SwitchA] multicast routing
    [SwitchA-mrib] quit
    

    # Enable PIM-SM on VLAN-interface 103 and VLAN-interface 100.

    [SwitchA] interface vlan-interface 103
    [SwitchA-Vlan-interface103] pim sm
    [SwitchA-Vlan-interface103] quit
    [SwitchA] interface vlan-interface 100
    [SwitchA-Vlan-interface100] pim sm
    [SwitchA-Vlan-interface100] quit
    

    # Enable IGMP on the receiver-side interface (VLAN-interface 200).

    [SwitchA] interface vlan-interface 200
    [SwitchA-Vlan-interface200] igmp enable
    [SwitchA-Vlan-interface200] quit
    

    # Enable IP multicast routing and PIM-SM on Switch B, Switch C, Switch D, Switch E, and Switch F in the same way Switch A is configured. (Details not shown.)

    # Configure a PIM domain border on Switch B.

    [SwitchB] interface vlan-interface 101
    [SwitchB-Vlan-interface101] pim bsr-boundary
    [SwitchB-Vlan-interface101] quit
    

    # Configure a PIM domain border on Switch C and Switch E in the same way Switch B is configured. (Details not shown.)

  4. Configure C-BSRs and C-RPs:

    # Configure Loopback 0 as a C-BSR and a C-RP on Switch B.

    [SwitchB] pim
    [SwitchB-pim] c-bsr 1.1.1.1
    [SwitchB-pim] c-rp 1.1.1.1
    [SwitchB-pim] quit
    

    # Configure C-BSRs and C-RPs on Switch C and Switch E in the same way Switch B is configured. (Details not shown.)

  5. Configure BGP for mutual route redistribution between BGP and OSPF:

    # On Switch B, configure an EBGP peer, and redistribute OSPF routes.

    [SwitchB] bgp 100
    [SwitchB-bgp] router-id 1.1.1.1
    [SwitchB-bgp] peer 192.168.1.2 as-number 200
    [SwitchB-bgp] address-family ipv4 unicast
    [SwitchB-bgp-ipv4] import-route ospf 1
    [SwitchB-bgp-ipv4] peer 192.168.1.2 enable
    [SwitchB-bgp-ipv4] quit
    

    # On Switch C, configure an EBGP peer, and redistribute OSPF routes.

    [SwitchC] bgp 200
    [SwitchC-bgp] router-id 2.2.2.2
    [SwitchC-bgp] peer 192.168.1.1 as-number 100
    [SwitchC-bgp] address-family ipv4 unicast
    [SwitchC-bgp-ipv4] import-route ospf 1
    [SwitchC-bgp-ipv4] peer 192.168.1.1 enable
    [SwitchC-bgp-ipv4] quit
    

    # Redistribute BGP routes into OSPF on Switch B.

    [SwitchB] ospf 1
    [SwitchB-ospf-1] import-route bgp
    [SwitchB-ospf-1] quit
    

    # Redistribute BGP routes into OSPF on Switch C.

    [SwitchB] ospf 1
    [SwitchB-ospf-1] import-route bgp
    [SwitchB-ospf-1] quit
    
  6. Configure MSDP peers:

    # Configure an MSDP peer on Switch B.

    [SwitchB] msdp
    [SwitchB-msdp] peer 192.168.1.2 connect-interface vlan-interface 101
    [SwitchB-msdp] quit
    

    # Configure an MSDP peer on Switch C.

    [SwitchC] msdp
    [SwitchC-msdp] peer 192.168.1.1 connect-interface vlan-interface 101
    [SwitchC-msdp] peer 192.168.3.2 connect-interface vlan-interface 102
    [SwitchC-msdp] quit
    

    # Configure MSDP peers on Switch E.

    [SwitchE] msdp
    [SwitchE-msdp] peer 192.168.3.1 connect-interface vlan-interface 102
    [SwitchE-msdp] quit
    

Verifying the configuration

# Display information about BGP peer groups on Switch B.

[SwitchB] display bgp peer ipv4

 BGP local router ID: 1.1.1.1
 Local AS number: 100
 Total number of peers: 1                  Peers in established state: 1

  Peer                    AS  MsgRcvd  MsgSent OutQ PrefRcv Up/Down  State

  192.168.1.2             200 24       21      0    6       00:20:07 Established

# Display information about BGP peer groups on Switch C.

[SwitchC] display bgp peer ipv4

 BGP local router ID: 2.2.2.2
 Local AS number: 1
 Total number of peers: 1                  Peers in established state: 1

  Peer                    AS  MsgRcvd  MsgSent OutQ PrefRcv Up/Down  State

  192.168.1.1             100 18       16      0    1       00:20:07 Established

# Display the BGP routing table on Switch C.

[SwitchC] display bgp routing-table ipv4

 Total number of routes: 5

 BGP local router ID is 2.2.2.2
 Status codes: * - valid, > - best, d - dampened, h - history,
               s - suppressed, S - stale, i - internal, e - external

     Network            NextHop         MED        LocPrf     PrefVal Path/Ogn

* >  1.1.1.1/32         192.168.1.1     0                     0       100?
* >i 2.2.2.2/32         0.0.0.0         0                     0       ?
* >  192.168.1.0        0.0.0.0         0                     0       ?
* >  192.168.1.1/32     0.0.0.0         0                     0       ?
* >  192.168.1.2/32     0.0.0.0         0                     0       ?

When Source 1 in PIM-SM 1 and Source 2 in PIM-SM 2 send multicast information, receivers in PIM-SM 1 and PIM-SM 3 can receive the multicast data.

# Display brief information about MSDP peer groups on Switch B.

[SwitchB] display msdp brief
Configured   Established  Listen       Connect      Shutdown     Disabled
1            1            0            0            0            0

Peer address    State       Up/Down time    AS         SA count   Reset count
192.168.1.2     Established 00:12:57        200        13         0

# Display brief information about MSDP peer groups on Switch C.

[SwitchC] display msdp brief
Configured   Established  Listen       Connect      Shutdown     Disabled
1            1            0            0            0            0

Peer address    State       Up/Down time    AS         SA count   Reset count
192.168.3.2     Established 01:43:57        ?          8          0
192.168.1.1     Established 01:43:57        ?          13         0

# Display brief information about MSDP peer groups on Switch E.

[SwitchE] display msdp brief
Configured   Established  Listen       Connect      Shutdown     Disabled
1            1            0            0            0            0

Peer address    State       Up/Down time    AS         SA count   Reset count
192.168.3.1     Established 01:07:57        200        8          0

# Display detailed MSDP peer information on Switch B.

[SwitchB] display msdp peer-status
MSDP Peer 192.168.1.2; AS 200
 Description:
 Information about connection status:
   State: Established
   Up/down time: 00:15:47
   Resets: 0
   Connection interface: Vlan-interface101 (192.168.1.1)
   Received/sent messages: 16/16
   Discarded input messages: 0
   Discarded output messages: 0
   Elapsed time since last connection or counters clear: 00:17:40
   Mesh group peer joined: momo
   Last disconnect reason: Hold timer expired with truncated message
   Truncated packet: 5 bytes in buffer, type: 1, length: 20, without packet time: 75s
 Information about (Source, Group)-based SA filtering policy:
   Import policy: None
   Export policy: None
 Information about SA-Requests:
   Policy to accept SA-Requests: None
   Sending SA-Requests status: Disable
 Minimum TTL to forward SA with encapsulated data: 0
 SAs learned from this peer: 0, SA cache maximum for the peer: 4294967295
 Input queue size: 0, Output queue size: 0
 Counters for MSDP messages:
   RPF check failure: 0
   Incoming/outgoing SA: 0/0
   Incoming/outgoing SA-Request: 0/0
   Incoming/outgoing SA-Response: 0/0
   Incoming/outgoing Keepalive: 867/867
   Incoming/outgoing Notification: 0/0
   Incoming/outgoing Traceroutes in progress: 0/0
   Incoming/outgoing Traceroute reply: 0/0
   Incoming/outgoing Unknown: 0/0
   Incoming/outgoing data packet: 0/0