Power error logging/ Latency Issues

[RelayBuff]

Reply by sirhc in regards to power logs making error to switch 738 indicating range errors to 3v and 24v

sirhc replied is an internal code to the programmer.

Upgrade to v1.4.7rc11 and see if those errors stop. When you have a problem always upgrade firmware first and see if problem goes away, if not then make a post in the forums.

If upgrading the firmware does not stop these errors or you ever notice the unit reboot for no reason then you will need to RMA it.

it appears the firmware upgrade and a reboot did resolve the power logging issue as far as i can tell.

--Type : Netonix
--Model: WS-6-MINI v1.4.7rc11

[RelayBuff]

However still having latency issues. further investigation
it appears the Netonix is generating a 15k outbound packet count on our uplink port, the port is connected to a PBM5, we've checked all of the other ports and inbound total the packet counts never go above 2k but the out bound on the uplink port is spiking to 15k and 20k every 5 to 10 seconds, inbound on that interface looks normal with counts averaging 500 to 1.5k, we see a direct correlation between the packet count and our available through put, we normally get 40M down except when the packet count shoots up then we only get 20-25M down
also, sometimes the packet count stays sustained at 15k for several minutes at a time, we tried disabling all the services within the Netonix and the traffic was still there.

[sirhc]

It is good to post screen grabs of all your Tabs, Status, Ports, Device/Configuration, Device/Status and any other Tab with changes from default.

Look at port details and see if they are Pause Frames.

Try disabling Flow control on all ports. There are known issues with some wireless gear with Flow Control issues such as UBNT airMAX AC radios and all airFIBER radios.

So if your running a large flat network and a backhaul radio is sending too many packets to another radio that is sending Pase Frames it will cause Tx Pause Frames to be sent out the port that the packet are coming in towards the bottle next radio.


My guess is your packets in question are Tx Pause Frames being sent out of the switch on your uplink port because the destination port is backed up because that radio is sending Tx Pause Frames to the switch which will see them as Rx Pause Frames on that switch port.

If you are running a large flat network segment you need to disable Flow Control as too many wireless devices do not handle Flow Control Pause Frames in a manor that works with a wireless bridge that is less capacity than the Ethernet link speed.

If it is Pause Frames do some searching and reading on our forum and UBNT Forum for posts like this:
viewtopic.php?f=17&t=2375&p=17116&hilit=+UBNT+Pause+Frame#p17116