NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
PoE doesn't start_GS308EP
We use the GS308EP to manage 2 differents VLAN in our custom system. the port 1 is used to power on a RFID reader (FEIG MR102), the others ports are for classic ethernet commnication. We configure it as we wanted and it works as expected, but we have an issue on the activation of the PoE function at the start of our system. The switch power supply come from an electric inverter (which supplies the main power line when its function of inverter is not needed). Upstream the inverter we put a circuit breaker (2CSR275180R1164 DS201 M C16 A30). Our issue follow this patern: If we turn our system ON, by starting it from the inverter (with the circuit breaker open), the PoE launches without a problem, in all cases. If we turn our system ON, with the circuit breaker close and we start the inverter, the PoE doesn't launch, and if we open the circuit breaker, the supply from the inverter takes over and the PoE launches immediatly When we say "PoE doesn't launch", we mean the green led on the port (and the orange) doesn't turn ON. And we say that "the PoE starts" because the green led turn ON. We suspected the circuit breaker, and change the type (from AC to A), but the issue continue. We have isolated the switch to keep only the port 1 (to know if the issue could came from some interference from something else), but the issue still occur. What is bother us the most is that, after changing the circuit breaker, the issue seemed to have been resolved (we made severals power ON test), and the PoE did activate in some previous problematics cases, but at one time, on another test of power ON, the PoE didn't launch (only by open the circuit breaker like before), and we went further by powering it ON on a normal power outlet , and even like this, the PoE didn't launch... The software is up to date (V2.0. something), the configuration seems ok, we activated the long time detection, etc It is not an isolated case, on one of our other product we reproduce the issue (same hardware configuration). Thanks for the help we could get.