Juniper Networks 5XT, 5200, 208, 204, 500 An SNMP sysObject OID reply returned in the wrong format

Juniper Networks NetScreen Release Notes

•36717 – When upgrading to ScreenOS 5.0.0, the maximum number of address groups allowed for Layer2 predefined zones incorrectly got set to the same number as for custom zones. As a result, if the number of address groups in Layer2 predefined zones surpasses the maximum number allowed, some address groups got removed during the upgrade.

•32690 – (Juniper NetScreen-5GT only) When multiple devices were connected with AV scanning enabled on policies, no traffic passed through the devices. For example, if two devices were connected together and both had AV scanning enabled on policies, no traffic traversed the devices.

•02081 – The active user table failed to clear automatically. New users were denied until the table was manually cleared.

•02079 – In an instance where the system was running in transparent mode, when you enabled traffic shaping mode, the system dropped all packets.

•02038 – Reboots occurred occasionally when traffic matched policies which had authentication enabled.

•02027 – An SNMP sysObject OID reply returned in the wrong format.

•02006 – Enabling DHCP Relay could cause a Juniper Networks security appliance to crash.

•01972 – A DHCP relay packet sometimes caused a Juniper Networks security appliance to crash.

•01971 – You were not able to add physical interfaces (different ports) of a Juniper Networks security appliance in the same redundant interface group.

•01968 – (Juniper NetScreen-5GT only) Ident-reset packets that terminated on the device might have caused the device to restart.

ScreenOS 5.0.0r9-FIPS P/N 093-1638-000, Rev. A Page 28 of 42