Equipment for unlicensed frequency bands is being broadly produced as consumer goods. Equipment for licensed frequency bands is specific and is not being designed for mass production, which has an impact on its costs.
Equipment for unlicensed frequency bands is being broadly produced as consumer goods. Equipment for licensed frequency bands is specific and is not being designed for mass production, which has an impact on its costs.
In most cases unlicensed bands are industrial, scientific and medical (ISM) radio bands which originally were reserved for non-communication purposes. Hence, unlicensed operation needs to be tolerant of interference from other devices and limit output power according to local radio band regulations. Licensed operation guarantees interference-free operation and transmission with necessary output power, which eventually results in much longer link distances.
The way of product delivery is decided with due consideration of each individual client and order details. According to the price list, we offer standard FCA Riga delivery. In case of need, we can offer different variants (CIP, CIF, DDU, DDP).
Yes, new products (one piece per order) can be sold to the client as part of Sales or Return condition, so that the client can evaluate functionality and suitability of products before making bigger orders.
Clients endowed with a line of credit can buy products by installments. The volume of the line of credit is being assigned in accordance with the clients' financials for the previous 2 fiscal years, availability of positive references and collaboration history with SAF.
SAF can arrange delivery of its products to locations covered by the services of our partner transportation companies. Delivery conditions can be defined when a concrete delivery order is received.
Yes, it is possible to hold presentations upon request. Please contact our sales department.
The only limitation is operation temperature, which must not exceed -33°C for Full Outdoor Unit / Outdoor Unit (ODU/FODU) and -5°C for Indoor Unit (IDU).
Capacity of equipment operating at full capacity cannot be increased with software upgrade, though every system can have capacity initially limited by means of licensing (CFIP, CFQ) or software (CFM).
Full Outdoor Unit (FODU) comprises management controller, modem, multiplexer and radio in one unit, whereas Outdoor Unit (ODU) comprises only radio part and requires Indoor Unit (IDU) for operation.
Lightning arrestors are highly recommended for system stability.
The following lightning arrestors are required:
In a single link only SAF equipment is interoperable, while outgoing interfaces are compatible with any equipment with appropriate interface support.
Accessories may vary depending on a link configuration planned. Common accessories for any configuration are mounting tools, lightning arrestors, power supplies, appropriate interface cables and connectors.
For any further details please contact sales department firstname.lastname@example.org
Normally links are installed and used on distances over 5-50 km, though every individual case requires discrete calculation because there are plenty of aspects to take into consideration (required capacity, fade margin, rain/multipath availability, available bandwidth, topography of the region, annual temperature, rain zone, height over sea level, antenna size, etc.). Under favorable conditions distance may be increased up to 150 km, but under unfavorable conditions distance may decrease to 1 km. Please refer to case study examples to assess real world practice
SAF equipment is compatible with any Network Management System (NMS) with Management Information Base (MIB) support.
In order to use NMS initially all Network Elements (IDU+ODU) should be properly configured. Please follow the steps below for proper Network Element configuration.
In order to configure IP addresses for NMS it should be configured in a way so that it is possible to ping management IP address and service channel IP address for both ends (Local and Remote) from the NMS server.
To do it, you need to add routes as it is shown in the following picture.
If there will be more than one link in the network, then we recommend that IP mask of site from which the chain will begin should not be greater than 255.255.255.240.
Service channel configuration
All IDU except CFM- M-MUX, CFM-MP-MUX, CFM-4M-MUX, CFM-4P-MUX service channel configuration can be as in the example (picture 1). For CFM-M-MUX, CFM-MP-MUX, CFM-4M-MUX, CFM-4P-MUX with soft version 4.20 and higher it is possible to change mask for service channel. By default the SLIP mask is 255.255.255.255. If you do not change the SLIP mask then it is possible to use the same configuration as in example (picture 1).
For software versions less than 4.20 contact techsupport and ask for a software upgrade.
For all IDU except CFM-M-MUX, CFM-MP-MUX, CFM-4M-MUX, CFM-4P-MUX default read community string is Saf-public, and write community string is Saf-private.
For CFM-M-MUX, CFM-MP-MUX, CFM-4M-MUX, CFM-4P-MUX there is no default read and write community strings. They have to be entered via telnet or console. It can be done with commands as follows:
SNMP community read [name]
SNMP community write [name]
Also for CFM-M-MUX, CFM-MP-MUX, CFM-4M-MUX, CFM-4P-MUX SNMP host have to be added. It can be done with following command:
SNMP host add [IP of management server]
It is made for security purposes. IDU will not answer to SNMP requests from IP addresses which are different from those which are added. There can be more than one address of management server.
All our products support management channels: Ethernet (CFIP, CFQ) and routed IP protocol (CFM). It means that you can manage any 3rd party device connected to SAF microwave link management channel network over Ethernet or IP protocol. SAF NMS by default can monitor only SAF manufactured devices, any other third party equipment monitoring requires integration procedure made by SAF NMS team. In such case please contact SAF Tehnika techsupport department by email:
CFIP: In-Band - same Ethernet as user traffic; CFM: out-of band: dedicated service channel.
Not any NMS software limitations regarding IP addressing.
There is not any NMS software limitations regarding NEs count. It depends only on PC (as NMS Server) resources (CPU, RAM, HDD).
Contact your sales manager or email to email@example.com to get detailed information on the subject.
Emission designator for SAF radio units has the form of xMxxD1W for channel bandwidth <10MHz or xxMxD1W for channel bandwidth ≥10MHz, where x will be substituted with required channel bandwidth, including one or two decimal places. For example, for 3.5 MHz channel Integra emission designator is 3M50D1W but for 60 MHz channel it will be 60M0D1W.
The CFIP products support the following standards:
IEEE 802.1p (traffic prioritization)
IEEE 802.1Q (VLAN Tagging)
IEEE 802.3u (100BASE-TX (SAF FreeMile 5.8/17/24, CFIP-106/108, CFIP PhoeniX M))
IEEE 802.3ab (1000BASE-T (CFIP Lumina/Marathon/PhoeniX/PhoeniX M)
IEEE 802.3x (Full duplex IEEE 802.3x flow control (PAUSE))
If unit was initially licensed in SAF factory premises, licenses can be managed using ‘License management' section in Web GUI.
Checklist for solving such issue is as follows:
1) Was the link tested in lab before? It is highly recommended to verify equipment operation in lab before installation on sites.
2) Is there clear line of sight between antennas? It is not enough just to „see” the remote antenna. Fresnel zone clearance also should be considered. An obstruction within the Fresnel zone can cause signal attenuation due to diffraction.
3) Is Tx power configured on maximum allowable value? It is recommended to set maximum allowable Tx output power on both radios during link installation and antenna alignment.
4) Is polarization of antennas and radios the same on both ends of link? Be sure that both antennas and ODUs are installed in position of the same polarization on both sites.
5) Is the same frequency channel set on both ends of the link? It is mandatory that on both radios is set the same frequency channel.
6) Are ATPC and ACM features disabled? All additional features which can change parameters, such as Tx power and modulation must be disabled during link installation. Only after successful link installation those features can be enabled.
7) Do antennas support the same frequency as radios? Be sure that antennas support the same frequency range as radios.
If all mentioned points above are verified and diagnosed as correct then repeat antenna alignment procedure from the beginning.
6GHz CFIP radios have N-Type female connector.
SAF Tehnika's 24GHz radios utilize both polarizations for duplex transmission, therefore radio should be installed with 90 degrees offset regarding remote side of the link.
EOW (Engineering Order Wire) in CFIP PhoeniX, PhoeniX M and CFIP Marathon is realized using 3.5mm headset.
In case of CFIP-106/108 FODU and CFIP Lumina FODU you can use an IP phone for EOW purposes.
It is possible to choose any other coaxial cable, but main thing is to ensure that this cable has 50 Ohm impedance and total attenuation per the necessary cable length does not exceed 20dB at 350 MHz frequency. SAF does not guarantee proper operation of the link in case cable attenuation exceeds 20 dB.
At the moment SAF products do not support Ethernet in the first mile OAM.
Cisco router traffic shaper settings for Ethernet interface going to microwave link shall be as follows:
traffic-shape rate bit-rate [burst-size [excess-burst-size ]]
traffic-shape group access-list bit-rate [burst-size [excess-burst-size]]
The former command traffic shapes all traffic on an interface. The latter uses an access-list to specify which traffic is to be traffic shaped.
bit-rate: Bit rate that traffic is shaped to in bits per second.
burst-size: Sustained number of bits that can be transmitted per interval. The default is the bit-rate divided by 8.
Burst size cannot exceed half of switch/bridge buffer size.
excess-burst-size: Maximum number of bits that can exceed the burst size in the first interval in a congestion event. The default is equal to the burst-size.
The measurement interval is calculated by dividing the burst-size (if non-zero) by the bit rate. If the burst-size is zero, the excess-burst-size is used (if non-zero).
Here is command example for 34 Mbit link:
traffic-shape rate 31000000 124000 0 1000
Generally, you need SAF provided Path calculation tool, but in case of verifying Fresnel zone clearance, when inspecting path profile, you should use "Pathloss".
There could be many reasons why you do not see expected bitrate with your tools:
So you see that option a and maybe b is more or less real, but option c is unlikely even on Gigabit Ethernet. That is - all mentioned transfer methods give the same average bitrate of 313 Mbps. Option c is impossible on SAF products because of switch buffer limitations. This is a well-known side-effect of Ethernet bottlenecks. You shall either make your traffic not so bursting or, if possible, use traffic shaping services of your Cisco Switches to limit traffic flow at exactly 313 Mbps - then it is upon your switch what to drop and how.
It is highly recommended to use radios with appropriate frequency antennas, otherwise it is impossible to predict antenna performance.
First of all it is necessary to spot all of the things that could cause the damages and take the pictures of them. The pictures should contain:
- the view of received package, especially the wrapped or smashed places;
- the view of opened package with an antenna inside;
- the overall view of the antenna with damages;
- the view of the damaged places on the antenna;
- the view of S/N of antenna and the package.
Secondly, need to prepare a list of the damages and their short descriptions. All this data should be summarized and sent to the technical support of SAF Tehnika.
Antennas sizes’ and frequency range’s choice is strongly dependent on the link distance and environmental conditions. For longer distances it is recommended to use lower frequency ranges and bigger antenna sizes, while for shorter distances recommended to use higher frequency ranges and smaller antenna sizes. Need to keep in mind that for frequency ranges below 10GHz rain fading is negligible and main performance factor is multipath fading. Frequency ranges above 10GHz start being considerably affected by the rain, therefore high frequency range usage should be avoided for the terrain with high rain rate. Anyways each particular link should be carefully studied before installation and antennas sizes, frequency range should be estimated during link planning.
For frequency ranges below 10GHz rain fading is negligible and main performance factor is multipath fading.
In common cases for 1+0 configuration single polarized antennas should be considered. Dual polarized antenna allows to connect 2 ODUs to a single antenna so it can be used for such applications as 2+0, 1+1 protected frequency diversity or for employing XPIC of MIMO features. For instance CFOL 5GHz MIMO product might be used with external dual-polarized antenna interconnected via 2 coaxial cables.
The choice of antenna type/vendor depends on frequency, SAF product type and planned link configuration. Most of the SAF products (in frequency range 5 up to 38GHz) require solid parabolic antennas, while 1.4GHz product CFIP Marathon requires grid antennas. Depending on planned configuration single or dual polarized parabolic antennas might be used for point-to-point microwave data transmission applications. It is important to consider the flanges on the antenna and SAF radios. The type of flanges should match, otherwise adapter or waveguide between the radio and antenna is required. Most of the SAF radios CFIP/CFM starting from 7GHz band have UBR type flanges. Specifically 6GHz band radios (CFIP and CFOL series) and also 1.4GHz CFIP Marathon have N-type connectors, while 24GHz band radios (CFIP series) have circular 10mm flange.
Some vendors provide SAF adapted antennas, so they can be connected directly to SAF radios. Another opportunity is to use waveguide (e.g. UBR-PBR) in between or a coaxial cable (for 6GHz CFIP/CFOL and 1.4GHz CFIP Marathon). Before choosing the vendor of antennas it is recommended to get in contact with SAF engineers in order to find out if particular antenna will be compatible with SAF product. Moreover it is recommended to use antennas that have adaptation to SAF products in order to avoid the use of adapters or waveguides.
A coupler is a passive device that couples signals from two ODUs into single waveguide output port. This will allow to connect two ODUs to a single antenna. Both ODUs will operate with the same polarization. Typically a single antenna with a coupler and two connected ODUs is used for 1+1 Hot Standby protection scheme (hardware protection), but it also can be applied to other setups.
An OMT (Orthomode transducer) combines both radio signal paths into single waveguide output port thus allowing to connect two ODUs to a single antenna. The signals are orthogonally polarized with respect to each other, meaning that both ODUs will operate with different polarizations. The insertion loss is insignificant, so the link budget is not affected. An OMT typically is used for 2+0 application, but also can be applied to other setups. NOTE! An OMT can be used for antenna sizes up to 1.2m.
Minimum required mast diameter for 0.3m up to 0.99m antennas is 40mm. Minimum required mast diameter for 1.2m antennas is 60mm.
SAF equipment has following type of waveguide flanges: UBR for ODUs and PBR for antennas. It is possible to connect SAF radio unit to a different vendor antenna, but in case of different antenna flange type, you most likely will need to install an adapter. Typically it is a flexible waveguide that has different type of flanges at both ends. Additionally you will require a separate ODU mast mounting bracket supplied by SAF, because SAF adapted antennas are slip-fit, meaning ODU is directly connected to antenna.
There is no restrictions painting the dish of antenna. It is painted with powder coating paint, so it is possible to do all you wish on top of that. For radome - film will be the best (such as Oracal, 3M, etc.), as radome is made of fairly slippery plastic and it is tricky to get good adhesion for paint over plastic. These films are available in any color and some of them guarantees outdoor performance. No penalty in radio signal propagation is expected. For 1.2m antennas and larger the same film probably is the best option, but it's trickier from mechanical perspective, as 1.2m and larger sized antennas radomes are flexible textile with rubbery plastic finish.
1+1 hot standby is considered as hardware protection only. One ODU transmits per site, the other is in standby mode. If main ODU operation is disturbed, the system will automatically switch over to alternate ODU and remain in operation.
1+1 protected frequency diversity protects hardware and also improves reliability against so called multipath fading phenomena. All ODUs operate at the same time but each ODU pair use separate frequencies. Hence having two frequency pairs, both frequencies are most likely NOT to simultaneously experience the same amount of destructive multipath from reflective atmospheric layers.
1+1 protected space diversity protects hardware and also gains improvement against multipath fading from reflective atmospheric layers AND ground reflections due to vertical spacing between receiving antennas. Space diversity typically is a "must" for very long and over-water paths where water covers significant part of the profile.
Of course, each link should be separately studied to identify the most appropriate configuration to apply.
Whether a SAF link will operate with good reliability over water is mainly depends on particular link profile and reflection geometry, which can be analyzed with the help of link planning software. In case the reflective point is located on the water and the surface is large enough to reflect a significant part of first fresnel zone hitting the receiving antenna, the link will periodically suffer from destructive interference. To counter performance degrade caused by reflections, 1+1 space diversity configuration can be used. Improvement is achieved due to two diversity paths not correlating with each other which means when one antenna experience outage, in the same time diversity antenna should receive maximum signal level.
It is possible some links will not experience reflection problems due to profile properties. Also, reflections can be minimized using such techniques as “shielding” or “Hi-Lo”. This is to say, some over water links can provide reliable operation without 1+1 diversity schemes. NOTE! Always use vertical polarization for over water links.
Recommended vertical spacing between the antennas is 7-14m. An optimal spacing is achieved if the antennas are spaced with at least 200 wavelengths. For example a wavelenght for 7GHz is 0.043m *200=8.6m. Microwave link case studies suggest a considerable diversity improvement is achievable even with 4m spacing.
There are no special requirements or distance restrictions between SAF radios and if necessary they can be installed side by side. However the operating radio frequency interference should be avoided between the units (frequency planning).
It is strongly recommended to install only same band radios in the same site ("L" with "L" band or "H" with "H" band) to avoid interference in between same site ODUs from the back of the antennas and to avoid overshoot interference at the remote sites. The best scenario is where links have a wide angle in between (close to 180°). In this case you can reuse the same frequency even in the same polarization. Usually antenna front-to-back ratio is sufficient enough to attenuate the interferer signal to a level at which it will not cause interference. In case where you have narrow angle between the "legs" (less than 60°) you can consider these links as very close or even parallel and the frequencies used for these links need to be different (adjacent channel). Also, different polarization implementation can be used to counter interference in such conditions. Enable ATPC (Automatic transmit power control) to decrease overshoot interference transmission during non-faded periods.
SAF Tehnika always recommend to use special ODU test suite consisting of waveguide to coaxial adapters (differing by frequency), attenuators and coaxial cable. However it is possible to interconnect ODUs installing 4-5 thick books between ODU waveguides to create additional attenuation, but this setup can not be used for performance measurements such as BER test. NOTE! Do not face powered-on ODUs towards each other without attenuation. You can irreversibly damage ODU internal components.
Link budget and performance quality does not depend only on Tx power. It depends also on other parameters like Rx sensitivity (Rx threshold level), antenna sizes etc. Link budget calculation softwares (SAF Pathcalculator, Pathloss etc.) uses following parameters for link budget and performance quality calculation: Tx power and Rx threshold values (System gain), antenna gains, additional losses (couplers, coax cables between ODUs and antennas etc), athmospheric attenuation. In result we can calculate link availability and link performance quality for planned link. Those results depend on all above mentioned parameters. Note that IF cable (connecting IDU and ODU) attenuation is not used for link budget and availability calculations as it does not carry RF signal.
Factory reset procedure affects IP address and the user login / passwords. To perform a power on reset:
1) Power on the CFIP PhoeniX M IDU.
2) During bootup, the CFIP PhoeniX M IDU will flash the controller card LED alternating red/green for five seconds. This LED is located on controlled card, on the left side from 2 x FE NMS ports.
3) Make sure the call button is not active at the start of this five second period.
While the LED is flashing, press the call button. Release the call button within one second after the LED stops flashing.
In this case please access management of CFIP Phoenix M via Serial management port (DB15 port on the front panel of IDU). When accessing Serial management please use the same username and password you are using for management web access. After successful login general device information will be indicated including current IP address. Also IP address can be changed via serial management if necessary.
SNR fluctuation could be due to several reasons: RF interference, IF interference, hardware fault – modem or ODU. You have to follow the next steps to find out the possible root cause of SNR fluctuation:
1) What is the range of fluctuation? If SNR fluctuation range is between 20 and 25.5 dB, then it is allowable and does not affect the traffic. If SNR during fluctuation is going below 19 dB, then please do next steps to find out the reason.
2) Hardware check – please perform built-in Loopbacks in order to check hardware. „Local modem loop” is for modem checking. „Local Radio loop” is for ODU checking. If SNR is stable during loopback action then particular part of equipment (modem or ODU) is working properly. You have to perform loopbacks on both ends of the link.
Interference check – 2 possible types of interference could cause SNR fluctuation – RF interference and IF (Intermediate Frequency) interference. To check RF interference possibility please temporary switch off remote ODU’s Tx power in order to monitor incoming Rx signal level in local end of the link. And vica versa if needed. Normally Rx level indication in CFIP PhoenixM equipment should be lower then -80 dBm if there is no incoming signal. Next option to check RF interference possibility is to change frequency channel temporary and check SNR behavior then. To check IF interference please find out if there are no any FM transmitters and VHF antennas working in 350 MHz or 140 MHz frequencies which could cause interference in IF (IDU-ODU) cable. Please shorten IF cable as short as possible. Please perform proper grounding of IDU, ODU and cable. If possible please try to use another type IF cable which is as short as possible and with different cable lying.
Firmware update for CFIP PhoeniX M equipment might be needed if there is any malfunction (firmware related issue or complaints about current firmware) of the equipment detected. In this case please contact SAF technical support team at firstname.lastname@example.org. Please provide detailed description of the issue, current firmware version and Serial numbers of devices. SAF technical support will analyze the issue and will provide you with further actions.
The SNR parameter corresponds to the measured signal to noise ratio by the digital demodulator/decoder. This is the signal power per bit divided by the noise in dB. The CFIP PhoeniX M IDU computes this based on the computed channel error rate. The CFIP PhoeniX M IDU's FEC decoder counts errors that it corrects, generating the channel error rate. Based on the channel error rate the CFIP PhoeniX M IDU computes the SNR, this is the theoretical SNR corresponding to the channel error rate.
If no errors are received during the measurement interval, the channel error rate is zero and the corresponding SNR is infinite. Therefore, the CFIP PhoeniX M IDU places a ceiling of 25.5 dB on the displayed SNR. This limit was chosen because it corresponds to error free performance for all modulation types.
Because the SNR computation includes effects of the channel, CFIP PhoeniX M ODU, and CFIP PhoeniX M IDU, such as phase noise and compression, for modulation types such as 128QAM, there may be an effective performance ceiling of 22-25 dB.
Therefore, even with very high RSL, the SNR displayed will not show as 25.5 dB.
Ports are not physically separated; they all are ports of single built-in switch. Two Ethernet channels are made using VLANs, internally. So, you shall not connect CFIP PhoeniX M split ports to single Ethernet segment or single switch, because then loop will be made. It means that two logically separated Ethernet channels of CFIP PhoeniX M can be used to connect two physically independent Ethernet segments only. There is an option to use router which has two interfaces between mentioned segments. Other option: to do traffic engineering outside CFIP PhoeniX M and make as much Ethernet channels as you need.
Here is a summary of maximum Layer2 frame sizes in various modules:
Standard Master I/O 2000 bytes
Enhanced Master I/O 1536 bytes
GigE Master I/O 4000 bytes
Enhanced GigE Master 4000 bytes
42 x E1 Master I/O 1536 bytes
* Enhanced GigE Master I/O comes with two options: Support for STM-1 Mux/Demux with 4000 Jumbo Packets or support for 9728 Jumbo Packets
Yes, CFIP PhoeniX M internal switch is transparent to QinQ VLANs.
Yes, Rapid Spanning-Tree Protocol and Multiple Spanning Tree Protocol is supported, as per IEEE 802.1D-2004 and IEEE 802.1Q-2005 respectively. The implemented RSTP protocol is backward compatible with non-Rapid STP.
Yes, the Management board can be hot-swapped. Traffic is not interrupted.
There is no specific limitation, however, only 1000Base-SX, 1000Base-LX, 1000Base-ZX, and 1000Base-T modules have been tested with the CFIP PhoeniX M. The following modules have been tested with the CFIP PhoeniX M:
• Avago AFBR-5715LZ
• Finisar FTLF8519P2BNL
• ZyXEL SFP-SX
- Avago AFCT-5715LZ:
• Finisar FTLF1319P1BTL
• ZyXEL SFP-LX-10
• Sumito SCP6F74-GL
- 1000Base-T (electrical):
• Avago ABCU-5710RZ
• Finisar FCLR-8521-3
The CFIP PhoeniX M will transparently forward BPDU frames when STP is disabled. When STP is enabled BPDU frames are forwarded to the CFIP PhoeniX M processor.
If the power is insufficient or it is close to maximum output value, it is possible that such issue occurs. Resolve the issue using IDU Web GUI: Go to Link Configuration -> Radio Link -> ODU Tx Mute Config. -> and select "Output remains the same" option. This will prevent ODU to stay in the "-3.8dBm" condition. Also, please check the power supply. It is required to provide at least 100W (-48V, ~2 Ampers) per IDU+ODU site.
Comments on comparative tests of the CFIP PhoeniX M 100 Mbps Ethernet link, performed by using software and hardware tools:
Test results show that it is unlikely to get actual (maximum) Ethernet throughput measurements using two computers and software. Both hardware testers measured full 100 Mbps Ethernet speed, but the maximum indicated speed from software testers was in range 90-95 Mbps. Iperf in default configuration (8KB window and one TCP/IP connection) measured only 52 Mbps throughput.
The main cause of the speed difference is that test software usually measures TCP/IP payload transfer speed, not raw Ethernet speed. It means that IP header and Ethernet frame headers are not taken in account! Example calculations:
1. Maximal 1518 byte raw packet rate over 100 Mbps Ethernet is 8127 packets/sec, bitrate is: 1518*8127*8 = 98694288 bps.
2. Ethernet payload bitrate excluding 14 byte MAC header and 4 byte CRC is: 1500*8127*8 = 97524000 bps.
3. TCP/IP (v4) payload transfer bitrate excluding 20 byte IP header is: 1480*8127*8 = 96223680 bps.
It means that 96.2 Mbps is theoretically maximal transfer rate using TCP/IP protocol and 1518 byte Ethernet frames under ideal conditions.
There are many other factors that can affect software test results, such as: packet size, latency of the Ethernet link, computer performance, network card performance, network card and operating system configuration, computer load, test connection count, TCP/IP transmission window size, test data buffer size, IP maximum transfer unit (MTU) size. In comparison, hardware Ethernet testers are built for this kind of tests and utilize FPGA as test engines that allows sending and receiving Ethernet test frames without any overhead, at full Ethernet speed and different frame sizes.
To correctly interpret test results of test software, good knowledge of tools itself and of TCP/IP protocol is needed. When using software for Ethernet testing, it is recommended to use increased TCP/IP window size (at least 64KB) and multiple connections. To get detailed information about Ethernet transfer rate, packet rate, latency, lost packets, FCS errors and more, there is no other way than to use dedicated Ethernet tester hardware.
At the moment there is no other solution than to use appropriate VLAN-capable 3rd party switches to separate VLANs, because CFIP PhoeniX M equipment is not able to tag packets.
Multiple Ethernet ports on CFIP PhoeniX M series indoor units are just for simple solutions, not requiring complex settings for each Ethernet port.
"Protected Diversity" mode is used for frequency diversity protection operation where both transmitters/receivers are always active as they use different frequencies. For Space Diversity setup please select the option "Protected Non-Diversity" as it is considered for Hot Standby and Space Diversity operation as well. After configuration more switch options will be available in Radio Link -> Protection Switch.
CFIP PhoeniX maximum packet size supported is 9728 bytes. Latency over 366Mbps link is 90..160 microseconds (0.09 .. 0.16 ms) depending on packet size.
Unfortunately, it is not possible to calculate bit errors if contents of bit stream is unknown - we do not know contents of data transmitted over E1 or Ethernet we are receiving, thus cannot know if bit is corrupted or not.
On other hand, CFIP PhoeniX has very strong Forward Error Correction mechanism built-in: LDPC, which is explained in detail in the CFIP PhoeniX user manual.
The distance strongly depends on environmental and terrain conditions. As there is EIRP limitation in license-free frequency bands (17/24GHz), the distance is limited and in particular example below cannot exceed 6km (FreeMile operates at full-rate and max antenna size 0.99m).
* Results are obtained using ITU Rain zone G=30mm/h. The errorless ACM feature will automatically switch to lower modulation during strong rain fading moments.
FreeMile 17GHz and 24GHz band radios utilize both polarizations for duplex transmission, therefore radio should be installed with 90 degrees offset regarding remote side of the link. Refer to the figure below for polarization indication that you can see in Web GUI and on the face of the unit.
SAF Tehnika always recommends to use special SAF FreeMile FODU test suite. However it is possible to interconnect radios installing few books between FreeMile waveguides to create additional attenuation, but this setup can not be used for performance measurements such as BER test.
NOTE! Do not face powered-on radios towards each other without attenuation. You can irreversibly damage FODU internal components.
SAF FreeMile is not IEEE 802.3af/at-compliant. However there is a chance to power-up SAF FreeMile from 802.3af/at switch, if it has the ability to configure appropriate ports to give sufficient amount of output power regardless the connected devices’ 802.3af/at-compliance. For instance some Cisco PoE switches support ‘static’ PoE configuration of the port. In this mode switch pre-allocates configured maximum wattage to the port even when no powered device is connected. Need to keep in mind that FreeMile power consumption is up to 15W, while 802.3af standard provides up to 15.4W (some power will be dissipated in the cable). So, you have to assure sufficient amount of input power to FreeMile unit.
Note that SAF FreeMile supports only Mode B PoE pinout (power on spare wire pairs).
The supported round pole diameter is between 50mm and 120mm. Please refer to the drawing below.