Configuring Data MDTs

To configure data MDTs:

1. Configure a dynamic interface profile to specify the PIM configuration of the IP/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

2. Configure a dynamic interface profile to specify the IP/MDT interface in the parent.

   host1(config-profile)#profile pe1DataMdtMdt

   host1(config-profile)#ip virtual-router pe1

   host1(config-profile)#ip unnumbered loopback 0

   host1(config-profile)#ip pim sparse-mode

3. Configure the destination profile for dynamic IP tunnel creation.

   host1(config-profile)#gre destination profile pe13DataMdtProfile
   virtual-router pe1

   host1(config-dest-profile)#tunnel destination subnet 233.3.0.0 255.255.0.0

   host1(config-dest-profile)#tunnel source 1.1.1.1

   host1(config-dest-profile)#tunnel mdt profile pe1DataMdtMdt

   host1(config-dest-profile)#profile pe13DataMdtMti

   host1(config-dest-profile)#virtual-router pe1

   For more information about creating dynamic IP tunnels, see Configuring Dynamic IP Tunnels in the JUNOSe IP Services Configuration Guide.

4. Configure the VRF, including an access list to match <S,G> and <*,G> entries.

   host1:pe1(config)#ip vrf pe13

   host1:pe1(config-vrf)#rd 100:13

   host1:pe1(config-vrf)#route-target both 100:3

   host1:pe1(config-vrf)#interface tunnel gre:MTI-13.mdt

   host1:pe1(config-if)# ip unnumbered loopback 0

   host1:pe1(config-if)# ip pim sparse-mode

   host1:pe1(config-if)#access-list pe13DataMdt permit ip any 225.1.0.0 0.0.255.255

5. 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(config)#route-map pe13MdtThresholds permit 10

   host1:pe1(config-route-map)#match ip address pe13DataMdtSend

   host1:pe1(config-route-map)#set threshold 0

   host1:pe1(config-route-map)#route-map pe13MdtThresholds permit 20

   host1:pe1(config-route-map)#match ip address pe13DataMdt

6. Configure the group address pools in the route map.

   host1:pe1(config-route-map)#ip pim group-address-pool pe13DataMdtGroups 233.3.1.0 233.3.1.255

   If the data MDTs are established using 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 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.

7. Configure the tunnel for the VRF.

   host1:pe1(config)#virtual-router pe1:pe13

   host1:pe1:pe13(config)#interface tunnel gre:MTI-13 transport-virtual-router pe1

   host1:pe1:pe13(config)#tunnel source 1.1.1.1

   host1:pe1:pe13(config)#tunnel destination 235.3.3.3

   host1:pe1:pe13(config)#tunnel mdt

   host1:pe1:pe13(config)#ip unnumbered loopback 0

   host1:pe1:pe13(config)#ip pim sparse-mode

8. 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 pe13DataMdtG$

   host1:pe1:pe13(config-ip-pim-data-mdt)#route-map pe13MdtThresholds

ip pim

• Use to enable PIM on an interface.
• Example

  host1(config-if)#ip pim sparse-dense-mode

• Use the no version to disable PIM on an interface.
• See ip pim.

ip pim data-mdt

• Use to activate data MDTs and enter IP PIM Data MDT Configuration mode.
• Example

  host1(config)#ip pim data-mdt

• Use the no version to deactivate data MDTs.
• See ip pim data-mdt.

ip pim group-address-pool

• Use to configure PIM group address pools from which data MDT group addresses are allocated.
• Example

  host1(config)#ip pim group-address-pool pe21DataMDT 232.1.0.0 232.2.255.255

• There is no no version.
• See ip pim group-address-pool.

mdt-data-delay

• Use to configure a delay before switching to data MDT.
• The delay is measured by 0.1 seconds; the default is 30.
• Example

  host1(ip-pim-data-mdt-config)#mdt-data-delay 20

• Use the no version to return to the default.
• See mdt-data-delay.

mdt-data-holddown

• Use to configure the time in seconds before switching to the default MDT group from the data MDT group.
• The default is 60.
• Example

  host1(ip-pim-data-mdt-config)#mdt-data-holddown 200

• Use the no version to return to the default.
• See mdt-data-holddown.

mdt-data-timeout

• Use to configure the time in seconds before the flow leaves the data MDT group.
• The default is 180.
• Example

  host1(ip-pim-data-mdt-config)#mdt-data-timeout 160

• Use the no version to return to the default.
• See mdt-data-timeout.

mdt-interval

• Use to configure the time in seconds between successive MLD join TLV messages.
• The default is 60.
• Example

  host1(ip-pim-data-mdt-config)#mdt-interval 80

• Use the no version to return to the default.
• See mdt-interval.

set threshold

• Use to configure a threshold value for multicast VPN applications, including default MDT and data MDT.
• Example

  host1(config)#set threshold 30

• Use the no version to remove the threshold.
• See set threshold.

tunnel group-address-pool

• Use to configure a group address pool for a data MDT tunnel.
• Example

  host1(ip-pim-data-mdt-config)#tunnel group-address-pool dataMDT1

• Use the no version to delete the group address pool.
• See tunnel group-address-pool.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.