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

Class of Service (CoS), Dynamic Host Configuration Protocol (DHCP), Flow and Processing - load data

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 32 highlights

Junos 10.3 OS Release Notes Class of Service (CoS) • On J-SRX Series devices, class-of-service-based forwarding (CBF) does not work. [PR/304830] Dynamic Host Configuration Protocol (DHCP) • On J-SRX210 and J-SRX240 devices, when autoinstallation is configured to run on a particular interface and the default static route is set with the options discard, retain, and no-advertise, the DHCP client running on the interface tries fetching the configuration files from the TFTP server. During this process, the UDP data port on the TFTP server might be unreachable. Because of the TFTP server being unreachable, the autoinstallation process might remain in the configuration acquisition state. When autoinstallation is disabled, the TFTP might fail. In this case, you should manually fetch the file from the server or the client through the relay. As a workaround, remove the static route options discard, retain, and no-advertise from the configuration.[PR/454189] Flow and Processing • On J-SRX Series devices, the show security flow session command currently does not display aggregate session information. Instead, it displays sessions on a per-SPU basis. [PR/264439] • On J-SRX Series devices, when traffic matches a deny policy, sessions will not be created successfully. However, sessions are still consumed, and the unicast-sessions and sessions-in-use fields shown by the show security flow session summary command will reflect this. [PR/284299 and PR/397300] • On J-SRX Series devices, configuring the flow filter with the all flag might result in traces that are not related to the configured filter. As a workaround, use the flow trace flag basic with the command set security flow traceoptions flag. [PR/304083] • On J-SRX210 and J-SRX240 devices, after the device fragments packets, the FTP over a GRE link might not perform properly because of packet serialization. [PR/412055] • On J-SRX240 devices, traffic flooding occurs when multiple multicast (MC) IP group addresses are mapped to the same MAC address because multicast switching is based on the Layer 2 address. [PR/418519] • On a J-SRX210 onboard Ethernet port, an IPv6 multicast packet received gets duplicated at the ingress. This happens only for IPv6 multicast traffic in ingress. [PR/432834] • On J-SRX240 PoE devices, the first packet on each multilink class gets dropped on reassembly. [PR/455023] • On J-SRX210 and J-SRX240 devices, the serial interface goes down for long duration traffic when FPGA 2.3 version is loaded in the device. As a result, the multilink goes down. This issue is not seen when downgrading the FPGA version from 2.3 to 1.14. [PR/461471] • On J-SRX Series devices, system log messages about interactive commands to the system log server do not work. [PR/511110] 32

  • 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
Class of Service (CoS)
•
On J-SRX Series devices, class-of-service-based forwarding (CBF) does not work.
[PR/304830]
Dynamic Host Configuration Protocol (DHCP)
•
On J-SRX210 and J-SRX240 devices, when autoinstallation is configured to run on a
particular interface and the default static route is set with the options discard, retain,
and no-advertise, the DHCP client running on the interface tries fetching the
configuration files from the TFTP server. During this process, the UDP data port on the
TFTP server might be unreachable. Because of the TFTP server being unreachable,
the autoinstallation process might remain in the configuration acquisition state. When
autoinstallation is disabled, the TFTP might fail. In this case, you should manually fetch
the file from the server or the client through the relay.
As a workaround, remove the static route options discard, retain, and no-advertise
from the configuration.[PR/454189]
Flow and Processing
•
On J-SRX Series devices, the
show security flow session
command currently does not
display aggregate session information. Instead, it displays sessions on a per-SPU basis.
[PR/264439]
•
On J-SRX Series devices, when traffic matches a deny policy, sessions will not be
created successfully. However, sessions are still consumed, and the
unicast-sessions
and
sessions-in-use
fields shown by the
show security flow session summary
command
will reflect this. [PR/284299 and PR/397300]
•
On J-SRX Series devices, configuring the flow filter with the
all
flag might result in
traces that are not related to the configured filter. As a workaround, use the flow trace
flag
basic
with the command
set security flow traceoptions flag
. [PR/304083]
•
On J-SRX210 and J-SRX240 devices, after the device fragments packets, the FTP over
a GRE link might not perform properly because of packet serialization. [PR/412055]
•
On J-SRX240 devices, traffic flooding occurs when multiple multicast (MC) IP group
addresses are mapped to the same MAC address because multicast switching is based
on the Layer 2 address. [PR/418519]
•
On a J-SRX210 onboard Ethernet port, an IPv6 multicast packet received gets duplicated
at the ingress. This happens only for IPv6 multicast traffic in ingress. [PR/432834]
•
On J-SRX240 PoE devices, the first packet on each multilink class gets dropped on
reassembly. [PR/455023]
•
On J-SRX210 and J-SRX240 devices, the serial interface goes down for long duration
traffic when FPGA 2.3 version is loaded in the device. As a result, the multilink goes
down. This issue is not seen when downgrading the FPGA version from 2.3 to 1.14.
[PR/461471]
•
On J-SRX Series devices, system log messages about interactive commands to the
system log server do not work. [PR/511110]
32
Junos 10.3 OS Release Notes