This is a clssical indication on that your PSU have done its work, repelace the PSU with a new one.
Be awere of that the connector is a special for SG-Series (very short contact) so if you don't find a replacement PSU you can use a generic one and re use the old contact.
if you have a spare power supply to test, it would be worth it if just to eliminate the power supply as the source of the problem.
Are the power requirements of v4 BIOS greater than v3? The box has been working reliably on v3 and only started crashing under load after being boosted to v4.05. Certainly timing wise, the memory running out seems to be a more statistically likely cause, but I',m more than prepared to test this idea out, as all good ideas are welcomed. I can switch power supplies with the current 560 running v3.1.5u and see if things go wrong on it.
No, the power requirements are no different.
It is a good way of eliminating the power supply as the cause of the issue if you have a 'spare' one right next to it.
There is a good chance itis not the power supply...but if it is easy, test it.
It's not the powersupply. I've switched with the other 560 and it's fine. It's definitely the memory and number of connections. I am seeking quotes to get a 720 as something with a little more capability to handle the larger number of connections we now deal with.
Note, that the default setting of concurrent sessions is 1024, enough for 30-50 users. The SG560 can safely handle up to more then 50.000 with correct setting.
This is from KB62283
You can se if this is the problem if you have klogd:ip_conntrack: table full, dropping packet in your log.
- Navigate to Firewall, Packet Filtering, Custom Firewall Rules.
- Add the following rule:
sysctl -w net.ipv4.ip_conntrack_max=<allowed number connections>
You can check the current value with
Yes, we need to update some KB articles which is currently in progress
In version 4 simply adjusting the memory allocation for connection tracking will affect this setting appropriately.
Did I read that right that the 560 can support more than 50K connections with the right settings?
In the v4 I'm not sure I ever understood how the memory adjustment tool worked. The 'current' settings that the router was using were far in excess of the 'maximum' listed. When I tried to increase the numbers in the fields, they increased some, but red-crosses appeared against the last category. It wasn't clear how to set the memory absolutely for as I adjusted the amount available for connection tracking up (wouldn't go higher than 5.5 even though I entered 7). So at this stage I gave up and reverted to the router running v3 bios.