Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents

saegw control-plane-peers

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
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

content_copy zoom_out_map
[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).

  • Range: 60 through 255

  • Default: 60

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 control-plane-peers stanza for each control plane peer rather than define a single loopback address.

n3-requests

Maximim number of retries of PFCP request messages upon t3-response timeout.

  • Range: 1 through 5

  • Default: 3

path-management

Enable/disable origination of heartbeat message requests to control peers.

  • Default: Disabled

response-cache-timeout

Configure the timeout for the PFCP response cache (seconds).

  • Range: 0 through 255

  • Default: 0

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:

  • Only PFCP messages coming from control plane peers over the default routing instance are handled.

  • PFCP responses are only sent in the default routing instance.

  • PFCP messages coming over any other routing instance are dropped even if the destination address matches the defined local-address.

If a single routing instance is configured:

  • Only PFCP messages coming from control plane peers over the configured routing instance are handled.

  • PFCP responses are only sent through this routing instance.

  • PFCP messages coming over any other routing instance are dropped.

t3-response

Waiting time of gateway before retrying a PFCP signaling-request upon response timeout (seconds).

  • Range: 1 through 5

  • Default: 5

The remaining statements are explained separately. See CLI Explorer.

Required Privilege Level

system

Release Information

Statement introduced in Junos OS Release 19.4R1.

footer-navigation