Dell PowerConnect J-8216 Release Notes JUNOS version 10.3 - Page 25

Command-Line Interface (CLI), Dynamic VPN, Relay MLFR

Get Dell PowerConnect J-8216 PDF manuals and user guides View all Dell PowerConnect J-8216 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 25 highlights

Known Limitations in Junos OS Release 10.3 for J-SRX Series Services Gateways • PoE is not supported in chassis cluster mode. • Group VPN is not supported. • Sampling features like J-FLow, packet capture, and port mirror on the reth interface are not supported. • Switching is not supported in chassis cluster mode. • The Chassis Cluster MIB is not supported. • Any packet-based services like MPLS and CLNS are not supported. • lsq-0/0/0-Link services Multilink Point-to-Point Protocol (MLPPP), Multilink Frame Relay (MLFR), and Compressed Real-Time Transport Protocol (CRTP) are not supported. • gr-0/0/0-Generic routing encapsulation (GRE) and tunneling are not supported. • ip-0/0/0-IP-over-IP (IP-IP) encapsulation is not supported. • lt-0/0/0-CoS for real-time performance monitoring (RPM) is not supported. • PP0-PPPoE and PPPoEoA are not supported. • On J-SRX100, J-SRX210, and J-SRX240 devices, UTM is supported only for active/backup chassis cluster configuration with both RG0 and RG1+ active on the same node. It is not supported for active/active chassis cluster configuration. For other limitations in chassis cluster, see "Limitations of Chassis Clustering" in the Junos OS Security Configuration Guide. Command-Line Interface (CLI) • On J-SRX210 and J-SRX240 devices, J-Web crashes if more than nine users log in to the device by using the CLI. The number of users allowed to access the device is limited as follows: • For J-SRX210 devices: four CLI users and three J-Web users • For J-SRX240 devices: six CLI users and five J-Web users Dynamic VPN J-SRX100, J-SRX210, and J-SRX240 devices have the following limitations: • 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 25

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
•
PoE is not supported in chassis cluster mode.
•
Group VPN is not supported.
•
Sampling features like J-FLow, packet capture, and port mirror on the
reth
interface
are not supported.
•
Switching is not supported in chassis cluster mode.
•
The Chassis Cluster MIB is not supported.
•
Any packet-based services like MPLS and CLNS are not supported.
•
lsq-0/0/0—Link services Multilink Point-to-Point Protocol (MLPPP), Multilink Frame
Relay (MLFR), and Compressed Real-Time Transport Protocol (CRTP) are not
supported.
•
gr-0/0/0—Generic routing encapsulation (GRE) and tunneling are not supported.
•
ip-0/0/0—IP-over-IP (IP-IP) encapsulation is not supported.
•
lt-0/0/0—CoS for real-time performance monitoring (RPM) is not supported.
•
PP0—PPPoE and PPPoEoA are not supported.
•
On J-SRX100, J-SRX210, and J-SRX240 devices, UTM is supported only for
active/backup chassis cluster configuration with both RG0 and RG1+ active on the
same node. It is not supported for active/active chassis cluster configuration.
For other limitations in chassis cluster, see “Limitations of Chassis Clustering” in the
Junos
OS Security Configuration Guide
.
Command-Line Interface (CLI)
•
On J-SRX210 and J-SRX240 devices, J-Web crashes if more than nine users log in to
the device by using the CLI. The number of users allowed to access the device is limited
as follows:
•
For J-SRX210 devices: four CLI users and three J-Web users
•
For J-SRX240 devices: six CLI users and five J-Web users
Dynamic VPN
J-SRX100, J-SRX210, and J-SRX240 devices have the following limitations:
•
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
25
Known Limitations in Junos OS Release 10.3 for J-SRX Series Services Gateways