Here, Chuck. I did something I didn't want to do.. mess with the network
on a Friday!
I put a spare Netgear switch using the two GigE uplink ports between the
AF5 master and the MT CCR at the NOC. FCS errors on the switch port that
the radio is plugged into now (port 25). It's not MikroTik, NO FCS
errors on the port uplinked to the CCR (port 26).
I have to go put everything back the way it was now.
On 11/7/2014 4:40 PM, George Skorup (Cyber Broadcasting) via Af wrote:
You lost me. Length? I just tried it with a 50' patch cable going into
the building wiring that's probably another 80+ feet. I tried both
10/100 and GigE ports on the switches. And it linked up to the CCR at
1Gb. I ran the discovery tool. I ran some pings to various stuff (from
the radio CLI). It did not trigger any FCS errors, not even on the MT
CCR. But like I said, there was no RF link up, so the "RF switch port"
wasn't active?
On 11/7/2014 4:29 PM, Chuck Macenski via Af wrote:
The cabling may play a role...
On Fri, Nov 7, 2014 at 3:54 PM, George Skorup (Cyber Broadcasting)
via Af <[email protected] <mailto:[email protected]>> wrote:
Well, I can't get it to happen on either the Zyxel or Netgear
managed switches I have. Nor on the MT CCR running in the server
room right now (which has two AF24's and one AF5 links running
live on it and the errors appear here and at the routers on the
other ends).
BUT.. this is a single spare unit running on the bench, no RF
link up. Which I have no way around because, 1) I don't have
another unit, and 2) it's indoors and AF24's no likey that anyway.
On 11/7/2014 2:10 PM, Chuck Macenski via Af wrote:
If you run into any issues, hit me ( [email protected]
<mailto:[email protected]> ) and we will figure it out.
Chuck
On Fri, Nov 7, 2014 at 12:34 PM, George Skorup (Cyber
Broadcasting) via Af <[email protected] <mailto:[email protected]>> wrote:
FWIW, the AF firmware has been pretty stable, even betas. I
had to run 2.2-beta3 on the AF5s since it has DFS/RADAR
improvements. I've had a 3.4 mile link up running DFS band
for a couple weeks and it has been pretty stable pushing
about 100Mbps. I would kill for a 5.1-5.3GHz AF5.
Anyway... since Chuck seems to think it's MikroTik, I will
pull out a spare AF24 and see if I get errors on either of
my two managed switches in the office.
On 11/7/2014 11:05 AM, Bill Prince via Af wrote:
I wouldn't call it "issues", as I almost never do the
Tools->Discovery. I only went through that process after I
read this from George.
The interface FCS error counter is zero (or near zero), and
each time I did Tools->Discovery, the FCS counter would
increment by between 5 and 15. Our AF24s are otherwise
working fine.
We upgraded to 1.5 to get SNMP, and haven't had the need to
upgrade beyond that. George tends to operate a bit closer
to the bleeding edge than I'm comfortable with.
bp
<part-15@SkylineBroadbandService>
On 11/7/2014 8:44 AM, Chuck Macenski via Af wrote:
You also have issues when connected to Microtik?
On Fri, Nov 7, 2014 at 9:58 AM, Bill Prince via Af
<[email protected] <mailto:[email protected]>> wrote:
Same thing happens on version 1.5.
bp
On 11/6/2014 2:59 PM, George Skorup (Cyber
Broadcasting) via Af wrote:
Found this interesting. I have some AF24's on 2.0
and AF5's on 2.2-beta3. They work fine. If I do a
Tools > Discovery, the MT ethernet counters on
both sides will increment FCS and Code errors.
Same thing happens if I run some pings between the
radios (not router to router, radio to radio). I'm
guessing this because of the switching method the
AF's use (cut-through?).
