■
The Juniper Networks rendezvous point (RP) does not process PIM Register
messages from a first-hop router in an IPv6 embedded RP group when the
Register message does not have the null-bit set. [PR/486902]
■
When a PPMD delegation of BFD sessions is configured over AE interfaces,
graceful Routing Engine switchover and NSR do not work. [PR/505058]
■
The BGP BMP message for IPv6 withdraw encoding does not follow the BMP-draft.
[PR/512780]
■
When an interface comes up after a down event, and LDP-IGP sync is configured
for that interface, OSPF does not include the interface in its LFA calculations
while the interface is in LDP Sync hold-down state. [PR/515482]
■
When the received next hop for a route has the same address of the EBGP peer
to which the route is readvertised, the next hop is errorneously set to the peer's
address instead of the next hop to self. [PR/533647]
■
When an IGMP snooping host interface goes down, mcsnoopd does not update
the affected nexthops for the statically configured groups. When the interface
comes back up, the affected nexthops remain in the inconsistent state leading
to traffic outage. As a workaround, restart the mcsnoopd process. [PR/536109]
Services Applications
■
The
show services accounting flow-detail extensive
command sometimes displays
incorrect information about input and output interfaces. [PR/40446]
■
When a routing platform is configured for graceful Routing Engine switchover
(GRES) and Adaptive Services (AS) PIC redundancy, and a switchover to the
backup Routing Engine occurs, the redundant services interface (rsp-) always
activates the primary services interface (sp-), even if the secondary interface was
active before the switchover. [PR/59070]
■
Detection of failure of remote PPP clients on the LNS through LCP echo requests
will take longer due to an increase in the number of echo request retries.
[PR/250640]
■
When the Border Signaling Gateway (BSG) configuration contains a policy that
has a term with regular expressions, configuration changes might not take effect
immediately after the commit process is complete. In most cases, the new policy
takes effect immediately. However, complex policies may take longer to take
effect depending on how many regular expressions they contain.
For example, if you have a term with four regular expressions, configuration
changes do not take effect until 50 seconds after you receive the message that
the commit process is complete. This behavior occurs whether you have a list
or regular expressions (for example, regular-expression [sip:88824.* sip:88821.*
sip:88822.sip:88823.*]), or you group regular expressions using the | symbol
(for example, "sip:88821.*|sip:88822.*|sip:88823.*|sip:88824.*").
The time taken for the software to apply the configuration changes increases
exponentially with the number of regular expressions in your configuration.
[PR/448474]
■
When a standard application is specified under the
[edit security idp idp-policy
policy-name
rulebase-ips rule
rule-name
match application]
hierarchy level, the IDP
62
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
