In this section:
This section describes how to create initial, basic configuration for an integrated SBC (I-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 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.
Begin the process to initially configure a new I-SBC cluster by accessing the SBC Configuration Manager for the cluster.
Click Network > Cluster Management. The Cluster Management / Manage VNFs window opens listing the SBC clusters registered with the EMS.
Click the Configurations tab.
Click Edit Configuration. The SBC Configuration Manager opens in a separate window against the cluster's active node. See the EMA User Guide for information on using the GUI to configure the SBC.
Use the following procedures and examples to configure basic I-SBC parameters using the SBC Configuration Manager.
To create IP interface groupa and IP interfaces, see Creating IP Interface Groups and IP Interfaces.
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.
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.
Select All > Address Context > IP Interface Group. The IP Interface Group List window opens.
Select AC2 from the Address Context drop-down list.
Click New IP Interface Group. The Create New IP Interface Group window opens.
Click Save.
Repeat the previous steps to create another interface group. For example: LIG2.
On the navigation pane, click All > Address Context > IP Interface Group > IP Interface. The IP Interface window opens.
Click Save.
Repeat the previous steps to add an interface LIF2 for the pkt1 port in a different Interface Group LIG2.
Click Save.
Click Save.
Select All > Address Context > DNS Group > Server. The Server window opens.
On the Server window, perform the following:
Select AC2 from the Address Context drop-down list.
Select the DNS group you created from the DNS Group drop-down list.
Click New Server. The Create New Server section opens.
In the Create New Server section:
Enter a server name.
Set the State to Enabled.
Enter the DNS server IP in the IP Address V4 or V6 field.
Click Save.
Select All > System > NTP > Server Admin. The Server Admin window opens.
Click Save.
Select All > System > NTP > Time Zone. The Time Zone window opens.
Select the instance from the list. The Edit Selected Time Zone section opens.
Select an appropriate time zone from the Zone drop-down list.
Click Save.
Select All > Address Context > Zone. The Zone window opens.
Select AC2 from the Address Context drop-down list.
Click New Zone. The Create New Zone section opens.
Click Save.
Repeat the previous steps to create another zone, for example, EXTERNAL.
Create SIP signaling ports for the zones you created:
Click Save.
Repeat the previous steps to create a SIP signaling port for the EXTERNAL zone.
Create SIP trunk groups in the the zones you created:
Click Save.
Repeat the previous steps to create another SIP trunk group for the EXTERNAL zone and using LIG2.
Create ingress IP prefixes for the SIP trunk groups you created:
Click Save.
Repeat the previous steps to create an IP Prefix for the EXTERNAL zone and EGRESS_TG trunk group.
Configure the settings for the remote PSX server:
Select the local server listed. The Edit Selected Local Server section opens.
Set the State to Disabled.
Select Out of Service from the Mode drop-down menu.
Click Save.
Click New Remote Server. The Create New Remote Server section opens.
Enter a server Name.
Enter the server IP Address.
Set the State to Enabled.
Select Active from the Mode drop-down list.
Click Save.
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 the EMS.