Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Defining an Application Identification

To configure a specific IP address or port-based application identification, include the application application-name statement at the [edit services application-identification] hierarchy level:

You can include the following general properties in the configuration:

  • application—Application name, a required statement; maximum 31 characters. Predefined applications have the prefix junos- to avoid conflict with user-defined ones.

  • idle-timeout—Amount of time that a session remains idle before it is deleted.

  • index—Application index number in the range from 1 through 65,534, with integers 1 through 1024 reserved for predefined applications.

  • session-timeout—Lifetime of a session.

  • type—Well known applications, such as HTTP or FTP.

  • type-of-service—Type of service, defined by service objective. There is no default value; options are maximize-reliability, maximize-throughput, minimize-delay, and minimize-monetary-cost.

  • disable—Disable this application definition in the APPID service.


You can also specify session and idle timeout values globally for a Multiservices interface by including the following statements at the [edit interfaces interface-name services-options] hierarchy level:

  • inactivity-non-tcp-timeout—Inactivity timeout period for non-TCP established sessions.

  • inactivity-tcp-timeout—Inactivity timeout period for TCP established sessions.

  • session-timeout—Lifetime of a session.

  • disable-global-timeout-override—Disallow overriding a global inactivity or session timeout.

You can include the following port-mapping properties at the [edit services application-identification port-mapping] hierarchy level:

  • port-range—TCP or UDP port number or numeric range, entered as [minimum-valuemaximum-value]. For port-mapping configurations, this entry is required if the parent node exists.

  • disable—Disable port-mapping properties for this application.


    For applications with signatures for both client-to-server and server-to-client directions, the APPID for Junos Application Aware (previously known as Dynamic Application Awareness) must accept the data packets in both directions on the same session to complete the identification process.

For a configuration example, see Examples: Configuring Application Identification Properties.