v1.5.21 Bug Reports and Comments

[sirhc]

Just making sure that what you wrote also applies to Voltage graphs .

Should, YES

[sirhc]

So the following are FIXED for v1.5.22 - to be released SOON

SMTP sender - FIXED

DHCP - FIXED


{switch-name}# web_conf_check - FIXED

sh: php-cli: not found

Graph anomalies
- IN PROCESS

I Still say those with issues with PPPoE are related to MTU settings either the value on our switch or a device between the customer and the point of destination/termination of PPPoE. AND DON'T FORGET THE CUSTOMER RADIO!!!

[Flo]

So the following are FIXED for v1.5.22 - to be released SOON
...
I Still say those with issues with PPPoE are related to MTU settings either the value on our switch or a device between the customer and the point of destination/termination of PPPoE. AND DON'T FORGET THE CUSTOMER RADIO!!!

For sure, that's not the case, as PPPoE discovery packets are filtered on SFP uplink ports on v1.5.21.
These packets are well under the default port MTU of 1528.

Tried it with two different SFP module brands: One FS.com, the other one has been a HPE.

The error has occurred on two different locations using SFP uplink ports after upgrading to v1.5.21 and resolved after downgrading to v1.5.16.
SFP ports are running with default settings.

I will investigate in this issue once again on Friday or next week if the shipment with different SFP module brands arrive in time here.

[sirhc]

@Mayheart

You say PPPoE is working for you, by chance are SFP ports involved?

If SFP ports are used are these mono fiber or dual fiber SFP modules?
NOTE: We are working on an issue with mono SFP module and have ordered the same equipment the customer has.
He is running a mono fiber module to a UBNT media converter then handing off copper to his customer.

If SFP modules what brand and model # please.

[Flo]

I ran into an issue with upgrading from 1.5.14 to 1.5.21, username/password did not get reset for the webui. I was unable to login using the old login/password or admin/admin. SSH was fine though.

After using credentials commands in SSH it fixed its self. I did make a backup of the config before and after the password change.

As for PPPoE, it seems to be working fine for me but I have my ports set to 9000 MTU. I use mostly FS.COM Cisco branded SFPs.

That's interesting. We also use FS.com SFPs but it does not work after upgrading to v1.5.21. PPPoE servers are MikroTik CCRs 2xxx.
Tried both: Standard MTU 1528 and increasing the MTU to 1556. My guess is that the MTU setting only gets pushed to the SFP module after a hard reset (unplug / re-insert).

I have ordered a few other SFP modules from the compatible list and will give it a retry the next days.

I did some bench testing here with a SFP, set the port to 1528. PPPoE worked, was fine after a hard power cycle as well.

The only difference is we're using Cisco ASR9000s configured as a BNG.

That's interesting. Did you have the Cisco ASR9000 connected via fiber on the SFP port?

[mayheart]

Hello,

Yes, the PPPoE uplink traffic is coming from the SFP port.

We ran fiber to another tower yesterday and I just migrated PPPoE clients over it last night. Running 1.5.21 here.

It's BiDi optic, model 1000BASE-BX-U https://www.fs.com/products/11802.html.

My toplogy here is as follows.

Netonix -> 1G fiber optic -> Cisco NCS-540 -> L2VPN (carrying PPPoE VLAN over MPLS network) -> Cisco 9000

[sirhc]

Plan is v1.5.22 to be released tonight or tomorrow for those interested.

Mono fiber SFP wont look at till next week when we get equipment but some claim they work for them?

PPPoE as far as we are concerned for now is being worked on among users and us on the forums.

BUT other than (PPPoE debate) and mono fiber we feel we nailed every request pretty quick.

OUCH, I think I dislocated my shoulder from line above.

[Stephen]

1.5.22 is now available

Please read release-notes, but among fixes:
-DHCP
-SMTP
-web conf utility
- Status graphs (for port throughput, something we found on our own while checking voltage graphs)
- Smart dc voltage graphs

For the voltage graphs specifically, please let us know if you still see these spikes or not. We tested ourselves for about 24 hours and saw them disappear. Whereas previously I would see about 2 spikes on a 24V linear supply approximately once every 6 hours.
This was due to a type of memory corruption that should now be fixed, but may find it's way in in other ways depending on network setup and configuration. So please let us know on the new thread if you see any difference, hopefully they are just gone and you can all reliably use the graphs as you need.

Like normal, this thread will be locked and conversation's can be continued here:
viewtopic.php?f=17&t=8132&p=39116#p39116

and of course you can download 1.5.22 here:
viewtopic.php?f=17&t=240