Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring an Aggregated Multiservices Interface (AMS)

Hardware and Software Requirements

This example requires MX Series routers that have services interfaces installed in that and Junos OS Release 13.2 running on that.

Overview

The aggregated multiservices (AMS) interface configuration in Junos OS enables you to combine multiple services interfaces to create a bundle of interfaces that can function as a single interface. This example shows you how to configure an AMS interface, load-balancing options, member failure options, high availability settings on an AMS interface, and an interface-style service set configuration that uses the AMS interface.

For more information about AMS interfaces, see Understanding Aggregated Multiservices Interfaces.

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

1. Create an aggregated multiservices interface and add member interfaces.

   Note: You cannot configure the same mams to be part of two different AMS interfaces at the same time.

   [edit]user@router1# set interfaces ams0 load-balancing-options member-interface mams-0/0/0user@router1# set interfaces ams0 load-balancing-options member-interface mams-0/1/0user@router1# set interfaces ams0 load-balancing-options member-interface mams-1/0/0user@router1# set interfaces ams0 load-balancing-options member-interface mams-1/1/0user@router1# set interfaces ams0 load-balancing-options member-interface mams-2/0/0user@router1# set interfaces ams0 load-balancing-options member-interface mams-2/1/0
2. Configure logical units for the AMS interface.

   Note: An AMS interface and its member interfaces cannot share the same logical interface units. For example, if one of the member interfaces has logical units 1 and 2 configured on it, you cannot configure logical units 1 and 2 for the AMS. Similarly, if you have configured logical units 3 and 4 on the AMS, you cannot configure those units on any of the member interfaces.

   [edit interfaces]user@router1# set ams0 unit 1 family inet
3. Configure member failure options.
   [edit interfaces ams0]user@router1# set load-balancing-options member-failure-options drop-member-traffic rejoin-timeout 300user@router1# set load-balancing-options member-failure-options drop-member-traffic enable-rejoin

   Note: This example shows the drop-member-traffic configuration. However, you if you would like to redistribute the traffic to other available members when one of the member interfaces goes down, you can include the redistribute-all-traffic statement instead of the drop-member-traffic statement. The default behavior, when the member-failure-options configuration is not included, is to redistribute the traffic among available member interfaces.

4. Configure the high-availability options.
   [edit interfaces ams0]user@router1# set load-balancing-options high-availability-options many-to-one preferred-backup mams-1/0/0
5. Configure interface style services.
   [edit services]user@router1# set service-set ams-ss1 interface-service service-interface ams0.1user@router1# set service-set ams-ss1 interface-service load-balancing-options hash-keys ingress-key source-ipuser@router1# set service-set ams-ss1 interface-service load-balancing-options hash-keys egress-key destination-ip
6. If you are done configuring the device, commit the configuration.
   [edit]user@router1# commit

   Table 1: Key Configuration Statements Used in this Example

   Statement	Description
   member-interface	Adds a member interface (mams) to the AMS bundle.
   drop-member-traffic	Specifies that all traffic to a member be dropped in case the member interface fails.
   rejoin-timeout	Specifies the time interval, in seconds, for the AMS to wait before declaring a member interface down. If the failed member comes back online during this period, it can rejoin the AMS and resume traffic forwarding. The range is 0 through 1000 seconds.
   enable-rejoin	Specifies whether a failed interface be allowed to rejoin the AMS when it comes back online. If this statement is not included in the configuration, you must manually add the interface to the AMS when the interface is back online.
   preferred-backup	Designates a member interface as the floating backup.
   interface-services	Specifies a service interface, an AMS interface in this example, to handle interface services.
   hash-keys	Specifies the load-balancing hash keys. You can configure the following hash key values: source-ip, destination-ip, iif (incoming interface), oif (outgoing interface), and protocol. Note: For services that require traffic symmetry, you must configure symmetrical hashing. Symmetrical hashing configuration ensures that both forward and reverse traffic are routed through the same member interface.

Results

From the configuration mode, confirm your configuration by entering the show interfaces ams0 command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Verification

Confirm that the configuration is working properly.

• Verifying the AMS Configuration

Verifying the AMS Configuration

Purpose

Verify the AMS configuration and status of member interfaces.

Action

From operational mode, enter the show command.

Load-balancing interfaces detail
Interface        : ams0
  State          : Up
  Last change    : 00:01:28
  Member count   : 6
  HA Model       : Many-to-One
  Members        :
      Interface    Weight   State
      mams-0/0/0   10       Active
      mams-0/1/0   10       Active
      mams-1/0/0   10       Backup
      mams-1/1/0   10       Active
      mams-2/0/0   10       Active
      mams-2/1/0   10       Active

Meaning

Shows that ams0 has six member interfaces with a many-to-one backup configuration. Of the six member interfaces, five are in active state and one, mams-1/0/0, is in backup state.