■
On J Series devices, when you commit a configuration for a node belonging to
a chassis cluster, all the redundancy groups might fail over to node 0. If graceful
protocol restart is not configured, the failover can destabilize routing protocol
adjacencies and disrupt traffic forwarding. To allow the commit operation to
take place without causing a failover, we recommend that you use the
set chassis
cluster heartbeat-threshold 5
command on the cluster. [PR/265801]
■
On J Series devices in a chassis cluster, a high load of SIP ALG traffic might result
in some call leaks in active resource manager groups and gates on the backup
router. [PR/268613]
■
On SRX Series devices in a chassis cluster, configuring the
set system process
jsrp-service disable
command only on the primary node causes the cluster to go
into an incorrect state. [PR/292411]
■
On SRX Series devices in a chassis cluster, using the
set system processes
chassis-control disable
command for 4 to 5 minutes and then enabling it causes
the device to crash. Do not use this command on an SRX Series device in a
chassis cluster. [PR/296022]
■
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, 8-queue configurations
are not reflected on the chassis cluster interface. [PR/389451]
■
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, the
iflset
functionality
is not supported for aggregated interfaces like
reth
. [PR/391377]
■
On an SRX210 device in a chassis cluster, when you upgrade the nodes,
sometimes the forwarding process might crash and get restarted. [PR/396728]
■
On an SRX210 device in a chassis cluster, when you upgrade to the latest software
image, the interface links do not come up and are not seen in the Packet
Forwarding Engine. As a workaround, you can reboot the device to bring up the
interface. [PR/399564]
■
On an SRX210 device in a chassis cluster, sometimes the
reth
interface MAC
address might not make it to the switch filter table. This results in the dropping
of traffic sent to the
reth
interface. As a workaround, restart the Packet Forwarding
Engine. [PR/401139]
■
On an SRX210 device in a chassis cluster, the fabric monitoring option is enabled
by default. This can cause one of the nodes to move to a disabled state. You can
disable fabric monitoring by using the following CLI command:
set chassis cluster fabric-monitoring disable
[PR/404866]
■
On an SRX210 Low Memory device in a chassis cluster, the firewall filter does
not work on the
reth
interfaces. [PR/407336]
■
On an SRX210 device in a chassis cluster, the restart forwarding method is not
recommended because when the control link goes through forwarding, the restart
forwarding process causes disruption in the control traffic. [PR/408436]
■
On an SRX210 device in a chassis cluster, there might be a loss of about 5 packets
with 20 Mbps of UDP traffic on an RG0 failover. [PR/413642]
■
On SRX3400, SRX3600, SRX5600, and SRX5800 devices, no trap is generated
for redundancy group 0 failover. You can check on the redundancy group 0 state
only when you log in to the device. The nonavailability of this information is
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
■
139
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
