Actions

FreeSBC:Cloud:VmWare Installation A: Difference between revisions

m (Wrong image size!)
 
(41 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:TSBC-SW:Cloud:VmWare Installation}}
{{DISPLAYTITLE:ProSBC/FreeSBC:Cloud:VmWare Installation}}
== Requirements ==
== Requirements ==
Minimal Cloud requirements:
Minimal Cloud requirements:
* Vmware ESX 5 or 6
* Vmware ESX 5 or 6
* 64 bits infrastructures only
* 64-bit infrastructure only
* 4 vCPU
* E1000 NIC emulation or VMXNET3 interfaces
* 20G hard drive
* One Ethernet adapter for management (mgmt0)
* 8G RAM
* One or more Ethernet adapter(s) for SIP and RTP traffic according to the table below (LAN/WAN)
* E1000 NIC emulation interfaces
* If you are deploying ProSBC in a 1+1 configuration, you need two (2) additional Ethernet adapters to be used as control ports (ctrl0/ctrl1).
* One Ethernet adapter for management
* If you are deploying ProSBC with transcoding devices, you will need four (4) additional Ethernet adapters to be used as control and transcoding ports (ctrl0/ctrl1, trans0/trans1).
* One or more Ethernet adapter(s) for data


For better performance (see [[TSBC-SW:Cloud:VmWare_Optimizations|optimization]] section)
{| cellpadding="5" border="1" class="wikitable"
|-
! width="150" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Sessions
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | CPU
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | RAM
! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Disk Space (SSD)
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Data Ethernet ports
|-
| valign="top" |
Up to 5,000
| valign="top" |
2 to 4
| valign="top" |
4 Gb
| valign="top" |
40 Gb
| valign="top" |
1 Gbps
|-
| valign="top" |
5,001-20,000
| valign="top" |
4 to 6
| valign="top" |
8 Gb
| valign="top" |
60 Gb
| valign="top" |
4 X 1 Gbps or
1 X 10 Gbps
|-
| valign="top" |
20,001-26,000
| valign="top" |
6 to 8
| valign="top" |
16 Gb
| valign="top" |
80 Gb
| valign="top" |
1 X 10 Gbps
|}
<nowiki>**</nowiki> The CPU number is based on Intel R630 with Xeon E5-2643. Double the CPUs number if yours are from a earlier generations.
 
More details on HW/CPU/NIC requirements can be found here: [[FreeSBC:RequirementsMatrix|Requirements Matrix]]
 
For better performance use these settings:
* CPU resource: allocation shares set to 'high'
* CPU resource: allocation shares set to 'high'
* CPU resource: reservation set to maximum and no limit (i.e. 'unlimited')
* CPU resource: reservation set to maximum and no limit (i.e. 'unlimited')
Line 17: Line 62:
* Disk: shares 'high'
* Disk: shares 'high'
* Advanced CPU: Hyperthread core sharing to 'None'
* Advanced CPU: Hyperthread core sharing to 'None'
* Latency Sensitivity: 'High'


== Getting the Image ==
== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.
Please go to our [http://www2.telcobridges.com/ProSBCDownload ProSBC Download site]  to get a copy of the latest SBC Image.


== Installation on VmWare cloud ==
== Installation on VmWare cloud ==


=== TBSC VmWare Image ===
=== ProBSC VmWare Image ===
A virtual machine image is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud.   
A virtual machine image is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud.   


You will need to upload the latest TSBC image into your VmWare before you can launch a virtual machine instance running the TSBC software.
You will need to upload the latest SBC image into your VmWare before you can launch a virtual machine instance running the SBC software.


==== Launching an instance ====
==== Launching an instance ====


#Log in using the Vmware infrastructure client interface
[[TSBC-SW:Cloud:VmWare_Launching_Instance_Web_A|Using the ESXi Web client]]
#Select File->Deploy OVF Template... from the menu <br/>[[File:vmware_upload.png|400px]]
#Browse to the location of the TSBC-SW image obtained from TelcoBridges <br/>[[File:vmware_ovf_location.png|400px]]
# Click 'Next' until you need to name the new virtual machine instance.  Enter the name and click 'Next' <br/>[[File:vmware_name.png|400px]]
# Select a datastore (if more than one are available) and select "Thick Provision Lazy Zeroed" as the disk format then click 'Next' <br/>[[File:vmware_disk.png|400px]]
# Accept all other default settings and wait until the machine is deployed.<br/> [[File:vmware_installing.png|200px]]
# Once deployed, right-click on the new instance and select "Edit Settings..." <br/>[[File:vmware_settings.png|400px]]
# Edit network adapters to connect on proper networks.  Make sure that at least one of the adapter connects to the private management network of the setup from which WebPortal access will be granted.  Do '''not''' press the 'OK' button yet. <br/>[[File:vmware_network.png|400px]]
# Go to the 'Resources' tab and select the CPU item.  Set 'Shares' to 'high', slide the 'Reservation' cursor to the max (i.e. right) and make sure the 'Unlimited' option is checked-marked.  Do '''not''' press the 'OK' button yet. <br/>[[File:vmware_cpu.png|400px]]
# Select the 'Memory' item and check-mark the 'Reserve all guest memory (All locked)' option.  Do '''not''' press the 'OK' button yet. <br/>[[File:vmware_mem.png|400px]]
# Select the 'Disk' item and set the 'Shares' to 'High'.  Do '''not''' press the 'OK' button yet. <br/>[[File:vmware_disk_res.png|400px]]
# Select the 'Advanced CPU' item and set the 'Mode' to 'None'.  Do '''not''' press the 'OK' button yet. <br/>[[File:vmware_adv_cpu.png|400px]]
# Press the 'OK' button
# Back to the main screen, select the newly instantiated virtual machine, right-click and select "Power-->Power On" to start it.  <br/>[[File:vmware_poweron.png|400px]]


=== Accessing the TSBC-SW ===
[[TSBC-SW:Cloud:VmWare_Launching_Instance_vSphere_A|Using the vSphere client application]]


==== Accessing the TSBC-SW web portal ====
If you are installing a standalone SBC, the ProSBC or FreeSBC will need access to LAN/WAN and MGMT networks. For transcoding on TSBC-HW-TRANS, or HA pair installation, the ProSBC will also need access to CTRL0/CTRL1, and TRANS0/TRANS1 networks. In both instance launching methods above, when editing network adaptor, please take reference to [[TSBC-SW:Networking|ProSBC Networking]] for details on network requirements. <br>
# Open a web browser to the management IP of the TSBC, on port 12358.  Example if your server address is 192.168.178.30, the URL would be: <br/> http://192.168.178.30:12358
For ProSBC Transcoding and associated network setup please also see [[FreeSBC:Transcoding and Network Setup]].
# You should get to the TSBC Configuration Wizard <br/> [[File:TSBC_WebPortal_Configuration_wizard.jpg|350px]]


From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration|Web Portal Initial Configuration Guide]] to continue the installation, and/or [[TSBC-SW:Baremetal:VmWare_Optimizations|optimize ]] your server to get the maximum out of your server.
=== Accessing the SBC ===
==== Accessing console ====
You need to use the VMware console to access the system - SSH interface is not activated yet. <br>
Default username/password is root/root.
 
==== Assigning IP address ====
By default, all detect network interfaces will have DHCP enabled.  Thus, the server might already have an IP address assigned if the network has a DHCP server running.  In such case, you can display and use it to access the web portal configuration panel.
 
# Retrieve an IP address assigned by DHCP
  # ifconfig
 
If you want to assigned a static IP address or there are no DHCP on your network, you will need to configure it manually.
 
# Use [[SBC:Change_Management_IP_Address|tbchangeip]] shell command and answered questions to changed your Ethernet interface address:
  # tbchangeip
 
<br>
'''Note:''' No changes must be done to the repositories on the systems, and no other software should be installed unless written consent from TelcoBridges.
 
==== Accessing the SBC web portal ====
* Open a web browser to the management IP of the SBC, on port 12358.  Example if your server address is 192.168.178.30, the URL would be: <br/> http://192.168.178.30:12358
<br/>
:You should get to the SBC Configuration Wizard <br/>
:[[File:TSBC_WebPortal_Configuration_wizard.jpg|700px]]
<br/>
* If you do not know the IP address, you can find it from the VMware interface: <br/>
:[[File:FreeSBC Initial IP address.png|700px]]
<br/>
* From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration|Web Portal Initial Configuration Guide]] to continue the installation, and/or [[TSBC-SW:Baremetal:VmWare_Optimizations|optimize ]] your server to get the maximum out of your server.


== Web Portal Initial Configuration ==
== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]
[[TSBC-SW:WebPortal:Initial Configuration|SBC Initial Configuration]]
 
== Optimizations ==
Click on the following link for VmWare optimizations:
[[TSBC-SW:Cloud:VmWare_Optimizations]]

Latest revision as of 16:47, 10 June 2022

Requirements

Minimal Cloud requirements:

  • Vmware ESX 5 or 6
  • 64-bit infrastructure only
  • E1000 NIC emulation or VMXNET3 interfaces
  • One Ethernet adapter for management (mgmt0)
  • One or more Ethernet adapter(s) for SIP and RTP traffic according to the table below (LAN/WAN)
  • If you are deploying ProSBC in a 1+1 configuration, you need two (2) additional Ethernet adapters to be used as control ports (ctrl0/ctrl1).
  • If you are deploying ProSBC with transcoding devices, you will need four (4) additional Ethernet adapters to be used as control and transcoding ports (ctrl0/ctrl1, trans0/trans1).
Sessions CPU RAM Disk Space (SSD) Data Ethernet ports

Up to 5,000

2 to 4

4 Gb

40 Gb

1 Gbps

5,001-20,000

4 to 6

8 Gb

60 Gb

4 X 1 Gbps or 1 X 10 Gbps

20,001-26,000

6 to 8

16 Gb

80 Gb

1 X 10 Gbps

** The CPU number is based on Intel R630 with Xeon E5-2643. Double the CPUs number if yours are from a earlier generations.

More details on HW/CPU/NIC requirements can be found here: Requirements Matrix

For better performance use these settings:

  • CPU resource: allocation shares set to 'high'
  • CPU resource: reservation set to maximum and no limit (i.e. 'unlimited')
  • Memory resource: reserve all guest memory (all locked)
  • Disk: shares 'high'
  • Advanced CPU: Hyperthread core sharing to 'None'
  • Latency Sensitivity: 'High'

Getting the Image

Please go to our ProSBC Download site to get a copy of the latest SBC Image.

Installation on VmWare cloud

ProBSC VmWare Image

A virtual machine image is a single file that contains a virtual disk that has a bootable operating system installed on it. Images are used to create virtual machine instances within the cloud.

You will need to upload the latest SBC image into your VmWare before you can launch a virtual machine instance running the SBC software.

Launching an instance

Using the ESXi Web client

Using the vSphere client application

If you are installing a standalone SBC, the ProSBC or FreeSBC will need access to LAN/WAN and MGMT networks. For transcoding on TSBC-HW-TRANS, or HA pair installation, the ProSBC will also need access to CTRL0/CTRL1, and TRANS0/TRANS1 networks. In both instance launching methods above, when editing network adaptor, please take reference to ProSBC Networking for details on network requirements.
For ProSBC Transcoding and associated network setup please also see FreeSBC:Transcoding and Network Setup.

Accessing the SBC

Accessing console

You need to use the VMware console to access the system - SSH interface is not activated yet.
Default username/password is root/root.

Assigning IP address

By default, all detect network interfaces will have DHCP enabled. Thus, the server might already have an IP address assigned if the network has a DHCP server running. In such case, you can display and use it to access the web portal configuration panel.

  1. Retrieve an IP address assigned by DHCP
 # ifconfig

If you want to assigned a static IP address or there are no DHCP on your network, you will need to configure it manually.

  1. Use tbchangeip shell command and answered questions to changed your Ethernet interface address:
 # tbchangeip


Note: No changes must be done to the repositories on the systems, and no other software should be installed unless written consent from TelcoBridges.

Accessing the SBC web portal

  • Open a web browser to the management IP of the SBC, on port 12358. Example if your server address is 192.168.178.30, the URL would be:
    http://192.168.178.30:12358


You should get to the SBC Configuration Wizard
TSBC WebPortal Configuration wizard.jpg


  • If you do not know the IP address, you can find it from the VMware interface:
FreeSBC Initial IP address.png


Web Portal Initial Configuration

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