Difference between revisions of "Troubleshooting Tips"
From Tech-Wiki
Line 4: | Line 4: | ||
If you are facing strange behavior, in an advanced/illogic scenario, evaluate/review the following items in this order: | If you are facing strange behavior, in an advanced/illogic scenario, evaluate/review the following items in this order: | ||
# Policy | # Policy | ||
− | # NAT (correct NAT mode?) | + | # NAT (correct NAT mode? Does it require manual proxy arp?) |
# Routing | # Routing | ||
− | # Anti-spoofing (even from return packet) | + | # Anti-spoofing (even from return packet, check logs in opposite direction) |
− | # VPN Encryption domain | + | # VPN Encryption domain (for your and remote peer) |
− | # IPS (ips off) | + | # IPS (Use command: ips off) |
# Connection Limit (fw ctl pstat) | # Connection Limit (fw ctl pstat) | ||
− | # Disable SecureXL (fwaccel off) | + | # Disable SecureXL (Use command: fwaccel off) |
− | # Test in the other cluster member (clusterXL_admin down –p) | + | # Test in the other cluster member (Use command: clusterXL_admin down –p) |
# Issue a cpstop/cpstart or reboot | # Issue a cpstop/cpstart or reboot | ||
# Consider installing the latest Jumbo hotfix accumulator or Recommended Hotfixes (per sk106162 and sk106389) | # Consider installing the latest Jumbo hotfix accumulator or Recommended Hotfixes (per sk106162 and sk106389) |
Revision as of 14:37, 22 October 2018
If you are facing strange behavior, in an advanced/illogic scenario, evaluate/review the following items in this order:
- Policy
- NAT (correct NAT mode? Does it require manual proxy arp?)
- Routing
- Anti-spoofing (even from return packet, check logs in opposite direction)
- VPN Encryption domain (for your and remote peer)
- IPS (Use command: ips off)
- Connection Limit (fw ctl pstat)
- Disable SecureXL (Use command: fwaccel off)
- Test in the other cluster member (Use command: clusterXL_admin down –p)
- Issue a cpstop/cpstart or reboot
- Consider installing the latest Jumbo hotfix accumulator or Recommended Hotfixes (per sk106162 and sk106389)
- Did I forget something?!
- That’s probably a bug, raise a TAC
Confirm the reason of your packet being dropped using:
fw ctl zdebug + drop | grep 'x.x.x.x\|y.y.y.y'