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 Next-Hop Style Services on an Aggregated Multiservices Interface

Hardware and Software Requirements

MX Series routers with services interfaces installed and running Junos OS Release 13.2.

Overview

Starting with Release 13.2, Junos OS extends next-hop style services support to aggregated multiservices (AMS) interfaces. In releases earlier than 12.3, only interface style services configurations were supported on AMS interfaces.

The next-hop style services configuration on AMS interfaces is different from the interface style services configuration. For next-hop style services, the load-balancing hash keys are defined as part of the logical unit configuration of the AMS interface. For interface style services, the hash keys configuration falls under the service-set configuration.

This example explains the next-hop style services configuration on an AMS interface, and shows the verification steps to verify that the configuration is working correctly.

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. Configure an aggregated multiservices interface and the load-balancing options.
   [edit interfaces ams0]user@router1# set load-balancing-options member-interface mams-1/0/0user@router1# set load-balancing-options member-interface mams-1/1/0user@router1# set load-balancing-options member-interface mams-2/0/0user@router1# set load-balancing-options member-interface mams-2/1/0user@router1# set unit 1 family inetuser@router1# set unit 1 service-domain insideuser@router1# set unit 2 family inetuser@router1# set unit 2 service-domain outside
2. Configure routing instances that use the aggregated multiservices interfaces configured in the first step.
   [edit routing-instances]user@router1# set ri-internal instance-type virtual-routeruser@router1# set ri-internal interface ge-0/0/2.0user@router1# set ri-internal interface ams0.1user@router1# set ri-internal routing-options static route 22.22.22.0/24 next-hop ams0.1user@router1# set ri-external instance-type virtual-routeruser@router1# set ri-external interface ge-2/0/6.0user@router1# set ri-external interface ams0.2user@router1# set ri-external routing-options static route 0.0.0.0/0 next-hop ams0.2
3. Configure hash keys for the aggregated multiservices interfaces.

   Note: Unlike in the interface-style configuration where hash keys are defined in the service-set configuration, for next-hop services, the hash keys are specified in the AMS configuration under the logical units.

   [edit interfaces ams0]user@router1# set unit 1 load-balancing-options hash-keys ingress-key source-ip protocoluser@router1# set unit 2 load-balancing-options hash-keys ingress-key destination-ip protocol
4. Configure next-hop style services under the service-set configuration.
   [edit services service-set ams-test]user@router1# set stateful-firewall-rules sfw1user@router1# set next-hop-service inside-service-interface ams0.1user@router1# set next-hop-service outside-service-interface ams0.2
5. Commit the configuration.
   [edit]user@router1# commit

Results

From the configuration mode, confirm your configuration by entering the show interfaces ams0, show routing-instances, and show services service-set ams-test commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.