TBwiki - User contributions [en]

Toolpack prerequisite CentOS7 A

2017-10-18T14:32:58Z

Cboulanger: Added DISTRO environment variable (tracking #22152)

'''<big>Applies to version(s) v2.8 to v2.9</big>'''
{{DISPLAYTITLE:Toolpack Prerequisites for CentOS 7}}

''WARNING'': The host MUST have been installed with the CentOS 7 DVD/ISO pointed in this procedure.



''WARNING'': The host MUST have been installed using the "Minimal" package set within the CentOS installation wizard.


== Install the base CentOS 7 server ==

Download the following DVD image:
http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/centos/CentOS-7.0-1406-x86_64-DVD.iso

Press Enter to choose the graphical installation:
* Enable the ethernet interface and set the hostname (make sure it is not localhost.localdomain)
* Select the "Minimal" install package

=== Configure network connection ===
If the IP interface was not configured and enabled during installation, it can be configure with the following command from a console connection or a monitor/keyboard connected to the server.

To list the ethernet card installed on your machine:
nmcli d

If your device shows the STATE as "disconnect", start the '''Network manager''' by typing:
nmtui

* Select "Edit a connection" and press Enter
* Select your network interface, select "Edit" (use arrows to change options), press Enter
* Set IPv4 static address or choose “Automatic” (for DHCP) in IPv4 CONFIGURATION and check "Automatically connect" check box.
* Select "Quit", press Enter

service network restart

Check your ip interface using:
ip addr

=== Add base packages ===
To continue installation, you need to download a few packages not provided by the minimal installation:

yum install net-tools wget

== Configure TelcoBridges repository ==

=== Online repository procedure ===
This procedure requires internet access and a DNS configured on your unit

==== Add TelcoBridges repository file ====

vi /etc/yum.repos.d/TB-Base.repo

Paste the following information in that file:

# TelcoBridges-Base.repo
#
# This repository is using TelcoBridges frozen version of CentOS
# to help client installing the required version of the
# applications required to run Toolpack
#

[tb-base]
name=TelcoBridges-$releasever - Base
baseurl=http://repo.telcobridges.com/centos/7/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-TB7

==== Get TelcoBridges repository key ====

cd /etc/pki/rpm-gpg/
wget http://repo.telcobridges.com/centos/7/os/x86_64/RPM-GPG-KEY-TB7

=== Offline repository procedure ===
This procedure '''does not''' requires internet access.

==== Install TelcoBridges repository locally ====

Download the .iso image of the repository
http://repo.telcobridges.com/centos/7/isos/x86_64/tb_centos7_x86_64_repo.iso

* Upload this .iso file to the "/root" directory of the server with scp or a SFTP tool like [http://filezilla-project.org/ FileZilla]
* Mount the .iso file on your server
mkdir -p /repo/centos/7
mount -t iso9660 -o loop /root/tb_centos7_x86_64_repo.iso /repo/centos/7

Add the mount point permanently to the system to make it stay after a reboot.
# cp /etc/fstab /etc/fstab.bak
# echo "/root/tb_centos7_x86_64_repo.iso /repo/centos/7 iso9660 loop 0 0" >> /etc/fstab

==== Add TelcoBridges repository file ====

vim /etc/yum.repos.d/TB-Base.repo

Paste the following information in that file:

# TelcoBridges-Base.repo
#
# This repository is using TelcoBridges frozen version of CentOS
# to help client installing the required version of the
# applications required to run Toolpack
#

[tb-base]
name=TelcoBridges-$releasever - Base
baseurl=file:///repo/centos/7/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-TB7

==== Get TelcoBridges repository key ====

cd /etc/pki/rpm-gpg/
cp /repo/centos/7/RPM-GPG-KEY-TB7 .

== Update CentOS ==
=== Disable base CentOS repositories ===

Edit the Centos repository configuration file

vi /etc/yum.repos.d/CentOS-Base.repo

Disable all repositories in that file. Example:

[base]
'''enabled=0'''
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#released updates
[updates]
'''enabled=0'''
name=CentOS-$releasever - Updates
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that may be useful
[extras]
'''enabled=0'''
name=CentOS-$releasever - Extras
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
'''enabled=0'''
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

=== Package update ===

Remove conflicting packages with TelcoBridges repository part of the original DVD

yum remove NetworkManager xfsprogs

Update your system to latest packages from TelcoBridges repository

yum clean all
yum update

If there was a kernel update, you need to reboot the machine to activate it:

shutdown -r now

=== Reply to ARP only on local interfaces ===

Modify the file /etc/sysctl.conf to add the following lines:

net.ipv4.conf.default.arp_ignore=1
net.ipv4.conf.all.arp_ignore=1

Then restart network interfaces using the following command:

service network restart

=== Disabling SELinux ===

Check SELinux status

sestatus

If SELinux is enable, see the [[SELinux_management|Disabling SELinux]] article to disable it.

=== Disabling Firewalld ===

systemctl mask firewalld
systemctl stop firewalld

== Install Toolpack Prerequisites ==

Then, install Toolpack set of pre-requisite packages. When asked to 'Importing GPG key', answer yes.

yum groupinstall Toolpack-Prerequisites

=== Configure ODBC ===

Be sure that Toolpack system is stopped before manipulating MySQL.

tbtoolpack stop

vi /etc/odbcinst.ini

Remove the '#' in front of each lines of the [MySQL] section Modify the 'Driver' line to set the correct driver

 Example:
[MySQL]
Description = ODBC for MySQL
Driver = /usr/lib/libmyodbc5.so
Setup = /usr/lib/libodbcmyS.so
Driver64 = /usr/lib64/libmyodbc5.so
Setup64 = /usr/lib64/libodbcmyS.so
FileUsage = 1

=== Configure MariaDB ===

vi /etc/my.cnf

Add these variables in the file under the [mysqld] section:

*log-bin=mariadb-bin
*relay-log=mariadb-relay-bin
*innodb_doublewrite=1
*innodb_flush_log_at_trx_commit=1
*sync_binlog=1
*expire_logs_days=30
*max_binlog_size=500M
*server-id=''[UniqueId]''
*innodb_stats_on_metadata=0

The server-id needs to be a non-zero unique value (do not use 0). If you use the host redundancy feature, the value '''MUST to be different''' on each host .

 Add below to remove database dependencies with DNS servers '''(**Applicable to TMG users only)'''

skip-name-resolve

 Add max_allowed_packet to increase the maximum size of binary blobs in the database. Make sure it is in the [mysqld] section AND [mysqldump] section

max_allowed_packet = 200MB

Example:

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
symbolic-links=0
log-bin=mariadb-bin
server-id=1123476
max_allowed_packet = 200MB
skip-name-resolve
expire_logs_days=30
max_binlog_size=500M
relay-log=mariadb-relay-bin
innodb_doublewrite=1
innodb_flush_log_at_trx_commit=1
sync_binlog=1
innodb_stats_on_metadata=0

[mysqldump]
max_allowed_packet = 200MB

 Enable and start MariaDB

systemctl enable mariadb
systemctl start mariadb

 Use the MariaDB wizard to secure your server installation.
mysql_secure_installation

You should:
* Set new root password
* Remove anonymous users
* Disallow root login remotely
* Remove test database and accesses
* Reload privilege tables

Example:

mysql_secure_installation

Set root password? [Y/n] Y
New password: AVeryStrongPassword
Re-enter new password: AVeryStrongPassword
Password updated successfully!
Reloading privilege tables..
... Success!
Remove anonymous users? [Y/n] Y
... Success!
Disallow root login remotely? [Y/n] Y
... Success!
Remove test database and access to it? [Y/n] Y
- Dropping test database...
... Success!
- Removing privileges on test database...
... Success!
Reload privilege tables now? [Y/n] Y
... Success!
Cleaning up...
Thanks for using MariaDB!

=== Restart the MariaDB service ===
systemctl restart mariadb

=== Configure MariaDB user ===

* Create a tbdb user (required by Toolpack)

Example:

mysql -uroot -pAVeryStrongPassword

USE mysql;
CREATE USER 'tbdb'@'%' IDENTIFIED BY 'tbdbpw';
GRANT ALL PRIVILEGES ON *.* TO 'tbdb'@'%' IDENTIFIED BY 'tbdbpw';
FLUSH PRIVILEGES;
exit

=== Install additional ruby gems ===
wget http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/linux/bundler-1.2.3.gem
gem install --local ./bundler-1.2.3.gem

wget http://download.distribution.telcobridges.com/3rdparty/prerequisite/bin/linux/json-1.7.7.gem
gem install --local ./json-1.7.7.gem

== Toolpack Development Prerequisite (Optional) ==

The Toolpack System Development prerequisite section is only required for customers that will develop their own application using the Toolpack API:

yum install libxml2-devel libpcap-devel unixODBC-devel libaio libaio-devel libcurl-devel.x86_64 ruby-devel.x86_64 libxslt

Be sure to add this environment variable by editing ~/.bashrc

vi ~/.bashrc
Add the following line:
---------
export DISTRO=centos7
---------
source ~/.bashrc

== Validation Guide (highly recommended) ==

If you would like to verify your installation go to the [[Toolpack_Installation:Validate_Toolpack_Installation_A|Toolpack Validation Guide]]

 

== Toolpack System installation ==

Now that the prerequisite are installed, now it is time to install the [[Toolpack_installer_B|Toolpack system]]

TSBC-SW:Cloud:VmWare Launching Instance Web A

2017-10-06T12:56:20Z

Cboulanger:

== Launching an instance using ESXi web interface ==

# Log in using the Vmware web interface
# Select 'Virtual Machines' from the left menu [[File:vmware_web_virtual_machines.png|200px]]
# Click on 'Create / Register VM' [[File:vmware_web_create.png|400px]]
# Select 'Deploy a virtual machine from an OVF or OVA file' then press 'next' [[File:vmware_web_select_type.png|400px]]
# Enter the name. Drag the file or browse to the location of the TSBC-SW image obtained from TelcoBridges. 'Click 'Next' [[File:vmware_web_browse_ova.png|400px]]
# Select a datastore (if more than one are available) then click 'Next' [[File:vmware_web_select_storage.png|400px]]
# Choose your network. Select 'Thick' disk provisioning. Uncheck 'Power on automatically'. Click 'Next' [[File:vmware_web_deployment_options.png|400px]]
# Click 'Next' [[File:vmware_web_ready_to_complete.png|400px]]
# Do not refresh your browser and wait until the machine is deployed. [[File:vmware_web_installing.png|400px]]
# Once deployed, edit the VM [[File:vmware_web_edit_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 'Save' button yet. [[File:vmware_web_network.png|400px]]
# Click on 'CPU' to open the details. Set 'Shares' to 'high', enter the maximum number of MHz corresponding to your number of CPU cores in 'Reservation' (See [[TSBC-SW:Cloud:VmWare_Launching_Instance_Web_A#Calculating_Reserved_CPU_MHz|Calculating Reserved CPU]]) and make sure the 'Unlimited' option is selected. Do '''not''' press the 'Save' button yet. [[File:vmware_web_cpu.png|400px]]
# Open the 'Memory' details and check-mark the 'Reserve all guest memory (All locked)' option. Do '''not''' press the 'Save' button yet. [[File:vmware_web_memory.png|400px]]
# Open the 'Hard disk 1' details and set the 'Shares' to 'High'. Do '''not''' press the 'Save' button yet. [[File:vmware_web_disk_res.png|400px]]
# Click on the second tab 'VM Options', expand 'Advanced' and set 'Latency Sensitivity' to 'High' then press the 'Save' button. [[File:vmware_web_latency.png|400px]]
# Back to the main screen, click on "Power On" to start the new VM. [[File:vmware_web_poweron.png|400px]]
# Once the VM had completely booted, its assigned DHCP IPs will be displayed in General Information -> Networking. Note this IP address to access the Web Portal configuration interface later. [[File:vmware_web_ip.png|400px]]

=== Calculating Reserved CPU MHz ===
To get the MHz per core, you need to figure out the total number of available MHz that your system has and divide by the total number of cores.
# Select 'Host' on the left menu [[File:vmware_web_host.png|200px]]
# Take note of the number of cores this system has. (In this example: 12) Also take a look at the 'CAPACITY', but is is not precise down to the MHz (In this example 36.7 GHz) [[File:vmware_web_total_cpus.png|400px]]
# When editing the VM, in the disk details, expand the 'Reservation' combobox. There should be a number in exact MHz for the maximum capacity of the system (In this example: 36708) [[File:vmware_web_total_mhz.png|400px]]
# Calculate your VM CPU MHz Reservation requirement
::mhz_per_core = total_system_mhz / total_system_cpus (In this example: 3059 = 36708 / 12 )
::vm_reserved_mhz = vm_cpus * mhz_per_core (In this example: '''12236''' = 3059 * 4 )

TSBC-SW:Cloud:VmWare Launching Instance vSphere A

2017-10-06T12:52:36Z

Cboulanger: Adding logging page image

==== Launching an instance the vSphere client ====

#Log in using the Vmware infrastructure client interface [[File:login_client.png|200px]]
#Select File->Deploy OVF Template... from the menu [[File:vmware_upload.png|400px]]
#Browse to the location of the TSBC-SW image obtained from TelcoBridges [[File:vmware_ovf_location.png|400px]]
# Click 'Next' until you need to name the new virtual machine instance. Enter the name and click 'Next' [[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' [[File:vmware_disk.png|400px]]
# Accept all other default settings and wait until the machine is deployed. [[File:vmware_installing.png|200px]]
# Once deployed, right-click on the new instance and select "Edit Settings..." [[File:vmware_settings.png|400px]]
# Press the 'OK' button [[File:Vmware_restricted.png]]
# 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. [[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. [[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. [[File:vmware_mem.png|400px]]
# Select the 'Disk' item and set the 'Shares' to 'High'. Do '''not''' press the 'OK' button yet. [[File:vmware_disk_res.png|400px]]
# Select the 'Advanced CPU' item and set the 'Mode' to 'None'. Do '''not''' press the 'OK' button yet. [[File:vmware_adv_cpu.png|400px]]
# Set the 'Latency Sensitivity' to 'High'
# 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. [[File:vmware_poweron.png|400px]]
# Again to the main screen, select the newly instantiated virtual machine and choose the 'Summary' tab. Once the virtual machine is completed booted, the assigned DHCP IP address will be displayed by clicking on the 'View all' button. Note this IP address to access the Web Portal configuration interface later. [[File:vmware_ip.png|400px]]

File:Login client.png

2017-10-06T12:51:25Z

Cboulanger:

TSBC-SW:Cloud:VmWare Launching Instance vSphere A

2017-10-06T12:49:50Z

Cboulanger: Removing word fat

==== Launching an instance the vSphere client ====

#Log in using the Vmware infrastructure client interface
#Select File->Deploy OVF Template... from the menu [[File:vmware_upload.png|400px]]
#Browse to the location of the TSBC-SW image obtained from TelcoBridges [[File:vmware_ovf_location.png|400px]]
# Click 'Next' until you need to name the new virtual machine instance. Enter the name and click 'Next' [[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' [[File:vmware_disk.png|400px]]
# Accept all other default settings and wait until the machine is deployed. [[File:vmware_installing.png|200px]]
# Once deployed, right-click on the new instance and select "Edit Settings..." [[File:vmware_settings.png|400px]]
# Press the 'OK' button [[File:Vmware_restricted.png]]
# 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. [[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. [[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. [[File:vmware_mem.png|400px]]
# Select the 'Disk' item and set the 'Shares' to 'High'. Do '''not''' press the 'OK' button yet. [[File:vmware_disk_res.png|400px]]
# Select the 'Advanced CPU' item and set the 'Mode' to 'None'. Do '''not''' press the 'OK' button yet. [[File:vmware_adv_cpu.png|400px]]
# Set the 'Latency Sensitivity' to 'High'
# 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. [[File:vmware_poweron.png|400px]]
# Again to the main screen, select the newly instantiated virtual machine and choose the 'Summary' tab. Once the virtual machine is completed booted, the assigned DHCP IP address will be displayed by clicking on the 'View all' button. Note this IP address to access the Web Portal configuration interface later. [[File:vmware_ip.png|400px]]

FreeSBC:Cloud:VmWare Installation A

2017-10-06T12:49:25Z

Cboulanger: Removing word "fat"

FreeSBC:Baremetal:Installation A

2017-09-25T14:42:21Z

Cboulanger: /* Installing using the ISO burned onto a bootable USB flash drive */

{{DISPLAYTITLE:TSBC-SW:Baremetal:Installation}}

== Requirements ==
Minimal server requirements:
* 64 bits server
* Quad core Intel CPU 2GHz
* Optical disk drive
* 80GB hard drive
* 8G RAM
* One management Ethernet
* Data Ethernet adapters
** 5,000 sessions or less: one 1Gbps interface
** 10,000 sessions or less: two 1Gbps interface
** 60,000 sessions: two 10Gbps interfaces
** See list of supported Network Interface Cards (NICs) here: [[Supported_NICs|List of supported NICs]]
* Console access through serial port or keyboard/monitor ports
* BIOS setup for maximum performance (i.e. no dynamic CPU throttling)

For better performance (see [[TSBC-SW:Baremetal:Optimizations|optimization]] section)
* NUMA tuning
* PCIe tuning

== Getting the ISO ==
Please contact our [mailto:sales@telcobridges.com sales team] to get a copy of the latest TBSC-SW ISO.

== Installing the ISO ==
The installation process will reformat the server's disks and install all the necessary software.

=== Installing using the ISO burned onto a bootable USB flash drive ===
Use a software application to burn the ISO onto a USB flash drive. On Windows, [[https://rufus.akeo.ie/ |Rufus ]] is known to work with the TSBC-SW ISO.
But generally any similar application should work. Make sure to set the volume label to "'''CENTOS 7 X8'''" and to format the drive in the FAT32 file system format.

=== Physical installation steps ===
# Identify which Ethernet networks you need and connect them to your server. Refer to [[TSBC-SW:Networking]] for more information
# Burn the ISO onto a DVD or a USB flash drive
# Get an access to the console of the server. Usually, this is achieved by connecting a keyboard and screen to the server.
# Insert the DVD in the optical drive of your server and boot from the DVD drive.
#* Alternatively, plug in your USB flash drive and boot from that drive.
# You should get the to the "Virtual Appliance Installer" menu on your display: [[File:ISO_install_prompt.jpg|350px]]
# Hit 'R' key, then 'ENTER' key to start the installation [[File:ISO_installing.jpg|350px]]
# Wait for the installation process to complete. When installation is complete, the server will reboot itself.
#* Important: Make sure to remove the DVD from the drive while the server is rebooting. If you get back to "Virtual Appliance Installer", just eject the CD or remove the USB flash drive and reboot again.
# It may take a couple of minutes for the system to be brought up after the first reboot. Until the WebPortal is accessible, you must '''not''' reboot the newly created machine to allow the installation to complete properly.

=== Changing the root password ===
# Use the console to login into the server
## user: root
## password: root
# Change the password to something stronger than root:
# passwd
New password: ........
Retype new password: ........
passwd: all authentication tokens updated successfully.

=== 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 there is no IP assigned, you will need to configure one manually.

# Assign a IP address to the Ethernet interface having network connectivity. Example if the NIC's name would be eth0:
# ip link set eth0 up
# ip addresss add 192.168.178.30/24 dev eth0

=== Accessing the TSBC-SW web portal ===
# Open a web browser to the IP of your server, 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 TSBC Configuration Wizard [[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:Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for baremetal server optimizations:
[[TSBC-SW:Baremetal:Optimizations]]

FreeSBC:Baremetal:Installation A

2017-08-31T18:42:30Z

Cboulanger: Added a warning not to reboot before the webportal is accessible

{{DISPLAYTITLE:TSBC-SW:Baremetal:Installation}}

== Requirements ==
Minimal server requirements:
* 64 bits server
* Quad core Intel CPU 2GHz
* Optical disk drive
* 80GB hard drive
* 8G RAM
* One management Ethernet
* Data Ethernet adapters
** 5,000 sessions or less: one 1Gbps interface
** 10,000 sessions or less: two 1Gbps interface
** 60,000 sessions: two 10Gbps interfaces
** See list of supported Network Interface Cards (NICs) here: [[Supported_NICs|List of supported NICs]]
* Console access through serial port or keyboard/monitor ports
* BIOS setup for maximum performance (i.e. no dynamic CPU throttling)

For better performance (see [[TSBC-SW:Baremetal:Optimizations|optimization]] section)
* NUMA tuning
* PCIe tuning

== Getting the ISO ==
Please contact our [mailto:sales@telcobridges.com sales team] to get a copy of the latest TBSC-SW ISO.

== Installing the ISO ==
The installation process will reformat the server's disks and install all the necessary software.

=== Installing using the ISO burned onto a bootable USB flash drive ===
Use a software application to burn the ISO onto a USB flash drive. On Windows, [[https://rufus.akeo.ie/ |Rufus ]] is known to work with the TSBC-SW ISO.
But generally any similar application should work. Make sure to set the volume label to "CENTOS 7 X8" and to format the drive in the FAT32 file system format.

=== Physical installation steps ===
# Identify which Ethernet networks you need and connect them to your server. Refer to [[TSBC-SW:Networking]] for more information
# Burn the ISO onto a DVD or a USB flash drive
# Get an access to the console of the server. Usually, this is achieved by connecting a keyboard and screen to the server.
# Insert the DVD in the optical drive of your server and boot from the DVD drive.
#* Alternatively, plug in your USB flash drive and boot from that drive.
# You should get the to the "Virtual Appliance Installer" menu on your display: [[File:ISO_install_prompt.jpg|350px]]
# Hit 'R' key, then 'ENTER' key to start the installation [[File:ISO_installing.jpg|350px]]
# Wait for the installation process to complete. When installation is complete, the server will reboot itself.
#* Important: Make sure to remove the DVD from the drive while the server is rebooting. If you get back to "Virtual Appliance Installer", just eject the CD or remove the USB flash drive and reboot again.
# It may take a couple of minutes for the system to be brought up after the first reboot. Until the WebPortal is accessible, you must '''not''' reboot the newly created machine to allow the installation to complete properly.

=== Changing the root password ===
# Use the console to login into the server
## user: root
## password: root
# Change the password to something stronger than root:
# passwd
New password: ........
Retype new password: ........
passwd: all authentication tokens updated successfully.

=== 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 there is no IP assigned, you will need to configure one manually.

# Assign a IP address to the Ethernet interface having network connectivity. Example if the NIC's name would be eth0:
# ip link set eth0 up
# ip addresss add 192.168.178.30/24 dev eth0

=== Accessing the TSBC-SW web portal ===
# Open a web browser to the IP of your server, 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 TSBC Configuration Wizard [[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:Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for baremetal server optimizations:
[[TSBC-SW:Baremetal:Optimizations]]

File:Vmware ip.png

2017-08-18T21:41:35Z

Cboulanger:

FreeSBC:Cloud:VmWare Installation A

2017-08-18T21:40:41Z

Cboulanger: Added VMXNET3 interfaces

{{DISPLAYTITLE:TSBC-SW:Cloud:VmWare Installation}}
== Requirements ==
Minimal Cloud requirements:
* Vmware ESX 5 or 6
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* E1000 NIC emulation or VMXNET3 interfaces
* One Ethernet adapter for management
* One or more Ethernet adapter(s) for data

For better performance (see [[TSBC-SW:Cloud:VmWare_Optimizations|optimization]] section)
* 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'

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on VmWare cloud ==

=== TBSC 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 TSBC image into your VmWare before you can launch a virtual machine instance running the TSBC software.

==== Launching an instance ====

#Log in using the Vmware infrastructure client interface
#Select File->Deploy OVF Template... from the menu [[File:vmware_upload.png|400px]]
#Browse to the location of the TSBC-SW image obtained from TelcoBridges [[File:vmware_ovf_location.png|400px]]
# Click 'Next' until you need to name the new virtual machine instance. Enter the name and click 'Next' [[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' [[File:vmware_disk.png|400px]]
# Accept all other default settings and wait until the machine is deployed. [[File:vmware_installing.png|200px]]
# Once deployed, right-click on the new instance and select "Edit Settings..." [[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. [[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. [[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. [[File:vmware_mem.png|400px]]
# Select the 'Disk' item and set the 'Shares' to 'High'. Do '''not''' press the 'OK' button yet. [[File:vmware_disk_res.png|400px]]
# Select the 'Advanced CPU' item and set the 'Mode' to 'None'. Do '''not''' press the 'OK' button yet. [[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. [[File:vmware_poweron.png|400px]]
# Again to the main screen, select the newly instantiated virtual machine and choose the 'Summary' tab. Once the virtual machine is completed booted, the assigned DHCP IP address will be displayed by clicking on the 'View all' button. Note this IP address to access the Web Portal configuration interface later. [[File:vmware_ip.png|400px]]

=== Accessing the TSBC-SW ===

==== Accessing the TSBC-SW web portal ====
# Open a web browser to the management IP of the TSBC, on port 12358. Example if your server address is 10.0.0.79, the URL would be: http://10.0.0.79:12358
# You should get to the TSBC Configuration Wizard [[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.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for VmWare optimizations:
[[TSBC-SW:Cloud:VmWare_Optimizations]]

FreeSBC:Cloud:VmWare Installation A

2017-08-18T21:39:48Z

Cboulanger: Added the method to get the IP address

{{DISPLAYTITLE:TSBC-SW:Cloud:VmWare Installation}}
== Requirements ==
Minimal Cloud requirements:
* Vmware ESX 5 or 6
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* E1000 NIC emulation interfaces
* One Ethernet adapter for management
* One or more Ethernet adapter(s) for data

For better performance (see [[TSBC-SW:Cloud:VmWare_Optimizations|optimization]] section)
* 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'

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on VmWare cloud ==

=== TBSC 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 TSBC image into your VmWare before you can launch a virtual machine instance running the TSBC software.

==== Launching an instance ====

#Log in using the Vmware infrastructure client interface
#Select File->Deploy OVF Template... from the menu [[File:vmware_upload.png|400px]]
#Browse to the location of the TSBC-SW image obtained from TelcoBridges [[File:vmware_ovf_location.png|400px]]
# Click 'Next' until you need to name the new virtual machine instance. Enter the name and click 'Next' [[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' [[File:vmware_disk.png|400px]]
# Accept all other default settings and wait until the machine is deployed. [[File:vmware_installing.png|200px]]
# Once deployed, right-click on the new instance and select "Edit Settings..." [[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. [[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. [[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. [[File:vmware_mem.png|400px]]
# Select the 'Disk' item and set the 'Shares' to 'High'. Do '''not''' press the 'OK' button yet. [[File:vmware_disk_res.png|400px]]
# Select the 'Advanced CPU' item and set the 'Mode' to 'None'. Do '''not''' press the 'OK' button yet. [[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. [[File:vmware_poweron.png|400px]]
# Again to the main screen, select the newly instantiated virtual machine and choose the 'Summary' tab. Once the virtual machine is completed booted, the assigned DHCP IP address will be displayed by clicking on the 'View all' button. Note this IP address to access the Web Portal configuration interface later. [[File:vmware_ip.png|400px]]

=== Accessing the TSBC-SW ===

==== Accessing the TSBC-SW web portal ====
# Open a web browser to the management IP of the TSBC, on port 12358. Example if your server address is 10.0.0.79, the URL would be: http://10.0.0.79:12358
# You should get to the TSBC Configuration Wizard [[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.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for VmWare optimizations:
[[TSBC-SW:Cloud:VmWare_Optimizations]]

FreeSBC:Cloud:VmWare Installation A

2017-08-18T21:34:05Z

Cboulanger: Wrong image size!

{{DISPLAYTITLE:TSBC-SW:Cloud:VmWare Installation}}
== Requirements ==
Minimal Cloud requirements:
* Vmware ESX 5 or 6
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* E1000 NIC emulation interfaces
* One Ethernet adapter for management
* One or more Ethernet adapter(s) for data

For better performance (see [[TSBC-SW:Cloud:VmWare_Optimizations|optimization]] section)
* 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'

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on VmWare cloud ==

=== TBSC 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 TSBC image into your VmWare before you can launch a virtual machine instance running the TSBC software.

==== Launching an instance ====

#Log in using the Vmware infrastructure client interface
#Select File->Deploy OVF Template... from the menu [[File:vmware_upload.png|400px]]
#Browse to the location of the TSBC-SW image obtained from TelcoBridges [[File:vmware_ovf_location.png|400px]]
# Click 'Next' until you need to name the new virtual machine instance. Enter the name and click 'Next' [[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' [[File:vmware_disk.png|400px]]
# Accept all other default settings and wait until the machine is deployed. [[File:vmware_installing.png|200px]]
# Once deployed, right-click on the new instance and select "Edit Settings..." [[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. [[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. [[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. [[File:vmware_mem.png|400px]]
# Select the 'Disk' item and set the 'Shares' to 'High'. Do '''not''' press the 'OK' button yet. [[File:vmware_disk_res.png|400px]]
# Select the 'Advanced CPU' item and set the 'Mode' to 'None'. Do '''not''' press the 'OK' button yet. [[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. [[File:vmware_poweron.png|400px]]

=== Accessing the TSBC-SW ===

==== Accessing the TSBC-SW web portal ====
# 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: http://192.168.178.30:12358
# You should get to the TSBC Configuration Wizard [[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.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for VmWare optimizations:
[[TSBC-SW:Cloud:VmWare_Optimizations]]

FreeSBC:Cloud:VmWare Installation A

2017-08-18T21:32:57Z

Cboulanger: Writing installation procedure

{{DISPLAYTITLE:TSBC-SW:Cloud:VmWare Installation}}
== Requirements ==
Minimal Cloud requirements:
* Vmware ESX 5 or 6
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* E1000 NIC emulation interfaces
* One Ethernet adapter for management
* One or more Ethernet adapter(s) for data

For better performance (see [[TSBC-SW:Cloud:VmWare_Optimizations|optimization]] section)
* 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'

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on VmWare cloud ==

=== TBSC 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 TSBC image into your VmWare before you can launch a virtual machine instance running the TSBC software.

==== Launching an instance ====

#Log in using the Vmware infrastructure client interface
#Select File->Deploy OVF Template... from the menu [[File:vmware_upload.png|400px]]
#Browse to the location of the TSBC-SW image obtained from TelcoBridges [[File:vmware_ovf_location.png|400px]]
# Click 'Next' until you need to name the new virtual machine instance. Enter the name and click 'Next' [[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' [[File:vmware_disk.png|400px]]
# Accept all other default settings and wait until the machine is deployed. [[File:vmware_installing.png|200px]]
# Once deployed, right-click on the new instance and select "Edit Settings..." [[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. [[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. [[File:vmware_cpu.png|5400px]]
# Select the 'Memory' item and check-mark the 'Reserve all guest memory (All locked)' option. Do '''not''' press the 'OK' button yet. [[File:vmware_mem.png|400px]]
# Select the 'Disk' item and set the 'Shares' to 'High'. Do '''not''' press the 'OK' button yet. [[File:vmware_disk_res.png|400px]]
# Select the 'Advanced CPU' item and set the 'Mode' to 'None'. Do '''not''' press the 'OK' button yet. [[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. [[File:vmware_poweron.png|400px]]

=== Accessing the TSBC-SW ===

==== Accessing the TSBC-SW web portal ====
# 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: http://192.168.178.30:12358
# You should get to the TSBC Configuration Wizard [[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.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for VmWare optimizations:
[[TSBC-SW:Cloud:VmWare_Optimizations]]

File:Vmware poweron.png

2017-08-18T21:31:39Z

Cboulanger:

File:Vmware adv cpu.png

2017-08-18T21:29:20Z

Cboulanger:

File:Vmware disk res.png

2017-08-18T21:27:28Z

Cboulanger:

File:Vmware mem.png

2017-08-18T21:25:38Z

Cboulanger:

File:Vmware cpu.png

2017-08-18T21:22:56Z

Cboulanger:

File:Vmware network.png

2017-08-18T21:21:41Z

Cboulanger:

File:Vmware settings.png

2017-08-18T21:18:06Z

Cboulanger:

File:Vmware installing.png

2017-08-18T21:08:53Z

Cboulanger:

File:Vmware disk.png

2017-08-18T21:04:52Z

Cboulanger:

File:Vmware name.png

2017-08-18T21:03:07Z

Cboulanger:

File:Vmware ovf location.png

2017-08-18T20:59:32Z

Cboulanger:

File:Vmware upload.png

2017-08-18T20:57:06Z

Cboulanger: uploaded a new version of "File:Vmware upload.png"

File:Vmware upload.png

2017-08-18T20:54:13Z

Cboulanger:

Product Installation

2017-08-18T20:47:53Z

Cboulanger: Added vmware

The following is a list of product installation manuals:
__NOTOC__

==''T''sbc==

===TSBC-SW===
<section begin=TSBC-SW-INSTALLATION/>
*[[TSBC-SW:Baremetal:Installation_A|Baremetal installation instructions]]
*[[TSBC-SW:Cloud:OpenStack_Installation_A|OpenStack installation instructions]]
*[[TSBC-SW:Cloud:VmWare_Installation_A|VmWare installation instructions]]
<section end=TSBC-SW-INSTALLATION/>
*[[Media:tsbc-hw-srv_Installation_Guide_Issue1.0.pdf|TSBC-SW-SRV-HIGH/MID System Installation Guide]]
*[[TSBC-SW:Cloud:AWS_Installation_A|AWS installation instructions]]

===TSBC5000===
*[[Media:tsbc5000_Installation_Guide_Issue1.0.pdf|TSBC5000 System Installation Guide]]

==''T''media==

===TMG800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TMG800 Standalone & TMG800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TMG800 Standalone & TMG800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TMG3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TMG3200 Standalone & TMG3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TMG3200 Standalone & TMG3200 1+1 System Installation Guide]] (For 2U units)

=== TMG7800 ===
*[[Media:TMG7800_Installation_Guide_Issue3.0.pdf|TMG7800 Installation Guide]]
*[[Media:TMG7800_Installation_Guide_Issue1.0.pdf|TMG7800 Installation Guide]] (For 2U units)

==''T''sig==

===TSG800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TSG800 Standalone & TSG800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TSG800 Standalone & TSG800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TSG3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TSG3200 Standalone & TSG3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TSG3200 Standalone & TSG3200 1+1 System Installation Guide]] (For 2U units)

==''T''trans==
===TMGIP800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TMGIP800 Standalone & TMGIP800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TMGIP800 Standalone & TMGIP800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TMGIP3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TMGIP3200 Standalone & TMGIP3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TMGIP3200 Standalone & TMGIP3200 1+1 System Installation Guide]] (For 2U units)

===TMGIP7800===
*[[Media:TMG7800_Installation_Guide_Issue3.0.pdf|TMGIP7800 Installation Guide]]
*[[Media:TMG7800_Installation_Guide_Issue1.0.pdf|TMGIP7800 Installation Guide]] (For 2U units)

==''T''dev==
===TMP800===
*[[Media:TMP800_Installation_Guide_Issue2.0.pdf|TMP800 Installation guide]]

===TMP6400===
*[[Media:TMP6400_Installation_Guide_Issue3.pdf|TMP6400 System Installation guide]]

==''T''monitor==
===TM1000===
*[[Media:TM1000 Installation guide.pdf|TM1000 Installation Guide]]

===TM3000===
*[[Media:TM3000_Installation_Guide_v1.pdf|TM3000 Installation Guide]]

[[Category:Gateway_OAM&P|Product Installation]]
[[Category:Revise on Major]]

FreeSBC:Download

2017-08-18T20:44:41Z

Cboulanger: /* Vmware image download */

=== Bare metal image download ===
* https://licenses.telcobridges.com/download/tsbc_sw?name=BareMetal

=== OpenStack image download ===
* https://licenses.telcobridges.com/download/tsbc_sw?name=OpenStack

=== KVM image download ===
* https://licenses.telcobridges.com/download/tsbc_sw?name=KVM

=== VmWare image download ===
* https://licenses.telcobridges.com/download/tsbc_sw?name=Vmware

FreeSBC:Cloud:VmWare Installation A

2017-08-18T20:41:58Z

Cboulanger: Empty shell creation

TMG7800

2017-08-10T19:28:55Z

Cboulanger: Reversed two lines

[[Image:7800_straight_front.png|thumb|350px| Front view of a TMG7800 VoIP gateway cluster]]

[[Image:Imb_x3250_straight_front.png|thumb|350px| Front view of TMG7800-CTRL VoIP gateway controller]]
[[Image:Imb_x3250_straight_back.png|thumb|350px| Front view of TMG7800-CTRL VoIP gateway controller]]
The TMG7800 VoIP gateway meets your system requirements by providing you with up to 131,072 universal voice ports (32,768 per cluster) and a flexibility to switch between TDM and IP. This capability is enhanced by being able to support a vast selection of signaling protocols, such as SS7, ISDN PRI, SIGTRAN, SIP, SIP-I/SIP-T and H.248, as well as a wide range of media processing codecs across a mix of T1/E1, DS3 and OC3/STM-1 interfaces, all within the same system.
 

The TelcoBridges Tmedia TMG7800 high availability system says it all. This multi-unit VoIP gateway is scalable and 100% redundant ensuring an infallible carrier-grade network. Leveraging redundant integrated VoIP gateway controllers, the TMG7800 delivers core network applications such as VoIP gateway, TDM switching, VoIP hairpinning with [[transcoding]], with advanced [[call routing]] and fax over IP. The TMG7800 can also host additional third-party applications such as softswitches and session border controllers locally, further answering the need for device consolidation and convergence. With separate chipsets for media processing and separate processors for call routing and signaling, the TMG7800 VoIP gateway provides full low-latency non-blocking capability for up to 32,768 channels per cluster. Up to 4 clusters can be included within a single TMG7800 system creating a 131,072 channels non-blocking switch. 

The TMG7800 VoIP gateway provides the ultimate in flexibility, easily scaling to a fully configured capacity of 1024 T1/E1, 48 DS3 or 16 OC3/STM-1 interfaces per cluster as service uptake increases, with the ability to mix and match different interface types.

A TMG7800 system consists of four (4) distinct hardware devices:

*TMG7800-CTRL: This is the system's controller. It performs call handling, call routing, CDR collection, and system configuration management. The TMG7800-CTRL also presents the system's Web Portal for OAM&P. The TMG7800-CTRL supports redundnacy.
*TMG7800-TE or -DS3 or -STM1: These are the gateway units that form the TMG7800 system. These gateway units provide the T1, E1, DS3 and/or OC3/STM-1 links and VoIP port capacity required to deliver the desired voice channel capacity. The TMG7800 gateway units are controlled by the TMG7800-CTRL controllers.
*TMG7800-TMS: This device is optional. The TMG7800-TMS is a non-blocking media switch that enables port to port switching between the TMG7800 gateway units of the same cluster. The TMG7800-TMS uses an any-to-any TDM switching fabric to minimize delay and maximize voice quality (unlike other technologies that use a packet technology that introduces delay). The TMG7800-TMS can switch a call terminating on any TMG7800 gateway unit to any other TMG7800 gateway unit of the cluster. This is particularly useful when the TMG7800 system needs to provide TDM switching services. The TMG7800-TMS also supports redundancy.

=== Characteristics ===

*3 to 22U VoIP gateway per cluster
*256 to 32,768 VoIP channels per cluster
*16 to 1024 T1/E1 or 1 to 48 DS3 or 1 to 16 OC3/STM1 per cluster
*Up to 4 clusters within a single system
*Redundant AC or DC power supplies

=== Available configurations ===

*TMG7800-CTRL, (VoIP server)
*TMG7800-TE16, (16 x T1/E1, 512 x VoIP)
*TMG7800-TE32, (32 x T1/E1, 1024 x VoIP)
*TMG7800-TE48, (48 x T1/E1, 1536 x VoIP)
*TMG7800-TE64, (64 x T1/E1, 2048 x VoIP)
*TMG7800-DS31, (1 x DS3, 672 x VoIP)
*TMG7800-DS32, (2 x DS3, 1344 x VoIP)
*TMG7800-DS33, (3 x DS3, 2016 x VoIP)
*TMG7800-STM1, (1 x STM1, 2048 x VoIP)
*TMG7800-TMS, (media switching fabric)
 
Each configuration is available with redundant AC or DC power.
 
 
See [http://www.telcobridges.com/en/tmg7800.aspx TMG7800 web site] to learn more about this product.

== References ==
*[[Datasheet|TMG7800 Datasheet]]
*[[Gateway_Installation#Tmedia|TMG7800 Installation Guide]]
*[[Regulatory compliance]]

[[category:Hardware]]

TMG7800

2017-08-10T19:17:10Z

Cboulanger: Change title of the picture

[[Image:7800_straight_front.png|thumb|350px| Front view of a TMG7800 VoIP gateway cluster]]

[[Image:Imb_x3250_straight_front.png|thumb|350px| Front view of TMG7800-CTRL VoIP gateway controller]]
[[Image:Imb_x3250_straight_back.png|thumb|350px| Front view of TMG7800-CTRL VoIP gateway controller]]
The TMG7800 VoIP gateway meets your system requirements by providing you with up to 131,072 universal voice ports (32,768 per cluster) and a flexibility to switch between TDM and IP. This capability is enhanced by being able to support a vast selection of signaling protocols, such as SS7, ISDN PRI, SIGTRAN, SIP, SIP-I/SIP-T and H.248, as well as a wide range of media processing codecs across a mix of T1/E1, DS3 and OC3/STM-1 interfaces, all within the same system.
 

The TelcoBridges Tmedia TMG7800 high availability system says it all. This multi-unit VoIP gateway is scalable and 100% redundant ensuring an infallible carrier-grade network. Leveraging redundant integrated VoIP gateway controllers, the TMG7800 delivers core network applications such as VoIP gateway, TDM switching, VoIP hairpinning with [[transcoding]], with advanced [[call routing]] and fax over IP. The TMG7800 can also host additional third-party applications such as softswitches and session border controllers locally, further answering the need for device consolidation and convergence. With separate chipsets for media processing and separate processors for call routing and signaling, the TMG7800 VoIP gateway provides full low-latency non-blocking capability for up to 32,768 channels per cluster. Up to 4 clusters can be included within a single TMG7800 system creating a 131,072 channels non-blocking switch. 

The TMG7800 VoIP gateway provides the ultimate in flexibility, easily scaling to a fully configured capacity of 1024 T1/E1, 48 DS3 or 16 OC3/STM-1 interfaces per cluster as service uptake increases, with the ability to mix and match different interface types.

A TMG7800 system consists of four (4) distinct hardware devices:

*TMG7800-CTRL: This is the system's controller. It performs call handling, call routing, CDR collection, and system configuration management. The TMG7800-CTRL also presents the system's Web Portal for OAM&P. The TMG7800-CTRL supports redundnacy.
*TMG7800-TE or -DS3 or -STM1: These are the gateway units that form the TMG7800 system. These gateway units provide the T1, E1, DS3 and/or OC3/STM-1 links and VoIP port capacity required to deliver the desired voice channel capacity. The TMG7800 gateway units are controlled by the TMG7800-CTRL controllers.
*TMG7800-TMS: This device is optional. The TMG7800-TMS is a non-blocking media switch that enables port to port switching between the TMG7800 gateway units of the same cluster. The TMG7800-TMS uses an any-to-any TDM switching fabric to minimize delay and maximize voice quality (unlike other technologies that use a packet technology that introduces delay). The TMG7800-TMS can switch a call terminating on any TMG7800 gateway unit to any other TMG7800 gateway unit of the cluster. This is particularly useful when the TMG7800 system needs to provide TDM switching services. The TMG7800-TMS also supports redundancy.

=== Characteristics ===

*3 to 22U VoIP gateway per cluster
*256 to 32,768 VoIP channels per cluster
*16 to 1024 T1/E1 or 1 to 48 DS3 or 1 to 16 OC3/STM1 per cluster
*Redundant AC or DC power supplies
*Up to 4 clusters within a single system

=== Available configurations ===

*TMG7800-CTRL, (VoIP server)
*TMG7800-TE16, (16 x T1/E1, 512 x VoIP)
*TMG7800-TE32, (32 x T1/E1, 1024 x VoIP)
*TMG7800-TE48, (48 x T1/E1, 1536 x VoIP)
*TMG7800-TE64, (64 x T1/E1, 2048 x VoIP)
*TMG7800-DS31, (1 x DS3, 672 x VoIP)
*TMG7800-DS32, (2 x DS3, 1344 x VoIP)
*TMG7800-DS33, (3 x DS3, 2016 x VoIP)
*TMG7800-STM1, (1 x STM1, 2048 x VoIP)
*TMG7800-TMS, (media switching fabric)
 
Each configuration is available with redundant AC or DC power.
 
 
See [http://www.telcobridges.com/en/tmg7800.aspx TMG7800 web site] to learn more about this product.

== References ==
*[[Datasheet|TMG7800 Datasheet]]
*[[Gateway_Installation#Tmedia|TMG7800 Installation Guide]]
*[[Regulatory compliance]]

[[category:Hardware]]

TMG7800

2017-08-10T19:15:59Z

Cboulanger: Modified to add clusters

[[Image:7800_straight_front.png|thumb|350px| Front view of TMG7800 VoIP gateway]]

[[Image:Imb_x3250_straight_front.png|thumb|350px| Front view of TMG7800-CTRL VoIP gateway controller]]
[[Image:Imb_x3250_straight_back.png|thumb|350px| Front view of TMG7800-CTRL VoIP gateway controller]]
The TMG7800 VoIP gateway meets your system requirements by providing you with up to 131,072 universal voice ports (32,768 per cluster) and a flexibility to switch between TDM and IP. This capability is enhanced by being able to support a vast selection of signaling protocols, such as SS7, ISDN PRI, SIGTRAN, SIP, SIP-I/SIP-T and H.248, as well as a wide range of media processing codecs across a mix of T1/E1, DS3 and OC3/STM-1 interfaces, all within the same system.
 

The TelcoBridges Tmedia TMG7800 high availability system says it all. This multi-unit VoIP gateway is scalable and 100% redundant ensuring an infallible carrier-grade network. Leveraging redundant integrated VoIP gateway controllers, the TMG7800 delivers core network applications such as VoIP gateway, TDM switching, VoIP hairpinning with [[transcoding]], with advanced [[call routing]] and fax over IP. The TMG7800 can also host additional third-party applications such as softswitches and session border controllers locally, further answering the need for device consolidation and convergence. With separate chipsets for media processing and separate processors for call routing and signaling, the TMG7800 VoIP gateway provides full low-latency non-blocking capability for up to 32,768 channels per cluster. Up to 4 clusters can be included within a single TMG7800 system creating a 131,072 channels non-blocking switch. 

The TMG7800 VoIP gateway provides the ultimate in flexibility, easily scaling to a fully configured capacity of 1024 T1/E1, 48 DS3 or 16 OC3/STM-1 interfaces per cluster as service uptake increases, with the ability to mix and match different interface types.

A TMG7800 system consists of four (4) distinct hardware devices:

*TMG7800-CTRL: This is the system's controller. It performs call handling, call routing, CDR collection, and system configuration management. The TMG7800-CTRL also presents the system's Web Portal for OAM&P. The TMG7800-CTRL supports redundnacy.
*TMG7800-TE or -DS3 or -STM1: These are the gateway units that form the TMG7800 system. These gateway units provide the T1, E1, DS3 and/or OC3/STM-1 links and VoIP port capacity required to deliver the desired voice channel capacity. The TMG7800 gateway units are controlled by the TMG7800-CTRL controllers.
*TMG7800-TMS: This device is optional. The TMG7800-TMS is a non-blocking media switch that enables port to port switching between the TMG7800 gateway units of the same cluster. The TMG7800-TMS uses an any-to-any TDM switching fabric to minimize delay and maximize voice quality (unlike other technologies that use a packet technology that introduces delay). The TMG7800-TMS can switch a call terminating on any TMG7800 gateway unit to any other TMG7800 gateway unit of the cluster. This is particularly useful when the TMG7800 system needs to provide TDM switching services. The TMG7800-TMS also supports redundancy.

=== Characteristics ===

*3 to 22U VoIP gateway per cluster
*256 to 32,768 VoIP channels per cluster
*16 to 1024 T1/E1 or 1 to 48 DS3 or 1 to 16 OC3/STM1 per cluster
*Redundant AC or DC power supplies
*Up to 4 clusters within a single system

=== Available configurations ===

*TMG7800-CTRL, (VoIP server)
*TMG7800-TE16, (16 x T1/E1, 512 x VoIP)
*TMG7800-TE32, (32 x T1/E1, 1024 x VoIP)
*TMG7800-TE48, (48 x T1/E1, 1536 x VoIP)
*TMG7800-TE64, (64 x T1/E1, 2048 x VoIP)
*TMG7800-DS31, (1 x DS3, 672 x VoIP)
*TMG7800-DS32, (2 x DS3, 1344 x VoIP)
*TMG7800-DS33, (3 x DS3, 2016 x VoIP)
*TMG7800-STM1, (1 x STM1, 2048 x VoIP)
*TMG7800-TMS, (media switching fabric)
 
Each configuration is available with redundant AC or DC power.
 
 
See [http://www.telcobridges.com/en/tmg7800.aspx TMG7800 web site] to learn more about this product.

== References ==
*[[Datasheet|TMG7800 Datasheet]]
*[[Gateway_Installation#Tmedia|TMG7800 Installation Guide]]
*[[Regulatory compliance]]

[[category:Hardware]]

File:TMG7800.pdf

2017-08-10T19:11:25Z

Cboulanger: uploaded a new version of "File:TMG7800.pdf": TMG7800 Datasheet

New 2012 TMG7800 data sheet

FreeSBC:Cloud:OpenStack Installation A

2017-08-07T19:19:59Z

Cboulanger: differenciate between management port and data port

{{DISPLAYTITLE:TSBC-SW:Cloud:OpenStack Installation}}
== Requirements ==
Minimal Cloud requirements:
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* Virtio NIC interface
* qemu-kvm CPU exposed as 'host' or minimally 'core2duo'
* One Ethernet adapter for management
* One or more Ethernet adapter(s) for data

For better performance (see [[TSBC-SW:Cloud:OpenStack_Optimizations|optimization]] section)
* SR-IOV or MacVTap compatible NICs
* Overcommit set to 1:1
* No CPU (including hyperthreading) shared between infrastructure and compute section
* Dedicated memory allocation to VM

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on OpenStack cloud ==

=== TSBC OpenStack Minimal Flavor ===
In OpenStack, a flavor defines the compute, memory, and storage capacity of a virtual server, also known as an instance. If you do not already have a flavor that meets the listed minimal requirements, you will have to create a new one.

==== Creating a Flavor ====
#Log in to the Dashboard and select the '''admin''' project from the drop-down list.
#In the '''Admin''' tab, open the '''System''' tab and click the '''Flavors''' category.
#Click '''Create Flavor'''.
#In the '''Create Flavor''' window, enter or select the parameters for the flavor in the '''Flavor Information''' tab.
#* '''Name''' : ''TelcoBridges TSBC Flavor''
#* '''VCPUs''' : ''4''
#* '''RAM (MB)''' : ''8192''
#* '''Root Disk (GB)''' : ''20''
#* Other fields are left to their default value [[File:OpenStackMinimalFlavorCreate.png|500px]]
#In the '''Flavor Access''' tab, you can control access to the flavor by moving projects from the '''All Projects''' column to the '''Selected Projects''' column. Only projects in the '''Selected Projects''' column can use the flavor. If there are no projects in the right column, all projects can use the flavor.
#Click '''Create Flavor'''.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-flavors.html
*https://docs.openstack.org/admin-guide/compute-flavors.html

=== TBSC OpenStack 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 TSBC image into your OpenStack before you can launch a virtual machine instance running the TSBC software.

==== Upload an Image ====
Follow this procedure to upload an image to a project:
#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Images category.
#Click Create Image.
#The Create An Image dialog box appears.
#Enter the following values:
#*'''Image Name''' : ''TelcoBridges TSBC xx.yy.zz'' (Where xxx.yy.zz is changed to the version number of the TSBC image)
#*'''Image Description''': ''TelcoBridges TSBC version xx.yy.zz''
#*'''Image Source''' :''File''.
#*'''Image File''' : Browse for the image file on your file system and add it.
#*'''Format''': ''QCOW2''
#*'''Architecture''': ''x86_64''
#*'''Minimum Disk (GB)''' : ''20''
#*'''Minimum RAM (MB)''': ''8192''
#*'''Visibility''' : The access permission for the image. ''Public'' or ''Private'', depending on your needs.
#*'''Protected''': Select this check box to ensure that only users with permissions can delete the image. ''Yes'' or ''No''. [[File:OpenStackImageUpload.png|500px]]
#Image Metadata : Leave empty.
#Click Create Image. The image is queued to be uploaded. It might take some time before the status changes from Queued to Active.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-images.html

=== TSBC OpenStack Instance ===
Instances are virtual machines that run inside OpenStack's cloud. You will need to launch a new instance from the TSBC Image created in the [[#Upload an Image]] section

==== Launching an instance ====

#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Instances category.
#The dashboard shows the instances with its name, its private and floating IP addresses, size, status, task, power state, and so on.
#Click Launch Instance.
#In the Launch Instance dialog box, specify the following values:
##<big>Details tab</big>
##*'''Instance Name''' : Assign a name to the virtual machine. For example: ''TelcoBridges TSBC''.
##*'''Availability Zone''' : By default, this value is set to the availability zone given by the cloud provider (for example, us-west or apac-south). For some cases, it could be nova.
##*'''Count''' : ''1'' [[File:OpenStackLaunchInstanceDetailsTab.png|500px]]
##<big>Source tab</big>
##*'''Instance Boot Source''' : ''Boot from image''.
##*'''Create new Volume''' : ''No''
##*'''Select Image Name''' : Select ''TelcoBridges TSBC xx.yy.zz'' as created in [[#Upload an Image]] section. [[File:OpenStackLaunchInstanceSourceTab.png|500px]]
##<big>Flavor tab</big>
##*'''Flavor''' : Select ''TelcoBridges TSBC Flavor'' as created in [[#Creating a Flavor]] section. [[File:OpenStackLaunchInstanceFlavorTab.png|500px]]
##<big>Networks tab</big>
##*'''Selected Networks''': If you are installing a '''standalone''' SBC, the TSBC will need access to ''WAN'' and ''MGMT'' networks. For transcoding on TSBC-TRANS, or HA pair installation, the TSBC will also need access to ''CTRL0'', ''CTRL1'' and ''TRANS0'' networks. Please refer to [[TSBC-SW:Networking]] for details on network requirements. '''Important''': For optimal performance, it is recommended to use SR-IOV or MacVTap ports to access ''LAN'' and ''WAN'' networks, see [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkTab.png|500px]]
##<big>Network Ports tab</big>
##*'''Ports''' : For optimal performances, SR-IOV and MacVTap ports should be used to access ''LAN'' and ''WAN'' networks. If you do choose to use Network Ports to attach to ''LAN'' and ''WAN'' networks, do not attach to them in ''Networks Tabs''. See [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkPortsTab.png|500px]]
##<big>Security Groups tab</big>
##*'''Security Groups''': Activate the security groups that you want to assign to the instance. Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. If you have not created any security groups, you can assign only the default security group to the instance. '''Warning''': ''Make sure the selected security group allows ingress traffic''. [[File:OpenStackLaunchInstanceSecurityGroupTab.png|500px]]
##<big>Key Pair tab</big>
##*'''Key Pair''' : SSH access to the TSBC with a password is disabled by default on the TSBC. You will need to provide your SSH public key here in order to get SSH access into the TSBC. [[File:OpenStackLaunchInstanceKeyPairTab.png|500px]]
#Click Launch Instance. The TSBC instance will starts on a compute node in your cloud. When the instance state is changed to Active, you will be able to the TSBC using SSH or a web browser as described in the next section..

==== References ====
*https://docs.openstack.org/user-guide/dashboard-launch-instances.html

=== Accessing the TSBC-SW ===
==== TSBC SSH Access ====
There is no root password by default, you will need to SSH onto the TSBC using SSH private key matching the public provided in the '''Key Pair tab''' when [[#Launching an instance|Launching]] the TSBC instance. Login using ''tbcloud'' as username.

For example, if you TSBC management IP is 192.168.178.30:
> ssh tbcloud@192.168.178.30
ECDSA key fingerprint is 5d:94:a1:93:0f:a4:7a:5d:41:cc:29:49:79:5a:58:f3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.178.30' (ECDSA) to the list of known hosts.

CentOS-7-x86_64-Minimal-1511/112/190195:197392, Fri 7 Apr 17:41:46 EDT 2017
[tbcloud@tsbc ~]$

==== Accessing the TSBC-SW web portal ====
# 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: http://192.168.178.30:12358
# You should get to the TSBC Configuration Wizard [[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:OpenStack_Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for OpenStack optimizations:
[[TSBC-SW:Cloud:OpenStack_Optimizations]]

FreeSBC:Baremetal:Installation A

2017-08-07T19:19:05Z

Cboulanger: Typo + differenciate between management port and data port

{{DISPLAYTITLE:TSBC-SW:Baremetal:Installation}}

== Requirements ==
Minimal server requirements:
* 64 bits server
* Quad core Intel CPU 2GHz
* Optical disk drive
* 80GB hard drive
* 8G RAM
* One management Ethernet
* Data Ethernet adapters
** 5,000 sessions or less: one 1Gbps interface
** 10,000 sessions or less: two 1Gbps interface
** 60,000 sessions: two 10Gbps interfaces
** See list of supported Network Interface Cards (NICs) here: [[Supported_NICs|List of supported NICs]]
* Console access through serial port or keyboard/monitor ports
* BIOS setup for maximum performance (i.e. no dynamic CPU throttling)

For better performance (see [[TSBC-SW:Baremetal:Optimizations|optimization]] section)
* NUMA tuning
* PCIe tuning

== Getting the ISO ==
Please contact our [mailto:sales@telcobridges.com sales team] to get a copy of the latest TBSC-SW ISO.

== Installing using the ISO ==
The ISO installation process will reformat the server's disks and install all the necessary software.

=== Physical installation steps ===
# Identify which Ethernet networks you need and connect them to your server. Refer to [[TSBC-SW:Networking]] for more information
# Burn the ISO onto a DVD
# Get an access to the console of the server. Usually, this is achieved by connecting a keyboard and screen to the server.
# Insert the DVD in the optical drive of your server and boot from the DVD drive.
# You should get the to the "Virtual Appliance Installer" menu on your display: [[File:ISO_install_prompt.jpg|350px]]
# Hit 'R' key, then 'ENTER' key to start the installation [[File:ISO_installing.jpg|350px]]
# Wait for the installation process to complete. When installation is complete, the server will reboot itself.
#* Important: Make sure to remove the DVD from the drive while the server is rebooting. If you get back to "Virtual Appliance Installer", just eject the CD and reboot again.

=== Changing the root password ===
# Use the console to login into the server
## user: root
## password: root
# Change the password to something stronger than root:
# passwd
New password: ........
Retype new password: ........
passwd: all authentication tokens updated successfully.

=== 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 there is no IP assigned, you will need to configure one manually.

# Assign a IP address to the Ethernet interface having network connectivity. Example if the NIC's name would be eth0:
# ip link set eth0 up
# ip addresss add 192.168.178.30/24 dev eth0

=== Accessing the TSBC-SW web portal ===
# Open a web browser to the IP of your server, 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 TSBC Configuration Wizard [[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:Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for baremetal server optimizations:
[[TSBC-SW:Baremetal:Optimizations]]

FreeSBC:Cloud:OpenStack Installation A

2017-06-28T15:24:24Z

Cboulanger: Added dedicated memory allocation

{{DISPLAYTITLE:TSBC-SW:Cloud:OpenStack Installation}}
== Requirements ==
Minimal Cloud requirements:
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* Virtio NIC interface
* qemu-kvm CPU exposed as 'host' or minimally 'core2duo'

For better performance (see [[TSBC-SW:Cloud:OpenStack_Optimizations|optimization]] section)
* SR-IOV or MacVTap compatible NICs
* Overcommit set to 1:1
* No CPU (including hyperthreading) shared between infrastructure and compute section
* Dedicated memory allocation to VM

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on OpenStack cloud ==

=== TSBC OpenStack Minimal Flavor ===
In OpenStack, a flavor defines the compute, memory, and storage capacity of a virtual server, also known as an instance. If you do not already have a flavor that meets the listed minimal requirements, you will have to create a new one.

==== Creating a Flavor ====
#Log in to the Dashboard and select the '''admin''' project from the drop-down list.
#In the '''Admin''' tab, open the '''System''' tab and click the '''Flavors''' category.
#Click '''Create Flavor'''.
#In the '''Create Flavor''' window, enter or select the parameters for the flavor in the '''Flavor Information''' tab.
#* '''Name''' : ''TelcoBridges TSBC Flavor''
#* '''VCPUs''' : ''4''
#* '''RAM (MB)''' : ''8192''
#* '''Root Disk (GB)''' : ''20''
#* Other fields are left to their default value [[File:OpenStackMinimalFlavorCreate.png|500px]]
#In the '''Flavor Access''' tab, you can control access to the flavor by moving projects from the '''All Projects''' column to the '''Selected Projects''' column. Only projects in the '''Selected Projects''' column can use the flavor. If there are no projects in the right column, all projects can use the flavor.
#Click '''Create Flavor'''.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-flavors.html
*https://docs.openstack.org/admin-guide/compute-flavors.html

=== TBSC OpenStack 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 TSBC image into your OpenStack before you can launch a virtual machine instance running the TSBC software.

==== Upload an Image ====
Follow this procedure to upload an image to a project:
#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Images category.
#Click Create Image.
#The Create An Image dialog box appears.
#Enter the following values:
#*'''Image Name''' : ''TelcoBridges TSBC xx.yy.zz'' (Where xxx.yy.zz is changed to the version number of the TSBC image)
#*'''Image Description''': ''TelcoBridges TSBC version xx.yy.zz''
#*'''Image Source''' :''File''.
#*'''Image File''' : Browse for the image file on your file system and add it.
#*'''Format''': ''QCOW2''
#*'''Architecture''': ''x86_64''
#*'''Minimum Disk (GB)''' : ''20''
#*'''Minimum RAM (MB)''': ''8192''
#*'''Visibility''' : The access permission for the image. ''Public'' or ''Private'', depending on your needs.
#*'''Protected''': Select this check box to ensure that only users with permissions can delete the image. ''Yes'' or ''No''. [[File:OpenStackImageUpload.png|500px]]
#Image Metadata : Leave empty.
#Click Create Image. The image is queued to be uploaded. It might take some time before the status changes from Queued to Active.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-images.html

=== TSBC OpenStack Instance ===
Instances are virtual machines that run inside OpenStack's cloud. You will need to launch a new instance from the TSBC Image created in the [[#Upload an Image]] section

==== Launching an instance ====

#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Instances category.
#The dashboard shows the instances with its name, its private and floating IP addresses, size, status, task, power state, and so on.
#Click Launch Instance.
#In the Launch Instance dialog box, specify the following values:
##<big>Details tab</big>
##*'''Instance Name''' : Assign a name to the virtual machine. For example: ''TelcoBridges TSBC''.
##*'''Availability Zone''' : By default, this value is set to the availability zone given by the cloud provider (for example, us-west or apac-south). For some cases, it could be nova.
##*'''Count''' : ''1'' [[File:OpenStackLaunchInstanceDetailsTab.png|500px]]
##<big>Source tab</big>
##*'''Instance Boot Source''' : ''Boot from image''.
##*'''Create new Volume''' : ''No''
##*'''Select Image Name''' : Select ''TelcoBridges TSBC xx.yy.zz'' as created in [[#Upload an Image]] section. [[File:OpenStackLaunchInstanceSourceTab.png|500px]]
##<big>Flavor tab</big>
##*'''Flavor''' : Select ''TelcoBridges TSBC Flavor'' as created in [[#Creating a Flavor]] section. [[File:OpenStackLaunchInstanceFlavorTab.png|500px]]
##<big>Networks tab</big>
##*'''Selected Networks''': If you are installing a '''standalone''' SBC, the TSBC will need access to ''WAN'' and ''MGMT'' networks. For transcoding on TSBC-TRANS, or HA pair installation, the TSBC will also need access to ''CTRL0'', ''CTRL1'' and ''TRANS0'' networks. Please refer to [[TSBC-SW:Networking]] for details on network requirements. '''Important''': For optimal performance, it is recommended to use SR-IOV or MacVTap ports to access ''LAN'' and ''WAN'' networks, see [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkTab.png|500px]]
##<big>Network Ports tab</big>
##*'''Ports''' : For optimal performances, SR-IOV and MacVTap ports should be used to access ''LAN'' and ''WAN'' networks. If you do choose to use Network Ports to attach to ''LAN'' and ''WAN'' networks, do not attach to them in ''Networks Tabs''. See [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkPortsTab.png|500px]]
##<big>Security Groups tab</big>
##*'''Security Groups''': Activate the security groups that you want to assign to the instance. Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. If you have not created any security groups, you can assign only the default security group to the instance. '''Warning''': ''Make sure the selected security group allows ingress traffic''. [[File:OpenStackLaunchInstanceSecurityGroupTab.png|500px]]
##<big>Key Pair tab</big>
##*'''Key Pair''' : SSH access to the TSBC with a password is disabled by default on the TSBC. You will need to provide your SSH public key here in order to get SSH access into the TSBC. [[File:OpenStackLaunchInstanceKeyPairTab.png|500px]]
#Click Launch Instance. The TSBC instance will starts on a compute node in your cloud. When the instance state is changed to Active, you will be able to the TSBC using SSH or a web browser as described in the next section..

==== References ====
*https://docs.openstack.org/user-guide/dashboard-launch-instances.html

=== Accessing the TSBC-SW ===
==== TSBC SSH Access ====
There is no root password by default, you will need to SSH onto the TSBC using SSH private key matching the public provided in the '''Key Pair tab''' when [[#Launching an instance|Launching]] the TSBC instance. Login using ''tbcloud'' as username.

For example, if you TSBC management IP is 192.168.178.30:
> ssh tbcloud@192.168.178.30
ECDSA key fingerprint is 5d:94:a1:93:0f:a4:7a:5d:41:cc:29:49:79:5a:58:f3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.178.30' (ECDSA) to the list of known hosts.

CentOS-7-x86_64-Minimal-1511/112/190195:197392, Fri 7 Apr 17:41:46 EDT 2017
[tbcloud@tsbc ~]$

==== Accessing the TSBC-SW web portal ====
# 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: http://192.168.178.30:12358
# You should get to the TSBC Configuration Wizard [[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:OpenStack_Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for OpenStack optimizations:
[[TSBC-SW:Cloud:OpenStack_Optimizations]]

FreeSBC:Cloud:OpenStack Installation A

2017-06-28T15:22:57Z

Cboulanger: Added minimal KVM CPU exposure

{{DISPLAYTITLE:TSBC-SW:Cloud:OpenStack Installation}}
== Requirements ==
Minimal Cloud requirements:
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* Virtio NIC interface
* qemu-kvm CPU exposed as 'host' or minimally 'core2duo'

For better performance (see [[TSBC-SW:Cloud:OpenStack_Optimizations|optimization]] section)
* SR-IOV or MacVTap compatible NICs
* Overcommit set to 1:1
* No CPU shared between infrastructure and compute section.

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on OpenStack cloud ==

=== TSBC OpenStack Minimal Flavor ===
In OpenStack, a flavor defines the compute, memory, and storage capacity of a virtual server, also known as an instance. If you do not already have a flavor that meets the listed minimal requirements, you will have to create a new one.

==== Creating a Flavor ====
#Log in to the Dashboard and select the '''admin''' project from the drop-down list.
#In the '''Admin''' tab, open the '''System''' tab and click the '''Flavors''' category.
#Click '''Create Flavor'''.
#In the '''Create Flavor''' window, enter or select the parameters for the flavor in the '''Flavor Information''' tab.
#* '''Name''' : ''TelcoBridges TSBC Flavor''
#* '''VCPUs''' : ''4''
#* '''RAM (MB)''' : ''8192''
#* '''Root Disk (GB)''' : ''20''
#* Other fields are left to their default value [[File:OpenStackMinimalFlavorCreate.png|500px]]
#In the '''Flavor Access''' tab, you can control access to the flavor by moving projects from the '''All Projects''' column to the '''Selected Projects''' column. Only projects in the '''Selected Projects''' column can use the flavor. If there are no projects in the right column, all projects can use the flavor.
#Click '''Create Flavor'''.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-flavors.html
*https://docs.openstack.org/admin-guide/compute-flavors.html

=== TBSC OpenStack 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 TSBC image into your OpenStack before you can launch a virtual machine instance running the TSBC software.

==== Upload an Image ====
Follow this procedure to upload an image to a project:
#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Images category.
#Click Create Image.
#The Create An Image dialog box appears.
#Enter the following values:
#*'''Image Name''' : ''TelcoBridges TSBC xx.yy.zz'' (Where xxx.yy.zz is changed to the version number of the TSBC image)
#*'''Image Description''': ''TelcoBridges TSBC version xx.yy.zz''
#*'''Image Source''' :''File''.
#*'''Image File''' : Browse for the image file on your file system and add it.
#*'''Format''': ''QCOW2''
#*'''Architecture''': ''x86_64''
#*'''Minimum Disk (GB)''' : ''20''
#*'''Minimum RAM (MB)''': ''8192''
#*'''Visibility''' : The access permission for the image. ''Public'' or ''Private'', depending on your needs.
#*'''Protected''': Select this check box to ensure that only users with permissions can delete the image. ''Yes'' or ''No''. [[File:OpenStackImageUpload.png|500px]]
#Image Metadata : Leave empty.
#Click Create Image. The image is queued to be uploaded. It might take some time before the status changes from Queued to Active.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-images.html

=== TSBC OpenStack Instance ===
Instances are virtual machines that run inside OpenStack's cloud. You will need to launch a new instance from the TSBC Image created in the [[#Upload an Image]] section

==== Launching an instance ====

#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Instances category.
#The dashboard shows the instances with its name, its private and floating IP addresses, size, status, task, power state, and so on.
#Click Launch Instance.
#In the Launch Instance dialog box, specify the following values:
##<big>Details tab</big>
##*'''Instance Name''' : Assign a name to the virtual machine. For example: ''TelcoBridges TSBC''.
##*'''Availability Zone''' : By default, this value is set to the availability zone given by the cloud provider (for example, us-west or apac-south). For some cases, it could be nova.
##*'''Count''' : ''1'' [[File:OpenStackLaunchInstanceDetailsTab.png|500px]]
##<big>Source tab</big>
##*'''Instance Boot Source''' : ''Boot from image''.
##*'''Create new Volume''' : ''No''
##*'''Select Image Name''' : Select ''TelcoBridges TSBC xx.yy.zz'' as created in [[#Upload an Image]] section. [[File:OpenStackLaunchInstanceSourceTab.png|500px]]
##<big>Flavor tab</big>
##*'''Flavor''' : Select ''TelcoBridges TSBC Flavor'' as created in [[#Creating a Flavor]] section. [[File:OpenStackLaunchInstanceFlavorTab.png|500px]]
##<big>Networks tab</big>
##*'''Selected Networks''': If you are installing a '''standalone''' SBC, the TSBC will need access to ''WAN'' and ''MGMT'' networks. For transcoding on TSBC-TRANS, or HA pair installation, the TSBC will also need access to ''CTRL0'', ''CTRL1'' and ''TRANS0'' networks. Please refer to [[TSBC-SW:Networking]] for details on network requirements. '''Important''': For optimal performance, it is recommended to use SR-IOV or MacVTap ports to access ''LAN'' and ''WAN'' networks, see [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkTab.png|500px]]
##<big>Network Ports tab</big>
##*'''Ports''' : For optimal performances, SR-IOV and MacVTap ports should be used to access ''LAN'' and ''WAN'' networks. If you do choose to use Network Ports to attach to ''LAN'' and ''WAN'' networks, do not attach to them in ''Networks Tabs''. See [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkPortsTab.png|500px]]
##<big>Security Groups tab</big>
##*'''Security Groups''': Activate the security groups that you want to assign to the instance. Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. If you have not created any security groups, you can assign only the default security group to the instance. '''Warning''': ''Make sure the selected security group allows ingress traffic''. [[File:OpenStackLaunchInstanceSecurityGroupTab.png|500px]]
##<big>Key Pair tab</big>
##*'''Key Pair''' : SSH access to the TSBC with a password is disabled by default on the TSBC. You will need to provide your SSH public key here in order to get SSH access into the TSBC. [[File:OpenStackLaunchInstanceKeyPairTab.png|500px]]
#Click Launch Instance. The TSBC instance will starts on a compute node in your cloud. When the instance state is changed to Active, you will be able to the TSBC using SSH or a web browser as described in the next section..

==== References ====
*https://docs.openstack.org/user-guide/dashboard-launch-instances.html

=== Accessing the TSBC-SW ===
==== TSBC SSH Access ====
There is no root password by default, you will need to SSH onto the TSBC using SSH private key matching the public provided in the '''Key Pair tab''' when [[#Launching an instance|Launching]] the TSBC instance. Login using ''tbcloud'' as username.

For example, if you TSBC management IP is 192.168.178.30:
> ssh tbcloud@192.168.178.30
ECDSA key fingerprint is 5d:94:a1:93:0f:a4:7a:5d:41:cc:29:49:79:5a:58:f3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.178.30' (ECDSA) to the list of known hosts.

CentOS-7-x86_64-Minimal-1511/112/190195:197392, Fri 7 Apr 17:41:46 EDT 2017
[tbcloud@tsbc ~]$

==== Accessing the TSBC-SW web portal ====
# 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: http://192.168.178.30:12358
# You should get to the TSBC Configuration Wizard [[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:OpenStack_Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for OpenStack optimizations:
[[TSBC-SW:Cloud:OpenStack_Optimizations]]

FreeSBC:Cloud:OpenStack Installation A

2017-06-26T18:06:10Z

Cboulanger: /* Requirements */

{{DISPLAYTITLE:TSBC-SW:Cloud:OpenStack Installation}}
== Requirements ==
Minimal Cloud requirements:
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* Virtio NIC interface

For better performance (see [[TSBC-SW:Cloud:OpenStack_Optimizations|optimization]] section)
* SR-IOV or MacVTap compatible NICs
* Overcommit set to 1:1
* No CPU shared between infrastructure and compute section.

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on OpenStack cloud ==

=== TSBC OpenStack Minimal Flavor ===
In OpenStack, a flavor defines the compute, memory, and storage capacity of a virtual server, also known as an instance. If you do not already have a flavor that meets the listed minimal requirements, you will have to create a new one.

==== Creating a Flavor ====
#Log in to the Dashboard and select the '''admin''' project from the drop-down list.
#In the '''Admin''' tab, open the '''System''' tab and click the '''Flavors''' category.
#Click '''Create Flavor'''.
#In the '''Create Flavor''' window, enter or select the parameters for the flavor in the '''Flavor Information''' tab.
#* '''Name''' : ''TelcoBridges TSBC Flavor''
#* '''VCPUs''' : ''4''
#* '''RAM (MB)''' : ''8192''
#* '''Root Disk (GB)''' : ''20''
#* Other fields are left to their default value [[File:OpenStackMinimalFlavorCreate.png|500px]]
#In the '''Flavor Access''' tab, you can control access to the flavor by moving projects from the '''All Projects''' column to the '''Selected Projects''' column. Only projects in the '''Selected Projects''' column can use the flavor. If there are no projects in the right column, all projects can use the flavor.
#Click '''Create Flavor'''.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-flavors.html
*https://docs.openstack.org/admin-guide/compute-flavors.html

=== TBSC OpenStack 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 TSBC image into your OpenStack before you can launch a virtual machine instance running the TSBC software.

==== Upload an Image ====
Follow this procedure to upload an image to a project:
#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Images category.
#Click Create Image.
#The Create An Image dialog box appears.
#Enter the following values:
#*'''Image Name''' : ''TelcoBridges TSBC xx.yy.zz'' (Where xxx.yy.zz is changed to the version number of the TSBC image)
#*'''Image Description''': ''TelcoBridges TSBC version xx.yy.zz''
#*'''Image Source''' :''File''.
#*'''Image File''' : Browse for the image file on your file system and add it.
#*'''Format''': ''QCOW2''
#*'''Architecture''': ''x86_64''
#*'''Minimum Disk (GB)''' : ''20''
#*'''Minimum RAM (MB)''': ''8192''
#*'''Visibility''' : The access permission for the image. ''Public'' or ''Private'', depending on your needs.
#*'''Protected''': Select this check box to ensure that only users with permissions can delete the image. ''Yes'' or ''No''. [[File:OpenStackImageUpload.png|500px]]
#Image Metadata : Leave empty.
#Click Create Image. The image is queued to be uploaded. It might take some time before the status changes from Queued to Active.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-images.html

=== TSBC OpenStack Instance ===
Instances are virtual machines that run inside OpenStack's cloud. You will need to launch a new instance from the TSBC Image created in the [[#Upload an Image]] section

==== Launching an instance ====

#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Instances category.
#The dashboard shows the instances with its name, its private and floating IP addresses, size, status, task, power state, and so on.
#Click Launch Instance.
#In the Launch Instance dialog box, specify the following values:
##<big>Details tab</big>
##*'''Instance Name''' : Assign a name to the virtual machine. For example: ''TelcoBridges TSBC''.
##*'''Availability Zone''' : By default, this value is set to the availability zone given by the cloud provider (for example, us-west or apac-south). For some cases, it could be nova.
##*'''Count''' : ''1'' [[File:OpenStackLaunchInstanceDetailsTab.png|500px]]
##<big>Source tab</big>
##*'''Instance Boot Source''' : ''Boot from image''.
##*'''Create new Volume''' : ''No''
##*'''Select Image Name''' : Select ''TelcoBridges TSBC xx.yy.zz'' as created in [[#Upload an Image]] section. [[File:OpenStackLaunchInstanceSourceTab.png|500px]]
##<big>Flavor tab</big>
##*'''Flavor''' : Select ''TelcoBridges TSBC Flavor'' as created in [[#Creating a Flavor]] section. [[File:OpenStackLaunchInstanceFlavorTab.png|500px]]
##<big>Networks tab</big>
##*'''Selected Networks''': If you are installing a '''standalone''' SBC, the TSBC will need access to ''WAN'' and ''MGMT'' networks. For transcoding on TSBC-TRANS, or HA pair installation, the TSBC will also need access to ''CTRL0'', ''CTRL1'' and ''TRANS0'' networks. Please refer to [[TSBC-SW:Networking]] for details on network requirements. '''Important''': For optimal performance, it is recommended to use SR-IOV or MacVTap ports to access ''LAN'' and ''WAN'' networks, see [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkTab.png|500px]]
##<big>Network Ports tab</big>
##*'''Ports''' : For optimal performances, SR-IOV and MacVTap ports should be used to access ''LAN'' and ''WAN'' networks. If you do choose to use Network Ports to attach to ''LAN'' and ''WAN'' networks, do not attach to them in ''Networks Tabs''. See [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkPortsTab.png|500px]]
##<big>Security Groups tab</big>
##*'''Security Groups''': Activate the security groups that you want to assign to the instance. Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. If you have not created any security groups, you can assign only the default security group to the instance. '''Warning''': ''Make sure the selected security group allows ingress traffic''. [[File:OpenStackLaunchInstanceSecurityGroupTab.png|500px]]
##<big>Key Pair tab</big>
##*'''Key Pair''' : SSH access to the TSBC with a password is disabled by default on the TSBC. You will need to provide your SSH public key here in order to get SSH access into the TSBC. [[File:OpenStackLaunchInstanceKeyPairTab.png|500px]]
#Click Launch Instance. The TSBC instance will starts on a compute node in your cloud. When the instance state is changed to Active, you will be able to the TSBC using SSH or a web browser as described in the next section..

==== References ====
*https://docs.openstack.org/user-guide/dashboard-launch-instances.html

=== Accessing the TSBC-SW ===
==== TSBC SSH Access ====
There is no root password by default, you will need to SSH onto the TSBC using SSH private key matching the public provided in the '''Key Pair tab''' when [[#Launching an instance|Launching]] the TSBC instance. Login using ''tbcloud'' as username.

For example, if you TSBC management IP is 192.168.178.30:
> ssh tbcloud@192.168.178.30
ECDSA key fingerprint is 5d:94:a1:93:0f:a4:7a:5d:41:cc:29:49:79:5a:58:f3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.178.30' (ECDSA) to the list of known hosts.

CentOS-7-x86_64-Minimal-1511/112/190195:197392, Fri 7 Apr 17:41:46 EDT 2017
[tbcloud@tsbc ~]$

==== Accessing the TSBC-SW web portal ====
# 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: http://192.168.178.30:12358
# You should get to the TSBC Configuration Wizard [[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:OpenStack_Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for OpenStack optimizations:
[[TSBC-SW:Cloud:OpenStack_Optimizations]]

FreeSBC:Baremetal:Installation A

2017-06-06T21:48:58Z

Cboulanger: Added a note to disable CPU throttling in baremetal machine

{{DISPLAYTITLE:TSBC-SW:Baremetal:Installation}}

== Requirements ==
Minimal server requirements:
* 64 bits server
* Quad core Intel CPU 2GHz
* Optical disk drive
* 80GB hard drive
* 8G RAM
* Ethernet adapters
** 10,000 sessions or less: two 1Gbps interface
** 60,000 sessions: two 10Gbps interface
** See list of supported Network Interface Cards (NICs) here: [[Supported_NICs|List of supported NICs]]
* Console access through serial port or keyboard/monitor ports
* BIOS setup for maximum performance (i.e. no dynamic CPU throttling)

For better performance (see [[TSBC-SW:Baremetal:Optimizations|optimization]] section)
* NUMA tunning
* PCIe tunning

== Getting the ISO ==
Please contact our [mailto:sales@telcobridges.com sales team] to get a copy of the latest TBSC-SW ISO.

== Installing using the ISO ==
The ISO installation process will reformat the server's disks and install all the necessary software.

=== Physical installation steps ===
# Identify which Ethernet networks you need and connect them to your server. Refer to [[TSBC-SW:Networking]] for more information
# Burn the ISO onto a DVD
# Get an access to the console of the server. Usually, this is achieved by connecting a keyboard and screen to the server.
# Insert the DVD in the optical drive of your server and boot from the DVD drive.
# You should get the to the "Virtual Appliance Installer" menu on your display: [[File:ISO_install_prompt.jpg|350px]]
# Hit 'R' key, then 'ENTER' key to start the installation [[File:ISO_installing.jpg|350px]]
# Wait for the installation process to complete. When installation is complete, the server will reboot itself.
#* Important: Make sure to remove the DVD from the drive while the server is rebooting. If you get back to "Virtual Appliance Installer", just eject the CD and reboot again.

=== Changing the root password ===
# Use the console to login into the server
## user: root
## password: root
# Change the password to something stronger than root:
# passwd
New password: ........
Retype new password: ........
passwd: all authentication tokens updated successfully.

=== 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 there is no IP assigned, you will need to configure one manually.

# Assign a IP address to the Ethernet interface having network connectivity. Example if the NIC's name would be eth0:
# ip link set eth0 up
# ip addresss add 192.168.178.30/24 dev eth0

=== Accessing the TSBC-SW web portal ===
# Open a web browser to the IP of your server, 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 TSBC Configuration Wizard [[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:Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for baremetal server optimizations:
[[TSBC-SW:Baremetal:Optimizations]]

SS7

2017-05-30T12:49:49Z

Cboulanger: Increased MTP3 DPC/routes capacity to 512 following tracking #18611

[[Image:Ss7-protocol-stack.jpg|thumb|300px|Diagram of the SS7 stack]]
SS7 is a signaling protocol which is used to set up and tear down phone calls. It also provides support for such functionality as local number portability, [[SMS|Short Messaging Service (SMS)]], [[Prepaid & postpaid calling|prepaid billing]] and number translation.

The configuration of SS7 requires that the physical layer, through to the transport layer, and up to the application layer be configured. SS7 configuration involves configuring values for [[MTP2 Layer]], [[MTP3 Layer]], SCCP, and [[ISUP]].

A conceptual illustration of the SS7 protocol stack is shown on the right. In the SS7 architecture, every layer has very specific task and responsibilities to provide to upper layers. Looking at the figure on the right, we see that an SS7 stack covers all levels of the OSI model from physical to application layer. Within this model, it is possible to replace one of more layers by another protocol as long as it provides the same functionalities. In a base call control application over a TDM network, the SS7 stack required would include layers [[MTP1 Layer]], MTP2, MTP3 and ISUP or TUP.

It is worth pointing out that, by being layered in different functional groups, SS7 was built so that different nodes in the network don’t need to implement every portion of the protocol stack if they don’t require to.

== TelcoBridges and SS7 ==
TelcoBridges provides SS7 support with all of its media gateway, VAS development platform and monitoring devices. SS7 functionality is licensed separately and can be provided at initial purchase or added later on via a software [[Add/Change_Licenses|license upgrade]].

SS7 signaling is configured once for the entire [[Tmedia]] or [[Tdev]] system. Any one Tdev unit is capable of running the entire SS7 signaling stack for all the Tdev units in a system.

Systems developed using TelcoBridges hardware can support up to a maximum of 64 point codes. It is worth noting that a single point code can be used for 2 or more devices configured as a single system.

[[High Availability|High availability]] (HA) has been designed into the architecture of the Tmedia product such that the failure of an SS7 stack on one Tmedia unit will be taken over by the SS7 stack of another Tmedia unit.

Click for further information on:
*[[MTP2:Specification|Supported MTP2 standards and variants]]
*[[MTP3:Specification|Supported MTP3 standards and variants]]
*[[ISUP:Specification|Supported ISUP standards and variants]]
== Maximum Capacity ==
{| cellpadding="5" border="1" class="wikitable" style="text-align: center"
|-
! !!Release!!MTP2 HSL!!MTP2 LSL!!MTP3 Links!!MTP3 Linksets!!OPC!!DPC/Routes!!ISUP Stacks!!ISUP Networks!!ISUP Userparts!!CIC Groups/ISUP stack!!CICs/ISUP stack !! MTP2 Link redundancy !! MTP3 Redundancy !! ISUP Redundancy
|-
| rowspan="3" | TMG800
| 2.2-2.7 || 2 || 64 || 64 || 64 || 64 || 128 || 8 || 8 || 8 || 300 || 512 || Yes || N/A || N/A
|-
| 2.8+ || 2 || 64 || 64 || 256|| 64 || 256 || 16 || 8 || 8 || 300 || 512 || Yes || N/A || N/A
|-
| 2.9+ || 2 || 64 || 64 || 256|| 64 || 512 || 16 || 8 || 8 || 300 || 512 || Yes || N/A || N/A
|-
| rowspan="3" | TMG3200
| 2.2-2.7 || 2 || 64 || 64 || 64 || 64 || 128 || 8 || 8 || 8 || 300 || 2048 || Yes || N/A || N/A
|-
| 2.8+ || 2 || 64 || 64 || 256 || 64 || 256 || 16 || 8 || 8 || 300 || 2048 || Yes || N/A || N/A
|-
| 2.9+ || 2 || 64 || 64 || 256 || 64 || 512 || 16 || 8 || 8 || 300 || 2048 || Yes || N/A || N/A
|-
| rowspan="3" | TMG7800
| 2.2-2.7 || 32 (2/Tmedia) || 256 (64/Tmedia) || 256 (64/Tmedia)|| 64 || 64 || 128 || 8 || 8 || 8 || 300 || 30000 || Yes || Yes || Yes
|-
| 2.8+ || 32 (2/Tmedia) || 512 (64/Tmedia) || 512 (64/Tmedia)|| 256 || 64 || 256 || 16 || 8 || 8 || 300 || 30000 || Yes || Yes || Yes
|-
| 2.9+ || 32 (2/Tmedia) || 512 (64/Tmedia) || 512 (64/Tmedia)|| 256 || 64 || 512 || 16 || 8 || 8 || 300 || 30000 || Yes || Yes || Yes
|}

== Supported SS7 Link types ==
Typically:
* A Link
* F Link
The following types are also supported in some circumstances:
* B/D Link
* C Link
* E Link

== Configuration ==

=== Configuration ===
*[[Toolpack:Protocol_Stack_Settings_A#SS7 ISUP|Web Portal v2.8: SS7 Signaling]]
*[[Web_Portal_Tutorial_Guide_v2.7#SS7 ISUP|Web Portal v2.7: SS7 Signaling]]
*[[Web_Portal_Tutorial_Guide_v2.6#SS7 ISUP|Web Portal v2.6: SS7 Signaling]]
*[[Web_Portal_Tutorial_Guide_v2.5#Configuring SS7|Web Portal v2.5: SS7 Signaling]]
*[[Web_Portal_Tutorial_Guide_v2.4#SS7_Signaling|Web Portal v2.4: SS7 Signaling]]
*[[Web_Portal_Tutorial_Guide_v2.3#SS7_Signaling|Web Portal v2.3: SS7 Signaling]]
*[[Web_Portal_Tutorial_Guide_v2.2#SS7_Signaling|Web Portal v2.2: SS7 Signaling]]

== References ==
*[http://en.wikipedia.org/wiki/Signaling_System_7 Wikipedia article]
*[[Short history of SS7]]

[[Category:Glossary]]
[[Category:Revise on Major]]

Product Installation

2017-05-12T21:45:54Z

Cboulanger: Fixed a typo

The following is a list of product installation manuals:
__NOTOC__

==''T''sbc==

===TSBC-SW===
*[[TSBC-SW:Baremetal:Installation_A|Baremetal installation instructions]]
*[[TSBC-SW:Cloud:OpenStack_Installation_A|OpenStack installation instructions]]
*[[Media:tsbc-hw-srv_Installation_Guide_Issue1.0.pdf|TSBC-SW-SRV-HIGH/MID System Installation Guide]]
*[[TSBC-SW:Cloud:VmWare_Installation_A|VmWare installation instructions]]
*[[TSBC-SW:Cloud:AWS_Installation_A|AWS installation instructions]]

===TSBC5000===
*[[Media:tsbc5000_Installation_Guide_Issue1.0.pdf|TSBC5000 System Installation Guide]]

==''T''media==

===TMG800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TMG800 Standalone & TMG800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TMG800 Standalone & TMG800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TMG3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TMG3200 Standalone & TMG3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TMG3200 Standalone & TMG3200 1+1 System Installation Guide]] (For 2U units)

=== TMG7800 ===
*[[Media:TMG7800_Installation_Guide_Issue3.0.pdf|TMG7800 Installation Guide]]
*[[Media:TMG7800_Installation_Guide_Issue1.0.pdf|TMG7800 Installation Guide]] (For 2U units)

==''T''sig==

===TSG800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TSG800 Standalone & TSG800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TSG800 Standalone & TSG800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TSG3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TSG3200 Standalone & TSG3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TSG3200 Standalone & TSG3200 1+1 System Installation Guide]] (For 2U units)

==''T''trans==
===TMGIP800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TMGIP800 Standalone & TMGIP800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TMGIP800 Standalone & TMGIP800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TMGIP3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TMGIP3200 Standalone & TMGIP3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TMGIP3200 Standalone & TMGIP3200 1+1 System Installation Guide]] (For 2U units)

===TMGIP7800===
*[[Media:TMG7800_Installation_Guide_Issue3.0.pdf|TMGIP7800 Installation Guide]]
*[[Media:TMG7800_Installation_Guide_Issue1.0.pdf|TMGIP7800 Installation Guide]] (For 2U units)

==''T''dev==
===TMP800===
*[[Media:TMP800_Installation_Guide_Issue2.0.pdf|TMP800 Installation guide]]

===TMP6400===
*[[Media:TMP6400_Installation_Guide_Issue3.pdf|TMP6400 System Installation guide]]

==''T''monitor==
===TM1000===
*[[Media:TM1000 Installation guide.pdf|TM1000 Installation Guide]]

===TM3000===
*[[Media:TM3000_Installation_Guide_v1.pdf|TM3000 Installation Guide]]

[[Category:Gateway_OAM&P|Product Installation]]
[[Category:Revise on Major]]

Product Installation

2017-05-12T21:45:35Z

Cboulanger: Changed the order of installation

The following is a list of product installation manuals:
__NOTOC__

==''T''sbc==

===TSBC-SW===
*[[TSBC-SW:Baremetal:Installation_A|Baremetal installation instruction]]
*[[TSBC-SW:Cloud:OpenStack_Installation_A|OpenStack installation instructions]]
*[[Media:tsbc-hw-srv_Installation_Guide_Issue1.0.pdf|TSBC-SW-SRV-HIGH/MID System Installation Guide]]
*[[TSBC-SW:Cloud:VmWare_Installation_A|VmWare installation instructions]]
*[[TSBC-SW:Cloud:AWS_Installation_A|AWS installation instructions]]

===TSBC5000===
*[[Media:tsbc5000_Installation_Guide_Issue1.0.pdf|TSBC5000 System Installation Guide]]

==''T''media==

===TMG800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TMG800 Standalone & TMG800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TMG800 Standalone & TMG800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TMG3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TMG3200 Standalone & TMG3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TMG3200 Standalone & TMG3200 1+1 System Installation Guide]] (For 2U units)

=== TMG7800 ===
*[[Media:TMG7800_Installation_Guide_Issue3.0.pdf|TMG7800 Installation Guide]]
*[[Media:TMG7800_Installation_Guide_Issue1.0.pdf|TMG7800 Installation Guide]] (For 2U units)

==''T''sig==

===TSG800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TSG800 Standalone & TSG800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TSG800 Standalone & TSG800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TSG3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TSG3200 Standalone & TSG3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TSG3200 Standalone & TSG3200 1+1 System Installation Guide]] (For 2U units)

==''T''trans==
===TMGIP800===
*[[Media:800_Series_Installation_Guide_Issue5.0.pdf|TMGIP800 Standalone & TMGIP800 1+1 System Installation Guide]]
*[[Media:800_Series_Installation_Guide_Issue3.0.pdf|TMGIP800 Standalone & TMGIP800 1+1 System Installation Guide]] (units shipped before October 28th 2015)

===TMGIP3200===
*[[Media:3200_Series_Installation_Guide_Issue6.0.pdf|TMGIP3200 Standalone & TMGIP3200 1+1 System Installation Guide]]
*[[Media:3200_Series_Installation_Guide_Issue5.0.pdf|TMGIP3200 Standalone & TMGIP3200 1+1 System Installation Guide]] (For 2U units)

===TMGIP7800===
*[[Media:TMG7800_Installation_Guide_Issue3.0.pdf|TMGIP7800 Installation Guide]]
*[[Media:TMG7800_Installation_Guide_Issue1.0.pdf|TMGIP7800 Installation Guide]] (For 2U units)

==''T''dev==
===TMP800===
*[[Media:TMP800_Installation_Guide_Issue2.0.pdf|TMP800 Installation guide]]

===TMP6400===
*[[Media:TMP6400_Installation_Guide_Issue3.pdf|TMP6400 System Installation guide]]

==''T''monitor==
===TM1000===
*[[Media:TM1000 Installation guide.pdf|TM1000 Installation Guide]]

===TM3000===
*[[Media:TM3000_Installation_Guide_v1.pdf|TM3000 Installation Guide]]

[[Category:Gateway_OAM&P|Product Installation]]
[[Category:Revise on Major]]

FreeSBC:Baremetal:Installation A

2017-05-03T20:31:51Z

Cboulanger: /* Requirements */

{{DISPLAYTITLE:TSBC-SW:Baremetal:Installation}}

== Requirements ==
Minimal server requirements:
* 64bits-capable server only
* Quad core Intel CPU 2GHz
* Optical disk drive
* 80G hard drive
* 8G RAM
* Intel DPDK supported NICs (http://dpdk.org/doc/nics)
* Console access through serial port or keyboard/monitor ports

For better performance (see [[TSBC-SW:Baremetal:Optimizations|optimization]] section)
* NUMA tunning
* PCIe tunning

== Getting the ISO ==
Please contact our [mailto:sales@telcobridges.com sales team] to get a copy of the latest TBSC-SW ISO.

== Installing using the ISO ==
The ISO installation process will reformat the server's disks and install all the necessary software.

=== Physical installation steps ===
# Identify which Ethernet networks you need and connect them to your server. Refer to [[TSBC-SW:Networking]] for more information
# Burn the ISO onto a DVD
# Get an access to the console of the server. Usually, this is achieved by connecting a keyboard and screen to the server.
# Insert the DVD in the optical drive of your server and boot from the DVD drive.
# You should get the to the "Virtual Appliance Installer" menu on your display: [[File:ISO_install_prompt.jpg|350px]]
# Hit 'R' key, then 'ENTER' key to start the installation [[File:ISO_installing.jpg|350px]]
# Wait for the installation process to complete. When installation is complete, the server will reboot itself.
#* Important: Make sure to remove the DVD from the drive while the server is rebooting. If you get back to "Virtual Appliance Installer", just eject the CD and reboot again.

=== Changing the root password ===
# Use the console to login into the server
## user: root
## password: root
# Change the password to something stronger than root:
# passwd
New password: ........
Retype new password: ........
passwd: all authentication tokens updated successfully.

=== 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 there is no IP assigned, you will need to configure one manually.

# Assign a IP address to the Ethernet interface having network connectivity. Example if the NIC's name would be eth0:
# ip link set eth0 up
# ip addresss add 192.168.178.30/24 dev eth0

=== Accessing the TSBC-SW web portal ===
# Open a web browser to the IP of your server, 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 TSBC Configuration Wizard [[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:Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for baremetal server optimizations:
[[TSBC-SW:Baremetal:Optimizations]]

FreeSBC:Cloud:OpenStack Installation A

2017-05-03T20:31:15Z

Cboulanger: /* Requirements */

{{DISPLAYTITLE:TSBC-SW:Cloud:OpenStack Installation}}
== Requirements ==
Minimal Cloud requirements:
* 64 bits infrastructures only
* 4 vCPU
* 20G hard drive
* 8G RAM
* Virtio NIC interface

For better performance (see [[TSBC-SW:Cloud:OpenStack_Optimizations|optimization]] section)
* SR-IOV or MacVTap compatible NICs
* Pinned CPU

== Getting the Image ==
Please contact our sales team at sales@telcobridges.com to get a copy of the latest TBSC Image.

== Installation on OpenStack cloud ==

=== TSBC OpenStack Minimal Flavor ===
In OpenStack, a flavor defines the compute, memory, and storage capacity of a virtual server, also known as an instance. If you do not already have a flavor that meets the listed minimal requirements, you will have to create a new one.

==== Creating a Flavor ====
#Log in to the Dashboard and select the '''admin''' project from the drop-down list.
#In the '''Admin''' tab, open the '''System''' tab and click the '''Flavors''' category.
#Click '''Create Flavor'''.
#In the '''Create Flavor''' window, enter or select the parameters for the flavor in the '''Flavor Information''' tab.
#* '''Name''' : ''TelcoBridges TSBC Flavor''
#* '''VCPUs''' : ''4''
#* '''RAM (MB)''' : ''8192''
#* '''Root Disk (GB)''' : ''20''
#* Other fields are left to their default value [[File:OpenStackMinimalFlavorCreate.png|500px]]
#In the '''Flavor Access''' tab, you can control access to the flavor by moving projects from the '''All Projects''' column to the '''Selected Projects''' column. Only projects in the '''Selected Projects''' column can use the flavor. If there are no projects in the right column, all projects can use the flavor.
#Click '''Create Flavor'''.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-flavors.html
*https://docs.openstack.org/admin-guide/compute-flavors.html

=== TBSC OpenStack 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 TSBC image into your OpenStack before you can launch a virtual machine instance running the TSBC software.

==== Upload an Image ====
Follow this procedure to upload an image to a project:
#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Images category.
#Click Create Image.
#The Create An Image dialog box appears.
#Enter the following values:
#*'''Image Name''' : ''TelcoBridges TSBC xx.yy.zz'' (Where xxx.yy.zz is changed to the version number of the TSBC image)
#*'''Image Description''': ''TelcoBridges TSBC version xx.yy.zz''
#*'''Image Source''' :''File''.
#*'''Image File''' : Browse for the image file on your file system and add it.
#*'''Format''': ''QCOW2''
#*'''Architecture''': ''x86_64''
#*'''Minimum Disk (GB)''' : ''20''
#*'''Minimum RAM (MB)''': ''8192''
#*'''Visibility''' : The access permission for the image. ''Public'' or ''Private'', depending on your needs.
#*'''Protected''': Select this check box to ensure that only users with permissions can delete the image. ''Yes'' or ''No''. [[File:OpenStackImageUpload.png|500px]]
#Image Metadata : Leave empty.
#Click Create Image. The image is queued to be uploaded. It might take some time before the status changes from Queued to Active.

==== References ====
*https://docs.openstack.org/admin-guide/dashboard-manage-images.html

=== TSBC OpenStack Instance ===
Instances are virtual machines that run inside OpenStack's cloud. You will need to launch a new instance from the TSBC Image created in the [[#Upload an Image]] section

==== Launching an instance ====

#Log in to the dashboard.
#Select the appropriate project from the drop down menu at the top left.
#On the Project tab, open the Compute tab and click Instances category.
#The dashboard shows the instances with its name, its private and floating IP addresses, size, status, task, power state, and so on.
#Click Launch Instance.
#In the Launch Instance dialog box, specify the following values:
##<big>Details tab</big>
##*'''Instance Name''' : Assign a name to the virtual machine. For example: ''TelcoBridges TSBC''.
##*'''Availability Zone''' : By default, this value is set to the availability zone given by the cloud provider (for example, us-west or apac-south). For some cases, it could be nova.
##*'''Count''' : ''1'' [[File:OpenStackLaunchInstanceDetailsTab.png|500px]]
##<big>Source tab</big>
##*'''Instance Boot Source''' : ''Boot from image''.
##*'''Create new Volume''' : ''No''
##*'''Select Image Name''' : Select ''TelcoBridges TSBC xx.yy.zz'' as created in [[#Upload an Image]] section. [[File:OpenStackLaunchInstanceSourceTab.png|500px]]
##<big>Flavor tab</big>
##*'''Flavor''' : Select ''TelcoBridges TSBC Flavor'' as created in [[#Creating a Flavor]] section. [[File:OpenStackLaunchInstanceFlavorTab.png|500px]]
##<big>Networks tab</big>
##*'''Selected Networks''': If you are installing a '''standalone''' SBC, the TSBC will need access to ''WAN'' and ''MGMT'' networks. For transcoding on TSBC-TRANS, or HA pair installation, the TSBC will also need access to ''CTRL0'', ''CTRL1'' and ''TRANS0'' networks. Please refer to [[TSBC-SW:Networking]] for details on network requirements. '''Important''': For optimal performance, it is recommended to use SR-IOV or MacVTap ports to access ''LAN'' and ''WAN'' networks, see [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkTab.png|500px]]
##<big>Network Ports tab</big>
##*'''Ports''' : For optimal performances, SR-IOV and MacVTap ports should be used to access ''LAN'' and ''WAN'' networks. If you do choose to use Network Ports to attach to ''LAN'' and ''WAN'' networks, do not attach to them in ''Networks Tabs''. See [[TSBC-SW:Cloud:OpenStack_Optimizations]] for details. [[File:OpenStackLaunchInstanceNetworkPortsTab.png|500px]]
##<big>Security Groups tab</big>
##*'''Security Groups''': Activate the security groups that you want to assign to the instance. Security groups are a kind of cloud firewall that define which incoming network traffic is forwarded to instances. If you have not created any security groups, you can assign only the default security group to the instance. '''Warning''': ''Make sure the selected security group allows ingress traffic''. [[File:OpenStackLaunchInstanceSecurityGroupTab.png|500px]]
##<big>Key Pair tab</big>
##*'''Key Pair''' : SSH access to the TSBC with a password is disabled by default on the TSBC. You will need to provide your SSH public key here in order to get SSH access into the TSBC. [[File:OpenStackLaunchInstanceKeyPairTab.png|500px]]
#Click Launch Instance. The TSBC instance will starts on a compute node in your cloud. When the instance state is changed to Active, you will be able to the TSBC using SSH or a web browser as described in the next section..

==== References ====
*https://docs.openstack.org/user-guide/dashboard-launch-instances.html

=== Accessing the TSBC-SW ===
==== TSBC SSH Access ====
There is no root password by default, you will need to SSH onto the TSBC using SSH private key matching the public provided in the '''Key Pair tab''' when [[#Launching an instance|Launching]] the TSBC instance. Login using ''tbcloud'' as username.

For example, if you TSBC management IP is 192.168.178.30:
> ssh tbcloud@192.168.178.30
ECDSA key fingerprint is 5d:94:a1:93:0f:a4:7a:5d:41:cc:29:49:79:5a:58:f3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.178.30' (ECDSA) to the list of known hosts.

CentOS-7-x86_64-Minimal-1511/112/190195:197392, Fri 7 Apr 17:41:46 EDT 2017
[tbcloud@tsbc ~]$

==== Accessing the TSBC-SW web portal ====
# 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: http://192.168.178.30:12358
# You should get to the TSBC Configuration Wizard [[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:OpenStack_Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for OpenStack optimizations:
[[TSBC-SW:Cloud:OpenStack_Optimizations]]

FreeSBC:Baremetal:Installation A

2017-05-03T20:30:37Z

Cboulanger: /* Requirements */

{{DISPLAYTITLE:TSBC-SW:Baremetal:Installation}}

== Requirements ==
Minimal server requirements:
* Quad core Intel CPU 2GHz, 64bits capable
* Optical disk drive
* 80G hard drive
* 8G RAM
* Intel DPDK supported NICs (http://dpdk.org/doc/nics)
* Console access through serial port or keyboard/monitor ports

For better performance (see [[TSBC-SW:Baremetal:Optimizations|optimization]] section)
* NUMA tunning
* PCIe tunning

== Getting the ISO ==
Please contact our [mailto:sales@telcobridges.com sales team] to get a copy of the latest TBSC-SW ISO.

== Installing using the ISO ==
The ISO installation process will reformat the server's disks and install all the necessary software.

=== Physical installation steps ===
# Identify which Ethernet networks you need and connect them to your server. Refer to [[TSBC-SW:Networking]] for more information
# Burn the ISO onto a DVD
# Get an access to the console of the server. Usually, this is achieved by connecting a keyboard and screen to the server.
# Insert the DVD in the optical drive of your server and boot from the DVD drive.
# You should get the to the "Virtual Appliance Installer" menu on your display: [[File:ISO_install_prompt.jpg|350px]]
# Hit 'R' key, then 'ENTER' key to start the installation [[File:ISO_installing.jpg|350px]]
# Wait for the installation process to complete. When installation is complete, the server will reboot itself.
#* Important: Make sure to remove the DVD from the drive while the server is rebooting. If you get back to "Virtual Appliance Installer", just eject the CD and reboot again.

=== Changing the root password ===
# Use the console to login into the server
## user: root
## password: root
# Change the password to something stronger than root:
# passwd
New password: ........
Retype new password: ........
passwd: all authentication tokens updated successfully.

=== 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 there is no IP assigned, you will need to configure one manually.

# Assign a IP address to the Ethernet interface having network connectivity. Example if the NIC's name would be eth0:
# ip link set eth0 up
# ip addresss add 192.168.178.30/24 dev eth0

=== Accessing the TSBC-SW web portal ===
# Open a web browser to the IP of your server, 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 TSBC Configuration Wizard [[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:Optimizations|optimize ]] your server to get the maximum out of your server.

== Web Portal Initial Configuration ==
Click on the following link to pursue installation from the web portal:
[[TSBC-SW:WebPortal:Initial Configuration]]

== Optimizations ==
Click on the following link for baremetal server optimizations:
[[TSBC-SW:Baremetal:Optimizations]]

SBC-SW:Networking

2017-05-01T20:46:07Z

Cboulanger: typo

{{DISPLAYTITLE:TSBC-SW:Networking}}

== Requirements ==

TSBC-SW deployments require a minimum of two networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the TSBC-SW will process.

[[File:Tsbc-sw-minimal_networks.png‎]]

The TSBC-SW can handle up to 32 different physical interfaces which allows numerous different deployment configuration to fit any networking needs.

[[File:Tsbc-sw-any-networks.png‎‎]]

== Network setups ==

Depending on the technical requirements of a particular deployment, a TSBC-SW can be installed as a standalone or protected (1+1) system. These options have different network needs to fulfill their functions. In addition to redundancy, the support of external transcoding equipment with the TSBC-SW also adds to the network requirements. The following section depict the different supported network configurations.

=== Redundancy ===

==== Standalone without transcoding ====

In this configuration, the TSBC-SW does not have any backup instances nor is using any transcoding equipment. Thus, the only networks needed are the management network along with one or many VoIP networks to carry the data streams. In the example below, the TSBC-SW was deployed with one "public" network named 'wan0' and one "private" network named 'lan0'.

[[File:Tsbc-sw-standalone-notrans.png‎]]

==== 1+1 without transcoding ====

In this configuration, the TSBC-SW system is deployed with two instances providing an active/standby redundancy scheme without any transcoding equipment. In addition to the regular networks required shown in the previous example (management and VoIP networks), the two instances need access to two control separate networks allowing to exchange check-pointing information. These networks are private to the TSBC-SW and should never be shared or be visible to non-TelcoBridges equipment.

Although a single control network is sufficient to achieve the 1+1 function, it is not recommended by TelcoBridges unless the operator fully controls all network segments and can guarantee it can never fail at both the physical and routing (IP) layer. In most cases, having two separate control networks going through independent network devices, switches and routers is the only way to ensure 'no single point of failure'.

[[File:Tsbc-sw-1p1-notrans.png‎]]

=== Transcoding ===

The TSBC-SW session border controller should be the only equipment facing the different networks to ensure proper protection and monitoring. In that sense, any transcoding units deployed (TSBC-HW-TRANS) will never be visible from data networks handled by the SBC. The TSBC-SW will require three internal networks to reach the transcoding units: two control networks and one media network. The control networks are the same as those deployed for redundant systems while the media network will contain all the VoIP traffic coming in or out of the transcoding units.

[[File:Transcoding.png]]

==== Standalone with transcoding ====

Combining the standalone network requirements to the transcoding network needs, the deployment of such a system requires multiple networks as depicted below:

[[File:Tsbc-sw-standalone-withtrans.png‎‎]]

==== 1+1 with transcoding ====

Combining the redundant network requirements to the transcoding network needs, the deployment of such a system requires multiple networks as depicted below:

[[File:Tsbc-sw-1p1-withtrans.png‎‎]]

== Network device discovery ==

Once all networks have been physically (or virtually) connected to the TSBC-SW instance, the system can be started. Upon first bootup (or after an operator initiated 'network device role' reset), the TSBC-SW web portal will show a network device assignation page. As the TSBC-SW cannot guess what type of traffic the operator wants to process on any given network, this page is used to identify the role of each detected devices. As described above, the role can be any of the following three: control, management or VoIP traffic (named LAN/WAN). Once the role is selected, the operator can enter a name for each. Every configured/detected physical network device will then appear as a 'physical port' in the 'IP Interace' tab in the web portal.

The operator can click on the '+' sign to get more information about a specific network device. These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).

[[File:network_discovery.png‎‎|500px]]

SBC-SW:Networking

2017-05-01T20:44:48Z

Cboulanger: Added network discovery

{{DISPLAYTITLE:TSBC-SW:Networking}}

== Requirements ==

TSBC-SW deployments require a minimum of two networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the TSBC-SW will process.

[[File:Tsbc-sw-minimal_networks.png‎]]

The TSBC-SW can handle up to 32 different physical interfaces which allows numerous different deployment configuration to fit any networking needs.

[[File:Tsbc-sw-any-networks.png‎‎]]

== Network setups ==

Depending on the technical requirements of a particular deployment, a TSBC-SW can be installed as a standalone or protected (1+1) system. These options have different network needs to fulfill their functions. In addition to redundancy, the support of external transcoding equipment with the TSBC-SW also adds to the network requirements. The following section depict the different supported network configurations.

=== Redundancy ===

==== Standalone without transcoding ====

In this configuration, the TSBC-SW does not have any backup instances nor is using any transcoding equipment. Thus, the only networks needed are the management network along with one or many VoIP networks to carry the data streams. In the example below, the TSBC-SW was deployed with one "public" network named 'wan0' and one "private" network named 'lan0'.

[[File:Tsbc-sw-standalone-notrans.png‎]]

==== 1+1 without transcoding ====

In this configuration, the TSBC-SW system is deployed with two instances providing an active/standby redundancy scheme without any transcoding equipment. In addition to the regular networks required shown in the previous example (management and VoIP networks), the two instances need access to two control separate networks allowing to exchange check-pointing information. These networks are private to the TSBC-SW and should never be shared or be visible to non-TelcoBridges equipment.

Although a single control network is sufficient to achieve the 1+1 function, it is not recommended by TelcoBridges unless the operator fully controls all network segments and can guarantee it can never fail at both the physical and routing (IP) layer. In most cases, having two separate control networks going through independent network devices, switches and routers is the only way to ensure 'no single point of failure'.

[[File:Tsbc-sw-1p1-notrans.png‎]]

=== Transcoding ===

The TSBC-SW session border controller should be the only equipment facing the different networks to ensure proper protection and monitoring. In that sense, any transcoding units deployed (TSBC-HW-TRANS) will never be visible from data networks handled by the SBC. The TSBC-SW will require three internal networks to reach the transcoding units: two control networks and one media network. The control networks are the same as those deployed for redundant systems while the media network will contain all the VoIP traffic coming in or out of the transcoding units.

[[File:Transcoding.png]]

==== Standalone with transcoding ====

Combining the standalone network requirements to the transcoding network needs, the deployment of such a system requires multiple networks as depicted below:

[[File:Tsbc-sw-standalone-withtrans.png‎‎]]

==== 1+1 with transcoding ====

Combining the redundant network requirements to the transcoding network needs, the deployment of such a system requires multiple networks as depicted below:

[[File:Tsbc-sw-1p1-withtrans.png‎‎]]

== Network device discovery ==

Once all networks have been physically (or virtually) connected to the TSBC-SW instance, the system can be started. Upon first bootup (or after an operator initiated 'network device role' reset), the TSBC-SW web portal will show a network device assignation page. As the TSBC-SW cannot guess what type of traffic the operator wants to process on any given network, this page is used to identify the role of each detected devices. As described above, the role can be any of the following three: control, management or VoIP traffic (named LAN/WAN). Once the role is selected, the operator can enter a name for each. Every configured/detected physical network device will then appear as a 'physical port' in the 'IP Interace' tab in the web portal.

The operator can click on the '+' sign to get more information about the network device. These information are helpful to match detected networks with the real network based on these characteristics (IP, driver type, etc).

[[File:network_discovery.png‎‎|500px]]

SBC-SW:Networking

2017-05-01T19:01:05Z

Cboulanger: draft

{{DISPLAYTITLE:TSBC-SW:Networking}}

== Requirements ==

TSBC-SW deployments require a minimum of two networks for initial configuration. The first network will be used as a local management interface to access the instance using the web portal (HTTP/HTTPS) and SSH access. The second network will transport the actual incoming and outgoing VoIP streams (signaling and media) that the TSBC-SW will process.

[[File:Tsbc-sw-minimal_networks.png‎]]

The TSBC-SW can handle up to 32 different physical interfaces which allows numerous different deployment configuration to fit any networking needs.

[[File:Tsbc-sw-any-networks.png‎‎]]

== Network setups ==

Depending on the technical requirements of a particular deployment, a TSBC-SW can be installed as a standalone or protected (1+1) system. These options have different network needs to fulfill their functions. In addition to redundancy, the support of external transcoding equipment with the TSBC-SW also adds to the network requirements. The following section depict the different supported network configurations.

=== Redundancy ===

==== Standalone without transcoding ====

In this configuration, the TSBC-SW does not have any backup instances nor is using any transcoding equipment. Thus, the only networks needed are the management network along with one or many VoIP networks to carry the data streams. In the example below, the TSBC-SW was deployed with one "public" network named 'wan0' and one "private" network named 'lan0'.

[[File:Tsbc-sw-standalone-notrans.png‎]]

==== 1+1 without transcoding ====

In this configuration, the TSBC-SW system is deployed with two instances providing an active/standby redundancy scheme without any transcoding equipment. In addition to the regular networks required shown in the previous example (management and VoIP networks), the two instances need access to two control separate networks allowing to exchange check-pointing information. These networks are private to the TSBC-SW and should never be shared or be visible to non-TelcoBridges equipment.

Although a single control network is sufficient to achieve the 1+1 function, it is not recommended by TelcoBridges unless the operator fully controls all network segments and can guarantee it can never fail at both the physical and routing (IP) layer. In most cases, having two separate control networks going through independent network devices, switches and routers is the only way to ensure 'no single point of failure'.

[[File:Tsbc-sw-1p1-notrans.png‎]]

=== Transcoding ===

The TSBC-SW session border controller should be the only equipment facing the different networks to ensure proper protection and monitoring. In that sense, any transcoding units deployed (TSBC-HW-TRANS) will never be visible from data networks handled by the SBC. The TSBC-SW will require three internal networks to reach the transcoding units: two control networks and one media network. The control networks are the same as those deployed for redundant systems while the media network will contain all the VoIP traffic coming in or out of the transcoding units.

[[File:Transcoding.png]]

==== Standalone with transcoding ====

Combining the standalone network requirements to the transcoding network needs, the deployment of such a system requires multiple networks as depicted below:

[[File:Tsbc-sw-standalone-withtrans.png‎‎]]

==== 1+1 with transcoding ====

Combining the redundant network requirements to the transcoding network needs, the deployment of such a system requires multiple networks as depicted below:

[[File:Tsbc-sw-1p1-withtrans.png‎‎]]

== Network device discovery ==

Once all networks have been physically (or virtually) connected to the TSBC-SW instance, the system can be startup. Upon first bootup or after an operator initiated 'network device role' reset, the TSBC-SW web portal will show a configuration page

[[File:network_discovery.png‎‎|500px]]

File:Network discovery.png

2017-05-01T18:57:13Z

Cboulanger:

SBC-SW:Networking

2017-05-01T18:51:16Z

Cboulanger: draft

SBC-SW:Networking

2017-05-01T18:41:10Z

Cboulanger: draft