context (Application Identification)
Syntax
Hierarchy Level
[edit services application-identification application application-name over protocol-type signature name member name ]
Release Information
Statement introduced in Junos OS Release 15.1X49-D40.
Description
Specify context for matching application running over TCP, UDP, or Layer 7.
Application identification supports custom application signatures to detect applications as they pass through the device. You can create custom application signatures for applications based on ICMP, IP protocol, IP address, and Layer 7. While configuring custom application signatures, you must specify context values that the device can use to match patterns in the application traffic.
Options
Examples of context types with direction. When configuring custom application signatures, the context-direction combinations as mentioned in Table 1 is supported. Any other combination other than this is not supported.
Table 1: Supported Context-Direction Combination for Custom Application Signatures
Context | Direction |
---|---|
http-get-url-parsed-param-parsed | client-to-server |
http-header-host | client-to-server |
http-header-user-agent | client-to-server |
http-post-url-parsed-param-parsed | client-to-server |
http-post-variable-parsed | client-to-server |
http-url-parsed | client-to-server |
http-url-parsed-param-parsed | client-to-server |
ssl-server-name | client-to-server |
stream | any/client-to-server/server-to-client |
http-header-content-type | any/client-to-server/server-to-client |
http-header-cookie | any/client-to-server/server-to-client |
If you are planning to upgrade the device to Junos OS release 15.1X49-D60 from the previous versions of the Junos OS, you must change the configuration to the valid combination of context-direction as mentioned in Table 1 to avoid any commit failure and possible disabling of the secondary node.
Required Privilege Level
services—To view this statement in the configuration.
services-control—To add this statement to the configuration.