Dell PowerConnect J-8208 Release Notes JUNOS version 10.3 - Page 41

J-Web, Network Address Translation (NAT), Power over Ethernet (PoE), Security

Page 41 highlights

Issues in Junos OS Release 10.3 for J-SRX Series Services Gateways J-Web • On J-SRX Series devices, when the user tried to associate an interface to GVRP, a new window appeared. This new window showed multiple move-left and move-right buttons. [PR/305919: This issue has been resolved.] • On J-SRX100, J-SRX210, and J-SRX240 devices, in J-Web configuration for the routing feature, if you entered double quotation marks in the text boxes that accepted characters (for example, protocol name, filename, and description), then you could not delete the data with double quotation marks through J-Web. [PR/464030: This issue has been resolved.] • On J-SRX Series devices, in the J-Web interface, the ui show or ui compare Junos XML protocol RPC commands generated some unnecessary debug messages. [PR/514540: This issue has been resolved.] Network Address Translation (NAT) • On J-SRX240 High Memory devices in a chassis cluster, the secondary node could go to DB> mode when there were many policies configured and TCP, UDP, and ICMP traffic matched the policies. [PR/493095: This issue has been resolved.] • On J-SRX Series devices, Remote Procedure Call (RPC) did not work with source NAT configuration. [PR/515455: This issue has been resolved.] • On J-SRX100 and J-SRX210 High Memory devices, h323/h245 OLC could not pass whether src nat or dst nat. [PR/538764: This issue has been resolved.] • On J-SRX100 High Memory devices, for "nat source" with "port no-translation", the configured source-pool IP addresses were divided into half and they were exclusively used on each node. However, when multiple groups of source-pool IP addresses were configured, the half-divided logic did not work properly, and it resulted in an unexpectedly insufficient IP address (from source-pool) for a node. [PR/538769: This issue has been resolved.] Power over Ethernet (PoE) • On J-SRX240 PoE devices, during failover, on the secondary node the ADSL Mini-PIM restarted and took about 3-4 minutes to come up. [PR/528949: This issue has been resolved.] Security • On J-SRX240 High Memory devices, when you committed a configuration change that added a security policy that contained a DNS address object, the device would core if the DNS address object was unresolved to an IP address. [PR/ 542175: This issue has been resolved.] • On J-SRX240 high memory devices, the device rebooted unexpectedly after execute 'commit' command with predefined-attack-groups changes that included Solaris Services - All attack group. [PR/546705: This issue has been resolved.] 41

  • 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

J-Web
On J-SRX Series devices, when the user tried to associate an interface to GVRP, a new
window appeared. This new window showed multiple move-left and move-right
buttons. [PR/305919: This issue has been resolved.]
On J-SRX100, J-SRX210, and J-SRX240 devices, in J-Web configuration for the routing
feature, if you entered double quotation marks in the text boxes that accepted
characters (for example, protocol name, filename, and description), then you could
not delete the data with double quotation marks through J-Web. [PR/464030: This
issue has been resolved.]
On J-SRX Series devices, in the J-Web interface, the
ui show
or
ui compare
Junos XML
protocol RPC commands generated some unnecessary debug messages. [PR/514540:
This issue has been resolved.]
Network Address Translation (NAT)
On J-SRX240 High Memory devices in a chassis cluster, the secondary node could go
to
DB>
mode when there were many policies configured and TCP, UDP, and ICMP
traffic matched the policies. [PR/493095: This issue has been resolved.]
On J-SRX Series devices, Remote Procedure Call (RPC) did not work with source NAT
configuration. [PR/515455: This issue has been resolved.]
On J-SRX100 and J-SRX210 High Memory devices, h323/h245 OLC could not pass
whether
src nat
or
dst nat
. [PR/538764: This issue has been resolved.]
On J-SRX100 High Memory devices, for "nat source" with "port no-translation", the
configured source-pool IP addresses were divided into half and they were exclusively
used on each node. However, when multiple groups of source-pool IP addresses were
configured, the half-divided logic did not work properly, and it resulted in an
unexpectedly insufficient IP address (from source-pool) for a node. [PR/538769: This
issue has been resolved.]
Power over Ethernet (PoE)
On J-SRX240 PoE devices, during failover, on the secondary node the ADSL Mini-PIM
restarted and took about 3-4 minutes to come up. [PR/528949: This issue has been
resolved.]
Security
On J-SRX240 High Memory devices, when you committed a configuration change that
added a security policy that contained a DNS address object, the device would core if
the DNS address object was unresolved to an IP address. [PR/ 542175: This issue has
been resolved.]
On J-SRX240 high memory devices, the device rebooted unexpectedly after execute
'commit' command with predefined-attack-groups changes that included
Solaris -
Services - All
attack group. [PR/546705: This issue has been resolved.]
41
Issues in Junos OS Release 10.3 for J-SRX Series Services Gateways