Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 145

Table of Contents

Advertisement

Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers
Use the
show chassis fpc pic-status
Use the
show pfe terse
is
Ready
and to verify the following:
All slots on the RG0 primary node have the status
All slots on the RG0 secondary node, except the Routing Engine slots, have the
status
.
Valid
[PR/503389, PR/520093]
On SRX650 devices, when the primary node is synchronizing heavy routes to the
secondary node and the secondary node is rebooted, FPCs on the secondary node
come up very slowly. PICs will not come up until all the routes are synchronized to the
secondary node. [PR/545429]
Class of Service (CoS)
J4350 and J6350 devices might not have the requisite data buffers needed to meet
expected delay-bandwidth requirements. Lack of data buffers might degrade CoS
performance with smaller (500 bytes or less) packets. [PR/73054]
On J Series devices with a CoS configuration, when you try to delete all the flow sessions
using the
clear security flow session
platform might fail over with heavy traffic. [PR/273843]
Command-Line Interface (CLI)
On SRX650 devices, tail drops and keepalive losses are seen at high load on multilink
bundles when queue 3 (out of queue 0 to queue 7) is oversubscribed. As a workaround,
use only queue 3 for keepalive packets, and use other queues for data or voice
transmission. [PR/539353]
Dual Stack Lite
On SRX650, SRX3400, SRX3600, SRX5600 and SRX5800 devices, if the interface
address is changed to a new address which is also the concentrator address with the
background traffic target to the address, you should manually clear the IPIP clear text
sessions with the concentrator address as the destination address, if there are any, so
that the Dual-stack lite concentrator could take effect on the traffic flow. [PR/541516]
On SRX5600 devices, with heavy DS-Lite traffic, flowd might stop responding with
flow table corruption because of a function related to flow table operation (for example,
flow_table_find_flow_v6). [PR/548790]
command to verify that the PIC status is
command to verify that the Packet Forwarding Engine status
command, the WXC application acceleration
Online
.
Online
.
145

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junos os 10.4

Table of Contents