Table of Contents
Advertisement
Copyright © 2011, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
On MPC-3D FPCs, the following IDMEM parity error messages appear:
MX960-LAB fpc3 LU 2 RD_NACK 2 AP[0x04] TOE Write 0x002913a0
MX960-LAB fpc3 LU 2 IDMEM Parity error in Bank 3, Count 10, IDMEM Bank 3
Offset 0x00014899 IDMEM[0x00052274]
These messages repeat as long as the software encounters the error. These error
messages occur within uninitialized memory locations. [PR/569887]
Incorrect K2 bytes might be transmitted if the mode bits are not set correctly by the
apsd process. [PR/569903]
Layer 2 Ethernet Services
The release message is not sent to the DHCP server even though the
flag is set under the DHCP relay configuration. As a workaround,
send-release-on-delete
to deactivate or deconfigure an interface, clear all the bindings on the interface before
you deactivate or delete the interface. To deactivate or deconfigure the relay, clear all
the bindings before you deactivate or delete the relay. [PR/498920]
MPLS Applications
On M Series and T Series routers, the MPLS label-switched path (LSP) log messages
are not logged for non-standby secondary MPLS LSPs. [PR/560069]
The routing protocol process crashes when an MVPN routing instance is activated and
deactivated. [PR/571131]
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]
Platform and Infrastructure
The SFC management interface
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
auto-configuration interfaces
configuration when the configuration is actively being used by subscribers can result
in an unpredictable behavior. [PR/512902]
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]
em0
is often displayed as
operational command. Modifying a routing instance
fxp0
in several warning
clear
53
Advertisement
Table of Contents
