host1(config-profile)#
exit
2.
Configure a dynamic interface profile to specify the IP interface or 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
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 ip 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 configuration 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 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 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.
host1:pe1(config)#
virtual-router pe1:pe13
Creating Multicast VPNs
■
103
Chapter 3: Configuring PIM for IPv4 Multicast
Содержание JUNOSE 11.1.X MULTICAST ROUTING
Страница 6: ...vi...
Страница 8: ...viii JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 16: ...xvi List of Figures JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 18: ...xviii List of Tables JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 24: ...2 Internet Protocol Version 4 JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 64: ...42 Investigating Multicast Routes JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 100: ...78 Monitoring IGMP Proxy JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 145: ...Monitoring PIM 123 Chapter 3 Configuring PIM for IPv4 Multicast...
Страница 146: ...124 Monitoring PIM JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 166: ...144 Monitoring DVMRP JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 168: ...146 Internet Protocol Version 6 JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 204: ...182 BGP Multicast JUNOSe 11 1 x Multicast Routing Configuration Guide...
Страница 263: ...Part 3 Index Index on page 243 Index 241...
Страница 264: ...242 Index JUNOSe 11 1 x Multicast Routing Configuration Guide...