JUNOSe 10.0.2 Release Notes

Configuring the Data MDTs

To configure data MDTs:

1. Configure a dynamic interface profile to specify the PIM configuration of the IP interface or MTI interface in the VRF.
host1(config)#profile pe13DataMdtMti
host1(config-profile)#ip virtual-router pe1:pe13
host1(config-profile)#ip unnumbered loopback 0
host1(config-profile)#ip pim sparse-mode
host1(config-profile)#exit
2. Configure a dynamic interface profile to specify the IP interface or MDT interface in the parent.
host1(config)#profile pe1DataMdtMdt
host1(config-profile)#ip virtual-router pe1
host1(config-profile)#ip unnumbered loopback 0
host1(config-profile)#ip pim sparse-mode
host1(config-profile)#exit
3. Configure the destination profile for dynamic IP tunnel creation.
host1(config)#gre destination profile pe13DataMdtProfile virtual-router pe1
host1(config-dest-profile)#tunnel source 1.1.1.1
host1(config-dest-profile)#tunnel destination subnet 233.3.0.0/16
host1(config-dest-profile)#tunnel mdt profile pe1DataMdtMdt
host1(config-dest-profile)#profile pe13DataMdtMti
host1(config-dest-profile)#exit

The router uses this destination profile to verify whether it can create a dynamic tunnel, and to supply additional parameters when it creates a tunnel. For more information about creating dynamic IP tunnels, see Configuring Dynamic IP Tunnels in the JUNOSe IP Services Configuration Guide.

4. Configure the group address pools in the route map.
host1(config)#virtual-router pe1
host1:pe1(config)# ip pim group-address-pool pe13DataMdtGroups 233.3.1.0 233.3.1.255

If the data MDTs are established using any-source multicast (ASM), you must divide the range of available MDT P-Group addresses so that PEs source VPN multicasts. All VRFs in a PE draw from a single address pool that contains the range of group addresses assigned to that PE.

If the data MDTs are established using source-specific multicast (SSM), you can configure VRFs to transmit on a tunnel using the same MDT P-Group address. Each VRF transmits using a unique P-Source address; however, each data MDT created by the VRF must use a different P-Group address. There might be one sender data MDT and possibly many receiver data MDTs sharing an IP tunnel.

For SSM, each PE can assign MDT P-Groups from the same range, but the P-Group addresses must be administratively divided among the VPNs as mentioned in the following example:

host1(config)#virtual-router pe1
host1:pe1(config)#ip pim group-address-pool pe11DataMdtSSMGroups 233.3.1.0 233.3.1.255
host1:pe1(config)#ip pim group-address-pool pe12DataMdtSSMGroups 233.3.2.0 233.3.2.255
host1:pe1(config)#ip pim group-address-pool pe13DataMdtSSMGroups 233.3.3.0 233.3.3.255
5. Configure the access list to match <S,G> and <*,G> entries. For more information about <S,G> and <*,G>, see the Creating Multicast VPNs Using the Data MDT section in Chapter 3, Configuring PIM for IPv4 Multicast of the JUNOSe Multicast Routing Configuration Guide.
host1:(config)#virtual-router pe1:pe13
host1:pe1:pe13(config)#access-list pe13DataMdtSend permit ip host 10.13.0.100 225.1.1.0 0.0.0.255
host1:pe1:pe13(config)#access-list pe13DataMdt permit ip any 225.1.0.0 0.0.255.255
6. Specify a route map to configure the set of <S, G> for which data MDTs can be created, and the threshold to be applied for each SG.
host1:pe1:pe13(config)#route-map pe13MdtThresholds permit 10
host1:pe1:pe13(config-route-map)#match ip address pe13DataMdtSend
host1:pe1:pe13(config-route-map)#set threshold 0
host1:pe1:pe13(config-route-map)#route-map pe13MdtThresholds permit 20
host1:pe1:pe13(config-route-map)#match ip address pe13DataMdt
host1:pe1:pe13(config-route-map)#exit
7. Configure the data MDT.
host1:pe1:pe13(config)#ip pim data-mdt
host1:pe1:pe13(config-ip-pim-data-mdt)#tunnel source 1.1.1.1
host1:pe1:pe13(config-ip-pim-data-mdt)#tunnel group-address-pool pe13DataMdtGroups
host1:pe1:pe13(config-ip-pim-data-mdt)#route-map pe13MdtThresholds