Traffic Issues

Go through below checklist to troubleshoot your installation.

The link is facing a lot of packet drops, what can we check first?

The frequency configuration should be checked.

The used frequency should be within the radio frequency range and respect the channel spacing.

For example if the bandwidth is 56 Mhz, the last frequency used should be the radio max frequency – 56.

The radio frequency range can be viewed from the product information.

Ethernet 4 on the S10 is connected to the Traffic loader. Ethernet 3 on the S10 is connected to a Switch for management. The traffic sent to the S10 is being broadcasted on all the switch ports.

The traffic loader should not be connected to a management port in order to avoid a broadcast of the data.

Accordingly, the switch should be connected to Eth 4 for management.

The traffic loader should be connected to Eth 3 where the management option for this port is disabled.

How can we have traffic aggregation?

In order to have aggregation, an external switch is needed.

At both nodes, it happened three times, that the units were not pingable (no management access) when sending traffic, and after rebooting they were normally accessible but the traffic was always passing. The sent traffic is on VLAN 4 and the used configuration is out-of-band.

The used VLAN configuration is out-of-band and the traffic being sent is on VLAN 4.

In order to manage the S10s and send traffic on VLAN4, the VLAN template should be changed to IEEE802.1Q where we have the Management on VLAN1 and the Payload on VLAN4.

Trunk traffic is not being successfully sent using the trunk interconnect configuration

Make sure that the two S10s don’t have the same IP address.

Eth1 is connected to a switch. By checking the counters of ETH1, we can see some Rx errors but with no drops. The cable connecting the S10 to the switch was replaced but the same issue still exists. The switch was connected to Eth2, 3 and 4 and still the same issue occurred. There are no errors on the modem and radio counters. This is not affecting the link performance.

The RX Errors counter is a cumulative counter.

It includes not only errors but also warning on the packet structure.

The S10 is very intelligent with regards to errors and provides a deep analysis on the packets.

These can be considered as warnings rather than real errors bearing in mind that the packets will NOT be dropped.