Page History

This page describes how to create the initial, basic configuration on a signaling SBC (S-SBC) SWe Cloud cluster using the EMS and the SBC Configuration Manager. One SBC node within the cluster, referred to as the "Head End" node, is used for creating the configuration, and the EMS is used for distributing the configuration across the cluster. For more information on how an SBC cluster interacts with the EMS for configuration, refer to Configuring an SBC SWe Cluster using the EMS.

Prior to following these procedures you must have created an SBC SWe cluster in the EMS for the S-SBC cluster. Refer to Creating an SBC SWe Cluster in EMS documentation. You must then instantiate the S-SBC cluster. After instantiation, the SBC nodes register with the EMS, but since there is no configuration yet for the cluster, its nodes start with a blank configuration. 

Accessing the SBC Configuration Manager

Begin the process to initially configure a new S-SBC cluster by accessing the SBC Configuration Manager on behalf of the cluster.

1. Log on to the EMS as an admin user.

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

1. .

   Caption
   0 Figure 1 Cluster

1. Management / Manage VNFs window

   Image Modified

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

2. Click the Configurations tab. 

1. Caption
   0 Figure 1

1. Cluster Configurations Tab

   Image Modified

1. Ensure the option selected for Create Candidate Configuration From is Head End. This is the default. A Head End node must be active, online, and registered with the EMS.

2. Click Create.

1. The SBC Configuration Manager opens against the Head End node.  

   Caption
   0 Figure 1

1. SBC Configuration Manager Window

   Image Modified

Configure the SBC using the SBC Configuration Manager

Use the following procedures and examples to configure basic S-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

1. groupa and

1. IP

1. interfaces, see Creating

1. IP Interface

1. Groups and

1. IP

1. Interfaces.

2. To create a static route, see

1. Create a Static Route.
2. To create a DNS group and a DNS server, see

1. Create a DNS Group and a DNS Server.
2. To create a NTP server, see

1. Create an NTP Server.
2. To create the D-SBC

1. signaling port, see

1. Create the D-SBC

1. Signaling Port.
2. To create a cluster type, see

1. Create a Policer Cluster Type.
2. To create

1. zones, see

1. Create Zones.
2. To create SIP

1. signaling ports, see

1. Create SIP

1. Signaling Ports.
2. To create SIP trunk

1. groups, see

1. Create SIP Trunk

1. Groups.
2. 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 during instantiation, review the meta variable table,

click All > System > Meta Variables.

 The Meta Variable window opens showing the Meta Variable

list.

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 Address Context > IP Interface Group. The IP Interface Group

1. List window opens.

2. Select AC2 from the Address Context drop-down

1. list.

2. Click New IP Interface Group.

1. The Create New IP Interface

1. Group window opens.

2. Enter an IP interface group name.

3. Click Save.

   Caption
   0 Figure 1 IP Interface Group 3 IP Interface Group
   Image Modified

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

Create

IP

Interfaces

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

1. The IP Interface window opens.

2. Select

1. AC2 from the Address Context drop-down

1. list.
2. Select an interface group created from the IP Interface Group drop-down

1. list. For example, SLIG1.
2. Click

1. New IP Interface.

1. The Create New IP

1. Interface section opens.
2. Enter a name for the interface. For example, SLIF1.
3. Enter IP Meta

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

1. Select the Mode as In Service.

1. Select the State as Enabled.
2. Enter the CE Name.

1. Select the pkt0 port from the Port Name drop-down menu.

2. Click Save.

   Caption
   0 Figure 1 Creating an IP Interface
   Image Modified

Repeat

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

1. window opens.
2. Select the AC2 Address Context from

1. the drop-down

1. list.
2. Click 

1. New Static Route. The Create New Static Route

1. window opens.
2. Enter the Destination IP Address (IPv4/IPv6).
3. Enter the Prefix value.
4. Enter the Next Hop IP

1. address (IPv4/IPv6).
2. Select

1. an IP Interface Group Name from the drop-down

1. list.
2. Select

1. an IP Interface Name from the drop-down

1. list.
2. Enter

1. a Preference value.

2. Click Save.
    

   Caption
   0 Figure 1

1. Static Route Window 3 Static Route

   Image Modified

Anchor
step2 step2

Create a DNS Group and a DNS Server

Create a DNS Group

1. Select Address Context > DNS Group.

1. The DNS Group window opens.
   
2. Select AC2 from the Address Context drop-down

1. list.
   
2. Click 

1. New DNS Group.

1. The Create New DNS

1. Group section opens.
   
2. Enter a DNS group name.
   
3. Select IP from the Type drop-down

1. list.
   
2. Select SLIG1 from the IP Interface drop-down

1. list.
   
2. Select Use Configured Dns

1. Server and Edns Support as Enabled.
   

2. Click Save.
   

   Caption
   0 Figure 1

1. Create New DNS Group

   Image Modified

Create a DNS Server

1. Select Address Context > DNS Group > Server.

1. The Server window opens. 

2. On the Server window, perform the following:

   1. Select AC2

1. 1. from the Address Context drop-down

1. 1. list.

   2. Select

1. 1. the DNS group you created from the DNS Group

1. 1. drop-down

1. 1. list. 
      

1. 1. Click New Server.

1. 1. The Create New Server

1. 1. section opens.

   2. In the Create New Server section, perform the following:

      1. Enter a

1. 1. 1. server name.

1. 1. 1. Select the State as Enabled.
         

      2. Enter the DNS server IP in the

1. 1. 1. IP Address V4 or V6

1. 1. 1. field.

1. 1. 1. Click Save.

Anchor
step3 step3

Create

an NTP Server

1. Select System > NTP > Server Admin.

1. The Server Admin window opens.

1. Click New Server Admin.

1. The Create New Server Admin

1. section opens.
2. Enter a server IP address.

1. Select the State

1. as Enabled.

1. Select the Version

1. as Version4.

1. Click Save.

   Caption
   0 Figure 1 NTP Server Admin
   Image Modified

2. Select System > NTP > Time Zone.

1. The Time Zone window opens.

2. Select the instance from the list.

1. The Edit Selected Time

1. Zone section opens.

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

1. list.

2. Click Save.

Anchor
step4 step4

Create the D-SBC Signaling Port

To create a D-SBC signaling port for SLIG2:

1. Select System > Dsbc > Dsbc Sig Port.

1. The Dsbc Sig Port

1. window opens.
2. Select SLIG1 from the IP Interface Group drop-down

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

1. list.
2. Click Save.

Anchor
step5 step5

Create a Policer Cluster Type

1. Select System > Dsbc > Cluster > Type.

1. The Type window opens.

2. Click

1. New Type. The Create New Type section displays.

2. Select the Name as Policer.
3. Select State as Enabled.

4. Enter the cluster FQDN.

1. Info
   title Note:
   The floating IP address of packet interfaces is added as a record in DNS server.

2. Select the name of the DNS group you created in the DNS Group drop-down

1. list.
2. Click Save.

Anchor
step6 step6

Create

Zones

1. Select Address

1. Context > Zone. The Zone

1. window opens.

2. Select AC2 from the Address Context drop-down

1. list.

2. Click 

1. New Zone.

1. The Create New

1. Zone section

1. opens.

2. Enter a Name

1. for the zone, for example, INTERNAL.
2. Enter

1. an ID for the zone.

2. Click Save.

   Caption
   0 Figure 1

1. Create New Zone

   Image Modified

Repeat the previous steps

to create another zone

, for example, EXTERNAL. The new zones are listed.

SIP Signaling

Ports

Create SIP signaling ports for the zones you created:

1. Select Address Context > Zone > SIP Sig Port. The SIP

1. Sig Port window opens.
2. Select AC2 from the Address Context drop-down

1. list.
2. Select

1. the INTERNAL zone from the Zone drop-down

1. list.
2. Click

1. New SIP Sig Port. The Create New SIP Sig Port section

1. opens.
2. Enter an Index number.
3. Set the State as Enabled.
4. Select SLIG1 from the IP Interface Group Name drop-down

1. list.
2. Select the sip-udp option in the Transport Protocols Allowed.

3. Click Save.

   Caption
   0 Figure 1

1. Create New SIP

1. Sig Port 3 SIP SigPort

   Image Modified

Repeat the previous steps

to create

a SIP signaling port for the EXTERNAL zone. The new SIP signaling ports are listed.

SIP Trunk

Groups

Create SIP trunk groups in the the zones you created:

1. Select Address Context > Zone > SIP Trunk Group.

1. The SIP Trunk Group

1. window opens.
2. Select AC2 from the Address Context drop-down

1. list.
2. Select a INTERNAL zone from the Zone drop-down

1. list.
2. Click

1. New SIP Trunk Group.

1. The Create New SIP Trunk

1. Group section opens.
2. Enter

1. a Name for the trunk group, for example, INGRESS_TG.
2. Set the State as Enabled.
3. Set the Mode as In Service.

4. Click Save.

   Caption
   0 Figure 1 Creating a SIP Trunk Group
   Image Modified

Repeat the previous steps

to create another SIP trunk group for the EXTERNAL zone. The new SIP trunk groups are listed.

IP Prefixes

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

1. Select Address Context > Zone > SIP Trunk Group > Ingress IP Prefix.

1. The Ingress IP Prefix

1. window opens.
2. Select AC2 from the Address Context drop-down menu.
3. Select

1. the INTERNAL zone from the Zone drop-down menu.
2. Select the INGRESS_TG trunk group from the SIP Trunk Group drop-down

1. list.
2. Click 

1. New Ingress IP Prefix. 

1. The Create New Ingress IP

1. Prefix section opens.
2. Enter

1. an IP address in IP Address V4 or V6.
2. Enter the Prefix Length.

3. Click Save.

   Caption
   0 Figure 1

1. Create New Ingress IP Prefix

   Image Modified

Repeat the previous steps

to create an IP Prefix for

the EXTERNAL zone and EGRESS_TG trunk group. The new IP

prefixes are listed.

1. The Media window opens.
2. Select AC2 from the Address Context drop-down

1. list.
2. Select

1. the INTERNAL zone from the Zone drop-down

1. list.
2. Select the INGRESS_TG trunk group from the SIP Trunk Group drop-down

1. list.
2. Select MLIG1 from the Media IP Interface Group Name drop-down

1. list.
2. Click Save. 

Repeat steps 3 through 6 to configure media for the EGRESS_TG trunk group

in the EXTERNAL zone

using Media IP Interface Group MLIG2.

Anchor
step11 step11

Configuring the Remote Policy Server

Configure the settings for the remote PSX server:

Disable the Local Policy Server

1. Select System > Policy Server > Local Server. The Local Server

1. window opens.

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

1. opens.

2. Set the State as Disabled.

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

4. Click Save. 

Create a New Remote Policy Server

1. Select System > Policy Server > Remote Server.

1. The Remote Server window opens. 

2. Click

1. New Remote Server.

1. The Create New Remote

1. Server section opens.

2. Enter

1. a server Name. 

2. Enter the server IP Address.

1. Set the State as Enabled. 

2. Select Active from the Mode drop-down

1. list.

2. Click Save.

   Caption
   0 Figure 1

1. Create New Remote

1. Server

   Image Added

Saving and Activating the Configuration in the Cluster

Once you have completed making configuration changes:

1. Click Save at the top of the SBC Configuration Manager window. A Save confirmation window opens. 

   Caption
   0 Figure 1 SBC Configuration Manager - Save Window
   Image Added

2. Click one of the following to save the configuration and return to the EMS:  
   1. Save and Activate configuration.
      This copies the configuration from the Head End SBC back to the EMS as the active configuration. This also sets the Head End SBC configuration status as Config-in-sync and all other non-Head End SBCs as Config-out-of-sync. Their configurations will sync once the non-Head End SBC nodes reboot.
   2. Save configuration.
      This saves the configuration but does not activate the configuration. If you select this option you must activate the configuration manually.
3. If you activated the configuration, skip this step. If you did not, to activate the configuration, on the Cluster Management / Manage VNFs window: 
   1. Make sure the correct cluster is selected.
   2. On the Configurations tab, click Activate Configurations.
4. Click the Nodes tab.
5. Click Reboot Node to reboot the non-Head End SBC nodes and synchronize the configurations for the nodes in the cluster.

Within the Cluster Management / Manage VNFs window, the Cluster Status column for the cluster displays All nodes online and Activation Complete, once the configuration is successfully activated.