Juniper Networks | NetScreen Release Notes |
|
|
•03269 – The Juniper
•03267 – The
•03263 – When managing the device from the
•03261 – When you have two VPNs active between two devices, with outgoing interfaces, after the VPN Monitor deactivated the tunnel after nine seconds, and caused a failover to the secondary VPN, the device did not update the session information.
•03250 – A memory corruption caused the device to fail.
•03243 – In an instance where the client on the Untrust side of the device connected to a MIP that connected the server to the trust side, when an ASP began the server, it used a
•03239 – When you performed an FTP transfer or email download that went beyond the maximum bandwidth allocated in the traffic shaping feature, VOIP calls experienced a lot of intermittent voice transmissions.
•03235 – When you forcefully closed several PKA/RSA SSH sessions without properly logging out first, the system randomly failed several times.
•03232 – Under some conditions, an HA (High Availability) pair with a 5000- M2 module installed failed. This occurred when the primary device had 4,000 sessions on it and the backup device had 100,000 sessions.
•03205 – When running two Juniper
•03203 – The device sometimes failed when it traversed the session table.
•03178 – The device sometimes failed with high CPU and the full session table due to session memory corruption.
•03177 – Intermittent system failures occurred during an SNMP walk.
•03152 – When running XAuth in the WebUI environment, the XAuth page displays the CHAP fragment reassembly method selected by default.
•03142 – When you sent 64 bytes of packets through a
•03136 – Gratuitous ARP packets sent out to broadcast the presence of a device were blocked from being sent.
ScreenOS | P/N | Page 8 of 42 |