Related Documentation
- M Series
- Configuring the AMT Protocol
- Configuring Default IGMP Parameters for AMT Interfaces
- AMT Applications
- MX Series
- Configuring the AMT Protocol
- Configuring Default IGMP Parameters for AMT Interfaces
- AMT Applications
- SRX Series
- Configuring the AMT Protocol
- Configuring Default IGMP Parameters for AMT Interfaces
- AMT Applications
- T Series
- Configuring the AMT Protocol
- Configuring Default IGMP Parameters for AMT Interfaces
- AMT Applications
Example: Configuring the AMT Protocol
This example shows how to configure the Automatic Multicast Tunneling (AMT) Protocol to facilitate dynamic multicast connectivity between multicast-enabled networks across islands of unicast-only networks.
Requirements
Before you begin:
- Configure the router interfaces.
- Configure an interior gateway protocol or static routing. See the Junos OS Routing Protocols Library for Security Devices.
- Configure a multicast group membership protocol (IGMP or MLD). See Understanding IGMP and Understanding MLD.
Overview
In this example, Host 0 and Host 2 are multicast receivers in a unicast cloud. Their default gateway devices are AMT gateways. R0 and R4 are configured with unicast protocols only. R1, R2, R3, and R5 are configured with PIM multicast. Host 1 is a source in a multicast cloud. R0 and R5 are configured to perform AMT relay. Host 3 and Host 4 are multicast receivers (or sources that are directly connected to receivers). This example shows R1 configured with an AMT relay local address and an anycast prefix as its own loopback address. The example also shows R0 configured with tunnel services enabled.
Figure 1 shows the topology used in this example.
Figure 1: AMT Gateway Topology

Configuration
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.
To configure the AMT protocol on R1:
Configure AMT tracing operations.
[edit protocols amt traceoptions]user@host# set file amt.log user@host# set flag errors user@host# set flag packets detail user@host# set flag route detail user@host# set flag state detail user@host# set flag tunnels detailConfigure the AMT relay settings.
[edit protocols amt relay]user@host# set relay family inet anycast-prefix 10.10.10.10/32 user@host# set family inet local-address 10.255.112.201 user@host# set tunnel-limit 10Configure PIM on R1’s interfaces.
[edit protocols pim]set interface all mode sparse-dense set interface all version 2 set interface fxp0.0 disableEnable tunnel functionality.
[edit chassis]set fpc 0 pic 0 tunnel-services bandwidth 1gIf you are done configuring the device, commit the configuration.
user@host# commit
Results
From configuration mode, confirm your configuration by entering the show chassis and show protocols commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.
Verification
To verify the configuration, run the following commands:
Related Documentation
- M Series
- Configuring the AMT Protocol
- Configuring Default IGMP Parameters for AMT Interfaces
- AMT Applications
- MX Series
- Configuring the AMT Protocol
- Configuring Default IGMP Parameters for AMT Interfaces
- AMT Applications
- SRX Series
- Configuring the AMT Protocol
- Configuring Default IGMP Parameters for AMT Interfaces
- AMT Applications
- T Series
- Configuring the AMT Protocol
- Configuring Default IGMP Parameters for AMT Interfaces
- AMT Applications

