New to Netonix switches

[wisp-wand]

Hi All, Have recently bought the WS-12-250-DC, this is like a dream switch for me. My biggest sites are DC, but run off AC PSU with SLA batteries, same as all of us I guess. The float charge voltage can be over 26v so I also have a DC-DC convertor to get clean 24VDC. In addition I have issues with the tough switches so have been installing Cisco SG300-10 and using a DC stepdown regulator to change the voltage from 24VDC to the 12VDC that switch requires. I then use Mikrotik Gig POE injectors to power the radios! I chose this kit because it works for me, and is reliable. You can see the wisp switch can replace the DC-DC convertor, the step down, the POE injectors as well.

I installed my first one and bought another. My experience was as follows. I set the Manage VLAN to be 160 and changed the switch IP to one in the management range. I did not cut over all of the kit, just one radio that linked back to the network with VLAN 160 on it. All worked fine.

I then planned a works window to cut over the other radios. This meant changing the management VLAN to 770 and using a completely different address. The switch took this. Heres the complication. My manage network is routed. It is separate from the payload network.(ALL IP's changed and not real) The PC I manage from is 192.168.16.10 the switch was set to 192.168.16.222 originally during the test.
I then changed the switch IP to 192.168.17.4, with default gateway of 192.168.17.1 and thought I would add VLAN 160 back in (not manage VLAN) but for ping purposes. My manage PC could now ping 192.168.16.222 quite happily via vlan 160, and also access the manage IP on 192.168.17.4. The switch was getting really confused though, because although the manage PC was accessing 192.168.17.4 the switch was replying via VLAN160. I knew this wasn't right, but left it as it was working, thinking I would figure it out later.
It ran for about 3 days, and I got a bunch of network alarms, the switch had crashed and rebooted, and dropped all of the client connections from that tower. I could no longer manage it from 192.168.16.10. I could see an ARP entry for 192.168.17.4 though, so got a router to masqurade as though it was on 192.168.17.0/24 network and deleted VLAN 160 completely. Then deleted the default gateway of 192.168.17.1, and then put it back in again, all fixed.


Not sure if the above helps anyone, it was confusing as the 'PING' function is for PING only, so I thought, but it does seem to have an impact on the switches own routing table as well.

I am going to cut our biggest tower over this weekend onto the second switch I bought, so fingers crossed!

Regards

W

[wisp-wand]

Turns out I have the switch crash and reboot issue, so delaying our roll out for now. The IP issue exists, but I now suspect the known issue/bug caused the crash and reboot.

[sirhc]

Turns out I have the switch crash and reboot issue, so delaying our roll out for now. The IP issue exists, but I now suspect the known issue/bug caused the crash and reboot.

What IP Issue and what known issue/bug that causes crash and reboot?

[adairw]

Maybe he's confused with some other product?

[wisp-wand]

Hi guys, read my post above for the IP issue. It seems from reading other posts there is a crash and reboot issue, although so far this seems to have only affected FM sites, mine switch crashes but writes the exact same log events even though I am not near a big TX. However, this may be relevant, I am 400 metres away from a large substation with exposed HV bus bar....

W