Copyright © 2010, Juniper Networks, Inc.
Known Behavior
27
Release 11.1.1
z
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”.
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
z
The
ip dipe sg-cache-miss
and
ipv6 dipe
commands are not intended or supported
for customer use, although they are visible in the User Exec and Privileged Exec
modes respectively. These commands are intended to be used in a Juniper Networks
internal lab environment for testing without a traffic generator.
z
Do not configure a multicast group with more than 10,219 outgoing interfaces (OIFS)
on the same ES2 10G LM. [Defect ID 81768]
z
When you upgrade a router running a release earlier than JunosE Release 8.2.x to
JunosE Release 8.2.x or higher-numbered releases, the Protocol Independent
Multicast (PIM) configuration settings in VPN routing and forwarding (VRF)
instances are not restored after the upgrade is completed. This problem happens
only if you did not previously configure PIM on the parent virtual router (VR) for the
VRF. This problem occurs with both IPv4 PIM and IPv6 PIM configurations on the
router.
After the completion of the upgrade process, if you attempt to restore the PIM
configuration directly on the VRF, an error message is displayed. For example, if you
try to restore the IPv4 PIM settings on the VRF using the
router pim
command, the
following error message is displayed:
host1:vrf01(config)#
router pim
% PimIp not configured on this router
Work-around
: To correct this problem after you upgrade a router running a release
earlier than JunosE Release 8.2.x to JunosE Release 8.2.x or higher-numbered
releases, you need to restore the PIM configuration on the upgraded router in two
steps (first, on the parent VR, and then, on the VRF), instead of attempting to restore
the PIM configuration directly on the VRF.