Dynamic Vpn; Flow And Processing - Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Release Note

JUNOS 10.1 Software Release Notes

Dynamic VPN

SRX100, SRX210, and SRX240 devices have the following limitations:

Flow and Processing

Sessions
ssh
telnet
Web
NOTE: These defaults are provided for performance reasons.
Device
SRX210
SRX240
134
Known Limitations in JUNOS Release 10.1 for SRX Series Services Gateways and J Series Services Routers
The IKE configuration for the dynamic VPN client does not support the
hexadecimal preshared key.
The dynamic VPN client IPsec does not support the Authentication Header (AH)
protocol and the Encapsulating Security Payload (ESP) protocol with NULL
authentication.
When you log in through the Web browser (instead of logging in through the
dynamic VPN client) and a new client is available, you are prompted for a client
upgrade even if the
force-upgrade
using the dynamic VPN client with the
upgrade occurs automatically (without a prompt).
Maximum concurrent SSH, Telnet, and Web sessions—On SRX210, SRX240,
and SRX650 devices, the maximum number of concurrent sessions is as follows:
SRX210 SRX240
3 5
3 5
3 5
On SRX210 and SRX240 devices, for optimized efficiency, we recommend that
you limit use of CLI and J-Web to the following numbers of sessions:
CLI J-Web
3 3
5 5
On SRX100 devices, Layer 3 control protocols (OSPF, using multicast destination
MAC address) on the VLAN Layer 3 interface work only with access ports.
On SRX210, SRX240, and J Series devices, broadcast TFTP is not supported
when is enabled on the device.
flow
option is configured. Conversely, if you log in
force-upgrade option configured, the client
SRX650
5
5
5
Console
1
1