interface (Services PIC)

Syntax

Hierarchy Level

Description

Specify one or more of the MS-MPC service interfaces that represent the service PICs used for anchoring subscriber-aware services in the MX Series router. The following conditions are applicable to the services PIC interfaces configured here:

If an aggregated multiservices interface (ams) is specified in this statement, the ams must already be defined at the [edit interfaces] hierarchy level.
The PIC must have the jservices-hcm, jservices-mss, jservices-jdpi, jservices-pcef, and jservices-crypto-base packages configured at the [edit chassis fpc slot-number pic pic-number adaptive-services service-package extension-provider] hierarchy level.
The appropriate services group configuration must be applied to the PIC:
- For each service PIC that requires application identification but not HTTP header enrichment, apply the tdf-services-xlp-dpi group.
- For each service PIC that requires both application identification and HTTP header enrichment, configure the tdf-services-xlp-dpi-with-hcm group.
If an MS-MPC service interface is a member of an AMS, then that member interface cannot be specified here. For example, if mams-2/0/0 is a member interface of ams0, then ms-2/0/0/ cannot be directly specified here.

Note:

If an AMS (for example ams0) is used for the services PIC, then load balancing is performed to distribute subscriber-aware services among the member interfaces. Otherwise, load balancing is not performed.

Options

interface-name

Name of the interface representing the services PIC.

Syntax: The interface must be a valid multiservices interface (amsn or ms-a/b/0, where n is the ams number, a is the Flexible PIC Concentrator [FPC] slot number, and b is the PIC slot number); for example, ams0 or ms-1/0/0.

Required Privilege Level

unified-edge—To view this statement in the configuration.

unified-edge-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 17.1.

ON THIS PAGE