Netonix Forums

I have a site that is fed with a M5 400 link and is working 100%, this site has a WS-12-250-DC
Switch powering everything and there are no issues apart that I'm getting close to the max I can pull over the link and need to upgrade the backhaul.

Today we installed a AirFibre24 link between the 2 sites and powered on end of the link with the WS-12-250-DC
. The AF24 link came up and was passing traffic but I could not log into the WS-12-250-DC
switch from my office (the otherside of the AF24 link). I could ping the switch but could not open the GUI.

I thought it might be a MTU issue and changed the MTU on the switch from 1528 to 9000 but it made no diffrence. I could log into all the devices powered by the WS-12-250-DC
switch but not the switch it's self, have you any suggestions as to what silly mistake I'm making?

There could be a million reasons why, need more information.

What firmware version are you using?
You can PING the switch, could you SSH into the switch?

Firmware Version 1.4.6

I did't try to ssh into the switch but yes I can ping it, I can loginto all the UBNT devices that the switch is powering and to anything connected to them, its just the switch I can't log into.


I have put it all back the way it was, getting its feed from the M5 unit so can't test it any more but until I go back to the site. I just thought I must be missing something as now its getting its feed from the M5 I can log into it again without any problem.

Post up your Config Tabs and explain what is/was on each port.

Your backhaul was the M5 and you added or replaced it with an AF24?

If you added the AF24 then how were you dealing with the possible loop?
1) RSTP
2) Disabled the M5 Link
3) Something else

When I used the AF24 I removed the M5 link.

The config has now changed as when I was running ther AF24 from it I made some changes as listed below.


Changed Port 1 from 24V POE to 48v POE
Changed MTU on port 1 from 1528 to 9000


This has since been changed back to allow putting back the M5 link.

Setting on the switch is simple setup from new, just changed IPv4, password, set NTP, Storm Control is off, Set SNMP Server setting and turned on POE on all the ports. This is the same on all your switches. We have never run your switches to power an AF24 before so have never seen this issue.

therealboss wrote:When I used the AF24 I removed the M5 link.

The config has now changed as when I was running ther AF24 from it I made some changes as listed below.


Changed Port 1 from 24V POE to 48v POE
Changed MTU on port 1 from 1528 to 9000

This has since been changed back to allow putting back the M5 link.

Setting on the switch is simple setup from new, just changed IPv4, password, set NTP, Storm Control is off, Set SNMP Server setting and turned on POE on all the ports. This is the same on all your switches. We have never run your switches to power an AF24 before so have never seen this issue.

Please tell me that that was a type O and you meant to say you changed it from 24V to 48VH as AF radios use 48VH not 48V

Using 48V to power an AF24 or AF5 radio can damage the radio and the port, please review these threads:
viewtopic.php?f=6&t=1215
viewtopic.php?f=6&t=1178

I do not think MTU was the issue as you should not be running jumbo frames on an internet backbone, especially a wireless backbone.

I use a lot of AF24 radios in my network with no issues at all.

Do you have any VLANs defined, if so please post up a picture of that Tab.

Please post up screen grabs of your Status and Device/Configuration Tabs as well

To upload pictures to your post use the Upload attachment link below the blue submit botton

Yes 48VH


No VLAN's on this link

A few more screen shots

LOL, OK a straight default config

But you forgot the device config file.

No idea in hell why you had issues, makes no sense that you would???

When and if this happens again see if you can SSH into the switch.

Let us know when you try again if you have an issue.

I had this issue just the other day. It was a web browser cache issue. Using a different browser or "private" mode and the UI came up fine.