I am a small MSP and have been getting requests recently for failover internet connections for my customers. I have used devices in the past utilizing different cell data connections tied into SonicWall Firewalls to achieve this with the success you’d expect.
Since having started my business I decided to get my customers a reliable solution and after some research and comparisons, I decided to five into a MAX-BR1-ENT-LTEA-R-T modem. The device was put into a bridge mode to send its WAN connection right to the SonicWall and it is up to the SonicWall to monitor the normal ISP connection through cable internet to decide if it needs to failover to the Pepwave for an alternative Internet source.
I thought this was set up and working beautifully after testing. The customer was happy and life moved on. This was back in October. However, recently there have been reports of network troubles and poor call quality over VoIP, dropped VPN connections, and you name it. My finger immediately went to the SonicWall and the investigation told me the CPU’s Core 0 is constantly spiking to 100% on the SonicWall.
Support said this is an issue they were seeing as a configuration problem and went through settings until they eventually caved and sent me an RMA device. The RMA arrived today and I decided to set it up on the Pepwave connection to minimize downtime for the client. The sad part is that the same behavior was seen after configuration and even with factory settings. This was a bummer. I went back to the old SonicWall and saw that the CPU behavior now was normal. This immediately tells me that the source of my problem is this Pepwave modem.
Has anyone seen anything like this or does anyone have any suggestions? Could I be setting up the Pepwave incorrectly and possibly using it to send the WAN IP to the SonicWall is a poor choice? I am just looking for any suggestions to help resolve this issue.
Thanks ahead of time.