ProSBC:Cloud:AWS Installation-B

This page is intended to give assistance to people launching an instance of ProSBC using an Amazon Machine Image (AMI) on Amazon Web Service (AWS).

Instantiate a ProSBC

• After logging in your Amazon account, click on “EC2” in the main AWS console:

• Be sure you are in the correct region, on the left menu click on “AMIs” and select “Private image” to locate FreeSBC/ProSBC AMI:

• Launch the FreeSBC/ProSBC image.

• Name the instance and add any necessary tag

• Select the instance type and its resources. The recommended instance type is:
  • m4.large (2 vCPU, 8 GiB)
• Supported instance type are:
  • C3, C4, D2, I2, M4 (excluding m4.16xlarge), and R3 instances (Supported instances from Amazon documentation)
    • Note: The Paris region is not supported at this time, since it does not have any of the supported instance types.
• This is the list of approximate performances for different AWS instance types. Results may vary according to configuration.

EC2 Instance	AWS CPU cores	Sessions per second (call rate)	Sessions with RTP anchoring	Sessions with Media bypass
m4.large	2	50	400	32,000
m4.xlarge	4	215	750	60,000
c4.xlarge	4	215	750	60,000
c4.2xlarge	8	575	2,000	60,000
m4.4xlarge	16	650	4,000	60,000
m4.10xlarge	40	650	4,800	60,000

• For later access to the FreeSBC/ProSBC SSH console you will need to select a Key Pair to secure the login. You can also create a new Key Pair in case you need.

• In "Networking Settings" select "Create security group". We recommend that you simply open "All Traffic" on your own IP addresses to whitelist it in AWS firewall on "Source", once all your IPs are listed click on "Add security group rule": (note that the SBC contains its own internal firewall)

• In "Configure Storage" change the Volume Size to 40Gb and select volume type to GP2.

• Finally review the summary of your instance and start the creation process clicking on "Launch Instance". Be aware, from this moment you will be billed by Amazon for the instance resources:

• You should receive the confirmation of the launching process, this process will take some minutes until the instance is available, You can view your instance clicking on “View Instances”:

Optional: Elastic IP Creation section

• If you want to use an associate public IP generated by Amazon (called "Elastic IP"). Click on "Elastic IP" on the left, then click on "Allocate new address":

• Click on "Allocate IP". A new public IP will be generated by Amazon:

• Click on "Close":

Optional: Elastic IP association section

• Go to the left pane and click on "Instance". Then select the instance "ProSBC" to display its description:

• Find the eth0 network interface in the instance description:

• Click on the eth0 Network Interface, then click on the "Interface ID" link:

• Right-click on the selected Network Interface, then click "Associate Address":

• In the Address list, select the public IP to associate with the main Network Interface. Then, click on "Associate Address":

• Click on "Instances" on the left pane and select "ProSBC" instance. Check if your instance is associated with a public IP:

Enable SR-IOV enhanced networking

It is very important to enable "enhanced networking" for tbrouter to have access to the network devices on the VM.

This must be done before completing the initial web portal configuration. Please shut down the instance before entering the serial number and all other information and set SR-IOV

There are two types of enhanced networking, we need the second one.

1) Elastic Network Adapter (ENA)

2) Intel 82599 Virtual Function (VF) interface

Install the AWS CLI

https://aws.amazon.com/cli/

Get security credentials for the command line

On the AWS web portal, click on your account name and choose "My Security Credentials"

Expand the "Access keys" section

Create a new key, you will need the AWSAccessKeyId and AWSSecretKey

Open a CLI and execute the aws cli commands

 aws configure

Paste the access key ID and key that you previously obtained along with your default region.

Show if the enhanced networking is enabled

Make sure to replace the example instance ID with your own AWS instance ID

 aws ec2 describe-instance-attribute --instance-id i-0123456789abcdef1 --attribute sriovNetSupport

Enabled:

 {
     "InstanceId": "i-0123456789abcdef1",
     "SriovNetSupport": {
         "Value": "simple"
     }
 }

Not enabled:

 {
     "InstanceId": "i-0123456789abcdef1",
     "SriovNetSupport": {}
 }

To enable the sriov enhanced networking, first turn off the instance then do:

 aws ec2 modify-instance-attribute --instance-id i-0123456789abcdef1  --sriov-net-support simple

Accessing the ProSBC

Accessing the ProSBC web portal

• Open a web browser to the management IP of the ProSBC, on port 12358. Example if your Instance public IP address is 35.183.126.193, the URL would be:
  http://35.183.126.193:12358

You should get to the ProSBC Configuration Wizard

Take note that it may take a while for the ProSBC system to make the Web Portal available (around 3-5 minutes).

• From here, you can go to Web Portal Initial Configuration Guide to continue the installation.

Web Portal Initial Configuration

Click on the following link to pursue installation from the web portal: ProSBC Initial Configuration

Troubleshooting

• Installation troubleshooting
• Recovering an Elastic IP address

External References

• Accessing device with SSH and private key using putty