Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
JIRAIDAUTHSYM-23035
REV5UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85500c9, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc5207f0, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f9, userName='null'}

Include Page
Not_for_SWe
Not_for_SWe

Panel

Table of Contents
maxLevel3


Purpose

This document details how to deploy a non-Ribbon supplied/third party application onto an

Spacevars
0product
 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.


Warning
  • Third party applications are not supported by Ribbon.
  • This document does not apply to ASMs shipped prior to the availability of Release 6.1 software (e.g., ASMs that feature a Celeron® CPU, Atom®, etc).


Background - How does the ASM Support Third Party Applications?

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

Spacevars
0longproduct
 chassis. Third-party software may be installed on the ASM host operating system or onto a Hyper-V VM (Virtual machine).  

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

Third-party software for the Ribbon 

Spacevars
0product
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 Ribbon. 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 Ribbon).

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

Info

This document does not apply to third party applications installed on an ASM's host operating system; this section is provided for context. See Best Practice - Common Use Cases for Repurposing the ASM for Third-Party Applications and Server Mode.

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 typestype:


ASM shipped with CCE (D-1537 CPU, as part of a Cloud Link device)
ASM TypeOperation Details
ASM shipped with SBA Application (D-1508 CPU)
  • The SBC remains in Appliance mode (i.e., Ribbon continues to provide support for the SBA application), provided no adjustments are made by the customer to remove physical and OS resources from the SBA.
  • Two Hyper-V VMs are available for use without additional licensing from Rbbon.
  • Additional Hyper-V VMs are available for use with additional licensing from Ribbon.
  • The SBC remains in Appliance mode, but does not support the CCE application. A CCE deployment within a Ribbon appliance mandates no third party applications on the ASM. Ribbon will confine support to the ASM OS and hardware.
  • Four Hyper-V VMs are available for use without additional licensing from Ribbon.
  • Additional Hyper-V VMs are available for use with additional licensing from Ribbon.


Note

This document details how to add third party applications to a VM. Ribbon is not responsible for the performance or support of third party applications installed on the VMs. Ribbon will only support the system in Appliance mode and may request the VMs to be temporarily turned off in order to support the OS and the SBA applications.


Info

For detailed information on how to repurpose a Cloud Link ASM to operate the Skype for Business server, see Best Practice - Repurposing the Ribbon Cloud Link ASM for Skype for Business Server 2015 Standard Edition.

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

Anchor
VerifyASM
VerifyASM
Verify ASM Hardware/Licensing Requirements

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

  2. Connect to the 

    Spacevars
    0product
    WebUI for configuration. For access details, see Logging into the SBC Edge Portfolio.

  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

    The CCE application will not be supported in the presence of any third party application being deployed on the Xeon ASM.
    ASM TypeResources to allocate
    Broadwell" Pentium® D-1508 Based ASMCPU 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 ASMCPU Threads available: 15
    RAM available: 30 GB
    Licensed Hyper-V VMs available: 4
    Additional VMS available with Appropriate Licensing:     Yes
    Warning


    Info

    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 

    Spacevars
    0product
    UI, navigate to Settings > Application Solution Module > Virtual Machines.

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

  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.

  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.
Info

To return the ASM to its original state, delete the VM(s) you created: Access Hyper-V Manager, click Turn Off and then click Delete.