Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    interfaces (Aggregated Multiservices)


    interfaces interface-name {load-balancing-options {high-availability-options {many-to-one {preferred-backup preferred-backup;}}member-failure-options {drop-member-traffic {rejoin-timeout rejoin-timeout;}redistribute-all-traffic {enable-rejoin;}}member-interface interface-name;}unit interface-unit-number {family family;}}

    Hierarchy Level


    Release Information

    Statement introduced in Junos OS Mobility Release 11.2W.


    Configure the aggregated multiservices (AMS) interface. The AMS interface provides the infrastructure for load balancing and high availability (HA).

    The high availability feature is used for mobile control plane redundancy and for service applications (application-level gateway [ALG], Network Address Translation [NAT], and stateful firewall). The load-balancing feature is currently used only for service applications. For service applications, load balancing can be used with or without high availability. Mobile control plane load balancing is done by the ingress Packet Forwarding Engine.

    Note: The interfaces must be valid aggregated multiservices interfaces (ams); for example, ams0 or ams1, and so on. The ams infrastructure is supported only in chassis with Trio-based modules and Multiservices Dense Port Concentrators (MS-DPCs).

    The remaining statements are explained separately.



    Name of the aggregated multiservices interface (ams); for example, ams0 or ams1, and so on.

    Required Privilege Level

    interface—To view this statement in the configuration.

    interface-control—To add this statement to the configuration.

    Published: 2011-11-22