Table of Contents
Advertisement
JUNOSe 10.2.2 Release Notes
Multicast
Netflow
Policy Management
44
Known Problems and Limitations
When you configure more than 10,219 outgoing interfaces (OIFs) on the same
ES2 10G LM in a single multicast group, the configuration of the multicast
group's OIF membership from the SRP module to the line module exceeds the
size of a single message and is sent in fragments. Because of this
fragmentation, the ES2 10G LM generates the following error message: [Defect
ID 81768]
pc: 0x9e5c88: -> fatalPanic(void) offset: 0x8
Flow sampling stops after a cold switchover on a router that is configured with
16 VRs and 32 interfaces per VR, when all flows are passing through the
configuration (32 flows per VR). [Defect ID 74477]
Work-around: After the cold switchover is completed, reissue the ip
flow-sampling-mode packet-interval 10 command on each VR, even though
the command is present in the configuration.
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]
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/184107]
Work-around: To avoid this problem, do not update the rate-limit profile in
Global Configuration mode in a scaled environment.
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]
Advertisement
Table of Contents
