Known Problems and Limitations
45
Release 10.3.2
When you issue a
traceroute
or
trace mpls
command to trace the paths of
router packets over MPLS interfaces on an ES2 10G LM or ES2 10G Uplink LM,
the results include an extra unknown host. [Defect ID 174537]
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]
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.
Содержание JUNOSe 10.3.2
Страница 8: ...viii Table of Contents JunosE 10 3 2 Release Notes ...
Страница 76: ...JunosE 10 3 2 Release Notes 68 Errata ...