26 port AC switch crapped out again

[Accel Wireless]

2nd time in 3 months this unit has crapped out we thought it was a radio that went bad that caused it the 1st time we happened to reset the switch to defaults and it worked, nothing previous would fix it until the reset which was just a last ditch effort. Well it happened again so I knew what to try first. two ports connected to our router from the switch were lit up but we could not get into the switch with our static ip assigned to it nor 192.168.1.20.

We then tried a serial cable no go nothing even after several power cycles and we had another netonix right next to it with the same setup on our PC and same serial cable and it worked just fine so our setup was spot on. we finally got tired of wasting time so we reset it and it came back up but still no serial access? we loaded our backup config and all is well again except one port sees a LOT of errors 27 15:51:55 switch[1395]: got excessive pause frames on port 11 (15518), count = 1

We checked everything and nothing is out of whack, cable tests good, radio is good both switch and radio show gig ethernet negotiation, so we tried to turn on flow control but it will not turn on, at leas the gui does not show it is on but then we get the same errors then we get the message it received to many errors so its shutting flow control off? even though it had not shown it being on.

We upgraded to 1.5.1 with success and the system came up after the upgrade but still having same issues and still no serial access. We have since ordered a new Netonix just to be on the safe side but I have doubts that's the issue. What could cause the switch to just die like this and have to reset it to defaults to get it to work again

Any suggestions?

Ps while logged into the switch just monitoring it throws up the red error that a configuration has changed click here to reload config. WTH why is it doing this nothing changed while I am sitting here just looking at the damn log file? very frustrating!

[sirhc]

Ps while logged into the switch just monitoring it throws up the red error that a configuration has changed click here to reload config. WTH why is it doing this nothing changed while I am sitting here just looking at the damn log file? very frustrating!

Sadly this "above" os a "RARE" but known issue that we can not recreate recreate to fix. The way around it to fix it once it happens is to simply change something obnoxious such as a port description and save/apply. We think this is something that happens in the browser so not sure this is is a bug with us or the browser. As I said it does happen on very rare occasions and since it can not be recreated on demand we have not been able to correct it.

As far as your other issue please disable Flow Control on all ports.

[Accel Wireless]

Flow control IS disabled on all ports per the GUI I was able to log int the gui and go to the terminal window and I see that ALL port's flow control says they are set to NONE but port 11 the one giving all the errors the port is set to FALSE?

Why does the GUI show all as off but CLI shows false? what does false mean and is this what's causing my issues with all these errors.


"Number": 11,
"Name": "Port 11 3.2",
"Enable": true,
"Link": "Auto",
"PoE": "48V",
"FlowControl": false,
"Multicast": true,
"MTU": "1528",
"TxLimit": "",
"RxLimit": "",
"STP": false,
"STPPriority": "128",
"STP_Path_Cost": "",
"Stats": true,
"Isolation": false,
"AllowedVLANs": "",
"DHCP_Snooping": false,
"Shutdown_Voltage": "",
"Restart_Voltage": "",
"Priority": "11",
"Shutdown_Time": "",
"Startup_Time": "",
"Boot_Start_Delay": "",
"Updated_SFP2": true,
"QoSSched": "Strict",
"PoE_Smart": true,
"Updated_MTU": true

[Accel Wireless]

FYI I tried your suggestion of making a change and the error keeps coming back..

[Accel Wireless]

Also how in the hell do you upload a picture?? there is nothing obvious I see when I hit reply that gives me that option or I would post pictures showing what I am seeing.

[Accel Wireless]

I did a show config now it says flow control is set to NONE? does it change every time I do a show command?

[Accel Wireless]

Can you please answer the original questions I had about the switch crapping out and not being able to get the serial port to respond? I cant have this switch in there anymore if its going to be causing issues for no apparent reason. I need to have confidence that this is a bad switch or something that was fixed in 1.5.1 and if fixed why am I still not able to get into the serial port like I can with the 20 other switches we have.

Thanks

[sirhc]

As far as uploading a picture read any of my post's FOOTER
There is a link by the blue SUBMIT button

Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.

Now we do have a known issue v1.5.1 and v1.5.2rcX that we are working on which could be your issue if your using a LAG and or possibly just STP.

See this post: viewtopic.php?f=17&t=4468&start=40#p28503

The issue does not exist in v1.5.0 and older but if this is a NEW switch it "should" use v1.5.1 or newer to properly drive the fans as the fan manufacturer changed our fans and we had to change the way the fans are driven. However it will not hurt anything to use v1.5.0 for now until we fix this issues.

You can try v1.5.0 and see if your issue goes away.

[Accel Wireless]

I still don't see an answer as to WHY the switch just UP an died and had to be reset to defaults to bring it back to life? Why does the serial port not respond. 3rd time asking same question? how else can I word this so that you can understand my question I don't care about the other little things I care more as to what caused it to die..

[sirhc]

I still don't see an answer as to WHY the switch just UP an died and had to be reset to defaults to bring it back to life? Why does the serial port not respond. 3rd time asking same question? how else can I word this so that you can understand my question I don't care about the other little things I care more as to what caused it to die..

Honestly I have no idea why this is occuring.

If the console port is not responding then that means the SOC is locked up which almost never occurs.

You see this on 2 different switches at the same site but you have other sites where this does not occur.

This would indicate that the switch is not the cause but rather something at the site is affecting the switch?

If you want me to guess:
I would say the switch is having a power issues of some kind. Meaning that if power is cut and restored rapidly several times the switch will start to power down but before it powers all the way down power is restored and the switch will come up in a weird state and at that point anything can happen.

Another possible thing that can cause "weird" issues and even damage to the switch is ground current but if the switch can be bench tested as explained in this post: viewtopic.php?f=6&t=2780#p19221 after a factory default and it passes all tests then I would think not ground current.

Other than power issues maybe another bug we are working on possibly related to Discovery TAB if you have it enabled. This causes memory to grow until the unit normally reboots, never heard of it causing a lock up. This bug affects a "few" people with larger layer 2 flat networks if the Discovery TAB is enabled.

If your using any SFP modules in this switch maybe you have a bad SFP module?

Possibly some sort of packet storm?

Again these are all guesses with little information to go on.

If you want me to speculate more please post up screen grabs all the config TAB with any changes from default and explain your power and grounding at this site.