Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

show services application-identification application

 

Syntax

Release Information

Command introduced in Junos OS Release 11.4. Starting in Junos OS Release 15.1X49-D100, the options Cacheable, Activation Date, and Last modified are introduced for show services application-identification application detail command. The Underlying consolidated Protocols/ports application is dependent on and Layer-7 Immediate Protocol(s) options are introduced in Junos OS Release 18.2R1.

Description

Display detailed information about a specified application signature, detailed information about all application signatures, or a summary of the existing application signatures.

Options

detail Display detailed information for all application signatures.
summaryDisplay summary information for all application signatures.

Required Privilege Level

view

List of Sample Output

show services application-identification application summary

show services application-identification application detail

show services application-identification application detail (Custom Applications)

show services application-identification application detail (Unified Policies)

show services application-identification application detail (Junos OS Release 20.2R1)

Output Fields

Table 1 lists shows the output details for the show services application-identification application detail command.

Table 1: show services application-identification application summary Output Fields

Field Name

Field Description

Application(s)

The number of applications present.

Application

Name of the custom application.

Disabled

The status of the application and whether the mapping method is currently used to identify this application.

ID

The unique ID number of an application. ID numbers 1 through 32,767 are automatically generated for applications; these IDs do not change. ID numbers for custom applications use 16,777,216 to 33,554,431.

Order

Number used to specify priority when multiple applications match the traffic. The lowest order number takes the highest priority.

Table 2 lists the output fields for the show services application-identification application command. Output fields are listed in the approximate order in which they appear.

Table 2: show services application-identification application Output Fields

Field Name

Field Description

Application Name

Name of the application.

Application Type

The basic application type, such as HTTP.

Description

A description of the application.

Application ID

The unique ID number of an application signature. ID numbers 1 through 32,767 are automatically generated for application; these IDs do not change.

ID numbers for custom applications use 16,777,216 to 33,554,431.

Priority

Priority over other signature applications.

Order

Disabled

The status of the application and whether the mapping method is currently used to identify this application.

Cacheable

The status whether the application identification results caching is enabled or not for the application.

When this option is enabled, you can cache the application detection result in an ASC table.

Activation Date

Date when the application was activated for the first time.

Last Modified

Date when the application was last updated.

Number of Parent Group(s)

Total number of parent groups in this application signature group or cluster.

Underlying consolidated Protocols/ports application is dependent on

List of default protocols and ports for dependent applications of the specified application.

  • Protocols—List of default protocols.

  • TCP ports—List of default TCP ports.

Layer-7 Immediate Protocol(s)

List of applications over which that dynamic application can be identified.

Application Specific Ports:

The default port for this application type.

Signature:

Signature mapping criteria for application identification

Protocol

Application protocol

Port range

Port range. This option is applicable for TCP or UDP-based applications only.

Member(s)

Member name for a custom application signature.

  • Depth–Maximum number of bytes to check for context match. Byte limit for AppID to identify custom application pattern for applications running over TCP or UDP or Layer 7 applications.

  • Context–Service-specific context, such as http-header-content-type.

  • Pattern–Deterministic finite automaton (DFA) pattern matched on the context. The DFA pattern specifies the pattern to be matched for the signature.

  • Direction–Connection direction of the packets to match pattern (example : CTS [client-to-server])

Sample Output

show services application-identification application summary

user@host> show services application-identification application summary

show services application-identification application detail

user@host> show services application-identification application detail junos:FTP

show services application-identification application detail (Custom Applications)

user@host> show services application-identification application detail my-custom-app

Sample Output

show services application-identification application detail (Unified Policies)

user@host> show services application-identification application detail

show services application-identification application detail (Junos OS Release 20.2R1)

user@host> show services application-identification application detail