peer-groups (control plane peers)
Syntax
peer-groups name {
heartbeat-interval seconds;
n3-requests n3-requests;
path-management (disable | enable);
peer {
address [ address ... ];
hostname hostname;
}
routing-instance routing-instance;
t3-response seconds;
}
Hierarchy Level
[edit services mobile-edge gateways saegw name control-plane-peers]
Description
If at least one peer group is configured, PFCP packets from control plane peers matching this address/prefix alone are accepted. The control plane peers are bound to the routing instance defined within this peer group, if configured. Otherwise the control plane function is bound to the routing instance listed under control-plane-peers.
Options
| name | Peer group name |
| heartbeat-interval | Time between origination of two successive heartbeat requests (seconds).
|
| 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.
|
| peer | IPv4 or IPv6 address or prefix value (required) of the PFCP peer and hostname (optional) of the PFCP peer. |
| routing-instance | Local routing instance of the PFCP peer. |
| 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.