Need help with interface X1 load balancing.
I have LB enabled on my Sonicwall NSA 2600 firewall. Both links are up, but our main link status is in failover where both targets are unavailable. I can ping both targets and there are no packets dropped. Any idea what could be the issue and how to fix it? This started randomly Monday morning, everything was fine when I left on Friday. Not an ISP issue, I can plug directly into the modem and access the internet and I've tried rebooting the modem several times. The numbers on the modem are just blinking.I've tried changing the targets, but they remain unavailable. I am able to ping the X1 & X2 interface IPs using the diag tool within sonicwall fw, but not outside sonicwall.
Best Answer
-
kylakonen Newbie ✭
I ended up just calling our ISP to confirm they were routing our static IP block and it turns out it was offline. According to them it was due to "a change in their system", which didn't really answer my question, but they were able to refresh the block and get them online and this solved the issue.
1
Answers
@kylakonen did you ran a Packet-Monitor to make sure the Probe was really initiated?
Did you tried the Option Probe responder.global.sonicwall.com on all interfaces in this group?
Do you have any custom Network Routes which may cause this?
--Michael@BWC
This is what was found during the packet monitor:
Yes, I've tried using that probe on all interfaces, no change.
No custom routes.
This wasn't recently configured. I regularly test our failover and up until Monday (12/12), everything was working as it should.
Not sure if the below results will help? X1 and DNS Server 2 are from our ISP, but again, I am able to access the internet when plugged directly into the modem.
If I attempted to reboot the firewall, could it cause more issues than there are now?
I don't see any reason why a reboot could cause more harm. If your Firmware is not at 6.5.4.11 I would take the opportunity to combine the reboot with a firmware upgrade if you don't have special needs to keep your firmware at current level.
--Michael@BWC
update: no change after reboot