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.

Configuration Example

Meta variable names are used to retrieve the IP addresses for intra-cluster VNFC communication and either packet or management interface variables can be specified as appropriate. For example, on a cloud media-SBC (M-SBC), the IPv6 address of pkt1 is IF3.IPV6, and the IPv4 address of mgt0 is IF0.IPV4. The following examples show use of both packet and management interfaces.

To configure packet interface using IPv6 address for VNFC communication in a Cloud M-SBC cluster:

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

To configure packet interface using IPv4 address for VNFC communication in a Cloud M-SBC cluster:

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

To configure management interface using IPv6 address for VNFC communication in a Cloud M-SBC cluster:

% set system clusterAdmin clusterComm type mgmt mgmtInterfaceGroup mgmtGroup mgmtIpVar IFO.IPV6
commit

To configure management interface using IPv4 address for VNFC communication in a Cloud M-SBC cluster:

% set system clusterAdmin clusterComm type mgmt mgmtInterfaceGroup mgmtGroup mgmtIpVar IFO.IPV4
commit

References

• For further details on CLI changes and configuration examples, refer to Cluster Admin - CLI.
• For configuring this feature, refer to Configuring Intra-Cluster VNFC Communication Using Packet Ports.