Network Management
•
The value of IfHighSpeed for the current bandwidth of an interface is in units of
1,000,000 bits per seconds. According to RFC 2683, the ifHighSpeed must be rounded
to the nearest whole value on both the physical interfaces and logical interfaces.
[PR/507004]
MPLS Applications
•
When the no-decrement-ttl statement is included at the [edit protocols mpls] or the
[edit protocols mpls label-switched-path path-name] hierarchy level, the VPN Label
TTL action field in the output of the show route extensive command displays
vrf-propagate-ttl as the action. This is a display issue only and has no operational
impact on the forwarding behavior. This is relevant to Layer 3 VPN scenarios where
BGP routes resolve over RSVP LSPs and the no-propagate-ttl statement is not
configured at the [edit protocols mpls] hierarchy level. [PR/563505]
Platform and Infrastructure
•
The SFC management interface em0 is often displayed as fxp0 in several warning
messages. [PR/454074]
•
On restarting with a large-scale configuration (16,000 logical interfaces per MPC), the
MPC-3D-16XGE-SFPP card may take up to 15 minutes to come up. [PR/478548]
•
The dynamic auto-sensed VPLS interfaces fail after modifications are made to the
routing instance. Before making configuration changes to any routing instance, clear
any active logical interfaces that are part of the routing instance using the clear
auto-configuration interfaces operational command. Modifying a routing instance
configuration when the configuration is actively being used by subscribers can result
in an unpredictable behavior. [PR/512902]
•
The GRE key tunnel performance falls by 10 percent when 4000 or more tunnels or
more are configured on the MS-PIC. [PR/520855]
•
An NTP server might not reply to clients with a source address that is explicitly
configured. [PR/540430]
•
The IPv6 BGP neighbors might not come back to the up state when an FPC associated
with that session is manually taken offline, removed, and re-inserted. [PR/552376]
•
With the IRB and AE interfaces in a bridge-domain, the old nexthop data is not cleared
from the Packet Forwarding Engines when they are updated. This causes the Packet
Forwarding Engine to crash when that nexthop is later referenced. [PR/560813]
•
On an MX960 router, when an MPC is installed and OSPF and IS-IS is activated
simultaneously, the "jtree memory free using incorrect value 8 correct 0" message is
displayed for all DPCs. [PR/562719]
•
On standalone routers with graceful Routing Engine switchover (GRES) (set chassis
redundancy graceful-switchover) enabled, or on multi chassis routers (TX, TXP), when
the interfaces are moved from one aggregate bundle to another using a single commit
operation, out of order logical interface messages might be sent to the Packet
Forwarding Engine. When this occurs, the error messages similar to the following are
displayed:
51Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
To Next Page
Loading...