Release Notes

ID Issue Description Workaround/Solution
21748 DR2000v FS was failing during boot on some
legacy Intel and AMD processors.
Corrected in version 3.1.2.
20766 DR Series deployment using a static IP may come
up in maintenance mode during initial boot as
default IP is not being assigned.
Corrected in version 3.1.2.
21893 Bash Security Fix - BASH Remote Code Execution
Vulnerability (ShellShock).
Corrected in version 3.1.1.
21873 During an upgrade from 2.x to 3.x under some
unusual corner cases, the latest configuration
database did not get backed up and tech support
had to correct the database.
Corrected in version 3.1.1.
21765 System with in-sync replication would show
pending bytes.
Corrected in version 3.1.1.
21690 During seeding, a network interruption caused
failure of seeding. When deleting a container and
attempting to reboot the system, the system
entered Maintenance Mode.
Corrected in version 3.1.1.
21667,
21079,
21000
Slow performance occurred on noisy networks. Additional TCP options were
enabled in the 3.1.1 release
for more effective TCP error
recovery.
21601 A Perc issue occurred if the drive greater than
2TB sent a UnitAttention check condition to the
Perc in descriptor format. This could cause the
drive to be taken offline.
Corrected in version 3.1.1
with new Perc firmware
(21.3.0-0009).
21538 Packet retransmissions may occur with
replication packets.
Customers should turn off
Deep Packet Inspection on
replication packets
(especially port 9916),
including GAV(gateway
antivirus), IPS (Intrusion
Prevention Service), Anti-
Spyware, etc.
To deal with TCP
retransmission issues, the
following is a check list for
troubleshooting packet
retransmission on the
Sonicwall side:
1. Check MTU settings.
The MTU settings are
located as follows:
• Firmware 6.x: Click
Advanced >
18