Introduction

This page is for ByteBlower servers migrating from 1.x to 2.x. If you have questions, or which to reinstall your 2.x ByteBlower servers do contact us directly at support.byteblower@excentis.com . We'll get your system up-and-running!

Migrating from the ByteBlower server 1.x environment to the newly released 2.x environment requires a full reinstallation. This guide will guide you through this process.

Once your 2.x server environment is installed, you can update your server software automatically over the network and switch between installed versions. Even running the legacy 1.10 server is possible from the 2.x server environment!

Please disconnect all network connections except the management interface during the installation process.

If you run into any problems, don't hesitate to contact us through this support portal. Furthermore, we can always ship an installation stick to your premises, if creating the bootable medium is not possible.

1. Download installer

To install the 2.x ByteBlower server environment, you need server installer image (an ISO file), which can be download from this support portal.

2. Create bootable installer medium

Now that you've downloaded the ISO-file it must be "burned"  to a CD or USB-key. We will use this CD or USB-key to boot the server and install ByteBlower-2.x.

Depending on your OS on your personal computer you can use the following methods to create a "bootable" USB/CD

a. Windows

USB stick

You can burn an ISO to a USB stick using the rawrite32 tool.

CD-ROM

A free tool called CDBurnerXP is available.  A how to to burn an ISO file to a disk is available.

b. Linux

USB stick

For the following shell example, we assume:

  • the USB stick is found as /dev/sdd
  • the path to the downloaded image is /path/to/byteblower-installer.iso
  • you have root rights or have access to sudo.

$ sudo dd if=/path/to/byteblower-installer.iso of=/dev/sdd
$ sync

CD-ROM

Any CD creating software will do.  You can use Brasero for example.

  1. Select "Burn image"
  2. Select the image to burn.
  3. Select the destination CDROM/DVD 

3. Configure BIOS to boot from installer medium

Before the ByteBlower software can be installed, the server must be configured to boot from the USB.

1100 and 1200 series servers

For 1100 and 1200 series servers, the boot order must be changed in the BIOS. This is explained in the following guides:

After the installation, the boot order must be changed back to the original order, so the (newly installed) server boots from its hard disk again.

1300, 2100, 2200, 3100 and 4100 series servers

On 1300, 2100, 2200, 3100 and 4100 series servers, you can select the device to boot from in the Boot menu. This is opened by rebooting the server and pressing F11 during startup.

From the boot menu, select your USB stick. There may be multipe USB devices in the boot menu, including the internal USB security dongle. The security dongle will have one of the following words in its name: SecuTech, Smartkey, SmartPico, Unikey, EuSec or Eutron. Make sure you do not select this USB device.

If your USB stick is not recognized as boot device, make sure that "Legacy USB Support" is set to enabled:

Using the boot menu, your system will boot from the selected device only once. Therefore, the boot order in the BIOS must not be changed.

4. Installing the ByteBlower software

Please make sure all network connections except the management interface are disconnected at this point!

  1. Boot the ByteBlower Server from the bootable install stick. When the Install Environment has finished booting, a login prompt will appear.
    The login credentials are username "root" and password "excentis".

    Installer login prompt

  2. When access is granted, start the installation with the following command:
    $ byteblower-installer

    Starting the ByteBlower installer

  3. Now the install environment is running, you will be asked a couple of questions.  

    ByteBlower installer welcome screen

  4. It will ask if the correct ByteBlower Server series is found for the current hardware.  Select No if the auto-detect was wrong.



  5. If you selected No in the previous step, you will see a selection list with supported ByteBlower Server series.  
    Please select your series. If you don't know the series, contact Excentis to assist.



  6. Next, the installation program will ask you if the detected management interface is correct.  How management interfaces are named can be found in this background article.



  7. If it's not correct, please select No.  A list will show up to select the correct interface. 



  8. After the installation program has determined its essential information, you can specifiy the hostname of your ByteBlower Server.  
    If you don't know what to do here, you can use the default (byteblower).  Press ENTER to continue.



  9. The install environment has all required the information and will install the ByteBlower software to the ByteBlower Server chassis.  Depending on your hardware this can take up to 10 minutes.



  10. When the basic installation is almost finished, the install environment will request to remove the installation medium (CD, usb-key) to finish the installation.



  11. When the installation is finished, the server will reboot to the ByteBlower update environment.  
    Please follow the guide to do an update on the ByteBlower Server

5. Running ByteBlower Server for the first time.

After the initial update after the installation, the ByteBlower server will reboot into the "ByteBlower Server environment". 

After booting, a login prompt will appear.  Please log in using username "root" and password "excentis".

6. Configuring the ByteBlower server

Since you've re-install the system you will need to run the byteblower-configurator in order to generate the default configuration files.

6.1 Port configuration

We need to configure the ports again so ByteBlower knows how many trunking switches you have. This can be done in some simple steps. 
Start the byteblower configurator ( byteblower-configurator )

Select ByteBlower Server Configuration


Port configuration

Depending on the version of server you will have 2 to 4 traffic interfaces. Depending on the license you will have 1 to 4 traffic swithces. 
A trunking port is connected to a traffic switch. the others are non-trunk ports.
To configure a port as a trunk select the interface



Select Trunking


Select the number of ports you want to assign to this trunking interface. ( usually it will be 48. If you have doubt, don't hesitate to contact us ) 



Configure the rest of the traffic ports accordingly to your license. If you are not sure, do ask us at ( support.byteblower@excentis.com )

Go back to the top level and save the configuration



6.2 other configurations

If you want to change the password or configure a fix IP for the system, then you can also use the ByteBlower-configurator. 
https://support.excentis.com/index.php?/Knowledgebase/Article/View/140 Information on how to configure the IP

Introduction

By default, the ByteBlower Tcl/Python API is installed interactively. When starting the installer, an installation wizard is presented to the user. By going through this wizard, settings such as the installation directory can be configured.

When a graphical environment is present on the system (e.g. Windows or a desktop version of a Linux distribution), an installer window is shown. In a non-graphical environment, the same questions are asked in the console, where the user can specify custom values.

To easily deploy the Tcl API/Python API application automatically across multiple devices in a controlled environment, a unattended (or non-interactive or quiet) installer is available.

Note: for a similar article about the GUI installer, see here.

Unattended mode

To run the installer in unattended mode, simply run the installer executable as a command and add the unattended option.

Note the API can only be installed by a superuser (i.e. a system-wide install).

Linux TCL-API(e.g. 64 bit):

$ ./ByteBlower-API-Tcl-linux-x86_64-installer.run --mode unattended
(returns when finished, no output)

Linux Python-API(e.g. 64 bit):

$ ./ByteBlower-API-Python-linux-x86_64-installer.run --mode unattended
(returns when finished, no output)

Windows TCL-API

> ByteBlower-API-Tcl-windows-x86-installer.exe --mode unattended
(returns immediately, run in background, no output) 

Windows Python-API

> ByteBlower-API-Python-windows-x86-installer.exe --mode unattended
(returns immediately, run in background, no output)

MacOS TCL-API(from 10.6 Snow Leopard on):

$ open ./ByteBlower-API-Tcl-osx-installer.app --args --mode unattended
(returns when finished, no output)

MacOS Python-API(from 10.6 Snow Leopard on):

$ open ./ByteBlower-API-Python-osx-installer.app --args --mode unattended
(returns when finished, no output)

Mac OS X (pre 10.6 Snow Leopard):

$ ./Byteblower-API-Tcl-osx-installer.app/Content/MacOS/installbuilder.sh --mode unattended
(returns when finished, no output)

Running the unattended installation has the following effects:

  • default installation directory is used
    • Windows 32-bit: C:\Program Files\Excentis\ByteBlowerTcl
    • Windows 64-bit: C:\Program Files (x86)\Excentis\ByteBlowerTcl
    • Linux superuser (system-wide): /opt/Excentis/ByteBlowerTcl
    • Mac OS X: /Applications/Excentis/ByteBlowerTcl
  • default directory for the Tcl packages is used
  • all components are installed
  • only the API library for the native system is installed
  • if an existing installation is found at the default directory, it is silently uninstalled!

In exactly the same way, the application can be silently uninstalled. For example for a Linux user-wide installation:

$ /opt/Excentis/ByteBlowerTcl/uninstall --mode unattended
(returns when finished, no output)

Customization in unattended mode

Sometimes the default installer settings are not desirable. They can be overridden by providing additional command-line arguments to the installer.

The following arguments can be used:

  • --prefix (default the system-default): override the installation directory
  • --tcl_pkg_path (default searches the system for relevant Tcl path): the directory to install the tcl packages; this should be part of the Tcl path
  • --disable-components (default none): disable components by adding a comma-seperated list of the following values
    • runtimedocs: Runtime help for all ByteBlower API calls
    • byteblowerhl: A higher-layer Tcl API, to speed up the creation of complex testing scenarios
    • examples: Example scripts using the higher-layer Tcl API
  • --llInstallWin32 (default selected if matching system): enable or disable installation of the ByteBlower lower-layer API for Windows
  • --llInstallLinux32 (default selected if matching system): enable or disable installation of the ByteBlower lower-layer API for 32-bit Linux
  • --llInstallLinux64 (default selected if matching system): enable or disable installation of the ByteBlower lower-layer API for 64-bit Linux
  • --llInstallMacosx (default selected if matching system): enable or disable installation of the ByteBlower lower-layer API for Mac OS X

For example, on a Linux system:

$ ./ByteBlower-API-Tcl-linux-x86-installer.run --mode unattended --prefix /mnt/software/byteblower/tcl --disable-components examples --tcl_pkg_path /mnt/tcllib/packages
(returns when finished, no output)

Note you can show all command-line options using the --help option.

Troubleshooting

Tcl installation not found

Question: You encounter the following message
No valid TCL installation was found. Please provide the path to the Tcl executable.

Answer: Is Tcl installed on your system? If yes you will need to use the graphical mode on you systen, This mode will request the path to the Tcl executable with a pop-up.

No such file or directory

Question: What does this error mean?
./ByteBlower-API-Tcl-linux-x86-installer.run: No such file or directory

Answer: Use the 64bit installer on a 64bit Linux system. The 32bit can't run.

Introduction

By default, the keyboard layout of the ByteBlower Server is Englisch - International. Sometimes, this is not the desired configuration. This setting can be changed easily.

Changing the layout

The ByteBlower server is running the Linux operating system. This OS allows changing the keyboard layout with the command 'loadkeys'.

E.g.

loadkeys fr

will use the french keyboard layout.

Restoring the default keyboard layout can be done using:

loadkeys -d

 

Below a list of some of the supported keyboard mappings

Country

Keyboard layout

Spain

es

France

fr

Belgium

be-latin1

Denmark

dk

Netherland

nl

Italy

it

Sweden

se

United Kingdom

uk

Germany

de

Switzerland

fr_CH

Poland

pl

United States

us

If your country isn't in the list and you would like to know it, just contact us.

ByteBlower systems are shipped with following default username/password. You can use this password to remotely login into the system over ssh.

Username root
Password excentis

Follow these steps to change the password

1. Login into the system

Connect to the server using either a keyboard / screen or by using ssh.

 2. Change the password

 Use the passwd command to change your password.

NOTE: There is no way to recover the password once it is lost. In case of loss, the system needs to be re-installed ( contact support in this case )

Start the byteblower-configurator



Continue after the welcome message



Select "System configuration"



Choose "Change root password"



Provide your new password ( no chars will be shown in the dialog )



Retype your new password



Go back to the main menu



Save and exit



Confirm to save and apply

When requesting support or license renewals, having the ByteBlower serial is handy. To get this information, you can execute this command on the ByteBlower servers command line:

$ byteblower-get-license

Excentis ByteBlower license information tool
(version 2.10.8)
Searching key...
Initializing the key
        Key model : UniKey Drive MINI   Serial : 161340204
Reading the license type...
ByteBlower Server License found :
        version : 3
        Non-trunking interfaces : 1
        Trunking ports : 1
                Ports on trunk 1 : 48
        Nbase-T (2.5G/5G) interfaces : 0
        USB interfaces : 0
        VLANs : 48

        Maximum allowed usage of this dongle : Unlimited
        Expired usage of this dongle : 0


ByteBlower Meeting Point License found :
        version : 1
        Endpoints : 32

        Maximum allowed usage for this license : Unlimited
        Expired usage for this license : 0

This information gives us the following information:

  • ByteBlower serial number. In this example this is 161340204
  • ByteBlower server license with
    • 1 trunking interface with 48 port (ByteBlower switch)
    • 1 non-trunking interface ( interface directly on the server )
    • No NBASE-T ports
    • This is a permanent license
  • ByteBlower Wireless Endpoint license with
    • 32 clients in parallel
    • This is also a permanent license

When using a ByteBlower server, it is sometimes needed to know which version of the ByteBlower server you are currently using.

In the GUI

The version running on your ByteBlower is shown next to its name in the Server-View ( See screenshot ). 

 

On the SERVER

Since 2.3.0

When logging in to a server, execute following command

$ byteblower-get-version

ByteBlower Series 1300
  Version      : 2.3.0
  Revision     : 11981
  Release date : 17/05/16 16:10:39
  Excentux     : 3.1.6-r128

Previous 2.3.0

When logging in to a server, execute following command (since Byteblower 1.8.18 / 1.10.0):

$ lsb_release -d
Description: Excentis ByteBlower 2100 release 2.

Or to get the version number execute:

$ /opt/ByteBlower/bin/byteblower -v
1.10.10

or (on older versions)

$ /opt/ByteBlower/byteblower -v
1.8.8

By default the ByteBlower-sever will use DHCP to get its management ip. In some lab-environments this is not wanted. This page explains you how you can configure a fixed-ip on the management interface.

All this configuration is done by using our ByteBlower-Configurator tool on the server.

Start the byteblower-configurator

Dismiss the welcome-screen

Select System Configuration

Select Network configuration

Select the management interface that you want to change. In most cases it will be Interface man0

In "Review the interface configuration" you can see its current configuration. We want to change this to a static ip. Select Connectivity to change the configuration



Provide all the needed information. IPv6 is optional

Everything is configured. Use the TAB-key to select <OK>. Select < Back > to go all the way back to the Main menu

Now save and exit
to apply the configuration

Now your server will have the configured IP-settings.

Depending on the version running on the ByteBlower, there are 2 methods to retrieve its management IP. By default, the system will obtain his management ip through DHCP/Stateless Autoconfiguration.

If you want to use a fixed ip, read here on how to configure this.

Versions 2.6.0 and up

Once the system is booted and you have attached a keyboard and screen, you will be presented with a login-dialog.

The login screen will show the management IP-address. In this example the management IP for this system is

IPv4 10.8.254.66
IPv6 fdec:5ef9:84b5:40fe:4b00:287e:fd9e:6c37

Pre 2.6.0 system

Once the system is booted and you have attached a keyboard and screen, you will be presented with a login-dialog.

In this version, you have to login to know the ip-address of the management interface. Below are the default login that you can use if you haven't changed them

Username root
Password excentis

 After the login you can use following command

ifconfig man0

 

This article will guide you through the process of identifying the interfaces on a ByteBlower server.

ByteBlower servers have different network interfaces. Some can only be used for management, other conneection are used for generating test-traffic.  The name and purpose of these interfaces differs between ByteBlower server model. Reading this articul, it is thus helpful to know the serie of your ByteBlower. The following article explains determining this serie number How to: Obtaining the ByteBlower Server series and version.

How to configure the ByteBlower server to use these interfaces, is explained on this article: How to: Configuring a ByteBlower server

In this article we will discuss following ByteBlower models:

ByteBlower 1300 series

Annotated 4100 interfaces

The ByteBlower 1300 server series management interfaces are named man0 and man1.  On models with more than 2 management interfaces, they are called man2 and man3.  The traffic interfaces are named enp3s0f0 and enp3s0f1, where the enp3s0f0 is normally configured as trunking interface and enp3s0f1 as non-trunk.  If the license allows it, spare man interfaces can be configured as additional traffic interfaces.

ByteBlower 2100 series

 

Annotated 2100 interfaces

Annotated 4100 interfaces

The ByteBlower 2100 server series management interfaces are named man0 and man1.  On models with more than 2 management interfaces, they are called man2 and man3.  The traffic interfaces are provided as SFP modules and are named phy-0-0 through phy-0-3.  Generally, phy-0-0 is configured as trunking interface while the other interfaces (phy-0-1 through phy-0-3) are configured as non-trunking interface.  If the license allows it, those interfaces can also be configured as trunking interfaces.

The time-sync port can be connected through an adapter-cable to a PTP-network, so the clocks can be synchronized.  This offers the advantage of more accurate inter-server latency measurements.

Please note the display ports on the additional graphics card cannot be used and unlike the ByteBlower 1300 series, the spare management interfaces cannot be used as traffic interfaces.

ByteBlower 3100 series

Annotated 4100 interfaces

The ByteBlower 3100 server series management interfaces are named man0 and man1.  The traffic interfaces are provided as SFP+ modules and are named enp1s0f0 and enp1s0f1.  Generally, enp1s0f0 is configured as trunking interface while the other interface (enp1s0f1) is configured as non-trunking interface.  If the license allows it, this interface can also be configured as trunking interface.

Please note the display ports on the additional graphics card cannot be used and unlike the ByteBlower 1300 series, the spare management interfaces cannot be used as traffic interfaces.

ByteBlower 3200 series


The ByteBlower 3100 server series management interfaces are named man0 and man1.  The traffic interfaces are provided as SFP+ modules and are named enp1s0f0 and enp1s0f1.  Generally, enp1s0f0 and enp1s0f1 are configured as trunking interface while the other interface (enp131s0f0 and enp131s0f1) are configured as non-trunking interface.  If the license allows it, this interface can also be configured as trunking interface.

ByteBlower 4100 series

Annotated 4100 interfaces 



The ByteBlower 4100 server series management interfaces are named man0 and man1.  On models with more than 2 management interfaces, they are called man2 and man3.  The traffic interfaces are provided as SFP+ modules and are named phy-0-0 through phy-0-1.  Generally, phy-0-0 is configured as trunking interface while the other interface (phy-0-1) is configured as non-trunking interface.  If the license allows it, those interfaces can also be configured as trunking interfaces.

The time-sync port can be connected through an adapter-cable to a PTP-network, so the clocks can be synchronized.  This offers the advantage of more accurate inter-server latency measurements.

Please note the display ports on the additional graphics card cannot be used and unlike the ByteBlower 1300 series, the spare management interfaces cannot be used as traffic interfaces.

 

Do you have troubles to identify your server series or its interfaces?  Is the chassis not listed?
Feel free to contact us: support.byteblower@excentis.com

 

Introduction

In some lab environments there isn't a DHCP server running in the management network. You must then use a fixed-ip. This howto explains you how you can configure a fixed-ip in the ByteBlower update-environment

Procedure

Connect to the ByteBlower

To update the ByteBlower server, you'll need a console on the ByteBlower. This can be achieved in 2 ways.

  1. Physical console: Connect a screen and a keyboard.
  2. SSH: Log in from the terminal (Linux or Mac) or with an application such as PuTTY (Windows).

Login using root and the password ("excentis" by default)

If you are not already in the update-environment type "byteblower-update" to reboot to the update system. Once the reboot is done, use the same credentials to login

Change the network configuration (ByteBlower 2.6.0 and later, Excentux-update 3.5.0 and later)

Once you are logged in you will get the following menu. Choose item 4 "Network configuration".

Change network settings

In this sub-menu, various network configuration options can be chosen.  Select item 2 "Interface man0" to configure the first management interface.

Select Interface man0

Select item 2 Connectivity to configure the network interface.

Select Interface man0

Here you can select DHCP, Static or None.  None means not to use this interface.
Select item 2 Static

Select Interface man0

Here you can provide the IP address, netmask and gateway.  Also IPv6 addresses are supported.
Use the UP/DOWN arrows to move between fields, TAB to switch between the input fields and the buttons.

Select Interface man0

Select OK, and return using the Back buttons until the system asks you what to do with this information.

Select item 1 "Apply the changes in the configuration" if you just want to apply the configuration, but you don't want to save it
Select item 3 "Persist the network configuration for updater use" if the configuration must be persisted for update purposes only
Select item 4 "Persist the network configuration for all uses" if the configuration must be persisted no matter what use.

Select Interface man0

 

Change the network configuration (pre-ByteBlower 2.6.0, pre Excentux-Update 3.5.0)

Once you are logged-in you will get following menu. Choose item 4 "Network configuration".

Change network settings

Here you can review or change the network settings.

Change the network configuration

Item 2 allows you to change the network configuration of the ByteBlower updater.Change network settings

Step 1:
First you need to choose the interface you want to change. Man0 is the management interface you want to change.

Select the management interface

Step 2:
After selecting the interface you must choose between DHCP of Static configuration. If you choose DHCP then this is all you need to do and can go to step 4 . For static configuration continue.

Static or Dhcp

Step 3: ( static configured address )
Provide the IP

new IP

Provide the Netmask

Netmask

Provide the Gateway

Gateway

Provide the DNS

DNS

Once you provide the information for this last step. Then the new static IP will be activated.

Step 4:
Review your settings. If you want, you can review your settings by selecting option 1. If not use Back to return to the main menu

review settings

New applied settings

( use page-down page-up to scroll )

Upgrade the server

Now you are ready to upgrade the server. Follow the steps explained in this article on how to upgrade your server.

The ByteBlower is rarely the only instrument in the lab. Especially when comparing events on different tools,  it's very useful having the same time on all. In this article we'll explain how to configure the time on your ByteBlower.

ByteBower supports two approaches to setting time. The manual time configuration sets time right once. Over weeks, months or years the clock on the system will drift away the real time. The automatic time synchronization takes a bit more work, but avoids this drift.

For a single system we recommend doing the manual time config. Once you have multiple ByteBlowers in your lab, we suggest using NTP or PTP for automatic time synchronization.

Manual Time Configuration

To configure the Time,date and timezone you can use our configurator tool installed on the system. Start this by typing byteblower-configurator in the console

Dismiss this message

Go to system configuration

Time Configuration



Configure time and date

If you want to change the time and date, select option 1

You can choose between NTP (Network Time Protocol ) PTP ( only on 2100 and 4100 ) or Manual.


Automatic Time Synchronization

NTP

NTP is the preferred time synchronization on the 1x00 and 3x00 models. The ByteBlower will continuously adapt time to updates from a remote time-server.

For the 4100 and 2100 systems we recommend using PTP. The NTP configuration will only correct time at startup.

For NTP you can use different servers to sync with.


PTP

PTP is the  Precision Time Protocol. This is the preferred option for the ByteBlower 2100 and 4100.  In these models use hardware acceleration for their traffic generation. This extra piece of hardware is also responsible for the time-management.

In addition to the PTP server, you will also need the PTP cable. Each ByteBlower is shipped with an appropriate cable, but you can us at support if it went missing. The cable has a standard RJ45 input. The other end is connected to the network with the PTP master clock.


PTP Clock domain: Clock domain to sync with
PTP User description: ( optional ) description

Configure Timezone

To configure your timezone select option 2

Choose your continent

Choose your country

 Go back to the main menu and Save and Exit to store and active the time configuration

Introduction

By default, the ByteBlower GUI / ByteBlower CLT is installed interactively. When starting the installer, an installation wizard is presented to the user. By going through this wizard, settings such as the installation directory can be configured.

When a graphical environment is present on the system (e.g. Windows or a desktop version of a Linux distribution), an installer window is shown. In a non-graphical environment, the same questions are asked in the console, where the user can specify custom values.

To easily deploy the GUI application automatically across multiple devices in a controlled environment, a unattended (or non-interactive or quiet) installer is available.

Note: for a similar article about the Tcl API installer, see here.

Unattended mode

To run the installer in unattended mode, simply run the installer executable as a command and add the unattended option.

Linux ByteBlower-GUI(e.g. 64 bit):

$ ./ByteBlower-GUI-linux-x86_64-installer.run --mode unattended
(returns when finished, no output)

Linux ByteBlower-CLT(e.g. 64 bit):

$ ./ByteBlower-CLT-linux-x86_64-installer.run --mode unattended
(returns when finished, no output)

Windows ByteBlower-GUI:

> ByteBlower-GUI-windows-x86-installer.exe --mode unattended
(returns immediately, run in background, no output) 

Windows ByteBlower-CLT:

> ByteBlower-CLT-windows-x86-installer.exe --mode unattended
(returns immediately, run in background, no output)

MacOS ByteBlower-GUI (from 10.6 Snow Leopard on):

$ open ./ByteBlower-GUI-osx-installer.app --args --mode unattended
(returns when finished, no output)

MacOS ByteBlower-CLT(from 10.6 Snow Leopard on):

$ open ./ByteBlower-CLT-osx-installer.app --args --mode unattended
(returns when finished, no output)

Mac OS X (pre 10.6 Snow Leopard):

$ ./Byteblower-GUI-osx-installer.app/Content/MacOS/installbuilder.sh --mode unattended
(returns when finished, no output)

Running the unattended installation has the following effects:

  • default installation directory is used
    • Windows 32-bit: C:\Program Files\Excentis\ByteBlower
    • Windows 64-bit: C:\Program Files (x86)\Excentis\ByteBlower
    • Linux user: ~/Excentis/ByteBlower
    • Linux superuser (system-wide): /opt/Excentis/ByteBlower
    • Mac OS X: /Applications/Excentis/ByteBlower
  • default installation settings are used (e.g. desktop icon)
  • if an existing installation is found at the default directory, it is silently uninstalled!

In exactly the same way, the application can be silently uninstalled. For example for a Linux user-wide installation:

$ ~/Excentis/ByteBlower/uninstall --mode unattended
(returns when finished, no output)

Customization in unattended mode

Sometimes the default installer settings are not desirable. They can be overridden by providing additional command-line arguments to the installer.

The following arguments can be used:

  • --prefix (default the system-default): override the installation directory
  • --create_desktop_shortcut (default 1): disable or enable the desktop shortcut

For example, on a Mac OS X system (from 10.6 Snow Leopard):

$ open ./ByteBlower-GUI-osx-installer.app --args --mode unattended --prefix /opt/Excentis/ByteBlower --create_desktop_shortcut 0
(returns when finished, no output)

Note you can show all command-line options using the --help option.

Introduction

For some procedures the ByteBlower server must boot from an USB-key.  This how to describes how to configure the BIOS to boot from an USB-key.

WARNING:  It is important that the configuration is reverted when e.g. the installation is done.  Otherwise the server may not boot consistently.

Procedure

  1. Connect a screen and keyboard to the server.

  2. Power on the server.

  3. When following screen is shown, press the F2-key to enter the BIOS setup.


  4. Use the up and down arrows to select USB Flash Drive Emulation Type


  5. Use the + and - keys to select "Hard disk"


  6. Press escape and select Save Changes and Exit.  Use RETURN to confirm.



  7. At reboot press the F2-key to enter the BIOS setup again.



  8. Use the up and down arrows to select Hard-Disk Drive Sequence


  9. Use the +,- keys to move the "Hard-disk-emulated USB flash drive" as the first device


  10. Press escape to get to the Save Changes and Exit menu.  Confirm using RETURN.


Introduction

For some procedures the ByteBlower server must boot from an USB-key.  This how to describes how to configure the BIOS to boot from an USB-key.

WARNING:  It is important that the configuration is reverted when e.g. the installation is done.  Otherwise the server may not boot consistently.

Procedure

  1. Connect a screen and keyboard to the server.

  2. Power on the server.

  3. When flollowing screen is shown, press the F2-key to enter the BIOS setup.


  4. Using the up and down arrows, select USB Flash Drive Emulation Type and press ENTER


  5. Using the SPACE, + or - keys, change "Auto" to "Hard Disk"


  6. Press escape to get to the main screen again.

  7. Using the up and down arrows, select Boot Sequence and press ENTER.


  8. Using the SPACE, + and - keys, move the Flash Disk to the first position
  9. Press escape to get to the exit menu.  Select Save Changes and Exit to confirm.

Introduction

In some lab environments you can only contact the world wide web by using a Proxy server. If you want to upgrade a ByteBlower 2.x Server, you need to have access to the internet so that the server can download its new software. This HOWTO will help you in some easy steps to activate the use of a proxy server on the ByteBlower system.

Preliminary note

The ByteBlower environments currently only support HTTP proxy servers. HTTPS servers are not yet supported.

Procedure

Connect to the ByteBlower

To update the ByteBlower server, you'll need a console on the ByteBlower. This can be achieved in 2 ways.

  1. Physical console: Connect a screen and a keyboard.
  2. SSH: Log in from the terminal (Linux or Mac) or with an application such as PuTTY (Windows).

Login using root and the password ("excentis" by default)

If you are not already in the update-environment type "byteblower-update" to reboot to the update system. Once the reboot is done, use the same credentials to login

Change the network configuration

Once you are logged-in you will get following menu. Choose item nr 4 "Network configuration".

 

Here you can review or change the network settings.

Configure a network proxy

Item 6 allows you to configure a HTTP-proxy.

First you will be asked for the proxy server its address. e.g. http://proxy.lab.excentis.com:8080 . If you make this blank, you will erase the previous settings and thus disable the use of a proxy server.
Secondly you can optional provide a username and password ( if needed by your proxy server ). Leave blank if not needed



Go back to the main menu by selecting Back

Save/Apply the new settings

Upgrade the server

Now you are ready to upgrade the server. Follow the steps explained in this article on how to upgrade your server.

The ByteBlower can be configured to use DHCP on its management interface. Your DHCP server could be configured to provide a fixed IP address to the ByteBlower server.  Some DHCP Servers use the DUID option to hand out an IP address when it is provided, otherwise it will use the hardware address field.

In this case, the ByteBlower DHCP client behaviour changed when moving from ByteBlower OS versions 2.x (ByteBlower server versions < 2.0) to ByteBlower OS versions 3.x (ByteBlower server versions >= 2.0 and ByteBlower server [compatibility] versions >= 1.10.22). This article will explain why and what the reader can do to fix this.

MAC address vs DUID?

First some history on DHCP, if you're not interested in the DHCP history, just skip this section.

The Dynamic Host Configuration Protocol (DHCP) was based on the BOOTP protocol. The latter did have a fixed header which contained the hardware address. When BOOTP was superseeded by DHCP, the header - and thus the hardware address field - were kept. The hardware address field was one of the identifiers used by the DHCP server to identify the DHCP host. On Ethernet networks commonly the MAC address of the clients NIC is used.

When DHCPv6 was born, a new client identifier was also introduced: the Device Unique IDentifier (DUID). The DUID can be built using multiple mechanisms (e.g. hardware address, hardware address + time, ...). This allows the client to aquire multiple DHCPv6 addresses per interface! This is so flexible that the Client Identifier option was also included in a DHCP extention and DHCP server implementations prefer this Client IDentifier instead of the old hardware address field.

Some DHCP Servers use the BOOTP hardware address field unless they find a DUID option in the DHCP options.  Also a DHCP server cannot dissect a DUID to retrieve the hardware address.  This means that a ByteBlower server can switch IP addresses between 2 software versions!  To prevent this, they ByteBlower server can be configured how to form the DUID option.

ByteBlower Configuration

Most of the DHCP client software packages can be configured which type of identifier to include, what kind of DUID must be used. The DHCP client implementation ByteBlower OS uses, has the choice between clientid and duid. The Client ID is MAC based, the DUID is hardware address + time based.

This is a configuration option which changed when releasing ByteBlower 2.1.0 (running on ByteBlower OS 3.1.0), but can easily be modified on the ByteBlower server.

So if your DHCP server has troubles parsing the DUID, consider changing the ByteBlower DHCP configuration.

  1. Login using the console or SSH.
  2. Edit the dhcpcd.conf file with nano
    # nano /etc/dhcpcd.conf
  3. Find the line 
    #clientid
    and put it active:
    clientid
  4. Find the line:
    duid
    and put into comments:
    #duid
  5. Save and close the file using:
    Ctrl-o, Ctrl-x
  6. Reboot the ByteBlower Server
    # reboot

 

 

New versions for the ByteBlower server are released several times a year. It is recommended to run the last released version. This release includes all the latest features and improvements. Howto update the server is described in this article. Sometimes one wants to compare results with a previously released version. This can be configured from the ByteBlower updater. The text below explains how to pick a new version.

The first step is to ssh into the byteblower-server. With the command excentux-update, the server restarts and boots into the ByteBlower updater mode. This will close the SSH session.




Once the updater has booted, log back in on the system. Depending on the system this might take a while. In the Update system, select the second option and press enter. This is shown in the picture below.



The second option opens a new screen with the available version. Before each version there can be two letter:
  • 'I' : This version is already installed.
  • 'A' : This version is activated. The ByteBlower server will start this version once booted.

In this menu scroll to the version you want to run and press enter. The picture below we select version 2.6.6 of the ByteBlower server. This is already installed, by not activated. After pressing enter, the ByteBlower updater will run perform a number of actions and finally activate the version 2.6.6.




The screen below is the result of activating version 2.6.6. The letters IA indicate that this version will start on bootup. Everything is set up in this menu we can go back to the main menu. This is done with the cancel option at the bottom of the screen.



Once back at the main screen, the system needs to boot back into the ByteBlower server mode. This is done with the Reboot  option in the menu (picture below).




At startup, the ByteBlower server will boot the version we've just select (2.6.6.). A final check is possible with the byteblower-get-version command, or the Server view in the ByteBlower GUI.

We to help you!