Instantiating a Standalone SBC SWe Instance

Instantiate an SBC SWe Standalone Instance

To instantiate an SBC SWe standalone instance, accomplish the following steps:

1. Log on to AWS.

2. Click Services and the AWS Services list displays.

3. Click CloudFormation from Management Tools section.

   All AWS Services

   

   The stacks page displays.
    

4. Click Create Stack.

   The Select Template page displays.
    

5. In the Choose a template section, select Upload a template to Amazon S3.
    
6. Click Choose File to navigate through the folders and select the heat template.
   The heat template selected displays.
    

7. Click Next.

   Select Template Page

   

   The Create A New Stack page displays.
    

8. Enter the required values for the fields. The following table describes the create stack fields:

   Create Stack fields

    

   Field	Description	Mandatory?	Can Be Left Blank?	Customizable by User?
   Stack name	An unique name for SBC stack which is a collection of AWS resources you create and delete as a single unit.
   VpcId	Select a VPC with Subnet, Security Group, etc., selected earlier.
   SecurityGrpMgt0	Acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic for MGT0.
   SecurityGrpHa0	Acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic for HA0.
   SecurityGrpPkt0	Acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic for PKT0.
   SecurityGrpPkt1	Acts as a firewall for associated Amazon EC2 instances, controlling both inbound and outbound traffic for PKT1.
   SubnetIdMgt0	Subnet ID of an existing subnet in your Virtual Private Cloud (VPC) for Mgt0.
   SubnetIdHA0	Subnet ID of an existing subnet in your Virtual Private Cloud (VPC) for HA0.
   SubnetIdPkt0	SubnetId of an existing subnet in your Virtual Private Cloud (VPC) for Pkt0.
   SubnetIdPkt1	SubnetId of an existing subnet in your Virtual Private Cloud (VPC) for Pkt1.
   AMIID	Amazon Machine Image (AMI) is an encrypted machine image which is like a template of a computer's root drive. For example, ami-xxxxxxxx.
   InstanceName	This is the host name for an SBC instance.
   SystemName	This is the name of the overall SBC system, and is used as the designation of all servers. Note: Sonus recommends you to capitalize the system name. For example, VSBCSYSTEM.
   InstanceType	Type of instance that is created from stack. Note: Sonus recommends c4.2xlarge or higher if this instance type is available in your zone. Use c4.2xlarge instance type or higher to handle more calls with transcoding. You can use m4.xlarge instance type if the number of calls are less and does not require transcoding.
   Volume Type	Select the type of volume for SBC.
   IOPS	Enter IOPS reservation for io 1 type EBS volume
   Volume Size	Enter size of disk required in GB.
   Number of Alternate IP on PKT0	Alternate IP address for packet port 0. Note: If you are using more than one IP for alternate IPs, use comma separated IPs list.
   Number of Alternate IP on PKT1	Alternate IP address for packet port 1. Note: If you are using more than one IP for alternate IPs, use comma separated IPs list.
   EipAssociationOnMgt	Select Yes from the drop-down to associate EIP for MGT0 interface to login and access SBC application from public networks.
   EipAssociationXface	MGT0 interface of active and standby systems will have elastic IPs associated. You can mention the required interfaces to be associated with EIP. For example, select PKT0 to associate EIP with PKT0 or PKT1 to associate EIP with PKT1, or both to associate EIPs for PKT0 and PKT1, or none not to associate EIPs with any interface. Note: After associating EIPs for interfaces, you must set the reverse NAT fields of the corresponding interfaces as true for SBC application to use the associated EIPs.
   ReveseNatEnablePkt0	Enable or disable reverse Network Address Translation (NAT) functionality for PKT0 interface. Set this field to true, to attach the assigned EIP on PKT0 and use it without SMM rule. See EipAssociationXface for associating EIP for the required interfaces. Note: When set to False, the SBC application cannot use the attached EIP.
   ReveseNatEnablePkt1	Enable or disable reverse Network Address Translation (NAT) functionality for PKT1 interface. Set this field to true, to attach the assigned EIP on PKT1 and use it without SMM rule. See EipAssociationXface   for associating EIP for the required interfaces. Note: When set to False, the SBC application cannot use the attached EIP.
   Keyname	Existing EC2 KeyPair name to enable SSH access on SBC instance.
   PlacementId	A placement group ID of logical group of instances within a single Availability Zone. This is an optional field and can be blank.

    

    

9. Click Next.

   Create A New Stack Page

   

   The Options page displays.
    

10. Enter a Key and Value.

    Tagging key-value pairs to the stack is optional.

11. Click Next.

    The Review page displays.
     

12. Review the stack details and click Create.

    Review Page

    

    On successful stack creation the stack will be listed.

Retrieving the admin Password for AWS Instances

Prior to 6.2.1 release, the default CLI admin user name and password for AWS SWe was admin/admin. The hard coded password must not be used for the security vulnerability on the AWS SWe platform.

1. Select the Stack Name once the stack is created.
2. Select the Outputs tab.

3. Copy the value of the field DefaultCliAdminPassword and use this value as the default password to login to the CLI/EMA/PM admin user. For more information, refer to Accessing an Active SBC SWe Instance Using EMA.

   DefaultCliAdminPassword in Outputs Tab

   
   
   
   

Verify the Instance Creation

Perform the following steps to view the SBC SWe instances created:

1. Click the Services drop-down list.
   The Services list is displayed.
    

2. From the left pane click EC2.

   Services

   

   The EC2 Dashboard page is displayed.
    

3. From the left pane under Instances click Instances.

   EC2 Dashboard

   

   The instances table lists the new instance.