Port Errors

[sirhc]

This will be an "easy" diagnostic since port 1 and 2 both have the same equipment just swap ports and see if the errors follow the radio/cable but be sure to swap the jumpers and all if any.

ALWAYS TURN POE OFF before unplugging and plugging in then turn the POE back on.

I am concerned with the power draw on port 4 - Too HIGH for a standard 24V/48V port.

Your cable diagnostics shows different lengths in your pairs which indicates your cable was stretched and or kinked during installation or you have a bad jumper.

Swap AF1 with AF2 in the ports and see if the errors follow the radios and cables.

Also run the cable diagnostic on the other AF link.

REMEMBER TO TURN POE OFF IN THE SWTCH FIRST, NEVER UNPLUG AND PLUG LIKE POE ESPECIALLY 24VH and 48VH

Here is 1 of my diagnostics of 1 of around 20 AF links on my Towers:
CLICK IMAGE BELOW TO SEE FULL SIZE

qr.jpg (335.03 KiB) Viewed 15507 times

[TheHox]

The AF5 port does all match. The port that shows different lengths is the port4 which is the RocketM5. I've noticed it showing different lengths if the ends are not good.

[sirhc]

The AF5 port does all match. The port that shows different lengths is the port4 which is the RocketM5. I've noticed it showing different lengths if the ends are not good.

Ah then 15 watts is a peak, OK

But still 15 watt peak is still high for an airMAX Rocket, could be cable or ends but your average current graphs look fine for that port.
I see short 12 watts peaks on mine

[sirhc]

I have not yet, I'll make a drive there maybe early in the morning and try that.

Awesome, let us know!

[sirhc]

Here is one of my AF port details

hc.jpg (355.76 KiB) Viewed 15500 times

[TheHox]

I ended up using another switch I had laying around as I had to rework some wiring etc.

I have the port layout the same as before, but an entirely new switch. 3.5hr uptime and about 328 errors already.

[sirhc]

I ended up using another switch I had laying around as I had to rework some wiring etc.

I have the port layout the same as before, but an entirely new switch. 3.5hr uptime and about 328 errors already.

Not sure what you're saying?
The new switch is our switch or another manufacturer?
I thought we left it that you were going to swap port 1 with port 2 and see if the errors followed the radio/cabling?

Anyway PLEASE upgrade that firmware - v1.0.10 is OLD firmware - use version 1.1.3

[wayneorack]

From the pics, it looks like he installed another WS-12-250B and still got errors.

Looks like it is time to replace the cable / connectors.

[sirhc]

From the pics, it looks like he installed another WS-12-250B and still got errors.

Looks like it is time to replace the cable / connectors.

I would agree, I was hoping he swapped port 1 with port 2 and the errors followed the link/cable which would point a very definite finger.

But too many people use these switches to power airFIBER with no problems (including me) so it has to be the cabling you would think as there are over 1,000 WISP Switches out there.

I have fielded about 6 calls on errors powering 1G devices like airFIBER and every single one resolved itself with a new cable run.

Currently I have 2 open instances of this including this one, did not hear back from the other guy today so maybe it is closed?

[TheHox]

I had to re organize the rack and moved the UPS around so I had another WISP switch (yea old firmware) I threw in.
I redid the config the same, but errors continue on brand new switch. So, it is not the switch itself.

I've changed ends, but I can do that again, or change the wire I suppose.

I was just asking if port error strictly means that there is a physical problem, such as wire/ends/radio/port, and not anything like MTU like that.

I have 4 other AFs on my network too, all with ZERO errors, all on WS's. It is just this one that is giving me problems.