v1.5.22 Bug Reports and Comments

[josh@belwave.com]

We are still struggling with the issue having all PPPoE discovery packets (MAC protocol: 8863) being filtered on SFP ports.

I did some more debugging with the following findings on Friday:
- PPPoE client PADI packets send out the network are no longer received from PPPoE server
- changing SFP module brand does not resolve this issue
- unplug / re-plug SFP modules does not resolve this issue
- soft-reboot WS-250-AC does not resolve this issue
- hard-reboot WS-250-AC does not resolve this issue
- increasing the port MTU from 1528 to 1556 does not resolve this issue
- disable "Storm Control": Broadcast, Multicast, Unicast filters to "None" does not resolve this issue
- disable Discovery protocols does not resolve this issue

Downgrading to v1.5.16 does immediately resolve the issue.

If you have PPPoE discovery working on latest v1.5.22 via SFP links please share details on your setup.

Sounds like in my troubleshooting its related to the SFP, is there an option for you to use ethernet directly to the switch and see if the issue goes away?

[sirhc]

Sounds like in my troubleshooting its related to the SFP, is there an option for you to use ethernet directly to the switch and see if the issue goes away?

I doubt there is an issue with all SFP modules, but I am sure a few. But that is a good idea to debug, bypass SFP for test.

Obviously, Cisco Brand I have never seen issue but $$$

I have had decent luck with these

AMAZON:
10Gtek 10/100/1000Base-T Copper SFP, Auto-Negotiation SFP to RJ45 Mini-GBIC Transceiver for Cisco GLC-T/SFP-GE-T, Pack of 10
Visit the 10Gtek Store
$160.00 $160.00 $16.00 per Count ($16.00 / Count)

10Gtek SFP to RJ45 1000BASE-T Copper Ethernet Module, Gigabit SFP-T Transceiver for Cisco SFP-GE-T, Meraki, Fortinet, Ubiquiti UniFi UF-RJ45-1G, D-Link, Supermicro, Netgear, TP-Link, Pack of 10
$150.00 $15.00 per Count ($15.00 / Count)

I prefer the 10/100/1000.
MOST all work fine, but I have had a "few" that did not work properly so I used in other devices.

Biggest issue was with the few that did not work properly was they did not come back after upgrade or warm boot.

Again, also test disable save apply enable save apply on ports tab, if you see any issue don't use.

Now if this SFP port is fiber and possibly MONO fiber that is another issue we are looking at. Some report work fine, one reports not. We ordered duplicate equipment to test next week. Read up this thread for better info.

[sirhc]

At my WISP I run OSPF ring with BGP at edge with Lumen.

RF Armor warehouse is 4 towers deep into the ring to an original 120 sector with an ORIGINAL RF Armor with a Rocket AC Lite (to fit in old shield kit box) shared with 15 clients then 2.61 miles to a PowerBeam 5AC 400 with RF Armor. But not PPPoE. We run a router and Netonix switch at each tower. Each switch port is a VLAN to a virtual port in router. Each client is a /32 subnet. Residential client radios are in NAT no client access, commercial are either NAT or bridged to their router with possibly a larger subnet if requested. We static assign all IP's which makes FBI or law enforcement requests easier as clients always have same address.

This Spring I plan to upgrade all OLD original RF Armor kits to upgrade to newest Rocket as antennas all look almost new as they are protected with the shield. All my antennas have been in service for 16 years. I even have 2 towers still running original rocket M5s which stil llook like new as they have been protected from sun and weather but they are lightly loaded towers but will upgrade them this spring. I played with the horns but for my setup I prefer the 120 degree sectors as most of my clients are 4 miles or less. I usually run 3 to 4 120 degrees at higher EIRP and 3 to 4 sectors on DFS for close in customers. This also usually gives me multiple sectors to choose from when hooking up a new client or load balancing.

GUESS IM OLD SCHOOL BUT IF IT AN'T BROKE WHY FIX IT.

I always run constant pings to 8.8.8.8. Today I missed 1 out of 545 pings.

I have seen better speeds, but this is about average. Keep in mind I have a residential service here at RF Armor not a commercial account.

Also keep in mind there are several security cameras here running back to WISP office and about 8 computers here and a TV in the lunchroom that is always on streaming Newsmax.

[mayheart]

By "mono" do you mean bi-directional?

We use a mixture of both. bidi to anything out in the field and use duplex in the data centre.

All optics we use are FS.COM with Cisco compatiable profile. There was one odd ball tower that I recently upgraded to 1.5.22 uses "D-Link DEM 310-GT" This one also appears to pass PPPoE and other routing protocols fine.

Note I am hard coded at 1G at these sites, for some reason Cisco XE/IOS is fine with running optics on auto. Anything XR based must manually set duplex/speed if operating at 1G or lower.

[sirhc]

By "mono" do you mean bi-directional?

We use a mixture of both. bidi to anything out in the field and use duplex in the data centre.

All optics we use are FS.COM with Cisco compatiable profile. There was one odd ball tower that I recently upgraded to 1.5.22 uses "D-Link DEM 310-GT" This one also appears to pass PPPoE and other routing protocols fine.

Note I am hard coded at 1G at these sites, for some reason Cisco XE/IOS is fine with running optics on auto. Anything XR based must manually set duplex/speed if operating at 1G or lower.

Yea I call mono when a single fiber optic cable is used for bi-directional communications instead of 1 for Tx and one for Rx.

[oeyre]

We have some ~150 odd devices that we're planning to upgrade to 1.5.22 soon. Most of our customers use PPPoE, although we don't have alot of units that use SFP. I will keep an eye out if there are any issues with those.

Speaking of SFP, is there a way to look at the SFP information/stats?

[sirhc]

Speaking of SFP, is there a way to look at the SFP information/stats?

The switch gives the same stats as copper ports.

With v1.5.22 there are very few SFP modules that will have issues.

If your asking about getting stats from an SFP control module or the SFP PHY then no, that is not available in any device that I know of?

The Status Tab will show errors, CRCs, same as copper ports.

Once upgraded to v1.5.22 SFPs are not an issue with 99% of SFPs that are Cisco compatible. If you read up this thread I detail how to test an SFP to insure you won't ever have issues with it before putting into service.

I use (2) SFP modules in all my switches and they are used for the main back hauls in and out of tower.

Read this thread. viewtopic.php?f=30&t=452#p2961

[bipbaep]

WS-12-400-AC had about 15 minutes of uptime, no SNMP activated. Booted fine after upgrade, but did not respond to ping/management.
Checked config via serial, all OK. Tried to reboot 3 times with the same result. Factory default got it to answer from 192.168.1.20.

WS-12-250-AC uptime about 1 month, SNMP activated, memory usage about 38MB. Is beeing checked on-site today. Have a feeling that the same thing happened there.

None of this use SFP modules.

We use SNMP on all our switches, and we have NEVER had this problem when upgrading, just to state that.

[IntL-Daniel]

There is still bug in SMTP but different one... curretnly it uses field "From Address" in "helo" command and the reply from SMTP is then

[<-] 501 5.5.4 Invalid domain name

...because it expects some FQDN domain, not an "email" format. Previously you ignored this field and used name "localhost" and then the same as "Mail From:" command and that was a bug. So the solution is to use "helo" only and nothing else (or the Local Host Name field) and "Form Address" field use in "Mail From:" command only. Thanks for fix.

[Flo]

We are still struggling with the issue having all PPPoE discovery packets (MAC protocol: 8863) being filtered on SFP ports.
...
Downgrading to v1.5.16 does immediately resolve the issue.

If you have PPPoE discovery working on latest v1.5.22 via SFP links please share details on your setup.

Sounds like in my troubleshooting its related to the SFP, is there an option for you to use ethernet directly to the switch and see if the issue goes away?

On the affected devices we are bound to using the SFP port to use fiber which interconnects the buildings in a campus.
Hint: The PPPoE discovery (protocol PADI packet filtered) issue does not occur using the latest firmware, if you are using the Ethernet ports, only.

For further debugging I am going to setup the same scenario with spare WS-250-AC switches in our lab the next days.

@sirhc: Is it possible for you to provide a v1.5.22-dev firmware containing the old, original SFP port code?
Using the SFP modules from the compatible list, we have not had any issues with SFP fiber connections using versions up to v1.5.16.