Diameter Endpoint

Feature Summary and Revision History

Summary Data

Table 1. Summary Data
Applicable Products or Functional Area 5G-PCF
Applicable Platform(s) SMI
Feature Default Setting Enabled – Always-On
Related Changes in this Release Not Applicable
Related Documentation Not Applicable

Revision History

Table 2. Revision History
Revision Details Release
First Introduced. Pre 2020.01.0

Feature Description

You can enable the Diameter endpoint to dynamically create pods on a designated node or host. This feature might be a requirement when you want to ensure that the nodes are meeting specific security and regulatory parameters, or the node is closer to the datacenter in terms of geographical proximity. The node affinity determines the node where PCF created the Diameter endpoint pods, which are based on the affinity towards a node or group of nodes. Node affinity is a set of rules that allows you to define the custom labels on nodes and specify the label selectors within the pods. Based on these rules, the scheduler determines the location where the pod can be placed.

Note

If you do not specify a node, then the Kubernetes scheduler determines the node where the Diameter endpoint creates a pod.

Configuring the Node for the Diameter Endpoint Pod

This section describes how to specify the node or host where the Diameter endpoint must spawn the pod.

To specify the node where you want Diameter endpoint to spawn the pod, use the following configuration:

config 
   diameter group diameter_group_name 
   mode server server_name 
   stack stack_name 
     application application_name 
     bind-ip host_address 
     fqdn fqdn_address 
     realm realm_address 
     node-host node_host_address 
     end

NOTES:

  • diameter group diameter_group_name – Specifies the Diameter group name.

  • mode server server_name – Specifies the server name that operates as the mode server.

  • stack stack_name – Specifies the stack name.

  • application application_name – Specifies the application name.

  • bind-ip host_address – Specifies the host address of the binding database.

  • fqdn fqdn_address – Specifies the FQDN address.

  • realm realm_address – Specifies the realm address.

  • node-host node_host_address – Specifies the host IP address of the node.

Sample Configuration

The following is a sample configuration of the node configuration.

mode server 
  stack cicdsite 
  application rx 
  bind-ip 192.0.2.18 
  realm cisco.com 
  node-host for-node-2a-worker39e1587354h 
  exit