The application identification set of services adds support for Intrusion Detection and Prevention (IDP) functionality using Deep Packet Inspection (DPI) technology to MX-series platforms equipped with MultiServices DPCs. IDP is already supported on J-series platforms and is described in J-series Services Router documentation. To configure IDP properties, include statements at the [edit security idp] hierarchy level. You configure IDP processes by including the idp-policy statement at the [edit system processes] hierarchy level. To specify an IDP profile, include the idp-profile statement at the [edit services service-set] hierarchy level. To configure SNMP IDP objects, include the idp statement at the [edit snmp health-monitor] hierarchy level. Operational commands for monitoring and regulating IDP activity use the clear/request/show security idp command syntax.
![]() |
Note: On MX-series routers, the IDP ip-action statement is supported on TCP, UDP, and ICMP flows. When the ip-action target is service, the ip-action flow is applied if the traffic matches the values specified for source port, destination port, source address, and destination address. However, for ICMP flows, the destination port is 0, so that any ICMP flow matching source port, source address, and destination address would be blocked. For more information on the ip-action statement, see the JUNOS Software CLI Reference for J-series Services Routers and SRX-series Services Gateways. |