Instantiate Standalone SBC in GCP

Use this procedure to instantiate a Standalone SBC on Google Cloud.

Prerequisites

The steps to do a Manual install of a standalone SBC instance are as follows (refer to Configure VPC Networks for details):

1. Create VPC Subnets for use in the deployment. 
2. Create Firewall Rules to each of the VPC networks created. 
3. Update or create Routes for the newly created subnets. 
4. Allocate Static External IP Addresses to be used for external access to the SBC. See 336572541.

Instantiating a Standalone GCE SBC Instance

Complete the following steps to instantiate a Standalone SBC instance in Google Cloud:

1. From the GCP Console Navigation menu, navigate to, select Compute Engine > VM instances.
2. Click Create. 
   The Create an instance page displays.
   
   
   
3. Enter a name in the Name field.
4. Select an appropriate Region.
5. Select an appropriate Zone.
6. Click Customize in the Machine type panel to open the expanded list.
7. Use the sliders to select 4 vCPU and 15 GB memory. 
   
   
   
8. Select Intel Broadwell or later under CPU platform.
9. Choose the Boot disk option and then press Change to open the Boot disk panel: 
   
   
10. Select Custom Images, then select the account containing the image (if not the current) and choose the SBC image.
11. Select SSD persistent disk as the Boot disk type with the disk size as ≥ 65GB. 
12. Click Select.
13. Under Identity and API access click Allow full access to all Cloud APIs.
14. Click on Management, security, disks, networking, sole tenancy. The tab will expand.
    

15. Click Management.

16. In the Metadata section, enter the following data using Key value "user-data". The following table describes the user-data. 
    Meta Data Format - Key = user-data
    

    Meta Data value

    #cloud-config
    runcmd:
        - usermod -p '$6$io3njQos$gZtBJ4MazQeWC0beqQwRPUDZCQcKXhMr2B8QLWYGajchR2BtkyHPvBTCQj0LctHAFaYTwbsIsUkm12ta4IoLe/' linuxadmin
    write_files:
        - content: | 
              {
                "CEName": "<CEName>",
                "SystemName": "<SystemName>",
                "SbcPersonalityType": "isbc",
                "Mgt0Prefix": "<prefix>",
                "ThirdPartyCpuAlloc" : "0",
                "ThirdPartyMemAlloc" : "0"
              } 
    path: /opt/sonus/conf/userData.json

    
    Meta Data Example - Key = user-data
    

    Meta Data value

    #cloud-config
    runcmd:
        - usermod -p '$6$io3njQos$gZtBJ4MazQeWC0beqQwRPUDZCQcKXhMr2B8QLWYGajchR2BtkyHPvBTCQj0LctHAFaYTwbsIsUkm12ta4IoLe/' linuxadmin
    write_files:
        - content: |
              {
                "CEName": "vsbc1",
                "ReverseNatPkt0" : "False",
                "ReverseNatPkt1" : "False",
                "SystemName": "vsbcSystem",
                "SbcPersonalityType": "isbc",
               "ThirdPartyCpuAlloc" : "0",
               "ThirdPartyMemAlloc" : "0",
                "Mgt0Prefix": "20"
              }
          path: /opt/sonus/conf/userData.json

    Userdata Content Description
    Parameter	Length	Type/Format	Description
    CEName	64	string	This specifies the actual CE name of the SBC instance. For more information, refer to System and Instance Naming in SBC SWe N:1 and Cloud-Based Systems. 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	string	This specifies the actual system name of the SBC instance. For more information, refer to System and Instance Naming in SBC SWe N:1 and Cloud-Based Systems System Requirements: Must start with an alphabetic character. Only contain alphabetic characters and/or numbers. No special characters. Cannot exceed 26 characters in length.
    Mgt0Prefix	2	digits	The prefix (for example, /24) of the MGT0 subnet.
    SbcPersonalityType	4	string	The name of the SBC personality type for this instance. At this time only integrated SBC (isbc) is supported in AWS.
    ThirdPartyCpuAlloc	n/a	0-? in vCPUs	Enter the number of CPUs to be reserved for use with third-party apps.   Note: Default is 0
    ThirdPartyMemAlloc	n/a	0-? in MB	Enter the number of MB of memory to be reserved for use with third-party apps.    Note: Default is 0

17. Click Networking.

18. Click default under Network interfaces. The default Network interface will expand.
    

19. Select the management VPC Network that you created earlier.

20. For Subnetwork select the management network that you created earlier.

21. Select Ephemeral (Automatic) for Primary internal IP.

22. Select an External IP for management based on that you created earlier.

23. Click Done.

24. Click Add network interface to add an interface for HA0.

25. Select the appropriate VPC Network that you created earlier.

26. For Subnetwork select the management network that you created earlier.

27. Select Ephemeral (Automatic) for Primary internal IP.

28. Click Done.

29. Repeat steps 24-28 for PKT0 and PKT1 networks.
    Once completed, the Networking tab will be similar to this example:
    

30. Click Create to instantiate the VM.

Enabling Serial Console Access to the Instance

1. After you create the instance, click the instance name and then click EDIT.
2. Enable the console access by clicking Enable connecting to serial ports.
3. Click Save. 
   
   

Connecting to the Serial Console of the Instance

1. After you create the instance, click the instance name and then click EDIT.
2. Connect to the serial console by clicking Connect to serial console. 
   
   
3. The first item shown in the console is the SSH key information needed to connect to the instance using the SSH key.