Juniper JUNOS OS 10.4 - RELEASE NOTES - Known Limitations in Junos os Release 10.4 for SRX Series Services Gateways and J Series Services Routers; Appsecure; Chassis Cluster

Known Limitations in Junos OS Release 10.4 for SRX Series Services Gateways and J Series
Services Routers
AppSecure
•
Junos OS application identification—When you create custom application or nested
application signatures for Junos OS application identification, the order value must be
unique among all predefined and custom application signatures. The order value
determines the application matching priority of the application signature.
The order value is set with the set services application-identification application
application-name signature order command. You can also view all signature order
values by entering the show services application-identification | display set | match order
command. You will need to change the order number of the custom signature if it
conflicts with another application signature.
Chassis Cluster
•
On SRX650 devices in a chassis cluster, ping packets sent from the forward node to
the active node are dropped intermittently.
•
On SRX650 devices in a chassis cluster, the T1/E1 PIC goes offline and does not come
online.
•
In large chassis cluster configurations on SRX3400 or SRX3600 devices, you need to
increase the wait time before triggering failover. In a full-capacity implementation, we
recommend increasing the wait to 8 seconds by modifying heartbeat-threshold and
heartbeat-interval values in the [edit chassis cluster] hierarchy.
The product of the heartbeat-threshold and heartbeat-interval values defines the time
before failover. The default values (heartbeat-threshold of 3 beats and
heartbeat-interval of 1000 milliseconds) produce a wait time of 3 seconds.
To change the wait time, modify the option values so that the product equals the
desired setting. For example, setting the heartbeat-threshold to 8 and maintaining the
default value for the heartbeat-interval (1000 milliseconds) yields a wait time of 8
seconds. Similarly, setting the heartbeat-threshold to 4 and the heartbeat-interval to
2000 milliseconds also yields a wait time of 8 seconds.
•
SRX100, SRX210, SRX240, and SRX650 devices have the following chassis cluster
limitations:
•
Virtual Router Redundancy Protocol (VRRP) is not supported.
•
In-service software upgrade (ISSU) is not supported.
•
The 3G dialer interface is not supported.
•
On SRX Series device failover, access points on the Layer 2 switch reboot and all
wireless clients lose connectivity for 4-6 minutes.
•
On VDSL mini-PIM, chassis cluster is not supported for VDSL mode.
•
Queuing on aggregated Ethernet (ae) interface is not supported.
133Copyright © 2010, Juniper Networks, Inc.
Known Limitations in Junos OS Release 10.4 for SRX Series Services Gateways and J Series Services Routers