Modified: for 6.2.1

 

 

Note
  • Download the required heat template and the environment file from Customer Portal. Edit the template with the required SBC instance information using the instructions included in the heat template.
  • EMS identifies the nodes based on the VNFC-ID. While instantiating SBC/PSX cloud nodes, ensure that you use a unique VNFC-ID only. If you reuse an existing VNFC-ID, EMS will treat this as a re-registration request and overwrite the existing data on the cloud node.

Note

If a switchover is triggered on the SBC SWe platform due to any of the following reasons, a media outage of 20 seconds occurs for the stable calls:

  • if there is process hang in the media handling application,
  • if media handling process is manually killed or because of the core dump.

The parameter mgmtMode is used for managing the HA/Redundancy of SBC SWe Cloud NFV.

  • centralized (default) - Use this mode for traditional HA/redundancy model (1:1 scenario) where one active instance is backed up by one standby instance. In Centralized mode, the SBC configuration is synchronized between active and standby SBCs. The Centralized mode is preferred for deployments where the scale/sessions requirements are low.
  • distributed - Use this mode for SBC SWe Cloud deployments where up to N active SBC instances are backed up by a single standby SBC instance (N:1). In this mode, each node is configured separately, and the configuration on active and standby instances are not synchronized. The instances in such deployments also have homogeneous configuration. The microservices based Distributed-SBC deployment is ideal for Communications Service Providers (CSPs) with large scale/sessions requirements. The Distributed mode is preferred in such deployments, as the lifecycle of the instances (instance spin-off, initial configuration,  delta configuration, and instance termination) are managed by EMS/VNFM and Configurator.

To instantiate I-SBC HA in centralized mode using 1:1 heat template:

  1. Log on to the OpenStack.

  2. On the navigation pane, click Project > Orchestration > Stacks. The Stacks window is displayed.

    Stacks Page

  3. Click Launch Stack to view the Select Template screen.

  4. From the Select Template dialog, do the following:
    1. From the Template Source drop-down list, select File.

    2. Under Template File, click Browse.

    3. Select the .yaml file saved on the computer.

    4. Click Next.

      Select Template

      The Launch Stack dialog box displays.

      Enter the required values for the fields.

      Note

      The SBC Cloud 1:1 in centralized mode is not supported with EMS download config option as True. For this mode, you can install SBC Cloud 1:1 in non-centralized mode and download the configuration using Configurator/EMS.

      Launch Stack


      The following table describes the Launch Stack fields:

      Launch Stack Fields

      FieldDescriptionExample or Recommendation
      Stack Name *A unique name of the stack to create.I-SBC
      Creation Timeout (minutes)*
      		Time in minutes for stack creation time-out. Default value is 60 minutes.60
      Rollback on FailureThis enables the rollback on create/update failure. 
      Password for user*This is required for operations to be performed throughout the life cycle of the stack.admin
      Image Name *The image to be used to launch the Integrated SBC instance.SBCSWe6.2.1R000
      Flavor*The flavor to be used to launch the instance. For more information, refer to For OpenStack.SBC
      Security Group*Name of the security group associated with the instance. For more information, refer to Understanding Security Group Rules.sonus-sg
      SBC System Name

      The SBC system name or Redundancy Group name. For more information, refer to System and Instance Name Convention.
      Note: Ensure that the System Name you mention, while instantiating a new SBC instance is unique. In case, a new SBC instance is created with the same name as that of an already existing SBC with a different IP then the new SBC's registration request is rejected.

      		ISBC
      SBC Personality Type

      Configure a SBC instance to either Integrated SBC (ssbc), Signaling SBC (isbc), or Media SBC (msbc) personality types.

      Default value is isbc.

      		isbc
      SBC active instance name.vsbc1
      SBC (Assigned) Standby Instance NameSBC standby instance name.vsbc2
      *Name of the management port public network.provider-mgmt
      *Name of packet port 0 public network. In case of port redundancy, the pkt0S uses the same network.provider-pkt0
      Packet Port 1 Public Network Name or ID*Name of packet port 1 private network. In case of port redundancy, the pkt1S uses the same network.provider-pkt1
      Number of public IPs on mgmt0.0
      Number of Logical IPs on mgt0Number of logical IPs on mgmt0.0
      Number of Floating IPs on pkt0Number of public IPs on pkt0.0
      Number of Floating IPs on pkt1Number of public IPs on pkt1.0
      Reverse NAT on pkt0Enable/disable reverse NAT on pkt0.False
      Reverse NAT on pkt1Enable/disable reverse NAT on pkt1.False
      Management Port Provider Network Name or ID*Name of the management port private network.provider-mgmt
      HA Port Private Network Name or ID*Name of the HA port private network.ha-net
      Packet Port 0 Provider Network Name or ID*Name of packet port 0 private network. In case of port redundancy, the pkt1S uses the same network.
      		provider-pkt0
      Packet Port 1 Provider Network Name or ID*Name of packet port 1 private network. In case of port redundancy, the pkt0S uses the same network.provider-pkt1
      Name or ID of the private subnet for mgt0.mgmt-subnet
      HA Port Private Subnet Name or ID*Name or ID of the private subnet for ha0.ha-subnet
      Packet Port 0 Private Subnet Name or ID*Name or ID of the private subnet for pkt0.PKT0-subnet
      * Name or ID of the private subnet for pkt1.PKT1-subnet
      Is DHCP enabled on Mgt0 Subnet?If DHCP is enabled on this port, set as TRUE. If DHCP is disabled in this port, set as False.False
      Management Port Gateway IPGateway IP address for management port.10.x.x.1
      Management Port Subnet PrefixSubnet prefix for Management port.23
      Is DHCP enabled on Hat0 Subnet?If DHCP is enabled on this port, set as TRUE. If DHCP is disabled in this port, set as False.False
      High Availability Port Gateway IPGateway IP address for HA port.10.y.y.1
      High Availability Port Subnet PrefixSubnet prefix for HA port.24
      Is DHCP enabled on Pkt0 Subnet?If DHCP is enabled on this port, set as TRUE. If DHCP is disabled in this port, set as False.False
      Packet Port 0 Gateway IPGateway IP address for Packet 0 port.10.z.z.1
      Packet Port 0 Subnet PrefixSubnet prefix for Packet 0 port.23
      Packet Port 0 VLAN IDVLAN ID for Packet 0 port.None
      Is DHCP enabled on Pkt1 Subnet?If DHCP is enabled on this port, set as TRUE. If DHCP is disabled in this port, set as False.False
      Packet Port 1 Gateway IPGateway IP address for Packet 1 port.10.a.a.1
      Packet Port 1 Subnet Prefix Subnet prefix for Packet 1 port.23
      Packet Port 1 VLAN ID VLAN ID for Packet 1 port.None
      Management Port IP Address (Active Instance)
      		The Management Port IP address of Active instance.10.x.x.10
      High Availability Port IP Address (Active Instance)
      		The HA Port IP address of Active instance.10.y.y.10
      The Packet 0 Port IP address of Active instance.10.z.z.10
       The Packet 1 Port IP address of Active instance.10.a.a.10
      Management Port IP Address (Standby Instance)The Management Port IP address of standby instance.10.x.x.11
      High Availability Port IP Address (Standby Instance)The HA Port IP address of standby instance.10.y.y.11
      Packet Port 0 IP Address (Standby Instance)The Packet 0 Port IP address of standby instance.10.z.z.11
      Packet Port 1 IP Address (Standby Instance)The Packet 1 Port IP address of Active instance.10.a.a.11
      Logical IP for Management PortLogical IP address to be assigned on Management Port.10.x.x.12
      Virtual IP for Packet Port 0Virtual IP address to be assigned on packet Port 0.10.z.z.12
      Virtual IP for Packet Port 1Virtual IP address to be assigned on packet Port 1.10.a.a.12
      EMS User NameEMS user name to communicate with the APIs.restuser
      EMS PasswordEMS user password which is required to perform operations throughout the life cycle of the stack.sonus123
      EMS IP

      The standalone EMS IP address to manage SBC instances. For Geographical Redundancy (GR) EMS deployment, this IP address denotes as EMS source IP address.

      For Example:

      For IPv6,

      • Standalone EMS IP address as fd00:10:6b50:4060::8e
      • Geographical Redundancy EMS IP address as fd00:10:6b50:4060::8e and fd00:10:6b50:4060::8f

      For IPv4,

      • Standalone EMS IP address as 10.54.68.185
      • Geographical Redundancy EMS IP address as 10.54.68.185 and 10.54.68.186
      		10.54.58.178 or fd00:10:6b50:4060::8e
      Cluster IDThe cluster ID of Integrated SBC (I-SBC) cluster.I-SBC-centralized
      Download Configuration from EMS

      Enable configuration download from EMS.

      NOTE: This flag should be enabled only when the instance needs to download the configuration from EMS.

      		False
      Download Configuration file name

      Name of the configuration file name.

      NOTE: If you did not provide the configuration file name, the default configuration file name is used.

      		None

      Note

      If the SBC SWe is not integrated with EMS, the corresponding EMS fields must be set to "None".

  5. Click Launch. The new stack is listed in the Stacks table.

    Launch Stack

  6. On the navigation pane, click Project > Compute > Instances to view both the active and standby instances.

    Instances Screen

  7. Perform the following to view the active and standby I-SBC instances registered in the EMS:
    1. Log on to EMS.
    2. In Network Management, click Cluster / VNF Management. The Cluster/VNF Management window displays.
    3. Click View Cluster/VNF Node Status tab.

    4. Navigate through the list to view the active and standby I-SBC instances.

      I-SBC Registration in EMS