Technical Documentation

Applying L-PDF Profiles to Service Sets

You can optionally apply policy decision statistics profiles as part of a service-set definition. To do this, you include the policy-decision-statistics-profile statement at the [edit services service-set service-set-name] hierarchy level:

policy-decision-statistics-profile profile-name;

You can include only one profile name in the specification for the application-aware access-list statement.

The following example shows a sample configuration for attachment of an L-PDF statistics profile:

services {service-set test_aacl_sset {aacl-rules aacl_rule;policy-decision-statistics-profile {pdf_stats_prof;}interface-service {service-interface ms-0/3/0.0;}}}

Note: Only one service sets can be applied to a single interface when L-PDF functionality is used.

The following example shows a sample configuration for attachment of a service set to a static interface:

interfaces {fe-0/0/0 {vlan-tagging;unit 1 {vlan-id 1;family inet {service {input {service-set test_aacl_sset;}output {service-set test_aacl_sset;}}address 10.1.1.1/24;}}}}

Note: The session-offload statement at the [edit chassis fpc slot-number pic number adaptive-services service-package extension-provider] hierarchy level controls session offload behavior for Multiservices DPCs on MX Series routers. It controls session offload on a per-device basis, where a device is a Multiservices interface (ms-fpc-pic-port). Currently, the session offload function is supported for at most one Multiservices interface. When offload function is enabled, it is strongly recommended that you limit Dynamic Application Awareness features to that Multiservices interface.

The default is to not offload any sessions. For more information on chassis configuration, see the Junos System Basics Configuration Guide.

Related Topics


Published: 2010-07-19

Help
|
My Account
|
Log Out