JUNOSe 10.0.3 Release Notes
44
Known Problems and Limitations
When you upgrade the router to JUNOSe Release 7.1.0 or a higher-numbered
release from a release numbered lower than Release 7.1.0, remote ATM layer 2
over MPLS circuits (also known as MPLS shim interfaces) that use Martini
encapsulation are erroneously signaled with the control word attribute setting
“Control word is not preferred by default”. Because control words are required
for these MPLS shim interfaces, these circuits should instead be signaled with
the setting “Control word is preferred by default”. [Defect ID 87048]
Work-around:
To reinstate the proper setting (“Control word is preferred by
default”), remove the MPLS shim interface from the ATM subinterface and then
reconfigure it.
Multicast
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
Netflow
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]
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]
No logs are created if you use the
policy-list
option when logging
policyMgrPacketLog events. [Defect ID 87203]
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]
