saegw control-plane-peers
Syntax
control-plane-peers {
apn-services {
apns name {
mobile-interface mobile-interface;
source-validation {
}
}
heartbeat-interval seconds;
local-address [ local-address ... ];
n3-requests n3-requests;
path-management (disable | enable);
peer-groups name {
heartbeat-interval seconds;
initiate-association;
n3-requests n3-requests;
path-management (disable | enable);
peer {
address [ address ... ];
hostname hostname;
}
routing-instance routing-instance;
t3-response seconds;
}
response-cache-timeout seconds;
routing-instance routing-instance;
t3-response seconds;
}
Hierarchy Level
[edit services mobile-edge gateways saegw]
Description
Use this section to define the connection to and characteristics of control plane peers (SAEGW-C, SGW-C, or PGW-C).
Options
| heartbeat-interval |
Time between two successive heartbeat requests (seconds).
|
| local-address |
Required. IPv6 or IPv4 or both addresses of the local end of the PFCP connection. Note:
If you are connecting to multiple control plane peers, define the
local address under the |
| n3-requests |
Maximim number of retries of PFCP request messages upon t3-response timeout.
|
| path-management |
Enable/disable origination of heartbeat message requests to control peers.
|
| response-cache-timeout |
Configure the timeout for the PFCP response cache (seconds).
|
| routing-instance |
Local routing instance of the PFCP. This is used to determine in which routing instance the responses are to be sent for incoming PFCP messages. If a routing instance is not configured:
If a single routing instance is configured:
|
| t3-response |
Waiting time of gateway before retrying a PFCP signaling-request upon response timeout (seconds).
|
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
system
Release Information
Statement introduced in Junos OS Release 19.4R1.