Installing Unsupported Third-Party Applications on the ASM via VM

Purpose

This document details how to deploy a non-Sonus supplied/third party application onto an SBC Edge device with an ASM (Applications Solutions Module), featuring a D-1508 or D-1537 Intel® CPU and Microsoft® Windows Server® 2012 R2. For more details regarding the ASMs, see Application Solution Module.

The Application Solution Module (ASM) module is a separate, fully-functional server installed inside the 

Support for Third Party Applications via ASM (SBA) Host Operating System

Third-party software for the Sonus SBC Edge can be installed on the ASM Host Operating system, categorized as:

1. Supported. Third-party applications supported on the ASM Host Operating System are listed here: Approved Partner Solutions for ASM. For these approved applications, the ASM runs in Appliance Mode (SBA default offering).
2. Unsupported. Third-party applications installed directly on the ASM that are not currently supported by Sonus. For these unapproved applications, the ASM runs in Server Mode (performance and behavior of the SBA and Cloud Connector Edition applications are not guaranteed and not supported by Sonus).

For details on the ASM in Appliance or Server Mode, and installing supported third party applications onto the ASM, see Managing the ASM.

Support for Third Party Applications via VM 

As opposed to deploying a third party application on the ASM host operating system, customers can choose to deploy a third party application on a Hyper-V VM (Virtual Machine). When installing a third-party application on a VM, take note of the following ASM types:

How to Install a Third-Party Application on the ASM using a Virtual Machine (VM)

Verify ASM Hardware/Licensing Requirements

1. For new nodes, perform the initial setup as described in Running Initial Setup.

2. Connect to the SBC Edge WebUI for configuration. For access details, see Logging in to the SBC Edge.

3. Access System > ASM System Details to confirm the availability of an Intel® "Broadwell" based ASM ("Broadwell" Pentium® or "Broadwell" Xeon®). 
   

4. Ensure the physical and licensed resources are available for the VM-resident third party applications you wish to deploy.

   Available Resources for Third Party Applications

   ASM Type	Resources to allocate
   Broadwell" Pentium® D-1508 Based ASM	CPU Threads available: 2 RAM available: 4 GB Licensed Hyper-V VMs available: 2 Additional VMS available with Appropriate Licensing: Yes
   Broadwell" Xeon® D-1537 Based ASM	CPU Threads available: 15 RAM available: 30 GB Licensed Hyper-V VMs available: 4 Additional VMS available with Appropriate Licensing: Yes

   The CCE application will not be supported in the presence of any third party application being deployed on the Xeon ASM.

   For detailed information on CPU, memory specifications, and disk storage for the supported ASM hardware platforms, see Application Solution Module.

5. From the WebUI, click Tasks > Application Solution Module> Operational Status to further determine the resources you can use for the VM.
   

Start the Hyper-V Service

1. From the SBC Edge UI, navigate to Settings > Application Solution Module > Virtual Machines.

2. From the Hyper-V Action drop down list, select Start.

   Start the VM

   

    

3. Access Settings > Application Solution Module > Change Admin Password.

4. From the Password Option drop down list, select User Configured.

5. Enter the password and click OK.

Build the Virtual Machine (VM)

1. Connect to the ASM using remote desktop (see Enabling and Disabling Remote Desktop on the ASM).
2. Start the Hyper-V manager on the Remote Desktop.
   

    

   Hyper-V Manager

   

3. Load the ISO of the Operating System you plan to use.

4. For further steps on creating a VM and assigning your third party application(s) to the VM, refer to Microsoft TechNet Documentation (https://technet.microsoft.com/en-us/library/cc772480(v=ws.11).aspx.

5. Build additional VMs as needed. See Step 4.