Configuring Intra-Cluster VNFC Communication Using Packet Ports

As an alternative to using the default management interface, the SBC supports using an IP address (IPv4 or IPv6) from a packet interface (pkt0 or pkt1) for intra-cluster Virtual Network Function Component (VNFC) communication in distributed SBC (D-SBC) deployments. 

The SBC uses UDP port number 3057 for intra-cluster VNFC communication. Therefore, when using a packet interface, you must set the parameter baseUdpPort to a value higher than 3057 to avoid a conflict.

Setting the Base UDP Port Value

To set the value of the parameter baseUdpPort to more than 3057, execute the following command:

set system media mediaPortRange baseUdpPort 3060
commit

Configuring the Intra-cluster VNFC Interface

To use a packet interface for intra-cluster VNFC communication, set the parameter type to ip, and specify a packet interface IP Interface Group and metavariable, as in the following examples:

IPv6 address:

set system clusterAdmin clusterComm type ip addressContext default ipInterfaceGroup LIG2 pktIpVar IF3.IPV6  
commit

IPv4 address:

set system clusterAdmin clusterComm type ip addressContext default ipInterfaceGroup LIG2 pktIpVar IF3.IPV4  
commit

To use a management interface for intra-cluster VNFC communication, set the parameter type to mgmt, and specify a management interface IP Interface Group and metavariable, as in the following examples:

IPv6 address:

set system clusterAdmin clusterComm type mgmt addressContext default ipInterfaceGroup LIG2 mgmtIpVar IF0.IPV6  
commit

IPv4 address:

set system clusterAdmin clusterComm type mgmt addressContext default ipInterfaceGroup LIG2 mgmtIpVar IF0.IPV4  
commit

Refer to D-SBC Signaling Port - CLI, Load Balancing Service - CLI, and DNS Group - CLI for more information.