WS-12-250-DC ; Error reading temp sensor

[sirhc]

New development in this problem.

We have learned that the noise is definitely coming in the DC cables, battery cables, and chargers.

We will work on making an external filter and then later integrate that filter into future DC2DC power supplies.

[Cameron]

ulink

I think we may be having the same issue. We have been fighting a WS-12-DC on one of our sites that has an FM broadcast reply/repeater within 25 feet of our switch and has our DC power cable running passed the antenna. Switch works fine in the office but once on site we will quickly get a flashing red error light on port 2, even without anything plugged into that port. We also are not able to get into the switch and it seems to reboot every minute or so. The FM transmitter is not a high powered one, it's a repeater for an out of town station and while we don't normally have problems with it we did have trouble with Mimosa's that they traced back to the FM station. Any ideas?

I am worried that the DC power lines going to the Netonix switch are picking up a lot of RF noise because you mentioned they are being run close to the FM repeater antenna. Can you run the DC power cable differently, or shield the DC power cable?

Dave

Yeah the more I look at this the more I think that is the most likely way for it to be getting into the switch. When I get a chance I will try powering the unit up a different way.

[sirhc]

We have confirmed and replicated in the lab what locating our DC switches at FM Broadcast towers will do to our "DC" switches.

WS-8-250-DC
WS-12-250-DC
WS-12-DC

This can not be fixed with firmware.

We are working on a hardware solution, we will keep you updated as we figure this out.

[redpeppers]

Is there a quick solution firmware wise that will at least keep the device from rebooting? I wish I would have seen this before I ordered this three days ago. Are you going to be offering the filter and/or a replacement free of charge? I can verify that I am having the same problem, 100ft below the FM antenna. Other than the errors everything else is working great.

[sirhc]

Is there a quick solution firmware wise that will at least keep the device from rebooting? I wish I would have seen this before I ordered this three days ago. Are you going to be offering the filter and/or a replacement free of charge? I can verify that I am having the same problem, 100ft below the FM antenna. Other than the errors everything else is working great.

Are all your towers at FM broadcast towers?

We are working on a solution, we will keep people posted as we figure this out but this only affect DC models if they are on a FM broadcast tower.

[adairw]

Is there a quick solution firmware wise that will at least keep the device from rebooting? I wish I would have seen this before I ordered this three days ago. Are you going to be offering the filter and/or a replacement free of charge? I can verify that I am having the same problem, 100ft below the FM antenna. Other than the errors everything else is working great.

I don't think it's really reasonable that they offer the filter for free. I mean c'mon, they produced a product and people are using it in a way that it probably wasn't really intended to be used. I think it's great that they are even working on a solution and plan on building that solution in to the next power supply. But standing there with your hand out isn't right.

Just my .02

[redpeppers]

Is it possible to disable the temp "shutdown" feature that will disable the POE when going into thermal protection. This would fix our problem now.

[wisp-wand]

I am also having this issue. The switch has rebooted with the below. It is not on a RF site. It has a stable power supply with battery backup. There is nothing within 1000 metres of this site with any RF on it at all, and then its a cell tower.
It is installed in a lift motor room, but some way from the motor and gear.

This is my first live install, and the customers connected have had stable service until I install the WS-12-250-DC. I can do limited testing if it helps, but if it keeps rebooting I might need to pull it. anything you want me to try, and should I also email support?

Jan 1 00:00:08 kernel: vtss_port: Loaded port module on board Luton26, type 5
Jan 1 00:00:09 system: Setting MAC address from flash configuration: xx:xx:xx:81:15:54
Jan 1 00:00:10 system: starting ntpclient
Jan 1 00:00:11 admin: adding lan (eth0.770) to firewall zone lan
Jan 1 00:00:12 admin: Unable to query power supply
Jan 1 00:00:21 dropbear[767]: Running in background
Jan 1 00:00:24 mini_snmpd[789]: started, listening on port 161/udp and 161/tcp
Jan 1 00:00:25 system: starting ntpclient
Jan 20 12:20:32 switch[783]: Error reading temp sensor
Jan 20 12:20:34 switch[835]: Detected cold boot
Jan 20 12:20:35 switch[835]: PoE enabled on port 2, PoE Smart is starting cable check
Jan 20 12:20:36 switch[835]: Port 2 cable check results: Ok, Ok, Ok, Ok
Jan 20 12:20:36 switch[835]: Port 2 passed PoE Smart cable check, turning on power
Jan 20 12:20:36 switch[835]: PoE enabled on port 3, PoE Smart is starting cable check
Jan 20 12:20:40 switch[835]: Port 3 cable check results: Open, Open, Open, Open
Jan 20 12:20:40 switch[835]: Port 3 passed PoE Smart cable check, turning on power

[sirhc]

OK you can not have the same issue if you are not at an FM site.

Please tell us your setup, firmware versions and start by describing your issue in detail.

[wisp-wand]

Hi, From the log the issue looks identical to the guys on the RF sites. Anyway firmware is latest (not beta) there are 2 radios connected, currently one has port status 'disabled' as its not in a vlan, but it is powered it is a ubnt PBE-400. Port 3 is a ubnt Rocket M5 AC lite. It is connected to a sector and customers connect there. It is powered on POE. There is a Mikrotik CCR connect on port 4, is is connected at 1gbps, and no POE (power off)
port 1 is for admin and not connected or powered.

All other ports are disabled. Port 3 and 4 and untagged together, this is customer traffic which is PPPOE. There is a VLAN for management which is tagged on all ports except port 2. I have thedude pinging the switch and also polling it for SNMP. I switched to SNMPv1 as I had stability issues with V2.

Everything works fine, then the switch reboots and I get the log as in my last post. Hope this is enough details, let me know what else you need.

Thanks