Page History

This section describes how to create initial, basic configuration for an integrated SBC (I-SBC) SWe 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 active node on the cluster. 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 configuration required for a basic call flow and configuration required by cloud-based clusters. For example, 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 I-SBC cluster configuration must be created in 

  Spacevars
  0 model3

  and configured with a Configuration Type of Direct Single. Refer to Create SBC Clusters and SBC SWe Configuration Management in Direct Single Mode.
• The I-SBC cluster 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 I-SBC cluster by accessing the SBC Configuration Manager for the cluster.

1. Log on to

   Spacevars
   0 model3

   .

2. Click Network → Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters registered with

   Spacevars
   0 model3

   .
   Figure 1: Cluster Management / Manage VNFs window
   
   

   
   

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

4. Click the Configurations tab. 
   Figure 2: Cluster Configurations Tab

   
   

   
   

5. Click Edit Configuration. The SBC Configuration Manager opens in a separate window against the cluster's active node. For information about using the GUI to configure the SBC, refer to the EMA User Guide.
   Figure 3: SBC Configuration Manager Window

   

Configure the SBC using the SBC Configuration Manager

Use the following procedures and examples to configure basic I-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 group and IP interfaces, see Creating IP Interface Groups and IP Interfaces.

4. To create a static route, see Create a Static Route.
5. To create a DNS group and a DNS server, see Create a DNS Group and a DNS Server.
6. To create a NTP server, see Create an NTP Server.
7. To create zones, see Create Zones.
8. To create SIP signaling ports, see Create SIP Signaling Ports.
9. To create SIP trunk groups, see Create SIP Trunk Groups.
10. To create a remote policy server, see Configuring a Remote Policy Server.

Anchor
meta_variable meta_variable

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.
Figure 4: Meta Variable

Anchor
AddressContext AddressContext

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 AC2 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 AC2. 

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 AC2 as the name of the address context (the name must be between 1-23 characters in length). 
4. Click Save.

Anchor
step1 step1

Create IP Interface Groups and IP Interfaces

Create IP Interface Groups

1. Select All → Address Context → IP Interface Group. The IP Interface Group List window opens.

2. Select AC2 from the Address Context drop-down list.

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

4. Enter an IP interface group name. For example, LIG1.

5. Click Save.
   Figure 5: IP Interface Group

   
   

   
   

Repeat the previous steps to create another interface group. For example: LIG2. 

Create IP Interfaces for each Pkt Port

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

2. Select AC2 from the Address Context drop-down list.
3. Select an interface group created from the IP Interface Group drop-down list. For example, LIG1.
4. Click New IP Interface. The Create New IP Interface section opens.
5. Enter a name for the interface. For example, LIF1.
6. Enter IP Metavariable 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 VLAN Tag Var fields as appropriate.
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 menu.

11. Click Save.
    Figure 6: Creating an IP Interface

    
    

    
    

Repeat the previous steps to add an interface LIF2 for the pkt1 port in a different Interface Group LIG2. 

Anchor
static_route static_route

Create a Static Route

1. Select Configuration → System Provisioning → Category: Base Provisioning → Static Route. The Static Route window opens.
2. Select the AC2 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 list.
9. Enter a Preference value.

10. Click Save.
     Figure 7: Static Route Window

    
    

    
    

    
    

Anchor
step2 step2

Create a DNS Group and a DNS Server

Create a DNS Group

1. Select All → Address Context → DNS Group. The DNS Group window opens.
   
2. Select AC2 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 LIG1 from the IP Interface drop-down list.
   
7. Enable Use Configured Dns Server and Edns Support.
   

8. Click Save.
   Figure 8: Create New DNS Group
   

   
   

   
   

Create a DNS Server

1. Select All → Address Context → DNS Group → Server. The Server window opens. 

2. On the Server window, perform the following:

   1. Select AC2 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. Set the State to Enabled.
         

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

      4. Click Save.

Figure 9: DNS Server Window

Anchor
step3 step3

Create an NTP Server

1. Select All → 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. Set the State to Enabled.
5. Set the Version to Version4.

6. Click Save.
   Figure 10: NTP Server Admin

   
   

   
   

7. Select All → 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.

Figure 11: Time Zone Window

Anchor
step6 step6

Create Zones

1. Select All → Address Context → Zone. The Zonewindow opens.

2. Select AC2 from the Address Context drop-down list.

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

4. Enter a Name for the zone, for example, INTERNAL.
5. Enter an ID for the zone.

6. Click Save.
   Figure 12: Create New Zone

   
   

   
   

Repeat the previous steps to create another zone, for example, EXTERNAL. 

Anchor
step7 step7

Create SIP Signaling Ports

Create SIP signaling ports for the zones you created:

1. Select All → Address Context → Zone → SIP Sig Port. The SIP Sig Port window opens.
2. Select AC2 from the Address Context drop-down list.
3. Select the INTERNAL zone from the Zone drop-down list.
4. Click New SIP Sig Port. The Create New SIP Sig Port section opens.
5. Enter an Index number.
6. Set the State as Enabled.
7. Select LIG1 from the IP Interface Group Name drop-down list.
8. Select the sip-udp option in the Transport Protocols Allowed.

9. Click Save.
   Figure 13: Create New SIP Sig Port

   
   

   
   

Repeat the previous steps to create a SIP signaling port for the EXTERNAL zone. 

Anchor
step8 step8

Create SIP Trunk Groups

Create SIP trunk groups in the the zones you created:

1. Select All → Address Context → Zone → SIP Trunk Group. The SIP Trunk Group window opens.
2. Select AC2 from the Address Context drop-down list.
3. Select the INTERNAL zone from the Zone drop-down list.
4. Click New SIP Trunk Group. The Create New SIP Trunk Group section opens.
5. Enter a Name for the trunk group, for example, INGRESS_TG.
6. Set the State to Enabled.
7. Set the Mode to In Service.
8. Enter LIG1 as the Media IP Interface Group Name.

9. Click Save.
   Figure 14: Creating a SIP Trunk Group

   
   

   
   

Repeat the previous steps to create another SIP trunk group for the EXTERNAL zone and using LIG2. 

Anchor
Step9 Step9

Configure Ingress IP Prefixes

Create ingress IP prefixes for the SIP trunk groups you created:

1. Select All → Address Context → Zone → SIP Trunk Group → Ingress IP Prefix. The Ingress IP Prefix window opens.
2. Select AC2 from the Address Context drop-down menu.
3. Select the INTERNAL zone from the Zone drop-down menu.
4. Select the INGRESS_TG trunk group from the SIP Trunk Group drop-down list.
5. Click New Ingress IP Prefix.  The Create New Ingress IP Prefix section opens.
6. Enter an IP address in IP Address V4 or V6.
7. Enter the Prefix Length.

8. Click Save.
   Figure 15: Create New Ingress IP Prefix

   
   

   
   

Repeat the previous steps to create an IP Prefix for the EXTERNAL zone and EGRESS_TG trunk group.

Anchor
step11 step11

Configuring the Remote Policy Server

Configure the settings for the remote PSX server:

Disable the Local Policy Server

1. Select All → System → Policy Server → Local Server. The Local Server window opens.

2. Select the local server listed. The Edit Selected Local Server section opens.

3. Set the State to Disabled.

4. Select Out of Service from the Mode drop-down menu.

5. Click Save. 

Figure 16: Edit Selected Local Server

Create a New Remote Policy Server

1. Select All → System → Policy Server → Remote Server. The Remote Server window opens. 

2. Click New Remote Server. The Create New Remote Server section opens.

3. Enter a server Name. 

4. Enter the server IP Address.

5. Set the State to Enabled. 

6. Select Active from the Mode drop-down list.

7. Click Save.

Figure 17: Create New Remote Server

 

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 active node replicates the configuration changes to the standby node in the cluster and stores a record of the updated configuration back to

Spacevars
0 model3

.