You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Note
  • Download the required heat template and the environment file from Salesforce 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.

To instantiate S-SBC HA using 1:1 nested heat template:

  1. Log on to the OpenStack.

  2. On the navigation pane, click Project > Orchestration > Stacks. The Stacks page displays: 

    Stacks Page

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

  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.

    5. Enter the required values for the fields.

      Launch Stack


      The following table describes the Launch Stack fields:

      Launch Stack Fields

      FieldDescriptionExample or Recommendation
      Stack Name *An unique name of the stack to create.SBC-Signaling
      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 Signaling SBC instance.S608
      Flavor*The flavor to be used to launch the instance. For more information see, SBC SWe Requirements.m1.large
      Security Group*Name of the security group associated with the instance. For more information see, Understanding Security Group Rules.vsbc_security_group name
      SBC System Name

      SBC system name or Redundancy Group name. For more information see, 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.

      		SSBC
      SBC Personality Type

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

      Default value is isbc.

      		ssbc
      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.provider-pkt0
      Packet Port 1 Provider Network Name or ID*Name of packet port 1 private network.provider-pkt1
      Mgt0 IP VersionIP version of networkV4 or V6
      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 IP AddressThe Mangement Port IP address of Active and Standby instance must be provided simultaneously separated by commas.10.x.x.10, 10.x.x.11
      Management Port Subnet PrefixSubnet prefix for Management port.23
      Management Port Gateway IPGateway IP address for management port.10.x.x.1
      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
      HA Port IP AddressThe HA Port IP address of Active and Standby instance must be provided simultaneously separated by commas.10.y.y.10, 10.y.y.11
      HA Port Subnet PrefixSubnet prefix for HA port.23
      HA Port Gateway IPGateway IP address for HA port.10.y.y.1
      Pkt0 IP VersionIP version of networkV4 or V6
      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 IP AddressThe Packet 0 Port IP address of Active and Standby instance must be provided simultaneously separated by commas.10.z.z.10, 10.z.z.11
      Packet Port 0 Subnet PrefixSubnet prefix for Packet 0 port.23
      Packet Port 0 Gateway IPGateway IP address for Packet 0 port.10.z.z.1
      Packet Port 0 VLAN ID
      		VLAN ID for Packet 0 port.789
      comma separated list of alternate IPs for pkt0Comma separated list of alternate IPs for pkt010.z.z.13, 10.z.z.14
      Pkt1 IP Version IP version of networkV4 or V6
      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 IP Address The Packet 1 Port IP address of Active and Standby instance must be provided simultaneously separated by commas.10.a.a.10, 10.a.a.11
      Packet Port 1 Subnet Prefix Subnet prefix for Packet 1 port.23
      Packet Port 1 Gateway IP Gateway IP address for Packet 1 port.10.a.a.1
      Packet Port 1 VLAN ID
      		 VLAN ID for Packet 1 port.789
      comma separated list of alternate IPs for pkt1Comma separated list of alternate IPs for pkt1.10.a.a.13, 10.a.a.14
      SBC Instance NameThe unique instance name of active and standby signaling instance must be separated by commas.vSsbc1,vSsbc2
      SBC Configured CE RoleThe role of the instance must be separated by commasACTIVE,STANDBY
      HA port IP address of one of the members of SBC Redundancy Group(RG). (Note - Provide 169.254.88.1 for the first node of RG)The IP Addresses of the SBC Redundancy Group (RG).169.254.88.1,10.y.y.10
      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

      EMS IP address to manage SBC instances.

      NOTE:

      • Provide the EMS IP address in double quotes ("<EMS IP address>").

      • If you are having a EMS GR deployment, you must provide the EMS Source and the EMS Target IP addresses while launching the SBC instance, as shown in the screen.

      Example:

      For IPv6,

      • Standalone EMS IP address as - "aaaa:bbbb:cccc:dddd::xx".
      • Geographical Redundancy EMS IP address as - ["aaaa:bbbb:cccc:dddd::xx","aaaa:bbbb:cccc:dddd::xx"].

      For IPv4,

      • Standalone EMS IP address as - "012.345.678.910".
      • Geographical Redundancy EMS IP address as - ["012.345.678.910","012.345.678.910"].
      		["aaaa:bbbb:cccc:dddd::xx","aaaa:bbbb:cccc:dddd::xx"]
      Cluster IDThe cluster ID returned by the EMS for the SBC Configurator cluster.aaaabbbb
      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.

      		True
      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 the new instances created.

    Instances Page

  7. Perform the following to view the registered instance 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 registered S-SBC instance.

      SSBC Registration in EMS

       

  • No labels