PoE toggle problem

[adairw]

Just defaulted a WS-12-250A, have five cameras and two radios plugged in. Noticed the cameras were up and passing traffic even though I had not enabled the power on the ports yet....

See attachments.

Edit:
Are the ports auto sensing? I see I can toggle the voltage on ports that do not have anything plugged in to them. But ports with cameras or radios do not let me specify a voltage.

[lligetfa]

I have not defaulted a switch but I did have one port that when I turned off the PoE in the UI, it still kept the PoE power on the port. I unplugged the port so there was no link and then could toggle the PoE back on and then off.

As long as there is link, the UI would not let you toggle the power back on. You need to unplug the cams so that the link drops.

[sirhc]

No that should not occur, this is an over sight in my count.

But I know why, I will have to have Eric fix that tomorrow.

If you remember we changed the unit so that you can reboot it and it leaves the POE ports on during the reboot or after a firmware upgrade ti limit radio down time.

I did not think about people having POE turned on or configured on then defaulting it in the UI.

If you power cycled it would turn them off to match the defaulted config.

I will have Eric make sure he turns all the POE off if you do a software UI default.

Good catch

[adairw]

Makes sense.
Like you say on a default it would probably be best to turn everything off. Or maybe it pops up and asks you how you want it to come back up? dunno, that might be confusing for people and not totally "default"

[sirhc]

I am just going to have it turn them all off on default before it reboots, as I said I was not thinking about the defaulting but rather I was excited about the fact that it normally does not turn POE off on upgrades, reboot and so on which is a good thing.

I hear the edgeMAX switch take a couple minuted to reboot then if you have DFS sectors that could be another couple minutes or an aifFIBER if they powered one would be another couple minutes to boot and re-establish a link. Our reboot is 17 seconds and your devices should lose less then 10 pings give or take.

As I said it was an oversight on the factory default, I just plain forgot about that but it is an easy fix, look for a new firmware today.

[lligetfa]

I am just going to have it turn them all off on default...

That is the only logical choice. After all, defaulting should leave it in the same state as when it just came out of the box, except of course the firmware version.

I hear the edgeMAX switch take a couple minuted to reboot...

They just released 1.0.1 firmware yesterday so I flashed my ES24. I wish now that I would have timed it. It took quite a long time. If this were a production switch, I would have to go for a walk so that I could breathe rather than sit there watching it with bated breath.

[sirhc]

The problem of NOT turning PoE Ports OFF when doing a factory default has been fixed with v1.0.6rc3

[adairw]

cool, will load it up and test it out just for fun.

[adairw]

Loaded 1.0.6rc3, defaulted the switch with ports powered on. When it booted back up, the ports were off as expected. I had to log in via the gui and manually turn them back on this time.
good work!

[sirhc]

We fixed the POE issue as I explained in an earlier post. We normally leave the POE ports on when doing a software reboot so radios do not have to also power cycle bringing the tower up faster. With the latest patch we make sure to turn POE OFF when preforming a factory default.

Also if you have not re-configured the ports or power cycled since firmware v1.0.4 then the MTU would never have been set to the SFP module. There was a fix in v1.0.4 that corrected the SFP MTU.

Unplugging the SFP and plugging it back in will cause the switch to set the SFP MTU.

Well glad we figured that out.

Then if you are now running v1.0.6rc3 you should be good.

Please let us know if you find another bug.