Configuring the Machines

Resonate RFID Reader Management 2.0 Software Installation Guide

Before installing Resonate RFID Reader Management, you must configure the machines (nodes) that you intend to use. You must set up the Host network settings, time synchronization, DNS, and, if required, SSH. You must also ensure all required network ports are open. The

setup.sh

script of the Resonate installer will create and configure any Resonate-required groups, files/folders, user accounts, and permissions.

Host Setup

Configure the following Host network settings before installing Resonate RFID Reader Management:

Hostname

Static IP address (highly recommended), with a valid FQDN

Subnet mask. Note that for a multi-node deployment, all nodes must use the same subnet mask

Default gateway

Time Synchronization

The machines require time synchronization with a central Network Time Protocol (NTP) server to maintain consistent system time across the cluster and with the RFID readers. The Resonate server requires an NTP client that synchronizes with the same NTP server as the RFID readers. Install an NTP client if one is not already installed.

DNS

Configure DNS on the machine to enable communication with other Resonate RFID Reader Management components. The DNS server must be able to:

Resolve the hostname or FQDN of the Resonate RFID Reader Management cluster

Forward DNS queries to internet DNS servers to resolve public FQDNs (for example, the Zebra Artifactory repository required for an online installation)

SSH

To run CLI commands securely on the machine, you can set up SSH for remote access, although you can use any other method.

Network Ports

For Resonate software downloads/updates and communication with the RFID readers, the Resonate cluster requires some access permissions and some ports to be open.

Resonate RFID Reader Management Solution Architecture

For an online installation, ensure the server has access to the destination and port shown in the following table. This is the Docker registry that serves all Resonate Service container images.

Docker Registry
Destination Host	Destination IP	Destination Port
resonate-doc-rel.artifactory-us.zebra.com	35.201.100.70	443

For Resonate software and RFID reader communication, open the following Resonate server ports.

Server Ports
Source	Destination	Protocol and Port number	Description
Passive RFID Reader	Resonate server	HTTPS/TCP port 443	Needed for the Resonate software to deploy, manage, and configure the readers.
SSH client	Resonate server	TCP 22	Needed for an installer or maintainer to get access to the system.
Browser – Resonate web client	Resonate server	TCP 443	Needed for establishing HTTP/HTTPS client connections between the web client and the Resonate server.

For communication between the nodes in a multi-node configuration, open the following ports on each of the machines intended for the cluster; this table is from the MicroK8s documentation at https://microk8s.io/docs. For information on how to open the ports, refer to Microk8s Multi-Node Firewall Documentation; for information about these services, refer to Services and ports in the MicroK8s documentation.

Required Ports
Port	Service	Access Restrictions
16443	API server	SSL encrypted. Clients need to present a valid password from a static password file.
10250	kubelet	Anonymous authentication is disabled. X509 client certificate is required.
10255	kubelet	Read only port for the Kubelet.
25000	cluster-agent	Proper token required to authorise actions.
12379	etcd	SSL encrypted. Client certificates required to connect.
10257	kube-controller	Serve HTTPS with authentication and authorization.
10259	kube-scheduler	Serve HTTPS with authentication and authorization.
19001	dqlite	SSL encrypted. Client certificates required to connect.
4789/udp	calico	Calico networking with VXLAN enabled.

Groups

The

setup.sh

script creates the following group:

MicroK8s

. If the group already exists, the script will use it. The script also creates and adds the user

trif-user

to this group.

To give users administrative access to the nodes in the cluster on Linux, add the users to the

MicroK8s

group. This gives the users the same administrative privileges as

trif-user

After a multi-node deployment, the group will exist on all the nodes. You only need to add the users to the primary node.

File/Folder Permissions

The

setup.sh

script creates the following files/folders, depending on the deployment, and assigns the required permissions to the user

trif-user

. These files/folders should have the following permissions:

Folder and File Permissions
Folder/File	Permission
/opt/zebra/trifecta	drwxr-xr-x. (trif-user:trif-user)
/data/volumes	drwx--x--x. (root:root)

For a multi-node deployment,

/opt/zebra/trifecta

is only needed and created on the primary node;

/data/volumes

is not needed nor created.

User Accounts and Permissions

When creating accounts and adding permissions, your system will automatically have the following two users. Do not add them manually.

Account Users
User	Privilege	Group	Description
root	root	wheel/root	Service account used to configure the system and install all prerequisites. This user is already present on Linux systems.
trif-user	Resonate service account	MicroK8s	Service account used for installation, configuration, and operation of the Resonate software. The setup.sh script of the Resonate installer creates and configures the user trif-user . In a multi-node deployment, the script only adds the user on the primary node.