02-16-2017 05:19 AM - edited 03-08-2019 09:22 AM
Never encountered this before - typical card reader access controller connected to network with static IP and communicates to host PC for door control. The controller operates fine stand alone disconnected from switch, online it will fail after a short time. By failure I mean that it can't function. It will start to reboot for unknown reasons, it's own firmware does not seem to run correctly. As soon as it is disconnected from the 3750 switch, it goes right back to normal. The manufacturer, Sielox, claimed that POE from the switch port was the cause. POE is not enabled on this switch. We connected a small Netgear switch between the controller and the 3750 and everything worked well for a couple of months. Now the same thing. It is as if this switch does not like this controller. It's been swapped out and even added a second one along side only to see both of them have the same failure. These controllers are used on networks all around the country and never have this problem. What is the 3750 doing to these controllers? Is it due to certain ports used for communication? So far, nobody can explain this unusual device behavior.
We would welcome any feedback on what could be the solution to this, as this customer is getting quite annoyed by such failure.
02-16-2017 06:14 AM
Hi
what software version are you running on the 3750 have you tried upgrading it incase your hitting a bug ?
did you check the arp and mac tables when its gets corrupted like that when still connected to the switch , to see if there gone incomplete
does the switchport show any errors crcs/inputs collision anything ?
have you tried changing the duplex speed , hardcode it of its auto negotiating
02-16-2017 11:22 AM
Hi
Have you checked the cabling connecting the controller to the switch. Check if your 3750 model switch supports TDR:
https://supportforums.cisco.com/document/74231/how-use-time-domain-reflectometer-tdr
hth
Andy
02-16-2017 11:33 AM
Thanks for heads up on TDR but it's not included on this model. Anyway, if cabling was at fault it wouldn't explain why two controllers both do the same thing on two separate connections. In addition, they shouldn't fail when they are after a 4 port switch in between. This is something "getting into" the controller itself, not sure what it is.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide