Keysight Nemo Server

User Guide
Notices
U.S.Government Rights Warranty
Copyright Notice
The Software is “commercial computer THE MATERIAL CONTAINED IN THIS
© Keysight Technologies, Inc. 2021 software,” as defined by Federal DOCUMENT IS PROVIDED “AS IS,”
No part of this manual may be Acquisition Regulation (“FAR”) 2.101. AND IS SUBJECT TO BEING
reproduced in any form or by any means Pursuant to FAR 12.212 and 27.405-3 CHANGED, WITHOUT NOTICE, IN
(including electronic storage and retrieval and Department of Defense FAR FUTURE EDITIONS. FURTHER, TO
or translation into a foreign language) Supplement (“DFARS”) 227.7202, the THE MAXIMUM EXTENT PERMITTED
without prior agreement and written U.S. government acquires commercial BY APPLICABLE LAW, KEYSIGHT
consent from Keysight Technologies, as computer software under the same DISCLAIMS ALL WARRANTIES,
governed by United States and terms by which the software is EITHER EXPRESS OR IMPLIED WITH
international copyright laws. customarily provided to the public. REGARD TO THIS MANUAL AND ANY
Accordingly, Keysight provides the INFORMATION CONTAINED HEREIN,
Manual Part Number Software to U.S. government INCLUDING BUT NOT LIMITED TO THE
customers under its standard IMPLIED WARRANTIES OF
NTE00000A-90000 commercial license, which is embodied MERCHANTABILITY AND FITNESS
in its End User License Agreement FOR A PARTICULAR PURPOSE.
Edition (EULA), a copy of which can be found KEYSIGHT SHALL NOT BE LIABLE
Edition 4.2, June 2021 at FOR ERRORS OR FOR INCIDENTAL
Documents Software Version 6.1.0 http://www.keysight.com/find/s OR CONSEQUENTIAL DAMAGES IN
weula. The license set forth in the CONNECTION WITH THE
Published by: EULA represents the exclusive FURNISHING, USE, OR
Keysight Technologies Finland, Ltd. authority by which the U.S. PERFORMANCE OF THIS DOCUMENT
Elektroniikkatie 10 government may use, modify, OR ANY INFORMATION CONTAINED
90590 Oulu, Finland distribute, or disclose the Software. HEREIN. SHOULD KEYSIGHT AND
The EULA and the license set forth THE USER HAVE A SEPARATE
therein, does not require or permit, WRITTEN AGREEMENT WITH
Technology Licenses WARRANTY TERMS COVERING THE
among other things, that Keysight: (1)
Furnish technical information related to MATERIAL IN THIS DOCUMENT THAT
The hardware and/or software described
commercial computer software or CONFLICT WITH THESE TERMS, THE
in this document are furnished under a
commercial computer software WARRANTY TERMS IN THE
license and may be used or copied only
documentation that is not customarily SEPARATE AGREEMENT WILL
in accordance with the terms of such
provided to the public; or (2) CONTROL.
license.
Relinquish to, or otherwise provide,
the government rights in excess of
Declaration of Conformity these rights customarily provided to
Declarations of Conformity for this product the public to use, modify, reproduce,
and for other Keysight products may be release, perform, display, or disclose A CAUTION notice denotes a hazard. It
downloaded from the Web. Go to commercial computer software or calls attention to an operating procedure,
http://www.keysight.com/go/conformity commercial computer software practice, or the like that, if not correctly
and click on “Declarations of Conformity.” documentation. No additional performed or adhered to, could result in
You can then search by product number to government requirements beyond damage to the product or loss of
find the latest Declaration of Conformity. those set forth in the EULA shall apply, important data. Do not proceed beyond a
except to the extent that those terms, CAUTION notice until the indicated
rights, or licenses are explicitly conditions are fully understood and met.
required from all providers of
commercial computer software
pursuant to the FAR and the DFARS
and are set forth specifically in writing
elsewhere in the EULA. Keysight shall A WARNING notice denotes a hazard. It
be under no obligation to update, calls attention to an operating procedure,
revise or otherwise modify the practice, or the like that, if not correctly
Software. With respect to any performed or adhered to, could result in
technical data as defined by FAR personal injury or death. Do not proceed
2.101, beyond a WARNING notice until the
pursuant to FAR 12.211 and 27.404.2 indicated conditions are fully understood
and DFARS 227.7102, the U.S. and met.
government acquires no greater than
Limited Rights as defined in FAR
27.401 or DFAR 227.7103-5 (c), as
applicable in any technical data.

2
 Nemo Server User Guide

Is the software of your Cloud-related measurement products up-to-date?

Keysight will periodically release software updates to fix known defects and incorporate product
enhancements. To search for software updates for your product, go to the Keysight Software
Manager website at:
www.keysight.com/find/softwaremanager

3
 Nemo Server User Guide

Contents

1 Before You Begin ...................................................................................................................... 5

1.1 Notes .......................................................................................................................... 5
1.2 Traffic safety ............................................................................................................... 5
1.3 Operating environment ............................................................................................... 5
1.4 Local laws and regulations .......................................................................................... 5
2 Introduction ................................................................................................................................ 6
2.1 Data testing................................................................................................................. 6
2.2 Audio testing ............................................................................................................... 6
3 Physical Nemo Server Installation ......................................................................................... 7
3.1 Step 1: Installing the server ......................................................................................... 7
3.2 Step 2: Booting the server........................................................................................... 7
3.3 Step 3: Change the root password .............................................................................. 7
3.4 Step 4: Configure network settings ............................................................................. 8
3.5 Step 5: Server time-base .......................................................................................... 11
4 Test Endpoint and Cloud Setup............................................................................................ 12
4.1 Install script ............................................................................................................... 12
4.2 Configuration script ................................................................................................... 12
4.3 Nemo Cloud .............................................................................................................. 14
5 Administration .......................................................................................................................... 15
5.1 File system................................................................................................................ 15
5.2 SSH access .............................................................................................................. 15
6 Data Testing ............................................................................................................................ 16
6.1 WWW ....................................................................................................................... 16
6.2 FTP ........................................................................................................................... 17
6.3 Iperf2-nemo .............................................................................................................. 18
6.4 Iperf2-latest ............................................................................................................... 18
6.5 Twamp ...................................................................................................................... 18
7 Appendices .............................................................................................................................. 19
7.1 Server measurement files ......................................................................................... 19
7.2 Update instructions ................................................................................................... 19
7.3 Server hardware diagnostics ..................................................................................... 20
7.4 Nemo Server networking........................................................................................... 20
8 Technical Support ................................................................................................................... 25
8.1 Nemo Support Portal ................................................................................................ 25
8.2 Phone and email support .......................................................................................... 25
8.3 Locations for Keysight Technologies ......................................................................... 25

4
 Nemo Server User Guide

1 Before You Begin

This manual explains how to set up and operate the Nemo Server software developed by
Keysight Technologies.

1.1 Notes
When using the Nemo Server devices for reporting use, the battery operation time is reduced
from normal use. The best operation times will be achieved when the batteries are regularly
charged and discharged as instructed in the device user manual. See also other instructions and
hints from the device user manual regarding the battery use.

1.2 Traffic safety

Do not operate Nemo Server (or any test device) and drive at the same time.
Remember, traffic safety comes first.

Note that in some countries it is illegal to drive a car and operate a device at the
same time.the top of the device screen and check that the mobile data setting is
activated.

1.3 Operating environment

Do not operate Nemo Server without reading the User Manual, including its
warnings, for the devices used by Nemo Server.
Always stop using Nemo Server and switch off the Nemo Server device(s) when it is
forbidden to use radio equipment or when it may cause interference or danger.
Do not use the Nemo Server device(s) in a hospital. It may interfere with nearby
electronic devices.
Never use Nemo Server in an aircraft. The use of mobiles in an aircraft may be
dangerous.
Observe restrictions on the use of radio equipment in gas stations, fuel depots,
chemical plants, or sites where blasting operations are in progress.

1.4 Local laws and regulations

Note that the local laws and/or regulations may set limitations, restrictions or other obligations on
the use of the Nemo Server and/or the test devices. Observe the laws and regulations of the
country (as well as of any other relevant jurisdiction) where the Nemo Server and/or test device
is used. Keysight assumes no responsibility or liability arising from the failure to comply with the
local laws and/or regulations.

5
 Nemo Server User Guide

2 Introduction
Starting from the 6th generation Nemo Server, the server does not support any kind of physical
PSTN/ISDN adapters and cannot do voice quality testing but data testing only. Since almost all
deployments are virtual nowadays, the Nemo Server platform has evolved from hardware-only
platform towards Cloud- and virtual-based deployments.

This chapter describes the procedures for physical and virtual Nemo Server on-site installation.
The server must be at the final installation location at the customer’s premises.

This manual is for Server v6.10 only and for Dell models T140 and R240.

2.1 Data testing

For server controlling it is recommended that the server is connected to LAN using integrated
Ethernet port 1. For data testing with Nemo Outdoor or Nemo Handy an external internet
connection is required.

Note that the physical, Keysight-delivered Nemo Server is properly firewalled using
iptables. For user’s own virtual/physical server installations, the firewall must be set
up and managed by the end-user.
In any case, Keysight is not responsible for the safe operation of the test protocols
and server platforms, and necessary security hardening is left for the end-user.

2.2 Audio testing

Voice Quality testing is not supported by v6 Nemo Server platform.

6
 Nemo Server User Guide

3 Physical Nemo Server Installation

This chapter can be skipped if own server platform is used.

Never shut down the server by pressing the power button for a long time. Instead,
shut down the server by using the command: # sudo shutdown -h now

3.1 Step 1: Installing the server

Please refer to the enclosed Dell server installation documents for how to set up the power,
keyboard, mouse and display.

Before connecting the power cable, make sure that the voltage selector of server
power is set according to local mains voltage. By default it is set to 230VAC. Do not
connect the server to the Internet at this time – only connect the LAN interface cable.

Depending on the selected datatest option, there will be either:

 Intel 4x 1Gbit Ethernet interface card
 Network interface with 2x SFP+ adapters and 2x 1Gbit Ethernet ports
installed to the second lowest PCI-E slot.

3.2 Step 2: Booting the server

Switch on the server and wait until the boot process finishes, and enter the following to the logon
prompt:
Username: root
Password: nemonemo
After the logon has completed, the NemoServer CLI appears and there is no Desktop available.

The following prompt symbol refers to root console commands from now on:

3.3 Step 3: Change the root password

This step is required only if the server is to be connected to the Internet.
The superuser/administrator is called root in Linux. The root’s password can be changed with
the passwd command:

# passwd
Changing password for user root.
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully.

Create a new password according to the following guidelines:

 Do not use common words or names

 The password must be at least 8 characters long

7
 Nemo Server User Guide

 The password should have upper and lower case characters, numbers, and special
characters
The following is an example of a valid password (do not use this, as it is the default password
for server 2.01 and earlier versions):

6yV-1pSc

Write the password down and keep it in a safe and secure place! There is no easy
way to retrieve it if it gets lost. In addition, after the root password has been changed,
the server’s superuser account can only be accessed locally with the password.
Please note that Keysight cannot guarantee absolute safety when the server is
connected to the Internet since the server has active, public services such as SSH,
FTP, WWW and Iperf that can be or become vulnerable. However, the server has a
properly configured firewall that should prevent all common intrusions.

Enable the Internet connection only AFTER these steps!

3.4 Step 4: Configure network settings

Interfaces can be configured by editing file /etc/network/interfaces

In Debian Linux network interfaces are named as shown in table below. The following interfaces
are installed by default: lo for localhost, and eno1 and eno2 for integrated 1 Gbit ports.
The datatest option adds interfaces like enp1s0f0np0 or enp1s0f0 depending on the interface
type.

Interface Description
lo Loop-back interface for local IP traffic
eno1 first integrated port, 1000BASE-T
eno2 second integrated port,1000BASE-T
enp1s0f0np0 first SFP+ interface adapter, 10GBASE-SR/LR
enp1s0f1np1 second SFP+ interface adapter, 10GBASE-SR/LR
enp1s0f0 first Ethernet interface port, 1000BASE-T
enp1s0f1 second Ethernet interface port, 1000BASE-T
enp1s0f2 third Ethernet interface port, 1000BASE-T
enp1s0f3 fourth Ethernet interface port, 1000BASE-T

Following command shows the current network configuration, and can be used for checking the
server’s IP addresses if they are assigned using DHCP:

# ip a

Example for Server with 10 Gbit dual-port SFP+ interface card:

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000

8
Nemo Server User Guide

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether 10:98:36:a0:71:0d brd ff:ff:ff:ff:ff:ff
inet 1.2.3.4/24 brd 1.2.3.0 scope global eno1
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 10:98:36:a0:71:0e brd ff:ff:ff:ff:ff:ff
4: enp1s0f0np0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
state DOWN group default qlen 1000
link/ether b0:26:28:78:b4:80 brd ff:ff:ff:ff:ff:ff
inet 10.10.0.1/24 brd 10.10.0.255 scope global enp1s0f0np0
valid_lft forever preferred_lft forever
5: enp1s0f1np1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
group default qlen 1000
link/ether b0:26:28:78:b4:81 brd ff:ff:ff:ff:ff:ff

Example for Server with 1 Gbit quad-port Ethernet interface card:

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether 10:98:36:a0:71:0d brd ff:ff:ff:ff:ff:ff
inet 1.2.3.4/24 brd 1.2.3.0 scope global eno1
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether 10:98:36:a0:71:0e brd ff:ff:ff:ff:ff:ff
4: enp3s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether b4:96:91:59:18:a8 brd ff:ff:ff:ff:ff:ff
5: enp3s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether b4:96:91:59:18:a9 brd ff:ff:ff:ff:ff:ff
6: enp3s0f2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether b4:96:91:59:18:aa brd ff:ff:ff:ff:ff:ff
7: enp3s0f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether b4:96:91:59:18:ab brd ff:ff:ff:ff:ff:ff

9
Nemo Server User Guide

Note also that if Docker is installed, there is an additional interface named as docker0 with
several virtual devices.

Edit network settings using the following command:

# nano /etc/network/interfaces

The file opens for editing, and by default all interfaces except eno1 are configured for DHCP:

# This file describes the network interfaces available on your system

# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface

auto lo
iface lo inet loopback

# The primary network interface

allow-hotplug eno1
iface eno1 inet static
address 1.2.3.4/24
gateway 1.2.3.1
dns-nameservers 1.2.3.5

allow-hotplug eno2
iface eno2 inet dhcp

allow-hotplug enp1s0f0np0
iface enp1s0f0np0 inet dhcp

allow-hotplug enp1s0f1np1
iface enp1s0f1np1 inet dhcp

Set up the static addresses where needed by changing the highlighted dhcp to static and
entering address and gateway (and dns name server if needed) like with section eno1, indented
using Tab.

Once editing is done, close by pressing Ctrl+x and answering Y.

If interface settings were changed, it is required to restart the interface using the following
commands: (this example is for interface enp1s0f0np0):

# ip link set enp1s0f0np0 down

# ip link set enp1s0f0np0 up

Note that it is recommended to use a static IP address on the WAN side so that there
is no need to change the IP address into measurement unit configurations in case of
possible later changes to it.

10
 Nemo Server User Guide

3.5 Step 5: Server time-base

By default, server is configured to UTC timezone.

Recommendation is that the Server should use UTC time whenever Cloud-related
functions are used as UTC is also the time reference for Nemo Cloud backend.

To change the time zone, run the following command:

# dpkg-reconfigure tzdata

Then select continent and country. For example, to set UTC timezone, first select None of the
above, then UTC and press Enter.

11
 Nemo Server User Guide

4 Test Endpoint and Cloud Setup

4.1 Install script

For physical Nemo Server this chapter can be skipped as setup is already
completed. The script can be found from folder /usr/nemo/install/.

Setup scripts install all required operating system service and software components needed for
running the datatest container endpoints on the host. It should be run as root or using sudo.

Supported operating systems are Debian 10 (amd64) and Ubuntu 20.04 LTS (amd64).

Download the install script and run it. This can be done for example at /tmp/ folder.

# wget -nc https://debian.nemo.fi/update/nemoserver-install.pl

# chmod u+x nemoserver-install.pl

# sudo ./nemoserver-install.pl

Debian version buster found on this server

Updating apt lists
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:2 http://deb.debian.org/debian buster InRelease
...
***End of install script***

The installation outputs a lot of text and may take long depending on what was already installed.

If errors happen during installation, check the install log file:

# less /var/log/dataserver_install.log

Press ctrl+f to go to the end, and sequence ctrl+c q to exit less.

4.2 Configuration script

At this point the server host should have IP addresses assigned and working network
connectivity (see chapter 3).

The configuration script is used for controlling and updating the datatest endpoints.

Start the script as root user or using sudo.

# sudo /usr/nemo/nemoserver-config

12
Nemo Server User Guide

The line 5-9 color indicates which services are running:

white service container is not installed
red service container is installed but stopped
green service container is installed and running

1 – Shows running test service containers

2 – Updates host operating system and all running containers, and restarts containers
3 – Menu for enabling/disabling automatic operating system updates
4 – Menu for enabling/disabling automatic daily test container restart
5 – 8 Menus for controlling individual datatest containers

Before enabling the actual services, select 2 from main menu to update everything.

4.2.1 nemo-iperf2 Docker container

Select 1 from submenu and return to main menu by pressing 0.

4.2.2 iperf2-latest Docker container

Select 1 from submenu and return to main menu by pressing 0.

4.2.3 http Docker container

Select 1 from submenu and return to main menu by pressing 0.

4.2.4 FTP Docker container

For diskless transfer the vsftpd has to be patched first. To do this, run the following command
and select: 7 – FTP Docker container:

13
 Nemo Server User Guide

# /usr/nemo/nemoserver-config.sh

NemoServer v6 configuration tool

Host: nsv6 - select action:

==================================
1 ----- Service status
2 ----- Update server host, Docker images and running containers
3 ----- [menu] Weekly automatic server updates
4 ----- [menu] Enable/Disable service containers autorestart
5 ----- [menu] nemo-iperf2 Docker container
6 ----- [menu] iperf2-latest Docker container
7 ----- [menu] http Docker container
8 ----- [menu] FTP Docker container
9 ----- [menu] TWAMP Docker container
0 q---- Exit

Then select: 1 – Run/restart diskless FTP Docker container:

FTP Docker container - select action:

===========================================
1 ----- Run/restart diskless FTP Docker container
2 ----- Stop diskless FTP container
3 ----- Update diskless FTP image
0 ----- Return to main menu
q ----- Quit

When this is done for the first time and each time after updating the Docker image, the vsftpd is
patched to support Nemo diskless FTP. Note that there will be lots of output during the building
but it is normal. The updating and building may take a long time. After it finishes, return to the
main menu by pressing 0.

4.2.5 TWAMP Docker container

Select 1 from submenu and return to main menu by pressing 0.

Note that the starting and stopping of this container may take long time.

4.3 Nemo Cloud

Nemo Cloud is not available for the moment.

14
 Nemo Server User Guide

5 Administration

5.1 File system

Once it is set up, the server is almost administration free when it comes to server settings. The
only situation where administration may be required is if the hard disk becomes full.
Initially, the server has more than 130 GB of free disk space, but it may run out of it in a couple
of years, especially if test files are uploaded constantly but not deleted at any point. If this
happens, the files must be deleted from the upload folders manually.

These clean-up tasks are done automatically:

 The /tmp folder is checked on Sundays at 3:20 am and files that have not been modified
for over 5 days are deleted.

5.2 SSH access

By default, the server accepts only public key authentication via SSH for root user.

To create a public key, pair login to root console and write the following commands.

# cd /root
# ssh-keygen -b 2048 -t rsa
# cat .ssh/id_rsa.pub >> .ssh/authorized_keys

Just press enter when the ssh-keygen asks.

Copy the private key .ssh/id_rsa to your workstation by using USB media.

Go to folder /root/.ssh

# cd /root/.ssh

Insert USB disk

Mount the USB media

# mount /dev/sdb1 /media/cdrom

Copy file id_rsa to USB media

# cp id_rsa /media/cdrom/

And unmount the USB stick so it can be detached.

# umount /media/cdrom

On Windows, run application puttygen.exe - it can be found usually from folder C:\Program Files
(x86)\PuTTY
Press Load and select All Files (*.*) from a dropdown list next to File Name field.
Browse the private key file named as id_rsa
Press OK and the key details should appear.
Now press Save private key and answer Yes
Set name like nemov5_private and press Save

15
 Nemo Server User Guide

6 Data Testing
NemoServer v6 datatest endpoints are implemented as Docker containers that are isolated
environments inside the host operating system, so that each test service protocol is a single
Docker container.

There are five running containers for http, ftp, iperf2-nemo, iperf-2.0.14 (latest) and Twamp
protocols.

Port mappings from containers to host ports

protocol host ports

ftp 20-21/tcp
http 80/tcp
iperf2-nemo 5001/tcp, 5001/udp
iperf2-latest (2.0.14) 5002/tcp, 5002/udp
twamp 862/tcp, 5010-5099/udp

Test endpoints can be controlled by using nemoserver-config script (see chapter 4.2).

Although the server is capable for 5x1 Gbit/s continuous transfer speed, this has
been measured with Iperf2 protocol that generates the traffic. In real world when for
example FTP is used for speed tests, the server has to read/write files to hard-disk
that may become a bottleneck, and if it happens that will effectively lower the max
obtainable speed. The server should handle approximately 400 MB transfers even if
all transfers are reading/writing different files.

To max out the available bandwidth, there are special methods available for both FTP and
HTTP(S) that effectively eliminate disk access, see chapters below. Other protocols, iperf2 and
twamp, are diskless by default.

6.1 WWW
All files can be accessed via HTTP and via any public IP address of the server.

HTTPS is not supported for the moment.

If the filename is omitted, the server returns simple PONG page:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>It works</title>
</head>
<body>PONG</body>
</html>

Standardized test web pages Copernicus, Kepler and Kepler for smartphones are behind URLs:
 http://ip.add.re.ss/copernicus
 http://ip.add.re.ss/kepler
 http://ip.add.re.ss/keplersm

16
 Nemo Server User Guide

Note that the IP address used on these examples is just an example.

For diskless transfer, use up.php and gen.php as they save server’s disk I/O resources.

up.php - Receives a file with POST but does not save it. The response message 200
RESPONSE contains the size of the received file.
gen.php?size=n - Generates n kilobytes random data and returns it as file random.bin, for
example: http://192.168.0.1/gen.php?size=1000

6.2 FTP
Only passive FTP mode and diskless transfer method are supported.

If no valid DNS is configured into network settings, the FTP login may become slow.
This is due to reverse DNS lookups that vsftpd does for connecting client IP
addresses. Unfortunately, the vsftpd does not support the disabling of this feature
(reverse_lookup_enable=NO) so the only way to shorten the time is to configure
DNS to network settings.
It can be done as described in chapter 3.5. If no proper DNS servers are available
locally, use Google’s free server at 8.8.8.8.

Diskless transfer is available via anonymous login mechanism only.

Vsftpd has been modified so that an anonymous account is used for diskless transfer so that I/O
streams are not pointed to disk files but RAM only.
Anonymous base directory is /var/ftp and that shows as the anonymous root folder / when
logged in. The base directory is write protected and the only writable folder is /pub
Anonymous account:
username: ftp
password: ftp (any string will do)

SSL- and ACSII-modes are not supported, binary-mode only.

Diskless uploading
The service accepts file creation only under /pub folder. File will be created when transfer starts
but all received packets are discarded instead of file writing. After the transfer, the created empty
file is removed and success-result sent for the client. Disk is accessed only when file is created
and removed. Multiple sessions can upload to the same target file simultaneously (that is not
possible with standard account).

Diskless downloading
When file is downloaded, the content comes from static 64k memory buffer filled with random
content.
The file request should start with integer/decimal number. The rest of the request filename is
composed of optional size factor and mandatory type modifier. The minimum and maximum
accepted sizes are 1 byte and 5000000000 bytes (5 gigabytes).
Format: n[.mmmmmm][x][t].bin
n[.mmmmm] = integer number, optionally decimal number, max 5 decimals
x is optional size factor (default 1 if omitted): k = 1000, m | M = 1000000, g | G = 1000000000
t Optional type modifier (default is byte if omitted): b | B = bytes and bit = bits = 1/8 bytes
The server sends requested amount in metric bytes as transfer speeds are always presented
within metric system, i.e. 1kb.bin means 1000 bytes and 8kbit.bin means also 1000 bytes. Bit

17
 Nemo Server User Guide

amounts are rounded down to nearest byte. The requested filename will be created and written
locally but it depends of course of the used FTP client what it does with the downloaded data.

Examples:
1.bin -> 1 byte 1kb.bin -> 1000 bytes
1mb.bin -> 1000000 bytes 1gb.bin -> 1000000000 bytes
8bit.bin -> 1 byte 1kbit.bin -> 125 bytes
1mbit.bin -> 125000 bytes 1gbit.bin -> 125000000 bytes
1.55kb.bin -> 1550 bytes 1.55kbit.bin -> 193 bytes

6.3 Iperf2-nemo
The server has two Iperf2-nemo services running at port 5001, one in UDP and other in TCP-
mode. Services are available via all connected network interfaces. Iperf2-nemo service is also a
diskless transfer method and very useful, for example, on UDP maximum throughput testing.

iperf2-nemo is not fully compatible with vanilla iperf2 protocol and can be used only
with Nemo products.
When configuring multi-data Iperf-tests with Nemo Outdoor, USE THE SAME IP
ADDRESS FOR EACH TERMINAL. This differs from normal data testing (www, FTP,
etc.) because those have to be configured to use different IP addresses.

6.4 Iperf2-latest
The server has two Iperf2-latest (currently 2.0.14) services running at port 5002, one in UDP and
other in TCP-mode. Services are available via all connected network interfaces. Iperf2-latest
service is also a diskless transfer method and very useful, for example, on UDP maximum
throughput testing.

iperf2-latest requires using iperf2-latest as test protocol as the field test unit side.

6.5 Twamp
The server has Twamp protocol service running at port 862/tcp (control port), and port range
5010-5099/udp (datatest ports) is reserved for connecting clients.

Field test unit side should not select the datatest port, but server assigns and sends
it.

18
 Nemo Server User Guide

7 Appendices

7.1 Server measurement files

The server does not generate measurement files from data testing.

7.2 Update instructions

7.2.1 System updating

By default, the Server checks from public Debian repositories available security upgrades once
per day. If updates are found, it downloads and installs security upgrades automatically and
unattended without asking permission.

The Server does not apply any Nemo SW updates automatically to minimize disruptions for data
testing. To keep the system up to date, run the following commands once per week when Server
is not used for testing.

# apt update
# apt upgrade

If any questions appear during the updating just press enter.

All measurements have to be stopped before updating is started as the update may
terminate several services during the updating and therefore open measurements
can be interrupted.

7.2.2 Test endpoint updating

The nemoserver-config script can update and restart all running test containers.

Run following commands as root user

# cd /usr/nemo
# ./nemoserver-config update

7.2.3 Server factory reset

This is required only if the server’s hard-disk fails for recovering the system, not for
casual updating. The server image updating method erases all files that are currently
on your server’s hard-disk! Backup all necessary data before continuing with the
update.

1. Shut down the server, open the chassis and remove Ethernet card(s).

2. Start the server and press F11 as soon as the BIOS POST screen appears. Press Ctrl-
Alt-Del to reset if you were not fast enough and Linux already started.

3. Insert bootable image USB.

19
 Nemo Server User Guide

4. Browse and select the USB from hard disks for boot device, after which Debian Isolinux
should appear on the screen. After a while, there will be a question whether to continue
with hard-disk overwriting. Answer y to continue. Image writing will take max 5 minutes.

5. After the writing is finished, take the USB off, and press the power button for a few
seconds to power off the server, and then start it again.

6. Setup networking IP addresses as described in chapter 3.5

The initial hard-disk partition is very small and hence NSM should be started on first
boot as it can extend the operating system to fill up the whole hard disk.

If BIOS is reset, the system has to be changed to boot from BIOS instead of UEFI.
Also go to Integrated Devices and set Memory Mapped I/O above 4 GB to Disabled.

7.3 Server hardware diagnostics

Dell servers have integrated HW diagnostics application that can be used for checking essential
system components.

Sometimes the HW problem occurs only rarely and therefore the diagnostics may not
be able to catch it. This may be the situation if server can be booted up and used for
some time before problem occurs.

How to start the system diagnostics:

Press F10 as soon as the boot menu and Dell logo appear and it boots Unified Server
Configurator.
Select Hardware Diagnostics.
Press tab to select Run Hardware Diagnostics and press enter.
Dialog appears asking 'Device initialization may be required... Continue?'.
Just answer Yes and select either of following:
 Run Diags for system-wide tests (20-30 minutes long test)

 MpMemory and Express mode for quicker memory+cpu tests (5-10 minutes)
The last item of system-wide tests will fail in absence of floppy disk but it is normal
since the system does not have floppy disk interface.

7.4 Nemo Server networking

7.4.1 Static Public Address

Public address
62.142.77.195

INTERNET

20
Nemo Server User Guide

7.4.2 Dynamic Public Address

DHCP for Public
addresses
Public address

INTERNET

7.4.3 Private Addresses (RFC 1918)

Private address spaces (reserved addresses):
 10.0.0.0 – 10.255.255.255

 172.16.0.0 -172.31.255.255

 192.168.0.0 - 192.168.255.255
No route from the Internet!
Internal use only!

7.4.4 Static NAT (destination NAT)

 Basic NAT. No port mapping

 Virtual Public IP is translated to private IP addresses

 What is my public IP?

Static NAT mode

Public address
Private address
62.142.77.198
192.168.200.2
INTERNET

Destination NAT (DNAT)

Source NAT (SNAT)

21
Nemo Server User Guide

With virtual interfaces we can map multiple public address to one private. (Nemoserver)

7.4.5 Static NAT and PAT

PAT = Port address translation
With port mapping, we can map one public address to many private servers

Static NAT + PAT

Public address 192.168.200.2

62.142.77.199
192.168.200.3
INTERNET

192.168.200.3

22
Nemo Server User Guide

7.4.6 Dynamic NAT

Multiple private addresses
Port mapping
Common ISP setup for homes
Access from internet needs static configuration

Dynamic NAT mode Private address from a

DHCP pool DHCP server address pool:
Public address 192.168.200.2
62.142.77.198 192.168.200.3
.
.

INTERNET

Static NAT

7.4.7 Debugging
 What is my ip?  http://whatismyip.com

 iptstate A top-like display of IP Tables state table entries (not installed by default)

 tcpdump dump traffic on a network (not installed by default)

Example: Dump iperf traffic on interface eso1

# tcpdump dst port 5001 -I eso1

 route display routing table and default Gateway

 ip a display interface configuration

 netstat pPrint network connections, routing tables, etc.

23
Nemo Server User Guide

7.4.8 Static NAT (port forwarding) example with Buffalo access point

24
 Nemo Server User Guide

8 Technical Support
If you have questions on or beyond this documentation about Nemo tools, please contact our technical
support service through Nemo Support Portal at http://nemo.support.keysight.com, call us or send us an
email at [email protected]. Note that for full support you need to have the Maintenance
Agreement.

8.1 Nemo Support Portal

Nemo Support Portal is a web interface for technical support, product-related questions, and RMA
requests. It offers a fast and convenient way to reach our technical support team and submit repair,
warranty repair, and calibration requests. Customers can open a support ticket, follow the status of
existing tickets, and request technical support 24/7/365. Furthermore, the Nemo Support Portal includes a
Knowledge Base for the most frequent and latest topics on Nemo Products. Submitting a ticket via Nemo
Support Portal ensures that our technical specialists have all the necessary information available to solve
your support case, resulting in faster response times.

Please go to http://nemo.support.keysight.com to access the portal and click Request access to obtain a
password to the system.

8.2 Phone and email support

During the warranty period, the phone support related to potential software errors is free of additional
charge. Registered users with a valid Maintenance Agreement are entitled to full support. For a list of
service locations, please visit http://www.keysight.com/find/assist

Nemo Support Portal is the preferred channel for technical support requests, but you can also send us an
email to [email protected]. When emailing, please let us know the number of your Software
Maintenance and Support Agreement.

8.3 Locations for Keysight Technologies

Online assistance: http://www.keysight.com/find/assist

Should the Declaration of Conformity be required, please contact a Keysight Sales Representative, or the
closest Keysight Sales Office. Alternately, contact Keysight at: www.keysight.com.

25
This information is subject to change without notice.
© Keysight Technologies Finland, Ltd. 2019-2021
Published in Finland, March 15, 2021
NTE00000A-90000
www.keysight.com