Juniper Networks ScreenOS Release
Notes
Release 6.3.0r4
July 2010
Revision 01
Products: Integrated Security Gateway (ISG) 1000, ISG 1000-IDP, ISG 2000, ISG

2000-IDP, Secure Services Gateway (SSG) 5, SSG 20, SSG 140, SSG 300M-series, SSG
500/500M-series, and NetScreen-5000 series (NS 5000–MGT2/SPM2 and NS
5000–MGT3/SPM3).

Contents

Version Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
New Software Features and Enhancements Introduced in 6.3.0 . . . . . . . . . . . 5
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Antivirus (AV) and Web Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Border Gateway Protocol (BGP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Internet Protocol Security (IPsec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Internet Protocol Version 6 (IPv6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
ISG-IDP Diagnostic Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
NetScreen Redundancy Protocol (NSRP) . . . . . . . . . . . . . . . . . . . . . . . . . 11
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Changes to Default Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Changes to Default Behavior Introduced in 6.3.0r4 . . . . . . . . . . . . . . . . . . . . . 14
Changes to Default Behavior Introduced in 6.3.0r3 . . . . . . . . . . . . . . . . . . . . . 14
Changes to Default Behavior Introduced in 6.3.0r1 . . . . . . . . . . . . . . . . . . . . . . 15
Network and Security Manager (NSM) Compatibility . . . . . . . . . . . . . . . . . . . . . . . 15
Detector and Attack Objects Update (only for ISG-IDP) . . . . . . . . . . . . . . . . . . . . . 15
Addressed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Addressed Issues in ScreenOS 6.3.0r4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
ALG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Copyright © 2010, Juniper Networks, Inc.

1

ScreenOS 6.3.0 Release Notes

Antivirus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
HA & NSRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
IDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
WebUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Addressed Issues from ScreenOS 6.3.0r3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Antivirus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HA and NSRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
IDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
WebUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Addressed Issues from ScreenOS 6.3.0r2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Antivirus (AV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Deep Inspection (DI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Domain Name System (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
General Packet Radio Service (GPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
High Availability and NetScreen Redundancy Protocol (HA and
NSRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Intrusion Detection and Prevention (IDP) . . . . . . . . . . . . . . . . . . . . . . . . . 26
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Voice-over-Internet Protocol (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Virtual Private Network (VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
WebUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues from ScreenOS 6.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Application Layer Gateway (ALG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Antivirus (AV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Deep Inspection (DI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Domain Name System (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
General Packet Radio Service (GPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
High Availability and NetScreen Redundancy Protocol (HA and
NSRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Intrusion Detection and Prevention (IDP) . . . . . . . . . . . . . . . . . . . . . . . . . 31
Internet Protocol Version 6 (IPv6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Voice-over-Internet Protocol (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Virtual Private Network (VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
WebUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Known Issues in ScreenOS 6.3.0r4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
DI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
HA & NSRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
IDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Known Issues from ScreenOS 6.3.0r3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Known Issues from ScreenOS 6.3.0r2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Antivirus (AV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
General Packet Radio Service (GPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Intrusion Detection and Prevention (IDP) . . . . . . . . . . . . . . . . . . . . . . . . 38
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Virtual Private Network (VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Copyright © 2010, Juniper Networks, Inc.

3

ScreenOS 6.3.0 Release Notes

Known Issues from ScreenOS 6.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
General Packet Radio Service (GPRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Intrusion Detection and Prevention (IDP) . . . . . . . . . . . . . . . . . . . . . . . . 39
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Voice-over-Internet Protocol (VoIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Virtual Private Network (VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Concepts and Examples ScreenOS Reference Guide . . . . . . . . . . . . . . . . . . . 40
ScreenOS IPv4 CLI Reference Guide: Command Descriptions . . . . . . . . . . . . 41
Limitations and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Limitations of Features in ScreenOS 6.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Getting Help for ScreenOS 6.3.0 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4

Copyright © 2010, Juniper Networks, Inc.

Version Summary

Version Summary
ScreenOS 6.3.0 firmware can be installed on the following products: Secure Services
Gateway (SSG) 5, SSG 20, SSG 140, SSG 320M/350M, SSG 520/520M, SSG 550/550M,
Integrated Services Gateway (ISG) 1000, ISG 1000-IDP, ISG 2000, ISG 2000-IDP, andNetScreen-5000 series with the NS 5000-MGT2/SPM2 and NS 5000-MGT3/SPM3.
This release incorporates bug fixes from ScreenOS maintenance releases up to 6.2.0r5,
6.1.0r7, 6.0.0r8, and 5.4.0r15.

NOTE:
•

If you are using an SSG 500-series device and an SSG 500M-series device in a
NetScreen Redundancy Protocol (NSRP) environment, all devices must be running
ScreenOS 6.0.0r1 or later.

•

NSRP clusters require the use of the same hardware products within a cluster. Do
not mix different product models in NSRP deployments. The exception to this rule is
SSG 500-series and 500M-series devices, which can be used together in a cluster.

New Features and Enhancements
The following sections describe new features and enhancements available in the
ScreenOS 6.3.0 release.

NOTE: You must register your product at http://support.juniper.net to activate licensedfeatures such as antivirus (AV), deep inspection (DI), and virtual systems (vsys) on thedevice. To register your product, you need the model and serial numbers of the device.
At the support page:•

If you already have an account, enter your user ID and password.

•

If you are a new Juniper Networks customer, first create an account, then enter yourID and password.

After registering your product, confirm that your device has Internet connectivity. Use
the exec license-key update all command to connect the device to the Juniper Networks
server and activate your desired features.

New Software Features and Enhancements Introduced in 6.3.0
The following sections describe the new features introduced in the ScreenOS 6.3.0
release.

Copyright © 2010, Juniper Networks, Inc.

5

ScreenOS 6.3.0 Release Notes

Authentication•

User Authentication—Beginning with ScreenOS 6.3.0, the Juniper Networks security
device supports authentication redirection for HTTP traffic that is directed to a
nonstandard destination port.

Antivirus (AV) and Web Filtering•

Sophos Anti-Spam to replace Symantec Anti-Spam—Beginning mid-September
2009, Sophos Anti-Spam service will be made available to the ScreenOS-based
products; SSG, and ISG. The Sophos Anti-Spam service will replace the Symantec
Anti-Spam.
There will be no impact to customers running any version of ScreenOS. No configuration
changes are required. The redirection to Sophos servers will be automatic andtransparent to the end-user. The security devices will be pointed to the Sophos servers.

•

Juniper Full Antivirus Database—Beginning with ScreenOS 6.3.0, Kaspersky Lab
supports only a single antivirus database known as Juniper Full Antivirus Database.
The existing databases such as extended, itw and standard are removed.

•

Virus Description and Alert Message—If the data sent to FTP or HTTP Traffic contains
a virus, the security device replaces the data with a warning message or drops the data.
In both cases, a message with a URL link that describes the virus is logged.
For SMTP, IMAP and POP3 Traffic, the security device in addition to the above, changes
the content type to text/plain, replaces the body of the message with a notice and a
URL link that describes the virus, sends it to the appropriate recipient, and notifies thesender.

•Web Filtering Whitelists and Blacklists Without a License—Web filtering supports
the following features even if the license key is not installed or has expired:•

Define Web-filtering profiles and bind them to policies•

Retrieve category information for HTTP requests•

Define static whitelist and blacklist categories•

Check cache for categories

NOTE: The device does not support checking the cache for categories if the key is notinstalled, but it does support this check if the key is expired.

•

6

Integrated Web Filtering Based on Group Membership—In the previous release, the
URL filter profile was bound to policy. Beginning with ScreenOS 6.3.0 release, theadministrator can bind the profile to user group. The Web Filtering (WF) Manager
extracts the URL from the request and identifies the username and user groupassociated with the IP address. If the user belongs to multiple user groups, the WF
Manager binds the profile with the user group that has highest priority. Then, the WF

Copyright © 2010, Juniper Networks, Inc.

New Features and Enhancements

Manager identifies the category of the URL and permits or blocks the request
accordingly. User groups can be prioritized.
•

Increased Number of Web-Filtering Profiles on SSG 500–series—For integrated Web
filtering, the number of customer-defined profiles for SSG 550 and SSG 520 devices
is increased to 300 profiles from 50 (SSG 550) and 25 (SSG 520).

Border Gateway Protocol (BGP)•

Redistributing Routes in BGP—For each virtual router (VR), BGP can support up to
17000 redistributable routes. The increase in redistributable routes in BGP to 17000
applies to the NetScreen-5000 platforms only.

•

Display Format of BGP Community Lists—Beginning with ScreenOS 6.3.0, theconfiguration file displays the BGP community lists in a new AA NN format, where AA
identifies autonomous system and NN identifies community. This new format is incompliance with RFC-1997.

Device Management•

Enabling Syslog on Backup Devices—Backup devices in an Active/Passive NSRP
configuration can now send all syslog messages to the syslog server, allowing an
administrator to effectively monitor the backup devices. By default, this feature isdisabled.

•

Simple Network Management Protocol Version 3 (SNMPv3)— ScreenOS 6.3.0
supports SNMPv3 framework. System status data can be collected securely from thedevice without the data being tampered with and corrupted. The SNMPv3 USM allows
ScreenOS to encrypt the confidential information to prevent the contents from being
exposed on the network. The SNMPv3 VACM provides a configurable access control
model for easy administration.

•

Interface Administrative Status—ScreenOS 6.3.0 supports a command for setting
an interface administrative status to the down state. By default, the administrative
status of an interface is set as up. The administrator can disable the administrative
status of an interface with the CLI:
set interface xx disable•

Increased Number of Hosts per SNMP Community—Beginning with the ScreenOS
6.3.0 release, you can configure 64 hosts per SNMP community. In earlier releases of
ScreenOS, this value was limited to no more than 40 hosts per SNMP community.

•

Include Device Serial Number in Log Messages—Beginning with the ScreenOS 6.3.0
release, for system logs, the device serial number is used as a unique device identifier
within the logs.

•

VLAN1 Interface to Support DHCP and AUTO Configuration—Beginning with the
ScreenOS 6.3.0 release, the VLAN1 interface of a device in transparent mode supports
the DHCP client and AUTO CONFIG features.

•

Loading Configuration from USB—When the SSG device initializes, and if theadministrator has configured envar properly, then ScreenOS can check if the USB
device is connected to the port and loads the configuration file usb: auto_config.txt (ifthe file is stored in the USB device).

Copyright © 2010, Juniper Networks, Inc.

7

ScreenOS 6.3.0 Release Notes

Internet Protocol Security (IPsec)•

AC VPN Enhancements—ScreenOS 6.3.0 supports dual-hub Auto Connect virtualprivate network (AC-VPN) where one hub remains active, passing the traffic from one
spoke to another spoke until a dynamic VPN tunnel is established. The hub with thehighest routing instance priority becomes the active one. The spokes use the VPN
monitoring feature to check the status of the hubs. When the hub acting as a primaryfails, the dynamic tunnel and its associated NHRP routing instance are removed atboth the spokes. Traffic begins to pass through the other hub, which creates a new
dynamic tunnel. If the failed hub comes back, the spokes choose this hub again becauseof the priority setting. However, the traffic continues to flow through the newly createddynamic tunnel until the other fails.

•

Support for Multiple Proxy IDs Over Route-Based VPN—ScreenOS 6.3.0 supports
multiple proxy IDs on a route-based VPN. If multiple tunnels exist between peers, thesecurity device uses proxy IDs to route the traffic through a particular tunnel. For eachproxy ID, a specific tunnel and Phase 2 SA are associated. When traffic matching a
proxy ID arrives, the security device does a proxy-ID check to route that traffic. If multiple
proxy IDs are defined for a route-based VPN, a proxy ID check is always performed,
even if it is disabled. In a hub-and-spoke topology, proxy IDs should be defined for both
hub-to-spoke and spoke-to-spoke configurations.

•

DPD Enhancement—ScreenOS 6.3.0 provides a DPD enhancement that allows thedead peer to failover the tunnel to another VPN group member with the second highest
weight. It uses the DPD reconnect parameter to renegotiate the tunnel with the deadpeer at specific intervals. If the tunnel is successfully renegotiated, the tunnel fails backto the first member.

•

Elliptical Curve Diffie-Hellman Key Arrangement—ScreenOS 6.3.0 supports ellipticalcurve Diffie-Hellman (ECDH) groups 19 and 20 for Internet Key Exchange version 1(IKEv1) key exchange. ECDH uses elliptical curve cryptography to generate public-private
key pair. The module sizes of DH groups 19 and 20 are 256 bits and 384 bits ECDH
prime curves, respectively.

•

Support Authentication Header Transport Mode—[ISG 1000/2000, NS 5200/5400
M2/SPM2 , NS 5200/5400 M3/SPM3] ScreenOS 6.3.0 supports authentication header(AH) transport mode on high-end systems for IPv4 packets only. This feature does notwork if IPv6 is enabled in the system environment.

•

IKEv2 Configuration Payload (CP) and Dial-up Support—Support for IKEv2
configuration payload (CP) for dynamic end points and IKEv2 dial-up group user VPN
is available in this release. For details on the implementation, refer to the Concepts &Examples ScreenOS 6.3.0 Reference Guide.

Internet Protocol Version 6 (IPv6)•

Support OSPFv3 for IPv6 —Beginning ScreenOS 6.3.0, Juniper Networks security
device supports OSPFv3 for IPv6. Most configuration and operational commands
function essentially the same as in OSPFv2.
OSPFv3 does not support the following features:•

8

NBMA link and neighbor authentication

Copyright © 2010, Juniper Networks, Inc.

New Features and Enhancements•

Demand Circuit and NSSA•Multiple instances per link.

OSPFv3 is supported across all platforms. However, advanced mode license is required
to run it on the following devices:•

ISG1000•

ISG1000 with SM•

ISG2000•

ISG2000 with SM•

Command to Inhibit AAAA Requests Over IPv4—ScreenOS 6.3.0 provides an option
to enable or disable the Network Address Translation-Port Translation Domain Name
System Application Layer Gateway (NAT-PT DNS ALG) to modify DNS requests
received from the IPv6 domain. Besides translating the addresses for transmitted DNS
requests, the NAT-PT DNS ALG also modifies the DNS request before forwarding it toanother domain that has only IPv4 addresses. By default, this option is disabled.

•

IPv6 Prefix and DNS Information Update—ScreenOS 6.3.0 supports dynamic IPv6
prefix and DNS information update from the upstream DHCPv6 server. A CPE router
acting as a DHCPv6 and PPPoE client negotiates IPv6 prefixes and DNS information
for the downstream DHCPv6 server on the other interface of the same CPE router. If
the connection between the CPE router and the upstream DHCPv6 server isdisconnected and then re-established, the CPE router updates the newly learned IPv6
prefix and DNS information dynamically on the downstream DHCPv6 server without
waiting for the delegated prefix to expire.

ISG-IDP Diagnostic Improvements•

IPv6 Full Support on ISG-IDP—Beginning with ScreenOS 6.3.0, ISG Security Module
provides IPv6 support for the following features: packet capture and packet logs for
IPV6 traffic; configure header match information for IPv6 traffic and ICMPv6 messages;
IPv6 traceroute anomaly; IPv6 log messages in the NSM log viewer.

•

ISG-IDP Means to Identify the Secure Module (SM) Used by a Session—Beginningwith ScreenOS 6.3.0, users can identify which SM card and CPU a session is using. It
is possible to filter the session table output with the CLI command get session sm-slot
slot-id sm-cpu cpu-no.

•

Command for Displaying CPU Usage on SM—Beginning with ScreenOS 6.3.0, users
can enable the security device to calculate the CPU usage of the ISG Security Module
for the last 60 seconds, last 60 minutes, and last 24 hours by using thesc_enable_cpu_usage parameter.

•

Transfer Core Dump to the Management Module Flash or Compact Flash—Beginningwith ScreenOS 6.3.0, users can transfer the core dump files from the RAM disk of the
ISG Security Module to the flash memory of the management module using the CLI
command set sm-ctx coresave.

•

SNMP Trap and Event Log Entries for ISG with IDP—From ScreenOS 6.3.0, ISG Security
Module supports generating log messages and SNMP Traps when CPU usage, memory

Copyright © 2010, Juniper Networks, Inc.

9

ScreenOS 6.3.0 Release Notes

usage, and session count per IDP security module exceeds the user-defined threshold.
The device also generates messages when it detects an IDP security module failure.

NOTE: The user-defined threshold value is not stored in NSM. The value is reset to thedefault once the system reboots.

•

Inspection of Multicast traffic by IDP Security Module—Beginning with ScreenOS
6.3.0, users can enable ISG Security Module to inspect multicast traffic by using the
CLI command set flow multicast idp.

NOTE: For multicast traffic inspection, all outgoing interfaces should belong to thesame zone.

•

UAC Integration with Role-Based IDP Policy—From ScreenOS 6.3.0, ISG Security
Module can support role-based IDP policy. Administrators can configure the security
device to inspect traffic using either user roles or source IPs. When user-role-based
IDP inspection is selected, the security device starts checking user-role-based policies
first; if a match is not found, only then the security device searches for IP-based rules.
This feature requires UAC deployment and role information is provided by Infranet
Controller.

Network Address Translation (NAT)•

Enhancement to IKE and ESP Passthrough Traffic—Beginning with ScreenOS 6.3.0,
Network Address Translation (NAT) supports both NAT-Traversal and
Non-NAT-Traversal IKE and IPsec passthrough traffic. The Application Layer Gateway(ALG) is enabled to support interface NAT and IKE DIP pool NAT.

•

Support for More Than 62946 Sessions per IP in a DIP Pool —When the security
device performs NAT-src with a DIP pool containing an IP address range with PAT
enabled, each DIP:DPort pair can only be assigned to one session. Beginning with
ScreenOS 6.3.0, you can enable DIP to support multiple sessions per DIP:DPort. The
DIP pool supports multiple session per DIP:DPort only if two packets have different
destination IP addresses. After configuring the DIP pool scale size, every IP addresscontains multiple port pools that consist of all available ports for an IP address. Every
IP can support up to scale-size* 62463 sessions.
The maximum scale size for an interface cannot exceed the DIP scale size value
specified in the vsys profile.

•

TCP Session Close Notification—ScreenOS sends a TCP session close notification
ACK message to both the client and the server when a session is being closed.
To enable a policy to send TCP session close notification, complete the following
prerequisites:

10•

You must enable TCP SYN checking and TCP reset options in both the client andthe server zones.

•

You must enable TCP sequence check only for ISG 1000/2000 and NS 5200/5400.

Copyright © 2010, Juniper Networks, Inc.

New Features and Enhancements•

Creating a Session Cache to Accelerate HTTP Traffic—Beginning with ScreenOS
6.3.0, you can create a session cache for HTTP-based protocols to minimize CPU
utilization and to enhance performance. A session cache is a special structure thatcaches all the reusable information of both software and hardware sessions createdby the first connection of an HTTP session bundle.
A session cache supports other traffic but does not ensure performance enhancement.
You cannot create a session cache for the following conditions:••

When the session is synched from another security device.

•

When the session is created by an Application Layer Gateway (ALG).

Importing Traffic to the Correct VSI by Proxy ARP—The administrator can enable
importation of traffic to the correct VSI by setting the proxy ARP entry. Upon adding a
proxy ARP entry on an interface, ScreenOS imports the traffic that is destined to the
IP range using this interface.
You can use the CLI command proxy-arp-entry or WebUI Network > Interface > Edit>
Proxy ARP Entries to set the proxy ARP entry.

•

NAT-Dst Port Shift using VIP—Using the port-range VIP entry, a range of ports can bemapped between Virtual IP and Real Server IP.

NetScreen Redundancy Protocol (NSRP)•

Add More Detail to the Output of get nsrp—The output of the get nsrp vsd-groupcommand includes a new column; the uptime column for VSD group or myself uptime
column for current security device denotes the duration in the primary or backup state.

Other
•

Hot Patch Management—Beginning with ScreenOS 6.3.0, the hot patch enables
injecting the customer service patch into the running image without rebooting thesecurity device. The hot patch as debug patch provides for easier debugging.
The ScreenOS hot patch management component runs on the security device andperforms the following functions:•

Loads the hot patch file from TFTP to flash memory•

Removes the hot patch file from flash memory•

Maintains the patch finite state machine (FSM)•

Cache Recently Used Route and ARP Entries—Beginning with ScreenOS 6.3.0, Juniper
Networks security device allows the user to cache recently used route and ARP entries
for destination routes by using the set flow route-cache command. This feature does
not work if ECMP is enabled.

•

Ability to Add exec and save Commands to Scripting Tool—Beginning with ScreenOS
6.3.0 release, the ScreenOS scripting tool supports the exec and save commands.
These commands are visible in the script context record. The parser identifies thesecommands in the script record context and saves them into the script. Thisenhancement enables the user to execute commands that facilitate troubleshooting.

Copyright © 2010, Juniper Networks, Inc.

11

ScreenOS 6.3.0 Release Notes•

Timeout for Track IP—Beginning with ScreenOS 6.3.0, the user can set the maximum
timeout value for track IP.

•

Boot with Default Gateway IP—The new ScreenOS boot loader allows you to define
a default gateway IP, then user can download image from a remote TFTP server.

•

Identifying Gigabit Interface—Beginning with ScreenOS 6.3.0, users can identify thetype of gigabit interface using the CLI command get interface interface-name.

•Boot Loader for SSG and Boot ROM Version for ISG or NetScreen–5000 series
Displayed in CLI—Beginning with ScreenOS 6.3.0, you can view the boot loader for an
SSG device and boot ROM version for ISG or NetScreen–5000 device using the getsystem command.
Example 1:
ssg20-> get system
BOOT Loader Version: 1.3.2

Example 2:
nsisg2000-> get system
BOOT ROM Version: 1.1.0
•

•

12

WELF Log Format Enhancement—Beginning with ScreenOS 6.3.0, enhancements
have been made to the event log, traffic log and IDP log formats to follow the WELF
log regulation. If backup for the logs is enabled, logs can be sent to a maximum of four
Webtrends servers. TCP or UDP transport protocol can be used for communication.
IP connections can be manually reset. The following log types must be sent along withthe appropriate heading prefix:•

Configuration log [Config Change]•

URL Filter Detection [URL filtering]•

AntiVirus Detection [AntiVirus]•

Antispam Detection [AntiSpam]•IPS/DI Detection [IPS/DI]•

Screen Attack [Attack]

SCTP Protocol Filtering—Beginning with ScreenOS 6.3.0, the existing Stream Control
Transmission Protocol (SCTP) stateful firewall supports protocol filtering. You canconfigure the security device to permit or deny traffic based on the SCTP Payload
Protocol and M3UA Service Indicator. The Payload Protocol identifies the type of data
being carried out by the SCTP data chunk, the M3UA Service Indicator identifies thetype of data being carried out by the M3UA data message. Based on the Payload
Protocol, you can create an SCTP profile and bind it to a policy.

Copyright © 2010, Juniper Networks, Inc.

New Features and Enhancements

NOTE: ScreenOS supports SCTP protocol filtering on NetScreen-5000 and ISG series
devices only.

•

Converting join-group igmp Commands to exec join-group—Beginning with ScreenOS
6.3.0, the exec join-group and exec leave-group commands replace the set igmp
join-group and unset igmp join-group commands. The exec join-group command replaces
the set join-group command. The exec leave-group command replaces the unset
join-group command. There is no impact on the functionality of the commands. The
set and unset commands are deprecated.

Policies•

Policy Installation Enhancement —Beginning with ScreenOS 6.3.0, the policy
installation process has been enhanced.
The new process provides the following advantages:•

Avoids frequent policy re-installation caused by dynamic DNS address changes.

•

Eliminates traffic drops while installing the policy.

•

Allows the user to configure the hold-interval option of policy installation using thefollowing CLI command:set policy install hold-interval seconds

The default value is 5 seconds. The minimum is 0 and the maximum is 10. This
command specifies the maximum time interval between when policy configuration
occurs and actual policy installation begins. When the user creates a new policy ormodifies an existing policy, the policy installation is delayed by up to the value ofhold-interval value specified. This allows the system to more efficiently process thesession table by handling several updates at once or by reducing the thrashing causedby extremely rapid updates.
unset policy install hold-interval

The unset command resets the default value of hold-interval.
Example: To configure hold-interval option to 2 seconds:
set policy install hold-interval 2

Routing•

IRDP Support for All Platforms—Beginning with ScreenOS 6.3.0 release, ICMP Router
Discover Protocol (IRDP) support is available on all platforms; however, IRDP support
is available only on an Ethernet interface with an IP address.

•

DSCP Marking for Self-Initiated Traffic—The administrator can configure the DSCP
value for traffic initiated by the security device. The DSCP value can be configured for
11 services: BGP, OSPF, RIP, RIPNG, TELNET, SSH, WEB, TFTP, SNMP, SYSLOG, andWEBTRENDS. You can use both the CLI and the WebUI to configure DSCP marking.

•

QoS Classification Based on Incoming Markings—In ScreenOS 6.3.0, traffic-shaping
policies are enhanced to support quality of service (QoS) based on the IP precedence

Copyright © 2010, Juniper Networks, Inc.

13

ScreenOS 6.3.0 Release Notes

and Differentiated Services code point (DSCP) marking of incoming packets. The QoSclassification feature for incoming traffic works only if the traffic-shaping mode is set
to Auto or On.

Security•

Denial of Service Attack Defenses—ScreenOS 6.3.0 supports the feature of strict
TCP-SYN-check wherein a strict syn check is applied to all the packets in a TCP
three-way-handshake before the three-way handshake completes. Users can enable
this feature by using the set flow tcp-syn-check strict command.

•

Verification of IP address in ASIC Whitelist—Beginning with ScreenOS 6.3.0, users
can verify if a specific IP-address is in the ASIC whitelist by using the get asic ppu
whitelist ip-address command.

•

Support for SecurID Server Cluster—RSA supports a primary server and up to 10 replica
servers to process authentication requests. At least one of primary or slave servers
must be configured with static IP. RSA SecurID Server Cluster supports the namelocking, load balancing, and failover functions.

Changes to Default Behavior
This section lists changes to default behavior in ScreenOS 6.3.0 from earlier ScreenOS
firmware releases.

Changes to Default Behavior Introduced in 6.3.0r4•

NSRP Configuration—NSRP configuration is out of synchronization due to set tftp
source-interface <interface name> command.

Changes to Default Behavior Introduced in 6.3.0r3

14•

Increase in the capacity of number of service objects and address groups—For ISG
Series, the capacity of number of service objects and address groups is increased to4096. For NS 5000, only the capacity of number of service objects is increased to
4096.

•

Maximum timeout value of ipsec-nat alg—The maximum value of ipsec-nat alg timeout
has been changed from 180 to 3600 seconds.

•

VPN tunnel capacity for advanced license key—On SSG550, the VPN tunnel capacity
has been changed from 1000 to 2048 for advanced license key.

•

Unexpected Low VPN Throughput—When VPN monitor is configured for VPNs on
NetScreen-5200 or NetScreen-5400, the device can define sub-optimal ASIC mapping
for processing VPN traffic in the hardware which causes unexpected low VPN
throughput. A new command set flow ipsec-distr-asic is introduced to include theenhancement that VPN encryption will be distributed into different chips based on thetunnel's SA index per round robin. By default, it is disabled. This is applicable for
NetScreen-5000 series only. For NetScreen-5000 series with VPN on IPv6 environment,
enabling this command is not recommended as it would yield less than optimal
performance.

Copyright © 2010, Juniper Networks, Inc.

Network and Security Manager (NSM) Compatibility

Changes to Default Behavior Introduced in 6.3.0r1•

The set igmp join-group and unset igmp join-group commands for the interface aredeprecated. If you execute the set/unset igmp join-group commands, the following
warning appears:
WARNING: This command is a deprecated command and cannot be saved toconfiguration. Please use the following new preferred syntax:
exec igmp interface if_name join-group group_addr [{ include | exclude| to_include|to_exclude} sources_ip ]•The CLI command set interface interface nameproxy-arp-entry ip_min ip_max takes
precedence over the existing set arp nat-dst command. This means that when theproxy ARP entry is defined and matched, then the system does not respond to the ARP
request via the physical interface.
Because the set interface interface nameproxy-arp-entry ip_min ip_max command allows
the customer to have better control of the device, the command set arp nat-dst is notrecommended.

•

The SNMP changes might affect the management software as follows:•

Logical interfaces are added to the interface table.

•

Several new SNMP traps are introduced in the ScreenOS 6.3.0. For details on the
new SNMP traps, see the change history of published ScreenOS 6.3.0 MIB
NS-TRAPS.mib.

You can consider modifications as required.

Network and Security Manager (NSM) Compatibility
This section provides information about updates required to complementary Juniper
Networks products to ensure their compatibility with ScreenOS 6.3.0.
Support for ScreenOS 6.3.0 has been introduced with NSM 2009.1r1. Navigate to the
Support webpage for more information: http://www.juniper.net/support.

Detector and Attack Objects Update (only for ISG-IDP)The Detector Engine shipped with this ScreenOS version is 3.5.134907. For more
information on the availability of new releases, see Detector Engine Release Notes at
http://www.juniper.net/techpubs/software/management/idp/de/.
After you have performed the ScreenOS firmware upgrade, you must update to the latest
IDP Detector Engine and Attack Object database:1.

Download the latest detector and attack database to the NSM GUI server. From
NSM, select Tools > View/Update NSM attack database, and complete the wizard
steps.

2.

Push the detector update to the ISG-IDP devices. From NSM, select Devices > IDP
Detector Engine > Load IDP Detector Engine, and complete the wizard steps.

Copyright © 2010, Juniper Networks, Inc.

15

ScreenOS 6.3.0 Release Notes

3.

Push a policy update to the ISG-IDP devices. From NSM, select Devices >Configuration > Update Device Config, and complete the wizard steps.

Addressed Issues
The following operational issues from ScreenOS 6.2, 6.1, 6.0, and 5.4 release branches
were resolved in this release:

Addressed Issues in ScreenOS 6.3.0r4
The following operational issues were resolved in this release:

Administration•

467398—Local root user sometimes lost root privilege when the remote admin used
the same user name.

•496029—While managing the firewall using SSH Secure Shell v.3.2.9, firewall reported"Potential replay attack detected on SSH connection initiated from x.x.x.x."•

501075—The VeriSign CA certificate had expired and was invalid. It could be removed
from the system as the system already contained a valid VeriSign CA certificate. The
valid certificate could be seen with get pki x list cert command.

•

504196—SSH management sometimes disconnected abruptly when large output
commands were executed.

•

508319—The device sometimes rebooted unexpectedly when the memory got
overwritten by the EAP task.

ALG

16

•

498113—In certain conditions, with RTSP ALG enabled, the RTSP traffic failed throughthe firewall.

•

498869—Fragmented MSRPC packets were supported in the ALG.

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues

Antivirus•

498121—In certain scenarios, with AV enabled, the HTTP slows down due to TCP
retransmission.

Authentication•

503196—The source interface option for authentication (auth) did not work when
LDAP was configured as the AUTH server.

CLI•

484141—System rebooted unexpectedly when get sip transactions command was
executed.

DHCP•

495244—DHCP custom option 43 was sent with an invalid length.

HA & NSRP•

515159—The backup device used virtual MAC for ip tracking in a PPPoE environment
using interface redundancy.

IDP•

507318—IDP Engine failed on security module and created core file.

•513071—With application identification enabled, invalid pointers had created an issue.

Management•491132—ICMP packets to the management interface experienced delay at regularintervals.

•

494629—SNMP trap was not sent to indicate that the CPU utilization had returned tonormal level.

•501026—The exec policy verify command did not work for the group service.

•502845—The firewall rebooted unexpectedly when the L2TP policy was removed
through NSM.

•

503139—Under certain conditions, during an SNMP walk, the firewall sometimes
rebooted unexpectedly.

Other
•

419637—Many drop notification messages between IC and IE caused instability in the
SSH connection between them.

•

471425—The event log displayed interface flapping messages within the same secondon the firewall, but the other end of the connection did not record interface flapping
messages within the same second on the firewall.

•

485192—The GRE packets of PPTP session were dropped sometimes if PPTP server
CALLID was set to 0.

•

488614—The set zone <zone name> tcp-rst command did not work for SSH on high-end
platforms.

Copyright © 2010, Juniper Networks, Inc.

17

ScreenOS 6.3.0 Release Notes

18•

491466—SQL connections failed sometimes when the SQL ALG was enabled.

•

492796—[NS5000] Under certain conditions, only software sessions were created
when there was no destination MAC address entry of the packet in the MAC learning
table. As a result, subsequent packets were flooded and the CPU utilization was high.

•494276—A URL blocked by Websense sometimes did not display the corresponding
blocked message in the browser in an asymmetric routing environment.

•

494617—ScreenOS devices managed by NSM version 2009 or above sometimes
encountered memory leak issue.

•

494946—[SSG 300] The alarm LED did not turn red when large ICMP packets weredetected.

•

495554—Firewall rebooted unexpectedly when the policies changed and read at thesame time.

•498529—The SNMP get query for BGP related OID sometimes provided an incorrect
output.

•498562—IPv6 did not work on PPPoE ADSL interface.

•

499421—With edipi enabled, XAUTH user cannot inherit the IP information from old
XAUTH session when rekeying new SA leading to memory leak.

•

500495—With antispam enabled, e-mail with attachments greater than 3 to 4 MB
sometimes dropped due to out of memory error.

•

500843—Output of SNMP walk sometimes displayed incorrect interface for ARP table
entries.

•501256—The Translated Dest column was empty when the traffic logs were saved
using WebUI.

•

501343—Even though there was no incoming traffic, alarm traffic for policy increased,because the self traffic was denied by the deny policy.

•

502419—Traffic shaping statistics were not displayed on the NSRP VSI interfaces on
the firewall.

•

504084—The track IP failed sometimes when the interface was inactive.

•

505456—Event log displayed "system temperature severely high" message even when
the temperature of the device was appropriate and the hardware was in good condition.

•

505554—Traffic log for large PING over MTU size was displayed as close-ageout
instead of close-resp.

•

506473—Radius server was not reachable when the source interface was not theVirtual Security Interface (VSI).

•

506543—Parsing a folder with the name "quit" abruptly closed the FTP session.

•

509166—SSG5 wireless device was not able to locate the best channel under certain
conditions.

•

510473—Typo in infranet enforcer mode test command resulted in syntax error after
reboot.

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues•

511026—The implementation of IKEv2 DoS attack prevention was incorrect.

•

511812—When a BGP neighbor was configured and an outgoing route map was applied,the firewall did not apply the local preference correctly as specified in the policy terms.

•

512752—In certain conditions, failure of the infranet controller connection caused highCPU condition on the device.

•515064—In certain conditions, it was possible to define a custom service object for
protocol 0.

•520662—Under certain conditions, the get alg pptp xlat command sometimes caused
the device to reboot unexpectedly.

Performance•

494910—[SSG 140] In certain circumstances, when there was heavy traffic throughthe interface, all the traffic passing through the interface e0/9 was blocked.

Routing•

501996—In case of multiple virtual routers (VRs), sometimes, deleting a multicast
route from one VR might not update information in the other VR causing the device toreboot unexpectedly.

•

504708—With NSRP sync route enabled, the redistribution of routes from BGP to
OSPF was delayed.

•

505962—The RIP packets were constructed twice with the same RTE, but with different
metrics.

•

501953—The redistributed default route did not get advertised in the OSPFv3.

VoIP•

511469—Limitation on the maximum h245 channel number was 10. This limitation
caused problem with certain VoIP applications.

•

517439—URI of SIP message was modified incorrectly when NAT with SIP ALG was
used.

VPN
•

441805—The ikmpd task caused periodic high task CPU peaks.

•

500203—ASIC based firewall sometimes stopped passing traffic when ESP packets
with invalid SA value were received.

•

502729—VPN failed to come up when the outgoing interface was a loopback interface.

•503323—After deleting a VSYS, the system log erroneously displayed error messages
related to deleting a tunnel zone, and SSH PKI key associated with that VSYS.

•

504014—In some scenarios, VPN policy with MIP failed to translate Proxy ID.

•

505065—VPN policy with domain name was not updating the right proxy-id after
reboot.

•508886—Netscreen Remote Client for dial up VPN did not failover to redundantgateway when track-ip failed.

Copyright © 2010, Juniper Networks, Inc.

19

ScreenOS 6.3.0 Release Notes

WebUI
•

496267—The tunnel interface erroneously appeared inactive in the WebUI and readyin the CLI when the VPN monitor was disabled.

•

496418—WebUI configured as a web bookmark did not open in a new window on an
SA Series page.

•502098—Sometimes, the device rebooted unexpectedly when the vpn name waschanged.

•504696—Potential unauthorized disclosure vulnerability was found, when the private
address of the firewall was sometimes disclosed.

•

506282—Whitelist URL was blocked by URL filtering because the code did not identify
the port number (non 80) in the hostname header.

•

507172—Sometimes, the firewall rebooted unexpectedly when WebUI was accessed.

•

513085—In the WebUI, under certain conditions, MIP configuration for IPv6 address
was not available.

•

515172—Alarm events for DI detection were missing in an exported report from the
WebUI.

Addressed Issues from ScreenOS 6.3.0r3
The following operational issues were resolved in this release:

Administration

20•

417686—Socket leak might occur when Internet Explorer (IE) with HTTPS was used
for WebAuth management.

•

472816—Sometimes the clear socket <socket id> command could not clear the tcp
socket when it was in a certain state.

•480480—Under certain conditions, memory leak in the event log module caused highmemory utilization.

•

481730—The get system command displayed the hardware version as 0000(0)-(00)on SSG300 and SSG500 devices.

•

493627—Under certain conditions, device might reboot unexpectedly when RPC(MS-RPC or SUN-RPC) traffic passes through the device and show rpc map command
was executed.

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues

Antivirus•

478469—In transparent mode, VLAN tag was removed from the HTTP traffic after AV
scanning.

DHCP•

484087—The destination IP was incorrectly set to 0.0.0.0 when DHCP relay agent
received a DHCP ACK in response to a DHCP INFORM.

GPRS•

448582—GTP inspection dropped the SGSN Context Response message if the Next
Extension Header type was 0xC2 (Suspend Response).

•

449284—In certain conditions, the firewall failed to allocate GSN, and hence caused
the GTP traffic to drop.

•

456358—The common flags GTP Information Element was not removed when set
remove-r6 command was configured.

•457093—For a new GTP tunnel, CreatePdpRequests from an SGSN were dropped if
the response was not received before a certain time period.

•

472199—When R6 IE removal was enabled, GTP CreatePdpRequest packets got
corrupted when both the MS-Time zone information element and a private extension
were present.

•

485578—The GTP remove-r6 feature removed the mandatory RAI IE from SGSN
Context Request and Identification Request messages.

•

485911—Support had been added for removing Information Element '184 - Bearer
Control Mode' using the GTP remove-R6 feature.

•486613—When GTP traffic dropped, the bad system status message appeared in thelog.

HA and NSRP•

472083—When NSRP track-ip monitoring was configured within vsys, configdata file
had incorrect track-ip information.

IDP•

467521—[ISG-IDP] In certain conditions, processing of RPC packets caused memory
allocation problem which eventually caused the security module to hang.

•

485928—[ISG-IDP] The IDP engine resets due to application identification.

•

493618—[ISG-IDP] IDP engine core dumps frequently due to DFA cache memory
corruption.

Management•455186—Firewall running OSPF rebooted unexpectedly after a delta configuration
through NSM was performed.

•

456690—The traffic log did not display IPv6 addresses correctly.

Copyright © 2010, Juniper Networks, Inc.

21

ScreenOS 6.3.0 Release Notes•

459999—The set flow vpn-tcp-mss command was not available for configuring in
NSM.

•

466692—The SNMP IPv6 IfIndex value was reported as incorrect from the firewall.

•

468514—Traffic log was not generated for a source or destination port equal to 1503.

•

468659—E-mail notifications for logs from the firewall were not formatted correctly.

•

470754—[NetScreen-5000] The redundant interface reported overflow errors when
it was not initialized correctly after a system restart.

•

471298—UDP MSRPC EnDPort mapper (MS-RPC-EPM) traffic incorrectly displayed
the traffic log as MSRPC ENDPOINT MAPPER (TCP).

•

485725—Firewall socket issue caused higher task CPU than expected which caused
the management through web and SSL to fail.

•485946, 470729—Event log message displayed <username> turn off debug switch
for all when admin exited the CLI.

•

485958—Source interface of secondary NSM server was incorrectly removed fromthe configuration.

•

491026—SNMP walk for certain MIBs did not return any value.

NAT•

450989—Unable to access MIP configured on loopback group from different zones
on the firewall.

•

480667—The firewall allocated vsys limit for configuring MIPs to a shared interface
in root-vsys instead of global limit.

Other

22

•

463515—MAC entries in the bgroup mac-table were not cleared after an interface went
down.

•

465718—Under certain conditions, the device might reboot unexpectedly when a
Dial-Up user tried to connect.

•

466619—The set license-key auto-update command rolled back to unset after a device
reboot.

•472178—The set zone trust screen udp-sweep threshold command enabled the
tcp-sweep option.

•

472433—Packet might be corrupted due to ASIC buffer problem.

•

472690, 264366—ICMP flood screening option incorrectly dropped packet andgenerated alarm even when the packet rate was lower than the configured threshold.

•477561—The guaranteed bandwidth parameter was incorrectly allocated in traffic
shaping.

•

479300—In some scenarios, non-impacting messages such as “TR installing ready
reverse wing” were logged to the debug buffer.

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues•

479752—Under certain conditions, the device might reboot unexpectedly when running
get config datafile command.

•

480179—When the SC-CPA server was inaccessible, the device displayed UF-MGR:
Internal error: Failed to allocate uf_record event.

•

481096—Enabling the set log audit-loss-mitigation feature caused the device to halt
traffic after the log buffer was filled.

•481805—The bandwidth settings configured on the gigabit subinterfaces were notloaded after reboot.

•484133—With unknown protocol protection disabled, traffic with protocol number
greater than 137 was dropped erroneously.

•

484169—Firewall might reboot unexpectedly if GBIC card was not properly initialized
during boot up.

•

484839—In some scenarios, firewall might restart unexpectedly if get alg pptp xlate
command was executed.

•

485332—PIM register message was dropped when the inner packets were fragments.

•

486445—The device might reboot unexpectedly due to its access to a NULL pointer.

•486896—Event log timestamp was changed because of NTP update.

•

489167—The session was torn down while changing multi-cell policy if RPC was oneof the service cell.

•489205—In IPv6, the MTU was not changed according to an ICMP6 "Packet Too Big"error message.

•

490158—[Netscreen-5000] In some scenarios, the firewall stopped forwarding traffic
and was also not accessible through in-band access.

•490176—An upgrade for SSG140 running a dual boot image using SCP (secure copy)
required the device to reboot twice.

•491531—TCP session might be broken when failover occurs from one tunnel to theother due to wrong TCP Window Scaling Factor in hardware session.

•

492544, 491555—In certain situations, TCP-based SIP traffic in the environment could
cause the firewall to reboot unexpectedly.

•

498306—[SSG 300/500] Under certain conditions the firewall would reboot
unexpectedly when UAC was configured.

Performance•

413433—[SSG-500] Internal sanity check caused higher CPU than expected resulting
in intermittent packet drops.

•

478205—When large amount of WebAuth transaction takes place at a time, some
HTTP SYN packets might drop during TCP 3-way handshake without returning SYN
and ACK packets.

•

491967—Policy search was slow with complex and larger number of policy
configurations causing high CPU utilization.

Copyright © 2010, Juniper Networks, Inc.

23

ScreenOS 6.3.0 Release Notes

Routing•466158—Capability negotiation error between BGP peers caused BGP to stay in idle
state.

•

473625—Under certain conditions, multicast traffic did not match the longest matching
multicast group policy.

•

474158, 446155—Change in RPF source route or change in route towards the RP was
not reflected properly to the multicast routing table.

•

480470—BGP anti-flap processing was removed from the backup NSRP node.

•482372—In some scenarios, IBGP did not send updates to some of the BGP peers.

•483854—OSPF neighbor relationship was lost on active primary connection when the
backup link flapped.

•

485608—Firewall failure dump was caused by the BGP route updates.

•

490020—In specific circumstances OSPF converged incorrectly.

VoIP•

458341—SIP ALG did not handle the SIP calls that used multi-part message as
expected.

•

484227—SIP MIME and Multipart messages were modified on the firewall that caused
the SIP packets to drop.

VPN

24

•

472618—NS-Remote IPsec phase one negotiation failed when IKE ID was changed.

•475831—Quotation marks (" ") were removed from configuration when the set vpn
vpn_name bind zone "zone_name" command was used.

•

479107—The VPN proposals ordered through WebUI of the firewall was ambiguous
and could lead to unintended selection of the proposal between the VPN peers.

•480642—User could not pair a VPN policy when multiple MIPs were used as destination.

•

480691—The VPN tunnel down message (for example, VPN <vpn-name> from
<IP-address> is down) was not generated in the event log when the NSRP backup
device became the master.

•

482399—AC-VPN failed to connect from one Spoke to another Spoke VPN site in the
NAT-T scenario.

•

486043—Firewall might reboot unexpectedly when IKE/CLI and flow module accessed
the NHTB table at the same time.

•

486608—The set vpn <vpn> dscp-mark <dscp> command for manual VPN failed to
set the DSCP marking for outgoing ESP packets.

•

489859—In some scenarios, when the firewall was reset, the tunnel interface status
remained down even when the security association (SA) was up.

•

494667—Incorrect proxy-id with VPN Policy having MIP and overlapping source anddestination address.

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues

WebUI
•

291948—When the device had many event log entries, refreshing the main WebUI
page or the report page using Report > System Log > Event action caused high CPU
utilization.

•

450974—Enabling or disabling the Java or ActiveX component also unsets IP Spoofing.

•

474665—In vsys, for IKE gateway configuration, option to select shared root interface
was not available in the outgoing interface drop box in the WebUI.

•

479160—Unable to save AutoIKE configuration for VPN phase 2 in the WebUI when
Proxy ID was enabled and vpn group was selected.

•

479440—“unknown keyword ipv6” error was displayed when using VPN wizard forvpn setup with IPv6 disabled on the firewall.

•

480387—“The value of time-out cannot be greater than interval” was displayed forcertain interval values greater than the threshold values when creating Track IP entry
using the WebUI.

•

493414—In the WebUI, when the user clicked Go or New button to open a policies
menu, the device rebooted unexpectedly.

•

495940—WebUI incorrectly displayed the tunnel interface status as inactive.

Addressed Issues from ScreenOS 6.3.0r2
The following operational issues were resolved in this release:

Administration•

445491—When displaying BGP route advertised without specifying a neighbor address,
the error bgp neighbor 0.0.0.0 doesn't exist is displayed.

•

456101—[ISG, NetScreen 5000] The port mirror command displayed erroneous Failed
command - set mirror port source ethernet4/1 destination ethernet1/1 message on consolebootup, even though the command existed in the configuration file and was working.

Antivirus (AV)•458125—In transparent mode, with the UTM enabled, when preparing a child session
in the ALG traffic, the VLAN tag information was lost.

Authentication•

416043—The device did not clear the existing System Information Block (SIB) when
the associated radio caused the wireless authentication failure.

•471517—Protocol version check caused the RSA SecureID authentication failure.

Copyright © 2010, Juniper Networks, Inc.

25

ScreenOS 6.3.0 Release Notes

Command Line Interface (CLI)•

462860—[SSG 140/300/500, ISG 1000/2000, NetScreen 5GT] After a reboot, theunset admin hw-reset command was not saved.

Deep Inspection (DI)•454303—When a DI policy was enabled, and the ip-action was "notify", the packet
that matched the DI group specified in the policy got dropped.

Domain Name System (DNS)•

458316—A device might reset if a vsys that contains address book objects with DNS
names was deleted.

•471892—DNS queries did not work when device was configured to use itself as DNS
server (when DNS proxy is enabled on an interface).

General Packet Radio Service (GPRS)•

437975—With GTP inspection enabled, at times, the GTP Echo Response might drop
and the log displays the bad state message.

High Availability and NetScreen Redundancy Protocol (HA and NSRP)•

448011—Under certain conditions, WSF was not being updated in hardware session.

•

449011—[SSG 140, SSG 300, SSG 500] When Active/Passive NSRP in L2 mode isconfigured, some traffic might stop for a few minutes just after failover under a specificcondition.

•

449858—Non-VSI PPTP session was not functioning as expected in NSRP
Active/Passive scenario.

•

454981—[SSG 300M] When NSRP failover occurred, the red LED alarm was triggered.

•461079—[NetScreen 5000] The backup firewall would prematurely remove thesessions on the master in a VSD-less NSRP cluster and cross-ASIC traffics.

•

463752—In NSRP Active/Active mode, if tcp syn-check was enabled, the user could
not update the session after the three-way TCP handshake was complete.

Intrusion Detection and Prevention (IDP)•

431797—Packets were dropped when the TCP Error Reassembler Packet Memory
Exhausted signature was enabled.

Management26•455868—[SSG Devices] Number of tasks has been increased on SSG devices to allow
management to the device.

•473110—Format of IPv6 addresses were being sent incorrectly to NSM log viewer.

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues

Network Address Translation (NAT)•455943—When the PPTP service and GRE service timeout are configured to never,the PPTP xlate fills up unless the PPTP connection is shutdown.

Other
•

302382—In certain conditions, the firewall might reset if a session incorrectly references
a MAC address without route information.

•

387173—Traffic was blocked intermittently because of an error in handling non-IDP
traffic as IDP sessions.

•

432190—[NetScreen 5000 M3] VLAN retag did not work properly with 10 Gig interfaces.

•

437660—Firewall reboots due to MGCP traffic.

•

448252—[SSG 300] In transparent mode, the NMAP scan caused packet going acrossthe firewall to drop.

•

449239—SQL ALG did not function as expected when client request came into the
SQL server's MIP address.

•

451051—[ISG] Internal memory corruption caused ISG devices to stop creating new
sessions and hence impacted traffic.

•

455183—Few packets might be dropped due to ASIC reinit.

•

455373—The device resets when some SQL ALG registers access an odd address.

•

455405—ALG for FTP, RSTP, GTP, SQL, SIP, and RSH was corrupting the control
packet which in turn was causing problems with the data packet.

•

459357—WebAuth redirect from firewall contains a corrupted target URL when a proxy
was used and the HTTP-request was split into two packets. The first packet includes
the GET line and the second packet includes the HOST line.

•

460233—With DST enabled, the e-mail notification time from ScreenOS was an hourahead of the actual time.

•461492—When SQL IPMP failover was performed, subsequent traffic did not passthrough the firewall.

•

462783—Under certain conditions, sessions with timeout of 0 or 1 were never agedout of the firewall.

•

463422—New TCP did not pass through the firewall in Transparent mode if there wasno matching MAC table entry.

•

465223—The get gbe id 1 CLI command causes the device to reset.

•

468821—Double quotation mark (" ") was not accepted in the middle of a commentor description for the definition of an address, route or group policy objects.

•

473279—The debug nsm nsp-debug command might result in system reset.

Copyright © 2010, Juniper Networks, Inc.

27

ScreenOS 6.3.0 Release Notes

Performance•

455350—MTU was set to 1500 when a tunnel interface causing performance issues
was added to the interface.

Routing•433987—Memory leak because of large OSPF LSA might reset the device.

•

435956—Firewall removed some RP-set when it received BSR messages with a tag
zero.

•

436444—Device might reset if IGMP v3 source specific report was sent.

•

448691—BGP routes can get stuck in route table if two neighbors send the same prefixroute and routes change frequently.

•

449723—Firewall might reboot because of incorrect scheduling of SPF algorithm for
the OSPF protocol.

•

459513—Unable to set IPv6 static route to null interface.

Voice-over-Internet Protocol (VoIP)•

422611—Power Cycling H.323 IP Phone resulted in NAT pport leak.

•

442077—H.323 calls failed when it exceeded 10 OLC channels.

•

442660—Incorrect format of INVITE messages resulted in random failure of VoIP calls
using SIP.

•

472554—[SSG 140] Maximum number of NAT cookies has been increased to 512.

Virtual Private Network (VPN)

28•442719—Unable to configure a C Class Broadcast IP address for the IKE Gateway
address.

•

448720—Unable to remove User Group that was previously bound to a VPN, evenafter that VPN has been removed.

•

452080—The TCP 3-way handshake failed because of an error in the setup of IPsec
VPN.

•

455520—Tunnel interface was not created when route based VPN configuration was
pushed from the NSM.

•

459053—A logically down interface might still respond to VPN monitor packets sent
by a VPN peer device, and hence not allowing the VPN state to go down.

•

459239—Xauth information was erroneously removed when initial-notify was received.

•

474622—[IKEv2] Tunnel IP address did not get released when Dial-Up IKE v2 SA was
terminated.

•

474923—[IKEv2] Rekey is unsuccessful when using Dial-Up VPN.

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues

WebUI
•

455462—Using the WebUI, when an aggregate BGP route was added, a new option
summary-only was added that was not specified in the WebUI.

•

459894—Unable to remove the address book object "DMZ Any" after it was configured.

•

463137—IRDP cannot be enabled on interface e0/0 using the WebUI.

•

465697—In certain conditions, the WebUI management causes the system to reset
because of incorrect parameter value.

•

468211—In the WebUI, the IPv6 route entry did not accept uppercase characters for
an IPv6 address.

•

469439—VPN monitor configuration might rollback to default after editing vpn entry
from the WebUI.

Addressed Issues from ScreenOS 6.3.0
The following operational issues were resolved in this release:

Administration•

309759—Reloading configurations while the device is experiencing heavy traffic mightcause the device to fail.

•388700—It is currently possible to configure a VIP from a subnet other than theunnumbered tunnel interface IP. However, this is not a supported configuration; admins
should not be allowed to configure a VIP from a subnet other than the unnumberedtunnel interface IP.

•

414839—The policy logs in syslog did not show the correct data sent or received for
FTP.

•

416873—After a reboot, some event log entries were not recorded in the syslog file,when the syslog was configured using UDP.

•

429883—The MSS-based sockets were changed on the new accepted socket.

•

432014—The authorized user with read and write privileges is able to issue the set
admin password command because of which some user privileges are lost.

Application Layer Gateway (ALG)•

446420—The Microsoft windows management interface (WMI) control service fails
in some scenario.

Antivirus (AV)•299960—Using the new Kaspersky Labs antivirus scan engine, the antivirus databasetakes a relatively long time (1 to 5 minutes) to load from a flash disk to system memory.
While the database is loading, CPU usage might go extremely high and device
performance might drop.

•

388885—The extended antivirus (AV) pattern file was too large for the flash memory
devices that support this function. However, the standard antivirus pattern file worked

Copyright © 2010, Juniper Networks, Inc.

29

ScreenOS 6.3.0 Release Notes

as expected. ISG 1000/2000 and NetScreen 5000-series devices do not support theextended AV pattern file setting.

Authentication•

429374—Re-authentication for dot1x was not handled correctly.

Command Line Interface (CLI)•

435979—[SSG 500] The output of the get chassis command does not include PIM
name.

•

392417—The set tag <number> command under vsys was not configured correctly.

Deep Inspection (DI)•410393—When updating offline from the Local Server, the automatic DI signature
update fails.

•

426280—The attack db rollback command did not work on some platforms. For theother platforms, the result of the command was logged as either successful or failedin event log.

Domain Name System (DNS)•

439044—If syslog server is referenced using DNS hostname, syslog messages are stillsent to the original IP address even after the IP address of the hostname is changed.

Flow•235781—Using transparent mode, under high traffic conditions, sometimes a small
number of sessions cannot be cleared. The sessions appear to be "time 0" but continue
to remain in the session table. Running set sat session-clean clears these sessions fromthe table after one round of session cleaning.

•239631—If you configure the initial session timeout below the valid range (20–300
seconds), the system interprets these values as minutes instead of seconds.

General Packet Radio Service (GPRS)•

422979—When GTP inspection was enabled, ICMP Destination Unreachable packetsof the GTP session were dropped.

•

426075—When GTP inspection was enabled, occasionally a DeletePdpResponse or
EchoResponse dropped and the message non-existent gsn appeared in the log.

High Availability and NetScreen Redundancy Protocol (HA and NSRP)

30•235303—Delay in the peripheral devices updating the forwarding table when a failover
occurs in an NSRP cluster in transparent mode. When the devices have no gratuitous
ARP mechanism as in NAT or Route mode, peripheral devices update the forwarding
table only when the active physical interface is restarted. The update happens after
five seconds by default.

•

236275—In transparent mode, if the VSD group is not bound to a VLAN group, thesecurity device incorrectly reports the VSD as being in Active-Passive mode.

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues•

236634—In an Active-Passive configuration, if the active security device handles alarge number of FTP connections, the CPU utilization of the backup device remains
high even when the rate of the FTP connections per second on the backup is low.

•

253467—If a device's SIP traffic is very heavy in an NSRP deployment, although themaster box works well, there are delays when resources on the backup box are removed.
Operational impact on the cluster is minimal, and the backup box recovers
automatically.

•

303714—For NSRP cluster deployments, when upgrading from ScreenOS 5.4 (or any
earlier release), the following ALGs do not sync correctly until both devices in the pairare upgraded: SIP, SCCP, MGCP, RTSP, SQL, PPTP, P2P, AppleiChat, and H.323.

•

422747—In the Active/Active mode, FIN packet in the NSRP data path is not processed
correctly when SYN-CHECK is enabled.

•

424242—When performing an NSRP failover, the route pointed to a different tunnel
interface. However, the synchronized session continued to point to the old SA tunnel.

•

437661—The RIP and OSPF MD5 authentication results in the NSRP configuration are
not in synchronization.

•

438794—Backup NSRP firewall lost synchronized OSPF routes.

Intrusion Detection and Prevention (IDP)•

305128—If only a destination port (dst-port) is specified in IDP flow filter, the filter
does not capture traffic in both directions.

•

305295—If an IDP rule is configured with the attack value NONE, then diffserv does
not work. Also, when the IDP rule attack value is NONE, if a TCP packet that matches
the drop packet action passes through the device, IDP is unable to escalate the responseand drop the connection.

•

410393—When updating offline from the Local Server, the automatic DI signature
update fails.

•

426280—The attack db rollback command did not work on some platforms. For theother platforms, the result of the command was logged as either successful or failedin event log.

Internet Protocol Version 6 (IPv6)•

227934—SSG platforms incorrectly process the ICMPv6 error packet that they receivein response to a non-first fragment packet that exceeds the outgoing interface MTU.

•

236085—In transparent mode, you cannot manage a zone that is on a vsys using thezone nsrp manage CLI command, because it is a global setting based on vlan1 interface.
In root mode, you can manage only the related vsys.

•

236087—On SSG 320/350 devices, a 4-byte PVE tag is used to identify which interface
the packet came from, limiting the maximum supported packet length to 1514 bytes.

•

236549—When deployed in transparent mode, some high-end platforms such as ISG
1000-IDP do not support more than 20 reassembled segments. If you try to ping anotherdevice with data that requires more than 20 reassembled segments (for example,
30,000 bytes), the ping request fails.

Copyright © 2010, Juniper Networks, Inc.

31

ScreenOS 6.3.0 Release Notes•

239285—ScreenOS does not verify the IP address that you enter when you configure
the security device.

•

239598—On some high-end platforms, after you have enabled IPv6, the CLI incorrectly
allows you to enable parameters such as DSCP marking, IDP, and NSRP Data
Forwarding that are not supported in IPv6 mode.

•

267239—When modifying an IPv6 or a wildcard policy through the WebUI, all existing
sessions for the policy are removed. However, existing sessions are not removed if you
only modify some minor features—such as session-limit or alarm-without-drop—of
an ordinary IPv4 policy through the WebUI.

Management•218168—The incorrect range in integrated URL filtering SC-CPA cache is causing NSM
validation error.

•

272925—When the console timeout is set to 0, telnet client applications have no way
to determine when a session has timed out. If the telnet client has not sent data for asignificant length of time and the session should timeout, the TCP socket for the telnet
session might not be correctly released.

•292490—NSM update fails when configuring IKEv2 soft lifetime buffer.

•

438684—The set flow mac-cache-mgt command is not working for the managementof the backup firewall using the master firewall.

Network Address Translation (NAT)•

403509—DIP leaks when a loopback interface for cross-Vsys is used simultaneouslywith a loopback group in the destination vsys for outgoing DIP NAT.

Other

32

•

255774—The debug command unset console dbuf might make the box unstable,
especially under heavy traffic. Administrators are advised to use care when running
this command.

•

258931—Due to a memory limitation, NS 5000 devices are currently unable to support
500 vsys when an advanced license key—such as for virtual router or Layer 2
Active-Active support—is part of the deployment.

•

263480—When a small second packet follows a jumbo frame (more than 8500 bytes)
on 10G card within a minute, then it might be dropped.

•

263512—ScreenOS 6.1.0 includes a new SSHv2 secondary login banner feature.
However, unless the feature is enabled, if the secondary banner is displayed before alogin prompt on a console or via a Telnet connection, no positive acknowledgment tothe secondary banner is required (applicable to console, Telnet, SSHv1, and SSHv2
connections).

•

263585—In certain situations, Network Address Translation (NAT) traffic using H.323
ALG resets the device.

•266022—Because the NS 5400 supports 2 million sessions by default in 6.1 (and6.0.0r2 and later), you must ensure that the device has a minimum of 450MB of free

Copyright © 2010, Juniper Networks, Inc.

Addressed Issues

memory when upgrading from 5.4 or 6.0.0r1 to 6.1.0 or 6.0.0r2. One million sessions
require approximately 340MB of memory.
•274425—The drop of to-self IKE packets is not logged when no IKE is configured.

•

278668—[SSG 550/550M] An error in the boot-loader code caused the interface
references to be switched and the motherboard version to be incorrectly reported while
upgrading from boot mode.

•

312046—On some devices, an attempt to negotiate the maximum transmission unit
(MTU) using the ICMP "packet too big" packet might fail. Failure to negotiate the MTU
might, for example, cause an FTP session failure. The failure is caused in part because
the ICMP packet is sent only once.

•

387143—The alarm LED is cleared automatically without issuing the clear led alarm
command.

•391304—The duration of time reported by policy traffic logs is shorter than the actual
time duration.

•

393301—During Web authentication, when an ACK packet was received, the firewall
erroneously sent a FIN packet to end the session.

•

413775—[ISG] The set sat sess-close [0|1] command did not function as expected.

•

416573—When the debug command was run, the redundant debug information wasremoved.

•419564—The ppp multi link bundle supports only two BRI channels.

•

427094—Occasionally, the connection between the Catalyst switch and the Copper
Gigabit interface with manual duplex setting is down.

•

427467—[SSG 140] The device reboots unexpectedly because of ARP traffic acrossbgroup interfaces.

•

428914—[ISG, NetScreen-5000] When Websense was enabled, access to certain
websites dropped due to application error.

•

429239—When the remote authentication server was primary, the authentication
failback option did not function as expected.

•

431675—The defragmentation limit is changed to support up to 65535 bytes of IP
packet.

•431762—During an upgrade to Release 6.1.0r5, MGCP-related messages might appear
on the console.

•

431944—In transparent mode, MPLS pass-through traffic is dropped.

•

433456—The original source and destination address are missing from the log to USB
flash.

•

435348—[SSG 5/20, SSG 140, SSG 500] The firewall could reset due to an exception
before the boot up process. The device shows the exception dump.

•

439759—When an access list that is tied to an RP configuration for multicast is not
set, the firewall might reboot.

Copyright © 2010, Juniper Networks, Inc.

33

ScreenOS 6.3.0 Release Notes•

440546—The antivirus scanning process might get stuck the SMTP sessions, if theclient is using SMTP DSN (Delivery Status Notification) and the recipient's e-mailaddress contains word QUIT.

•

441723—Firewall does not send TCP RST for traffic matched by IPv6 REJECT policies.

Performance•

297405—Inter-Vsys traffic are dropped if it do not pass through an ALG or ICMP.

Routing•258978—For the SSG 320M/350M, the supported maximum number of Border Gateway
Protocol (BGP) redistributed routes is 4096. However, if a large number of routes areadded with an automated script, it is possible to exceed the supported limit. Routes
entered or redistributed manually should not be able to exceed 4096.

•

398277—OSPF adjacencies were lost due to an FPGA error.

•

416966—When a route was displayed by get route command some of the flags were
not freed, and the firewall rebooted. The route was frequently added and deleted bychanging dynamic routing.

•430932—Secondary VPN Tunnel configured with point to multi-point OSPF stopped
in ExStart.

•

440113—IPv6 Neighbor solicitation messages from the source “::” are dropped by IP
Spoofing.

Voice-over-Internet Protocol (VoIP)•

310928, 314481—In NAT mode, the security device might stop responding under heavy
Media Gateway Control Protocol (MGCP) traffic.

•

421768—When the H.323 ALG was enabled, the H.323 RAS admissionConfirm packets
were dropped.

Virtual Private Network (VPN)

34•395216—The fragmented packets of cross-chip ASIC VPN traffic were dropped.

•

395312—When Baltimore Unitrust CA was used, the PKI negotiation using the SCEP
failed.

•430028—The device reboots when auto renewal of the same SCEP key was performed.

•

433028—The device reboots on its own when SCEP auto-renewal of the same key is
performed.

Copyright © 2010, Juniper Networks, Inc.

Known Issues

WebUI
•

393022—ECDSA signature authentication is missing from the authentication methods
list in the IKE phase 1-proposal editing WebUI page.

Known Issues
The following are known deficiencies in features at the time of this release. Wheneverpossible, a workaround is suggested following the problem description, preceded by
W/A.

Known Issues in ScreenOS 6.3.0r4
The known issues listed in this section are specific to ScreenOS 6.3.0r4. For the known
issues identified for previous ScreenOS releases, see the Release Notes for the specificrelease.

Administration•

511835—The configuration might get deleted while configuring the administration
setting for custom L2-zone.

Authentication•

511019—802.1X authentication fails after PC hibernation.

•

528252—The firewall sends multiple WebAuth requests to the user when a single
HTTP request is split into multiple packets.

DHCP•

510653—Unable to configure DHCP option string with a length greater than 128 bytes.

DI•528641—Under certain conditions, after DI attack signature update, the configured"action" in attack policies becomes incorrect.

HA & NSRP•

509803—Software sessions on backup firewall do not ageout properly because of its
inability to synchronize time with its master unit.

•

519838—Both firewalls in NSRP cluster might become master.

IDP•

522728—Under certain conditions, changing inline-tap mode to inline might cause
traffic to drop.

Management•

505106—Under certain conditions, NSM policy push might cause policies to be marked
as "invalid".

•

520991—After reboot, the unset http skipmime mime-list command is added to theconfiguration.

Copyright © 2010, Juniper Networks, Inc.

35

ScreenOS 6.3.0 Release Notes•

522075—TCP sweep and UDP sweep screen options cannot be configured using NSM
because these options are missing in the ScreenOS config datafile.

•526797—When DNS response is fragmented, the reason for session close in the traffic
log becomes ageout.

•529788—NSM view statistics might cause the device to reboot unexpectedly with
dump.

NAT
•

512224—MIP translation between IPv6 addresses fail to translate.

Other
•

442729—Traffic might stop on an interface when the system chip fails.

•

478573—[SSG 300] The device sends corrupted IP packets on reboot.

•483101—The Elliptical Curve Diffie-Hellman (ECDH) IKE implementation populates
both group type and description in the Payload, and causes interoperability issue withthird party VPN devices.

•

503307—Application-Specific Integrated Circuit (ASIC) hangs and stops passing traffic
due to incorrect session pointer.

•

509654—[SSG 140] TX/RX Led remains ON even after set interface ethernet0/X phy
link-down command is executed.

•

513394—A problem with the counter statistics generation causes the firewall to reboot
unexpectedly.

•

518253—[SSG Series] Mapped IP (MIP) of the firewall does not respond to ARP querywith source IP of 0.0.0.0.

•519557—Firewall might drop packets in transparent mode if syn-flood is enabled.

•

522349—Signatures with 30 or more characters get truncated while passing throughthe syslog output.

•

526215—"Policy:Not Found" error is displayed when the user tries to add a new policy
with "before id" and "DSCP enable value" keywords together.

•

529690—ESP pass-through traffic does not consider custom service timeout when
the custom ESP service is part of a service group.

•529736—The policy scheduling options "Recurring" and "Once" do not work together.

•532937—The firewall incorrectly allows the user to configure an IPv6 MIP and then
DIP with the same address.

Routing

36•528011 —In specific circumstances, BGP does not send updates on routes that are
unreachable.

•

528417—Redistributed default IPv6 route in OSPFv3 is not advertised after an hour ofredistribution.

Copyright © 2010, Juniper Networks, Inc.

Known Issues

VoIP•

529845—With SIP ALG enabled, the firewall might experience high CPU.

VPN•

469089—The VPN monitor does not function for a manual key VPN because a proxy
id check is added on the packet sanity check, which is not required for a manual key
VPN.

•

506464—Under certain conditions, the device might reboot unexpectedly related to
RSA authentication.

Known Issues from ScreenOS 6.3.0r3
The known issues listed in this section are specific to ScreenOS 6.3.0r3. For the known
issues identified for previous ScreenOS releases, see the Release Notes for the specificrelease.
None.

Known Issues from ScreenOS 6.3.0r2
The known issues listed in this section are specific to ScreenOS 6.3.0r2. For the known
issues identified for previous ScreenOS releases, see the Release Notes for the specificrelease.

Antivirus (AV)•478469—In transparent mode, VLAN tag is removed from the HTTP traffic after AV
scanning.

DHCP•

484087—The destination IP is incorrectly set to 0.0.0.0 when DHCP relay agent receives
a DHCP ACK in response to a DHCP INFORM.

General Packet Radio Service (GPRS)•

448582—GTP inspection drops the SGSN Context Response message if the Next
Extension Header type is 0xC2 (Suspend Response).

•

456358—The Common Flags GTP Information Element is not removed when set
remove-r6 command is configured.

•457093—For a new GTP tunnel, if a CreatePdpRequest does not receive any response,
then the already used TEIDs cannot be reused for a certain time period. This can resultin the dropping of CreatePdpRequests from an SGSN that reuses these TEIDs before
a certain time period.

•

472199—When R6 IE removal is enabled, GTP CreatePdpRequest packets get corrupted
if they contain both the MS-Timezone information element and a private extension.

•

485578—The GTP remove-r6 feature removes the mandatory RAI IE from SGSN
Context Request and Identification Request messages.

•

486613—When GTP traffic drops, the bad system status message appears in the log.

Copyright © 2010, Juniper Networks, Inc.

37

ScreenOS 6.3.0 Release Notes

Intrusion Detection and Prevention (IDP)•

485928—[ISG-IDP] The IDP engine resets due to application identification.

Management•466692—Certain IPv6 Index value is reported as incorrect.

Network Address Translation (NAT)•

480667—The firewall allocates only 2000 MIPs to an interface even when all the user
ids configure MIP in one shared interface.

Other
•

468514—Traffic log is not generated for a source or destination port equal to 1503.

•

471298—UDP MSRPC EnDPort mapper (MS-RPC-EPM) traffic incorrectly displays its
traffic log as MSRPC ENDPOINT MAPPER (TCP).

•

472433—Packet might be corrupted due to ASIC buffer problem.

•

472690—At times, ICMP flood might generate false alarm.

•

481096—Enabling set log audit-loss-mitigation feature causes device to halt traffic
after log buffer is filled.

•481805—After reboot, bandwidth settings configured on gigabit subinterfaces are notloaded.

•484133—With unknown protocol protection disabled, traffic with protocol number
greater than 137 is erroneously dropped.

•484839—Firewall might fail if get alg pptp xlate command is executed.

Performance•

478205—When large amount of WebAuth transaction happens at a time, some HTTP
SYN packets might be dropped during TCP 3-way handshake without returning SYN
and ACK packets.

Routing•

480470—BGP anti-flap processing is removed from the backup NSRP node.

Virtual Private Network (VPN)

38•

472606—False replay protection alarm occurs when the sequence number is updated
incorrectly due to race condition between the rekey process and the update from ASIC.

•

472618—NS-Remote IPsec phase one negotiation might fail if IKE ID is changed.

•475831—Quotation marks (" ") are removed from the configuration when using theset vpn vpn_name bind zone "zone_name" command.

•

480642—User cannot pair a VPN policy when multiple MIPs are used as destination.

Copyright © 2010, Juniper Networks, Inc.

Known Issues•

480691—The VPN tunnel down message (for example, VPN <vpn-name> from
<IP-address> is down) is not generated in the event log when the NSRP backup device
becomes the master.

•

489859—After the firewall is reset, the tunnel interface is down, even though thesecurity association (SA) is up.

Known Issues from ScreenOS 6.3.0
The following are known deficiencies in features at the time of this release. Wheneverpossible, a workaround is suggested following the problem description, preceded by
W/A.
The known issues listed in this section are specific to ScreenOS 6.3.0r1. For the known
issues identified for previous ScreenOS releases, see the Release Notes for the specificrelease.

Flow•

456996—The syn-cookie does not function for IPv6 SYN packet with fragment header.
This packet type is generated when IPV4 translates to IPV6 and the DF bit is not set
in original V4 packet.
This does not impact the IPv4 only deployment in any way. The syn-cookie feature canbe used in IPv4 deployment. For IPv6 deployment, syn-proxy option can be used.

General Packet Radio Service (GPRS)•

440783—[ISG] The CPU does the GTP packet check only for the first GTP-DROP
UserGtPdu and drops it correctly.

Hardware•440062—On executing the set interface X/X phy link-down command on the
JXU-1SFP-S card, the interface link status is erroneous. This is because the TX of fibertransceiver cannot be disabled on the JXU-1SFP-S card.

Intrusion Detection and Prevention (IDP)•

313252—On the ISG series device, when the Security Module is functioning in the TAP
mode, then ScreenOS only transfers the first fragment of packets to Security Module.

•

436544—The Security Module of the ISG series cannot detect certain DNS compound
attack. This is because of the detector functionality.

Other
•

416822— If you execute the CLI command save many times, there is no FBTL available
to extend the flash life. Because this conflict with the FAT cluster allocation process,it leads to logic flash block leakage. This will be fixed in the subsequent ScreenOS
release.

•453156— ScreenOS crashes when the USB device mount fails. This occurs due tocontinued and repetitive execution of the get file command.

Copyright © 2010, Juniper Networks, Inc.

39

ScreenOS 6.3.0 Release Notes•

454916— On a Jupiter chip, when clearing the ARP table several times with heavy VPN
encryption traffic poured out, all of the VPN encrypted packets are sent to CPU for l2
entry reinstall. This causes a buffer leak.
W/A—Reinitialize the ASIC. This can take up to three minutes.

Routing•

430289—On certain Virtual Routers, after configuring the interface rp candidate(interface xx mgroup-list yy;) if you configure the Virtual Router access-list (yy) in arange such as 231.6.0.1/32 to 231.6.0.100/32; then some groups cannot create (s,g) on
untrust vrouter and some other groups cannot forward.

Voice-over-Internet Protocol (VoIP)
Security•

431084—Support for UDP and ICMP flood is not available on the aggregate interface.

Virtual Private Network (VPN)•

423941—When configuring overlapped proxy ids for route-based VPN, the IKEv2
negotiation might fail. The issue can be resolved if traffic selector narrowing is supported
by IKEv2.
W/A—The issue can be resolved if traffic selector narrowing is supported by IKEv2.

•

469089—The VPN monitor does not function for a manual key VPN. This is becauseof adding a proxy id check on the packet sanity check, which is not required for a manual
key VPN.

ErrataThis section lists outstanding issues with the documentation.

Concepts and Examples ScreenOS Reference Guide•

Configuring a DHCP Server section in the ScreenOS 6.1.0, Concepts & Examples ScreenOS
Reference Guide: Vol 2, Fundamentals has the following incorrect information.
WebUI> Addresses > New: Enter the following, then click OK:
Reserved: (select)
IP Address: 172.16.10.11
Ethernet Address: 1234 abcd 5678
CLI
DHCP Server
set interface ethernet0/1 dhcp server option domainname dynamic.com
set interface ethernet0/1 dhcp server option lease 0
set interface ethernet0/1 dhcp server option dns1 172.16.10.240
set interface ethernet0/1 dhcp server option dns2 172.16.10.241

40

Copyright © 2010, Juniper Networks, Inc.

Limitations and Compatibility

set interface ethernet0/1 dhcp server option smtp 172.16.10.25
set interface ethernet0/1 dhcp server option pop3 172.16.10.110
set interface ethernet0/1 dhcp server ip 172.16.10.10 to 172.16.10.19
set interface ethernet0/1 dhcp server ip 172.16.10.120 to 172.16.10.129
set interface ethernet0/1 dhcp server ip 172.16.10.210 to 172.16.10.219
set interface ethernet0/1 dhcp server ip 172.16.10.11 mac 1234abcd5678
set interface ethernet0/1 dhcp server ip 172.16.10.112 mac abcd1234efgh
set interface ethernet0/1 dhcp server servicesave

To successfully configure the example, make the following corrections to the above
WebUI and CLI:
Do not perform the following in the WebUI:> Addresses > New: Enter the following, then click OK:
Reserved: (select)
IP Address: 172.16.10.11
Ethernet Address: 1234 abcd 5678
Remove the command set interface ethernet0/1 dhcp server ip 172.16.10.11 mac
1234abcd5678 from the CLI.
•

ScreenOS releases prior to 6.2.0 support VLAN retagging option only on
NetScreen-5200 and NetScreen-5400 devices. VLAN retagging is not supported on
ISG and SSG series. This limitation is not included in the release 6.0.0 Concepts andExamples ScreenOS Reference Guide.

ScreenOS IPv4 CLI Reference Guide: Command Descriptions
The set flow log-dropped-packet and unset flow log-dropped-packet commands are notdocumented in the ScreenOS 6.3.0 IPv4 CLI Reference Guide. You can access thedescription of these commands from the ScreenOS 6.3.0 IPv6 CLI Reference Guide.

Limitations and Compatibility
This section describes limitations and compatibility issues with the current release.

Limitations of Features in ScreenOS 6.3.0
This section describes the limitations of some features in the ScreenOS 6.3.0 release.
They apply to all platforms unless otherwise noted.

Copyright © 2010, Juniper Networks, Inc.

41

ScreenOS 6.3.0 Release Notes

NOTE: Transceiver Compatibility—Juniper Networks strongly recommends that only
Juniper–provided transceivers be used on interface modules. Different transceiver types(long-range, short-range, copper and so on) can be used together on multi-port SFP
interface modules as long as they are Juniper-provided transceivers.
Juniper Networks cannot guarantee that the interface module will operate correctly if
third-party transceivers are used.
Please contact Juniper Networks for the correct transceiver part number for your device.

•

Admin login sessions not cleared automatically—If the admin timeout value is set tozero using the set console time 0 command, any accidental network disconnection(For example, a cable is unplugged or the client is not closed normally) leaves theassociated sessions open and leave an active entry in the admin table. The entries are
not cleared until the device is reset. [281310].

•

Telnet client not available from a Virtual System (Vsys)—The new telnet client fromthe CLI interface enhancement is not available at the Vsys level. [307763]•

Fast Ethernet port trunking on ISG 1000/2000 requires consecutively numberedports—Fast Ethernet port trunking on ISG 1000 and ISG 2000 devices has a limitation.
If an aggregate interface has more than two ports defined, the ports must be numberedconsecutively without interruption when they are added to the interface.
For example, ethernet2/2, ethernet2/1, and ethernet2/3 ports can be configured evenin the order given because they are numbered consecutively. If ports ethernet2/1,
ethernet2/2, and ethernet2/4 are configured, however, then sessions on this interface
experience load balancing issues. This second example is not a supported orrecommended configuration.

•

•

42

Use of DIPs and SCTP multi-homing—There are several Stream Control Transmission
Protocol (SCTP) limitations when the ScreenOS devices uses DIPs.
•

When SCTP multi-homing is used with DIPs, there is source port translation errorthat results in erroneous source port translation and ultimately dropped traffic.

•

When DIPs are used in an SCTP multi-homing deployment, sessions cannot be
immediately cleared when a shutdown message is received. Sessions are freed after
a timeout.

•

When SCTP multi-homing is employed on a device using DIPs, not all sessions aresynched by devices in an NSRP cluster.

•

When DIPs are used with SCTP multi-homing, SCTP heartbeat traffic is dropped by
the device, thus the SCTP heartbeat function is not supported.

•

ScreenOS 6.3.0 does not support SCTP multi-homing when DIPs are used by the
ScreenOS device. [285236, 285672, 285722, 285988]

8G2-G4 card throughput stability—Running repetitive maximum throughput tests at
certain small frame sizes, can cause a variance of up to about 14% difference in

Copyright © 2010, Juniper Networks, Inc.

Limitations and Compatibility

throughput between two test cycles. The behavior is restricted to the 8 port G4 card.
This does not jeopardize customer traffic in any way.
•

NetScreen 5000 series throughput stability—For NetScreen–5000 8G2-G4, ahardware limitation might result in degraded throughput stability. This limitation is
also present in ScreenOS 6.0.0 and 6.1.0. [287811]•

TCP and UDP sweep screen attack monitoring—The TCP and UDP sweep screen
check is insufficiently accurate. Under extended testing, the TCP and UDP sweep screen
sometimes reports benign traffic or below-threshold attacks as valid sweep attacks.
[293313]•

Virtual MAC Address duplication—Because ScreenOS derives VMACs based on
information taken from cluster ID, interface ID, and VSD, it is not permitted to use thesame clusters and VSDs on the same broadcast domain. If cluster IDs and VSDs are
duplicated on a broadcast domain, it might result in the same VMAC being assigned
to more than one interface or device. [300933]•

PIM Power and Thermal Requirements—If you install either 8-port or 16-port uPIMs
in your SSG 140, SSG 500-series, or SSG 500M-series device, you must observe thepower and thermal guidelines. Please refer to the PIM and Mini-PIM Installation andConfiguration Guide for the power and thermal guidelines for all supported platforms,
available at:
http://www.juniper.net/techpubs/hardware/pim_guide/pim_guide.pdf .

WARNING: Exceeding the power or heat capacity of your device might cause the device
to overheat, resulting in equipment damage and network outage.

•

NSRP—NSRP is not supported on WAN interfaces. Devices with WAN interfaces canuse NSRP, but the WAN ports do not automatically failover as the Ethernet ports do.

•

Flood Screens—On ISG 1000, ISG 2000, NetScreen-5000 Series devices, the UDP
and ICMP flood screens apply to the physical interface and therefore require that thezone be bound to a physical interface. The following limitations apply:••

When zones are bound to a sub-interface, the ICMP and UDP flood screens are notenforced unless the zone is also bound to a physical interface.

•

When ICMP and UDP flood screen options are configured for different zones and on
the same physical interface, the flood threshold is applied based on the lastconfigured zone threshold.

•

When ICMP and UDP flood screen options are applied to a zone tied to multiple
physical interfaces, the entire threshold value is applied to each of the physicalinterfaces.

•

For reference, the High Availability (HA) zone does not allow any screen features tobe configured.

UDP and ICMP Flood Screening—ScreenOS 6.3.0 does not support UDP and ICMP
flood screening for aggregate interfaces in ISG and NetScreen 5000 series. [428057]

Copyright © 2010, Juniper Networks, Inc.

43

ScreenOS 6.3.0 Release Notes•

Configuration file downloads through WebUI without authentication—Using the
WebUI, the firewall downloads the configuration file without authentication. For more
information, see the JTAC knowledge base number KB 12943 located at
http://kb.juniper.net.

•

Call unhold fails—According to RFC 3261, a calling party shall use a=sendonly to holda call and a=sendrecv to unhold it. The observed behavior of the SIP phone used in our
testing is that it does not include the a=sendrecv command when it tries to unhold acall. This lack causes the SIP server to return a "500 internal error" response because
it is unable to determine the state of the transaction. This problem is a telephonysystem issue that cannot be resolved by ALG. Hence, there is no work around for thisissue available through a firewall. [300723].

•

Maximum number of OSPF Redistributed Routes—For the SSG 320M/350M , thesupported maximum number of Open Shortest Path First (OSPF) redistributed routes
is 4096, but it might be possible to exceed the maximum. OSPF redistributed routes
are handled in two parts: route task and OSPF task. The route task adds redistributed
routes to OSPF continuously during one CPU time slice. The redistributed routes counterare not, however, updated until the OSPF task is processed by the CPU, so more routes
might be added in OSPF when the routes are added using an automated script. Routes
entered or redistributed manually should not be able to exceed 4096. [258979]•

ISG and NetScreen 5000 series Multicast Hardware Support—Multicast sessions
can be handled by the ASIC only if there is a single output interface per virtual router.
The mcast group address can be pushed to ASIC so frames are forwarded in hardware.
To use this feature run the set/unset flow multicast install-hw-session command.
[309007, 427260]

Documentation Changes•

Starting with the ScreenOS 6.3.0 documentation, the content presentation of thefollowing guides is standardized to align with Juniper Technical Publications Standards:•

Concepts & Examples ScreenOS 6.3.0 Reference Guide•

ScreenOS 6.3.0 IPv4 CLI Reference Guide•

ScreenOS 6.3.0 IPv6 CLI Reference Guide•

Upgrade Guide

Because of the alignment, the content presentation of ScreenOS 6.3.0 documentationdiffers from that of ScreenOS 6.2.0 and earlier documentation

Getting Help for ScreenOS 6.3.0 Software
For further assistance with Juniper Networks products, visit:www.juniper.net/customers/support .
Juniper Networks occasionally provides maintenance releases (updates and upgrades)
for ScreenOS firmware. To have access to these releases, you must register your security
device with Juniper Networks.

44

Copyright © 2010, Juniper Networks, Inc.

Getting Help for ScreenOS 6.3.0 Software

Copyright © 2010, Juniper Networks, Inc. All rights reserved.
Juniper Networks, the Juniper Networks logo, NetScreen, and ScreenOS are registeredtrademarks of Juniper Networks, Inc. in the United States and other countries. All othertrademarks, service marks, registered trademarks, or registered service marks in thisdocument are the property of Juniper Networks or their respective owners. All
specifications are subject to change without notice. Juniper Networks assumes noresponsibility for any inaccuracies in this document or for any obligation to update
information in this document. Juniper Networks reserves the right to change, modify,transfer, or otherwise revise this publication without notice.

Copyright © 2010, Juniper Networks, Inc.

45