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

Outstanding Issues In Junos OS Release 10.3 for J-SRX Series Services Gateways

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

Page 30 highlights

Junos 10.3 OS Release Notes Outstanding Issues In Junos OS Release 10.3 for J-SRX Series Services Gateways The following problems currently exist in J-SRX Series devices. The identifier following the description is the tracking number in our bug database. Application Layer Gateways (ALGs) • On J-SRX210 devices, the SCCP call cannot be set up after disabling and enabling the SCCP ALG. The call does not go through. [PR/409586] • On J-SRX240 devices, the maximum SCCP calls cannot be made under stress conditions. [PR/490839] • On J-SRX Series devices, SIP server protection does not work. The set security alg sip application-screen protect deny command does not work. [PR/512202] AX411 Access Point • On J-SRX210 PoE devices, the access point reboots when 100 clients are associated simultaneously and each one is transmitting 512 bytes packets at 100 pps. [PR/469418] Chassis Cluster • On J-SRX Series devices in a chassis cluster, configuring the set system process jsrp-service disable command only on the primary node causes the cluster to go into an incorrect state. [PR/292411] • On J-SRX Series devices in a chassis cluster, using the set system processes chassis-control disable command for 4 to 5 minutes and then enabling it causes the device to crash. Do not use this command on a J-SRX Series device in a chassis cluster. [PR/296022] • On a J-SRX210 device in a chassis cluster, when you upgrade the nodes, sometimes the forwarding process might crash and get restarted. [PR/396728] • On a J-SRX210 device in a chassis cluster, sometimes the reth interface MAC address might not make it to the switch filter table. This results in the dropping of traffic sent to the reth interface. As a workaround, restart the Packet Forwarding Engine. [PR/401139] • On a J-SRX210 device in a chassis cluster, the fabric monitoring option is enabled by default. This can cause one of the nodes to move to a disabled state. You can disable fabric monitoring by using the following CLI command: set chassis cluster fabric-monitoring disable [PR/404866] • On a J-SRX210 Low Memory device in a chassis cluster, the firewall filter does not work on the reth interfaces. [PR/407336] • On a J-SRX210 device in a chassis cluster, the restart forwarding method is not recommended because when the control link goes through forwarding, the restart forwarding process causes disruption in the control traffic. [PR/408436] • On a J-SRX210 device with an FTP session ramp-up rate of 70, either of the following might disable the secondary node: 30

  • 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
Outstanding Issues In Junos OS Release 10.3 for J-SRX Series Services Gateways
The following problems currently exist in J-SRX Series devices. The identifier following
the description is the tracking number in our bug database.
Application Layer Gateways (ALGs)
•
On J-SRX210 devices, the SCCP call cannot be set up after disabling and enabling the
SCCP ALG. The call does not go through. [PR/409586]
•
On J-SRX240 devices, the maximum SCCP calls cannot be made under stress
conditions. [PR/490839]
•
On J-SRX Series devices, SIP server protection does not work. The
set security alg sip
application-screen protect deny
command does not work. [PR/512202]
AX411 Access Point
•
On J-SRX210 PoE devices, the access point reboots when 100 clients are associated
simultaneously and each one is transmitting 512 bytes packets at 100 pps. [PR/469418]
Chassis Cluster
•
On J-SRX Series devices in a chassis cluster, configuring the
set system process
jsrp-service disable
command only on the primary node causes the cluster to go into
an incorrect state. [PR/292411]
•
On J-SRX Series devices in a chassis cluster, using the
set system processes
chassis-control disable
command for 4 to 5 minutes and then enabling it causes the
device to crash. Do not use this command on a J-SRX Series device in a chassis cluster.
[PR/296022]
•
On a J-SRX210 device in a chassis cluster, when you upgrade the nodes, sometimes
the forwarding process might crash and get restarted. [PR/396728]
•
On a J-SRX210 device in a chassis cluster, sometimes the
reth
interface MAC address
might not make it to the switch filter table. This results in the dropping of traffic sent
to the
reth
interface. As a workaround, restart the Packet Forwarding Engine.
[PR/401139]
•
On a J-SRX210 device in a chassis cluster, the fabric monitoring option is enabled by
default. This can cause one of the nodes to move to a disabled state. You can disable
fabric monitoring by using the following CLI command:
set chassis cluster fabric-monitoring disable
[PR/404866]
•
On a J-SRX210 Low Memory device in a chassis cluster, the firewall filter does not work
on the
reth
interfaces. [PR/407336]
•
On a J-SRX210 device in a chassis cluster, the restart forwarding method is not
recommended because when the control link goes through forwarding, the restart
forwarding process causes disruption in the control traffic. [PR/408436]
•
On a J-SRX210 device with an FTP session ramp-up rate of 70, either of the following
might disable the secondary node:
30
Junos 10.3 OS Release Notes