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:

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 29 shows the topology used in this example.

Figure 29: AMT Gateway Topology

Image g040622.gif

Configuration

CLI Quick Configuration

To quickly configure the AMT protocol on R1, copy the following commands and paste them into the CLI.

[edit]set protocols amt traceoptions file amt.log set protocols amt traceoptions flag errors set protocols amt traceoptions flag packets detail set protocols amt traceoptions flag route detail set protocols amt traceoptions flag state detail set protocols amt traceoptions flag tunnels detail set protocols amt relay family inet anycast-prefix 10.10.10.10/32 set protocols amt relay family inet local-address 10.255.112.201 set protocols amt relay tunnel-limit 10 set protocols pim interface all mode sparse-dense set protocols pim interface all version 2 set protocols pim interface fxp0.0 disableset chassis fpc 0 pic 0 tunnel-services bandwidth 1g

Step-by-Step Procedure

To configure the AMT protocol on R1:

  1. Configure AMT tracing operations.

    [edit]user@host# edit protocols amt traceoptions[edit protocols amt traceoptions]user@host# set file amt.log [edit protocols amt traceoptions]user@host# set flag errors [edit protocols amt traceoptions]user@host# set flag packets detail [edit protocols amt traceoptions]user@host# set flag route detail [edit protocols amt traceoptions]user@host# set flag state detail [edit protocols amt traceoptions]user@host# set flag tunnels detail [edit protocols amt traceoptions]user@host# exit
  2. Configure the AMT relay settings.

    [edit]user@host# edit protocols amt relay[edit protocols amt relay]user@host# set relay family inet anycast-prefix 10.10.10.10/32 [edit protocols amt relay]user@host# set family inet local-address 10.255.112.201 [edit protocols amt relay]user@host# set tunnel-limit 10 [edit protocols amt relay]user@host# exit
  3. Configure PIM on R1’s interfaces.

    [edit]user@host# edit protocols pim[edit protocols pim]set interface all mode sparse-dense [edit protocols pim]set interface all version 2 [edit protocols pim]set interface fxp0.0 disable[edit protocols pim]exit
  4. Enable tunnel functionality.

    [edit]user@host# edit chassis[edit chassis]set fpc 0 pic 0 tunnel-services bandwidth 1g
  5. If you are done configuring the device, commit the configuration.

    [edit chassis]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 configuration instructions in this example to correct it.

user@host# show chassisfpc 0 {pic 0 {tunnel-services {bandwidth 1g;}}}
user@host# show protocolsamt {traceoptions {file amt.log;flag errors;flag packets detail;flag route detail;flag state detail;flag tunnels detail;}relay {family {inet {anycast-prefix 10.10.10.10/32;local-address 10.255.112.201;}}tunnel-limit 10;}}pim {interface all {mode sparse-dense;version 2;}interface fxp0.0 {disable;}}

Verification

To verify the configuration, run the following commands:

Related Topics