Network Management
■
Under certain SNMP conditions, the following log message is displayed:
M10i-RE0 pfed: PFED_NOTIF_GLOBAL_STAT_UNKNOWN: Unknown global
notification stat: transit options/ttl-exceeded (re-injected)
M10i-RE0 pfed: PFED_NOTIF_STAT_UNKNOWN: Unknown notification type stat:
Unknown
This log message might also be displayed during the installation of AI Scripts
(version 2.1R2 or above) on the router. AI Scripts versions prior to 2.1R2 do not
cause these messages. This is a cosmetic message, and does not have any impact.
[PR/427590: This issue has been resolved.]
■
Under certain conditions, the SNMPD crashes due to a BAD_PAGE_FAULT.
[PR/496351: This issue has been resolved.]
Platform and Infrastructure
■
When certain FPCs (T1600-FPC4-ES, T640-FPC4-1P-ES, T640-FPC1-ES,
T640-FPC2-ES, and T640-FPC3-ES) receive corrupted cells via high-speed links,
they might unnecessarily reboot and report the following system log error
message: "Unrecoverable Error: Flist gtop bit toggled !." No reset is needed to
recover from this condition. [PR/441844: This issue has been resolved.]
■
The configured static NDP entry is cleared automatically after a certain interval.
[PR/453710: This issue has been resolved.]
■
When the flow monitoring version 9 feature is enabled on an MS PIC (or service
PIC that supports flow monitoring version 9), the MS PIC might crash upon
receiving certain corrupted IPv6 packets. [PR/458361: This issue has been
resolved.]
■
When an aggregated SONET with a Cisco High-Level Data Link Control (HDLC)
encapsulation is configured, a member link might not be marked as link-down
in the Packet Forwarding Engine if the remote end of the link is disabled.
[PR/472677: This issue has been resolved.]
■
The output of the
show arp
command does not display the entire demux interface
identifier, making it impossible to determine which specific demux sub-interface
a given ARP entry is associated with. [PR/482008: This issue has been resolved.]
■
A problem occurs on an M120 router with an FEB redundancy configuration
when the backup FEB is protecting a non-primary FEB. In this case, the Routing
Engine will prompt the incorrect Packet Forwarding Engine for status, causing
delays in the SNMP responses. [PR/490172: This issue has been resolved.]
■
If you configure an IP address with a larger subnet, for example, /19, on a
different interface first, the router begins to negotiate for the ARP of a specific
host on that interface and gets stuck in a hold state. If you later configure a more
specific subnet of /29 on another interface from where the host can be reached,
the forwarding table will still prefer the route with the hold entry via /19 instead
of the route with the ucst entry via /29. [PR/491468: This issue has been resolved.]
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
77
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
