Versions Compared

Old Version 11

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7e1be77a0005, userName='null'}
REV1

 

UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef40ce0, userName='null'}



Panel

In this section:

Table of Contents
maxLevel4



Info
iconfalse

Related articles:


This section describes how to create initial, basic configuration on a signaling SBC (S-SBC) SWe Cloud 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 configuration required for a basic call flow and configuration required by cloud-based clusters. As part of a distributed SBC cloud deployment, an S-SBC cluster must be paired with a media (M-SBC) cluster to provide full SBC functionality. Both cluster configurations include a D-SBC signaling port to allow communication between the two clusters. 

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.

Info
titleNote:

Prior releases supported the use of a dedicated SBC Configurator cluster to configure other SBC SWe clusters. This approach is replaced by using one of the SBC nodes within the cluster, referred to as the "Headend" SBC, to configure the other nodes. While the SBC Configurator currently remains supported for backward compatibility, it will be deprecated in a subsequent release. Beginning with release 7.1, use the Headend SBC configuration model described in this topic.

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 "Headend" 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 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 registered with the EMS.

    Caption
    0Figure
    1Cluster Management / Manage VNFs window
    Image Modified


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

  4. Click the Configurations tab. 

    Caption
    0Figure
    1Cluster Configurations Tab

    Image Modified

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


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

    Caption
    0Figure
    1SBC 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 groupa 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 the D-SBC signaling port, see Create the D-SBC Signaling Port.
  8. To create a cluster type, see Create a Policer Cluster Type.
  9. To create zones, see Create Zones.
  10. To create SIP signaling ports, see Create SIP Signaling Ports.
  11. To create SIP trunk groups, see Create SIP Trunk Groups.
  12. 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, click All > System > Meta Variables. The Meta Variable table by clicking All > System > Meta Variables. The Meta Variable window opens showing the Meta Variable list. Caption0Figure1In cloud deployments, metavariables are used to assign interface values, such as IP addresses, whose values are configured dynamically during instantiation.

Caption
0Figure
1Meta Variable
3Meta Variable

Image Modified


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

  5. Click Save.

    Caption
    0Figure
    1IP Interface Group
    3IP Interface Group

    Image Modified


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

Caption
0Figure
1New IP Interface Groups

Image Modified

 


Create IP

Interfaces

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 AC2 from the Address Context drop-down list.
  3. Select an interface group created from the IP Interface Group drop-down list. For example, SLIG1.
  4. Click New IP Interface. The Create New IP Interface section opens.
  5. Enter a name for the interface. For example, SLIF1.
  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 menu.

  11. Click Save.

    Caption
    0Figure
    1Creating 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.

Caption
0Figure
1New IP Interfaces

Image Modified

 


Anchor
static_route
static_route
Create a Static Route

  1. Select Configuration > System 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. 

    Caption
    0Figure
    1Static Route Window
    3Static Route

    Image Modified



Anchor
step2
step2
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 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 SLIG1 from the IP Interface drop-down list.
  7. Select Use Configured Dns Server and Edns Support as Enabled.

  8. Click Save.

    Caption
    0Figure
    1Create New DNS Group

    Image Modified


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 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, perform the following:

      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.

 


Caption
0Figure
1DNS Server Window

Image Modified


Anchor
step3
step3
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.

    Caption
    0Figure
    1NTP Server Admin

    Image Modified


  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.


Caption
0Figure
1Time Zone Window

Image Modified


Anchor
step4
step4
Create the D-SBC Signaling Port

To create Create a D-SBC signaling port for SLIG2communication with the M-SBC cluster in the deployment:

  1. Select System > Dsbc > Dsbc Sig Port. The Dsbc Sig Port window opens.
  2. Select SLIG1 from the IP Interface Group drop-down list.
  3. Select AC2 from the Address Context drop-down list.
  4. Click Save.
Info
titleNote:

Make sure when configuring SIP Sig Port and Dsbc Sig Port for an S-SBC deployment that you specify different IP addresses for them. To do so you must select different metavariables for each of them. The actual values of the metavariables are determined during orchestration based on your Heat templatesenvironment.

  


Caption
0Figure
1Dsbc Sig Port Window

Image Modified


Anchor
step5
step5
Create a Policer Cluster Type

  1. Select System > Dsbc > Cluster > Type. The Type window opens.

  2. Click New Type. The Create New Type section displays.

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

  5. Enter the cluster FQDN.

    Info
    titleNote:

    The floating IP address of packet interfaces is added as a record in DNS server.


  6. Select the name of the DNS group you created in the DNS Group drop-down list.
  7. Click Save.


Caption
0Figure
1Creating a Policer Cluster Type

Image Modified


Anchor
step6
step6
Create Zones

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

    Caption
    0Figure
    1Create New Zone

    Image Modified


Repeat the previous steps to create another zone, for example, EXTERNAL. The new zones are listed.

Caption
0Figure
1Zones List
3Zone

Image Modified

 


Anchor
step7
step7
Create SIP Signaling Ports

Create SIP signaling ports for the zones you created:

  1. Select 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 SLIG1 from the IP Interface Group Name drop-down list.
  8. Select the sip-udp option in the Transport Protocols Allowed.

  9. Click Save.

    Caption
    0Figure
    1Create New SIP Sig Port
    3SIP SigPort

    Image Modified


Repeat the previous steps to create a SIP signaling port for the EXTERNAL zone. The new SIP signaling ports are listed.

Caption
0Figure
1SIP Sig Port List

Image Modified

 

 



Anchor
step8
step8
Create SIP Trunk Groups

Create SIP trunk groups in the the zones you created:

  1. Select Address Context > Zone > SIP Trunk Group. The SIP Trunk Group window opens.
  2. Select AC2 from the Address Context drop-down list.
  3. Select a 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 as Enabled.
  7. Set the Mode as In Service.

  8. Click Save.

    Caption
    0Figure
    1Creating 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.

Caption
0Figure
1SIP Trunk Group List

Image Modified

 


Anchor
Step9
Step9
Configure Ingress IP Prefixes

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

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

    Caption
    0Figure
    1Create 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.

Caption
0Figure
1Ingress IP Prefix List

Image Modified

 


Anchor
Step10
Step10
Configure Media Settings

Configure media settings for the SIP trunk groups you created:

  1. Select Address Context > Zone > SIP Trunk Group > Media. The Media window opens.
  2. Select AC2 from the Address Context drop-down list.
  3. Select the INTERNAL zone from the Zone drop-down list.
  4. Select the INGRESS_TG trunk group from the SIP Trunk Group drop-down list.
  5. Select MLIG1 from the Media IP Interface Group Name drop-down list.
  6. Click Save. 


Caption
0Figure
1Media Parameters

Image Modified

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 window opens.

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

  3. Set the State as Disabled.

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

  5. Click Save. 


Caption
0Figure
1Edit Selected Local Server

Image Modified


Create a New Remote Policy Server

  1. Select 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 as Enabled. 

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

  7. Click Save.

    Caption
    0Figure
    1Create New Remote Server

    Image Modified


Saving and Activating the Configuration in the Cluster

Once you have completed making configuration changes:

Click Save

, click Apply Saved Changes and Close at the top-right of the SBC Configuration Manager window.

A Save confirmation window opens. 
Caption
0Figure
1SBC Configuration Manager - Save Window

Image Removed

Click Save and Activate configuration. This copies the configuration from the Headend SBC back to the EMS as the active configuration. This also sets the Headend SBC configuration status as Config-in-sync and all other non-Headend SBCs as Config-out-of-sync. The EMS pushes configuration differences to all of those nodes which are config-out-of-sync unless the nodes are unavailable. 

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.

Info
titleNote:
The EMS performs the reboot of out-of-sync nodes automatically during initial configuration. However, if the nodes lose synchronization after that point, for example if an activation fails, then you must reboot the nodes to trigger a configuration download to bring the nodes back into sync. To reboot a node, use the Reboot Node option on the Nodes tab.

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. 

Pagebreak