JUNOSe 11.1.0 Release Notes
54
Known Problems and Limitations
The OC3/STM1 GE/FE line module might reset after sending Ethernet traffic
into a VPLS network in a test environment when Ethernet packets are flooded
to remote VPLS bridges. [Defect ID 74540]
Policy Management
On the E320 router, redirecting a large configuration with thousands of
interfaces to a script file can take a long time, perhaps exceeding a half-hour
depending on the configuration. [Defect ID 80429]
When you attach a policy to an interface and the policy contains a classifier
rule that is unsupported for that interface, the CLI generates a message and the
policy is applied. However, if an existing policy is already attached to that
interface, then support for the new policy is not checked and the invalid policy
is applied to the interface without warning. The results of this attachment are
not predictable. [Defect ID 83562]
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]
No logs are created if you use the
policy-list
option with the
log severity
severityValue
policyMgrPacketLog policy-list
policyListName
command when
logging policyMgrPacketLog events. [Defect ID 87203]
When you reload the slot holding a GE-2 or GE-HDE line module and you have
configured more than about 2000 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]
On E320 line modules that support secure policies, the SRP module enables
you to configure more than 1022 secure policies per module. [Defect ID
175756]
Work-around
: To avoid potential performance issues, we recommend that you
do not configure more than 1022 secure policies per module.
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]
