caused by a failure of the SNMP walk on the backup (secondary) node. As a
workaround, use a master-only IP address across the cluster so that you can
query a single IP address and that IP address will always be the master for
redundancy group 0. [PR/413719]
■
On an SRX210 device with an FTP session ramp-up rate of 70, either of the
following might disable the secondary node:
■
Back-to-back redundancy group 0 failover
■
Back-to-back primary node reboot
[PR/414663]
■
If an SRX210 device receives more traffic than it can handle, node 1 either
disappears or gets disabled. [PR/416087]
■
On SRX3400, SRX3600, SRX5600, SRX5800, and J Series devices in an
active/active chassis cluster, when the fabric link fails and then recovers, services
with a short
time-to-live
(such as ALG FTP) stop working. [PR/419095]
■
On SRX5800 devices, SNMP traps might not be generated for the
ineligible-primary state. [PR/434144]
■
On SRX3400, SRX3600, SRX5600, and SRX5800 devices in chassis cluster
active/active mode, the J-Flow samplings do not occur and the records are not
exported to the
cflowd
server. [PR/436739]
■
On SRX240 Low Memory and High Memory devices, binding the same IKE policy
to a dynamic gateway and a site-to-site gateway is not allowed. [PR/440833]
■
On SRX650 devices, the following message appears on the new primary node
after a reboot or a RG0 failover:
WARNING: cli has been replaced by an updated version:
CLI release 9.6B1.5 built by builder on 2009-04-29 08:24:20 UTC
Restart cli using the new version ? [yes,no] (yes) yes
[PR/444470]
■
On SRX240 and SRX650 devices in chassis cluster active/active preempt mode,
the RTSP session breaks after a primary node reboot and preempt failover. The
following common ALGs will be broken: RSH, TALK, PPTP, MSRPC, RTSP,
SUNRPC, and SQL. [PR/448870]
■
On SRX240 devices, the cluster might get destabilized when the file system is
full and logging is configured on JSRPD and chassisd. The log file size for the
various modules should be appropriately set to prevent the file system from
getting full. [PR/454926]
■
On SRX3400, SRX3600, SRX5600, and SRX5800 devices in a chassis cluster,
the ping operation to the redundant Ethernet interface (
reth
) fails when the cluster
ID changes. [PR/458729]
■
On SRX100 devices, after primary node reboot and cold synchronization are
finished, the chassis cluster auth session timeout age and application name
cannot synchronize with the chassis cluster peers. [PR/460181]
140
■
Issues in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
JUNOS 10.1 Software Release Notes