M-SBC Cluster Configuration using SBC Configuration Manager

This section describes how to create initial, basic configuration on a media SBC (M-SBC) SWe N:1 HA cluster using the SBC Configuration Manager GUI. Although the following procedures use the GUI, you can also make cluster configuration changes using the CLI on the OAM node. Refer to Modifying SBC Cluster Configuration for information on using the CLI and the CLI Reference Guide for information on the available commands.

The configuration shown here is a basic example and focuses on minimum network configuration and configuration required by cloud-based clusters. As part of a distributed SBC cloud deployment, an M-SBC cluster must be paired with a signaling (S-SBC) cluster to provide full SBC functionality. Both cluster configurations include a D-SBC signaling port to allow communication between the two clusters. An M-SBC cluster also requires load balancing configuration to enable distributing media-related requests among the nodes in the cluster. 

In contrast to assigning static values, cloud deployments use metavariables to assign interface values such as IP addresses. The actual values are determined dynamically during instantiation, based on the cloud environment. 

Beyond this minimal configuration, a full deployment would require further configuration and customization based on the intended use and environment, similar to other types of SBC deployments.

Prerequisites

• The M-SBC cluster configuration must be created in the Insight EMS and configured with a Configuration Type of OAM. Refer to Creating an SBC SWe Cluster (EMS document) and SBC SWe Configuration Management Using OAM Nodes.
• The M-SBC cluster, including its OAM nodes, must be instantiated using either VNFM or the Heat template method of deployment. Refer to Instantiating SBC SWe Using a Heat Template or Instantiating SBC SWe on OpenStack using VNFM.  

Accessing the SBC Configuration Manager

Begin the process to initially configure a new M-SBC cluster by accessing the SBC Configuration Manager for the cluster.

1. Log on to the EMS.

2. Click Network > Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters created on the EMS.

   

3. Click the radio button adjacent to the name of the M-SBC cluster you want to configure. The Details tab for the selected cluster opens. 

4. Click the Configurations tab. 

   

   
   

5. Click Edit Configuration. The SBC Configuration Manager opens in a separate window against the cluster's active OAM node. See the EMA User Guide for information on using the GUI to configure the SBC.

   

Configure the SBC using the SBC Configuration Manager

Use the following procedures and examples to configure basic M-SBC parameters using the SBC Configuration Manager.

1. To validate the meta variable table, see Validating the Meta Variable Table.
2. To create an address context, see Create an Address Context.

3. To create IP interface groups and IP interfaces, see Create IP Interface Groups and IP Interfaces.

4. To create a static route, see Create a Static Route.
5. To create the D-SBC signaling port, see Create the D-SBC Signaling Port.
6. To create a DNS group and a DNS server, see Create a DNS Group and a DNS Server.
7. To create an NTP server, see Create an NTP Server.

8. To create a load balancing service, see Create a Load Balancing Service.
   
   

Validating the Meta Variable Table

To validate the values assigned to metavariables during instantiation, review the Meta Variable table by clicking All > System > Meta Variables. The Meta Variable window opens showing the Meta Variable list. In cloud deployments, metavariables are used to assign interface values, such as IP addresses, whose values are configured dynamically during instantiation.

Create an Address Context

Some of the following procedures require that you specify an address context in which to create configuration objects. The following procedures use an example address context named AC1 as a placeholder. In actual practice you can specify your own address context name or use the default address context. The following steps create an address context named AC1. 

1. Click Configuration > System Provisioning > Category: Base Provisioning > Address Context. The Address Context window opens.
2. Click New Address Context. The Create New Address Context window opens.
3. Enter AC1 as the name of the address context (the name must be between 1-23 characters in length). 
4. Click Save.

Create IP Interface Groups and IP Interfaces

Create IP Interface Groups

1. Select Address Context > IP Interface Group. The IP Interface Group window opens.

2. Select AC1 from the Address Context drop-down menu.

3. Click New IP Interface Group. The Create New IP Interface Group window opens.

4. Enter an IP interface group name. Example: MLIG1
   

5. Click Save.

   

   Repeat the previous steps to create another interface group. Example: MLIG2. The two new interface groups are listed.

   

Create IP Interfaces for each Pkt Port

1. On the navigation pane, click Address Context > IP Interface Group > IP Interface. The IP Interface window opens. 

2. Select AC1 from the Address Context drop-down list.
3. Select an interface group from the IP Interface Group drop-down list. For example, MLIG1.
4. Click New IP Interface. The Create New IP Interface section opens.
5. Enter a name for the interface. For example, MLIF1.
6. Enter IP Meta variable keys in the IP Var V4, Prefix Var V4, IP Public Var V4, IP Var V6, IP Prefix Var V6, IP Public Var V6, and IP VLAN Tag Var fields.
7. Select the Mode as In Service.
8. Select the State as Enabled.
9. Enter the CE Name.
10. Select the pkt0 port from the Port Name drop-down list.

11. Click Save.
    

    

Repeat the previous steps to add an interface MLIF2 for the pkt1 port in a different Interface Group MLIG2.  The two interfaces are listed.

Create a Static Route

1. Select Configuration > System Provisioning > Static Route. The Static Route window opens.
2. Select the AC1 Address Context from the drop-down list.
3. Click New Static Route. The Create New Static Route window opens.
4. Enter the Destination IP Address (IPv4/IPv6).
5. Enter the Prefix value.
6. Enter the Next Hop IP address (IPv4/IPv6).
7. Select an IP Interface Group Name from the drop-down list.
8. Select an IP Interface Name from the drop-down menu.
9. Enter a Preference value.
10. Click Save. 

Create the D-SBC Signaling Port

Create a D-SBC signaling port for communication with the S-SBC cluster in the deployment:

1. Select System > Dsbc > Dsbc Sig Port. The Dsbc Sig Port window opens.
2. Select MLIG2 from the IP Interface Group drop-down list.
3. Select AC1 from the Address Context drop-down list.
4. Click Save.

Create a DNS Group and a DNS Server

Create a DNS Group

1. Select Address Context > DNS Group. The DNS Group window opens.
   
2. Select AC1 from the Address Context drop-down list.
   
3. Click New DNS Group. The Create New DNS Group section opens.
   
4. Enter a DNS group name.
   
5. Select IP from the Type drop-down list.
   
6. Select MLIG2 from the IP Interface drop-down list.
   
7. Select Use Configured Dns Server and Edns Support as Enabled.
8. Click Save.

Create a DNS Server

1. Select Address Context > DNS Group > Server. The Server window opens. 

2. On the Server window, perform the following:

   1. Select AC1 from the Address Context drop-down list.

   2. Select the DNS group you created from the DNS Group drop-down list. 
      

   3. Click New Server. The Create New Server section opens.

   4. In the Create New Server section:

      1. Enter a server name.

      2. Select the State as Enabled.
         

      3. Enter the DNS server IP in the IP Address V4 or V6 field.

      4. Click Save.

         

Create an NTP Server

1. Select System > NTP > Server Admin. The Server Admin window opens.

2. Click New Server Admin. The Create New Server Admin section opens.
3. Enter a server IP address.
4. Select the State as Enabled.
5. Select the Version as Version4.

6. Click Save.

   

7. Select System > NTP > Time Zone. The Time Zone window opens.

8. Select the instance from the list. The Edit Selected Time Zone section opens.

9. Select an appropriate time zone from the Zone drop-down list.

10. Click Save.

    

Create a Load Balancing Service

The M-SBC Load Balancing Service is responsible for distributing media requests among the M-SBC nodes (and T-SBC nodes, if present) in the cluster.

Configure Intra-Cluster Communication Parameters

You must define IP interface group parameters to use for communication among the nodes in the cluster. The following procedure configures this using the default type: Mgmt, which then uses the management interface. Refer to Cluster Admin - Cluster Comm for information on using a packet interface (IP type) instead. If you choose to use a packet interface, refer to Configuring Intra-Cluster VNFC Communication Using Packet Ports for additional configuration that must be performed to define a media port range that avoids a conflict with the default port (3057) used for intra-cluster communication.

1. Select System > Cluster Admin > Cluster Comm. The Cluster Comm window opens.

   

2. In Mgmt Interface Group, select the name of the management IP interface group to use for intra-cluster communication. 
3. In Mgmt IP Var, enter the configuration metavariable representing the IP address to use for intra-cluster communication.
4. Click Save.

Configure Load Balancing Service Parameters

1. Select System > Load Balancing Service. The Load Balancing Service window opens.

   

2. In Group Name, enter a domain name (FQDN)  for the Load Balancing Service group. 

3. Enter the Private IP Interface Group Name to use to communicate with the M-SBC nodes.

4. Click Save.

   Note:

   The Management fixed IP address should be added as an A record on the DNS server. The DNS server must be configured to resolve the Load Balancing Service FQDN to the IP addresses for the M-SBC nodes in the cluster.

Saving and Activating the Configuration in the Cluster

Once you have completed making configuration changes, click Apply Saved Changes and Close at the top-right of the SBC Configuration Manager window. When prompted, confirm that you want to save and activate your configuration changes. The SBC Configuration Manager window closes. The OAM node notifies the SBC nodes in the cluster of the configuration changes and stores a record of the updated configuration back to the EMS.