03.03.2013 Views

6.3.0r10 Release Notes - Juniper Networks

6.3.0r10 Release Notes - Juniper Networks

6.3.0r10 Release Notes - Juniper Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ScreenOS 6.3.0 <strong>Release</strong> <strong>Notes</strong><br />

Addressed Issues from ScreenOS 6.3.0r6<br />

30<br />

Administration<br />

• 536897—Under certain circumstances, the message command rejected due to writing<br />

config conflict was printed on the telnet, ssh or console of the device.<br />

Antivirus<br />

• 535728—While scanning the FTP session, the APP session was aborted because the<br />

device ran out of packets with code 0 resulting in low memory. Delete unused license<br />

to free memory space.<br />

Authentication<br />

• 536931—Cross-vsys authentication did not bind to the correct session in both vsys<br />

CLI<br />

which resulted in a session that was created in the ingress vsys but not in the egress<br />

vsys. This resulted in denial of traffic.<br />

• 541186—The set log exclude-id command did not work for some of the event-types.<br />

DI<br />

• 538459—Memory leak in sys memory pool occurred when generating an alarm for<br />

some signatures.<br />

DNS<br />

• 531507—The status of Domain Name Server (DNS) entry in the address book was<br />

incorrect.<br />

GPRS<br />

• 544157—GTP events produced multiple log entries.<br />

HA & NSRP<br />

• 524021—NSRP backup session installation error occurred because of route look up<br />

failure that caused packet drop after failover.<br />

• 529696—Under certain circumstances, with the HA link probe configured, the device<br />

sometimes rebooted unexpectedly when the status of the HA link changed.<br />

• 538250—Communication through the master node sometimes failed when exchanging<br />

the backup device through NSM doing the RMA procedure.<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!