Configuring Port Control Protocol
This topic describes how to configure port control protocol (PCP). PCP is supported on the MS-DPC, MS-100, MS-400, and MS-500 MultiServices PICs. Starting in Junos OS Release 17.4R1, PCP for NAPT44 is also supported on the MS-MPC and MS-MIC. Starting in Junos OS Release 18.2R1, PCP on the MS-MPC and MS-MIC supports DS-Lite. In Junos OS Release 18.1 and earlier releases, PCP on the MS-MPC and MS-MIC does not support DS-Lite. Starting in Junos OS release 20.2R1 PCP is supported on the MX-SPC3 security services card for CGNAT services.
Perform the following configuration tasks:
Configuring PCP Server Options
Configuring a PCP Rule
A PCP rule has the same basic options as all service set rules:
A
term
option that allows a single rule to have multiple applications.A term is not required when running the MX-SPC3 security services card for Next Gen Services.
A
from
option that identifies the traffic that is subject to the rule.A
then
option that identifies what action is to be taken. In the case of a PCP rule, this option Identifies the pcp server that handles selected traffic
Configuring a NAT Rule
To configure a NAT rule:
Configuring a Service Set to Apply PCP
To use PCP, you must provide the rule name (or name of a list
of rule names) in the pcp-rule rule-name
option.
Your service set must also identify any required nat-rule
and softwire-rule
.
SYSLOG Message Configuration
A new syslog class, configuration option, pcp-logs
, has been provided to control PCP log generation. It provides the
following levels of logging:
protocol
—All logs related to mapping creation, deletion are included at this level of logging.protocol-error
—–All protocol error related logs (such as mapping refresh failed, PCP look up failed, mapping creation failed). are included in this level of logging.system-error
—Memory and infrastructure errors are included in this level of logging.