Configuring Multiple SCTP and Protocol Pod Pairs

To configure multiple SCTP and Protocol pod pairs use the following configuration:

config 
    instance instance_id instance_id 
    endpoint endpoint_name 
    replicas replicas_per_node 
    service service_name 
        interface interface_name instancetype instance_type 
        internal-port internal_port_config 
        vip-ip ip_address vip-port port_number 
        offline vip-interface vip_interface_name 
        vip-ip6 ip_address vip-ipv6-port port_number  
        offline vip-interface 
        end 

NOTES:

  • instance instance_id instance_id —Specify the endpoint instance ID. Must be an integer in the range of 1-4.

  • endpoint endpoint_name —Specify the endpoint name.

    Note

    In this release, it is recommended not to configure any service under NGAP. Currently, only one service can be configured under NGAP.

  • replicas replicas_per_node —Specify the number of replicas per node.

  • service service_name —Specify the service name.

  • interface interface_name —Specify the endpoint interfaces, as the name of the SCTP in this multiple SCTP configuration. sctp-1-sctp-primary is an example.

  • instancetype instance_type —Specify the instance type. Must be one of the following:

    • Dual

    • IPv4

    • IPv6

    The default value is Dual.

  • internal-port internal_port_config —Specify the internal base-port to start the endpoint. It includes your required internal-ports and their ID from the list of available ports.

    • admin—Admin port for SCTP. The default value is 7879.

    • ipc—IPC port for SCTP. The default value is 9005.

    • keepalived—keepalived port for SCTP. The default value is 29000.

    • metrics—metrics port for SCTP. The default value is 7083.

    • pprof—pprof port for SCTP. The default value is 7850.

    Note

    It is mandatory to configure the internal-ports CLI when more than one SCTP service is configured or more than one AMF is deployed on the same k8 cluster.

  • vip-ip ip_address vip-port port_number offline —Specify the IPv4 address of the pod on which the VIP is enabled. Also, specify the interface and port number. This configuration marks vip-ip as offline or standby.

    Note

    When AMF receives SCTP INIT from IPv4 address and no address is included in INIT chunk address list, AMF responds with all IPv4 and IPv6 addresses in SCTP INIT_ACK.

  • vip-interface vip_interface_name —Specify the VIP interface and port number. This configuration marks vip-ip as offline or standby.

    Note

    To support multi-homing, AMF listens on multiple IP address as configured.Currently, AMF uses VIP to support high availability of SCTP pods. For multi-homing, multiple VIP addresses should be configured.

    It is recommended to use different physical interfaces for each different VIP so that AMF can have different routes for each VIP address.

  • vip-ip6 ip_address vip-ipv6-port port_number —Specify the new IPv6 address and port number.

    Note

    When AMF receives SCTP INIT from IPv6 address and no address is included in INIT chunk address list, AMF respond with only IPv6 addresses in SCTP INIT_ACK.

After the VIP-IP and VIP-Ports are up, modify the gNBs configuration to refer to the new VIP-IP and port.