fan rpm with no load

[abrust]

I have a brand new WS-12-250-AC WISP Switch that is running the latest firmware (v1.5.0). The switch is running indoors (room temp) and has no PoE ports enabled.

About every 10 minutes or so, the fan goes from 0 rpm up to about 8900 rpm for 5-10 seconds, then back down to 0 rpm for another 10 seconds, then back up again to 8900. This loop happens for about 5-10 minutes before it idles again for 0 rpms for 10 minutes before it starts the cycle again.

Other models of this unit seem to consistently run the fan at around 2500rpm.

I have factory reset this device as well as re-loaded the firmware (v1.5.0).

I'm curious if this is normal or could be indicative of a fan issue.

[Stephen]

It could be a hardware problem, but the fans behaving like that can also happen if the 'switch' process is being restarted. Could you post up the logs that you have while it's been doing this?

[abrust]

We tried to deploy this switch anyways this afternoon and noticed the switch was rebooting in a loop when we connected a device with 48VH PoE. (apologies for not grabbing the logs then).

I had previously been running this switch on a bench with 2 X 24V .75A devices powered and never noticed the switch "rebooting".

Below are the logs when the switch has no devices connected to it (other than my ethernet connection). Can you advise on whether I should RMA this switch?

Dec 31 16:00:04 kernel: 0x00000000-0x00040000 : "RedBoot"
Dec 31 16:00:04 kernel: 0x00040000-0x00080000 : "config"
Dec 31 16:00:04 kernel: 0x00080000-0x001c0000 : "linux_recovery"
Dec 31 16:00:04 kernel: 0x001c0000-0x003c0000 : "rootfs_recovery"
Dec 31 16:00:04 kernel: 0x003c0000-0x00500000 : "linux"
Dec 31 16:00:04 kernel: 0x00500000-0x00b00000 : "rootfs"
Dec 31 16:00:04 kernel: mtd: partition "rootfs" set to be root filesystem
Dec 31 16:00:04 kernel: 0x00b00000-0x00f40000 : "rootfs_data"
Dec 31 16:00:04 kernel: 0x00f40000-0x00f80000 : "FIS directory"
Dec 31 16:00:04 kernel: 0x00f80000-0x00f81000 : "RedBoot config"
Dec 31 16:00:04 kernel: 0x00fc0000-0x01000000 : "Redundant FIS"
Dec 31 16:00:04 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Dec 31 16:00:04 kernel: TCP cubic registered
Dec 31 16:00:04 kernel: NET: Registered protocol family 10
Dec 31 16:00:04 kernel: lo: Disabled Privacy Extensions
Dec 31 16:00:04 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Dec 31 16:00:04 kernel: NET: Registered protocol family 17
Dec 31 16:00:04 kernel: 802.1Q VLAN Support v1.8 Ben Greear
Dec 31 16:00:04 kernel: All bugs added by David S. Miller
Dec 31 16:00:04 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Dec 31 16:00:04 kernel: Freeing unused kernel memory: 116k freed
Dec 31 16:00:04 kernel: Please be patient, while OpenWrt loads ...
Dec 31 16:00:04 kernel: Algorithmics/MIPS FPU Emulator v1.5
Dec 31 16:00:04 kernel: mini_fo: using base directory: /
Dec 31 16:00:04 kernel: mini_fo: using storage directory: /jffs
Dec 31 16:00:04 sysinit: killall: udhcpc: no process killed
Dec 31 16:00:06 netonix: 1.5.0 on WS-12-250-AC
Dec 31 16:00:07 kernel: vtss_core: module license '(c) Vitesse Semiconductor Inc.' taints kernel.
Dec 31 16:00:07 kernel: switch: 'Luton26' board detected
Dec 31 16:00:09 kernel: vtss_port: Loaded port module on board Luton26, type 5
Dec 31 16:00:09 kernel: nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
Dec 31 16:00:10 system: Setting MAC address from flash configuration: EC:13:B2:63:7C:F2
Dec 31 16:00:10 kernel: i2c /dev entries driver
Dec 31 16:00:10 kernel: i2c_vcoreiii i2c_vcoreiii: i2c bus driver on IRQ 19
Dec 31 16:00:11 sysinit: Loading defaults
Dec 31 16:00:11 sysinit: Adding custom chains
Dec 31 16:00:12 system: starting ntpclient
Dec 31 16:00:12 sysinit: Loading zones
Dec 31 16:00:12 sysinit: Loading forwarding
Dec 31 16:00:12 sysinit: Loading redirects
Dec 31 16:00:12 sysinit: Loading rules
Dec 31 16:00:12 sysinit: Loading includes
Dec 31 16:00:13 admin: adding lan (eth0.800) to firewall zone lan
Dec 31 16:00:15 syslogd exiting
Dec 31 16:00:17 syslogd started: BusyBox v1.19.4
Dec 31 16:00:21 kernel: eth0.800: no IPv6 routers present
Dec 31 16:00:23 sysinit: 1969-12-31 16:00:22: (log.c.216) server started
Dec 31 16:00:26 dropbear[766]: Running in background
Dec 31 16:00:28 switch[794]: Detected cold boot
Dec 31 16:00:30 switch[794]: PoE enabled on port 1, PoE Smart is starting cable check
Dec 31 16:00:30 switch[794]: PoE enabled on port 12, PoE Smart is starting cable check
Dec 31 16:00:30 system: starting ntpclient
Dec 31 16:00:34 switch[794]: Port 1 cable check results: Open, Open, Open, Open
Dec 31 16:00:34 switch[794]: Port 1 passed PoE Smart cable check, turning on power
Dec 31 16:00:34 switch[794]: Port 12 cable check results: Open, Open, Open, Open
Dec 31 16:00:34 switch[794]: Port 12 passed PoE Smart cable check, turning on power
Dec 31 16:00:41 system: starting ntpclient
Dec 31 16:00:53 system: starting ntpclient
Dec 31 16:01:04 system: starting ntpclient
Dec 31 16:01:15 system: starting ntpclient
Dec 31 16:01:25 Port: link state changed to 'up' (1G) on port 10
Dec 31 16:01:25 STP: set port 10 to discarding
Dec 31 16:01:26 system: starting ntpclient
Dec 31 16:01:27 STP: set port 10 to learning
Dec 31 16:01:27 STP: set port 10 to forwarding
Dec 31 16:01:37 system: starting ntpclient
Dec 31 16:01:49 system: starting ntpclient
Dec 31 16:02:00 system: starting ntpclient
Dec 31 16:02:11 system: starting ntpclient
Dec 31 16:02:22 system: starting ntpclient
Dec 31 16:02:34 system: starting ntpclient
Dec 31 16:02:45 system: starting ntpclient
Dec 31 16:02:56 system: starting ntpclient
Dec 31 16:03:07 system: starting ntpclient
Dec 31 16:03:18 system: starting ntpclient
Dec 31 16:03:30 system: starting ntpclient
Dec 31 16:03:41 system: starting ntpclient
Dec 31 16:03:52 system: starting ntpclient
Dec 31 16:04:03 system: starting ntpclient
Dec 31 16:04:15 system: starting ntpclient
Dec 31 16:04:26 system: starting ntpclient
Dec 31 16:04:37 system: starting ntpclient
Dec 31 16:04:48 system: starting ntpclient
Dec 31 16:04:59 system: starting ntpclient
Dec 31 16:05:11 system: starting ntpclient
Dec 31 16:05:22 system: starting ntpclient
Dec 31 16:05:33 system: starting ntpclient
Dec 31 16:05:44 system: starting ntpclient
Dec 31 16:05:56 system: starting ntpclient
Dec 31 16:06:07 system: starting ntpclient
Dec 31 16:06:18 system: starting ntpclient
Dec 31 16:06:29 system: starting ntpclient
Dec 31 16:06:41 system: starting ntpclient
Dec 31 16:06:52 system: starting ntpclient
Dec 31 16:07:03 system: starting ntpclient
Dec 31 16:07:14 system: starting ntpclient
Dec 31 16:07:25 system: starting ntpclient
Dec 31 16:07:37 system: starting ntpclient
Dec 31 16:07:48 system: starting ntpclient
Dec 31 16:07:59 system: starting ntpclient
Dec 31 16:08:11 system: starting ntpclient
Dec 31 16:08:22 system: starting ntpclient
Dec 31 16:08:33 system: starting ntpclient
Dec 31 16:08:44 system: starting ntpclient
Dec 31 16:08:56 system: starting ntpclient
Dec 31 16:09:07 system: starting ntpclient
Dec 31 16:09:18 system: starting ntpclient
Dec 31 16:09:29 system: starting ntpclient
Dec 31 16:09:40 system: starting ntpclient
Dec 31 16:09:51 system: starting ntpclient
Dec 31 16:10:03 system: starting ntpclient
Dec 31 16:10:14 system: starting ntpclient
Dec 31 16:10:25 system: starting ntpclient
Dec 31 16:10:36 system: starting ntpclient
Dec 31 16:10:47 system: starting ntpclient
Dec 31 16:10:59 system: starting ntpclient
Dec 31 16:11:10 system: starting ntpclient
Dec 31 16:11:21 system: starting ntpclient
Dec 31 16:11:32 system: starting ntpclient
Dec 31 16:11:44 system: starting ntpclient
Dec 31 16:11:55 system: starting ntpclient
Dec 31 16:12:06 system: starting ntpclient
Dec 31 16:12:17 system: starting ntpclient
Dec 31 16:12:28 system: starting ntpclient
Dec 31 16:12:40 system: starting ntpclient
Dec 31 16:12:51 system: starting ntpclient
Dec 31 16:13:02 system: starting ntpclient
Dec 31 16:13:13 system: starting ntpclient
Dec 31 16:13:25 system: starting ntpclient
Dec 31 16:13:36 system: starting ntpclient
Dec 31 16:13:47 system: starting ntpclient
Dec 31 16:13:58 system: starting ntpclient
Dec 31 16:14:10 system: starting ntpclient
Dec 31 16:14:21 system: starting ntpclient
Dec 31 16:14:32 system: starting ntpclient
Dec 31 16:14:43 system: starting ntpclient
Dec 31 16:14:55 system: starting ntpclient
Dec 31 16:15:06 system: starting ntpclient
Dec 31 16:15:17 system: starting ntpclient
Dec 31 16:15:28 system: starting ntpclient
Dec 31 16:15:39 system: starting ntpclient
Dec 31 16:15:51 system: starting ntpclient
Dec 31 16:16:02 system: starting ntpclient
Dec 31 16:16:13 system: starting ntpclient
Dec 31 16:16:24 system: starting ntpclient
Dec 31 16:16:36 system: starting ntpclient
Dec 31 16:16:47 system: starting ntpclient
Dec 31 16:16:58 system: starting ntpclient
Dec 31 16:17:09 system: starting ntpclient
Dec 31 16:17:21 system: starting ntpclient
Dec 31 16:17:32 system: starting ntpclient
Dec 31 16:17:43 system: starting ntpclient
Dec 31 16:17:54 system: starting ntpclient
Dec 31 16:18:06 system: starting ntpclient
Dec 31 16:18:17 system: starting ntpclient
Dec 31 16:18:28 system: starting ntpclient
Dec 31 16:18:39 system: starting ntpclient
Dec 31 16:18:50 system: starting ntpclient
Dec 31 16:19:02 system: starting ntpclient
Dec 31 16:19:13 system: starting ntpclient
Dec 31 16:19:24 system: starting ntpclient
Dec 31 16:19:35 system: starting ntpclient
Dec 31 16:19:47 system: starting ntpclient
Dec 31 16:19:58 system: starting ntpclient
Dec 31 16:20:09 system: starting ntpclient
Dec 31 16:20:20 system: starting ntpclient
Dec 31 16:20:31 system: starting ntpclient
Dec 31 16:20:43 system: starting ntpclient
Dec 31 16:20:54 system: starting ntpclient
Dec 31 16:21:05 system: starting ntpclient
Dec 31 16:21:16 system: starting ntpclient
Dec 31 16:21:28 system: starting ntpclient
Dec 31 16:21:39 system: starting ntpclient
Dec 31 16:21:50 system: starting ntpclient
Dec 31 16:22:01 system: starting ntpclient
Dec 31 16:22:13 system: starting ntpclient
Dec 31 16:22:24 system: starting ntpclient
Dec 31 16:22:35 system: starting ntpclient
Dec 31 16:22:46 system: starting ntpclient
Dec 31 16:22:58 system: starting ntpclient
Dec 31 16:23:09 system: starting ntpclient
Dec 31 16:23:20 system: starting ntpclient
Dec 31 16:23:31 system: starting ntpclient
Dec 31 16:23:42 system: starting ntpclient
Dec 31 16:23:54 system: starting ntpclient
Dec 31 16:24:05 system: starting ntpclient
Dec 31 16:24:16 system: starting ntpclient
Dec 31 16:24:27 system: starting ntpclient
Dec 31 16:24:39 system: starting ntpclient
Dec 31 16:24:50 system: starting ntpclient
Dec 31 16:25:01 system: starting ntpclient
Dec 31 16:25:13 system: starting ntpclient
Dec 31 16:25:24 system: starting ntpclient
Dec 31 16:25:35 system: starting ntpclient
Dec 31 16:25:46 system: starting ntpclient
Dec 31 16:25:58 system: starting ntpclient
Dec 31 16:26:09 system: starting ntpclient
Dec 31 16:26:20 system: starting ntpclient
Dec 31 16:26:31 system: starting ntpclient
Dec 31 16:26:43 system: starting ntpclient
Dec 31 16:26:54 system: starting ntpclient
Dec 31 16:27:05 system: starting ntpclient
Dec 31 16:27:16 system: starting ntpclient
Dec 31 16:27:28 system: starting ntpclient
Dec 31 16:27:39 system: starting ntpclient
Dec 31 16:27:50 system: starting ntpclient
Dec 31 16:28:02 system: starting ntpclient
Dec 31 16:28:13 system: starting ntpclient
Dec 31 16:28:24 system: starting ntpclient
Dec 31 16:28:36 system: starting ntpclient
Dec 31 16:28:47 system: starting ntpclient
Dec 31 16:28:58 system: starting ntpclient
Dec 31 16:29:09 system: starting ntpclient
Dec 31 16:29:21 system: starting ntpclient

Copyright 2014-2018 Netonix

[Stephen]

If you've already seen other WS-12-250-AC's using the same setup (power, cables, PoE devices, etc) and they are behaving as expected as opposed to this unit, then yes I'd say RMA the unit.