Netonix Forums

Should the Af5x be set to 48v?
Is it normal to be jumping from 8w to 12w? can stick at 12.4w for 6/8 seconds, wondering if this is ok

Master side port 9 is powering the Af5X
The slave side is port 5 powering the Af5x and i am also getting a pause rate and bridge?
Also flowcontrol is off on every device, switches setup as default only enabled PoE nothing fancy

So we have posts for questions like this: https://forum.netonix.com/viewtopic.php?f=6&t=1215#p9040


READ THE POST ABOVE BUT UNLESS YOU HAVE ONE OF THE ORIGINAL FEW AF5X I WOULD POWER IT WITH 48VH

There is an ADVANCED search by clicking on the magnifying glass in the search box.

Thanks i will check the model.
I check back maybe once a year trying to find my issue.
I dont think changing the voltage will fix the main issue but i will try if i have a later model AF5X

First day I bought the switch i had an issue.
viewtopic.php?f=17&t=1946&p=14359#p14359
I thought is was becuase of scanning with Aircontrol in the end it was not the case.

This is a later issue, and I completly forgot about the issues a few years ago.
viewtopic.php?f=17&t=5332&p=29028#p29028

I have changed ports, updated firmware, changed connections, changed cable, paid an electriction to check eltric socket grounding.
Older firmware no lockups new firmware lockups.

The first issue was becuase I had my Pc connected to the Switch so when turning the PC on off It would trigger all the ports to have a link change.
I forgot about this issue becuse since then i connected the Pc direct to my Mikrotik, but when cleaning out the rack i bumped one of the cables and it gave the same result.

Does this mean my switch has always been dodgy since I bought it, touching or disconnecting a cable seems to change many ports to change link state to up and down?
I know its been about 3 years becuase i never touch the cables I forgot about the problem, just would like to know why it happens

I am also seeing this often from the AF5X

No, the link state change is due to RSTP, possibly the fact that vtss which is a service we have running is reloading which was for the most part corrected in v1.5.2.

If you like DISABLE STP/RSTP.

What is forcing all the ports to change is either a RSTP root issue or your using older than v1.5.2 or v1.5.3rcX as there was an issue in v1.5.1 which was removed from service.