Netonix Forums

We have just replaced a ToughSwitch8 with WS-8-250-AC but cant get spanning tree to work.

our setup is:

Firewall -> Cisco3750 (STP Master) -> Fiber link -> EdgeSwitch24 - > AirFiber24 (Master-link path cost: 20000) and PowerBeam5-400 (Backup-link path cost: 200000) -> WS-8-250-AC AirFiber24 port1 PBM5 port 6 (RSTP Enable, STP on LAGs Disabled)

It all worked on ToughSwitch8!

But on WS-8-250-AC we get link on AirFiber online 2-5 minutes, and Port 6 Disabled after that time the switch automatic enables Port 6 and we get loop for 30-60 sec and then it continues like this.... forever....

is this normal? or am i missing some thing?

I know WS-8-250-AC dosent have path cost yet, but it shout use Port ID instead

Any suggestions

/Carsten

Hi Carsten,

Sorry to hear of your problem, not sure why you are having a problem with R/STP as this feature has been tested by us and other users to work properly but that is not to say your setup does not expose another issue that no one else has found.

I did just post up v1.2.0rc4 which has R/STP Path Cost in it but this version is still being tested.

If you leave it set to Auto the switch assumed the standards based on link speed.

rstp.jpg (39.55 KiB) Viewed 7723 times

Any information you can provide to help us determine if there is indeed a problem with our firmware that we can fix is greatly appreciated but unfortunately we do not have all the equipment you are using to lab your issue.

Thanks,
Chris

Hi Chris

I need some help to identify what settings i need to do on WS-8-250-AC to get my redundant link working with RSTP.

Switch firmware is now 1.1.3.

Setup is link comming from EdgeSwitch24 port 1- throu AirFiber24 cost 20000 to netonix port 1, redundant link from EdgeSwitch24 port 2 - NBM5-400 cost 20000 (to force cost as 100mbit link) to netonix port 6

I have disabled "Loop Protection" on Netonix

This was all the settings i did on ToughSwitch8 to get it working, but on netonix i get loop on the network.
Are there something more i need to set?

Please load v1.1.4 which was posted today.

If you had ever installed v1.2.0rcX then the switch will mi-behave until either you default it and set it back up or install v1.1.4

It might also help if you actually enable RSTP on each port

CLICK IMAGE TO SEE FULL SIZE

Thanks, i have upgradet all switch to 1.1.4

I have locket all lan port to fixed speed, instead of Auto, and havent had any link issues after reboot, issues since.

It simse to work now, but shudent State change to "Blocked" on the backup link? both ports says "Forwarding"?

Hightech wrote:Thanks, i have upgradet all switch to 1.1.4

I have locket all lan port to fixed speed, instead of Auto, and havent had any link issues after reboot, issues since.

It simse to work now, but shudent State change to "Blocked" on the backup link? both ports says "Forwarding"?

I would use Auto instead of hardcoding speed/duplex as this can cause packet loss and disables any Flow Control as Flow Control only works on Auto sensing ports with any switch not just us, that is the standard.

If you have 2 switches both using RSTP connected together by 2 cables then ONE switch will elect to be the one that actually changes a port status to Blocking not both switches.

Ok, Thanks :-)

So now i have no issues keeping us from preorder the next batch of switches

Hightech wrote:Ok, Thanks :-)

So now i have no issues keeping us from preorder the next batch of switches

Thanks, Eric and I were up late for the past few nights trying to track this down and last night around midnight the bug was found!

for you and your team.
And for all the work your team put in to making the perfect WISP switch.....

and all our stupid questions, when we are stress up....