Instantiating a Standalone Instance

To instantiate a standalone instance:

1. Log onto AWS.

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

3. From the left pane click EC2.

   Amazon Services

   

   The EC2 Dashboard page displays.
    

4. From the left pane under Images click AMIs.
   The AMI ID page displays.
   

   AMI ID Page

   

5. Choosing an AMI ID:

   1. Enter the AMI ID to search.
      The AMI entered displays.

   2. Select the AMI ID and click Launch.

      AMI ID

      

      The Choose an Instance Type page displays.

6. Choosing an instance type:

   1. Select an instance type that meets the requirements.

      Sonus recommends c4.2xlarge or higher instance type 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. 

      Chose an Instance Type

      

   2. Click Configure InstanceDetails.

      The Configure Instance Details page displays.

7. Configuring an instance:

   1. Select the Network (VPC) and Management Subnet from the list.
      This creates the mgt0 network interface and is attached as eth0.
       

   2. Select a Placement group from the list.
      

      A placement group ID is a logical grouping of instances within a single Availability Zone. This is an optional field and can be blank.

       

   3. Select Tenancy from the list.
      

      Dedicated instances have a dedicated hardware isolated at host hardware level from the non-dedicated instances and instances that belong to other AWS accounts.
      It accepts default - for instances running on shared hardware or dedicated - for instances running on a single-tenant hardware.

       

   4. Click Advanced Details section to expand.

   5. In the User data section select As text.

   6. Enter the user data information in the following format:

      Format of Userdata for Standalone

      If the CERole parameter is missing, it represents standalone userdata format.

      {
       "ReverseNatPkt0" : "False", 
       "ReverseNatPkt1" : "False",
       "CEName" : "CEName",
       "SystemName" : "SystemName"
       
      }

      Example of Userdata for Standalone

      If the CERole parameter is missing, it represents standalone userdata format.

      {
       "ReverseNatPkt0" : "False", 
       "ReverseNatPkt1" : "False", 
       "SystemName" : "vsbcSystem", 
       "CEName" : "vsbc1"
      }

       

       

      Userdata Parameter Description

      Parameter	Length	Format	Description
      ReverseNatPkt0 / ReverseNatPkt1	Reverse NAT flag for Pkt0 and Pkt1 Default value - False	True/False	Values: True: To consider FIPV4 entity using value provided in the dictionary False: To configure FIPV4 using SMM rules, and ignore the FIPV4 value provided here.
      CEName	64	vsbc1	Specifies the actual CE name of the SBC instance. For more information, see System and Instance Naming Conventions. CEName Requirements: Must start with an alphabetic character. Only contain alphabetic characters and/or numbers. No special characters. Cannot exceed 64 characters in length
      SystemName	26	vsbcSystem	Specifies the actual system name of the SBC instance. For more information, see System and Instance Naming Conventions. System Requirements: Must start with an alphabetic character. Only contain alphabetic characters and/or numbers. No special characters. Cannot exceed 26 characters in length.

      
      

   7. Click Next: Add Storage.
      
      

      Configure Instance Details

      

      The Add Storage page opens.

8. Adding storage:

Select Provisioned IOPS (SSD) as Volume Type.

1. 1. Click Tag Instance.

      Add Storage

      

      The Tag Instance page displays.

2. Tagging an instance:

   1. Enter a key name and value.

      Click Create Tag to create more than one tag.

   2. Click Configure Security Group.

      Tag Instance

      

      The Configure Security Group page displays.

3. Configuring security group:

   1. Click Select an existing security group.

   2. Select the management security group from the list.

   3. Click Review and Launch.

      Configure Security Group

      

      The Review Instance Launch page displays.

4. Reviewing an instance:

   1. Review the instance details and click Launch.

      Review Instance Launch

      

      You will be prompted to select a key pair.
       

5. Selecting a key pair:

   1. Select Choose an existing key pair from the drop-down and select the key pair.

   2. Select the acknowledgement for the key.

   3. Click Launch Instances.

      Selecting a Key Pair

      

      Use a key-value pair for which you have a .pem file because you will need that for logging (ssh) into the system.

      The new instance will launch.

6. Click the instance ID to view the instance.

   Launch Status

   

    

   The new Instance details displays. Wait until the Instance State changes from Pending state to running state.

   New Instance Details

   

7. Stopping an instance:

   1. Right-click the instance and select Instance State > Stop.

      Stopping an Instance

      

      A message appears to confirm stopping the instance.
       

   2.  Click Yes, Stop.
      

      Instance Stop Confirmation

      

       

8. Attaching network interface:

   1. Right-click the instance and select Networking > Attach Network Interface.

      The network interface must be attached with the instance in the order of HA, PKT0, and PKT1.

      Attaching a Network Interface

      

   2. Select the HA interface and click Attach.

      Attaching HA Network Interface

      
      This attaches the HA network interface as eth1.
      
      

9. Repeat step 15 to attach PKT0 and PKT1 network interfaces.

   In instance details, the attached network interfaces are listed as eth0, eth1, eth2, and eth3. Sonus refers to these as MGT0, HA, PKT0, and PKT1 respectively.

10. Starting an instance:

    1. Right-click the instance and select Instance State > Start.
       

       The system takes approximately 6-8 minutes to start.

       
       

       Starting the Instance

       

        

    2. Click Yes, Start.
       A message appears to confirm starting the instance.
       

       Instance Start Confirmation

       

       New Instance

       

       The systemName and local host name can be changed by editing the userdata. For more information, refer to Metadata and Userdata Format, Meta Variables and CLI Configuration on AWS.