v1.4.2 Bug Reports and Comments

[sirhc]

Well your silly to not upgrade to v1.4.2

I am about to release v1.4.3rc3 later tonight after I finish some more testing.

The question you need to ask yourself is are you seeing this with any other ports/VLANs that are the same setup but not the same type of radio?

[givemesam]

I thought we were on 1.4.2
didnt realize rc6 was not the final. its hard to keep track of what is the latest RC vs production version

should i wait for the new RC? how do i know when its ready?

===
as for the issue, 1Fiber<2Netonix><3Metrolinq><4metrolinq><5netonixs><6Many other radios>
the issue happens at point 5 in the chain above. So we dont get any data past the slave radio of the metrolinq. the metrolinq is the feed radio to this switch. I am assuming its VLANs, but it could also be the netonix is blocking ALL traffic at the switchport, hence why i can still get to the Metrolinq slave side.

[sirhc]

I thought we were on 1.4.2
didnt realize rc6 was not the final. its hard to keep track of what is the latest RC vs production version

should i wait for the new RC? how do i know when its ready?

===
as for the issue, 1Fiber<2Netonix><3Metrolinq><4metrolinq><5netonixs><6Many other radios>
the issue happens at point 5 in the chain above. So we dont get any data past the slave radio of the metrolinq. the metrolinq is the feed radio to this switch. I am assuming its VLANs, but it could also be the netonix is blocking ALL traffic at the switchport, hence why i can still get to the Metrolinq slave side.

We are on v1.4.2

v1.4.2rc6 is v1.4.2 Release Candidate 6 "rc" stands for Release Candidate.

Where does your chart indicate which side is slave and master of Metrolinq?
1Fiber<2Netonix><3Metrolinq><4metrolinq><5netonixs><6Many other radios>

I doubt your issue is the switch from your description of intermittent fails.

Also have no idea of your real configuration as there is a lot lacking in your diagram.
Where is your router?
What is your router?
How are your VLANs setup?
Much details missing.

[lligetfa]

I thought we were on 1.4.2
didnt realize rc6 was not the final. its hard to keep track of what is the latest RC vs production version...

We are on v1.4.2

v1.4.2rc6 is v1.4.2 Release Candidate 6 "rc" stands for Release Candidate...

Is there any change between RC6 and stable? If there is, then should there not have been an RC7?

[givemesam]

I understand rc6 was a release candidate. I wasnt aware there was a final release. Was looking for an RC7. My bad.

Isp<0Mikrotik ccr 1036><1Fiber><2Netonix><3Metrolinq-master><4metrolinq-slave><5netonixs><6Many other radios>

Vlan routing is happening at head router ccr. Vlans Packets are tagged on downstream switches after the Netonix. Netonix is trunking vlans 1-100 on all ports.

Let me know if I need to provide any more info.

How can I get alerted of a new RC?

Do I need to disable the discovery tab to make sure I avoid any stp to ensure its not the switch? We have no loops at this time.

[sirhc]

I thought we were on 1.4.2
didnt realize rc6 was not the final. its hard to keep track of what is the latest RC vs production version...

We are on v1.4.2

v1.4.2rc6 is v1.4.2 Release Candidate 6 "rc" stands for Release Candidate...

Is there any change between RC6 and stable? If there is, then should there not have been an RC7?

There were some changes between rc6 and FINAL (fixes for things reported wrong in rc6)
They were minor fixes that really did not need tested but yes there are differences.

As I said during the last rc versions of v1.4.2 when asking for people to test v1.4.2rcX we NEEDED v1.4.2 finalized before we could produce anymore switches as v1.4.2 was a requirement of Rev F boards and the NEW models but most people said they were unwilling to put rc versions on production switches to test.

Since your not v1.4.2 final and one difference between rc6 and final was a fix on the Discovery tab yes it could affect RSTP.

Just upgrade the firmware to v1.4.2.

[sirhc]

I understand rc6 was a release candidate. I wasnt aware there was a final release. Was looking for an RC7. My bad.

Isp<0Mikrotik ccr 1036><1Fiber><2Netonix><3Metrolinq-master><4metrolinq-slave><5netonixs><6Many other radios>

Vlan routing is happening at head router ccr. Vlans Packets are tagged on downstream switches after the Netonix. Netonix is trunking vlans 1-100 on all ports.

Let me know if I need to provide any more info.

How can I get alerted of a new RC?

Do I need to disable the discovery tab to make sure I avoid any stp to ensure its not the switch? We have no loops at this time.

The fact that you are getting to the slave side or far side of Metrolink and not beyond could be a bug in their bridging between the wireless interface and the Ethernet interface.

Since your bridging VLANs through your link make sure the MTU on the Metrolink is at least 1528 or higher if your running higher MTUs anywhere else.

Since your issue is intermittent and is fixed by rebooting and works for awhile I am pretty certain this is not a switch related issue but could be the Discovery Tab issue..

[givemesam]

Well it didn't fix after the reboot. It continued to present after the reboot for about 30 second until it decided to pass traffic.

We are not running any mtus higher than 1500. Metrolinq is also set to 1500 on Ethernet side. But may run higher MTU on wireless interfaces adaptively.

Arg. Should we go to 1.4.2 or wait for the new RC? Any useful fixes on thr RC? Our required feature set is vlan trunking w/ Poe

[givemesam]

If I set the MTU to 1528 on the far side metrolinq, should I also set it on the far side Netonix before setting it on the far side of the metrolink?

We have had it set to 1500 since day one on the metrolinq.

Should we go all the way to jumbo packets on the Ethernet and Netonix?

[bonac]

Hello,

on both this new FW and previous stock FW,
on both WS-12-250-DC and WS-10-250-DC,

on Device -> Configuration menu
in SMTP section, "Local Hostname" field only accept 4 hexadecimal chars ! Wouldn't this be plain text ?

btw, where do we found the current firmware version number ?

Except there is NO LED for the SFP ports (though I bought them a few weeks ago) which is horribly annoying for troubleshooting, those are really nice switches. I have 6 of them on production and am happy.

Many thanks.