Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note page 53

Release 10.0.3
If you have removed the last rule in a policy list, the router generates a warning
only after you exit Policy List Configuration mode. If you have removed the last
policy rule and then added a classifier group before you exit Policy List
Configuration mode, the router does not generate a warning about removing
the last rule. [Defect ID 83834]
When an MD-Port-Number value greater than 65,535 is sent to an E120 or
E320 router by means of a COA request, the value that is displayed in the UDP
header of mirrored packets is the actual value minus 65,536. For example, an
MD-Port-Number of 65,540 is displayed in the mirrored packet as 4. [Defect ID
84712]
On the E120 and E320 routers, when a mirror rule is deleted after a CoA
request is sent with Juniper-LI-Action set to No-Action, the existing mirroring
session is not disabled. [Defect ID 84826]
When you attach certain hierarchical policies to subinterfaces as input policies,
secondary input policies, and output policies, incoming traffic loss can occur
when the number of subinterfaces to which the policies are attached exceeds
4600. [Defect ID 86741]
On E320 line modules that support secure policies, the SRP module enables
you to configure more than 1022 secure policies per module.
Work-around: To avoid potential performance issues, we recommend that you
do not configure more than 1022 secure policies per module. [Defect ID
175756]
Unified in-service software upgrade (unified ISSU) is not supported on an E120
or E320 router if a hierarchical policy is attached to an external parent group.
[Defect ID 177478]
When you reload the slot holding a GE-2 or GE-HDE line module and you have
configured more than about 2,000 policies with rate limiting on that module,
the drop count becomes more than expected. This unexpected drop count does
not occur when you create the same configuration after you reload the router
to the factory-default configuration. [Defect ID 175696]
Work-around: If you must reload the slot, issue the slot erase command after
you do so and then reconfigure the policies on the line module.
When you modify a rate-limit profile in Global Configuration mode after the
system is in a scaled state, changes to the rate-limit profile fail owing to lack of
adequate policy resources. However, the changed value of the rate-limit profile
is displayed in the output of the show rate-limit profile command. [Defect ID
79342]
Work-around: To avoid this problem, do not update the rate-limit profile in
Global Configuration mode in a scaled environment.
45
Known Problems and Limitations