v1.3.6 FINAL bug reports and comments

[rgunderson]

Chris, what are your thoughts on my WS-12-250B filling up the log with "voltage should not be zero" on ports 3 & 4 when upgraded to 1.3.6?

All my WS-8-250-AC units accepted 1.3.6 fine but my WS-12-250B was filling up the log with "voltage should not be zero" on ports 3 & 4 so I downgraded back to 1.3.3. The voltages never did work right on this unit. Should I RMA? See attachments.

WS-12-250B-Image1.gif

WS-12-250B-Image2.gif

[sirhc]

Chris, what are your thoughts on my WS-12-250B filling up the log with "voltage should not be zero" on ports 3 & 4 when upgraded to 1.3.6?

All my WS-8-250-AC units accepted 1.3.6 fine but my WS-12-250B was filling up the log with "voltage should not be zero" on ports 3 & 4 so I downgraded back to 1.3.3. The voltages never did work right on this unit. Should I RMA? See attachments.

WS-12-250B-Image1.gif

WS-12-250B-Image2.gif

Read what is on the bottom of the Thread for reporting issues: viewtopic.php?f=17&t=1154

I am guessing this switch may have a damaged current sensor or 2.

I would swap out the switch and take it back to your office then test it out.

NOTE:
Our switches are designed to continue to run even when they are damaged. Sometimes the switch can take damage to sensors from a surge from the tower or ground potential shift between the tower and the cabinet damaging the current sensor on a port. Since all the current, voltage, and temp sensors share the same I2C bus this can cause other sensors to report erroneous values.
Prior to v1.3.5 we did not do as good of job at alerting the user to out of range readings, therefore after upgrading to v1.3.5 or newer if you are now seeing voltages, watts, or temperatures out of range this may be an indication that your unit took damage in the past and you were unaware of it.
This is why I say to always make sure your Tower Ground is Bonded to your Electrical Service ground and to run a ground wire up the tower and to each radios on the tower. I have a good post
HERE about proper grounding methods.
Another possible cause of "false" out of range readings can be from an incompatible SFP module. Since the SFP cages also share this same I2C bus to relay information about the SFP module to the system some incompatible SFP modules "can" disrupt normal I2C communication. Try removing the SFP module and see if the readings return to acceptable ranges. If you find an SFP module that is causing issue try another brand of SFP module. We are working on a way to eliminate this interference from some SFP modiule manufacturers and may offer a firmware in the future to fix this issue with these modules.

[dan_]

Just to clarify, if a switch detects a cold boot and shuts off PoE, does it remain off, or will PoE be re-enabled on all ports (including the first PoE port) after the switch comes back up?

Is it possible to have the first PoE port not come back up on a normal cold boot (such as after a power failure)?

No it shuts off the POE on the first POE port and requires you to turn it back on. THis will happen everytime you reboot the switch if you have a WS-6-MINI, WS-8-250-AC, or WS-8-250-DC model.

Here is an RC version that does not if you wish to try it

Click HERE to download v1.3.7rc2 - RELEASE CANDIDATE

We are still working on further improvements but this fixes the reboot issue for the WS-6-MINI, WS-8-250-AC and WS-8-250-DC

I've tested this and it fixed the PoE issue i was having
Thanks
Dan

[canpandave]

Really like the new graphics, the total power usage and in the status tab!

A request?

Could you put a clock type Icon in the graphic port representation on the main ports image whenever a port is set for shutdown/startup time?

Thanks

/d

[sakita]

When using RADIUS a password that starts with $ won't work.

Possibly an escaping / delimiting issue?

Haven't tested passwords with $ in other positions (or using other non alphanumeric characters).

[LRL]

Not sure if you want the 1.3.7rc7 comments here, but here's some.

I upgraded a new install of a ws-12-250-dc to 1.3.7rc7 and all appeared fine. I made some config changes (NTP, Name, password) and after applying I receive errors on most of the sensor readings.

Port watts read -1.0 on all ports.

See screenshot below.

screen

11-7-2015 1-50-18 AM.png (57.57 KiB) Viewed 7266 times

[sirhc]

Sorry for your issue LRL.

Could you power cycle the unit and see if that corrects it? (remove power for 10 seconds)

We had another person who power cycled it and all was fine.
viewtopic.php?f=17&t=1172#p8758

We are still trying to figure out what causes this issue when upgrading.

If you do power cycle it and it fixes the errors please provide a screen grab of the Device Status Page without the errors.

[lligetfa]

Repro'ing it is the first step to resolving it and I could not repro it consistently but then it magically fixed itself. In the industry we refer to it as CWT (problem Cleared While Testing).

[sirhc]

Yea, that is what I have been doing for the past couple hours is trying to recreate this ERROR.

I have an idea to try and force an I2C error, will discuss with Dave when he gets back to his terminal.

Also hoping LRL power cycles it and let's us know if that fixes it for him, every little bit of information helps.

[sirhc]

LRL - Did you look in the Log and see if there was an error reported in the switch Log?