Quickly Fluctuating Voltages WS-8-150-AC

[Chris@edgarhighspeed.com]

Hi Guys,
I was wondering if someone else can confirm this as normal or abnormal. It isn't happening on my WS-12-250-AC. And tonight I have had 2 cold reboots according to the logs. This switch is plugged into a APC SMART UPS 1000, it shows constant input power. But I am seeing the voltages on the Status Screen changing wildly and quickly.
I am running firmware 1.4.3rc3 and prior to the 2 cold reboots I was running 1.4.2 Final.

Also there are no watchdogs configured on this switch. I am wondering if the power supply isn't starting to fail and the wild swing in voltage reboots the switch.
I took a screen recorder video of how quick the voltages are changing. it is posted here.
https://drive.google.com/open?id=0BxVaW ... GJySmVpM0k
also the log is here. Prior to firmware update but post reboot.
Dec 31 17:00:04 kernel: 0x003c0000-0x00500000 : "linux"
Dec 31 17:00:04 kernel: 0x00500000-0x00b00000 : "rootfs"
Dec 31 17:00:04 kernel: mtd: partition "rootfs" set to be root filesystem Dec 31 17:00:04 kernel: 0x00b00000-0x00f40000 : "rootfs_data"
Dec 31 17:00:04 kernel: 0x00f40000-0x00f80000 : "FIS directory"
Dec 31 17:00:04 kernel: 0x00f80000-0x00f81000 : "RedBoot config"
Dec 31 17:00:04 kernel: 0x00fc0000-0x01000000 : "Redundant FIS"
Dec 31 17:00:04 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Dec 31 17:00:04 kernel: TCP cubic registered
Dec 31 17:00:04 kernel: NET: Registered protocol family 10
Dec 31 17:00:04 kernel: lo: Disabled Privacy Extensions
Dec 31 17:00:04 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Dec 31 17:00:04 kernel: NET: Registered protocol family 17
Dec 31 17:00:04 kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
Dec 31 17:00:04 kernel: All bugs added by David S. Miller <davem@redhat.com>
Dec 31 17:00:04 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Dec 31 17:00:04 kernel: Freeing unused kernel memory: 116k freed
Dec 31 17:00:04 kernel: Please be patient, while OpenWrt loads ...
Dec 31 17:00:04 kernel: Algorithmics/MIPS FPU Emulator v1.5
Dec 31 17:00:04 kernel: mini_fo: using base directory: / D
ec 31 17:00:04 kernel: mini_fo: using storage directory: /jffs
Dec 31 17:00:04 sysinit: killall: udhcpc: no process killed
Dec 31 17:00:05 netonix: 1.4.2 on WS-8-150-AC
Dec 31 17:00:07 kernel: vtss_core: module license '(c) Vitesse Semiconductor Inc.' taints kernel.
Dec 31 17:00:07 kernel: switch: 'Luton26' board detected
Dec 31 17:00:09 kernel: vtss_port: Loaded port module on board Luton26, type 5
Dec 31 17:00:09 kernel: nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
Dec 31 17:00:09 system: Setting MAC address from flash configuration: EC:13:B2:D1:00:50
Dec 31 17:00:09 kernel: i2c /dev entries driver
Dec 31 17:00:10 kernel: i2c_vcoreiii i2c_vcoreiii: i2c bus driver on IRQ 19
Dec 31 17:00:11 sysinit: Loading defaults
Dec 31 17:00:11 sysinit: Adding custom chains
Dec 31 17:00:11 system: starting ntpclient
Dec 31 17:00:12 sysinit: Loading zones
Dec 31 17:00:12 sysinit: Loading forwarding
Dec 31 17:00:12 sysinit: Loading redirects
Dec 31 17:00:12 sysinit: Loading rules
Dec 31 17:00:12 sysinit: Loading includes
Dec 31 17:00:12 admin: adding lan (eth0.20) to firewall zone lan
Dec 31 17:00:17 sysinit: killall: telnetd: no process killed
Dec 31 17:00:18 Port: link state changed to 'up' (1G) on port 1
Dec 31 17:00:18 Port: link state changed to 'up' (1G) on port 3
Dec 31 17:00:19 Port: link state changed to 'up' (1G) on port 5
Dec 31 17:00:19 Port: link state changed to 'up' (1G) on port 6
Dec 31 17:00:19 Port: link state changed to 'up' (1G) on port 4
Dec 31 17:00:19 main: packet_rx_filter_change NOT IMPLEMENTED
Dec 31 17:00:19 Port: link state changed to 'up' (1G) on port 7
Dec 31 17:00:19 sysinit: 1969-12-31 17:00:18: (log.c.97) server started
Dec 31 17:00:20 kernel: eth0: no IPv6 routers present
Dec 31 17:00:20 kernel: eth0.20: no IPv6 routers present
Dec 31 17:00:20 dropbear[738]: Running in background
Jul 25 20:48:27 switch[766]: Detected cold boot
Jul 25 20:48:27 Port: link state changed to 'down' on port 5
Jul 25 20:48:27 Port: link state changed to 'down' on port 6
Jul 25 20:48:27 Port: link state changed to 'down' on port 7
Jul 25 20:48:27 Port: link state changed to 'down' on port 3
Jul 25 20:48:28 Port: link state changed to 'down' on port 4
Jul 25 20:48:28 switch[766]: PoE enabled on port 3, PoE Smart is starting cable check
Jul 25 20:48:28 switch[766]: PoE enabled on port 4, PoE Smart is starting cable check
Jul 25 20:48:28 switch[766]: PoE enabled on port 5, PoE Smart is starting cable check
Jul 25 20:48:28 switch[766]: PoE enabled on port 6, PoE Smart is starting cable check
Jul 25 20:48:28 switch[766]: PoE enabled on port 7, PoE Smart is starting cable check
Jul 25 20:48:32 switch[766]: Port 3 cable check results: Abnormal termination, Open, Abnormal termination, Abnormal termination
Jul 25 20:48:32 switch[766]: Port 3 passed PoE Smart cable check, turning on power
Jul 25 20:48:32 switch[766]: Port 4 cable check results: Open, Open, Open, Open
Jul 25 20:48:32 switch[766]: Port 4 passed PoE Smart cable check, turning on power
Jul 25 20:48:33 switch[766]: Port 5 cable check results: Open, Open, Open, Open
Jul 25 20:48:33 switch[766]: Port 5 passed PoE Smart cable check, turning on power
Jul 25 20:48:33 switch[766]: Port 6 cable check results: Open, Open, Open, Open
Jul 25 20:48:33 switch[766]: Port 6 passed PoE Smart cable check, turning on power
Jul 25 20:48:33 switch[766]: Port 7 cable check results: Open, Open, Open, Open
Jul 25 20:48:33 switch[766]: Port 7 passed PoE Smart cable check, turning on power
Jul 25 20:48:36 Port: link state changed to 'up' (1G) on port 6
Jul 25 20:48:36 Port: link state changed to 'up' (100M-F) on port 4
Jul 25 20:48:36 Port: link state changed to 'up' (100M-F) on port 3
Jul 25 20:48:39 Port: link state changed to 'down' on port 6
Jul 25 20:48:42 Port: link state changed to 'up' (100M-F) on port 6
Jul 25 20:48:53 Port: link state changed to 'down' on port 3
Jul 25 20:48:53 Port: link state changed to 'down' on port 4
Jul 25 20:48:56 Port: link state changed to 'up' (1G) on port 3
Jul 25 20:48:56 Port: link state changed to 'up' (1G) on port 4
Jul 25 20:49:01 Port: link state changed to 'down' on port 6
Jul 25 20:49:04 Port: link state changed to 'up' (1G) on port 6
Jul 25 20:49:05 Port: link state changed to 'down' on port 6
Jul 25 20:49:07 Port: link state changed to 'up' (1G) on port 6
Jul 25 20:49:23 Port: link state changed to 'down' on port 4
Jul 25 20:49:26 Port: link state changed to 'up' (100M-F) on port 4
Jul 25 20:49:43 Port: link state changed to 'down' on port 4
Jul 25 20:49:46 Port: link state changed to 'up' (1G) on port 4
Jul 25 20:49:57 Port: link state changed to 'up' (1G) on port 5
Jul 25 20:49:58 Port: link state changed to 'up' (1G) on port 7
Jul 25 20:50:19 Port: link state changed to 'down' on port 5
Jul 25 20:50:19 Port: link state changed to 'down' on port 7
Jul 25 20:50:20 Port: link state changed to 'up' (1G) on port 5
Jul 25 20:50:21 Port: link state changed to 'up' (1G) on port 7
Jul 25 21:04:41 switch[756]: !3V is out of range (3.5V)


any info would be great. I have a spare WS-8-150-AC so swapping isn't an issue.

[sirhc]

I would like you to swap it and see please.

But before you put the new switch in service run it on the bench and verify it behaves normally, maybe even power similar devices on the bench.

Also see if the switch you take out of service preforms normally on your bench.

If the replacement switch does the same thing and the one you remove acts normal on a bench then we need to look at grounding.

Please describe the location and application this switch is installed at.

What is it powering?
Is the Electric service ground bonded to the the tower ground (if there is one)?
Do you have a dedicated grounding system and not relying on the tower (if there is one) for the ground path?

[Chris@edgarhighspeed.com]

I bench tested the replacement and the voltages don't change rapidly like the video. I will be replacing the switch at lunchtime and I will bring it back here to bench test it.

[sirhc]

Please describe the location and application this switch is installed at.

What is it powering (meaning where is the AC power coming from)?
Is the Electric service ground bonded to the the tower ground (if there is a tower)?
Do you have a dedicated grounding system and not relying on the tower (if there is one) for the ground path?

If there is excessive "ground" current flowing between the tower and AC power source which would be through the cables and the switch this could happen.

Read this post: viewtopic.php?f=30&t=1816

Here are some other good posts on grounding:
viewtopic.php?f=30&t=188
viewtopic.php?f=30&t=1429
viewtopic.php?f=17&t=1786&start=30#p13447

[Chris@edgarhighspeed.com]

This switch is mounted in a small indoor cabinet in a boiler room of a 16 story tall apartment building. It is grounded directly to the A/C service and it has a dedicated 110 outlet wired to the breaker box into the cabinet. I will double check the grounding hasn't come loose or anything.

This isn't a typical tower install but more of a tall building install. The equipment on the top of the building is all grounded to the halo grounding system that the cellular providers who also use the location installed.

I'll know more in a few hours. Since the update to 1.4.3-RC3 it hasn't rebooted (going on 12+ hours) .

[sirhc]

This switch is mounted in a small indoor cabinet in a boiler room of a 16 story tall apartment building. It is grounded directly to the A/C service and it has a dedicated 110 outlet wired to the breaker box into the cabinet. I will double check the grounding hasn't come loose or anything.

This isn't a typical tower install but more of a tall building install. The equipment on the top of the building is all grounded to the halo grounding system that the cellular providers who also use the location installed.

I'll know more in a few hours. Since the update to 1.4.3-RC3 it hasn't rebooted (going on 12+ hours) .

This would be a problem, you have 2 differnt grounding systems and the common bond is the Switch, Ethernet cables, and radios.

GROUND IS NOT GROUND, there are 2 differnt ground potentials at play here and all that current which could be many AMPS (low voltage) will try and equalize across your Ethernet cables and tear up equipment.

I guarantee you that the cellular company has their Electrical service ground bonded to the HALO ground system.

You can not do what your doing with 2 differnt ground potentials bonded with your Ethernet cable.


Please read the links I provided above.

[Chris@edgarhighspeed.com]

Makes sense, I will move my ground from AC to halo system I believe there is a good bus bar close to my cabinet.

[sirhc]

Makes sense, I will move my ground from AC to halo system I believe there is a good bus bar close to my cabinet.

Yes so the idea would be to use the HOT and NEUTRAL from the AC service panel but use the HALSO ground as your AC power ground as well like in this post:

viewtopic.php?f=17&t=1786&start=30#p13447

[Chris@edgarhighspeed.com]

I went onsite today and routed the Halo ground directly to a buss bar in the small cabinet and then replace the utility ground with the Halo ground. I also made sure to swap the WS-8-150-AC ground to the halo buss bar. I not longer have utility ground anywhere near my cabinet.

I did the switch swap and the current values seems to be stable.

I brought the other switch home and reset it to factory as well as re-flashed it to 1.4.2 final.

It still has the quickly changing voltage values. I can post another video but it isn't much different than the original.

Should I send this unit back for inspection to see if there was any damage done? Please let me know as I am pretty sure it won't be warranty if it's because of the grounding we had at the site.

[sirhc]

I would RMA it and let us look at it to be sure it is damage and not a failure.

Even if damaged the repair is half the cost of a new one.

viewtopic.php?f=6&t=1259