Create and Deploy on Azure

You can deploy the Oracle Communications Session Border Controller (SBC) on Azure public clouds. Azure provides multiple ways of managing your environment(s), including via its web portal, using its powershell and its CLI interfaces. This document focuses on the portal. The portal provides navigation via a web-page pane with links to specified functions on the left side of portal pages. These procedure also assume you have reviewed Azure documentation, and can access portal pages and navigation.

Deployment detail specific to Azure includes:

• VM Interfaces—An initial instance deployment creates only a single (wancom0) network interface with an ACL for inbound SSH and HTTP/HTTPS access only. You add additional media interfaces after initial deployment.
• Interface Types—Use Para-Virtual interfaces for both management and media/signaling ports.
• Virtual Hard Disk (VHD) Size—The SBC default disk size for Azure is 20G. Use the formula, (2xRAM)+2+2+8 GB, and reconfigure the disk size during deployment if you plan on using the /sys and /app partitions or if you have larger RAM and disk requirements for your deployment.
• Console Selection—Use the serial console as the default device because Azure does not support a virtualized VGA console at startup.
• Cloud Detection—The SBC show platform command includes the cloud field, which, when applicable, shows the detected cloud environment, including Azure.

Note:

Azure auto-fills the target Subscription, Resource Group, Region and Location fields. These components are deployment-specific and used in some Azure configuration components. You may need to specify them if your cloud environment includes multiples of these components, which you would have defined prior to instance deployment.