Background: Identifying the interfaces on a ByteBlower server
Posted by Vincent De Maertelaere, Last modified by Wouter Debie on 26 April 2019 02:53 PM

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

 

(3 vote(s))
Helpful
Not helpful

Comments (0)

We to help you!