My work environment uses a Peplink Balance 20x and we attempted to connect around 200 or so clients that needed to upload a small amount of data to our AWS storage. After 50-60 or so connected the router stopped handing out IP addresses. The DHCP scope was large enough to handle the amount of devices plus some. The data sheet recommends 1-60 users, but I did not think that would cause it to stop handing out IP addresses. The amount of traffic is not very large for each device. I’m wondering why it would not lease out more addresses.
Its not a hard stop at 60 users, so either you have an issue with your DHCP scope or the device had performance issues from the traffic. What do the utilisation graphs from IC2 show?
I don’t think it was the DHCP scope. It stopped handing out IPs across mutiple vlans. Unfortunately, the set up was temporary and I would now have to recreate the issue in a testing environment. You did answer my main question of whether or not the 60 users were a hard stop. I will keep digging. Thank you.
I have seen the Balance 20X CPU choke quite horribly from ARP traffic from much less clients than 200… shame Ic2 doesn’t log anything for CPU utilisation though.
We’d see the 20X start dropping pings to its LAN IPs and the Web GUI become totally unresponsive too.
Aside from the DHCP server not giving out addresses in your case was there anything else behaving strangely?
I didn’t notice anything strange, and any device connected before the DHCP server stopped handing out address continued to work without issue. I had about 60 devices I was trying to connect to the existing network that would not get IPs. I moved them to a separate network with a different router and DHCP server to get them up and running. I then had to clear the leased addresses from the Peplink (I only cleared one Vlan) in order to get it to hand out IPs again. It was a work around because of time constraints.