over (Application Identification)
Syntax
over protocol-type {
chain-order;
signature name {
member name {
context {
context;
}
direction {
any;
client-to-server;
server-to-client;
}
pattern pattern;
depth byte-number;
}
port-range value;
Hierarchy Level
[edit services application-identification application]
Hierarchy Level
[edit services application-identification application application-name]
Description
Specify set of L4/L7 application that carries given application
Configure a custom signature based on Layer 4/Layer 7 applications. You create Layer 7-based custom application signatures for the identification of multiple applications running on the same Layer 7 protocols. For example, applications such as Facebook and Yahoo Messenger can both run over HTTP, but there is a need to identify them as two different applications running on the same Layer 7 protocol.
Options
| protocol-type | Application protocol |
| chain-order |
The order of members is used to match the pattern (Next Gen Services) |
| signature name | Name of the custom application signature. Must be a unique name with a maximum length of 63 characters. |
| member name | Member name for a custom application signature. Custom signatures can contain multiple members that define attributes for an application. (The supported member name range is m01 through m15.) |
| context | Service-specific context, such as http-header-content-type. |
| direction | Connection direction of the packets to match pattern |
| patterns | (Optional) Deterministic finite automaton (DFA) pattern matched on the context. The DFA pattern specifies the pattern to be matched for the signature. Maximum length is 128. |
| depth | Maximum number of bytes to check for context match. Use the byte limit for AppID to identify custom application pattern for applications running over TCP or UDP or Layer 7 applications. |
| port-range | Port range. This option is applicable for TCP or UDP-based applications only. |
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
services—To view this statement in the configuration.
services-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 15.1X49-D40.
Support for Next Gen Services introduced in Junos OS Releases 19.3R2 and 19.4R1 on MX Series MX240, MX480 and MX960 using the MX-SPC3 services card.