Ray3 Man en

User manual
RAy3 Microwave Link

.
fw 1.1.1.0
2020-12-14
version 1.9
RACOM s.r.o. | Mirova 1283 | 592 31 Nove Mesto na Morave | Czech Republic
www.racom.eu
Tel.: +420 722 937 522 | E-mail: [email protected]
Table of Contents
Legal Notice ........................................................................................................................................ 5
Quick guide ......................................................................................................................................... 7
1. Product .......................................................................................................................................... 10
1.1. Main characteristics ............................................................................................................ 10
1.2. Mechanical interfaces ......................................................................................................... 12
1.3. Ethernet + power interfaces ............................................................................................... 15
1.4. Service interfaces ............................................................................................................... 20
1.5. Status LED ( S ) ................................................................................................................. 23
1.6. Sizes, packaging and labeling ............................................................................................ 24
1.7. Ordering codes ................................................................................................................... 30
2. Accessories ................................................................................................................................... 35
3. Step-by-step Guide ....................................................................................................................... 36
3.1. Service access ................................................................................................................... 39
3.2. Basic link configuration ....................................................................................................... 46
3.3. Link test .............................................................................................................................. 46
4. Installation ..................................................................................................................................... 48
4.1. Line of sight test ................................................................................................................. 48
4.2. Antenna mounting .............................................................................................................. 48
4.3. RAy unit mounting .............................................................................................................. 52
4.4. Connectors assembly and disassembly ............................................................................. 57
4.5. Grounding and overvoltage protection ............................................................................... 61
4.6. Power supply ...................................................................................................................... 66
4.7. Start up ............................................................................................................................... 69
5. Configuration ................................................................................................................................. 76
5.1. Introduction ......................................................................................................................... 76
5.2. Status bar ........................................................................................................................... 77
5.3. Status ................................................................................................................................. 79
5.4. Link settings ....................................................................................................................... 84
5.5. Switch settings ................................................................................................................. 103
5.6. Tools ................................................................................................................................. 142
5.7. Help .................................................................................................................................. 166
6. Command Line Interface ............................................................................................................. 169
6.1. Connection via CLI ........................................................................................................... 169
6.2. Working with CLI .............................................................................................................. 170
6.3. Configuration with CLI ...................................................................................................... 172
7. RAy Tools app for Mobile devices ............................................................................................... 174
7.1. Menu options .................................................................................................................... 175
7.2. Application availability ...................................................................................................... 176
7.3. Feedback to RACOM ....................................................................................................... 177
8. Troubleshooting ........................................................................................................................... 178
9. Technical parameters .................................................................................................................. 181
9.1. General parameters ......................................................................................................... 181
9.2. RAy3-17 parameters ........................................................................................................ 185
9.3. RAy3-24 parameters ........................................................................................................ 189
10. Safety, environment, licensing ................................................................................................... 193
10.1. Regulations .................................................................................................................... 193
10.2. Safety distance ............................................................................................................... 194
10.3. Professional installation .................................................................................................. 194
10.4. RoHS and WEEE compliance ........................................................................................ 195
10.5. RACOM Open Software License .................................................................................... 197
10.6. Warranty ......................................................................................................................... 197
© RACOM s.r.o. – RAy3 Microwave Link 3

RAy3 Microwave Link
10.7. Declarations of Conformity ............................................................................................. 198

10.8. FCC and IC authorization ............................................................................................... 202
10.9. Country of Origin Declaration ......................................................................................... 203
A. SSH key generation .................................................................................................................... 204
B. Unit block diagrams .................................................................................................................... 205
Index ................................................................................................................................................ 206
Revision History .............................................................................................................................. 209
List of Tables
1.1. LED status indicators ................................................................................................................. 23
1.2. Overview of Jirous Class 2 and Class 3 antennas ..................................................................... 28
1.3. Overview of LEAX-RAy antennas .............................................................................................. 28
1.4. Capacity keys code scheme ...................................................................................................... 32
1.5. Upgrade keys code scheme ....................................................................................................... 33
9.1. Parameters 1 ............................................................................................................................ 181
9.2. Parameters 2 ............................................................................................................................ 182
9.3. Link speed - raw link ................................................................................................................. 183
9.4. Link speed - Ethernet (according to RFC 2544) ....................................................................... 183
9.5. Frequency limits - 17 GHz ........................................................................................................ 185
-6
9.6. Radio parameters - 17 GHz, BER = 10 ................................................................................. 185
9.7. ACM switching - 17 GHz according to MSE state .................................................................... 187
9.8. Frequency tables 17 GHz ........................................................................................................ 188
9.9. Frequency limits - 24 GHz ........................................................................................................ 189
-6
9.10. Radio parameters - 24 GHz, BER = 10 ............................................................................... 189
9.11. ACM switching -24 GHz according to MSE state ................................................................... 191
9.12. Frequency tables 24 GHz ...................................................................................................... 192
10.1. Minimum Safety Distance 24 GHz ......................................................................................... 194
4 RAy3 Microwave Link – © RACOM s.r.o.

Legal Notice
Legal Notice
Copyright
© 2020 RACOM. All rights reserved.

RACOM s. r. o. (further referred to under the abbreviated name RACOM) is the sole author and owner
of all rights to this User manual. Same apply for other materials and documentation relating to RACOM
products. It is prohibited to make written, printed or other copies of this User manual and related product
documentation or records on various media or translate any part of this manual into other languages
(without the written permission of the rights owner).
Products described in this User manual may contain software proprietary to RACOM and its use is
governed by RACOM Open Software License. The offer of supply of these products and services does
not include or infer any transfer of ownership. No part of the software or documentation or information
supplied may be divulged to any third party without the express written consent of RACOM.
Disclaimer
These materials and information are provided “as is” without warranty of any kind, either expressed or
implied, including but not limited to, the implied warranties of merchantability, fitness for a particular
purpose or non-infringement. Although every precaution has been taken in preparing this information,
RACOM assumes no liability for errors and omissions, or any damages resulting from the use of this
information.
This User manual contains links to the RACOM website and to other entities outside control of RACOM.
All links are intended solely to speed up the operation of the manual and improve user comfort. RACOM
shall not be liable for the timeliness, availability or content of such websites and shall not be liable for
any damages or consequences resulting from access to or use of such websites.
This document or the equipment may be modified without notice, in the interests of improving the
product or the information about it.
Suppliers, and other parties involved in creating and delivering described product shall not be liable
for any special, indirect, incidental, or consequential damages, including lost revenues or lost profits.
Trademark
All trademarks and product names are the property of their respective owners.
Important Notice
• Due to the nature of wireless communications, transmission and reception of data can never be
guaranteed. Data may be delayed, corrupted (i.e., have errors), or be totally lost. Significant delays
or losses of data are rare when wireless devices produced by RACOM are used in an appropriate
manner within a well constructed network.
Conditions of use
• Equipment mentioned in this manual may only be used in accordance with instructions contained in
this manual. Error-free and safe operation of this equipment is only guaranteed if this equipment is
transported, stored, operated and controlled in the proper manner. The same applies to equipment
maintenance.

Legal Notice
• RACOM wireless communication device should not be used in situations where failure to transmit
or receive data could result in damage of any kind to the user or any other party, including but not
limited to personal injury, death, or loss of property.
• RACOM products are not developed, designed or tested for use in applications which may directly
affect health and/or life functions of humans or animals, nor to be a component of similarly important
systems, and RACOM does not provide any guarantee when company products are used in such
applications.
• The radio equipment can only be operated on frequencies stipulated by the body authorised by the
radio operation administration in the respective country and cannot exceed the maximum permitted
output power. RACOM is not responsible for products used in an unauthorised way.
• In order to prevent damage to the radio modem and other terminal equipment the supply must always
be disconnected upon connecting or disconnecting the cable to the radio modem data interface. It
is necessary to ensure that connected equipment has been grounded to the same potential.
Limitation of responsibility
• RACOM accepts no liability for damages of any kind resulting from delays or errors in data transmitted
or received using RACOM wireless communication device, or its failure to transmit or receive such
data.
• Under no circumstances is RACOM or any other company or person responsible for incidental, acci-
dental or related damage arising as a result of the use of this product. RACOM does not provide the
user with any form of guarantee containing assurance of the suitability and applicability for its applic-
ation.
Product changes
• The radio equipment described in this manual may be modified by RACOM without notice, in the
interests of improving the product. RACOM will apply the reasonable effort to describe product
changes in this manual as soon as possible.
• The production of the radio equipment may be postponed or discontinued by RACOM without prior
notice.
• The radio equipment hardware, firmware and software can't be changed or modified by a user or
any other third-party. Only officially distributed firmware from RACOM is allowed to be installed on
the equipment.
Important
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.

Quick guide
Quick guide
1. Delivered items 2. Accessories
3. Power supply 4. Configuration
Accessing units
- Default IP addresses for Ethernet access: 192.168.169.169/24 (L unit) and 192.168.169.170/24 (U unit)
- Default IP address for USB/WiFi or USB/Eth access: 172.17.17.17/24 (both units)
Ethernet access - set computer IP address within the range 192.168.169.1-255. USB/WiFi or USB/Eth access - IP address
set automatically by DHCP (enabled by default, can be disabled in unit management). Recommended USB adapter must be
plugged in to the unit. Default WiFi setting is without any password (recommended is to set one immediately).
- Web browser access to management: - Antenna Alignment Tool:

http://172.17.17.17 (both units, USB/WiFi or USB/Eth) http://172.17.17.17/tk (both units, USB/WiFi or USB/Eth)
or http://192.168.169.169 (L unit, Ethernet) or http://192.168.169.169/tk (L unit, Ethernet)
or http://192.168.169.170 (U unit, Ethernet) or http://192.168.169.170/tk (U unit, Ethernet)
Defaults: Username: admin, Password: admin no Username or Password is required for Tool
Secure HTTPS access can be optionally used instead (use „secured version“ below main entry to the management and then
accept the https security certificate issued by RACOM).
If the units are linked to each other, the status indicator in management interface states “OK” and status LED lights
green. If not, utilize the antenna alignment (see pict. 10 and Antenna Alignment Tool above).
Configuration and backup of basic parameters

- Set bandwidth, channels, modulation, power, IP addresses (do not use the default ones), Access channels (ssh, https..).
- Change the password, restart both units and check the link status (to verify that the parameters are saved correctly).
- Backup the configuration in the Tools / Maintenance / Backup / Settings menu. Store the backup file to your PC.

Quick guide
5. Bracket and antenna 6. Unit lubrication and installation
7. Unit polarization 9. Power grounding and connections
8. Sealing

Quick guide
10. Directing antennas 11. RSS measurement

Product
1. Product
1.1. Main characteristics

RAy3 microwave units work as a point-to-point link in a full duplex setting with transfer speeds of up
to 1002 Mbps.
Supported are 2 license-free bands 17 GHz (17.10 – 17.30 GHz) and 24 GHz (24.00 – 24.25 GHz).
Bandwidth can be configured from 3.5 up to 112 MHz, independently for Tx and Rx. Modulation can
be fixed or adaptive and can be adjusted from QPSK to 4096QAM. QPSK modulation could be on the
fly (without data loss) strengthened for higher receiver sensitivity by extremely robust FEC – such
modulation is marked as QPSK-S (S means “strong”). RAy3 microwave links operating in 17 and 24
GHz bands can also be operated as a Short Range Device (SRD).
This link is formed by two RAy units, each equipped

by its own parabolic antenna and accessories to be
fully operational.
Hardware concept
RAy product line has been designed to have minimum

possible number of hardware variants. Upgrade of
functionality does not result in on-site hardware
changes– everything is done by activating software
feature keys (see Section 1.7, “Ordering codes” and
Chapter 5, Configuration).
HW models are determined only by frequency bands,

because both RAy units have identical hardware.
Transmitting and receiving channels are freely defined
by software and technically separated from each other
by cross polarization. Fig. 1.1: RAy3 – Microwave link
Cross polarization means that one side of the link

uses one polarization for transmission (e.g. horizontal) and the opposite polarization for receiving (e.g.
vertical). The other side of the link is turned by 90°. Therefore it transmits and receives using opposite
polarization with respect to the second unit. Practical result for users is that RAy units for 17 and 24
GHz must be mounted with reverse polarity on both ends of the link.
Note
All units for selected band are hardware identical. Default factory settings for each RAy in the
pair use different channels for L and U unit, so the link could be established by using default
radio parameters.
Ethernet concept
RAy links are transparent for IP and UDP Ethernet traffic. Practically all protocols pass through including
MPLS, RSTP (BPDU frames) and many others, except following:
• Management packets targeted for RAy units itself

Product
• Special packets for protocols explicitly mentioned in this manual, which are somehow processed by
RAy units (like PTP)
• Packets, which did not went through and were discarded due to capacity limitation and/or policy rules
(e.g. PIRL, QoS, EGRES shaping ...)

Product
1.2. Mechanical interfaces

This chapter describes basic properties of each RAy unit, which are important for its mechanical install-
ation: antenna waveguide, unit fixing (screws, etc.) and unit grounding (screw + cable). Other interfaces
(for data, power and service purposes) are described in next chapters Ethernet + power interfaces and
Service interfaces.
1.2.1. Antenna waveguide
Antenna waveguide flange on RAy unit (located across the holder) ensures perfect microwave connection
between the unit and the antenna.
RAy3 link requires use of external parabolic antenna for each RAy unit – both for physical mounting
1
as well as for the wireless transmission itself. Parabolic antennas from different producers are available.
Fig. 1.2: Waveguide pivot and flange
Important
Before assembling RAy unit with antenna, always carefully lubricate both antenna waveguide
pivot and RAy waveguide flange with thin layer of silicone grease to prevent the damage of
O-ring and surfaces. Pivot fits smoothly in to the flange, if it is properly lubricated. A box with
silicone grease is packaged with each delivery of new units - see Section 1.6.3, “Packaging”.
Note
If O-ring is injured or damaged, please exchange it immediately for a new one (size 22x2 mm,
type 'FPM80'), otherwise moisture + dust can leak into the waveguide and emitter. It may
eliminate several dB of signal and cause a corrosion.
1
https://www.racom.eu/eng/products/microwave-link.html#accessories_antennas

Product
1.2.2. Unit mounting
RAy unit is mechanically fixed to the antenna by 4× M8 screws (one per each side of RAy unit).
Installation and basic adjustment of the antenna is described in the Section 4.2, “Antenna mounting”.
Attaching RAy unit to it by 4× M8×30 (Allen) screws delivered with each antenna or each mount kit is
described in the Section 4.3, “ RAy unit mounting”. For adjusting the exact antenna direction see Sec-
tion 4.7.2, “Directing antennas” .
Fig. 1.3: Antenna and RAy3 unit
1.2.3. Grounding screw
Grounding screw is used for a proper grounding of the RAy unit, which
is necessary for its function (ensured by galvanic connection to the
grounded mast through a grounding cable).
One M8 screw (with standard 6-edge head) is delivered with each RAy
unit. Grounding screw has two possible positions (two holes) to be
mounted in. Those are located near the left and right fixing screws of the
RAy unit and both are marked by a yellow grounding symbol and both
are equivalent (second hole remains unused). For more information
about unit grounding see Section 4.3.3, “ RAy unit grounding”. Fig. 1.4: Grounding screw
Note
Grounding screw function is to ensure proper grounding of the RAy unit (by a grounding cable),
not for mechanical fixing of the unit.

Product
1.2.4. Pressure equalization
Pressure equalization between outside and inside of RAy

unit is an important technical requirement. It is realized by
a small plastic screw next to ETH2 label. It ensures the
pressure equalization without letting moisture or humidity
to enter the unit.
Important
Do not manipulate or remove this small plastic

screw. It is part of the cabinet and its manipulation
or a deformation can damage the water protection
of the unit.
Warranty does not apply for units with this screw

missing or deformed.
Fig. 1.5: Pressure equalization screw

Product
1.3. Ethernet + power interfaces

This chapter describes interfaces for user data transfer and power sourcing of the unit, as described
on the picture and characterized in the table below. Remaining interfaces for service purposes are
described in next chapter Service interfaces.
Fig. 1.6: Slots ETH1+POE, ETH2
Slot Function
Gigabit metallic Ethernet + Power over Ethernet (PoE) port
This port is capable of powering the unit with any PoE power source working ac-
ETH1+POE cording to IEEE 802.3at standard.
Passive PoE from 20 to 60 V is supported (if DC input is required, it could be injec-
ted through this connector - the voltage range is identical: from 20 to 60 V).
Slot for user exchangeable SFP module
A wide range of fibre optics Ethernet modules is available. Both single or dual
mode transceivers can be used. SFP module with metallic RJ45 interface can also
be used.
ETH2
The SFP LED
Located on SFP, just next to connectors. It is controlled by SFP module. Its function
is specific for each SFP module. The typical behavior is an indication the received
signal from the optical or metallic link to be within operational range.
Note
A set of all necessary bushing parts are delivered with each RAy unit - see a description of
2
this standard basic accessory ACS-RAy3 . Additional bushing options for installation of longer
connectors or other equipment are available as well. For bushings installation see Section 4.4,
“Connectors assembly and disassembly”.
Important
All bushings and plugs (including the original plugs in the flanges) must be fitted with O-rings
and carefully tightened. Otherwise, the unit is not protected against moisture intake through
connectors and cannot offer guaranteed functionality.
2
https://www.racom.eu/eng/products/microwave-link.html#accessories_kit

Product
1.3.1. RJ45 connector (ETH1+POE)
RJ45 socket connector marked „ETH1+POE“ is a standard

10/100/1000Mbps metallic Ethernet port. One plastic RJ45
plug for CAT5e and CAT6 cables is delivered with each
3
RAy unit (within item ACS-RAy3 ), ready to be punched
to an Ethernet cable.
Higher quality and CAT7 compatible RJ45 plugs are
available from RACOM as well – see for example item
4
CON-RJ45-CAT7 .
This port can be optionally used for power sourcing the

unit by PoE (Power over Ethernet). Both an active PoE
power supply (compliant with at least IEEE 802.3at stand-
ard known also as „PoE plus“) and a passive PoE power
supply (with voltage range 20-60 V) are supported.
Technical parameters of PoE power input:
Supported voltage range is 20 to 60 V, both polarities

are supported. For RAy unit booting the minimum re-
quired voltage is 21 V (to prevent booting with discharged Fig. 1.7: RJ45 Ethernet connector
24 V battery).
It is possible to use all 4 Eth pairs (8 pins) or only 2 Eth pairs (4 pins). Use:
• either 4,5 (V+) and 7,8 (V-) or opposite +/- DC polarity
• or 1,2 (V+) and 3,6 (V-) or opposite +/- DC polarity
• or both simultaneously (with all combinations of +/- DC polarities supported)
All contacts of RJ45 connector are galvanically separated from RAy unit. It ensures galvanical separation
5
for any kind of PoE power supply as well as for DC power sourcing (made through OTH-DC/RJ45 ).
More information about usage and installation of available power options can be found in Section 4.6,
“Power supply” and Section 4.5, “Grounding and overvoltage protection”.
3
4
https://www.racom.eu/eng/products/microwave-link.html#accessories_cable
5
https://www.racom.eu/eng/products/microwave-link.html#accessories_poe

Product
1.3.2. SFP slot (ETH2)
„ETH2“ is a standard SFP slot for 10/100/1000 Mbps Eth-

ernet SFP modules, user exchangeable. Both fibre optic
and metallic Ethernet SFP modules are supported. For
optical both single and dual mode fibre optics Ethernet
modules (= 2 or 1 fibres) can be used. CSFP modules are
not supported. RACOM offers all mentioned types of SFP
modules, tested to be RAy compatible as a standard ac-
6
cessory .
The SFP status LED is located just next to the slot. It is

controlled by SFP module. Its function is specific for each
SFP module. The typical behavior is an indication the re-
ceived signal from the fibre optic or metallic link to be
within operational range.
Note
Fig. 1.8: SFP slot
It is strongly recommended to use a high quality
SFP module with industry temperature range. The
7
SFP modules listed in Accessories are thoroughly tested by RACOM and are guaranteed to
function with RAy units. It is possible to use any other SFP module with power consumption
up to 1.25 W, but RACOM cannot guarantee their complete compatibility with RAy units.
Important
SFP module has to be inserted to out-of-power unit, otherwise its function is unpredictable
and the module and/or the RAy unit can be damaged.
Do not remove the smaller plastic screw next to ETH2 label. It is part of the cabinet and assures
pressure equalization outside and inside.
6
https://www.racom.eu/eng/products/microwave-link.html#accessories_sfp
7

Product
1.3.3. DC power (using ETH1+POE)
Direct DC power source can be used to power the RAy3 unit.

Instead of standard DC connector the DC cable is mounted to
8
a terminal block on DC/RJ45 adapter (item OTH-DC/RJ45 ).
The adapter is then fitted in to the RJ45 connector in slot
ETH1+POE.
9
Item OTH-DC/RJ45 is orderable with the unit (see Sec-
tion 1.7.1, “ RAy units”). It is equipped by 2 terminals (each min
2
2 A / 1.5 mm / AWG 14) with screws to ensure perfect connec-
tion with cooper DC power cable.
Internal RJ45 pins wiring of DC/RJ45 adapter utilizes all
8 contacts on RJ45 and is:
• DC terminal (+) RJ45 pins: 1,2,4,5

• DC terminal (-) RJ45 pins: 3,6,7,8
• RJ45 shield floating (not connected to any pin)
Supported voltage range is 20 to 60 V, both polarities are sup-

ported. The minimum required voltage for RAy unit booting is Fig. 1.9: Power supply connector
21 V (to prevent booting with discharged 24 V battery). Maxim-
um long-term voltage on RAy unit is recommended to be below 58
V (to ensure over-voltage protection inside the unit stays deactiv-
ated). Power input is galvanic separated inside RAy unit.
Optional grounding of DC cable should be connected directly to the

mast or to the Grounding screw on RAy chassis, to ensure proper
grounding of the cable. For grounding to the mast use suitable
10
grounding kit – for example see Grounding in section Accessories.
More information about DC power sourcing installation can be found

in Section 4.6, “Power supply”.
Fig. 1.10: DC-RJ45 adapter
Fig. 1.11: Power via DC-RJ45 adapter
8
https://www.racom.eu/download/hw/ray/free/eng/07_prislusenstvi/OTH-DC-RJ45.pdf
9
10
https://www.racom.eu/eng/products/microwave-link.html#accessories_zemneni

Product
Note
DC-RJ45 adapter occupies ETH1+POE port. When used, Ethernet connection to the unit has
to be made through SFP module inserted in to ETH2 port. Standard SFP modules for fibre
optic Ethernet or for metallic Ethernet (with RJ45 connector) can be used - see Accessories /
11
SFP modules for more details.
Fig. 1.12: SFP possibilities when direct DC power is used
Other valid possibility how to power the unit using DC power source is to use passive PoE in-
jector or active PoE power supply with DC input and deliver the power to RAy3 unit over PoE
through Ethernet cable with RJ45 connector plugged in to ETH1+POE slot as described in
Section 1.3.1, “RJ45 connector (ETH1+POE)”.
11

Product
1.4. Service interfaces

Slot „S“ stands for "Service". It contains system connectors – standard USB port and a pair of contacts
for RSS voltage output (red + gray ones). Also HW button and Status LED are located there.
Fig. 1.13: Slot S
Slot Function
USB service connector
For USB/WiFi or USB/ETH adapters, see Section 1.4.1, “USB connector ( S )”
RSS voltage output
Red and green connectors (for example 0.547 V means RSS = –54.7 dBm),
see Fig. 1.17, “RSS voltage contacts”
S HW button
For service purposes: Internal backup or Factory settings,
see Section 5.6.1, “Maintenance”
Status LED
Visible through semitransparent plug,
see Section 1.5, “Status LED ( S )”

Product
1.4.1. USB connector ( S )
USB-A port is designed for access to RAy management through

USB/WIFI adapter or USB/ETH adapter plugged in to. More
information about installation and configuration of available
adapters can be found in Quick Guide and in Section 5.4.3,
“Service access” (part “USB Accessories”).
Note
Only RACOM recommended adapters are supported.

12
See USB adapters on RAy Accessories web site.
1.4.2. Service WiFi - optional (using USB „S“)
Each RAy3 unit is equipped with the service WiFi interface from
the factory. It is realized by standalone WiFi module inserted Fig. 1.14: USB connector
in to the USB connector in slot "S". WiFi can be used solely for
unit management (no user traffic can be transmitted by using
this WiFi connection).
WiFi module can be disabled in FW (WiFi module is out of power

then) or manually unplugged. In both cases the results are
identical - no WiFi is possible. Management of the WiFi port is
described in Section 5.4.3, “Service access” (part “USB Ac-
cessories”).
Fig. 1.15: USB WiFi adapter
1.4.3. Service Ethernet - optional (using USB „S“)
RAy3 unit can be equipped with the service Ethernet interface

as an option. It can be used solely for unit management (no
user traffic can be transmitted using this Ethernet connection).
13
Optional Eth adapter (ordering code OTH-USB/ETH-XA ) can
be inserted in to the USB connector in slot "S" (instead of WiFi
module). Management of this Ethernet port is described in
Section 5.4.3, “Service access” (part “USB Accessories”).
Fig. 1.16: Ethernet adapter
12
https://www.racom.eu/eng/products/microwave-link.html#wifi-adapter
13
https://www.racom.eu/eng/products/microwave-link.html#wifi-adapter

Product
1.4.4. RSS voltage contacts ( S )
RSS voltage output connectors are located in slot „S“ aside

USB connector. This pair of contacts (red + green ones) al-
lows to connect a voltmeter (pin diameter 2 mm) to the RAy
unit and measure RSS value transformed to the voltage out-
put.
RSS (Received Signal Strength) is a basic parameter used

for directing antennas to the optimal direction. RSS output
voltage is calibrated to be proportional to actual RSS dBm
(for example 0.547 V means RSS –54.7 dBm). Thus a
standard digital voltmeter allows to see RSS value in a digital
form interactively during the antenna alignment. More inform-
ation about RSS voltage output usage is in Section 4.7.2,
“Directing antennas” (part “Voltmeter”) together with several
alternative ways to get this value by other methods.
1.4.5. HW button ( S )
Fig. 1.17: RSS voltage contacts
It is located in a small hole next to USB connector. It can be
pushed by any tiny blunt thing with the diameter up to 2 mm.
Its length has to reach about 7 mm in to the hole. (It can be
ball pen cartridge – both ends work on the thin one, match,
toothpick, etc.).
Important
Usage of very sharp things for pushing the HW but-

ton (like needle, edge clip etc.) may destroy the
contact inside RAy unit! Such a button destruction
is not covered by warranty.
The button supports multiple functions, which are activated

dependent on the state of the unit when the button is pushed
Fig. 1.18: Service interfaces
and the length of the push:
Action to be performed Unit status Button pushed SYS LED indication

Restore Normal For 5 seconds Flashes Green
internally temporary stored operation
customer settings
Applying Out of power Pushed before power on, Flashes Red (delayed after
Default settings released after SYS LED power on, for a duration of 5
to Local unit, then reboot stops flashing red seconds)
Entering the Out of power Pushed before power on, Flashes Red (delayed after
Service mode. released when SYS LED power on)
(Please, exit this mode starts flashing red
by powering off the unit)
Note
Those actions and their use are described in detail in Section 5.6.1, “Maintenance”.

Product
1.5. Status LED ( S )

RAy3 unit is equipped with one LED indicator located inside
the housing of the FOD unit in slot „S“ (during normal opera-
tion covered by semi-transparent plug). Meaning of the color
combinations of this LED indicator is:
Tab. 1.1: LED status indicators Fig. 1.19: Status LED
Green and
Function
Red LEDs
System is up and working OK
System reports warning or alarm,

which can be possibly repaired by user
System reports HW alarm
Unit is out of power or HW button pressed
Unit is starting

Product
1.6. Sizes, packaging and labeling
1.6.1. RAy3 unit
Outer sizes and weights for all RAy3 models are identical:
• Outer size: 245 × 245 × 160 mm
• Weight: 2.6 kg
Basic technical parameters like identification of the HW model, working frequency, maximum Tx power,
requirements for power supply, most important certifications, etc. are visible on RAy Production label.
All technical parameters are stated in detail in Chapter 9, Technical parameters.
1.6.2. Production label
The label contains identification of the HW model and its serial number, basic technical parameters,
most important certifications, QR code to manual, address of the producer, etc. Meaning of the most
important information listed on the production label is:
• Type – RAy3 product line identification (for details see Section 1.7, “Ordering codes” )
• Code – detailed identification of the unit HW (for details see Section 1.7.1, “ RAy units” )
• S/N – serial number, MW link consists of two separated units with two different serial numbers
• QR code – www link to the latest version of the User manual
• RF Power – maximum output power
• TX, RX freq – range of working frequency
• PoE – power supply characteristics
• CE, FCC ID, IC or other - available certifications
Fig. 1.20: Production label example
Important
The processor included in the unit variant S and X (identified by the item 'Code' on production
label and in the ordering code) uses an encryption module listed as 5A002 a.1 in the COUNCIL
REGULATION (EC) No 428/2009, setting up a Community regime for the control of exports,
transfer, brokering and transit of dual-use items. Units are subject to export control when ex-
14
porting outside the European union, according to national, EU and US law.
14
http://ec.europa.eu/trade/import-and-export-rules/export-from-eu/dual-use-controls/index_en.htm

Product
Note
A link should consist from a pair of “-L” and “-U” units (L and U are always a last letter in Code
printed on production label of each unit), but it is not mandatory (HW for L and U unit is
identical and L/U settings could be assigned by SW). Using L + U pair ensures all default settings
of both units match each other (including proper IP addresses as described in this manual). It
ensures the link is automatically established after factory defaults (to simplify initial setting of
the unit).

Product
1.6.3. Packaging
The RAy3 radio link is supplied in a package containing two separate boxes. Delivery includes:
• 2 pcs RAy3
15
• 2 pcs Cable bushing set ACS-RAy3 (bushings and connectors)
• 1 pc SILICONE GREASE
If only one unit is delivered, then delivery includes one piece of each item.
The unit is fixed in the box as follows:
Fig. 1.21: Packaging the RAy3 unit
Fig. 1.22: Initial arrangement Fig. 1.23: SILICONE GREASE capsule Ø45mm × 25mm
Note
Two separate boxes in the common package are turned such that both waveguides are
heading to each other. It allows to automatically establish a link between delivered RAy3 units
without unpacking them from the box. See Quick Guide, step 4 or Chapter 3, Step-by-step
Guide.
15

Product
Single unit packaging
• Outer size:
29 × 28 × 18 cm
• Weight:
RAy3-17 3.2 kg
RAy3-18 3.4 kg
RAy3-24 3.2 kg
Double unit packaging
• Outer size:
38 x 32 x 29 cm
• Weight:
RAy3-17 6.8 kg
RAy3-18 7.2 kg
RAy3-24 6.8 kg

Product
1.6.4. Supplied antennas
RAy3 units are ready for direct mounting to:

16 17
• Jirous Class 3 or Class 2 antennas (Jirous Antennas )
18 19
• LEAX-RAy Class 3 antennas (LEAX Arkivator Telecom )
Note
Jirous Class 3 antennas (type JRMC in Ordering code) smoothly replaced Jirous Class 2 an-
tennas (types JRMA or JRMB in Ordering code) in RACOM portfolio of antennas during
Q1/2020.
20
Individual datasheets with exact sizes and weights are accessible on RACOM website .
Standard antennas shipment is one antenna in its own box. RACOM is able to arrange more compact
shipment for a bigger amount of antennas (on a special request).
Tab. 1.2: Overview of Jirous Class 2 and Class 3 antennas
10, 11 GHz 17, 18 GHz 24 GHz

diameter gain diameter gain diameter gain
[m] [dBi] [m] [dBi] [m] [dBi]
- - 0.18 22.6 - -
0.4 28.0-30.5 0.4 34.6-35.6 0.4 36.8-37.4
0.7 33.6-36.0 0.7 38.6-40.0 0.7 41.7-42.0
0.9 36.5-37.5 0.9 41.0-42.5 0.9 44.0
1.2 39.5-41.0 1.2 44.6-44.8 1.2 46.0-46.6
1.8 43.0-44.0
Tab. 1.3: Overview of LEAX-RAy antennas
10, 11 GHz 17, 18 GHz 24 GHz

diameter gain diameter gain diameter gain
[m] [dBi] [m] [dBi] [m] [dBi]
0.3 30.1 0.3 34.7 0.3 36.9
0.6 35.2 0.6 39.7 0.6 42.0
0.9 38.5 0.9 43.5 0.9 45.4
1.2 41.0 1.2 45.2 1.2 47.9
16
17
http://en.jirous.com/
18
19
http://www.leax-arkivator-telecom.com/
20

Product
Andrew (Class 2 or 3 or 4) or traditional Arkivator antennas or antennas from other suppliers can also
21 22
be used, but they require an antenna mounting kit . Flexible waveguide is a general-purpose option
23
for any antenna usage. Contact us for available types and details.
1.6.5. Supplied accessories
Antennas and other accessories are necessary for RAy units to allow a proper functionality of the whole
microwave link.
RACOM always tries to ship all ordered accessories together with RAy units and antennas. Accessories
are mostly small items, so typical RACOM packaging is that all accessories are shipped on the same
palette with other material (within one additional RAy box).
21
22
23
https://www.racom.eu/eng/about_us/contact.html

Product
1.7. Ordering codes

All RAy3 models mentioned in this manual have their unique ordering codes. Available are also capacity
keys, feature activation keys and accessories necessary to reach expected functionality of the link. All
24
ordering codes are discussed in detail in this chapter and at RACOM web , and are available for
25
purchase at RACOM E-shop .
Note
Ask your supplier to ensure completeness of your product delivery for the individual link situation,
applicable spectrum regulations, local safety and security requirements, type of power sourcing,
grounding, etc.
Important
RACOM does not have any responsibility for improper use of any offered device. It is customers
full responsibility to check technical parameters of all ordered items and to use and configure
them in accordance with their purpose. It is also customers full responsibility to respect all
requirements applicable at the site of installation.
1.7.1. RAy units
RAy ordering codes begin with a string printed on Production label (9-11 characters long, lasting by „-
L“ or „-U“). It defines HW parameters and factory settings, which cannot be changed later on (like
working frequency, encryption HW acceleration, factory defaults and limitations built in to units in the
factory like limitation of Tx power or prevention to use any form of encryption). Rest of the ordering
code defines functionalities and options which could be added, erased or changed by a user later on
(like SW feature key for initial capacity or an optional DC power adapter).
Ordering Code structure:
Trade name + Gen. RAy3

Band Frequency band in GHz
Possible values: 17, 24
Var. Designation of product variant. More variants can be used within one
unit, i.e. more letters can be on this position. These variants are fixed
in unit HW and cannot be changed later on.
Possible values:
none – (position not used) – means same as X
E – no encryption HW installed
24
https://www.racom.eu/eng/products/microwave-link.html#order-codes
25
https://webservice-new.racom.eu/main/eshop.list

Product
N – no encryption HW installed, encryption will never be possible

(neither HW nor SW)
X – encryption HW installed - see export restriction below, MTU
10240 Bytes
S – encryption HW installed - see export restriction below, MTU
2048 Bytes (manufactured only until 3/2019)
R – reduced RF output power -30 to -15 dBm (always in combination
with E, N, X or S)
FRQ Lower / Upper frequency
Possible values:
L – unit transmits on lower part of the band
U – unit transmits on upper part of the band
Note
For RAy3-17 and RAy3-24 L/U indicates TX and other defaults,

which can be changed in management. Both lower and upper
units have the same HW.
SW keys If unit is ordered with SW keys, all keys are specified in this bracket.
SW key activates the Data speeds, which are under specific license.
SW key can be ordered independently for specific S/N anytime later
on.
Possible values: 360, 500, 1000
default is 360 Mbps, optional SW key for 500 or 1000 Mbps,
Part No’s.: RAy3-SW-360, RAy3-SW-500, RAy3-SW-1000
Optional accessories If unit is ordered with optional accessories, it is specified in this
bracket.
Possible values:
DC - DC/RJ45 power adapter, Part No.: OTH-DC/RJ45, is bundled
with the unit.
Type Specific product type for which type approvals like CE, FCC etc. are
issued.
Possible values: RAy3-17 , RAy3-24
Code Detailed HW identification of the unit printed on Production label on
the housing.
Note
SW keys and Optional accessories are not HW dependent

and can be installed or de-installed later on, so they are not
printed on Production label.
Important
The processor included in the unit variant S and X uses an encryption module listed as 5A002
a.1 in the COUNCIL REGULATION (EC) No 428/2009, setting up a Community regime for
the control of exports, transfer, brokering and transit of dual-use items. Units are subject to

Product
26
export control when exporting outside the European union, according to national, EU and
US law.
Note
The proper pair of Lower (L) and Upper (U) units should be selected when ordering the mi-
crowave link. Unit marked with L is set for transmission on lower frequency (and receive on
higher one), while unit marked with U is set for transmission on higher frequency (and receive
on lower one). This allows the link to be established without any initial manual settings – just
by powering up both units at factory defaults (see Quick Guide). The difference between L and
U code is only in default factory settings, which are different for each side of the link.
1.7.2. SW keys for capacity
RAy units allow to pay only for purchased transmission capacity (pay as-you-grow concept). Activation
27
keys could be purchased together with the unit or later at RACOM E-shop . Each key is generated
for specific S/N of the unit and the purchased capacity. Once installed, it unlocks all combinations of
channels and modulations up to the purchased capacity. SW keys could be erased or upgraded. See
Configuration / Feature keys for more details.
For allowed combinations of channel width and modulation for transmitting channel see Capacity SW
28
keys table . The Capacity feature key limit applies for transmitted data on the unit where the key is
installed. For asymmetrical capacity keys could be different for each side of the link.
Several types of SW feature key are available for RAy units:
• Bundled capacity (ordered together with RAy units - see previous chapter)
• Separately purchased capacity feature keys (see below)
• Upgrade capacity feature keys (see below)
Note
RACOM is able to generate customer specific Capacity feature keys on special request.
Separately purchased capacity feature keys
Keys purchased separately and installed by user.
Tab. 1.4: Capacity keys code scheme
26
http://ec.europa.eu/trade/import-and-export-rules/export-from-eu/dual-use-controls/index_en.htm
27
28
https://www.racom.eu/eng/products/microwave-link.html#scalability

Product
29
For ordering see RACOM E-shop .
Upgrade capacity feature keys
Keys purchased separately and installed by user.
Tab. 1.5: Upgrade keys code scheme
30
For ordering see RACOM E-shop .
1.7.3. SW keys for features activation
RAy units allow to pay only for purchased features (pay as-you-grow concept). Activation keys could
31
be purchased together with the unit or later at RACOM E-shop . Each key is generated for specific
S/N of the unit and the purchased feature (or a set of features). Once installed, a specific feature or
function of the unit is allowed. Feature keys could be erased or upgraded. See Configuration / Feature
keys for more details.
Available feature activation keys are listed in following table:
RAy3 Ordering codes for other feature keys

Ordering code Meaning Parameters Example
x: P = positive value RAy3-SW-TX-N15
Limitation of
RAy3-SW-TX-xyy N= negative value (limits Tx power to
Tx power
yy: value of limit in dBm -15 dBm)
RAy3-SW-AES Allow AES encryption - RAy3-SW-AES
ver 1.0
Note
Units with variant 'N' in the Code printed on Production label would never allow to use encryp-
tion, even if such a SW key is purchased and installed to the unit ('N' prevails).
29
30
31

Product
1.7.4. Tested Accessories
Ordering codes for all accessories offered by RACOM to allow a proper functionality of the whole mi-
32
crowave link are listed on Accessories section of RAy web site and they are available for purchase
33
in RACOM E-shop . More information about accessories can be also found in Chapter 2, Accessories.
Note
Please consult your supplier to ensure completeness of your product delivery for the individual
link situation, spectrum regulations, local security requirements, type of power sourcing,
grounding, etc.
32
https://www.racom.eu/eng/products/microwave-link.html#accessories
33

Accessories
2. Accessories
RACOM offers a complete set of accessories to operate RAy microwave units in all relevant use-cases
and environments. All accessories are selected and thoroughly tested by RACOM for compatibility and
are guaranteed to function with RAy units. There are only a very few accessories which has to be
purchased from RACOM to work properly - e.g. WiFi adapters (the reason is limited set of WiFi drivers
in RAy FW). Such an information is always part of accessory description. With most types of accessories
it is possible to use other components with same or similar functionality and temperature range, but
RACOM cannot guarantee they will be completely compatible with RAy units.
1
All accessories are listed on Accessories section of RAy web site and they are available for purchase
2
in RACOM E-shop .
Important
It is strongly recommended to double-check the main voltage and local installation standards
before purchasing accessories to ensure they comply with the accessory specifications and
that all safety regulations are complied with.
In particular, we recommend that you consult your local specialists for grounding, voltage
spikes, overvoltage protection and other equipment, ensuring a proper installation. For more
information see Section 4.5, “Grounding and overvoltage protection”.
Units and accessories should be installed by trained professionals (see Section 10.3, “Profes-
sional installation”).
The warranty does not apply to units damaged by voltage spikes or surges (see Section 10.6,
“Warranty”).
1
2

Step-by-step Guide
3. Step-by-step Guide
The following chapters will guide you step by step through preparation, installation and activation of
the RAy3 link:
• Pre-installation check out

• Installation (Chapter 4.)
• Advanced configuration (Chapter 5.)
• Troubleshooting (Chapter 8.)
Pre-installation Checklist
Default settings for L and U units are chosen to allow delivered units to automatically establish a link
without unpacking RAy3 units from the box. It is enough to open the boxes and power both RAy units
up (by PoE or DC power supplies). It allows users to comfortably set up basic parameters necessary
for the installation in the lab and thus shorten the time on the tower or roof to a minimum. Following
text provides a guide how to optimally arrange the workplace, how to setup the link and which parameters
are good to be set up before the installation outside.
Default factory settings define the initial link to be established on the most narrow channel, strongest
modulation and lowest available Tx power (in RAy3 case those are 3.5 MHz channel, QPSK_S modu-
lation and Tx power = -30 dBm). Complete default settings are described in section 10 Technical
parameters.
Note
RAy3 default factory settings allow to install both units on the mast and establish the short link
without prior manual configuration. Just the distance has to be very short due to Tx power set
to the minimum for the unit (-30 dBm on RAy3-17 and RAy3-24). Typically, Tx power has to
be increased to a reasonable level (or even to a maximum) before link alignment.
Fig. 3.1: Workplace for link testing and configuration

Step-by-step Guide
Take the following steps to link together both delivered RAy3 units and to establish a connection
between them and PC or tablet or mobile and perform a basic setup:
■ Open both boxes and double check that both RAy3 units are turned OK, so waveguides are heading
to each other.
■ Connect power sources (PoE or DC) to both RAy3 units (using slot ETH1+POE).
■ Wait about 30 seconds until both units boot up and the link is established. The green light should be
visible on both units through transparent plug on slot “S”. Until a WiFi password is set, red light
periodically flashes together with green light - see Section 1.5, “Status LED ( S )”.
■ Connect by WiFi or by Ethernet cable (plugged in to LAN input on PoE power supply or in to Eth port
on USB/ETH adapter) to one of those two units. Units linked together allow effectively set all IP ad-
dresses, passwords, security keys, feature keys, users, etc. from one side of the link.
○ If WiFi is used, then just select which WiFi to connect to. IP address of your PC or laptop is set
automatically by DHCP.
○ If Eth over USB port is used (through USB/ETH adapter OTH-USB/ETH-XA), IP address of your
PC or laptop is set automatically by DHCP as well.
○ If Eth connection to one of data ports on RAy3 (ETH1 or ETH2) is used, then the IP address on
your PC or laptop has to be set manually to establish a working connection. See Quick Guide for
the complete list of IP addresses to use.
○ Enter a web management of the unit and configure everything you like to change to be ready for
outside installation. Following parameters are typically set in this phase:
• IP addresses and VLANs
• passwords
• security keys
• feature keys
• users
• WiFi password and behavior
• Tx and Rx frequencies (if known in advance)
• Higher Tx power (to be ready for antenna alignment) – see section “Important” below
Note
• This setup can be used for link configuration, however full radio performance can't be expec-
ted (high modulations, full Tx power range, etc.) because standard conditions between units
(antenna interface, polarization planes, free space attenuation) are not met inside the box.
• High TX power does not lead to better RX signal quality, because the receiver input can be
saturated with too strong signal - see Overexcited receiver.
• Until a WiFi password is set, red light periodically flashes together with green light - see
Section 1.5, “Status LED ( S )”.
Important
• Maximum secure Tx power for RAy units inside the box is 0 dBm. Higher Tx power risks
the damage of sensitive input circuits!
• If you need to configure higher Tx power to be ready for antenna alignment during installation
on the mast, first you have to turn units in to position where waveguides are not heading to
each other, so reasonable attenuation is ensured. Secure is for example to put RAy units

Step-by-step Guide
in parallel in to a direction without any metal material in front of the microwave beams (it
could reflect waves back to units).
• Maximum time, that units can be powered up inside the box is 10 minutes (standard room
temperature expected). Longer time may lead to the unit overheat! If more time is needed
for configuration, units have to be unpacked from boxes.

Step-by-step Guide
3.1. Service access

The RAy3 link is supplied with a default configuration of access parameters:
For Ethernet access through RJ45 or SFP ports:

• Unit L has the service IP address 192.168.169.169 and mask 255.255.255.0
• Unit U has the service IP address 192.168.169.170 and mask 255.255.255.0
For WiFi or Ethernet access via USB/WiFi or USB/ETH adapter:
• Both units have service IP address 172.17.17.17 and mask 255.255.255.0
For Ethernet access through RJ45 or SFP ports an IP address has to be set on your PC that is within
the mask, e.g. 192.168.169.180. For WiFi or USB/ETH access an IP address for laptop or mobile or
tablet is set automatically by DHCP (enabled by default).
Then open the HTTP or HTTPS configuration interface, e.g. https://192.168.169.169 or ht-
tp://172.17.17.17
Access is allowed over HTTP, HTTPS or SSH.
The default username and the password is "admin" (it is strongly recommended to change it).
See Configuration / Link settings / Service access / USB accessories chapter for detailed information.
The Antenna Alignment Web Tool can also be used for antenna direction alignment. It can be accessed
via a web browser utilizing IP addresses with „/tk“ at the end (e.g. http://172.17.17.17/tk for WiFi or
USB/ETH adapter or http://192.168.169.169/tk or http://192.168.169.168/tk for ETH1/ETH2 ports).
When connection has been established, use the Service access menu to customize access parameters.
Default management IP addresses should be replaced with well-chosen operating addresses. Default
can lead to network problems later.
The menu contains parameters for the entire link, both for the Local and remote Peer units. If a connec-
tion has been established, both sets of parameters have been set. While working with an isolated unit,
only Local parameters are functional for the currently connected unit.
Note
If the link is OK and there are no parameters shown of the station Peer, it is necessary to click
on Refresh.
Follow the description of basic settings. Pictures in following sections show default factory settings for
L unit and RC info “rcinfo20_250_default:XXX”. Default settings for unit U (for opposite side of the link)
would be adequately exchanged. Values for other RCinfo may be different as well (differences typically
refer to frequencies and Tx power as they are allowed by authorities for the actual band and a region).
After entering values on the screen always save the content by clicking on Apply.

Step-by-step Guide
3.1.1. Choosing right band according the country of use
Menu Tools / Maintenance / Radio adaptation
First step is to set the right set of rules for the band according the region or country of use, so the unit
is compliant with the local regulation. Go to the menu according the picture below and set parameter
RCINFO accordingly.
Fig. 3.2: Menu Tools / Maintenance / Radio adaptation
For full explanation of all possibilities of this screen see the section called “Radio adaptation” in
Chapter 5, Configuration.

Step-by-step Guide
3.1.2. Setting units name and location
Menu Link settings / General
Not necessary settings. Anyhow it is beneficial to name the link and its location for easier identification
later on:
• Station name – station can be assigned with a name, e.g. the place of installation.
• Station location – for easier inclusion the network hierarchy, it is possible to enter the station’s location
Fig. 3.3: Configuration Menu Link settings / General
For full explanation of all possibilities of this screen see Section 5.4.1, “General”.

Step-by-step Guide
3.1.3. Setting Ethernet access parameters
Menu Link / Service access / Services
Those settings are necessary to make new units accessible within target Ethernet network. Typically,
all following parameters should be set according to both networks IP addressing, routing, planned access
methods for data and for management, etc.:
• IPv4 address – enter a valid IP address to access the unit. The default IP address has to be replaced
with a valid address. Keeping the default address will probably lead to future problems in the network.
• Netmask – enter the network mask.
• Gateway – if necessary, enter a gateway, otherwise leave blank
• Enable access protocols that you will need. For security reasons, do not enable more than is neces-
sary.
• HTTP(S) – allow access to the web interface.
• Telnet – enabling access to the CLI interface using telnet protocol.
• SSH – enabling access to the CLI interface using SSH protocol.
• Management VLAN – Enabling 802.1Q VLAN tag for separation of user and service operations.
• Management VLAN id – Defining 802.1Q VLAN tag for service operations.
Fig. 3.4: Configuration menu Link settings / Service access / Services
For full explanation of all possibilities of this screen see Section 5.4.3, “Service access” in Chapter 5,
Configuration.

Step-by-step Guide
3.1.4. Creation of users
Menu Link / Service access / Users
It is recommended to create user accounts managed by the main user already in this phase (for example
a user with rights limited to read-only access). Following actions are available:
• Edit - enter the menu.

• New password – choose a password and enter it.
• Confirm password – enter the password again to confirm.
Fig. 3.5: Configuration menu Link settings / Service access / Users
For full explanation of all possibilities of this screen see the section called “Users” in Chapter 5, Config-
uration.

Step-by-step Guide
3.1.5. Applying Feature keys
Menu Maintenance / Feature keys
The firmware of the microwave link is capable of controlling several features (for example the maximum
user data speed, maximum Tx power, etc.). It is recommended to install all separately purchased feature
keys prior to physical installation to allow all expected features of the link to be usable after the install-
ation.
Fig. 3.6: Configuration menu Tools / Maintenance / Feature keys
Note
Speed keys purchased with the unit are installed in the factory (and can be double checked
within this menu). Key for limited Tx power is not installed except specifically ordered. If RCinfo
limits the maximum power, it cannot be overruled by feature key with the higher Tx power.
For full explanation of possibilities of this screen see the section called “Feature keys” in Chapter 5,
Configuration.

Step-by-step Guide
3.1.6. WiFi settings
Menu Link / Service access / USB accessories
Go to menu Link Settings / Service Access / USB accessories and enter WiFi password or disable WiFi
completely. Standard settings are that Enable on Air link loss is ON (when the link is down, WiFi is
activated; when link is OK, WiFi will be deactivated in few minutes) and Force Enable is OFF (activates
WiFi permanently). Passphrase has to be set, otherwise the WiFi is unsecured and system warning is
active.
Fig. 3.7: Configuration menu Link settings / Service access / USB accessories
Note
If you access the unit over WiFi, do this step as last action before reboot (as the WiFi connection
will be interrupted and new connection with new password would be required to continue the
work).
For full explanation of possibilities of this screen see the section called “USB accessories” in Chapter 5,
Configuration.

Step-by-step Guide
3.2. Basic link configuration

Default radio parameters depend on the specific type of link and the specific channel allocation table.
Channels are typically set for smallest possible bandwidth in the lower part of the band. Radio defaults
also define QPSK modulation and low Tx power, so both units in the pair should connect each other
right from the box (or even inside a box). If there is no spectrum conflict with other equipment in the
room (or on sites later on) and units can "hear" each other, those parameters can be used as they are
and both units can be powered on. After boot (about 30 seconds) the link should be automatically es-
tablished.
If a change in the parameters is necessary, it can be done in the menu Link settings / Radio and saved
by clicking Apply. This applies, when the work is done simultaneously on both units, while they are
connected. Otherwise each unit has to be configured individually. When configuring units individually,
pay attention to correct settings of duplex pair for channels TX and RX. For example, if one station has
TX channel L1, then the second station must also have the channel RX L1.
3.3. Link test
Verify the functionality of the radio link:
• Switch in screen Status / Brief.

• Status Bar displays Link: Ok.
If the alarm message appears at Local or Peer, it doesn’t necessarily mean there is a problem. The
message indicates, that WiFi password was not set or the limit of any of the monitored parameters
has been exceeded. Essential is the "Link: Ok" message on the status bar.
• The Status screen contains values for both Local and Peer units. N/A next to Peer indicates that the
data from the Peer unit has not been transferred. If Link is Ok, simply click Refresh at the bottom of
the screen and Peer data will be updated.
• Menu Status / Detailed / Radio indicates link RSS and MSE values, in case of ACM also the selected
modulation and Netbitrate. If the ATPC function is enabled (menu Link settings / Radio) it also indic-
ates instantaneous / max. allowed power and for MSE and RSS values it indicates immediate / target
value size.
• Menu Tools / Live data / Bar indicators displays current size of RSS and MSE.
• Menu Tools / Programs / Ping allows you to send a ping test to the selected IP address.
Try out the possibility of modulation:
• Modulation ACM. In menu Link settings / Radio enable ACM. Set the TX modulation parameter to
the required maximum value. In menu Status / Brief / Radio you can monitor (Refresh or Start)
changes in used modulation based on the instantaneous MSE signal quality.
• To set a fixed modulation go to Link settings / Radio, switch off ACM and set the TX modulation to
a value from the range of QPSK through 256-QAM based on the results of the previous test. If you
choose modulation higher than allowed by MSE, the connection will be lost. Status Link will lose its
Ok value. Both units will need to be moved closer to resume the link. If this is not possible, use the
Ethernet to access each unit individually and set the basic modulation QPSK.
Verify the functionality of the entire link:
• If possible, connect user devices to both RAy units over PoE and test mutual communication.
• Another way of testing this is to connect a PC to the other unit and send a ping from one PC to the
other.

Step-by-step Guide
• The minimum variant of this test is to use an Ethernet cable connection from the PC connected to
the local RAy to the PC connected to the remote RAy and test communication between both units
over Ethernet. This will verify Ethernet functionality.
Prepare installation configuration:
• Bandwidth e.g. 3.5 MHz. To get the highest possible receiver sensitivity, set the bandwidth as narrow
as possible according to specific frequency band.
• TX channel: Use your allocated channel. If you do not have any allocated channel yet, use for example
channel L1.
• RX channel will setup automatically when channel lock activates.
• Set TX modulation QPSK to get the highest possible sensitivity.
• Set RF power according to selected antenna and according to individual frequency license. Set the
output power as high as possible.
• Set a new user access passwords.
• Record access parameters from the Service access menu, especially the IP addresses.
• Restart units by interrupting the power supply to verify that the parameters are stored correctly and
the link works.
After this preparation phase you can continue to install your devices in a working environment.

Installation
4. Installation
4.1. Line of sight test

Before you install the device to a mast tube, verify visually that the view in the direction of the remote
unit is unobstructed.
Line of sight considerations:
• Free Fresnel zones. Signal needs space wider than the diameter of the antenna.
• Trees at the lower end of the Fresnel zone. They will grow taller in a few years.
• Possible building development.
• Objects in the close proximity of the antenna such as edges of other antennas, their mounting racks,
edges of the roof.
d1
× ×
a a a a
F1 r a a a a
aaaaaaa aaaaaaa
aaaaaaa aaaaaaa
aaaaaaaaaa aaaaaaaaaa
a a a a a a a a
aaaaaaa aaaaaaa
a a a a a a a a
aaaaaaa aaaaaaa
aaaaaaa aaaaaaa
aaaaaaa aaaaaaa
Fig. 4.1: Fresnel zone
4.2. Antenna mounting

Antenna mounting depends on the antenna vendor, antenna type and the size of the chosen antenna.
The result of any antenna installation is that it is fixed to the mast, pointing to the right direction and its
waveguide and fixing screws are ready for mounting RAy unit to it.
Fig. 4.2: Antenna mounting

Installation
Fig. 4.3: Fixing screws
Common for all antennas is a holder which ensures:
• fixing of the antenna to the mast

• flexibility in two planes (necessary for antenna adjustment to the proper direction).
Each holder allows at least 2 methods of mounting antenna on the mast tube:
• right-side mounting
• left-side mounting
Following sections describe in detail installation of antennas, mounting kits and/or flexible waveguides,
so the antenna is ready for mounting RAy unit to it. Choose below a chapter relevant for your antenna
supplier and installation manual according to antenna type and size.
Note
Each antenna allows RAy unit to be mounted on it with horizontal or vertical polarization. This
is discussed in detail in Section 4.3, “ RAy unit mounting”.
4.2.1. Jirous antennas mounting
Mounting instructions for Jirous antennas are available on the manufacturer's website http://en.jirous.com.
1
Mounting is also described in detail on RACOM RAy download section:
2
• Installation of Jirous antennas ANT-JRM-inst.pdf
optionally with strut for 120 cm Jirous antenna
4 pcs M8×30 (Allen) screws to mount the RAy unit to the antenna are part of the antenna delivery.
1
https://www.racom.eu/eng/products/microwave-link.html#download
2
https://www.racom.eu/download/hw/ray/free/eng/04_anteny/ANT-JRM-inst.pdf

Installation
Note
1.2m Jirous antennas on windy sites (max wind speed above 50 m/s) has to be installed with
3 4
optional struts ANT-JRZ-1200-STRUT-F (fixed) or ANT-JRZ-1200-STRUT-A (adjustable).
5
Strut allows to increase operational wind speed (typically up to 65 m/s). Consult Jirous website
for exact parameters and additional info.
Ensure the pin lubrication is completed during assembly.
4.2.2. LEAX-RAy antenna mounting
Mounting instructions for LEAX-RAy antenna are shipped with each antenna. Identical mounting instruc-
6
tions are available within RACOM RAy download section, on our website. See list below:
7
• Installation of 0.3m antennas - ANT-LEAX-300-inst.pdf
8
9
10 11
optionally with standard strut ANT-LEAX-RAy-900-STRUT - ANT-LEAX-strut-std-inst.pdf
12
• Installation of 1.2m antennas - ANT-LEAX-1200-inst.pdf (includes standard strut)
13 14
optionally with extra strut ANT-LEAX-RAy-1200-STRUT - ANT-LEAX-strut-extra-inst.pdf
15
• Installation of RAy interface for LEAX-RAy antennas - ANT-LEAX-RAy-inst.pdf
(same for all sizes). The RAy interface is part of each LEAX-RAy delivery (one interface set per
antenna). It needs to be mounted to each antenna according to the instruction manual before
mounting the RAy unit. Four pcs M8x30 (Allen) screws to mount the RAy unit to the antenna are
also part of the antenna delivery.
Note
0.9m and 1.2m LEAX-RAy antennas on windy sites (max wind speed above 50 m/s) has to
16
be installed with optional struts . They allow to increase operational wind speed up to 65 m/s
(instead of 50 m/s respectively 55 m/s). They also allow to use tower pipe Ø50-120 mm (instead
17
standard Ø90-120 mm). Consult LEAX website for exact parameters and additional info.
4.2.3. Other antennas mounting

18
Antenna which do not have a direct interface to RAy needs also a proper antenna mounting kit or a
19
flexible waveguide with a mounting kit for it. Such interface has to be installed prior to RAy unit install-
ation to the antenna.
3
4
5
http://en.jirous.com
6
https://www.racom.eu/eng/products/microwave-link.html#download
7
https://www.racom.eu/download/hw/ray/free/eng/04_1_anteny/ANT-LEAX-300-inst.pdf
8
9
10
11
https://www.racom.eu/download/hw/ray/free/eng/04_1_anteny/ANT-LEAX-900-strut-inst.pdf
12
13
14
https://www.racom.eu/download/hw/ray/free/eng/04_1_anteny/ANT-LEAX-1200-strut-inst.pdf
15
https://www.racom.eu/download/hw/ray/free/eng/04_1_anteny/ANT-LEAX-RAy-inst.pdf
16
17
https://www.leax-arkivator-telecom.com/en/products/microwave-antennas.html
18
19

Installation
Antenna mounting kit can be ordered as an accessory part (one per antenna). It has to be chosen ac-
20
cording to selected band and antenna vendor - contact your local supplier or RACOM to check currently
available types. Any other antenna can be connected to the RAy by standard flexible waveguide. RACOM
21
offers mounting kits (RAy holders) for different flexible waveguides (see Accessories and the picture
Flexible waveguide).
Standard mechanical tools are enough to install each of those accessories.
Antenna mounting kit for standard Arkivator antennas
Items "ANT-ARK-KIT-xx" (where xx is the band) fits all traditionally produced Arkivator antennas (from
company Arkivator, acquired by LEAX Group) as well as today produced Arkivator antennas from
company LEAX Arkivator Telecom sold without RAy interface.
Note
All LEAX-RAy antennas listed in the RACOM portfolio contain specific RAy interface and thus
no mounting kit is required.
Antenna mounting kit for standard Andrew antennas
Items "ANT-ANW-KIT-xx" (where xx is the band) fits most of Andrew antennas manufactured by
CommScope with specific vendor's interface unmounted. All generations of RAy units (including those
for 17 and 24 GHz ones, which are using cross polarization) are OK with Single polarized Andrew
VHLP antennas with round waveguide. Dual polarized antennas can be used as well, but are typically
more expensive.
• for 17 GHz band use ANT-ANW-KIT-17/18 and order the following VHLP single-polarized antenna
types:
VHLP1-18-BW1 1 ft
VHLP2-18-BW1 2 ft
VHLP3-18-BW1 3 ft
VHLP4-18-BW1 4 ft
Note
All VHLP 18 GHz antennas labelled for 17.700 - 19.700 GHz band are also OK for 17.100
- 17.300 GHz band (confirmed to RACOM by CommScope).
• for 24 GHz band use ANT-ANW-KIT-24 and order the following VHLP single-polarized antenna types:
VHLP1-26-BW1 1 ft
VHLP2-26-BW1 2 ft
VHLP3-26-BW1 3 ft
VHLP4-26-BW1 4 ft
Note
All VHLP 26 GHz antennas labelled for 24.250 - 26.500 GHz band are OK for 24.000 -
24.250 GHz band (confirmed to RACOM by CommScope).
20
https://www.racom.eu/eng/about_us/contact.html
21

Installation
Note
BW1' is a code for 'no flange', which is an optimal choice for VHLP purchase (and typically the
cheapest one). Most CommScope distributors do not resell those, because normally each
shipped antenna has a unique flange for a concrete MW vendor product (defined by a string
of 3 letters+numbers at the end of the ordering code). If any vendor interface is purchased,
then it has to be unmounted before installation of RAy antenna mounting kit.
If there is a requirement to connect different type of antenna (for example some newer antenna
type), it is possible to modify the existing adapter to meet new requirements.
Flexible waveguide
22
Flexible waveguide mounting kit can be ordered as an accessory part .
Fig. 4.4: Flexible waveguide assembly
Flexible waveguides themselves are not offered by RACOM - please consult your antenna supplier.
4.3. RAy unit mounting

RAy unit can be attached to several different models of antennas from several vendors. Installation of
RAy unit on to LEAX-RAy or Jirous antennas or to any other antenna with proper RAy mounting kit
(eventually with flexible waveguide) is very simple and it is identical for all antennas and mounting kits.
Installation starts with the lubrication of antenna pivot, followed by fixing the RAy unit in a proper position
to the antenna and finished by unit grounding to the mast – as described in following sections.
4.3.1. Lubrication of the antenna pivot
Before fitting the RAy bushing to the antenna pivot ensure the "O" ring (part No. 1) is in the correct
position. It is also essential to prevent moisture getting in between these two parts. This moisture could
cause oxidation, which would complicate disassembly of this mechanical coupling in the future. For
this reason, we need to lubricate these surfaces with the grease, which is supplied in the capsule
22

Installation
marked "SILOCONE GREASE". If you use a different grease for lubrication, then it should be a teflon
or a silicone grease.
Fig. 4.5: Grease points on the antenna pivot and RAy unit flange
Lubricate internal area of the bushing on the RAy unit (2) and the "O" ring (1) with a thin even layer
that allows the pin to slide easily into the bushing without damaging the "O" ring. The layer has to be
really thin and even to ensure no grease is pushed in to the waveguide. A little bit more grease may
only be applied in the area (3) beyond the "O" ring on the antenna pin to optimally fill the small gap
(max. 0.1 mm) between the pin and the bushing to prevent leakage of moisture and water into the unit.
Installation should be carried out according to the antenna installation instructions.
A tub of grease is supplied with each RAy unit.
Important
Lubrication is a very important assembly step for every RAy unit.

Failure to lubricate the unit can lead to operational and assembly
complications.
The layer of grease has to be really thin (especially on the surface
"No 2"), otherwise grease blocks the waveguide after the as- Fig. 4.6: Silicone grease
sembly (and many decibels of the signal are lost).

Installation
4.3.2. RAy unit mounting to the antenna
Each antenna allows RAy unit to be mounted on it with different polarization:
• horizontal TX polarization
• vertical TX polarization
Fig. 4.7: Horizontal and vertical TX polarization – see the arrow sign
In all cases mount the unit with the connectors facing downwards at an angle.
Note
RAy3-17 and RAy3-24 links need one unit to be installed with vertical polarization and the
other unit with horizontal polarization because these units use cross polarization.
Fig. 4.8: RAy3 unit with antenna (left-side mounting and horizontal polarization)
RAy unit is fixed to the antenna by 4 pcs M8×30 (Allen) screws, which are part of the delivery of each
antenna or each mounting kit. Those should be partially unscrewed so that the unit can slide on to
them.
Then check whether the "O" ring is correctly fitted on the antenna pin and make sure it is not damaged
and has been lubricated with grease – see Section 4.3.1, “Lubrication of the antenna pivot” above. If
O-ring is injured or damaged, please exchange it immediately for a new one (size 22x2 mm, type
'FPM80'), otherwise moisture and/or dust can leak into the waveguide and emitter. It may eliminate
several dB of signal and cause a corrosion.
Then remove the protective plastic cover from the central pin of the antenna and fit the unit flange
(located in the center of flat part of RAy unit, across the holder) to it carefully, so there is no possibility
to damage the "O" ring. Once the RAy unit is plugged to the antenna pin, turn RAy clockwise so its

Installation
screw-holders fit the right position for all 4 screws. Carefully ensure the correct polarization of the unit
and secure the RAy unit in place with all four bolts. Finally, gently tighten the bolts with a No. 6 Allen
key.
Important
Gently tightening all 4 screws is enough. Do not over-tighten any screw, it may damage the
protective color surface of the aluminum unit (enforcing corrosion processes) and in the case
of an extreme force also deformations of the RAy aluminum cover may happen. Later de-in-
stallation of the unit then becomes difficult.
Please ensure that all 4 screws are tightened equally during tightening and the gap between
RAy screw-holders and spacers on all 4 sides of the RAy unit is approximately identical. Too
strong tightening of one or 2 screws on one side of RAy unit may lead to the deformation of
the sensitive zone of the waveguide between the antenna and the unit, resulting in weaker
radio parameters.
Even a small residual gap between RAy unit and the antenna is OK, because important is a
good connection of waveguide – it is good enough even with screws gently tightened.
Note
On older LEAX-RAy antennas (shipped during the year 2017) the residual gap under each
screw-holder on RAy and antenna body may be up to 1 mm.
4.3.3. RAy unit grounding
RAy unit has to be properly grounded, otherwise its function cannot be guaranteed and the unit can
be even damaged. Grounding connection through antenna and its holder is not enough (due to color
surface, oxidation etc.), thus a separated grounding is required to ensure the perfect galvanic connection.
23
The RAy grounding kit GND-RAy equipped with 100 cm of cable with grounding lugs and grounding
terminal ZSA16 with 40 cm grounding strip 15 mm wide is ideally suited for this.
Important
The RAy unit has to be grounded before connecting to the power supply and/or to the user
network.
Typically the unit is grounded to the antenna mast, which has to be properly grounded (according to
Fig. 4.19, “Grounding installation 1” and Fig. 4.20, “Grounding installation 2”, where unit grounding to
the antenna mast is marked by yellow-green cable).
2
The RAy unit must be grounded by an insulated copper cable with a minimum cross-section of 6 mm
terminated with a terminal lug fixed to the RAy unit by M8 grounding screw. It is marked by yellow
located on RAy flange nearby fixing ears (place for fixing screws). The conductor should have a
green/yellow plastic cover along its whole length and its other end should be ended by an appropriate
24
grounding terminal. For instructions on installing terminals see the grounding kit datasheet . The antenna
and the unit grounding must be installed by a qualified person.
23
24
https://www.racom.eu/download/hw/ray/free/eng/07_prislusenstvi/GND-RAy.pdf

Installation
Properly installed unit grounding kit is documented on photos below.
Fig. 4.9: Protective conductor at the RAy unit Fig. 4.10: Grounding the RAy unit
Fig. 4.11: RAy grounding kit Fig. 4.12: Protective conductor at the mast

Installation
4.4. Connectors assembly and disassembly

The unit is equipped with 3 connector slots described in detail (including connectors’ pin-outs) in Sec-
tion 1.3, “Ethernet + power interfaces” and Section 1.4, “Service interfaces”. Use only standard coun-
terparts to these connectors.
Fig. 4.13: Slots ETH1+POE, ETH2 Fig. 4.14: Slot S
25
A set of standard bushing and plugs is delivered with each RAy unit as an accessory ACS- RAy .
The rubber sealing for each bushing is delivered with three different internal diameters to fit different
cable diameters. The rubber is diagonally cut to enable sealing of cables with pre-installed connectors.
If the lengthening of the bushing is needed use the long bushing delivered within standard accessory
26 27
kit ACS-RAy2 or purchased separately as an option SET-BUSH65 (providing 65 mm long inner
28
space for connector) or the long extension OTH-BUSH-EXT500 (adds up to 50 cm).
Important
Before connecting the RAy unit to the power supply and/or to the user network it must be
grounded according to Section 4.3.3, “ RAy unit grounding”.
All cables have to be secured by appropriate bushings which must be fitted with relevant O-
rings and carefully tightened in, according the instructions below.
Remaining connector slots on RAy unit has to be secured by plugs (including the original
plugs in the flanges). Those must be fitted with O-rings and carefully tightened as well. Other-
wise, the unit is not protected against moisture intake through connectors and can not guar-
antee unit functionality.
25
26
27
28
https://webservice-new.racom.eu/main/eshop.detail?i=1513

Installation
Assembly variants:
Fig. 4.15: Short bushing assembly for metallic Ethernet with short ETH connector (for example
29
CON-RJ45-CAT6)
30
Fig. 4.16: Short bushing assembly for fibre optical Ethernet with RACOM / OFA fibre optic cable
Fig. 4.17: Bushing including short lengthening (for metallic Eth with longer connector or for DC-RJ45
31
adapter or for non-OFA fibre optic cable)
29
30
31

Installation
Assembly procedure:
• Put on the cable: the nut No.1, rubber sealing No.2, bushing No.3 and O-ring No.4.
• (If you use extension ring No.6 with O-ring No.7 put those on the cable as well.)
• Attach the appropriate connector No.5 to the cable.
• Plug the connector No.5 into the RAy3 unit.
• (If you use extension ring No.6 with O-ring No.7, lubricate its thread with grease and screw those
into the RAy3 unit.)
• Screw the bushing No.3 with the sealing O-ring into the RAy3 unit (or into the extension if used).
• Move the rubber sealing (2) along the cable to fit in the bushing. Screw the nut (1) on bushing (3).
Tip
Practical tip: Screw the ring No.6 and bushing No.3 quote tightly, so they could not rotate when
the nut No.1 is screwed (or released later on). Not doing so could damage the cable by twisting
it during sealing. It can also create the issue later on when the nut No.1 is released (and ring
No.6 or ring No.3 releases first).
Disassembly procedure:
• Release the nut No.1

• Remove the rubber sealing No.2
• Unscrew the bushing No.3 with O-ring No.4 (and extension No.6 with O-ring No.7).
• Remove the connector.
Warning
It is absolutely critical first to completely release and disassemble the nut No.1 and remove
the rubber No.2. Failure to do so could cause the damage of Ethernet cable or fibre optic wire
by cable rotation. Even connectors inside the RAy unit can be damaged. Should the rubber
sealing No.2 become fastened to the cable and/or to the plastic bushings, the rubber sealing
must be detached from the cable by a brute force. We suggest you use a flat screw driver to
release the rubber sealing No.2.
It is always better to optionally damage the bushing rather than damage a cable or
components inside the RAy unit.
At the outer end of the long lengthening there is necessary to use a flat ring supplied as part of the
32
OTH-BUSH-EXT500 . On other places O-rings are used. See next Figure:
32

Installation
Fig. 4.18: Bushing including long lengthening
Important
• When using other bushing or connector than the delivered, there is a danger of bad seal or
damaging the connector. Interior space can be small.

Installation
4.5. Grounding and overvoltage protection

The proper grounding together with surge protection components should be installed on site to increase
the resiliency of the whole installation against natural overvoltage situations (stimulated by storms,
lightning and other atmospheric issues). Such a system has to respect local standards for grounding
and electromagnetic protection, otherwise the risk of damaging the unit and/or connected IT infrastructure
gets much higher. We also recommend to consult each site situation with local experts to ensure the
installed grounding is enough for the actual site conditions and that the overvoltage protection of
sensitive components or infrastructures is reasonably effective against typical situations on site.
The rule is that every metallic component of wireless infrastructure located outside the building (in
LPZ0) should be properly grounded and protected against overvoltage, especially:
• grounded RAy unit itself (as described in Section 4.3.3, “ RAy unit grounding” )
• grounded all shields from all metallic Ethernet cables
• grounded all DC cables (shields or one wire)
• overvoltage protection is applied on all metallic Ethernet cables at the point of entrance to the building
• overvoltage protection is applied on DC cable at the point of entrance to the building
All types of cables should be grounded and longer cables should be grounded in several places (outside
the building every few meters). Overvoltage protective devices are available for all types of cables and
33
usage. Accessories offered by RACOM for those purposes are listed in Grounding section of RAy
web site.
Important
The unit and mast must be properly grounded before the power supply and/or the user network
are connected to RAy unit.
Warranty does not apply for units destroyed by surges or over-voltage (see RACOM warranty
conditions at Section 10.6, “Warranty” ).
Note
Some PoE power sources, PoE injectors and DC power supplies have overvoltage / surge
protection built in. Please consult the datasheets of those versus the local standards and site
requirements.
On sensitive sites additional overvoltage protection should / could be applied between different
zones (or rooms) even within one building (for example between network center and datacenter).
LPZ acronym means Lightning Protection Zone.
The example and rules below are designed in accordance with regulation EN 62305.
1. Where it is possible, the antenna should be located in an LPZ 0B protection zone with the use of a
local or artificial air termination device for protection against direct lightning strikes.
2. When meeting conditions for ensuring electrical insulation (distance from the lightning conductor)
in accordance with article 6.3 of this standard, it is not recommended to ground the load-bearing
structure and antenna to the external air termination network. Grounding should be attached to the
protective system of the internal LV (Low Voltage) wiring or grounded internal structures using a
2
CYA 6 mm bonding conductor , see Fig. 4.19 Grounding installation 1.
33

Installation
LPZ 0A
R
LPZ 0B
LPZ 1 230 V~
PoE
ETH ETH
LIGHTNING
ARRESTER
Fig. 4.19: Grounding installation 1
LPZ 0A
R
LPZ 0B
GROUNDING KIT
LPZ 1 230 V~
PoE
ETH ETH
LIGHTNING
ARRESTER
Bonding bar
Fig. 4.20: Grounding installation 2

Installation
3. If it is not possible to set up conditions of electrical insulation in accordance with article 6.3 of this
standard, we recommend connecting the load-bearing structure at roof level to the external air ter-
mination network via an 8mm diameter FeZn conductor and shielding the data cable before entry
2
to the building with a grounding kit and CYA 6 mm conductor to the bonding bus, and if not already
set up then also to the external air termination network, see Fig. 4.20 Grounding installation 2.
4. If there is not an external LPS on the building we recommend routing lightning current through an
8mm FeZn conductor to a common grounding system, or to a separate grounding electrode with a
ground resistance up to 10 Ω.
5. For limiting the overvoltage transferred over the data cable and into the building we recommend
2
fitting surge protection at the interface between zones LPZ 0 and LPZ 1 connected via a CYA 4 mm
conductor to the same grounding point as the antenna or the antenna mast.
6. We recommend protecting the PoE power supply from overvoltage on the LV side with suitable
class D surge protection.
RACOM supplies surge protection for installation on Ethernet cables entering buildings. For more details
34
see Surge protection .
Additional safety recommendations
• Only qualified personnel with authorization to work at heights are entitled to install antennas on masts,
roofs and walls of buildings.
• Do not install the antenna in the vicinity of electrical wiring. The antenna and bracket should not
come into contact with electrical wiring at any time.
• The antenna and cables are electrical conductors. During installation electrostatic charges may build
up which may lead to injury. During installation or repair work to parts of the antenna lead, bare
metal parts must be temporarily grounded.
• The antenna and antenna cable must be grounded at all times.
• Do not mount the antenna in windy or rainy conditions or during a storm, or if the area is covered
with snow or ice.
• Do not touch the antenna, antenna brackets or conductors during a storm.
34
https://www.racom.eu/eng/products/microwave-link.html#accessories_ochrana

Installation
Fig. 4.21: Grounding Kit universal Fig. 4.22: Grounding Kit for 5-11mm cables,
for 5-11mm cables assembled
Fig. 4.23: Grounding kit for S/FTP 4+2 cable Fig. 4.24: Grounding kit detail

Installation
Fig. 4.25: Separated lightning conductor
Note
It is always better not to install the microwave unit directly under the lightning conductor holders.
There is lower probability of unit being polluted by birds.
It is necessary to install the Ethernet lead so that there is no excessive mechanical stress applied on
the connector bushing:
Fig. 4.26: Example of a correct lead installation.

Installation
4.6. Power supply

RAy microwave unit can be powered by active PoE, passive PoE or by DC power source. All variants
of power are supplied through RJ45 Ethernet connector (in slot ETH1+POE). Detailed description and
technical parameters of the connector are described in Section 1.3.1, “RJ45 connector (ETH1+POE)”.
Fig. 4.27: Power supply possibilities
RACOM is offering all kinds of power supplies, all guaranteed for compatibility with RAy unit and tested
35
for long-term stability – they are listed in Powering section of RAy web site.
4.6.1. PoE power sourcing
• Active PoE plus (called also Standard PoE+) power supply compatible with IEEE 802.3at, sourced
by AC or DC power. The standard IEEE 802.3at defines negotiation method, wires to be used, oper-
ating voltage (36-56V), maximum supported current, overcurrent protection and other parameters.
Any power supply compatible with IEEE 802.3at standard can be used.
• Passive PoE power supply (called sometime PoE injector) is an equipment pushing DC power into
the pins of Ethernet connector according IEEE 802.3at standard polarity and voltage. Thus, supported
voltage, distances, grounding and internal RJ45 pins wiring are identical with Standard PoE+ (men-
tioned above). Typically, the current is sourced from a DC power with adequate parameters (nominal
voltage 24-60V, max current at least 1A). The only additional requirement is that non-grounded wire
of DC power circuit to the PoE injector has to be secured by a fuse disconnecting the power circuit
in the case of over current (similar like for DC power source connected directly to the RAy unit by a
DC connector).
Note
RAy unit requires the voltage on RJ45 connector (ETH1+POE) to be at least 20 V, for
booting 21 V (to prevent booting with discharged 24 V battery). If a longer Ethernet cable
than few meters is used, then both voltage and Watts of power supply and PoE injector has
to be adequately higher to cover the power loss within the Ethernet cable.
36
Quality Ethernet cable (i.e. shielded one, like CAB-CAT7 ) with UV protection is recommen-
ded for outside use.
35
36

Installation
37
Quality connectors (like CON-RJ45-CAT7 ) are recommend to be used on both ends of
Ethernet cable to ensure long-term reliability of the connection. Such connectors have better
resistance against oxidation and also against scorching contacts due to spikes during power-
on and power-off the unit by plug / unplug Ethernet cable. Anyhow standard Eth cable with
standard Eth connectors should work as well.
38
Overvoltage protection unit is recommended to be applied between RAy unit and PoE
power supply – for details see Section 4.5, “Grounding and overvoltage protection” (easily
visible on Fig. 4.19, “Grounding installation 1”).
4.6.2. DC power sourcing
Direct DC power input for RAy3 unit described in Section 1.3.3, “DC power (using ETH1+POE)” requires
39
the use of DC/RJ45 adapter (item OTH-DC/RJ45 ).
• Any kind of DC power source with supplied nominal DC voltage in the range 24-60 V and with enough
power for the RAy unit plus energy loss on the DC cable. (For RAy3-17 and RAy3-24 the minimum
is 25 Watts).
• RAy unit requires the voltage on RJ45 connector (ETH1+POE) to be at least 20 V, for booting 21 V
(to prevent booting with discharged 24 V battery). If a longer DC cable than few meters is used, then
both voltage and Watts of power supply has to be adequately higher to cover the power loss within
the DC cable.
• RAy3 internal DC power circuits accept both polarities and they ensure galvanic separation of power
source line from the RAy unit itself. This simplifies the DC power circuits installation.
• The DC power circuit must be fitted with a fuse to protect against short circuiting (or power supply
has to have such a fuse built-in).
Note
2 40
• Typically, DC wires have cross-section 1.5 mm . DC contacts on OTH-DC/RJ45 are de-
signed for this cross-section.
41
• OTH-DC/RJ45 occupies ETH1+POE port on RAy3 unit. When used, Ethernet connection
to the unit has to be made through ETH2 port. Possible solutions are described in section
Note at the end of Section 1.3.3, “DC power (using ETH1+POE)”.
• If shielded DC power cable is used, then shield should be grounded by a proper Grounding
42
kit to the mast or to the Grounding screw on RAy unit.
• If the galvanic separated power source is used and the DC power line needs to be grounded
(either positive or negative wire), the connection of one DC line to the ground should be
43
made by a proper Grounding kit to the mast. Possible is also to use a small piece of DC
37
38
https://www.racom.eu/eng/products/microwave-link.html#accessories_ochrana
39
https://www.racom.eu/download/hw/ray/free/eng/07_prislusenstvi/OTH-DC-RJ45.pdf
40
41
42
43

Installation
cable to connect the line to be grounded to the Grounding screw on RAy unit. For more details
see Section 4.5, “Grounding and overvoltage protection”.

Installation
4.7. Start up
Connect a power supply to the installed RAy unit. Connect the device to be used for configuration via
WiFi or Ethernet cable. Access the configuration menu using browser or Alignment tool.
4.7.1. Noise on the site
This is particularly true for installation of links working in free bands, where the user has no secured
frequency.
Analyze the level of noise in the individual channels using the spectrum analyzer under Tools/Live
data/Frequency spectrum analyzer. If necessary, adjust the choice of working channel on the basis of
the results.
While doing so, respect the rule that all units emit a signal in the Upper part of the range and receive
it in the Lower part of the range in one location, or vice versa. A transmitter must not be installed in the
part of the spectrum where other units function as receivers.
4.7.2. Directing antennas
Placing the antennas to the correct antenna alignment is very important to ensure the strongest signal
is received:
Fig. 4.28: Correct alignment diagram
• For first antenna alignment, use a narrow channel, low modulation and high power where possible.
• ATPC and ACM functions should be switched off (prevents Tx power fluctuations during alignment).
• Where possible adjust both ends of link simultaneously to speed up the process.
• Alternate adjustments at both ends of link in small increments both horizontally and vertically to es-
tablish position with strongest signal (highest value of parameter RSS, received signal strength)
whilst looking for maximum main signal (see paragraph on main & side lobes).
• Link parameter RSS (received signal strength) is a key parameter for a proper antenna alignment
and later on for a proper link functionality. All the adjustment effort is to maximize this parameter on
both sides of the link and to reach pre-calculated RSS value (which is typically calculated before the
link is physically established to ensure necessary link transmission parameters could be met).

Installation
• Several available methods to measure RSS are built in to the RAy unit. Those are discussed in detail
in section 4.7.3.
• Connect a PC, tablet, mobile or voltmeter according your preferred RSS measurement method and
find the best possible antenna alignment for both sides of the link. Following section Main and side
lobes would help you.
Main and side lobes
Directional antennas have a specific angle within which radio waves can be transmitted or received
(Angle of Tx/Rx).
The strongest signal is emitted in a forward direction; the main lobe is a graphical representation of its
direction of travel and strength. However, signals are also emitted and received from unwanted directions
through side lobes. In receiving antennas this is a highly significant factor contributing to the level of
interference in a radio network (See Fig. 4.29 Antenna lobe diagram ).
Fig. 4.30 Signal strength graph provides an indication of comparative signal strength from different
beams emitted from a directional antenna.
0
90
Antenna Main lobe

Directivity (dBi)
Back lobe Main lobe Side lobe

level Side lobes
0
0
Side lobes
Angle of T x / R x
-180 -60 -30 0 30 60 180
Angle (Degrees)
0
-90
Fig. 4.29: Antenna lobe diagram Fig. 4.30: Signal strength graph

Installation
Examples
A–A
1 2
A 3 A CRO
G [dbi]
4 SS-S 2
B 5 B EC T
ION
A–
C 6 C A
MAIN
CRO
20
BEAM
SS-
G [dbi]
SEC
1 3
TIO
SIDE 10
20
NC
LOBE
–C
0
10
-10
0
-40° -20° 0° 20° 40° -40° -20° 0° 20° 40°
B–B C–C
G [dbi]
G [dbi]
20 20
10 4 5 10 6
0 0
-10 -10
-40° -20° 0° 20° 40° -40° -20° 0° 20° 40°
Fig. 4.31: Radiation diagrams
Both antennas should be oriented towards each other using the peaks of the radiation diagram. Adjust
the antenna alternately in the horizontal and vertical axes and monitor the resulting signal strength.
Use the calculation of the expected RSS with the precision of several dBm as guidance. Side lobes
44
transmit a signal ca 20 dBm weaker, see the Microwave link Calculation .
44
https://www.racom.eu/eng/products/microwave-link.html#calculation

Installation
The resulting RSS helps distinguish between

the states A-A and C-C which appear similar.
It also helps in situations where simple search
for a maximum doesn’t work as shown in the
illustration “incorrect adjustment”.
Real radiation diagrams are more complex,

especially in that they run differently in horizont-
al and vertical axes. The basic steps for determ-
ining the main radiation lobe however stay
valid. For example:
Fig. 4.32: Radiation diagram – incorrect adjustment
Fig. 4.33: 3D example of more complicated Radiation Pattern

Installation
4.7.3. RSS measurement
There are 4 tools available to support measurement of the 2 basic parameters for optimum antenna
alignment: RSS (Radio Signal Strength) and MSE (Mean Square Error, the inverse to often used value
called SNR - Signal to Noise Ratio):
1. Voltmeter – indicates local RSS
2. RAy Tools smartphone application – indicates RSS, MSE - Local & Peer
3. Antenna Alignment Tool web page – indicates RSS, MSE – Local & Peer
4. Bar graph on Live Data page inside web management – indicates RSS, MSE, BER – Local & Peer
Before antenna alignment starts, it is recommended to find out RSS and MSE values from the link
design for the installed link or calculate these values yourself. There are 4 methods available with in-
creasing levels of accuracy:
• Module Calculation inside RAy Tools smartphone application

45
• Link calculation on RACOM website
46
• Use Link calculation chapter in Application notes
• Precise link calculation using dedicated tools (e.g. Pathloss)
Voltmeter
RAy units support traditional antenna alignment using a volt-
meter measurement representing RSS in dBm (only for a
local unit). Connect a voltmeter with the range 2V DC via
connectors to the operational unit and adjust antennas to the
lowest indicated voltage. Voltage is calibrated according to
signal strength. E.g.:
RSS -65 dBm corresponds to voltage 0.65 V,
RSS -80 dBm corresponds to voltage 0.80 V etc.
RAy Tools – smartphone application

RAy Tools is an application described in detail in Chapter 7.
RAy Tools app for Mobile devices . Module Alignment displays
RSS and MSE for both local and peer RAy unit. All key func-
tionality in this module performs an identical function to An-
tenna Alignment Tool described in Section 5.6.2 Live data .
More about RAy Tools in Chapter 7. RAy Tools app for Mobile
devices .
45
https://www.racom.eu/eng/products/microwave-link.html#calculation
46
https://www.racom.eu/eng/products/m/ray/app/linkcalc/index.html

Installation
Antenna Alignment Tool – html page within unit management

Antenna Alignment Tool is optimized for devices with smaller
displays. All values are refreshed ten times per second to
enable smooth operation. The Antenna Alignment Tool is de-
scribed in Section 5.6.2 Live data . The Tool is available on
http://<ip>/tk, (e.g. http://192.168.169.169/tk for standard
Ethernet ports, alternatively on http://172.17.17.17/tk in the
case of connection through USB/WiFi or USB/Eth).
The Tool is accessible without any username or password.
Bar graph in web management

Within user management Tools / Live data / Bar indicators
shows bar graphs of RSS and MSE values for local and peer
units. Values are refreshed every second or manually. See
Section 5.6.2 Live data for detailed information.
4.7.4. Link test
Basic parameters of the link are RSS and MSE. They can be checked by many different ways:
• in RAyTools page Alignment (both sides, refreshed automatically)
• in the menu Status/Brief and Status/Detailed (both sides, can be refreshed manually by pressing the
Refresh button or in real time with a period of several seconds after activating the Start button)
• on the screen Tools/Live data/Bar indicators (both sides, refreshed once a second After pressing
the Start button)
• on voltmeter (only local RSS value)
Verify the functionality of the radio link similar like in chapter Link test.
After installation, it is good to reset the statistics using the Clear stats button in menu
Status/Detailed . This allows easier diagnostics of the link’s reliability over time.
4.7.5. Parameters setup
After both antennas have been aligned, setup operation parameters for the link. In the case of links
operating in the free band, setup the parameters based on survey results from the tool Tools/Live
data/Frequency analyzer. In the case of links operating on a licensed band, setup the parameters based
on the assigned license:
• Bandwidth
• Channel Selection (TX / RX channel)

Installation
• Modulation (TX modulation) – ACM is recommended. When selecting fixed modulation it is necessary
to account for the fade margin. If fixed modulation is setup close to a possible maximum, then a de-
terioration in RSS could endanger the link both for data transfer as well as service access.
• Transmit power (TX power), or ATPC
• Verify and record IP addresses
• Define access channels – HTTPS / telnet / ssh / ssh with password
• Check the users password settings
• Check / setup the WiFi password or deactivate WiFi access permanently (in unit management menu
USB accessories or physically by removing the WiFi module from slot “S”)
Restart both units by interrupting their power supply and verify the status of the link. This verifies that
all parameters have been stored correctly in the memory.
Select Tools/Maintenance/Backup/Settings (Local & Peer)/Full and save the configuration to backup
file “cnf_backup.tgz”.
This completes the installation. Further configuration can be performed remotely.

Configuration
5. Configuration
5.1. Introduction
The following configuration buttons are used for configuration:
• Apply
Apply and save parameters.
• Cancel
Set parameters are overwritten with original values.
• Refresh
Reload all current values of the unit / both units.
• Show defaults
Clicking the button displays the default values of all individual parameters on the current screen. To
use these values, you must click on the "Apply" button.
• Show backup
Clicking the button displays the values of individual parameters held in the backup file (Backup/Set-
tings/Open file upload). To use any of these values, you must use the "Apply" button. For loading
the backup configuration see menu Tools/Maintenance/Backup.
• Start
Activating automatic refresh fields marked by icon using the Start button with the frequency circa
1 sec.
• Stop
Use the "Stop" button to stop automatic refresh of displayed information with 1sec period. Date and
time values are refreshed anyway.
Fig. 5.1: Configuration Controls
Help
The microwave link configuration system is equipped with built in Help - see Help section. The Help is
accessible in two forms:
• Configuration parameter context help. The help text is displayed in the pop-up window after clicking
the parameter name.
• The whole user interface help, activated by clicking the Help menu.

Configuration
Login
You can login into the configuration interface using either the insecure HTTP protocol (default login
screen), or the secure HTTPS protocol. You should select the connection method on the login screen.
If the HTTPS protocol is used, it is not possible to tap the network communication and acquire the
station’s login information.
Fig. 5.2: Login
Note
Antenna alignment link below Login window activates smartphone Antenna alignment tool.
See its detailed description in chapter Live data.
Rollback function
If you interrupt the connection on an operating link by entering inappropriate radio link parameters, the
original parameters will be restored after 1 minute. The connection is automatically restored.
5.2. Status bar
Fig. 5.3: Status bar 1
The Status bar is located on the upper part of the screen below the title bar. It consists of 3 fields:
• Local unit status (unit assigned to the IP address entered in the browser or CLI)
• Local to Peer Link status.
• Peer unit status.
Local and Peer field displays:
• Station name according to configuration.

• Actual time valid for respective unit.
• Warning or Alarm icon in case of warning or alarm.
Link field display:

Configuration
• Status of the link between both sides of the microwave link.

• Warning icon when the link is not capable of user data transfer.
The Link status can be one of the following values:
• UNKNOWN
Unit start up. The initialization is not yet finished.
• SETUP
Unit initialization according to valid configuration.
• SINGLE
Unit in operation status. Link to peer unit is not established.
• CONNECTING
Connection to peer unit in progress.
• AUTHORIZING
Authorization of the peer unit in progress.
• OK
Link is connected. Peer unit is authorized.
• ANALYZER
Spectrum analyzer mode active. User data are not transferred.
All link states except for the state of OK are highlighted with a triangle.:
Fig. 5.4: Status bar 2
Example of a complete page - status bar, menu and control buttons.

Configuration
5.3. Status
The "Status" menu provides basic information about local and remote station. Information is valid in
the moment, the page is opened, or the Refresh button is clicked.
The Status/Brief tab shows only the most important values whereas the Status/Detailed tab provides
further details. Below is a list of all values according to the tab Status/Detailed .
The icon marks fields which are automatically updated with 30 sec period (or 1 sec when the "Start"
button is active).
Fig. 5.5: Menu Status - Brief (example)

Configuration
Fig. 5.6: Menu Status - Detailed (example)
5.3.1. Status - General
• Product code
Unit product code - is the same as the Ordering code.
• Serial no.
Unit serial number.
• Station name
Station name (for example to reflect the unit location in the network topology).
• Station location
Station location (for example GPS position or to reflect the network topology hierarchy).
• Radio SW version
Software defined radio version.
• Firmware version

Configuration
Unit’s firmware version.
• Date, Time
The internal real-time clock. The clock is set manually or it is synchronized with NTP server and set
for both units.
• Inside temperature [°C]

Temperature inside the unit (on the modem board).
• Voltage [V]
Unit’s power supply voltage level.
5.3.2. Status - Radio
• Band index
Radio unit type: L (Lower) or U (Upper) part of the frequency band.
• TX polarization
Horizontal or vertical polarization based on the physical installation. Indicates the polarization of the
transmitted signal. Local and Peer are indicated separately. The proper position of the cable is
sideways down.
Notice for RAy3-17 and RAy3-24 links: One side of the link must be installed in vertical polarization
and the other in horizontal polarization.
• Frequency table
Displays the currently used frequency table in format <name:version>.
• Net bitrate [Mbps]

Current transfer capacity of radio channel for user data.
• Max. net bitrate [Mbps]

The maximum RF channel capacity according to installed feature key.
• Bandwidth [MHz]
One of the standard channel widths can be selected. This parameter must be set identically in local
and remote.
• TX and RX channel [GHz]

Used channels. Both number of the channel and frequency in GHz are listed.
• TX modulation
Modulation type currently used for transmitting. When adaptive modulation is enabled, the ACM letters
are displayed as well as information about maximum permitted modulation: "current modulation ACM
/ maximum modulation"
• TX power [dBm]
Current output power on the RF channel in dBm. If ATPC is enabled, the ATPC letters are displayed
as well as information about maximum permitted power: "current power ATPC / maximum power"
• RSS [dBm]
Received signal strength. If ATPC is enabled, the ATPC letters are displayed as well as information
about threshold value for activation of power control loop: "current RSS ATPC / threshold RSS"
• MSE [dB]

Configuration
Mean Square Error (the inverse to often used SNR - Signal to Noise Ratio). If ATPC is enabled, the
ATPC letters are displayed as well as information about threshold value for activation of power control
loop: "current MSE ATPC / threshold MSE"
• BER [-]
Bit Error Rate is registered at the receiving end; instantaneous value.
• Link uptime
Time elapsed since the current link connection has been established.
5.3.3. Status - Switch interface
• Egress rate limit Air

Status of the Egress rate limiter on the Air interface. The traffic can be limited according to bits per
second or frames per second.
Message format for bits per second: "xx.xx Mbps Ly auto" where:
○ xx.xx Mbps
Egress speed limit.
○ Ly
L1/L2/L3 which Ethernet layer is used for speed calculation.
○ auto
gives information about active Speed guard function.
Message format for frames per second: "xx.xx fps" where:

○ xx.xx fps
Egress frames per second limit.
• Link mode Eth1, 2

Status of Ethernet interface. Current bit rate (10 = 10BASE-T, 100 = 100BASE-TX and 1000 =
1000BASE-T) and state of duplex (FD = full duplex, HD = half duplex).
5.3.4. Status - Service access
• MAC address
HW address of the Ethernet module.
• IPv4 address
IP address in the standard dotted decimal notation, including the bit width of netmask after the forward
slash.
• Management VLAN
Service access via VLAN management only.
• Services
Services enabled for unit management and monitoring (Web, Telnet, SSH, SNMP, NTP).
• USB accessories
Indicates physical devices inside USB connector in system slot 'S' and its status (for example: 'WiFi:
disabled').
• Unit 24S compatibility (formerly 'Unit S mode')

This parameter is available only for newly deployed 24 GHz units without the 'S' label in Product
code (i.e. '24S'). When "active", the unit behaves like the unit '24S' (it can establish a link only with

Configuration
another '24S' unit). For a link between the units without the 'S' label, this compatibility needs to be
disabled ("off").
5.3.5. Status - Radio link statistics
Information on statistical data:
• Statistics Cleared
Time of log clearing.
• Statistics Period
Period of log refresh.
• Overall Link Uptime

Overall time the link has been connected.
• Overall Link Downtime

Overall time the link has been disconnected.
• Reliability [%]
The ratio of "Uptime" and "Downtime".
• Current Link Uptime

Current time the link has been connected.
• The Longest Drop

The longest downtime period recorded.
• The Last Drop

Length of the last link interruption.
• Number of Drops
Number of link interruptions.

Configuration
5.4. Link settings
5.4.1. General
Setup of general parameters of the link.
Fig. 5.7: Menu Link settings / General
• Product code
Unit type indicator.
• Serial no.
Unit serial number.
• IPv4 address
IP address in the standard dotted decimal notation, including the bit width of netmask after the forward
slash.
• Station name
Station name can be modified by user (for example to reflect the unit location in the network topology).
• Station location
Station location can be modified by user (for example to reflect the network topology hierarchy).
• Date, Time

Configuration
The internal real-time clock. The clock is set manually or it is synchronized with NTP server and set
for both units.
• Time source
Time synchronization source setup. Manual setup or NTP protocol use. For easier diagnostics of
link operation, it is recommended to use the NTP time synchronization.
• Adjust time
Manual time setup. Use the dialog box to manually set the current date and time. You can copy time
from browser (local PC).
• NTP source IP
IP address of the time synchronization server.
• NTP period
Time synchronization interval.
• Time zone
Time zone
Note
When the time zone is changed, the original values set in the RAy unit are kept. The actual
change takes place after OS restart in order to prevent unexpected states related with local
time change.
• Adjust time zone

Use the dialog box to set the new time zone. You can copy the time zone from a browser (local PC),
select the time zone code from a list or input time zone string.
The string can be either time zone code from IANA time zone database (ie.: "Europe/Prague") or the
POSIX format (ie.: "CET-01:00:00CEST-02:00:00,M3.5.0/02:00:00,M10.5.0/03:00:00"). The posix
format allows shortened variants usage when default values are used (ie.: "CET", "CET-1CEST",
...).
The unit will reboot to use the new setting.
5.4.2. Radio
Setup of general parameters of the radio link.

Configuration
Fig. 5.8: Menu Link settings / Radio
• Band index
Radio unit type: L(ower) or U(pper) part of the frequency band.
• TX polarization
Horizontal or vertical polarization based on the physical installation. Indicates the polarization of the
transmitted signal. Local and Peer are indicated separately. The proper position of the cable is
sideways down.
Notice for RAy3-17 and RAy3-24 links: One side of the link must be installed in vertical polarization
and the other in horizontal polarization.
• Asymmetric bandwidth
Enable asymmetric channel bandwidth.
• TX bandwidth [MHz], RX bandwidth [MHz]

One of the standard channel widths can be selected. This parameter must be set identically in local
and remote (local TX bandwidth = peer RX bandwidth and local RX bandwidth = peer TX bandwidth).
When units are connected, this is ensured automatically. If asymmetry is not allowed, then TX
bandwidth = RX bandwidth on both units.
• Frequency input
Allows to choose if TX and RX channel frequencies are selected from the list of predefined channels
or if manual input of frequencies would be possible (if supported).
• TX channel [GHz], RX channel [GHz]

TX and RX channels are selected from a list of channels. The basic configuration has the TX and
RX options interconnected. In this case the basic duplex spacing between channels is preserved
and by selecting one channel, the other three are defined as well. For units operating in free bands,
it is possible to disconnect the TX-RX lock and select TX and RX channels individually. Corresponding
channels at peer unit are set automatically.

Configuration
Note
Non-standard duplex setting leads to non-effective use of the spectrum.
• Duplex spacing [MHz]

Information about duplex spacing of TX and RX channel.
• ACM max TX modulation, ACM min TX modulation

Setting of minimum and maximum modulation level for ACM on TX channel (can be set differently
for local and peer unit). ACM is always enabled on RAy3 and would operate within those boundaries.
You can select in range from QPSK_S (highest sensitivity for difficult conditions) up to 4096QAM
(highest speed for good conditions).
Note
On some channel widths the highest available modulation to select may be lower than
4096QAM.
• ATPCEnable automatic control of RF power.

Once enabled, the TX power is regulated towards lower level while maintaining signal level high
enough not to affect current degree of modulation.
• ATPC RSS threshold [dBm]

The ATPC algorithm controls the output power according to RSS of the peer unit. The lowest allowed
-6
RSS (the threshold) is approx. 10 dBm above declared sensitivity for BER 10 . If necessary, it is
possible to use this parameter to move the threshold slightly up or down.
• TX power [dBm]
RF output power. With ATPC enabled this parameter defines maximum RF power level.
• Antenna gain [dBi]

Gain of used antenna. It is used to calculate approximate EIRP.
Valid only for RAy3-17 and RAy3-24 links.
• EIRP ?= limit [dBm]

Approximate calculation of EIRP. Number on the right shows the allowed EIRP limit. Sign between
numbers gives information on compliance / noncompliance with allowed EIRP limits. If the EIRP
limit field background is RED, the value shown may be used but will exceed the EIRP limit.
This field value will only be shown for certain RAy3-17 and RAy3-24 links and based on the Frequency
tables used.
The principle behind ATPC is to maintain the lowest transmitting power without affecting the throughput
of the link. The output is primarily controlled by RSS on the opposite side. ATPC is also used to maintain
MSE thus protecting the selected modulation level.
The ATPC Control loop is evaluated once per second.
The principle behind ACM is to maintain the connection between the two units even when degraded
propagation conditions are experienced which make it impossible to maintain the selected modulation
level. ACM regulates TX modulation across all ranges from ACM min TX modulation up to ACM max
TX modulation (as configured by the user) according to the limits in table ACM switching according to
MSE state.
ACM control loop is evaluated with each frame, i.e. roughly after tens of microseconds.

Configuration
In normal operating conditions, ATPC is applied first (even if it is the slower control loop). When deteri-
oration in propagation conditions gradually increases the attenuation on the route, it is compensated
by increasing RF power. ACM control will only be applied in conditions when ATPC reaches its ceiling.

Configuration
5.4.3. Service access
Services
Access routes for link configuration.
Fig. 5.9: Menu Link settings / Service access / Services
• IPv4 address
Service IP address, by default 192.168.169.169 for L unit and 192.168.169.170 for U unit. Management
address of the Peer station has to be set up as well.
• Netmask
Mask for service access, 24 by default.
• Gateway
Default gateway for service access; empty by default.
• Management VLAN, 1st tag, 2nd tag

Enables management access via VLAN. Management VLAN can be single-tagged or dual-tagged.
Line for 2nd tag gets active only after 1st tag is activated. Blocks access for HTTPS, ssh and telnet
configuration via untagged packets (without VLAN) making only VLAN access possible. VLAN
management is off by default.

Configuration
Warning
By enabling VLAN management, ALL accesses are blocked for configuration using normal
(untagged) LAN! During tests, you may enable VLAN management on one unit only. Then
it is possible to access the link via LAN and VLAN either directly or via radio link.
• VID
VLAN management id, by default 1. This field must have a value entered even when VLAN manage-
ment is not active.
• Protocol
Protocol 802.1q or 802.1ad
• Web server
Allows access via web server (for HTTP and HTTPS protocol).
Warning
After disabling access via web server, you will not be able to access the unit using a web
browser!
• CLI (telnet)
Enables access via telnet protocol. Provides access to CLI (Command Line Interface) for simple
telnet clients. Disabled by default.
• CLI (SSH)
Enables access via SSH protocol. Provides secure access to CLI. If preventing unauthorized access
to the unit is the number one priority, leave only this server on.
• SNMPEnabling SNMP server. Off by default.
• SNMP community string

SNMP community string. Can contain both lower and uppercase letters, numbers, four characters .
: _ - and can be up to 256 characters long.
• SNMP trap IP
Address for sending SNMP traps. It is possible to record up to 3 addresses separated by commas.
• LED indicators
Enable LED status indicators on the body of the unit. You can turn off LED indication with this option.
• LLDP (Service IP info)

Data transmitted through the LLDP protocol can be accessed in two ways:
○ OnTransmissions every 60 seconds
○ SingleTransmitted once only when unit is rebooted
If you forget the Service IP address, it can be found by reading data broadcast through LLDP protocol.
Data contains the following information:
○ Management addressIP address
○ System DescriptionSerial number
○ Chassis SubtypeType (e.g. RAy3-17 -L)
○ IEEE 802.1 - Port and Protocol VLAN ID

Configuration
Port and Protocol VLAN Identifier: (e.g. 300 (0x012C))

but only if Management VLAN is enabled.
The message can be recorded and converted into a readable form using a LLDP client. A suitable
tool for this purpose is Wireshark IP traffic analyzing tool, with free licenses available for both Windows
and Linux. To locate the message easily, use the Capture filter "ether proto 0x88cc" in Wireshark.
Management address of the Peer station has to be set up as well.
• Link authorization guard

User data flow to the remote unit can be established dependent on remote station authorization. The
authorization is secured by using SSH keys. See Section 6.3.3, “Remote unit authorization” for more
details.
○ Disabled ... User data flow through the Air channel is enabled even if the remote unit is not author-
ized.
○ Enabled ... User data flow through the Air channel is enabled only if the remote unit is authorized.
The "Link authorization guard" parameter value of the remote unit is ignored.
• Speed guard
The speed guard controls automatically the Egress data rate shaping according to available capacity
of the Air channel. The Air channel capacity check and the Egress shaping adjustment takes place
approx. once per 50 ms.

Configuration
USB accessories
The USB connector is used for management access (not for user data) to the local unit using Ethernet
or WiFi adapter. Only RACOM recommended adapters are supported.
Default WiFi IP address of the unit is 172.17.17.17 with DHCP enabled by default allocating IP address
automatically to connected device.
Fig. 5.10: Menu Link settings / Service access / USB accessories
• USB info
Status information about device connected via the USB:
n/a - info not available (HW not known to RAy3 FW = probably not RACOM supplied accessory), or
No device - no device plugged in the USB port, or
List of basic USB module credentials:
○ Vendor ID: Product ID
○ Manufacturer
○ Product
○ WiFi/Eth: up/down ... only for network device
○ MAC ... only for network device
• IPv4 address
Unit service management address when connecting via USB port.
• Netmask
Network mask when connecting via USB port.
• DHCP start, DHCP end

DHCP range for dynamic address allocation of the management client connected via USB port.

Configuration
• Ethernet adapter Enable

Enables operation of USB/Eth adapter.
• Ethernet adapter DHCP

Enables DHCP on WiFi adapter if present (for automatic setting of client(s) IP address).
• WiFi adapter Enable on Air link loss

WiFi is activated only during Air-Link loss – means WiFi starts to work and transmit SSID. WiFi is
activated 60 seconds after Air-Link loss and deactivated 600 seconds after the Air-Link is restored.
The WiFi passphrase should be set by admin before using this option (if not WiFi management alarm
is activated).
• WiFi adapter Force enable

WiFi is forced to be permanently active (and to transmit SSID) and WiFi management alarm is activ-
ated. WiFi passphrase should be set by admin before using this option.
This parameter has a higher priority than "WiFi adapter enable on Air link loss", so if it is set ON then
WiFi activity does not depend on Air-Link status.
• WiFi adapter DHCP

Enables DHCP on WiFi adapter if present (for automatic setting of client(s) IP address).
• WiFi SSID
Name of service WiFi visible by clients (can be max 32 characters long).
• WiFi encryption
Service WiFi encryption is WPA2 and cannot be changed. Factory default is "none" due to missing
passphrase. WPA2 is applied automatically once any passphrase is entered.
• WiFi passphrase
Service WiFi passphrase has to be 8-64 characters long. The WiFi passphrase should be set by
admin before any use of WiFi. Until passphrase is set, WiFi management alarm is activated.
• WiFi mode
Service WiFi mode can be IEEE 802.11n or IEEE 802.11g
• WiFi channel
WiFi channel can be set 1-11 depending on WiFi mode setting (see parameter above):
IEEE 802.11n - channels 1-7
IEEE 802.11g - channels 1-11
The WiFi adapter does not search for conflicts in the air. If problems occur, changing the channel is
the easiest way to resolve the issue.

Configuration
Users
List and setup of users. Example menu of the cli_super level user.
Fig. 5.11: Menu Link settings / Service access / Users
Within the default Factory Settings one user is defined in the system. This user has username admin
and password admin and is assigned the highest level of permissions cli_super. This user then
assigns other users to the system along with their level of permissions.
Service access has three levels of permissions. Numbers of users that can be defined in the system:
Permissions No of users
cli_guest 10
cli_admin 10
cli_super 2
Permissions defined in the system cli_guest cli_admin cli_super

Create new user No No Yes
Change own password Yes Yes Yes
Delete user * No No Yes
Copy (Mirror) permissions local to peer No No Yes
Configure and modify link settings No Yes Yes
* The system prevents the user from deleting both cli_super accounts.
The logged-on user is shown in the top right of the screen. There can be different users on either end
of the link.
Important
It is strongly recommended that the default password admin is changed. Similarly, all other
users should change their password. Using the CLI, it is appropriate to supplement the SSH
key.
• Local, Peer
List of users on Local and Peer stations.
• Username

Configuration
This name is entered at Login to log into the link management.
• Group
User group to which the user belongs.
○ cli_guest
Read Only
○ cli_admin
Configure and modify link settings
○ cli_super
Configure and modify user accounts and link settings
• Password
Information about whether user has a password
• SSH key
Information about whether user has at least one ssh key defined.
Note
More users concurrently

If two or more users work concurrently on the unit any change of configuration settings should
be applied by all users. This applies to the menu Link settings which works with both, Local
and Peer parameters.
If one user sends the Apply command, other users will receive a message: "Configuration
changed, please go to Link settings and click Refresh". Other users can only use the Apply
command after refreshing Link Settings.

Configuration
Edit user
Clicking "Edit" next to a username opens a screen with configuration of the given account.
Fig. 5.12: Menu Link settings / Service access / Users / edit
• Username
User name.
• Group
The group to which this user will belong.
• Password
Password can be set or deleted.
○ Delete
User will not have a password. The user will only be able to log in with a ssh key. In order to delete
the password, you must first upload the ssh key.
○ Set
Password settings.
• New password
New password.
• Confirm password
Repeat password.
• SSH key
Working with ssh key.
○ Delete
Clear all ssh keys from user account.
○ Set/replace
Add a new key. If there already was any key(s), it will be overwritten.

Configuration
○ Add
Add a new key. You can enter multiple ssh keys in this way.
• Key file
Insert key file.
Save the menu content by clicking on the button Apply.
Note
The user settings can be backed up, see Tools / Maintenance / Backup.
Delete user
Users at level cli_super have a Delete button next to each user. Delete a user using this button
without being asked to confirm deletion. Users at level cli_super cannot both be deleted.
Add user
The button is located on the bottom bar.
For level cli_super users, the "Add user" button is active. Use it to create a new user within any
group.
• Username
Name of new user.
• Group
The group to which this user is assigned.
• New password
Password for this user.
• Confirm password
Repeat password.
• SSH key
If you want the user to have access using ssh protocol and identity verification using ssh key, enter
the ssh key here.
Create a new user account by clicking on the button Apply.
Mirror users
The button is located on the bottom bar.
For level cli_super users, the "Mirror users" button is active. This function will copy all user accounts
from Local unit to Peer unit. All existing user accounts on the Peer unit are deleted.

Configuration
5.4.4. Alarms
Alarms Config
Fig. 5.13: Menu Link settings / Alarms / Config
The diagnostics system of the link monitors the operation of both units.
It generates various event outputs - system warnings and alarms. The event is always written to the
system log and indicated in the status bar and Alarms/Status screen. Some events have adjustable
thresholds. Events with no adjustable thresholds may or may not be Enabled. If they are not Enabled,
the system event is not activated even if the system status is changed.
If the event goes above or below the set parameter limits or a link goes down or up, you can choose
to send an SNMP trap. All SNMP traps are OFF in defaults.
• Inside temperature [°C]

Default >80
Temperature inside the unit (on the modem board). Active if temperature exceeds the threshold.
• Voltage min [V]

Default <40
Lower threshold of supply voltage. Active if voltage drops below min voltage threshold.
The same SNMP trap (same OID) applies for both Voltage min and max.
• Voltage max [V]

Default >58
Upper threshold of supply voltage. Active if voltage rises above max voltage threshold.
The same SNMP trap (same OID) applies for both Voltage min and max.
• RSS [dBm]
Default <-80

Configuration
Received Signal Strength. Active if RSS drops below RSS threshold.
• MSE [dB]
Default >0
Mean Square Error (the inverse to often used SNR - Signal to Noise Ratio). Active if MSE rises above
MSE threshold.
• BER [-]
-6
Default >10e
Bit Error Rate is registered at the receiving end of the link - instantaneous value. Active if BER exceeds
the threshold set in this parameter.
• Net bitrate [Mbps]

Default >0
The system warning is generated when the current transfer capacity of radio channel is lower than
the threshold set in this parameter.
• Air link down

Default on
Interruption of radio link. Active if radio link is interrupted and units can not communicate by Air.
• Eth1/Eth2 link down

Default off
Corresponding user Eth link (Eth1/Eth2) on station interrupted.
Note
The "EthX link" system alarm can only be activated if this alarm is Enabled. When the alarm
is not Enabled, the "EthX link" alarm on Status screen is always "Ok" regardless of the current
status of the Ethernet link.
• WiFi Management
Default on
Warning is generated when WiFi passphrase is not set or WiFi adapter (and Host Access Point) is
permanently enabled (WiFi Force Enable is ON). Parameter can not be changed in web interface
(only through CLI).
• Air capacity changed

Default off
If allowed, the Event and/or SNMP Trap is generated when Net bitrate of the air channel changes
(e.g. because of ACM operation).

Configuration
Alarms Status
Fig. 5.14: Menu Link settings / Alarms / Status
Overview of alarms
All system alarms are listed on this screen. Inactive alarms are colored
white with an "OK" text label. Active alarms are colored according to the
severity of the alarm with a text message describing the measured value
status.
For a detailed description of each Alarm click on the Alarm name.

Fig. 5.15: Alarm severity

Configuration
Alarms Acknowledge
Fig. 5.16: Menu Link settings / Alarms / Acknowledge
Alarm acknowledgement allows the operator to confirm the system is set in alarm state. Only an active
alarm can be acknowledged. Multiple selections of active alarms (to acknowledge groups of alarms)
can be performed using Shift or Ctrl keys.
• Name
Alarm identification - The following alarms can appear:
Inside temperature, Voltage min, Voltage max, RSS, MSE, BER, Net bitrate, Air link, Eth1 link, Eth2
link, RF power, WiFi management
• State
There are three possible alarm states:
○ OK
No alarm (alarm is inactive) or alarm disabled.
○ Ack
Alarm is active and acknowledged.
○ Alarm
Alarm is active and is not acknowledged.
• From

Configuration
Time stamp when the alarm occurred.
• To
Time stamp when the alarm expired (returned to normal conditions).
• Ack
Time stamp when the alarm was acknowledged.
Time stamp format: yyyy-MM-dd hh:mm:ss
• User
Name (login) of the user who acknowledged the alarm.
• Comment
The comment field can be used to add user defined comments when an 'alarm acknowledge' is
performed. Use this comment field to describe important details of the alarm status. The comment
can be up to 50 characters long. Special characters are not allowed.
The alarm can be acknowledged multiple times with different comments. Every acknowledgement
is written to the internal memory and is visible in the alarm log.

Configuration
5.5. Switch settings

Ethernet switch is a key part of the RAy3 unit. It is responsible for data transfer inside the unit - see
Appendix B, Unit block diagrams.
5.5.1. Status
Port status
The unit internal Ethernet switch port status
Fig. 5.17: Menu Switch settings / Status / Port status
• Port name
Identification of the internal switch port. The switch ports are connected to an external port or to an
internal device (radio modem, management CPU).
○ Eth1 (port1)
The external port (with RJ45 interface) labeled "ETH1+POE".
○ Eth2 (port10)
The external port (with SFP interface) labeled "ETH2".
○ CPU (port0)
The internal port to management CPU.
○ Air (port9)
The internal port to radio modem, i.e. link to the peer unit.
• Link status
Ethernet link status can be
○ down
no link signal detected
○ up
link signal detected
• Speed / duplex
Ethernet link Speed and duplex.
○ Speed:
0/100/1000 Mbps.
○ Duplex:
full/half
• SFP info

Configuration
Information about the (optionally) inserted SFP module. The three different types of SFP modules
can be used:
○ Fibre
dual mode with LC connector
○ Fibre
single mode with LC connector
○ Copper
with RJ45 connector
There can be one of the following scenarios:

○ Scenario
message
○ SFP OK
The SFP vendor string read out of SFP module. The vendor, model, connector (RJ45/LC) and
wavelength values are shown. Separate window with more detailed information can be opened
by clicking the "more..." link.
○ No SFP
No SFP module
○ read error
n/a
○ no SFP option
-
• MDIX
Status of the internal crossover of Ethernet cables. (MDIX = internally crossed pairs, MDI = direct
connection, N/A means an unknown state).
• Tx state
Port transmitting status can be
○ transmitting
Normal port operation.
○ paused
Port transmitter is paused due to Pause frames reception.
○ n/a
Info not available.
• Stp state
Ethernet switch port forwarding control.
○ disabled
The switch port is disabled and it will not receive or transmit any frames.
○ forwarding
The switch examines all frames, learning source addresses (SA) from all good frames (except
those from MGMT frames) and receives and transmits all frames as a normal switch.
○ blocking
Only MGMT frames are allowed to enter (ingress) or leave (egress) a Blocked port. All other frame
types are discarded. Learning is disabled on Blocked ports.
○ learning
Only MGMT frames are allowed to enter (ingress) of leave (egress) a Learning port. All other frame
types are discarded but learning takes place on all good non-MGMT frames that are not discarded
owing to being filtered.
• QoS

Configuration
Quality of Service status. It will be available starting from FW version 1.1.1.0. It can present one of
the following values:
○ disabled
QoS functions are disabled.
○ 802.1p
QoS according to 802.1p is enabled.
○ DSCP
QoS according to DSCP is enabled.
○ 802.1p,DSCP
QoS according to 802.1p and DSCP is enabled. The 802.1 prefer tag is selected.
○ DSCP,802.1p
QoS according to 802.1p and DSCP is enabled. The DSCP prefer tag is selected.

Configuration
RMON counters
The unit internal Ethernet switch RMON counters
Fig. 5.18: Menu Switch settings / Status / RMON counters
The Remote Network MONitoring (RMON) MIB was developed by the IETF to support monitoring and
protocol analysis of LANs.
• Port name
○ Eth1 (port1)
○ Eth2 (port10)
○ CPU (port0)

Configuration

○ Air (port9)
The Internal switch port RMON counters
These counters provide a set of Ethernet statistics for frames received on ingress and transmitted on
egress.
Ingress statistics counters
• In good octets
The sum of lengths of all good Ethernet frames received, that is frames that are not bad frames.
• In bad octets
The sum of lengths of all bad Ethernet frames received. Fragments are included.
––––––––––––––––––
• In unicasts
The number of good frames received that have a Unicast destination MAC address.
• In multicasts
The number of good frames received that have a Multicast destination MAC address.
Note
This does not include frames counted in "In broadcasts" nor does it include frames counted
in "In pause".
• In broadcasts
The number of good frames received that have a Broadcast destination MAC address.
• In pause
The number of good frames received that have a Pause destination MAC address (Flow Control
frames). This includes Priority Flow Control Pause frames too.
––––––––––––––––––
• In undersize
Total frames received with a length of less than 64 octets but with a valid FCS.
• In oversize
Total frames received with a length of more than MaxSize octets but with a valid FCS.
• In FCS errors
Total frames received with a CRC error not counted in "In fragments", "In jabber" or "In RX" errors.
• In fragments
Total frames received with a length of less than 64 octets and an invalid FCS.
• In jabber
Total frames received with a length of more than MaxSize octets but with an invalid FCS.
• In RX errors
Total frames received with an RxErr signal from the PHY.
––––––––––––––––––
• In discards
The number of good, non-filtered frames that are received but cannot be forwarded due to a lack of
buffer memory.
• In filtered
The number of good frames that were not forwarded due to ingress policy filtering rules.
• In accepted
The number of good frames that are not policy filtered nor discarded due to an error and made it
through the Ingress process and is presented to the Queue Controller.

Configuration
• In bad accepted
The number of good frames that were not forwarded due to ingress policy filtering rules.
• In good AVB A, B
The number of good AVB frames received that have a Priority Code Point for Class A (or B) that are
not Undersize nor Oversize and are not discarded or filtered.
• In bad AVB A, B
The number of bad AVB frames received that have a Priority Code Point for Class A (or B) that are
not Undersize nor Oversize.
• In TCAM 0 ... 3
The number of good frames received that have a TCAM Hit on a TCAM Entry that has its IncTcamCtr
bit set to a one and its FlowID[7:6] = 0 ... 3 and are not discarded or filtered. This allows this counter
to be used for any purpose as programmed in the TCAM.
• In dropped AVB A, B
The number of good AVB frames received that have a Priority Code Point for Class A (or B) that are
not Undersize nor Oversize and are not discarded or filtered but were not kept by the switch due to
a lack of AVB buffer.
• In DA unknown
The number of good frames received that did not have a Destination Address 'hit' from the ATU (i.e.,
the frame's DA was not in the address database) and are not discarded or filtered.
• In management
The number of good frames received that are considered to be Management frames and are not
discarded (i.e., the frame's size is legal and its CRC is good or it was forced good by register. Remote
Management frames are counted regardless if the RMU accepted them or not.
Egress statistics counters
• Out octets
The sum of lengths of all Ethernet frames sent from this MAC.
• Out FCS errors
The number of frames transmitted with an invalid FCS. Whenever a frame is modified during trans-
mission (e.g., to add Out FCS errors or remove a tag) the frame’s original FCS is inspected before
a new FCS is added to a modified frame. If the original FCS is invalid, the new FCS is made invalid
too and this counter is incremented.
––––––––––––––––––
• Out unicasts
The number of frames sent that have a Unicast destination MAC address.
• Out multicasts
The number of good frames sent that have a Multicast destination MAC address.
Note
This does not include frames counted in "Out broadcasts" nor does it include frames counted
in "Out pause".
• Out broadcasts
The number of good frames sent that have a Broadcast destination MAC address.
• Out pause
The number of Flow Control frames sent. This includes Pause and Priority Flow Control frames.
––––––––––––––––––
• Out collisions
The number of collision events seen by the MAC not including those counted in "Out Single", Multiple,
Excessive, or Late. This counter is applicable in half-duplex only. See Auto negotiation.
• Out deferred

Configuration
The total number of successfully transmitted frames that experienced no collisions but are delayed
because the medium was Out deferred busy during the first attempt. This counter is applicable in
halfduplex only.
• Out single
The total number of successfully transmitted frames that experienced exactly one collision. This
counter is applicable in halfduplex only.
• Out multiple
The total number of successfully transmitted frames that experienced more than one collision. This
counter is applicable in halfduplex only.
• Out late
The number of times a collision is detected later than 512 bitstimes into the transmission of a frame.
This counter is applicable in half-duplex only.
• Out excessive
The number frames dropped in the transmit MAC because the frame experienced 16 consecutive
collisions. This counter is applicable in half-duplex only.
• Out queue 0 ... 7
The number of frames that egress this port from Queue 0 ... 7. It does not matter if these frames had
a good CRC or not.
• Out cut through
The number of frames that egress this port from the Cut Through path. It does not matter if these
frames had a good CRC or not nor what the frame's size was.
• Out octets A, B
The sum of lengths of all Ethernet frames sent from the AVB Class A (or B) Queue not including
frames that are considered Out octets A, B Management by Ingress. The purpose of this counter is
to measure the actual used rate of the shaper for stream data. The actual data rate from any queue,
AVB or not, can be measured with this counter, however.
• Out yellow
The number of Yellow frames that egressed this port (i.e., the number of Yellow frames that success-
fully made it through the queue controller).
• Out dropped yellow
The number of Yellow frames not counted in "In discards" that are 'head dropped' from an egress
port's queues and the number Out dropped yellow of Yellow frame's 'tail dropped' from an egress
port's queues due to Queue Controller's queue limits.
Frame size histogram counters
• Size 64 octets
Total frames received (and/or transmitted) with a length of exactly 64 octets, including those with
errors.
• Size 65-127 octets

Total frames received (and/or transmitted) with a length of between 65 and 127 octets inclusive, in-
cluding those with errors.

Total frames received (and/or transmitted) with a length of between 128 and 255 octets inclusive,
including those with errors.


Configuration
• Size 1024-max octets

Total frames received (and/or transmitted) with a length of between 1024 and MaxSize (see MTU
parameter) octets inclusive, including those with errors.
• Histogram counters mode

Frame size histogram counters can count received and/or transmitted octets. The mode of histogram
counters is indicated here.
• Measure time
This is the time interval, the diff column is valid for. The "diff" column shows the difference of the
actual value of the counters at the moment of pressing the Difference button and the value of the
counters at the moment of pressing the Refresh button.
• Refresh Difference
In another way: The Difference counter reference value can be reset by pressing the Refresh button.
The time point at which the Difference counter sample is triggered and the "diff" value is calculated
is defined by pressing the Difference button. The "total" column always shows the actual values. It
is refreshed either by pressing the Refresh and also the Difference button.
RSTP status
This page and RSTP root bridge functionality is available only for FW 1.0.19.0 and earlier.
Page allows to check the status of RSTP root bridge daemon. For more information about RSTP and
root bridge settings see section 5.5.3. Advanced / RSTP setup.
Fig. 5.19: Menu Switch settings / Status / RSTP status
The page calls CLI command which checks the status of RSTP root bridge daemon (running or not
running).

Configuration
5.5.2. Interface
Port setup
Configuration of port settings
Fig. 5.20: Menu Switch settings / Interface / Port
• Port name
○ Eth1 (port1)
○ Eth2 (port10)
○ CPU (port0)
○ Air (port9)
• Label
Name of each port on the switch (up to 15 characters).
• Port enable
Enables functionality of individual port on the switch. Each port can be enabled or disabled.
Warning
When the port is disabled, no communication is possible through this port.
• Auto negotiation

Configuration
Enables Auto-Negotiation functionality of individual port. Negotiation is an Ethernet procedure by

which two connected devices choose common transmission parameters, such as speed, duplex
mode and flow control. In this process, the connected devices first share their capabilities regarding
these parameters and then choose the highest performance transmission mode they both support.
The device supports three types of Auto-Negotiation:
○ 10/100/1000BASE-T Copper Auto-Negotiation. (IEEE 802.3 Clauses 28 and 40)
○ 1000BASE-X Fibre Auto-Negotiation (IEEE 802.3 Clause 37)
○ SGMII Auto-Negotiation (Cisco specification)
Auto-Negotiation provides a mechanism for transferring information from the local unit to the link
partner to establish speed, duplex and Master/Slave preference during a link session.
Auto-Negotiation is initiated upon any of the following conditions:
○ Power up reset
○ Hardware reset
○ Software reset
○ Restart Auto-Negotiation
○ Transition from power down to power up
○ The link goes down
The 10/100/1000BASE-T Auto-Negotiation is based on Clause 28 and 40 of the IEEE 802.3 spe-
cification. It is used to negotiate speed, duplex and flow control over CAT5 (or higher) UTP cable.
Once Auto-Negotiation is initiated, the device determines whether or not the remote device has Auto-
Negotiation capability. If so, the device and the remote device negotiate the speed and duplex with
which to operate.
If the remote device does not have Auto-Negotiation capability, the device uses parallel detect
function to determine the speed of the remote device for 100BASE-TX and 10BASE-T modes. If a
link is established based on the parallel detect function, it is then required to establish the link at half-
duplex mode only. Refer to IEEE 802.3 clauses 28 and 40 for a full description of Auto-Negotiation.
1000BASE-X Auto-Negotiation is defined in Clause 37 of the IEEE 802.3 specification. It is used
to auto-negotiate duplex and flow control over fibre cable.
If one side of the link enables 1000BASE-X Auto-Negotiation and the link partner does not, the link
cannot linkup. The device implements an Auto-Negotiation bypass mode.
SGMII Auto-Negotiation. SGMII is a de-facto standard designed by Cisco. SGMII uses 1000BASE-
X coding to send data as well as Auto-Negotiation information. However, the contents of the SGMII
Auto-Negotiation are different than the 1000BASE-X Auto-Negotiation.
Warning
If one device provides Auto-negotiation and the other works with a manual link parameters
setting (i.e. without Auto-negotiation) the link operates in half-duplex mode. If the manual
setting is set to full-duplex, the "Out collisions" may occur.
• Speed / duplex
Ethernet link speed and duplex mode can be selected. Both parameters can be either auto negotiated
or set manually. When the Auto negotiation parameter is disabled, only manual setting of the speed
and duplex is possible. In most cases it is better to enable the auto negotiation and use "auto / auto"
speed and duplex settings.
There are two possibilities to force the link to operate in specific speed and duplex:
○ Auto negotiation enabled. Select the desired Speed / duplex. The auto negotiation process advert-
ises only this specified link mode. The link partner is asked to use it.

Configuration
○ Auto negotiation disabled. Select the desired Speed / duplex. The link is set to this specified link
mode. The link partner has to be set manually to the same mode.
• Frame mode
Ethernet Frame mode control defines the expected Ingress and the generated Egress tagging frame
format for this port as follows:
○ normal
Normal Network mode uses industry standard IEEE 802.ac Tagged or Untagged frames. Tagged
frames use an Ether Type of 0x8100. Ports that are expected to be connected to standard Ethernet
devices should use this mode
○ DSA
Inactive options are not required.
○ provider
Provider mode uses user definable Ether Types per port (see Ether type parameter) to define that
a frame is Provider Tagged. Ports that are connected to standard Provider network devices, or
devices that use Tagged frames with an Ether Type other than 0x8100 should use this mode.
Frames, that ingress this port with an Ether Type that matches the port's "Ether Type" parameter
will be considered tagged, will have the tag's VID and PRI bits assigned to the frame (i.e. they will
be used for switching and mapping), and will have the Provider Tag removed from the frame. If
subsequent Provider Tags are found following the 1st Provider Tag, they too will be removed from
the frame with their VID and PRI bits being ignored. Modified frames will be padded if required.
Frames, that ingress this port with an Ether Type that does not match the "Ether Type" parameter
will be considered untagged. The ingressing frames are modified so they are ready to egress out
Customer ports (Normal Network Frame Mode ports) unmodified.
Frames that egress this port will always have a tag added (even if they were already tagged). The
added tag will contain this port's "Ether Type" as its Ether Type. The PRI bits will be the Frame
Priority assigned to the frame during ingress. The VID bits will be the source port's Default VID
bits (if the source port was in Normal Network mode), or the VID assigned to the frame during in-
gress (if the source port was in Provider mode).
○ ether type DSA

Valid only for the "p5 CPU" port.
Ether Type DSA mode uses standard Marvell DSA Tagged frame information following a user
definable Ether Type (see Ether type parameter). This mode allows the mixture of Normal Network
frames with DSA Tagged frames and is useful on ports that connect to a CPU.
Frames that ingress this port with an Ether Type that matches the port's "Ether Type" will be con-
sidered DSA Tagged and processed accordingly. The frame's Ether Type and DSA pad bytes will
be removed so the resulting frame will be ready to egress out Marvell DSA Tag Mode ports unmod-
ified. Frames that ingress this port with a different Ether Type will be considered Normal Network
Frames and processed accordingly.
Marvell DSA Tag control frames that egress this port will always get the port's "Ether Type" inserted
followed by two pad bytes of 0x00 before the DSA Tag. Marvell DSA Tag Forward frames that
egress this port can egress just like the control frames (with the added Ether Type and pad) or
they can egress as if the port was configured in Normal Network mode. This selection is controlled
by the port's Egress Mode bits above.
• Ether type

Configuration
Ethernet frame type (often called EtherType) is used to indicate which protocol is encapsulated in
the payload of an Ethernet Frame. This parameter is important when one protocol is encapsulated
to another protocol.
Examples:
Ether type Standard Comment

0x8100 IEEE 802.1q Double-tagged, Q-in-Q or C-tag stacking
on C-tag. C-tag in IEEE 802.1ad frames.
0x88a8 IEEE 802.1ad S-Tag
0x88e7 IEEE 802.1ah S-Tag (backbone S-Tag)
0x9100 -- It is used very often. For example an old
non-standard 802.1QinQ protocol uses
this value.
See http://en.wikipedia.org/wiki/EtherType for further details.
• MTU [B]
Defines maximum transmission unit (MTU) frame size allowed to be received or transmitted from or
to a given physical port. This implies that a Jumbo frame may be allowed to be received from a given
input port but may or may not be allowed to be transmitted out of a port or ports.
The possible values are 1522, 2048 and 10240 Bytes.
Note
The definition of frame size is counting the frame bytes from MAC_DA through Layer2 CRC
of the frame.
• Flow control send/receive (previously TX/RX)

It is the mechanism for temporarily stopping the transmission of data on an Ethernet network, so that
the receiving node is not overwhelmed with data from transmitting node. It works according IEEE
802.3x standard. If allowed, speed of data receive in to the switch (from the connected device) is
regulated by the switch sending out flow control pause frames (according parameter 'Pause limit
out') to the connected device. If allowed, speed of data transmission out from the switch (to the
connected device) is regulated by processing received in flow control pause frames (according
parameter 'Pause limit in') sent by the connected device.
Enabling flow control allows use of buffers of connected active network elements for leveling uneven
flow of user data. For correct operation it is necessary to also enable Flow control on the connected
device. Flow control is handled by sending Pause frames to the connected device. Possible values:
○ off
Flow control is disabled.
○ on
Flow control is enabled (forced to be active).
○ auto
Sending pause packets is advertised and depends on result on the auto-negotiation process. Auto-
Negotiation has to be supported and enabled on the port to take effect.
Important
For optimal utilization of Ethernet switch buffers and maximal operational speed of the link
it is recommended to upgrade unit to the latest FW version and apply its defaults to ensure
optimal buffers cooperation.

Configuration
Note
Additional link performance and better utilization of all available buffers in transmitting network
could be typically achieved by configuring Flow Control between the MW unit and the nearest
switches feeding the link by data. Important for incoming data are parameters 'Flow Control
send' on ports 'Eth1(p1)' and/or 'Eth2(p10)', which needs to be set to values 'auto' or 'on'
(the value to use depends on the switch).
FW versions 1.0.16.0 and earlier require RX Flow Control for port 'Air (p9)' on both units to
be set to 'on'. The only exception is FW version 1.0.14.0 with activated 'Unit 24S compatib-
ility' (for more info see 'Setting up a link between RAy3-24S and other hardware variant of
RAy3-24' in Chapter 8, Troubleshooting).
• Pause limit in [frame]

Value limits the number of continuous Pause refresh frames that can be received on this port (if full-
duplex) or the number of 16 consecutive collisions (if half-duplex). Pause limit in [frame] When a port
has flow control enabled, this parameter can be used to limit how long this port can be Paused or
Back Pressured off to prevent a port stall through jamming. The Flow Control on the port is (tempor-
arily) disabled when the Pause refresh frames count exceeds the value of this parameter.
Setting this parameter to 0 will allow continuous jamming to be received on this port.
• Pause limit out [frame]

Value limits the number of continuous Pause refresh frames that can be transmitted from this port
– assuming each Pause refresh is for the maximum pause time of 65536 slot times. When full-duplex
Flow Control is enabled on this port, this parameter is used to limit the number of Pause refresh
frames that can be generated from this port to keep this port’s link partner from sending any data.
Clearing this parameter to 0 will allow continuous Pause frame refreshes to egress this port as long
as this port remains congested.
Setting this parameter to 1 will allow 1 Pause frame to egress from this port for each congestion
situation.
Setting this parameter to 2 will allow up to 2 Pause frames to egress from this port for each congestion
situation, etc.
• Ignore checksum
Enables ignoring Frame checksum (FCS) - or in other words - Force good FCS in the frame. When
this parameter is not set (default behavior), frames entering this port must have a good CRC or else
they are discarded. When this parameter is set, the last four bytes of frames received on this port
are overwritten with a good CRC and the frames are accepted by the switch (assuming that the
frame’s length is good and it has a destination).

Configuration
PIRL setup
Page allows to configure PIRL - Port-based Ingress Rate Limiting. It is a useful feature to limit bursts
and storms of packets according different services, priorities and other network parameters to optimize
the usage of limited capacity of RAy wireless link.
Fig. 5.21: Menu Switch settings / Interface / PIRL
The device supports per port TCP/IP ingress rate limiting along with independent Storm prevention.
Port based ingress rate limiting accommodates information rates from 64 Kbps to 1 Mbps in increments
of 64 Kbps, from 1 Mbps to 100 Mbps in increments of 1 Mbps and from 100 Mbps to 1000 Mbps in
increments of 10 Mbps.
In addition to this, the device supports Priority based ingress rate limiting. Given ingress rate resource
can be configured to track any of the four priority traffic types. The device supports a color- blind leaky
bucket scheme, one of the popular schemes for implementing rate limiting. The way a leaky bucket
scheme works is that the bucket drains tokens constantly at a rate called Committed Information Rate
(CIR) and the bucket gets replenished with tokens whenever a frame is allowed to go through the
bucket. All calculations for this bucket are done in tokens. Therefore, both bucket decrementing and
incrementing is performed using tokens (i.e. frame bytes are converted into bucket tokens for calculation
purposes).
The traffic below Committed Burst Size limit (CBS Limit) is passed without any further actions. If the
traffic burst were to continue and the bucket token depth approaches closer to the Excess Burst Size
limit (EBS Limit) by less than the CBS Limit, then a set of actions are specified. Note that if the frame
gets discarded then the equivalent number of tokens for that frame will not get added to the bucket.
Fig. 5.22: PIRL EBS and CBS limits

Configuration
There are two default ingress limiting rules already configured in the switch default configuration. They
limit the maximum allowed ARP traffic coming to the CPU port to 10 Mbps from Eth1 and 10 Mbps
from Eth2 ports.
• Primary key
The icon indicates which parameter field is taken as the unique identifier in the database. This field
entry ensures each record is unique and must not be duplicated.
• Port name
Identification of the internal switch port, see Section 5.5, “Switch settings”.
• ID
Unique ID of ingress rate resource. Each port can be assigned up to five different ingress rate re-
sources.
Each resource defines a rule (filter) for the incoming frame. If the rule is met, the frame is affected
(as set by the EBS limit action parameter). If the incoming frame doesn't meet any rule, it is not affected
by PIRL. The frame is accepted and forwarded further to the switch engine.
• Rate [Mbps or fps]

The Bucket Rate. It is dependent on the Bucket Rate factor and the Bucket increment.
The calculation is estimated as the real data throughput depends on frame size. The Accounted
bytes parameter affects this as well.
The formula for the rate (in bits or frames per second) is as follows:
rate = α * BRF / BI.
Where α is constant, which is 62 500 000 for Accounted bytes="frame", and is 500 000 000 for Ac-
counted bytes="layer1". BRF is Bucket Rate factor and BI is Bucket increment.
• Size [kB]
The Burst allocation buffer size depends on the Bucket increment, the Committed Burst Size limit or
the Excess Burst Size limit.
The formula for the BA is as follows:
BA = xBS / BI.
Where xBS can be either the Committed Burst Size limit CBS for the green bucket size or the Excess
Burst Size limit EBS for the yellow bucket size and BI is the Bucket increment.
In order for the rate limiting to be accurate, it is required that bucket size is larger than max frame
size (MTU).
The Burst allocation size should be less than switch internal memory which is 250 kB.
• Mode
Rate type or Traffic type of rate limiting. See Bucket type parameter.
• Edit
Press Edit to edit selected PIRL resource.
• Delete
Press Delete to delete selected PIRL resource.
• Add resource
Press Add resource button to add another PIRL resource.

Configuration
PIRL resource configuration (after clicking on 'Add resource' button)
Fig. 5.23: Menu Switch settings / Interface / PIRL / Add resource
Each port can be assigned up to five different ingress rate resources.
Each resource defines a rule (filter) for the incoming frame. If the rule is met, the frame is affected (as
set by the EBS limit action parameter). If the incoming frame doesn't meet any rule, it is not affected
by PIRL. The frame is accepted and forwarded further to the switch engine.
• Port name
• ID
Unique ID of ingress rate resource - see its detailed explanation on previous page.
• Rate [Mbps or fps]

The Bucket Rate - see its detailed explanation on previous page.
• Size [kB]
The Burst allocation buffer size - see its detailed explanation on previous page.
• Accounted bytes

Configuration
This parameter determines which frame bytes are to be accounted for in the rate resource's rate
limiting calculations.
There are four different supported configurations:
○ Frame
Frame based configures the rate limiting resource to account for the number of frames from a
given port mapped to this rate resource.
○ layer 1
Preamble (8bytes) + Frame’s DA to CRC + IFG (inter frame gap, 12 bytes)
○ layer 2
Frame’s DA to CRC
○ layer 3
Frame’s DA to CRC - 18 - 4 (if the frame is tagged)
A frame is considered tagged if it is either Customer of Provider tagged during ingress.
• Bucket increment
Bucket increment (BI) indicates the amount of tokens that need to be added for each byte of the in-
coming frame.
• Bucket rate factor

This is a factor (green or yellow) which determines the amount of tokens that need to be decremented
for each rate resource decrement (which is done periodically based on the Committed Information
Rate).
• Burst size limit

Excess Burst Size limit - used for the yellow bucket.
Committed Burst Size limit - used for the green bucket.
• Color mode
Single rate two color, Single rate three color, Dual rate three color.
• Account green overflow

false = Green and Yellow buckets are isolated when in Color Aware mode
true = Green and Yellow buckets are connected when in Color Aware mode
• Account discarded frames

This parameter decides whether the ingress rate limiting logic accounts for frames that have been
discarded by the queue controller due to output port queue congestion reasons. To account for all
frames coming into a given port associated with this rate resource, this parameter needs to be set.
• Account filtered frames

This parameter decides whether the ingress rate limiting logic accounts for frames that have been
discarded because of ingress policy violations. To account for all frames coming into a given port
associated with this rate resource, this parameter needs to be set.
• Color aware
false = color blind mode
true = color aware mode
• EBS limit action

This parameter controls what kind of action is performed when the EBS limit has been exceeded.
Two types of action can be selected:
○ drop
The frame that was received on the port will get discarded.

Configuration
○ flow control
The frame that was received on the port will get discarded.
In this mode an Ethernet flow control frame gets generated (if the flow control is enabled for that
port) and sent to the source port but the incoming frame gets passed through the rate resource.
If the port is operating in half-duplex mode then the port gets jammed.
Flow control mode is expected to be programmed on ports that have a trusted flow control mechanism
available. The EBS limit action is a per-port characteristic. If a port has multiple rate resource buckets
then all buckets enabled are expected to be programmed with the same EBS limit action.
• Flow control de-assertion

This parameter controls the flow control de-assertion when EBS limit action is set to generate a flow
control message. There are two modes available:
○ empty
Flow control gets de-asserted only when the ingress rate resource has become empty.
○ CBS limit
Flow control gets de-asserted when the ingress rate resource has enough room to accept at least
one frame of size specified by the CBS limit.
For example, if the CBS limit is programmed to be 2k Bytes, then the flow control will get de-asserted
if there is at least 2k Bytes worth of tokens available in the ingress rate resource.
• Mask operation
This parameter controls whether an ingress frame must meet both Priority and Frame type require-
ments to be counted for ingress rate calculations or if meeting only one requirement is sufficient to
be counted for ingress rate calculations for this rate resource.
• Priority type
frame - use FPri assigned to the frame
queue - use QPri assigned to the frame
• Priority
Any combinations of the eight queue priorities can be selected. Frames with marked priority are ac-
counted for in this ingress rate resource.
If there is no priority selected, priority of the frame does not have any affect on the ingress rate limiting
calculations done for this ingress rate resource.
• Frame type
Any of the following frame types can be selected to be tracked as part of the rate resource calculations:
Unknown unicasts, Unknown multicasts, Unknown broadcast, Multicasts/Broadcasts, Unicasts,
Network management, ARP (Address Resolution Protocol), TCP data, TCP control, UDP, group
IGMP, ICMP, GRE, IGRP and L2TP covers Non-TCPUDP, Ingress monitor source, Policy mirror,
Policy trap.
More than one frame type can be selected for a given rate resource.

Configuration
Egress queues setup
The Egress queue page allows to set parameters for four output (egress) queues available in internal
Ethernet switch of RAy unit.
Each queue is used to store frames with given priority (as set in 802.1p and DSCP configuration). The
queue depth is controlled dynamically to reach maximum utilization of the switch memory. The queue
frame egress is controlled by scheduling algorithms as described further below.
Fig. 5.24: Menu Switch settings / Interface / Egress queue
• Port name
• Scheduling mode
Port's Scheduling mode.
The device supports strict priority, weighted round robin, or a mixture on a per egress port selection
basis.
In the strict priority scheme all top priority frames egress for a port until that priority’s queue is empty,
then the next lower priority queue’s frames egress, etc. This approach can cause the lower priorities
to be starved out preventing them from transmitting any frames but also ensures that all high priority
frames egress the switch as soon as possible.
In the weighted scheme an 8, 4, 2, 1 weighting is applied to the four priorities unless an alternate
weighting is programmed into the QoS Weights Table. This approach prevents the lower priority
frames from being starved out with only a slight delay to the higher priority frames.
Some applications may require the top priority queue, or the top two priority queues to be in a fixed
priority mode while the lower queues work in the weighted approach. All scheduling modes are se-
lectable on a per port basis.
The port scheduling mode can be one of the following values:
○ weighted RRB
Use a weighted round robin queuing scheme.
○ strict pri 3
Use Strict for priority 3 and use weighted round robin for priorities 2,1 and 0.
○ strict pri 3, 2
Use Strict for priorities 3 and 2 and use weighted round robin for priorities 1 and 0.
○ strict
Use a Strict priority scheme for all priorities.
• Count mode

Configuration
Egress rate limiting count mode. This parameter is used to control which bytes in the transmitted
frames are counted for egress rate limiting as follows:
○ frame
The egress rate limiting is done based on frame count [fps] as opposed to the byte count [kbps]
of the packet.
○ layer 1
Preamble (8bytes) + Frame’s DA to CRC + IFG (inter frame gap, 12 bytes)
○ layer 2
Frame’s DA to CRC
○ layer 3
Frame’s DA to CRC - 18 - 4 (if the frame is tagged)
Only one tag is counted even if the frame contains more than one tag. A frame is considered tagged
if the egress frame going out onto the wire is tagged.
• Rate limit
Egress data rate shaping. When Rate = 0 egress rate limiting is disabled.
Note
The Count mode parameter is used to control which bytes in the transmitted frames are
counted for egress rate limiting.
If the egress shaping is controlled by frame rate, the desired frame rate can vary from 7.6k to 1.488M
frames per second. Valid values are between 7632 and 1488000.
If the egress shaping is controlled by bit rate, the desired rate can vary from 64 kbps to 1 Gbps in
the following increments:
○ Desired rate between 64 kbps and 1 Mbps in increments of 64 kbps
○ Desired rate between 1 Mbps to 100 Mbps in increments of 1 Mbps
○ Desired rate between 100 Mbps to 1 Gbps in increments of 10 Mbps
Therefore, the valid values are:

○ 64, 128, 192, 256, 320, 384,..., 960,
○ 1000, 2000, 3000, 4000, ..., 100000,
○ 110000, 120000, 130000, ..., 1000000.
• Frame overhead [B]

This parameter is used to adjust the number of bytes that need to be added to a frame’s IFG (inter
frame gap) on a per frame basis. This is to compensate for a protocol mismatch between the sending
and the receiving stations. For example, if the receiving station were to add more encapsulations to
the frame for the nodes further downstream, this per frame adjustment would help reduce the con-
gestion in the receiving station.
This adjustment, if enabled, is added to the Egress Rate Control’s calculated transmitted byte count
meaning Egress Rate Control must be enabled for this Frame Overhead adjustment to work.
• Weight table
The weighted round robin alternate weighting can be defined here. The sequence of the output queue
numbers (0,1,2 to 7) defines the sequence of the output queue frame egressing. This sequence can
be up to 128 items long.

Configuration
5.5.3. QoS
Quality of Service (QoS) is the ability to provide different priorities to different applications, users, or
data flows, or to guarantee a certain level of performance to a data flow. QoS using 802.1p and DSCP
are implemented.
The ingress block has the task of determining the priority of each frame to be used for the internal
Queue Controller (QPri) as well as the priority assigned to the frame (FPri) if the frame egresses the
switch tagged. The classification as to if the frame is discard eligible (Yellow) is also determined. The
Ingress block does not perform the QoS switching policy, which is the task of the Queue Controller.
Instead, it has the job of determining the QPri and FPri assigned to each frame for the Queue Controller
and Egress block.
Port
Port based QoS parameters makes it possible to control QoS based on the ingress port.
Every frame entering the switch gets two priority values assigned to it. One priority value is used inside
the switch only to determine which output queue the frame is to be mapped into. This is called QPri for
queue priority. The other priority value is used outside the switch only to mark the frame’s IEEE PCP
bits if the frame egresses a port tagged. This is called FPri for frame priority. A third parameter, called
Yellow, is also assigned to the frame. If Yellow=1 the frame is considered eligible for discard if congestion
warrants it.
The initial QPri, FPri and Yellow values are assigned differently to various frame types. Some frames
are assigned more than one set of QPri, FPri and Yellow values. For example, an IEEE tagged IPv4
frame will get a set of values from the IEEE tag, another set from the IPv4 header and another set from
the port. Some applications require that the port’s default priority be used regardless of the contents
of the frame. The Initial priority parameter selects this default priority.
Fig. 5.25: Menu Switch settings / QoS / Port
• Update DSCP
If the parameter is enabled, the DSCP field in frames that egress this port is updated.
• Default frame priority

All ingressing frames are assigned a default FPri (frame priority) and QPri (queue priority). The default
value for Yellow is zero (i.e. the frame is not discarded eligible).
• Default queue priority

All ingressing frames are assigned a default FPri (frame priority) and QPri (queue priority).

Configuration
802.1p ingress
The IEEE 802.1p QoS technique also known as class of service (CoS), is using a 3-bit field called the
Priority Code Point (PCP) within an Ethernet frame header when using VLAN tagged frames as defined
by IEEE 802.1Q. It specifies a priority value of between 0 and 7 inclusive that can be used by QoS
disciplines to differentiate traffic. The value 0 is generally taken as the lowest priority and 7 as the
highest priority.
Fig. 5.26: Menu Switch settings / QoS / 802.1p ingress
• Priority code point (PCP)

Priority Code Point (PCP) value to which the following parameters (Yellow, Frame Enable, Frame
Priority, Queue Enable and Queue Priority) belong to.
• 802.1p yellow
When this parameter is enabled any IEEE tagged frame (having given PCP priority) that accesses
this port will be given an initial IEEE color of Yellow. This color will be assigned to the frame using
the same rules used to select the frame’s initial FPri and QPri values.
• Enable 802.1p frame priority

When the Frame Enable parameter is checked, the Frame Priority (FPri) mapping is enabled.
• 802.1p frame priority

The Frame Priority value is taken as the frame’s initial IEEE FPri in case the Frame Enable is checked.
• Enable 802.1p queue priority

When the Queue Enable parameter is checked, the Queue Priority (QPri) mapping is enabled.
• 802.1p queue priority

The Queue Priority value is taken as the frame’s initial IEEE QPri in case the Queue Enable is
checked.

Configuration
802.1p egress
Fig. 5.27: Menu Switch settings / QoS / 802.1p ingress
• Frame priority for 802.1p mapping

Frame priority value to which the following Green and Yellow parameters (VID marking, PCP marking
and PCP) belong to.
• VID marking
Enable/disable VID marking for the given Frame priority. When the parameter is disabled frames
assigned with this FPri in ingress will not get their VID field updated even if the frame egresses
Tagged (normally all egressing Tagged frames get their VID updated to the value assigned in ingress).
• PCP marking
Enable/disable PCP marking for the given Frame priority. When the parameter is disabled frames
assigned with this FPri in ingress will not get their PCP & CFI fields updated even if the frame egresses
Tagged (normally all egressing Tagged frames get their FPri & CFI bits updated to the value assigned
in ingress).
• 802.1p frame PCP

Frame Priority Code Point. This parameter contains the new PCP or FPri value that is assigned to
frames that egress this port. The FPri assigned to the frame in ingress is used to access this table.

Configuration
DSCP ingress
The DSCP stands for Differentiated services Code Point which is a 6-bit value stored within the IP
header. The QoS techniques using those bits are called DiffServ or Differentiated services.
Fig. 5.28: Menu Switch settings / QoS / DSCP ingress
• DSCP
DSCP value to which the following parameters (Yellow, Frame Enable, Frame Priority, Queue Enable
and Queue Priority) belong to.
• DSCP Yellow
When this parameter is enabled any IP frame that accesses this entry will be given an initial IP color
of Yellow. This color will be assigned to the frame using the same rules to select the frame’s initial
FPri and QPri values.
• Enable DSCP frame priority

When this parameter is enabled, the Frame Priority Mapping will be used.
• DSCP frame priority

The value set in this parameter is used as the frame’s initial IP Frame priority as long as Enable is
checked.
• Enable DSCP queue priority

When this parameter is enabled, the queue Priority mapping will be used.
• DSCP queue priority

The value set in this parameter is used as the frame’s initial IP Queue priority as long as Enable is
checked.

Configuration
DSCP egress
Fig. 5.29: Menu Switch settings / QoS / DSCP egress
• Port name
Selects the port on Eth switch for which settings below are shown/updated.
• Frame priority
Frame priority value for DSCP mapping to which the following Green and Yellow parameters (DSCP
marking and DSCP) belong to.
• DSCP marking
When this parameter is enabled for some Frame priority, the Frame Priority Mapping will be used,
i.e. IP frames assigned with this FPRi in ingress will get their DSCP fields updated.
• DSCP
This parameter defines the new DSCP value that is assigned to frames that egress this port. The
FPri assigned to the frame in ingress is used to access this table.
5.5.4. Advanced
VLAN setup
The VLAN (Virtual LAN) page allows to set VLAN related and global parameters needed for VLAN
functionality of RAy unit.
Important
Parameters in VLAN page are tightly related to the settings configured in pages STU and
VTU. For a proper functionality all parameters inside pages VLAN, STU and VTU have to
correspond to each other.

Configuration
Fig. 5.30: Menu Switch settings / Advanced / VLAN
• Remove one provider tag

When this parameter is enabled and a port is configured as a Provider Port, recursive Provider Tag
stripping will NOT be performed. Only the first Provider Tag found on the frame will be extracted and
removed. Its extracted data will be used for switching.
When this parameter is disabled and a port is configured as a Provider Port, recursive Provider Tag
stripping will be performed. The first Provider Tag's data will be extracted and used for switching,
and then all subsequent Provider Tags found in the frame will also be removed. This will only occur
if the port's "Ether type" is not 0x8100 (recursive Provider Tag removal cannot be performed when
the Provider's Ether Type is equal to 0x8100).
• VTU page mode

The VTU page mode supports alternate VID look up results based on if a frame is a Multicast (including
Broadcasts) or not, or based on what source port the frame came in on, or if the frame was properly
Provider tagged or not.
• Port name
• Egress modeThis parameter determines the makeup of frames when they egress this port. The
Egress mode behavior is affected by the Frame mode (menu Interface/Port advanced/Frame mode)
parameter.
Frame mode ... normal:
○ unmodify ... Frames are transmitted unmodified.
○ untag ... Remove the tag from any tagged frame.
○ tag ... Add a tag (e.g. according to "Default VID") to any untagged frame. Ethernet frame type is
set to 0x8100.

Configuration
Frame mode ... provider:

○ unmodify ... Use this mode when "Frame mode" is set to "provider".
○ untag ... not used
○ tag ... not used
Frame mode ... ether type DSA:

○ unmodify ... not used
○ untag ... not used
○ tag ... not used
○ ether type tag ... Add a tag (e.g. according to "Default VID") to any untagged frame. Ethernet frame
type is set according to "Ether type" parameter (menu Switch settings/Interface/Port advanced).
• 802.1q modeThis parameter determines if 802.1q base VLANs are used along with port based
VLANs for this Ingress port. It also determines the action to be taken if an 802.1q VLAN Violation is
detected. VLAN barriers (both port based and 802.1q based) can be bypassed by VLAN Tunnel.
○ disabled
Use Port Based VLANs only. The VID assigned to the frame is the port's Default VID which is used
as the VID in the Provider Tag if the frame egresses a Provider port.
○ fallback
Enable 802.1q for this Ingress port. Do not discard Ingress Membership violations and use the
VLAN Table bits if the frames' VID is not contained in the VTU.
The ingressing frames are not discarded and it doesn't matter if the frames' VID is a member of
the VTU.
○ check
Enable 802.1q for this Ingress port. Do not discard Ingress Membership violation but discard the
frame if its VID is not contained in the VTU.
The ingressing frames' VID must be configured in the VTU to enable it to ingress. The VTU
"Member tag" parameter doesn't have any effect.
○ secure
Enable 802.1q for this Ingress port. Discard Ingress Membership violations and discard frames
whose VID is not contained in the VTU.
The ingressing frame is checked fully against the record in the VTU table. The "VID" and the
"Member tag" parameters are validated to allow the frame to ingress.
• Discard tagged
When this parameter is enabled all non-MGMT frames that are processed as tagged are discarded
as they enter this switch port. Priority only tagged frames (with a VID of 0x000) are considered un-
tagged. This feature works whether 802.1q is enabled on the port or not.
If the port is configured in Provide Mode and this parameter is enabled, frames that contain an Ether
Type that matches the port's PortEType ("Ether type" parameter) that have a non-zero VID will be
discarded.
• Discard untagged
When this parameter is enabled all non-MGMT frames that are processed as untagged are discarded
as they enter this switch port. Priority only tagged frames (with a VID of 0x000) are considered un-
tagged. This feature works if 802.1q is enabled on the port or not.
If the port is configured in Provide Mode and this parameter is enabled, frames that don't contain an
Ether Type that matches the port's PortEType ("Ether type" parameter) that have a non-zero VID
will be discarded.
• VTU priority override

When this parameter is set to anything other than "none", VTU priority overrides can occur on this
port. A VTU priority override occurs when the determined VID of a frame results in a VID whose "Use

Configuration
VID priority" parameter is enabled. When this occurs three (other than "none") forms of priority
overrides are possible:
○ none Normal frame priority processing occurs.
○ frame The "VID priority" value assigned to the frame's VID (in the VLAN database) is used to
overwrite the frame's previously determined FPri (frame priority). If the frame egresses tagged the
priority in the frame will be this new "VID priority" value - the frame is permanently modified.
○ queue The "VID priority" value assigned to the frame's VID (in the VLAN database) is used to
overwrite the frame's previously determined QPri (queue priority). The QPri is used internally to
map the frame to one of the egress queues inside the switch. QPri override will not affect the
contents of the frame in any way.
○ frame + queue Both the above overrides take place on the frame.
The VTU Priority override has higher priority than the port's Default Priority and the frame's IEEE
and/or IP priorities. The priority determined by the frames' VID can however be overridden by the
frames' SA and/or DA Priority Overrides.
• VTU page
When "VTU page mode" is set to value "port" this setting is used to determine which VTU page is
used for frames ingressing this port. This supports different VTU lookup results for the same VID
based on the value of this bit and allows Core ports to use one set of VTU values while Edge ports
use a different set.
• Force default VID

Force to use Default VID. When 802.1q is enabled on this port and this parameter is enabled, all
Ingress frame's VID are ignored and the "Default VID" is assigned and replaced into the frame (if
the frame egresses tagged). When this parameter is disabled all IEEE802.3ac Tagged frames with
a non-zero VID use the frame's VID unmodified.
When 802.1q is disabled on this port, this bit has no effect.
• VID 0 enable
When this bit is cleared to a zero normal network switching occurs (i.e., a frame received with a VID
of 0x000 will get an initial VID assignment from the Port’s Default VID from Port offset 0x07). When
this bit is set to a one frames received with a VID of 0x000 will NOT get an initial VID assignment
from the port’s Default VID – it will get an initial VID assignment value of 0x000 instead.
• Default VID
Default VLAN Identifier. When 802.1q is enabled on this port the Default VID parameter is used as
the IEEE Tagged VID added to untagged or priority tagged frames during egress that ingressed from
this port. It is also used as a tagged frame's VID if the frame's VID was 0x000 (i.e., it is a priority
tagged frame) or if the port's "Force Default VID" is enabled.
When 802.1q is disabled on this port, the Default VID field is assigned to all frames entering the port
(whether tagged or untagged). This assignment is used internal to the switch.
• FID
Port's Default Filtering Information Database (FID). This parameter can be used with non-overlapping
VLANs to keep each VLAN's MAC address mapping database separate from the other VLANs. This
allows the same MAC address to appear multiple times in the address database (at most one-time
per VLAN) with a different port mapping per entry. This field is overridden by the FID returned from
a VTU hit and it should be zero if not used. It must be a unique number for each independent, non-
overlapping, address database if used.
• VLAN tunnel
When this parameter is disabled, the port based VLANs defined in the VLAN Table, 802.1q VLANs
defined in the VTU and Trunk Masking are enforced for ALL frames.

Configuration
When this parameter is enabled, the port based VLAN Table masking, 802.1q VLAN membership
masking and the Trunk Masking are bypassed for any frame entering this port with a DA that is cur-
rently 'static' in the ATU. This applies to unicast as well as multicast frames.
While enabled, the Unicast frames with the management CPU DA can go from the Eth1 and Eth2
ports in to the CPU port. The static record with the CPU DA in the ATU table has to be configured
(it is pre-configured by default).
• Member (VLAN Table)

The In Chip Port based VLAN Table contains parameters used to restrict the output ports to which
an input port can send frames.
These parameters (VLAN Table bits) are used for all frames, except for MGMT frames, even if 802.1q
is enabled on this port. These parameters restrict where a port can send frames to (unless a VLAN-
Tunnel frame is being received). If ForceMap (Learning) is enabled, these parameters indicate which
port or ports all frames that ingress this port are sent to overriding the mapping from the address
database.
The default setting prevents sending frames from Eth1 to Eth2 and vice versa. This is very important
for separating different networks (e.g. different customers) connected to separate user ports.
• Link authorization guard (in Note)

The parameter Link authorization guard (from menu Link Settings / Service access /Services) affects
the user data flow through the Air channel. When the Link authorization guard is enabled, the user
Ethernet ports to Air port connection control is disabled. Parameter status of user Ethernet to Air port
connection changes dynamically according to Link authorization status.

Configuration
STU setup
The STU (Spanning Tree Unit) is related to VLAN functionality (pages STU, VTU and VLAN has to
correspond to each other). The per VLAN STU in the device supports user commands to access and
modify the contents of the Port State database.
Fig. 5.31: Menu Switch settings / Advanced / STU
• Add entry
Add a new STU database entry.
• Edit/Copy
Opens the configuration dialog of the selected STU database record.
Note
Should the Primary key value be modified, the "other" record - identified by the entered
Primary key - is added (if it doesn't exist yet) or modified (if it exists already).
• Delete
Deletes the selected STU database record.

Configuration
Fig. 5.32: Menu Switch settings / Advanced / STU / Add Entry
Enter values to each field (see their meanings below):
• Primary key
• SID
VTU 802.1s (MSTP) Port State Information Database number. This parameter indicates the SID
number that is associated with the 802.1s "Port state" parameter. It is essential to define the SID to
be able to create records in the VTU (VLAN Table).
• Label
A custom string label for a STU entry.
• Port state
This parameter is used to support 802.1s per VLAN spanning tree. Port states are valid for frames
with a VID that is associated to this SID:
○ disabled ... Use non-VLAN Port States (i.e., the port's default Port State) for this port.
○ blocking/listening
○ learning
○ forwarding
This "Port state" takes precedence over the port's Port State bits unless the port's Port State (driven
by STP) is Disabled (which prevents all frames from flowing).

Configuration
VTU setup
The VTU (VLAN Table Unit) is related to VLAN functionality (pages STU, VTU and VLAN has to cor-
respond to each other). Its records form the VLAN Table.
Fig. 5.33: Menu Switch settings / Advanced / VTU
• Add entry
Adds a new VTU database entry.
• Edit/Copy
Opens the configuration dialog of selected VTU database record.
Note
• Delete
Deletes the selected VTU database record.
• Flush all
Deletes the whole VTU database.

Configuration
Fig. 5.34: Menu Switch settings / Advanced / VTU / Add Entry
Enter values to each field (analogically to STU pages):
• Primary key
• Page
To be implemented yet.
• VID (VLAN ID)

This parameter indicates the VID number that is associated with the Member tag, VTU Priority, VTU
policy and the FID (Forwarding Information Database number).
• Label
• FID
Forwarding Information Database number. If separate address databases are used, this parameter
indicates the address database number to use for all frames assigned with this VID. All MAC DA
look-ups and SA learning will refer to the address database number defined by the FID associated
with the frame's VID. Multiple VID's can use the same FID. If separate address databases are not
used, the FID must be zero. The ATU database records are joined with the VTU database records
via this number.
• SID
802.1s Information Database Number. If 802.1s per VLAN spanning tree is being used, this parameter
indicates the spanning tree instance number to use for all frames assigned with this VID. Multiple
VID's can use the same SID. The STU database records are joined with the VTU database records
via this number.
• VID frame priority

Configuration
VID Frame Priority Use. This parameter is used to indicate that frames assigned with this VID can
have their priority overridden with the "VID priority" value (see below) if the port's "VTU priority
override" parameters is enabled to do so. See "VTU priority override" for more details.
VID Priority override value when enabled by the "Use VID priority" parameter (see above). Used for
priority override on ingressing frames. Enabling a priority on a VID will override the frame's priority
only if the port's "VTU priority override" parameter is enabled to do so.
• VID queue priority

VID Queue Priority Use. This parameter is used to indicate that frames assigned with this VID can
have their priority overridden with the "VID priority" value (see below) if the port's "VTU priority
override" parameters is enabled to do so. See "VTU priority override" for more details.
VID Priority override value when enabled by the "Use VID priority" parameter (see above). Used for
priority override on ingressing frames. Enabling a priority on a VID will override the frame's priority
only if the port's "VTU priority override" parameter is enabled to do so.
• VID policy
This parameter is used to indicate that frames assigned with this VID can have Layer 2 Policy actions
applied to it if the port's "Policy VTU" (menu Advanced/Monitoring, Policy/Policy) is enabled to do
so.
• Don't learn
To be implemented yet.
• Filter UC/BC/MC
To be implemented yet
• Member tagThis parameter is used to indicate which ports are members of the VLAN (i.e., with the
given VID) and if these VLANs frames should be tagged or untagged, or unmodified when exiting
the port as follows:
○ egress unmodified ... Port is a member of this VLAN and frames are to egress unmodified.
○ egress untagged ... Port is a member of this VLAN and frames are to egress Untagged.
○ egress tagged ... Port is a member of this VLAN and frames are to egress Tagged.
○ not member ... Port is not a member of this VLAN. The result is that frames assigned with this VID
cannot egress this port.
This parameter takes effect only if the "802.1q mode" parameter (see menu Advanced/VLAN) is set
to "secure" mode.

Configuration
ATU setup
The Address Translation Unit (ATU) in the device supports user commands to access the contents of
the MAC address database.
There is one static record which cannot be deleted. This is the management CPU record. The unicast
frames directed to management are allowed to access the CPU port. The "VLAN tunnel" parameter is
also used to enable the AP frames to access the CPU port.
Fig. 5.35: Menu Switch settings / Advanced / ATU
• Add entry
Adds a new ATU database entry.
• Edit/Copy
Opens the configuration dialog of the selected ATU database record.
Note
• Delete
Deletes the selected ATU database record.
• Flush all and use default

Deletes the whole ATU database and create default record(s).
• Flush non-static
Delete all but static ATU database records.

Configuration
Fig. 5.36: Menu Switch settings / Advanced / ATU / Add Entry
Enter values to each field (analogically to STU or VTU pages):
• Primary key
• FID
Forwarding Information Database number. If multiple address databases are not being used, this
parameter must remain zero. If multiple address databases are being used, this parameter is used
to set the desired address database number that is to be associated with this ATU Entry's MAC Ad-
dress. When frames ingress the switch, the VID assigned to the frame is used to access the VTU.
The VTU returns the FID associated with that VID for MAC address lookups in to the ATU.
• MAC
MAC address associated with this ATU entry in the database number defined by the FID.
• Label
• Entry state
The Entry state parameter is used to determine the entry's age or its type as follows:
○ static ... Use for ordinary static entry.
○ static policy ... Use for "Policy DA" and/or "Policy SA" (menu Advanced/Monitoring/Policy).
○ static non rate limiting ... Use for "SA non rate limit" and/or "DA non rate limit" (menu Interface/PIRL).
○ static management ... This value is used for the mapping of the DA even if the "DA mapping"
parameter is disabled (menu Advanced/ATU settings).
○ dynamic ... ordinary dynamic entry.
• Use MAC priority

Use this parameter to enable the "MAC priority" (see "MAC priority" description).
• MAC frame priority

Configuration
The MAC's Frame Priority override value when enabled by the "Use MAC priority" parameter. Used
for priority override on ingressing frames. Enabling a priority on a MGMT MAC address will override
all priorities for these MGMT frames. Enabling a priority on a static, non-MGMT MAC address, will
only override the frame's priority if the port's "DA priority override" or "SA priority override" parameters
are enabled.
• MAC queue priority

The MAC's Queue Priority override value when enabled by the "Use MAC priority" parameter. Used
for priority override on ingressing frames. Enabling a priority on a MGMT MAC address will override
all priorities for these MGMT frames. Enabling a priority on a static, non-MGMT MAC address, will
only override the frame's priority if the port's "DA priority override" or "SA priority override" parameters
are enabled.
• Trunk member
When this parameter is enabled, the MAC address is a member of a trunk - according to the "Trunk
Id" parameter. When this parameter is disabled, the MAC address is associated with port(s) - according
to the "Port association" parameter.
• Trunk ID
The Trunk ID associated with this MAC address.
The port or ports that this DA MAC address is associated with is determined by the "Port association"
parameter below.
Use this parameter to ensure the proper unit management CPU is accessed when two units are
connected in trunk.
• Port association
Mask of ports associated with this MAC address.
RSTP setup
This page and related RSTP root bridge functionality is available only for FW 1.0.19.0 and earlier.
Page allows to configure RSTP (Rapid Spanning Tree Protocol by IEEE 802.1w) root bridge. RSTP
provides significantly faster recovery in response to network changes or failures, introducing new
convergence behaviors and bridge port roles to do this. RSTP root bridge configuration on RAy make
sense only for RAy configurations with both Ethernet ports used and only for network segments without
its own Ethernet bridge or router. Because it is very rarely used (if ever) and its wrong usage may cause
a lot of network troubles, the functionality was removed in FW release 1.0.20.0. For more information
about RSTP, STP, related Path cost, etc. see
https://en.wikipedia.org/wiki/Spanning_Tree_Protocol.

Configuration
Fig. 5.37: Menu Switch settings / Advanced / RSTP
• RSTP enable
Enables RSTP protocol. When RSTP is enabled, the bridge is created and RSTP service is initiated.
Should the unit be connected via two Ethernet cables (using Eth1 and Eth2 ports), the active parti-
cipation of the RSTP protocol may be necessary. If the parameter is not enabled, the unit transfers
the BPDU frames transparently.
Note
To enable proper RSTP functionality, these switch parameters has to be set:

○ Switch settings / Interface / Port advanced / Frame mode / p5 CPU: "ether type DSA"
○ Switch settings / Interface / Port advanced / Ether type / p5 CPU: "0xDADA"
○ Switch settings / Advanced / ATU settings / Reserved multicast to CPU: "Enable"
• Bridge priority
The priority value is a number between 0 and 61440 in incremental steps of 4096, with a default
value of 32768. Lower priority values are 'better'. The bridge with the lowest priority value will be
elected 'root bridge'.
• Hello time [s]

The hello time is the time between each Bridge Protocol Data Unit (BPDU) that is sent on a port.
Hello time is equal to 2 seconds by default.
• Max age [s]

The max age timer controls the maximum length of time that passes before a bridge port saves its
configuration BPDU information. This time is set to 20 sec by default.
• Forward delay [s]

The forward delay is the time that is spent in the listening and learning state. This time is equal to
15 sec by default.
• Algorithm

Configuration
This parameter sets the bridge's spanning tree algorithm to operate in normal (RSTP) or force it to
operate in slow (STP) mode. In normal mode, RSTP reverts back to STP on ports where it sees
other hosts operating in STP mode.
• Port name
Identification of the internal switch port, see Section 5.3, “Status”.
• Port priority
The ports' priority value is a number between 0 and 240 in increments of 16, with a default value of
128.
• Path cost
The Path cost indicates "suitability of the link for the data transmission" and it is used in networks
with redundant connections to choose the best route for packets.
The Path cost can be set automatically or manually. Entering the value of zero sets this parameter
automatically. The automatic setup is based on link speed. It is calculated as 20 Tbits/sec divided
by a link capacity.
For manual settings, lower value increase probability the link is chosen as a primary one for the data
transmission.
• Edge
Selecting the checkbox sets the port as an "edge" port. If a port is an edge port it is assumed to be
a leaf link in the graph, not connected to any other bridges. Receiving any STP BPDU's on a port
configured as an edge port temporarily overrides edge port behavior for the port.
• MAC address
The ports' default MAC addresses are the same as the MAC address of the unit. Value can be
overwritten by a user.

Configuration
5.6. Tools
5.6.1. Maintenance
Backup, Default settings, Diagnostic package, MIB
Fig. 5.38: Menu Tools / Maintenance / Backup
• Settings (Local & Peer)

Saving and restoring whole link (both units) configuration. User accounts are not affected by those
functions.
Local Peer
Link
Switch
Users
○ Backup to external file

Configuration is saved to backup file which is downloaded to management PC. The backup file
name contains the date, time and RAy serial number as follows:
yyyyMMddhhmm_SN_cnf_backup.tgz.
It can be either a full configuration or a difference to the default configuration.
○ Upload file

Configuration
Upload configuration from a backup file into buffer. The current unit configuration is not affected.
The uploaded configuration can be displayed using "Show backup" button on particular configuration
screens. The configuration of the entire unit can be restored (from this buffer) using "Restore"
button below.
○ Restore from file
After the configuration backup file has been loaded into the unit buffer (using Upload button above),
the whole unit configuration can be restored using Restore button.
• Settings - Internal backup (Local)

It is possible to make a temporary backup of the unit configuration. The backup is stored directly in
the unit FLASH memory.
Note
The internal backup is deleted if factory settings or firmware upgrade are performed.
L P
L
S
U
○ Internal backup
Make a temporary backup of the unit configuration locally in the unit FLASH memory.
○ Internal restore
Restore (from the unit FLASH memory) the temporary backup of the unit configuration.
○ Internal restore - HW button
After the configuration backup file has been loaded into the unit buffer (using Upload button above),
the whole unit configuration can be restored using Restore button.
The local temporary backup of the unit configuration can be restored using the hardware button.
The HW button is located next to the USB connector within the slot marked "S".
The rollback and reboot functions are suppressed while restoring from internal backup. All changes
are applied immediately. Should the time zone be changed, the unit has to be restarted for changes
to take effect.
Press the HW button for the required time interval of 5 seconds. The button being pressed is
confirmed by the Status LED flashing green. After the 5 seconds guard time, the unit restores to
customer settings.
• Users (Local)
Saving and restoring user accounts.
Note
L P
L
S
U
○ Backup to external file

Backup local unit user accounts to an external file. The file is downloaded to management PC.

Configuration
Note
○ Upload file & restore

Restoring user accounts from an external backup file.
• Default settings
Applying default values to configuration parameters.
○ Restore link settings (Local & Peer)
L P
L
S
U
Whole set of parameters from the Link settings menu tree is affected.
○ Restore switch settings (Local)
L P
L
S
U
Whole set of parameters from the Switch settings menu tree is affected.
○ Restore default settings (Local) - HW button
L P
L
S
U
It is possible to bring the unit to Default settings by holding the hardware button depressed during
unit's boot. The HW button is located next to the USB connector within the slot marked "S".
Disconnect the power supply from the unit. Keep the HW button depressed while reconnecting
the power. The LED marked SYS starts to flash red after a few seconds. Keep the HW button
pressed another 5 seconds until the red status LED stops flashing. The unit's boot up sequence
continues and Default settings are applied.
Should the HW button be released when the status LED is in the red flashing phase (but before
the 5 s guard time), the unit stays in Service mode. Please, leave this mode by rebooting the unit.
• (Factory settings (Local)

Applying Factory settings to Local unit. The unit reboots itself after applying all changes.
L P
L
S
U
○ Restore factory settings

Applying Factory settings to Local unit. The unit reboots itself after applying all changes.

Configuration
Warning
Using the factory settings function will revert the unit to its original state. All configuration
items, user accounts, measured values and system messages (logs) will be irreversibly
deleted. This task takes a few minutes to complete. Do not interrupt the power supply
during the operation.
• Diagnostic package (Local & Peer)

To facilitate communication with the technical support you can create an archive file with detailed
information about the unit. If connection with Peer unit is active the diagnostic information from both
units are saved.
○ Create & download file
Saving a file with information about the unit (Local and Peer).
Note
This task takes a few minutes to complete.
• Management Information Base

To facilitate communication with the technical support you can create an archive file with detailed
information about the unit. If connection with Peer unit is active the diagnostic information from both
units are saved.
○ SNMP MIB
Saving a file with SNMP MIB (Management Information Base) table. The downloaded file is
1
identical to the SNMP MIB table file downloaded from web (section Downloads ) for relevant FW
version.
1
https://www.racom.eu/download/hw/ray/free/eng/03b_fw/ray3-mib.mib

Configuration
Feature keys
Fig. 5.39: Menu Tools / Maintenance / Feature keys
The sub-set of RAy parameters is affected by use of Feature keys.
The feature keys limiting data transfer speed [Mbps] and/or few other parameters and functionality of
the RAy unit are available. Speed of the transferred data is determined by a combination of the radio
channel bandwidth (parameter Bandwidth [MHz]) and modulation order (parameter TX modulation).
The Feature key limiting the data transfer speed enables only certain combinations of the channel
bandwidth and modulation order to get the data transfer speed according to the Feature key. The data
transfer speed is typically slightly higher than declared.
When installed, the Feature key is activated after the unit restart. The unit can be restarted using the
Tools – Maintenance – Restart. Choose the Restart mode – warm.
• Local
Shows current status of installed Feature keys on Local unit.
• Peer
Shows current status of installed Feature keys on Peer unit.
• Feature
Name of the function controlled by the Feature key.
Available feature keys:
○ speed
○ Tx power
○ Sync Eth
○ AES encryption etc.
• Limit / Enable
The numeric value set by the key.
• Remove

Configuration
The specific Feature key can be deleted using the Delete button. The parameters controlled by this
Feature key are reset to their default values after the unit restart. Only Local feature keys could be
deleted. To be able to manipulate the Feature keys, it is necessary to access directly the management
system of the relevant unit - use the IP address of the relevant unit.
Note
Before deleting the feature key it is recommended to configure the link such a way that it
does not require this feature key.
• Upload local feature keys

Feature keys are installed into the unit from binary files. Installed Feature keys are activated after
the unit restart.
• Upload (the button 'Open file upload')

Dialog for the Feature key binary file selection is open.
Note
Use the file as it is (do not unpack).
Firmware
Fig. 5.40: Menu Tools / Maintenance / Firmware
If a new firmware version is released for the given microwave link type, you can upload it to your RAy
units.
Info
• Radio SW version
Information about the Software Defined Radio (SDR) version on the Local and Peer units.

Configuration
• Firmware version
Information about the current firmware package version on the Local and Peer units.
Firmware version
• Firmware upload
Open file upload - opens a dialog for uploading firmware package to the unit buffer. Only after firmware
has been prepared in the buffer, can you perform the actual upgrade.
Note
Use the file as it is (do not unpack).
• File name
Name of the uploaded firmware file.
• File size [B]

Size of the uploaded firmware file (in bytes).
• Version in buffer
Information about firmware version prepared in the buffer for installation into the unit (Local, Peer).
This firmware must first be prepared in the Firmware upload section (see above).
• Clean buffer
You can use the Clean buffer button to delete prepared firmware package in the buffer.
• Force upgrade
Force mode blocks all safety and compatibility checks and may result in breaking your unit.
Important
You should not use force mode until instructed to do so by the technical support.
• Upgrade
Use the Upgrade button to perform the firmware installation.
Warning
Installing the firmware takes about 45 seconds (including reboot). During this time, transmis-
sion of user data is interrupted. Do not interrupt the power supply during firmware installation!

Configuration
Radio adaptation
Fig. 5.41: Menu Tools / Maintenance / Radio adaptation
Band index
• Band index
Band index displays radio channel assignment of local unit transmitter (Tx) for L (Lower) or U (Upper)
part of the frequency band.
○ Change button
Change button changes the band index (L -> U and U-> L). If units are linked together both Local
and Peer units are changed in the same time.
Note
Change button applies only for 17 GHz and 24 GHz links, where hardware of each RAy
unit is universal for the entire frequency band.
Note
After restoring factory settings Band index is set to its pre-defined state L or U as typed on
Product Label.
Warning
When the radio type is changed, the "Link settings" menu parameters of each unit are reset
to default values except login / password details.
Frequency tables
The microwave link contains one or more frequency tables (called rcinfo). These tables contain the
following information:
List of available bandwidths and modulations.
Assignment of frequencies to the channels and the names of these channels. These channels are used
to configure radio parameters of the link (see screen Link settings / Radio).
Default values of radio parameters.

Configuration
A set of radio parameters, needed for the ATPC operation.
• Active
Name of the currently used frequency table in format <name:version>.
• New
Select a new frequency table. Available tables are displayed in format <name:version>. Use the
Change button to change the table.
Warning
Using the wrong frequency table can lead to violation of the corresponding telecommunica-
tions regulations.
Compatibility
• Unit '24S' compatibility (formerly 'Unit S mode')

This parameter is available only for newly deployed 24 GHz units without the 'S' label in Product
code (i.e. '24S') - as visible on Production label and in Ordering codes.
When "active", the unit behaves like the unit '24S' (it can establish a link only with another '24S' unit).
For a link between the units without the 'S' label, this compatibility needs to be disabled ("off"). The
unit reboots after changing this parameter.
Note
Used only if a combination of different hardware variants of units have to be used to set up
the link together. For more info see the topic 'Setting up a link between RAy3-24S and other
hardware variant of RAy3-24' in chapter Troubleshooting.
Wrong setting of compatibility causes the link is not established (both units remain in status
'Connecting').

Configuration
Restart
Fig. 5.42: Menu Tools / Maintenance / Restart
• Target
Chose the unit(s) to be restarted: Local or Peer or both.
• Restart mode
Chose the type of the restart:
○ Warm
Reboot only management system and web interface.
○ Cold
Restart the whole unit as if power was removed.
• System restart
Pushing the "Restart" button performs the selected restart.

Configuration
5.6.2. Live data
Bar indicators
Fig. 5.43: Menu Tools / Live Data / Bar indicators
Graphical indication of RSS and MSE.
• Refresh
One-time update of displayed values.
• Start, Stop
Start button starts automatic update of displayed values with a period of 1 second. Stop button stops
refreshing of both graphs.
• Antenna alignment
Link "go to antenna alignment screen" activates Antenna Alignment Tool (black page ).
Antenna Alignment Tool
The Antenna Alignment Tool supports interactive antenna alignment. RSS and MSE are displayed for
both local and peer unit. A selected value can be indicated in large font and acoustically. Values are
refreshed 10× per second.
When performing antenna alignment, both ATPC and ACM functions should be disabled; their automatic
behavior interferes with the alignment process which is based on finding the maximum signal strength.

Configuration
The tool is accessed via e.g. http://192.168.169.169/tk for standard Ethernet ports, and via ht-
tp://172.17.17.17/tk for connections using USB/WiFi or USB/Eth. The Antenna Alignment Tool does
not require user authentication.
Fig. 5.44: Antenna Alignment Tool
• Red strip (top of the page)

○+
Increases the number of displayed parameters
○x
Decreases the number of displayed parameters
○ text
Local Station name (e.g. RAy3-17 -L)
• Link
○ 3.5 MHz Ok
Channel width
Link connected (green icon).
The Peer values (see below) are visible when the connection between Local and Peer unit has
been established.
• Local, Peer
○ QPSK-2048QAM
Current modulation of the Tx signal.
○ ACM, ATPC
Status of ACM + ATPC (red color warns ACM or ATPC is enabled).
• Go to unit management
Link to the full configuration interface of the microwave unit; user authentication is required.
• -48.9
Actual RSS [dBm] or MSE value. The selected value is chosen by clicking/tapping on the respective
value below the main display.
• Exclamation icon !
An exclamation icon is displayed when either Local or Peer unit has ACM or ATPC enabled. ACM
and ATPC mode should be disabled; they can affect signal strength.
• Icon of speaker
Acoustic indication for local RSS value ON/OFF.

Configuration
The TONE or BEEP signal is supplemented with voice output every 10 seconds, notifying signal
strength.
• TONE / BEEP
Select the sound generated.
The better the signal, the higher the frequency.
The acoustic indication is linked to the value on the main display.
If a WiFi connection is used to access Antenna Alignment, the 'noise' audio signal is used to notify
low quality or low stability of the WiFi signal.
• COARSE / FINE
Choose the scale of acoustic indication.
○ COARSE
for approximate alignment. Range of tones (or frequency of beeps) is equal to -100 to -30 dBm.
○ FINE
for a more precise alignment. Range of tones (or frequency of beeps) is equal to ±10 dBm from
the value sampled at the moment when the FINE button was pressed).
• RSS, MSE
Values RSS and MSE for local and peer unit (4 values in total):
○ First column
Best values recorded
○ Second column
Current values.
The value to be displayed on the main display is selected by a tapping/clicking on the respective
value.
• Reset peaks
Best values history is cleared.

Configuration
Frequency spectrum analyzer
Fig. 5.45: Menu Tools / Live Data / Frequency spectrum analyzer
A very useful tool for identifying in-band interference and locating a free channel. It is not a full-blown
spectrum analyzer as it scans the spectrum with 2 MHz channel resolution. The accuracy of measured
results is given by the accuracy of measuring RSS.
• Enable
Opening analyzer functions.
• Start
Interrupts communication on the link and starts scanning frequencies in the band.
• Spectrum measure time

Selection of measurement length in range:
• Mute peer TX
The deactivation of Peer station transmission during measurement.
single sweep … up to 15 min
Note
Single sweep takes about 2 seconds for the whole band scan. The link is automatically re-es-
tablished after it is finished.
Warning
Running spectrum measurement causes interruption of user data flow between stations!

Configuration
Interruption of the scan before selected measure time can be achieved anytime by visiting any of the
Link menu settings and select Refresh. This restores the configuration connection (message Peer:
n/a).

Configuration
5.6.3. History
The unit continuously stores information about the values of important variables. Stored values can be
viewed using three methods - Thumbnails, Viewer and Data
Thumbnails
Preview all values for the last 24 hours. Click on a thumbnail to open the viewer with a chart.
Fig. 5.46: Menu Tools / History / Thumbnails
• Temperature
Instantaneous value of temperature inside the unit. Measured on the modem board.
• Voltage
Instantaneous value of unit supply voltage.
• RSS
Received signal strength.
• Signal quality

Configuration
Signal quality of the received signal. It is negative value of Mean Square Error (MSE, the inverse to
often used SNR - Signal to Noise Ratio).
• BER
Instantaneous bit error rate on link.
• Net bitrate
Instantaneous transmission capacity.
• Eth1, Eth2 in throughput

Instantaneous speed (20s average) of incoming user data on the user Ethernet port.
• Eth1, Eth2 out throughput

Instantaneous speed (20s average) of outgoing user data on the user Ethernet port.
• TX power
Instantaneous value of transmission power.
Viewer
Detailed graphical view of one or two selected values for the given interval. You can choose to view
data from Local or Peer or both.
Fig. 5.47: Menu Tools / History / Viewer
The values are saved in the following resolutions and history lengths:
Interval 1 hour - 3 hours, Resolution 1 minute, length of history 7 days
Interval 6 hours - 4 days, Resolution 15 minutes, length of history 30 days

Configuration
Interval 1 week - 6 months, Resolution 1 day, length of history about 180 days
• Interval
Selecting width of interval to be displayed. Data is displayed in a suitable grid based on the interval
width (see above).
More options:
○ Previous
Move by one width of selected interval towards older values.
○ Next
Move by one width of selected interval towards newer values.
○ Last
Move to the newest values.
• Primary Y axis
Selecting one of the observed values:
Temperature, Voltage, RSS, Signal quality, BER, Net bitrate, Ethernet in throughput, Ethernet out
throughput, TX power
• Secondary Y axis
Selecting a second value:
None
Temperature, Voltage, RSS, Signal quality, BER, Net bitrate, Ethernet in throughput, Ethernet out
throughput, TX power

Configuration
Data
Numerical view of all values
Fig. 5.48: Menu Tools / History / Data
• Quantities
Detailed graphical view of values for selected interval.
○ Plotted
Shows only the values that are selected for the graph.
○ Local, Peer, All

Shows all logged values. Filtering of values from local, remote or both.
• Interval, Previous, Next, Last

See explanation of those in Viewer section above.

Configuration
5.6.4. Logs
Shows internal unit logs. Individual tabs allow total or filtered view.
Fig. 5.49: Menu Tools / Logs
When you first open the screen, it is necessary to start browsing logs by pressing the Refresh button.
Maximum length of displayed logs is 250 entries. If you need to display longer history, use CLI interface
instead.
• Overall
Displays the last 3 records from all types of logs.
• Local alarms, Peer alarms

Alarms from Local or Peer unit.
• Local events, Peer events

Events from Local or Peer unit.
• Local system, Peer system

System events from Local or Peer unit.
• Filter
Listings of all logs can be filtered. Filtering string is entered in to the upper left corner window and
Filter button is pushed. For example, you want to know when the configuration of the unit was mod-
ified: On the Local events screen, enter Configuration and hit Enter.
Plain text or regular expressions can be used for filtering (JavaScript format).

Configuration
5.6.5. Programs
Ping
The Ping tool allows sending ICMP pings to a selected address
Fig. 5.50: Menu Tools / Programs / Ping
• Destination
Destination address in dotted decimal notation. The default address 127.0.0.1 is the localhost address
- i.e. the unit itself.
• Size [B]
Length of sent data 7 to 1500 bytes, 8 bytes of the header will be added.
• Count
Number of sent pings.
Start the test by clicking on Send. The period for sending pings is constant: 1000 ms. The result is
displayed in the text window.

Configuration
CLI
Web interface for executing non-interactive scripts and programs.
Fig. 5.51: Menu Tools / Programs / CLI
• Manage custom commands

Using "Open file upload"/"upload" the user can upload scripts to the unit. The uploaded file can be
either a single shell script with extension .sh (e.g. my_script.sh) or package with multiple scripts with
extension .tar.gz or .tgz created using tar.
"Delete all" removes all custom scripts from the unit.
Custom scripts are located in /home/shared/bin.
• Custom commands
A custom script can be selected here and initial comments/help is shown.
• CLI commands
A CLI command can be selected here. You can use cli_help for listing all CLI commands or <com-
mand> --help to obtain detailed help on a selected command.
• Command
Command line for writing commands with parameters. You can use any non-interactive program/script
according to your permissions. Command is executed by pushing the "Run" button.
• Format of custom scripts

Custom scripts must be a shell script with preamble #!/bin/sh and extension sh.
Blocks of lines beginning with the comment sign (#) after preamble are considered to be help and
are listed when the script is selected in the web interface.
Scripts should not be interactive as there is no possibility to send a response from the web interface.
All script options should be implemented as parameters.
Syntax should be valid for interpret shell ash from BusyBox v1.20.1.

Configuration
• Example of custom script
#!/bin/sh
#script checks if service with the same name or vid already exists
#if not creates a new entry in VTU with given VID
#
# input parameters:
# service_name - name of the new service
# VID - vid of the new service
#
# return values:
# 0 - ok
# 3 - bad parameter
# 5 - service already exists
# 6 - there already exists an entry with given VID
# 42 - other error
D42_NAME="$1"
D42_VID="$2"
D42N="service_data42"
error()
{
echo "$D42N: Error: $*" >&2
}
info()
{
echo "$D42N: $*" >&2
}
die()
{
error "$*"
exit 42 #error
}
# basic check if not empty

if [ -z "$D42_NAME" ]; then
error "Bad service name"
exit 3
fi
if [ -z "$D42_VID" ]; then
error "Bad service VID"
exit 3
fi
D42_FOUND=$(cli_nw_get --vtu all | grep "$D42_NAME")

if [ -n "$D42_FOUND" ]; then
error "Service(s) with name $D42_NAME found"
echo $D42_FOUND
exit 5

Configuration
fi
D42_VALID=$(cli_nw_get --vtu "$D42_VID" | sed -n 's/^valid=$.\+$$/\1/p')

if [ "pre_$D42_VALID" = "pre_true" ]; then
error "VID $D42_VID is used"
cli_nw_get --vtu "$D42_VID"
exit 6
fi
D42_VALID=$(cli_nw_get --stu 1 | sed -n 's/^valid=$.\+$$/\1/p')

if [ "pre_$D42_VALID" = "pre_false" ]; then
info "Creating STU entry with SID=1"
cli_nw_set --stu 1 'label="D42_auto", port_state=["disabled", "disabled", ►
"forwarding", "disabled", "disabled", "forwarding", "forwarding"]'
if [ $? -ne 0 ]; then
die "Failed to create STU entry"
fi
fi
info "Creating service \"$D42_NAME\" with VID=$D42_VID"

cli_nw_set --vtu "$D42_VID" label="$D42_NAME" 'fid=0, sid=1, pri_override=true, priority=5, ►
policy=false, member_tag=["unmodify", "unmodify", "tag", "unmodify", "not_member", ►
"not_member", "unmodify"]'
if [ $? -ne 0 ]; then
die "Failed to create service \"$D42_NAME\" with VID=$D42_VID"
fi

Configuration
5.7. Help
Fig. 5.52: Help menu

Configuration
Help from Help menu
The Help screen displays contents of the embedded help. The help text is displayed in the whole con-
figuration window. The text structure corresponds to individual configuration screens. Every item of
this Help opens the specific help menu.
CLI help visible Allows displaying of the CLI help with examples.
Third party Allows displaying references to the third party documentation (e.g. internal switch
documentation documentation).
Help from configuration menu
Clicking the name of the specific parameter in the configuration menu brings up the help belonging
to this parameter. The help text is displayed in the pop-up window:
Fig. 5.53: Parameter help
There is a Go to help link within the help text. It displays the whole configuration menu help:

Configuration
Fig. 5.54: Configuration menu help
There is a link on each help screen which points to the respective configuration screen.
Clicking the question mark icon in the upper right corner of the configuration screen brings a summary
help for the configuration screen in the pop-up window:
Fig. 5.55: Summary help
The Help window can be moved by dragging the Hints bar. Resize it by dragging the bottom corner.

Command Line Interface
6. Command Line Interface

The Command Line Interface (CLI) provides an alternative to HTTPS access. CLI allows you to work
in a text regime interface using a SSH (PuTTY) or telnet client.
6.1. Connection via CLI
6.1.1. Telnet
Use the telnet client to connect to the unit with service IP address 192.168.169.169. Type this in the
command prompt:
telnet 192.168.169.169
Then use the username and password from the menu Service access/Users for HTTPS access
(by default admin, admin). This works if Service access/Services/Telnet is checked in
HTTPS access.
6.1.2. PuTTY
Connection using putty client. Type this into the Host Name (or IP address) field:
[email protected]
Click Open. Then enter the password admin. This procedure (without key) is subject to selection
Service access/Services/SSH on in HTTPS access.
If you own the private key part, then you do not need a password. In PuTTY, continue by selecting
Connection/SSH/Auth and selecting path to file with key e.g. key.ppk. Use Session/Logging
to save the PuTTY configuration. To access the unit via CLI simply select the connection in PuTTY
and click Open.
6.1.3. SSH
Connection using client ssh in Linux.
ssh [email protected] -i key
If you know the password and it is enabled in Service access/Services/SSH onlykey in HTTPS
access, you can skip the key and use password in the next query.

6.2. Working with CLI

• Overview of CLI options
cli_help
Fig. 6.1: CLI menu
• Parameters of CLI commands are listed in the help. For example:
-h help listing
-t target unit
-t l local, default option
-t b both, both units, command item for remote unit has PEER_ prefix
-t p peer, opposite unit, when reading using the show command
• When inserting commands, using the tabulator can help
• An incorrect command is rejected (e.g. inserting forbidden frequency)
• A parameter that caused the loss of the connection is restored after 1 minute (Rollback)
• Reading parameters of local unit

cli_cnf_show
• Reading radio parameters of peer unit

cli_cnf_show -t p | grep RADIO
• Entering parameters (TX power of local unit)

cli_cnf_set RADIO_TX_PWR=-3
Items of command (RADIO_TX_PWR=) are taken from the list cli_cnf_show

• Entering more parameters in both units

cli_cnf_set -t b RADIO_TX_CHAN=17128000 PEER_RADIO_RX_CHAN=17128000
• Put parameters containing spaces in quotation marks:

cli_time_set -t b -T '2012-11-27 10:55:00'
Set time in both units
6.2.1. SSH keys
• Generation using ssh-keygen

[user@laptop ~]$ ssh-keygen -t dsa -f usr_ssh_key
Uses working directory to save private usr_ssh_key and public part of the key usr_ssh_key.pub
• Copying the key into the RAy unit

[user@laptop ~]$ scp usr_ssh_key.pub [email protected]:/tmp
The public part of the key is written to the folder /tmp
• Installation of key in RAy unit

CLI(admin):/rrusrhomes/admin$ cli_user_authkey -c a -k /tmp/usr_ssh_key.pub
• Testing access to RAy unit using SSH key

[user@laptop ~]$ ssh -i usr_ssh_key [email protected]
6.2.2. Scripts
• Script example with access using key
[user@laptop ~]$ ssh -i usr_ssh_key [email protected]

"source /etc/profile;cli_info_link;echo \$?;cli_cnf_show | grep TX_PWR;echo $?"
Warning: Permanently added '192.168.141.202' (DSA) to the list of known hosts.
cli_info_link: Link status: up
0
RADIO_TX_PWR=4
0
[user@laptop ~]$
• The script contains:
source /etc/profile; environment settings

cli_info_link; query for link status
echo \$?; reading return value
cli_cnf_show | grep TX_PWR; query for radio power
echo \$? reading return value
cli_info_link: Link status:up return value

0 OK command
RADIO_TX_PWR=4 power +4 dBm
0 OK command

6.3. Configuration with CLI
6.3.1. Configuration file
• Configuration backup
cli_cnf_backup_get
Saves the configuration of both units to file cnf_backup.tgz into the working directory.
• Configuration restore
cli_cnf_set -t b -b cnf_backup.tgz
Restores configuration of both units from file cnf_backup.tgz
• Default configuration list

cli_cnf_def_show
Warning, the command
cli_cnf_factory_set
is not a default setting - it uses factory settings, deleting all logs and saved data. It is very likely that
the connection to peer unit will be interrupted!
6.3.2. Firmware upgrade
• Current version of fw
cli_info_station
• Preparation of files
fw package, a file with cpio extension, for example xxxxxx.cpio copy using SSH or PuTTY into
folder /tmp in RAy3-17
Command
cli_fw_clear_buffer
Clears the RAy buffer
cli_fw_buffer_status
Checks buffer status
• Saving into buffers

cli_fw_load_package -f /tmp/xxxxxx.cpio
A new fw package is loaded into the buffer (20 sec)
cli_fw_upload2peer
The fw package is also loaded into the peer unit (20 sec)
• Upgrade
cli_fw_upgrade -t b
Firmware in both units will be replaced with new version from the buffer. After few seconds, this
message appears:
Firmware upgrade started. Estimated time to finish is 45 s.
Connection is terminated. After a minute, log in to RAy again
6.3.3. Remote unit authorization
The RAy unit in default configuration, establishes a connection with any remote unit and both units act
as a communication pair. Should the higher protection from the unauthorized communication take-over
be required, it is possible to use the so called Secured mode of remote unit authorization. This mode
is based on locking the two specific units into one communication pair. Units with Secured mode activated

refuse to make a connection with any other communication unit. The units are locked using the unique
authorization keys. The keys are exchanged between the units concerned. The authorization keys can
be backed up to an external medium to be able to make a service unit exchange, if necessary. Should
the Link authorization quard be disabled, the user data occurs even the remote unit is not authorized.
The Secured mode set up process consists of a few steps:
• Unique authorization keys generation:

cli_link_key_gen -t b
• Authorization keys exchange between the two communication units:

cli_link_key_swap
• Authorization keys activation:

cli_link_key_apply -t b
Parameter -t determines whether we configure the whole link (-t b) or only one unit (-t l).
• Secured mode activation. Both sides of the link must have identically secured mode set On or Off:
cli_cnf_set -t b SVC_SECURE_PEER_MODE=on PEER_SVC_SECURE_PEER_MODE=on
• Secured mode de-activation:

cli_cnf_set -t b SVC_SECURE_PEER_MODE=off PEER_SVC_SECURE_PEER_MODE=off
• Backup of the keys to an external medium. The backup has to be performed to be able to make
service exchange of the corrupted unit, if necessary. The new exchanged unit is not able to make
an active connection with the other unit if it is not loaded with the proper authorization key.
cli_link_key_save -s s -f <file>
The key is backed up to a selected file in the internal unit file system. It can be transferred to an ex-
ternal medium using for example the scp client.
• Authorization key restoration from the external medium.

The key has to be transferred to the unit internal file system first. The scp client can be used. The
CLI commands can be applied subsequently:
cli_link_key_load -t b -f <file>
cli_link_key_apply -t b
6.3.4. Radio loopback
"Radio loopback" function (accessible via CLI only) provides indicative measurement of XPD (cross
polar discrimination). XPD is the ratio between desired signals on preferred polarization and signals
on opposite polarization.
• Command
cli_rloop
The Radio loopback command takes 10 seconds. The result is suppression [dB] of the unwanted signal
(transmitter to receiver penetration). Radio loopback can only be used with units operating in 17 GHz
or 24 GHz band.
Warning
User traffic is interrupted during command execution!

RAy Tools app for Mobile devices
7. RAy Tools app for Mobile devices

RAy Tools is a stand-alone application designed to perform all steps of
establishing a new link and operate it. It is optimised for use on mobile
devices with smaller displays and especially in challenging conditions.
RAy Tools supports the following functions:

○ Link Calculation – to calculate or verify the link budget
○ Antenna Alignment – indicates current RSS and MSE values, optionally
with acoustic indication, for convenient antenna alignment
○ Link Management – standard web-based unit management
Antenna Alignment and Link Management functions require a WiFi con-

nection to the RAy unit. It has to be established by the user before those
2 functions can be used.
RAy WiFi network name is "RAy Code + RAy Serial Number" (for example
"RAy3-24-1234567890").
Note
WiFi on the RAy unit is active only if RAy WiFi module is present
and its functionality is allowed in RAy management (permanently
or only during air link loss - for WiFi setup see Section 1.4.2,
“Service WiFi - optional (using USB „S“)”).
Every RAy3 shipped from the factory is equipped by a WiFi

module and the WiFi is allowed with no password (one should
be set immediately by the user).

7.1. Menu options
7.1.1. Calculation
Can be used in conjunction with all

RACOM microwave products and
compatible antennas. Available para-
meters to input that affect link budget
are:
• Modulation
• Throughput
• Tx Power
• Link distance
• Antenna specifications
RAy Tools calculation outputs are:

• Free Space Loss (FSL)
• 1st Fresnel Zone radius
• RSS
• Sensitivity
• Fade margin (shown to be accept-
able/marginal/inadequate)
iOS version Android version

The calculation assumes a clear line of sight and makes no allow-
ance for precipitation. A more accurate calculation can be performed
using the tool available on RACOM web pages (see
https://www.racom.eu/eng/products/microwave-link.html#calculation).
Precise link calculation should be performed using dedicated tools
(e.g. Pathloss).
7.1.2. Alignment
This function behaves like a digital voltmeter with values in dBm (instead of Volts). When activated,
the biggest number on the display (the main value) is RSS dBm value (with 0,1 dBm precision), refreshed
10x per second.
Smaller 4 lines in lower part of the display show 4 key metrics (local RSS and MSE and once the link
is established also remote RSS and remote MSE) and their best values (in right column). Any of those
can be chosen to become the main one (the biggest number on the display), just by taping on it by a
finger.
Additionally the sound can be switched on. Then tones or pulses related to the main value are produced,
with coarse or fine sensitivity (coarse at the beginning, fine for fine tuning). Additionally every 5 seconds
the current value is told in English, so the absolute value of main parameter could be heard even without
looking to the display. The sound can be used with a big advantage in situations, when both hands are
needed and the mobile has to be in the pocket (in such a case Bluetooth ears are the best choice).

Antenna Alignment Tool is accessed using this

menu. See Section 5.6.2 Live data for detailed
description.
This function works only if WiFi connection with
RAy unit is established.
7.1.3. Configuration
Links to web management of RAy unit as de-

scribed in Chapter 5, Configuration. User au-
thentication is required.
This function works only if WiFi connection with
RAy unit is established.
7.1.4. About
This item shows the application version and its Release notes.
Note
If gloves are used it is strongly recommended to activate smartphone option for “work in gloves”,
which increase the sensitivity of touch screen display (quite common option for modern
smartphones).
7.2. Application availability

RAy Tools application version 2.xx requires RAy3 unit with firmware version 1.0.0.0 or later. The same
1
application and same version of RAyTools works also with all RAy2 units (with WiFi module and
firmware version 2.1.28.0 or later).
RAy Tools version 2.xx or later is available for mobile operating systems Android (Google compatible
devices) and iOS (Apple devices). All display sizes are supported on both operating systems. Android
2
version can be downloaded from Google Play (https://play.google.com/store ), iOS version is available
3
for download on AppStore (https://www.apple.com/ios/app-store ) or their local versions.
Note
RAy Tools application contains an automatic crash report feature; Firebase tool is used to report
the crash. Any data transmitted is for the exclusive use of RACOM developers to analyze the
problem. It will not be used in any other way by Apple, Google, Firebase or RACOM. For more
4
info see RACOM Privacy policy on our web.
1
https://www.racom.eu/download/hw/ray/free/eng/07_prislusenstvi/OTH-USB_WIFI-W2.pdf
2
https://play.google.com/store/apps/details?id=job.raytools
3
https://itunes.apple.com/cz/app/ray-tools/id1279358257?l=cs&mt=8
4
https://www.racom.eu/eng/about_us/privacy-policy

7.3. Feedback to RACOM

Any feedback for this application is welcome. Please contact us on email address:
<[email protected]>
We would also like to hear from any who would like to become a beta tester of upcoming versions of
RAy Tools.

Troubleshooting
8. Troubleshooting
• Polarization incorrect
Units RAy3-17 and RAy3-24 must be mounted with opposite polarization; one with TX horizontal
polarization (horizontal arrow) and the second with TX vertical polarization (vertical arrow). See Cross
polarization for more info.
Install the unit with the correct horizontal or vertical polarization: The arrow mark indicates the unit
TX polarization. When the arrows heading perpendicular to the earth, the unit transmits a signal in
vertical polarization. When the arrow is heading parallel to the earth, the unit transmits a signal in
horizontal polarization. The connectors must point downward at an angle.
• The link cannot be established
Double check the correct polarization (see above) of both units on the link.
Double check the correct compatibility settings for both units on the link. For more info see the section
called “Radio adaptation” and Troubleshooting topic Setting up a link between RAy3-24S and other
hardware variant of RAy3-24 (see below in this chapter).
Start with the most “resilient” configuration. This configuration depends on the variant of unit. We
recommend using the narrowest available bandwidth (e.g. 3.5 MHz), the lowest modulation level
(QPSK_S) and maximum available output power. TX and RX channels must be the same as the RX
and TX channels in the remote unit. When the connection has been established and the antennas
have been directed, proceed with operation parameters.
• RSS and Antenna alignment
To configure the link and monitor its state, several menus display the RSS signal strength (most in-
teractive are pages Live Data / Bar indicators or Antenna Alignment Tool). Additionally RSS can be
monitored by a voltmeter connected to RSS voltage contacts or by RACOM smartphone application
RAy Tools on a mobile phone connected to RAy WiFi.
Note
Please keep in mind, that RAy is not a measuring instrument, hence the precision of the
RSS reading is limited. Though, in most situations the RSS reading accuracy is better than
± 2dB, the absolute RSS value should not be used for accurate comparisons e.g. between
two links.
• Ethernet Buffers are small
To optimize the total buffer size of RAy radio (by optimizing a cooperation between Ethernet switch
buffer and a buffer inside modem chip) it is required to set 'Flow Control receive' for port 'Air (p9)' (in
menu Switch settings / Interface / Port) on both units to be 'on'. With latest FW versions this parameter
cannot be edited in web interface (CLI still allows that), so the change to the proper state can be
achieved in web interface only by applying unit defaults (followed by manual settings of other para-
meters in this page, if needed). See Chapter 6, Command Line Interface.
Note
Correct Flow Control setting typically increases operational speed of the link for mixed traffic,
where bigger capacity of buffers helps to optimize the link performance.

Troubleshooting
Additional link performance and better utilization of all available buffers in transmitting network
could be typically achieved by configuring Flow Control also between each MW unit and the
nearest switch feeding the link by data. For more info see Port setup in Section 5.5.2, “Inter-
face”.
• Ethernet throughput far below published RFC2544 numbers
In the case when Ethernet throughput of the link is far below expectations based on published Eth-
ernet speeds measured according RFC2544, one of the reasons may be wrong settings for a cooper-
ation between Ethernet buffers inside RAy unit and between RAy unit (Ethernet switch inside the
unit) and outside network (Ethernet switches and routers RAy is connected to).
To ensure buffers inside RAy unit are cooperating optimally please double-check 'Flow Control Re-
ceive' parameter for port 'Air (p9)' (in menu Switch settings / Interface / Port) - it should be 'on' for
both units. (Units produced with initial FW 1.0.16.0 and later solve that automatically, so there is no
need to manually set the parameter).
• Access to the Local unit is blocked
Access to the Local unit may be accidentally blocked, for instance by disabling HTTPS access. If
you can access the Remote unit over HTTPS, type its address in your web browser's address field.
The link will transfer the packet over the Local unit with blocked service access all the way to the
Remote unit, which will give you access to the control menus of both units. Warning, the Remote
unit will report as Local.
• Distinguishing Local-Remote
A unit accessed via service access always reports as Local. If you connect through another (peer)
unit and radio channel, a certain amount of caution is necessary. For example, do not reduce the
transmission power so that the link interrupts accidentally. Errors of this type should be fixed by the
rollback function within approx. 1 minute.
Resolution can be done by comparing the length of ping on Local and Remote. Pinging the unit behind
the radio channel is slower. The difference is more pronounced in the case of a long packet and the
low speed of the radio channel.
• Access security
For better protection against unauthorised access to configuration you should only allow as few kinds
of access as possible. The most secure type is SSH with key – leave only SSH active with "only key"
choice.
• Problem with HTTPS certificate
First login into the unit management typically requires to accept web browser warning about self-
signed HTTPS certificate. The issue may occur if a list of trusted HTTPS certificates stored by your
web browser already contains a record for a network element with identical IP address or network
name as the current unit management interface. In this case, the trusted HTTPS certificates for the
particular network element in your web browser needs to be manually erased. After that self-signed
certificate of the unit can be accepted.
Fast workaround: Try to use a different web browser or use HTTP connection instead (should be no
issue in private network).
• Overexcited receiver

Troubleshooting
A natural property of each radio receiver is to compress the signal in one of the functional blocks,
when the signal level gets out of the AGC (automatic gain control) dynamic range. The result of this
effect is non-linear distortion of the received signal which is observed as decrease in the signal to
noise ratio, i.e. in case of digital modulations increase of the Mean Square Error (MSE).
Limit for guaranteed functionality of RAy3 radio receiver is -15 dBm (measured on the waveguide
input). This limit applies for all channel bandwidths and all modulations.
Beyond this limit the distortion of linearity appears and signal quality is depreciated. In extreme cases,
this can lead to the disintegration of the radio link due to reduced signal to noise ratio (as a result of
signal distortion).
• Setting up a link between RAy3-24S and other hardware variant of RAy3-24
Sometime it is necessary to set up a link from a legacy unit RAy3-24S and some newly deployed
hardware variant of RAy3-24 unit (like RAy3-24X) - for example after exchange of failed unit on one
end of the link (for an explanation of hardware variants '24S', '24X', '24E' and other see Section 1.7,
“Ordering codes”).
Then it is necessary to configure newly deployed unit to behave like unit variant 'S' (legacy model).
To achieve that the parameter 'Unit 24S compatibility' (in menu Tools / Maintenance / Radio adaptation)
has to be set to 'active'.
Note
Wrong setting of compatibility causes the link is not established (both units remain in status
'Connecting').
Unit with FW version 1.0.14.0 with activated 'Unit S mode' (identical with 'Unit 24S compat-
ibility' in later FW versions) requires to manually set RX FlowControl for port 'Air (p9)' (in
menu Switch settings / Interface / Port) to the value 'auto'. On FW version 1.0.16.0 it is re-
commended to set this parameter to 'on'. In later FW versions it is enough to manually apply
default values of FlowControl parameters.

Technical parameters
9. Technical parameters
9.1. General parameters
9.1.1. Overview
Tab. 9.1: Parameters 1
RAy3 Technical parameters 1

Type RAy3-17 RAy3-24
Band 17.10 – 17.30 GHz 24.00 – 24.25 GHz

Type of duplex traffic FDD (Frequency division duplex)
ODU units One universal unit
Bandwidth 3.5; 5; 7; 10; 14; 20; 28; 40; 56; 80; 100; 112 MHz
1)
Modulation QPSK_S ; QPSK; 16; 32; 64; 128; 256; 512; 1024; 2048; 4096 QAM
ACM yes
Forward Error Corr. LDPC, RS
Flexible, min. 24 MHz between channel edges
Channels gap
or 18 MHz in case of 2 × 112 MHz Bandwidth
User data speed (each 2.7 – 1002 Mbps

direction) detail
Data speed according Up to 987 Mbps
to RFC 2544 detail
268 µs (64 B / 366 Mbps); 313 µs (1518 B / 366 Mbps)
Latency
173 µs (64 B / 1002 Mbps); 198 µs (1518 B / 1002 Mbps)
-99.0 dBm (2.7 Mbps) -99.0 dBm (2.7 Mbps)
-6 -52.5 dBm (1002 Mbps) -52.5 dBm (1002 Mbps)
Sensitivity, BER 10
detail detail
Output Power -30 to +10 dBm -30 to +10 dBm

2)
(-30 to -15 dBm)
ATPC yes
ver. 1.2
1)
Stability optimized (stronger) FEC
2)
RF Output power -30 to -15 dBm for all models with variant “R” (e.g. RAy3-24R or RAy3-24NR)

Tab. 9.2: Parameters 2
RAy3 Technical parameters 2

3)
1 Gb Eth. (10/100/1000) 1000BASE-T, MTU 10240 bytes ,
User interface RJ45
recommended cable S/FTP Cat.6, Cat.7
1 Gb Eth. (10/100/1000) 1000BASE-T / 1000BASE-SX / 1000BASE-LX,
User interface SFP 3)
MTU 10240 bytes , user exchangeable SFP, power consumption max. 1.25 W
Service interface USB 2.0, Host-A: USB / WiFi, USB / ETH
Synchronization Synchronous Ethernet; IEEE-1588v2, Transparent clock
Config. & Manag. Web, CLI (HTTP, HTTPS, SSH, Telnet)
4)
Encryption AES 128, 192, 256
Floating, PoE IEEE 802.3at

Power
PoE injector (20-60 VDC), DC/RJ45 (20-60 VDC)
Power consumption 22.5 W (typ.) – 24.5 W (incl. SFP)
Operating temperature -30 to +55°C (EN 300 019-1-4, class 4.1.)
range
Surge immunity 4 kV according to EN 61000-4-5
ESD immunity 8 kV according to EN 61000-4-2
Mechanical design FOD (Full Outdoor), antenna mounting compatible with RAy1 and RAy2
IP code IP66 (Ingress Protection)
Dimensions 245 × 245 × 160 mm
Weight 2.6 kg
Antenna Class 3, 0.3 – 1.2 m, direct mounting (Jirous or LEAX/Arkivator or others)
Spectrum EN 300 440 V2.2.1

EN 301 489-1 V2.1.1
EMC EN 301 489-3 V1.6.1
EN 301 489-4 V3.1.1
Safety EN 62368-1:2014 + A1:2017
FCC / IC CFR 47 part 15 (SQT-RAY3-24) / (24993-RAY324) - for RAy3-24 only
ver. 1.3
3)
Model RAy3-24S (produced December 2018 till April 2019) has MTU 2048 bytes. All other models
have MTU 10240 bytes.
4)
Encryption is possible only with model variants 'X, 'S' and 'E'. Variants 'S' and 'X' means the unit is
equipped with HW module for encryption acceleration, variants 'E' and 'N' are not equipped. Variant
'E' allows SW encryption, while variant 'N' does not allow any encryption to be used.

9.1.2. Link speed
Tab. 9.3: Link speed - raw link
RAy3 Radio parameters – Bit Rate [Mbps]

Band Modulation
width QPSK QPSK 16 32 64 128 256 512 1024 2048 4096
1)
MHz _S QAM QAM QAM QAM QAM QAM QAM QAM QAM
3.5 2.7 5.0 9.5 11 15 17 19 21 23
5 3.8 7.1 14 16 21 25 28 31 33
7 5.8 10 20 24 31 37 42 47 52 57
10 7.9 14 27 33 42 50 57 64 71 78
14 12 22 41 50 65 77 88 98 109 119 128
20 17 32 60 72 94 111 127 142 158 171 185
28 24 38 81 105 132 157 181 202 227 249 269
40 34 54 113 148 185 220 253 283 318 348 377
56 49 81 169 213 268 319 366 414 459 501 540
80 69 115 240 303 381 454 521 589 653 713
100 87 145 299 381 479 569 653 736 820 895
112 97 162 334 426 537 637 731 824 918 1002
ver. 1.2
1)
Tab. 9.4: Link speed - Ethernet (according to RFC 2544)
The full-size table is located on the next page.
ver. 1.1
1)

RAy3 Link speed [Mbps] for Ethernet frames 64 B / 1518 B / 8960 B

Band Modulation
width QPSK QPSK 16 32 64 128 256 512 1024 2048 4096
1)
3.5 2.4 4.6 8.8 11 14 16 18 20 21
2.6 4.7 9.3 11 14 17 19 21 23
2.6 4.8 9.4 11 14 17 19 21 23
5 3.5 6.6 13 15 20 23 26 29 31
3.6 6.9 13 16 21 24 27 30 33
3.6 7.0 13 16 21 24 28 31 33
7 5.2 9.8 19 23 29 34 39 44 48 53
5.5 10 20 24 31 36 41 46 51 57
5.6 10 20 24 31 37 42 46 51 57
10 7.3 13 26 31 40 47 54 60 67 73
7.7 14 27 33 42 50 57 64 71 78
7.8 14 27 33 42 50 57 64 71 78
14 11 21 39 47 61 72 82 92 103 112 121
12 22 41 50 65 77 87 98 109 118 128
12 22 41 50 65 77 88 98 109 119 128
20 16 30 56 68 88 104 119 133 148 161 174
17 32 59 72 93 111 126 141 157 171 184
17 32 59 72 93 111 127 141 157 171 185
28 23 36 76 99 124 148 170 190 213 234 252
24 38 81 105 131 157 180 202 226 248 268
24 38 81 105 132 157 180 202 227 248 269
40 32 50 107 139 174 207 238 267 299 328 352
34 53 113 147 184 220 252 282 317 347 375
34 54 113 147 184 220 252 283 317 348 376
56 46 76 158 200 252 300 345 390 432 471 508
48 81 168 212 267 318 365 413 458 499 539
48 81 168 213 267 319 366 413 459 500 540
80 65 108 226 285 358 428 491 555 615 671
69 115 239 302 380 453 519 587 651 711
69 115 239 303 380 454 520 588 653 712
100 81 136 281 358 451 535 615 692 739 760
86 144 297 380 478 567 651 733 817 892
86 144 298 381 479 568 652 735 820 894
112 91 152 314 393 505 599 688 740 761 762
96 161 333 425 535 635 728 821 916 987
97 161 334 426 536 636 730 823 918 998

9.2. RAy3-17 parameters
9.2.1. Upper/Lower Limits
Tab. 9.5: Frequency limits - 17 GHz
RAy3-17 Band Range [GHz]

Unit L Unit U
min 17.104 17.104
max 17.296 17.296
ver. 1.0
9.2.2. Radio parameters

-6
Tab. 9.6: Radio parameters - 17 GHz, BER = 10
Table cells contain values: ver. 1.0

User Bit Rate [Mbps] Bit Rate for the selected modulation and bandwidth
RSS (Received Signal Strength) [dBm] Minimum required RSS (Receiver Threshold,
Rx Sensitivity)
MSE (Mean Square Error) [dB] Maximum required MSE (the inverse to often
used value SNR)

1)

RAy3-17 Radio parameters – Bit Rate [Mbps] / RSS [dBm] / MSE [dB] ver. 1.1
Band Modulation
width QPSK QPSK 16 32 64 128 256 512 1024 2048 4096
1)
3.5 2.7 5.0 9.5 11 15 17 19 21 23
-99.0 -94.5 -88.5 -85.0 -82.0 -79.0 -76.0 -73.0 -69.5
-6.1 -9.0 -15.2 -18.4 -21.6 -24.9 -28.0 -31.0 -34.6
5 3.8 7.1 14 16 21 25 28 31 33
-97.5 -93.0 -87.5 -84.0 -81.0 -78.0 -75.0 -72.0 -69.0
-6.5 -9.0 -15.1 -18.0 -21.3 -24.6 -27.6 -30.7 -34.3
7 5.8 10 20 24 31 37 42 47 52 57
-95.5 -92.0 -86.5 -83.0 -80.0 -77.0 -74.0 -71.0 -67.0 -63.0
-6.2 -8.5 -14.4 -17.7 -20.9 -24.2 -27.5 -30.3 -34.6 -38.2
10 7.9 14 27 33 42 50 57 64 71 78
-93.5 -90.5 -85.0 -81.5 -78.5 -75.5 -72.5 -69.5 -66.0 -62.5
-7.0 -8.5 -14.4 -17.4 -20.5 -23.8 -26.9 -29.7 -33.6 -37.0
14 12 22 41 50 65 77 88 98 109 119 128
-92.0 -89.0 -83.5 -80.0 -77.0 -74.0 -71.0 -68.0 -65.0 -61.5 -57.5
-6.6 -8.7 -14.3 -17.4 -20.6 -23.6 -26.7 -29.6 -33.3 -36.5 -40.2
20 17 32 60 72 94 111 127 142 158 171 185
-91.5 -87.5 -82.0 -78.5 -75.5 -72.5 -69.5 -66.5 -63.5 -60.5 -57.0
-6.1 -8.7 -14.2 -17.3 -20.2 -23.5 -26.5 -29.3 -32.6 -35.4 -39.1
28 24 38 81 105 132 157 181 202 227 249 269
-91.0 -88.0 -81.5 -77.0 -74.0 -71.0 -68.0 -65.0 -62.0 -59.0 -56.0
-5.8 -7.2 -13.5 -17.2 -20.1 -23.3 -26.2 -29.2 -32.7 -35.5 -38.7
40 34 54 113 148 185 220 253 283 318 348 377
-89.0 -86.0 -79.5 -75.5 -72.5 -69.5 -66.5 -63.5 -60.5 -57.5 -54.5
-5.8 -7.3 -13.6 -17.3 -20.1 -23.3 -26.1 -29.0 -32.4 -35.2 -38.1
56 49 81 169 213 268 319 366 414 459 501 540
-88.0 -84.5 -77.5 -73.5 -70.5 -67.5 -64.5 -61.5 -58.5 -55.5 -52.5
-5.5 -7.3 -13.9 -17.4 -20.2 -23.4 -26.5 -29.3 -32.3 -35.0 -38.2
80 69 115 240 303 381 454 521 589 653 713
-86.5 -83.0 -76.0 -72.0 -69.0 -66.0 -63.0 -60.0 -57.0 -54.0
-5.5 -7.3 -13.8 -17.5 -20.2 -23.5 -26.5 -29.4 -32.4 -35.0
100 87 145 299 381 479 569 653 736 820 895
-85.5 -82.0 -75.0 -71.0 -68.0 -65.0 -62.0 -59.0 -56.0 -53.0
-5.6 -7.4 -13.7 -17.2 -20.3 -23.3 -26.3 -29.0 -32.2 -34.9
112 97 162 334 426 537 637 731 824 918 1002
-85.0 -81.5 -74.5 -70.5 -67.5 -64.5 -61.5 -58.5 -55.5 -52.5
-5.5 -7.3 -13.7 -17.2 -20.3 -23.2 -26.5 -29.1 -32.2 -35.0

9.2.3. ACM switching
Tab. 9.7: ACM switching - 17 GHz according to MSE state
RAy3-17 MSE degrade [dB] / MSE improve [dB]

Band Modulation
width QPSK QPSK 16 32 64 128 256 512 1024 2048 4096
1)
3.5 -- -10.5 -16.7 -23.1 -23.1 -26.4 -29.5 -32.5 -36.1
-11.5 -17.7 -20.9 -24.1 -27.4 -30.5 -33.5 -37.1 --
5 -- -10.5 -16.6 -22.8 -22.8 -26.1 -29.1 -32.2 -35.8
-11.5 -17.6 -20.5 -23.8 -27.1 -30.1 -33.2 -36.8 --
7 -- -10.0 -15.9 -22.4 -22.4 -25.7 -29.0 -31.8 -36.1 -39.7
-11.0 -16.9 -20.2 -23.4 -26.7 -30.0 -32.8 -37.1 -40.7 --
10 -- -10.0 -15.9 -22.0 -22.0 -25.3 -28.4 -31.2 -35.1 -38.5
-11.0 -16.9 -19.9 -23.0 -26.3 -29.4 -32.2 -36.1 -39.5 --
14 -- -10.2 -15.8 -22.1 -22.1 -25.1 -28.2 -31.1 -34.8 -38.0 -41.7
-11.2 -16.8 -19.9 -23.1 -26.1 -29.2 -32.1 -35.8 -39.0 -42.7 --
20 -- -10.2 -15.7 -21.7 -21.7 -25.0 -28.0 -30.8 -34.1 -36.9 -40.6
-11.2 -16.7 -19.8 -22.7 -26.0 -29.0 -31.8 -35.1 -37.9 -41.6 --
28 -- -8.7 -15.0 -21.6 -21.6 -24.8 -27.7 -30.6 -34.2 -37.0 -40.2
-9.7 -16.0 -19.8 -22.6 -25.8 -28.7 -31.6 -35.2 -38.2 -41.2 --
40 -- -8.8 -15.1 -21.6 -21.6 -24.8 -27.6 -30.5 -33.9 -36.7 -39.6
-9.8 -16.1 -19.8 -22.6 -25.8 -28.6 -31.5 -34.9 -37.7 -40.6 --
56 -- -8.8 -15.4 -21.7 -21.7 -24.9 -28.0 -30.8 -33.8 -36.5 -39.7
-9.8 -16.4 -19.9 -22.7 -25.9 -29.0 -31.8 -34.8 -37.5 -40.7 --
80 -- -8.8 -15.3 -21.7 -21.7 -25.0 -28.0 -30.9 -33.9 -36.5
-9.8 -16.3 -20.0 -22.7 -26.0 -29.0 -31.9 -34.9 -37.5
100 -- -8.8 -15.2 -21.8 -21.8 -24.7 -28.0 -30.6 -33.7 -36.5
-9.8 -16.2 -19.7 -22.8 -25.7 -29.0 -31.6 -34.7 -37.5
112 -- -8.8 -15.2 -21.8 -21.8 -24.7 -28.0 -30.6 -33.7 -36.5
-9.8 -16.2 -19.7 -22.8 -25.7 -29.0 -31.6 -34.7 -37.5
ver. 1.1
1)

9.2.4. Frequency tables
Tab. 9.8: Frequency tables 17 GHz
RAy3-17 Frequency tables

name description
rcinfo17_ISM200_default 17.100 - 17.300 GHz default table
The microwave link contains one or more frequency tables (called rcinfo), see menu Radio adaptation.
Tables are labeled in format <name:version>, e.g.: rcinfo17_ISM200_default:15

9.3. RAy3-24 parameters
9.3.1. Upper/Lower Limits
Tab. 9.9: Frequency limits - 24 GHz
RAy3-24 Band Range [GHz]

Unit L Unit U
min 24.004 24.004
max 24.246 24.246
ver. 1.0
9.3.2. Radio parameters

-6
Tab. 9.10: Radio parameters - 24 GHz, BER = 10
Table cells contain values: ver. 1.1

User Bit Rate [Mbps] Bit Rate for the selected modulation and bandwidth
RSS (Received Signal Strength) [dBm] Minimum required RSS (Receiver Threshold,
Rx Sensitivity)
MSE (Mean Square Error) [dB] Maximum required MSE (the inverse to often
used value SNR)

1)

RAy3-24 Radio parameters – Bit Rate [Mbps] / RSS [dBm] / MSE [dB] ver. 1.1
Band Modulation
width QPSK QPSK 16 32 64 128 256 512 1024 2048 4096
1)
3.5 2.7 5.0 9.5 11 15 17 19 21 23
-99.0 -94.5 -88.5 -85.0 -82.0 -79.0 -76.0 -73.0 -69.5
-6.1 -9.0 -15.2 -18.4 -21.6 -24.9 -28.0 -31.0 -34.6
5 3.8 7.1 14 16 21 25 28 31 33
-97.5 -93.0 -87.5 -84.0 -81.0 -78.0 -75.0 -72.0 -69.0
-6.5 -9.0 -15.1 -18.0 -21.3 -24.6 -27.6 -30.7 -34.3
7 5.8 10 20 24 31 37 42 47 52 57
-95.5 -92.0 -86.5 -83.0 -80.0 -77.0 -74.0 -71.0 -67.0 -63.0
-6.2 -8.5 -14.4 -17.7 -20.9 -24.2 -27.5 -30.3 -34.6 -38.2
10 7.9 14 27 33 42 50 57 64 71 78
-93.5 -90.5 -85.0 -81.5 -78.5 -75.5 -72.5 -69.5 -66.0 -62.5
-7.0 -8.5 -14.4 -17.4 -20.5 -23.8 -26.9 -29.7 -33.6 -37.0
14 12 22 41 50 65 77 88 98 109 119 128
-92.0 -89.0 -83.5 -80.0 -77.0 -74.0 -71.0 -68.0 -65.0 -61.5 -57.5
-6.6 -8.7 -14.3 -17.4 -20.6 -23.6 -26.7 -29.6 -33.3 -36.5 -40.2
20 17 32 60 72 94 111 127 142 158 171 185
-91.5 -87.5 -82.0 -78.5 -75.5 -72.5 -69.5 -66.5 -63.5 -60.5 -57.0
-6.1 -8.7 -14.2 -17.3 -20.2 -23.5 -26.5 -29.3 -32.6 -35.4 -39.1
28 24 38 81 105 132 157 181 202 227 249 269
-91.0 -88.0 -81.5 -77.0 -74.0 -71.0 -68.0 -65.0 -62.0 -59.0 -56.0
-5.8 -7.2 -13.5 -17.2 -20.1 -23.3 -26.2 -29.2 -32.7 -35.5 -38.7
40 34 54 113 148 185 220 253 283 318 348 377
-89.0 -86.0 -79.5 -75.5 -72.5 -69.5 -66.5 -63.5 -60.5 -57.5 -54.5
-5.8 -7.3 -13.6 -17.3 -20.1 -23.3 -26.1 -29.0 -32.4 -35.2 -38.1
56 49 81 169 213 268 319 366 414 459 501 540
-88.0 -84.5 -77.5 -73.5 -70.5 -67.5 -64.5 -61.5 -58.5 -55.5 -52.5
-5.5 -7.3 -13.9 -17.4 -20.2 -23.4 -26.5 -29.3 -32.3 -35.0 -38.2
80 69 115 240 303 381 454 521 589 653 713
-86.5 -83.0 -76.0 -72.0 -69.0 -66.0 -63.0 -60.0 -57.0 -54.0
-5.5 -7.3 -13.8 -17.5 -20.2 -23.5 -26.5 -29.4 -32.4 -35.0
100 87 145 299 381 479 569 653 736 820 895
-85.5 -82.0 -75.0 -71.0 -68.0 -65.0 -62.0 -59.0 -56.0 -53.0
-5.6 -7.4 -13.7 -17.2 -20.3 -23.3 -26.3 -29.0 -32.2 -34.9
112 97 162 334 426 537 637 731 824 918 1002
-85.0 -81.5 -74.5 -70.5 -67.5 -64.5 -61.5 -58.5 -55.5 -52.5
-5.5 -7.3 -13.7 -17.2 -20.3 -23.2 -26.5 -29.1 -32.2 -35.0

9.3.3. ACM switching
Tab. 9.11: ACM switching -24 GHz according to MSE state
RAy3-24 MSE degrade [dB] / MSE improve [dB]

Band Modulation
width QPSK QPSK 16 32 64 128 256 512 1024 2048 4096
1)
3.5 -- -10.5 -16.7 -23.1 -23.1 -26.4 -29.5 -32.5 -36.1
-11.5 -17.7 -20.9 -24.1 -27.4 -30.5 -33.5 -37.1 --
5 -- -10.5 -16.6 -22.8 -22.8 -26.1 -29.1 -32.2 -35.8
-11.5 -17.6 -20.5 -23.8 -27.1 -30.1 -33.2 -36.8 --
7 -- -10.0 -15.9 -22.4 -22.4 -25.7 -29.0 -31.8 -36.1 -39.7
-11.0 -16.9 -20.2 -23.4 -26.7 -30.0 -32.8 -37.1 -40.7 --
10 -- -10.0 -15.9 -22.0 -22.0 -25.3 -28.4 -31.2 -35.1 -38.5
-11.0 -16.9 -19.9 -23.0 -26.3 -29.4 -32.2 -36.1 -39.5 --
14 -- -10.2 -15.8 -22.1 -22.1 -25.1 -28.2 -31.1 -34.8 -38.0 -41.7
-11.2 -16.8 -19.9 -23.1 -26.1 -29.2 -32.1 -35.8 -39.0 -42.7 --
20 -- -10.2 -15.7 -21.7 -21.7 -25.0 -28.0 -30.8 -34.1 -36.9 -40.6
-11.2 -16.7 -19.8 -22.7 -26.0 -29.0 -31.8 -35.1 -37.9 -41.6 --
28 -- -8.7 -15.0 -21.6 -21.6 -24.8 -27.7 -30.6 -34.2 -37.0 -40.2
-9.7 -16.0 -19.8 -22.6 -25.8 -28.7 -31.6 -35.2 -38.2 -41.2 --
40 -- -8.8 -15.1 -21.6 -21.6 -24.8 -27.6 -30.5 -33.9 -36.7 -39.6
-9.8 -16.1 -19.8 -22.6 -25.8 -28.6 -31.5 -34.9 -37.7 -40.6 --
56 -- -8.8 -15.4 -21.7 -21.7 -24.9 -28.0 -30.8 -33.8 -36.5 -39.7
-9.8 -16.4 -19.9 -22.7 -25.9 -29.0 -31.8 -34.8 -37.5 -40.7 --
80 -- -8.8 -15.3 -21.7 -21.7 -25.0 -28.0 -30.9 -33.9 -36.5
-9.8 -16.3 -20.0 -22.7 -26.0 -29.0 -31.9 -34.9 -37.5 --
100 -- -8.8 -15.2 -21.8 -21.8 -24.7 -28.0 -30.6 -33.7 -36.5
-9.8 -16.2 -19.7 -22.8 -25.7 -29.0 -31.6 -34.7 -37.5 --
112 -- -8.8 -15.2 -21.8 -21.8 -24.7 -28.0 -30.6 -33.7 -36.5
-9.8 -16.2 -19.7 -22.8 -25.7 -29.0 -31.6 -34.7 -37.5 --
ver. 1.1
1)

9.3.4. Frequency tables
Tab. 9.12: Frequency tables 24 GHz
RAy3-24 Frequency tables

name description
rcinfo24_ISM250_default 24.000 - 24.250 GHz default table
rcinfo24_ISM250_-9dBm 24.000 - 24.250 GHz limited RF power
rcinfo24_ISM250_-15dBm 24.000 - 24.250 GHz limited RF power
rcinfo24_ISM200 24.050 - 24.250 GHz
rcinfo24_ISM150 24.000 - 24.150 GHz
The microwave link contains one or more frequency tables (called rcinfo), see menu Radio adaptation.
Tables are labeled in format <name:version>, e.g.: rcinfo24_ISM250_default:15

Safety, environment, licensing
10. Safety, environment, licensing
10.1. Regulations
RAy3 microwave links must be used in accordance with rules issued by the Telecommunications Au-
thority for the area the device is operating in.
RAy3 microwave links must comply with the maximum permitted radiated power (EIRP) in accordance
with conditions of the given country.
Important
For US:
This device complies with part 15 of the FCC Rules. Operation is subject to the following two
conditions:
1. This device may not cause harmful interference.

2. This device must accept any interference received, including interference that may cause
undesired operation of the device.
Changes or modifications not expressly approved by the party responsible for compliance
could void the user's authority to operate the equipment.
For Canada:
This device contains licence-exempt transmitter(s)/receiver(s) that comply with Innovation,

Science and Economic Development Canada’s licence-exempt RSS(s). Operation is subject
to the following two conditions:
1. This device may not cause harmful interference.

2. This device must accept any interference, including interference that may cause undesired
operation of the device.
L’émetteur/récepteur exempt de licence contenu dans le présent appareil est conforme aux
CNR d’Innovation, Sciences et Développement économique Canada applicables aux appareils
radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes :
1. L’appareil ne doit pas produire de brouillage;

2. L’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est
susceptible d’en compromettre le fonctionnement.

10.2. Safety distance
Safety distances with respect to the US health limits of the electromagnetic field intensity
are in the Minimum Safety Distance tables below, calculated for different antennas and
RAy power levels.
Tab. 10.1: Minimum Safety Distance 24 GHz
RAy3-24 24.000 – 24.250 GHz +10 dBm RF power

Parabolic Distance where the FCC limits is met for
antenna Gain General Population / Occupational /
Antenna code
diameter [dBi] Uncontrolled Exposure Controlled Exposure
[m] [cm] [cm]
ANT-LEAX-RAy-300-24 ø 0.3 37.0
70 30
ANT-JRMB-400-24R ø 0.4 36.8
ANT-LEAX-RAy-600-24 ø 0.6 42.4
120 60
ANT-JRMB-680-24R ø 0.7 41.7
ANT-LEAX-RAy-900-24 ø 0.9 45.7
180 80
ANT-JRMB-900-24R ø 0.9 44.0
ANT-LEAX-RAy-1200-24 ø 1.2 48.4
240 110
ANT-JRMB-1200-24R ø 1.2 46.6
ver. 1.0
10.3. Professional installation

RAy units are only intended for installation by professionally trained people and in locations not access-
ible to the public. Installation and servicing must be carried out by personnel with appropriate technical
training and knowledge of potential hazards.
RAy units shall be installed according to local Electrical Safety Codes. Each person participating on
the installation has to respect all local standards and regulations for personal security and electromag-
netic protection for everybody on the site. We also recommend to consult each site situation with local
experts to ensure both the people and installed equipment are safe, the grounding and other protection
are chosen reasonably for the actual site conditions. Trained staff must check that all parts recommended
by experts regarding grounding and overvoltage protection of sensitive components or infrastructures
are perfectly installed, so they effectively protect the equipment against typical situations.
It is the responsibility of the installer to ensure that all building and safety codes are met and that the
installation is fully completed and equipment properly secured.

10.4. RoHS and WEEE compliance
This product is fully compliant with the European Parliament’s 2011/65/EU RoHS
(Restriction of Certain Hazardous Substances in Electrical and Electronic
Equipment), as amended by Directive (EU) 2015/863, and Directive 2012/19/EU
WEEE (Waste Electrical and Electronic Equipment) environmental directives.
Disposed equipment must be collected separately, and disposed of properly.

In any case it may not be put aside as unsorted municipal waste. Equipment
has to be returned to supplier or producer (RACOM) or placed to a designated
collection point ensuring proper recycling and recovery of waste in an environ-
mentally safe manner using processes that comply with the WEEE Directive.
Battery Disposal RACOM products and accessories may contain a battery. Batteries must be
disposed of properly, and may not be put aside as unsorted municipal waste.
For proper recycling, return the product or its battery to your supplier or place
it to a designated collection point.

10.4.1. RoHS and WEEE Declaration of Conformity
Fig. 10.1: RoHS and WEEE Declaration of Conformity

10.5. RACOM Open Software License

Version 1.0, November 2009
Copyright (c) 2020, RACOM s.r.o., Mírová 1283, Nové Město na Moravě, 592 31
Everyone can copy and spread word-for-word copies of this license, but no changes are permitted.
The program (binary version) is freely available on https://www.racom.eu. This product contains open
source or other software originating from third parties subject to GNU General Public License (GPL),
GNU Library / Lesser General Public License (LGPL) and / or further author licences, declarations of
responsibility, exclusion and notifications. Exact terms of GPL, LGPL and some further licences are
mentioned in the source code packets (typically the files COPYING or LICENSE). You can obtain ap-
plicable machine-readable copies of source code of this software under GPL or LGPL licences on ht-
tps://www.racom.eu. This product also includes software developed by the University of California,
Berkeley and its contributors.
10.6. Warranty
RACOM supplied parts or equipment ("equipment") are covered under warranty for inherently faulty
parts and workmanship for a warranty period as stated in the delivery documentation from the date of
dispatch to the customer. The warranty does not cover custom modifications to software. During the
warranty period RACOM shall, on its option, fit, repair or replace ("service") faulty equipment, always
provided that malfunction has occurred during normal use, not due to improper use, whether deliberate
or accidental, such as attempted repair or modification by any unauthorised person; nor due to the
action of abnormal or extreme environmental conditions such as overvoltage, liquid immersion or
lightning strike.
Any equipment subject to repair under warranty must be returned by prepaid freight to RACOM direct.
The serviced equipment shall be returned by RACOM to the customer by prepaid freight. If circumstances
do not permit the equipment to be returned to RACOM, then the customer is liable and agrees to reim-
burse RACOM for expenses incurred by RACOM during servicing the equipment on site. When
equipment does not qualify for servicing under warranty, RACOM shall charge the customer and be
reimbursed for costs incurred for parts and labour at prevailing rates.
This warranty agreement represents the full extent of the warranty cover provided by RACOM to the
customer, as an agreement freely entered into by both parties.
RACOM warrants the equipment to function as described, without guaranteeing it as befitting customer
intent or purpose. Under no circumstances shall RACOM's liability extend beyond the above, nor shall
RACOM, its principals, servants or agents be liable for any consequential loss or damage caused directly
or indirectly through the use, misuse, function or malfunction of the equipment, always subject to such
statutory protection as may explicitly and unavoidably apply hereto.
Liability for defects does not apply to any product that has been used in a manner that conflicts with
the instructions contained in this operator manual, if the case in which the radio modem is packed has
been opened, or if the equipment has been tampered with.

10.7. Declarations of Conformity
10.7.1. RED Declarations of Conformity
EU DECLARATION OF CONFORMITY
Radio equipment type RAy3-17 Radio SW version

1.0.2
Manufacturer RACOM s.r.o.

Mirova 1283, 592 31 Nove Mesto na Morave, Czech Republic
This declaration of conformity is issued under the sole responsibility of the manufacturer.
The radio equipment described above is in conformity with the Directive 2014/53/EU of the European
Parliament and of the Council on the harmonisation of the laws of the Member States relating to the
making available on the market of radio equipment and repealing Directive 1999/5/EC.
Harmonised standards used for demonstration of conformity:

EMC EN 301 489-1 V2.1.1
EN 301 489-3 V1.6.1
EN 301 489-4 V3.1.1
Safety EN 62368-1:2014+A1:2017
Signed for and on behalf of the manufacturer:
Nove Mesto na Morave, 15th of August 2019

Jiri Hruska, CEO
www.racom.eu
ver. 1.0
Fig. 10.2: RED Declaration of Conformity for RAy3-17

EU DECLARATION OF CONFORMITY
Radio equipment type RAy3-24 Radio SW version

1.0.2
Manufacturer RACOM s.r.o.

Mirova 1283, 592 31 Nove Mesto na Morave, Czech Republic
This declaration of conformity is issued under the sole responsibility of the manufacturer.
The radio equipment described above is in conformity with the Directive 2014/53/EU of the European
Parliament and of the Council on the harmonisation of the laws of the Member States relating to the
making available on the market of radio equipment and repealing Directive 1999/5/EC.
Harmonised standards used for demonstration of conformity:

EMC EN 301 489-1 V2.1.1
EN 301 489-3 V1.6.1
EN 301 489-4 V3.1.1
Safety EN 62368-1:2014+A1:2017
Signed for and on behalf of the manufacturer:
Nove Mesto na Morave, 26th of October 2018

Jiri Hruska, CEO
www.racom.eu
Tel.: +420 565 659 511 | Fax: +420 565 659 512 | E-mail: [email protected]
ver. 1.0
Fig. 10.3: RED Declaration of Conformity for RAy3-24

10.7.2. Simplified declaration
Simplified EU declaration of conformity
BG С настоящото RACOM s.r.o. декларира, че този тип радиосъоръжение RAy3 е в

съответствие с Директива 2014/53/ЕС.
ES Por la presente, RACOM s.r.o. declara que el tipo de equipo radioeléctrico RAy3 es conforme
con la Directiva 2014/53/UE.
CS Tímto RACOM s.r.o. prohlašuje, že typ RAy3 rádiového zařízení RAy3 je v souladu se směrnicí
2014/53/EU.
DA Hermed erklærer RACOM s.r.o., at radioudstyrstypen RAy3 er i overensstemmelse med

direktiv 2014/53/EU.
DE Hiermit erklärt RACOM s.r.o., dass der Funkanlagentyp RAy3 der Richtlinie 2014/53/EU
entspricht.
ET Käesolevaga deklareerib RACOM s.r.o., et käesolev raadioseadme tüüp RAy3 vastab direktiivi
2014/53/EL nõuetele.
EL Με την παρούσα ο/η RACOM s.r.o., δηλώνει ότι ο ραδιοεξοπλισμός RAy3 πληροί την οδηγία
2014/53/ΕΕ.
EN Hereby, RACOM s.r.o. declares that the radio equipment type RAy3 is in compliance with
Directive 2014/53/EU.
FR Le soussigné, RACOM s.r.o., déclare que l'équipement radioélectrique du type RAy3 est
conforme à la directive 2014/53/UE.
HR RACOM s.r.o. ovime izjavljuje da je radijska oprema tipa RAy3 u skladu s Direktivom
2014/53/EU.
IT Il fabbricante, RACOM s.r.o., dichiara che il tipo di apparecchiatura radio RAy3 è conforme
alla direttiva 2014/53/UE.
LV Ar šo RACOM s.r.o. deklarē, ka radioiekārta RAy3 atbilst Direktīvai 2014/53/ES.
LT Aš, RACOM s.r.o., patvirtinu, kad radijo įrenginių tipas RAy3 atitinka Direktyvą 2014/53/ES.
HU RACOM s.r.o. igazolja, hogy a RAy3 típusú rádióberendezés megfelel a 2014/53/EU

irányelvnek.
MT B'dan, RACOM s.r.o., niddikjara li dan it-tip ta' tagħmir tar-radju RAy3 huwa konformi mad-
Direttiva 2014/53/UE.
NL Hierbij verklaar ik, RACOM s.r.o., dat het type radioapparatuur RAy3 conform is met Richtlijn
2014/53/EU.
PL RACOM s.r.o. niniejszym oświadcza, że typ urządzenia radiowego RAy3 jest zgodny z
dyrektywą 2014/53/UE.
PT O(a) abaixo assinado(a) RACOM s.r.o. declara que o presente tipo de equipamento de rádio
RAy3 está em conformidade com a Diretiva 2014/53/UE.

RO Prin prezenta, RACOM s.r.o. declară că tipul de echipamente radio RAy3 este în conformitate
cu Directiva 2014/53/UE.
SK RACOM s.r.o. týmto vyhlasuje, že rádiové zariadenie typu RAy3 je v súlade so smernicou
2014/53/EÚ.
SL RACOM s.r.o. potrjuje, da je tip radijske opreme RAy3 skladen z Direktivo 2014/53/EU.
FI RACOM s.r.o. vakuuttaa, että radiolaitetyyppi RAy3 on direktiivin 2014/53/EU mukainen.
SV Härmed försäkrar RACOM s.r.o. att denna typ av radioutrustning RAy3 överensstämmer med
direktiv 2014/53/EU.

10.8. FCC and IC authorization
FCC (US) compliance
RAy3-24 complies with CFR 47 part 15.
Code FCC part FCC ID

RAy3-24 15 SQT-RAY3-24
IC / ISED (Canada) compliance
RAy3-24 complies with ISED Canada RSS-210 Issue 9.
Code IC specification IC Certif. No.

RAy3-24 RSS-210 Issue 9 24993-RAY324

10.9. Country of Origin Declaration
To whom it may concern
Country of Origin Declaration
Producer: RACOM s.r.o.

Address: Mirova 1283, 592 31 Nove Mesto na Morave, Czech Republic
VAT No: CZ46343423
We, the manufacturer, hereby declare that Country of Origin of the RAy microwave links
and its accessories is the Czech Republic, EU.
Part Number Description

RAy3-24 Unit RAy3-24, 2× Gb Eth
Nove Mesto na Morave, 26 of October 2018

Jiri Hruska, CEO
www.racom.eu
ver. 1.0
Fig. 10.4: Country of Origin Declaration

SSH key generation
Appendix A. SSH key generation
Linux
Use “ssh-keygen” command.
Windows
Use "PUTTYGEN.EXE" software, which is typically located in the c:\Program Files\putty\ directory and
apply the "Generate" button.
To use CLI (Command Line Interface) access the unit with a PuTTY client. Access is protected by an
SSH key.

Unit block diagrams
Appendix B. Unit block diagrams
Unit overview
Eth1
Eth2 SWITCH 2.5 Gbps
LoPri
Radio
1 Gbps Modem
1 Gbps
HiPri
USB CPU
Fig. B.1: Block diagram of the unit

Index block, 205
directing
calculation, 71
A indication, 69
accessories, 35 lobes, 70
ACM, 86
address
IP, 42, 89
E
egress
MAC, 82
parameters, 121
advanced
EIRP, 86
ATU, 137
environment, 193
RSTP, 139
STU, 132
VLAN, 127 F
VTU, 134 factory settings, 142
alarms, 98 FCC
antenna authorization, 202
Alignment Tool, 152, 174 feature keys, 44, 146
dimensions, 28 firmware, 147
directing, 69 frequency tables, 149
assembly, 48 function test
lubrication, 52 after installation, 74
ATPC, 86 before installation, 46
authorization, 172
G
B graphs, 157
backup, 142 grounding, 61
bandwidth, 85
box contents, 26 H
help, 166
C https access, 39
CLI, 163, 169
configuration, 76 I
link, 46 installation
connectors antenna, 48
assembly, 57 power, 66
description, 15 RAy , 52
copyright, 5
K
D keys
declaration of conformity, 198 feature, 44
declaration of origin, 203 ssh conversion, 204
default, 39 ssh generation, 204
settings, 142
diagnostics L
Antenna Alignment, 152 LED, 23
graphs, 157 licensing, 193
logs, 161 link
ping, 162 configuration, 46
RSS indication, 73, 152 LLDP protocol, 89
spectrum, 155 logs, 161
diagram

Index
M setup parameters, 74
mobile devices, 152, 174 smartphone, 153, 174
spectrum analyzer, 155
O SSH access, 169
start up, 69
Open Software license, 197
statistics
ordering codes, 30
radio link, 83
RMON, 106
P RSTP, 110
parameters status
presetting, 37 bar, 77
setup, 74 LED, 23
technical, 181 menu, 79
ping, 162
polarization, 10, 54
port
T
tables
connectors, 15
RAy3-17 , 185
parameters, 111, 116
RAy3-24 , 189
power
speeds, 183
DC, 18
technical parameters, 181
PoE, 16
time, 84
product, 10
troubleshooting, 178
conformity
EU, 200
production label, 24 U
programs USB accessories, 92
CLI, 163
ping, 162 V
VLAN, 89
Q
qos
802.1p egress, 125
802.1p ingress, 124
DSCP egress, 127
DSCP ingress, 126
port, 123
Quick guide, 7
R
RAy Tools, 174
rcinfo, 149
restart
button, 22
menu, 151
RoHS and WEEE, 195
rollback, 77, 170
RSS indication, 73
RSS indicator, 152
S
safety, 193
service access, 39, 89

208
Revision History
Revision History
Revision 1.0 2018-10-04
First issue
Revision 1.1 2019-04-15

RAy3-17 data - preliminary
RAy3 HW variants introduced
Revision 1.2 2019-05-20

Extended Chapter 5, Configuration (to reflex FW development)
Revision 1.3 2019-07-23

Updated Legal Notice, Section 1.6, “Sizes, packaging and labeling”, Section 1.7, “Ordering
codes” and Section 10.8, “FCC and IC authorization” (RAY3-24 FCC for US and IC for
Canada compliance)
Revision 1.4 2019-09-06

Updated Chapter 2, Accessories
Extended Section 10.7.1, “RED Declarations of Conformity” - DoC RAy3-17
Revision 1.5 2019-11-11

New items in Chapter 2, Accessories (marked by '*')
Improved description of some items (accepted polarities of PoE and power supply,
FlowControl parameters in Eth switch, Chapter 8, Troubleshooting).
Final parameters for RAy3-17
Revision 1.6 2020-02-10

Extended sections:
PIRL setup, Egress queue setup and VLAN setup (to reflex FW development).
Improved description of some items (new Pressure equalization).
Revision 1.7 2020-04-09

In Chapter 2, Accessories removed sections 2.1. Overview and 2.2 Details (from now
1
all Accessories are available in section Accessories on RAy web site).
Improved description of some items:
Section 1.3.3, “DC power (using ETH1+POE)”
Table 1.2, “Overview of Jirous Class 2 and Class 3 antennas”
Section 1.7, “Ordering codes”
Antenna mounting kit for standard Andrew antennas
Flow control
Radio adaptation
Extended sections:
Section 5.5, “Switch settings” - RSTP status, RSTP setup (to reflex FW development)
Revision 1.8 2020-06-22
1

Revision History
Improved description of some items:

Section 1.7, “Ordering codes”
Section 3.2, “Basic link configuration”
Section 4.3.2, “ RAy unit mounting to the antenna”
Section 5.5.1, “Status” - RMON counters
Chapter 7, RAy Tools app for Mobile devices
Removed Appendix B. - Change of HTTPS certificate (not relevant for RAy3 yet)
Revision 1.9 2020-09-29

Completely new Section 5.5.3, “QoS” (to reflex FW development)
Improved description of Section 1.3.3, “DC power (using ETH1+POE)”

Ray3 Man en

Uploaded by

Copyright:

Available Formats

Ray3 Man en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ray3 Man en

Uploaded by

Copyright:

Available Formats

User manual

RAy3 Microwave Link

© RACOM s.r.o. – RAy3 Microwave Link 3

10.7. Declarations of Conformity ............................................................................................. 198

4 RAy3 Microwave Link – © RACOM s.r.o.

© 2020 RACOM. All rights reserved.

© RACOM s.r.o. – RAy3 Microwave Link 5

6 RAy3 Microwave Link – © RACOM s.r.o.

3. Power supply 4. Configuration

- Web browser access to management: - Antenna Alignment Tool:

Configuration and backup of basic parameters

© RACOM s.r.o. – RAy3 Microwave Link 7

5. Bracket and antenna 6. Unit lubrication and installation

7. Unit polarization 9. Power grounding and connections

8 RAy3 Microwave Link – © RACOM s.r.o.

10. Directing antennas 11. RSS measurement

© RACOM s.r.o. – RAy3 Microwave Link 9

1.1. Main characteristics

This link is formed by two RAy units, each equipped

RAy product line has been designed to have minimum

HW models are determined only by frequency bands,

Cross polarization means that one side of the link

• Management packets targeted for RAy units itself

10 RAy3 Microwave Link – © RACOM s.r.o.

© RACOM s.r.o. – RAy3 Microwave Link 11

1.2. Mechanical interfaces

1.2.1. Antenna waveguide

Fig. 1.2: Waveguide pivot and flange

12 RAy3 Microwave Link – © RACOM s.r.o.

1.2.2. Unit mounting

Fig. 1.3: Antenna and RAy3 unit

1.2.3. Grounding screw

© RACOM s.r.o. – RAy3 Microwave Link 13

1.2.4. Pressure equalization

Pressure equalization between outside and inside of RAy

Do not manipulate or remove this small plastic

Warranty does not apply for units with this screw

Fig. 1.5: Pressure equalization screw

14 RAy3 Microwave Link – © RACOM s.r.o.

1.3. Ethernet + power interfaces

Fig. 1.6: Slots ETH1+POE, ETH2

© RACOM s.r.o. – RAy3 Microwave Link 15

1.3.1. RJ45 connector (ETH1+POE)

RJ45 socket connector marked „ETH1+POE“ is a standard

This port can be optionally used for power sourcing the

Technical parameters of PoE power input:

Supported voltage range is 20 to 60 V, both polarities

16 RAy3 Microwave Link – © RACOM s.r.o.

1.3.2. SFP slot (ETH2)

„ETH2“ is a standard SFP slot for 10/100/1000 Mbps Eth-

The SFP status LED is located just next to the slot. It is

© RACOM s.r.o. – RAy3 Microwave Link 17

1.3.3. DC power (using ETH1+POE)

Direct DC power source can be used to power the RAy3 unit.

• DC terminal (+) RJ45 pins: 1,2,4,5

Supported voltage range is 20 to 60 V, both polarities are sup-

Optional grounding of DC cable should be connected directly to the

More information about DC power sourcing installation can be found