R3303-HP HSR6800 Routers IP Multicast Configuration Guide

250
[PE2-GigabitEthernet2/1/1] quit
# Bind GigabitEthernet 2/1/2 with VPN instance b, configure an IP address and enable PIM-SM
on the interface.
[PE2] interface gigabitethernet 2/1/2
[PE2-GigabitEthernet2/1/2] ip binding vpn-instance b
[PE2-GigabitEthernet2/1/2] ip address 10.110.3.1 24
[PE2-GigabitEthernet2/1/2] pim sm
[PE2-GigabitEthernet2/1/2] quit
# Bind GigabitEthernet 2/1/3 with VPN instance a, configure an IP address and enable PIM-SM
on the interface.
[PE2] interface gigabitethernet 2/1/3
[PE2-GigabitEthernet2/1/3] ip binding vpn-instance a
[PE2-GigabitEthernet2/1/3] ip address 10.110.4.1 24
[PE2-GigabitEthernet2/1/3] pim sm
[PE2-GigabitEthernet2/1/3] quit
# Configure an IP address for Loopback 1, and enable PIM-SM.
[PE2] interface loopback 1
[PE2-LoopBack1] ip address 1.1.1.2 32
[PE2-LoopBack1] pim sm
[PE2-LoopBack1] quit
# Configure BGP.
[PE2] bgp 100
[PE2-bgp] group vpn-g internal
[PE2-bgp] peer vpn-g connect-interface loopback 1
[PE2-bgp] peer 1.1.1.1 group vpn-g
[PE2-bgp] peer 1.1.1.3 group vpn-g
[PE2–bgp] ipv4-family vpn-instance a
[PE2-bgp-a] import-route rip 2
[PE2-bgp-a] import-route direct
[PE2-bgp-a] quit
[PE2–bgp] ipv4-family vpn-instance b
[PE2-bgp-b] import-route rip 3
[PE2-bgp-b] import-route direct
[PE2-bgp-b] quit
[PE2–bgp] ipv4-family vpnv4
[PE2–bgp-af-vpnv4] peer vpn-g enable
[PE2-bgp-af-vpnv4] peer 1.1.1.1 group vpn-g
[PE2–bgp-af-vpnv4] peer 1.1.1.3 group vpn-g
[PE2–bgp-af-vpnv4] quit
[PE2–bgp] quit
The interface MTI 0 will automatically obtain an IP address after BGP peer configuration on PE 2.
This address is the loopback interface address specified in the BGP peer configuration. The PIM
mode running on MTI 0 is the same as the PIM mode running on all the interfaces in VPN instance
a.
The interface MTI 1 will automatically obtain an IP address after BGP peer configuration on PE 2.
This address is the loopback interface address specified in the BGP peer configuration. The PIM
mode running on MTI 1 is the same as the PIM mode running on all the interfaces in VPN instance
b.