Known Issues
This section contains a list of known issues in the SonicOS 5.6.5.1 release.
| Symptom |
|
| Condition / Workaround |
|
| Issue |
|
In Active/Active clustering, a node cannot |
|
| Occurs when the node does not own a Virtual Group, |
| 97905 |
| ||
access MySonicWALL for license |
|
| which can occur when it is configured with factory |
|
|
|
| |
synchronization, and diagnostic tests to the |
|
| defaults and not aware of its A/A Clustering license, or |
|
|
|
| |
Default Gateway and DNS server fail. |
|
| when the license is activated, but the unit is not yet |
|
|
|
| |
|
|
|
| configured to own a Virtual Group. Workaround: |
|
|
|
|
|
|
|
| Before connecting the node to the A/A Cluster, register |
|
|
|
|
|
|
|
| the units and synchronize with MySonicWALL. |
|
|
|
|
|
|
|
|
|
|
| ||
The redundant port for the X1 WAN |
|
| Occurs when High Availability is enabled for |
| 97883 |
| ||
interface does not pass traffic after X1 is |
|
| Active/Passive mode, and X4 or another interface is |
|
|
|
| |
disconnected. |
|
| configured as a redundant port for X1, and then the X1 |
|
|
|
| |
|
|
|
| interface is physically disconnected. Workaround: |
|
|
|
|
|
|
|
| Disable High Availability and then traffic is passed on |
|
|
|
|
|
|
|
| the redundant port. |
|
|
|
|
|
|
|
|
|
|
| ||
The gateway IP address is wrong for |
|
| Occurs when a remote router or firewall is connected to |
| 97409 |
| ||
default routes received from OSPF. |
|
| a SonicWALL appliance (X1 on router is connected to |
|
|
|
| |
|
|
|
| a DMZ zone port (X2) on the appliance). OSPF is |
|
|
|
|
|
|
|
| enabled on both devices, the router advertises a |
|
|
|
|
|
|
|
| default route to the appliance, and the appliance adds |
|
|
|
|
|
|
|
| the default route to its routing table. However, the |
|
|
|
|
|
|
|
| gateway IP address for the default route is set to the IP |
|
|
|
|
|
|
|
| address of the router’s X1 interface, rather than to the |
|
|
|
|
|
|
|
| router’s gateway IP address. |
|
|
|
|
|
|
|
|
|
|
| ||
In Active/Active clustering, the IP address |
|
| Occurs when verifying NAT policies after running the |
| 95327 |
| ||
for interface X1, Virtual Group 2 reverts to |
|
| Public Server Wizard. The IP address for |
|
|
|
| |
the IP address for X1, Virtual Group 1. |
|
| Group 2 incorrectly displays the address for |
|
|
|
| |
|
|
|
| Group 1 instead. |
|
|
|
|
|
|
|
|
|
|
| ||
In a |
|
| Occurs when the policy is bound to Virtual Group 1 and |
| 93392 |
| ||
active Manual Key VPN policy tunnel does |
|
| a |
|
|
|
| |
not appear in the VPN settings of a backup |
|
| use on Node 1. |
|
|
|
| |
unit in Node 2, although traffic continues to |
|
|
|
|
|
|
| |
pass and the active unit shows the tunnel. |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| ||
When Active/Active clustering is enabled, |
|
| Occurs when the Packet Monitor filter settings are |
| 93188 |
| ||
settings for the Packet Monitor filter are |
|
| added before enabling Active/Active clustering. The |
|
|
|
| |
copied to the Display filter. The Display |
|
| Display filter contains these settings even after |
|
|
|
| |
filter settings cannot be removed. |
|
| manually clearing them and then restarting the |
|
|
|
| |
|
|
|
| SonicWALL appliance. |
|
|
|
|
|
|
|
|
|
|
| ||
When using Active/Active Clustering with |
|
| Occurs on Active/Active clusters with four nodes |
| 90256 |
| ||
four nodes where each node is part of HA |
|
| configured as HA pairs. Multiple WAN interfaces are |
|
|
|
| |
pair, traffic from the HA idle units cannot |
|
| configured and probing/probe target is enabled. When |
|
|
|
| |
go out and they cannot connect to the |
|
| one of the WAN interfaces is down, the default route of |
|
|
|
| |
License manager. |
|
| the idle units remain pointed to the down WAN |
|
|
|
| |
|
|
|
| interface. |
|
|
|
|
|
|
|
|
|
|
|
|
|
SonicOS Enhanced 5.6.5.1 Release Notes
P/N
5
