Dell PowerConnect J-8208 Release Notes JUNOS version 10.2 - Page 10

Infrastructure, Interfaces, On J-EX Series switches,

Page 10 highlights

JUNOS 10.2 Software Release Notes commit operation. Use separate commit operations to commit the two configurations. [PR/490542] Infrastructure • On J-EX Series switches, MAC addresses not present in the forwarding database (FDB) because of hash collision are not removed from the Ethernet switching process (eswd). These MAC addresses do not age out of the Ethernet switching table even if traffic is stopped completely and are never relearned when traffic is sent to these MAC addresses, even when there is no hash collision. As a workaround, clear those MAC addresses from the Ethernet switching table. [PR/451431] • On J-EX Series switches, the static neighbor discovery protocol (NDP) entries for IPv6 addresses are cleared automatically after some time. [PR/453710] • On J-EX8200 switches, when IGMP snooping is enabled on an interface, the IPv6 multicast Layer 2 control frame is not forwarded to other interfaces in the same VLAN. [PR/456700] • On J-EX4200 switches with GRES enabled, when a backup member switch has a route to a destination whose egress member is on the backup member itself, packets generated on the backup member egress out of the switch. [PR/506119] • On J-EX Series switches, the clear interface statistics all command takes a long time to execute. [PR/509303] • On J-EX4200 switches, the headers in ARP requests sent from a virtual IP address contain the virtual IP address as the source address instead of the virtual MAC address. [PR/512488] • On J-EX8200 switches with a 10-gigabit uplink port, when the Routing Engine is switched over, the 10-Gigabit uplink port stops forwarding traffic in the egress direction. [PR/515011] • On J-EX8200 switches, the output of an SNMP walk on jnxOperatingTemp and jnxFruTemp does not show the temperature for line cards. [PR/524112] Interfaces • On J-EX8200 switches, aggregated Ethernet interfaces might go down and come back up for a few minutes while the switch is updating many routes. [PR/416976] • On J-EX8200 switches, after enabling GRES. you might not be able to connect to the management interface on the backup Routing Engine using Telnet, and an existing Telnet session with the management interface on the backup Routing Engine might become inactive. [PR/520966] • On J-EX8200 switches, the following message is logged frequently in the /var/log/mastership file: mcontrol_refresh_mastership: time 6 These messages are harmless. 10

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14

commit operation. Use separate commit operations to commit the two configurations.
[PR/490542]
Infrastructure
On J-EX Series switches, MAC addresses not present in the forwarding database (FDB)
because of hash collision are not removed from the Ethernet switching process (
eswd
).
These MAC addresses do not age out of the Ethernet switching table even if traffic is
stopped completely and are never relearned when traffic is sent to these MAC
addresses, even when there is no hash collision. As a workaround, clear those MAC
addresses from the Ethernet switching table. [PR/451431]
On J-EX Series switches, the static neighbor discovery protocol (NDP) entries for IPv6
addresses are cleared automatically after some time. [PR/453710]
On J-EX8200 switches, when IGMP snooping is enabled on an interface, the IPv6
multicast Layer 2 control frame is not forwarded to other interfaces in the same VLAN.
[PR/456700]
On J-EX4200 switches with GRES enabled, when a backup member switch has a route
to a destination whose egress member is on the backup member itself, packets
generated on the backup member egress out of the switch. [PR/506119]
On J-EX Series switches, the
clear interface statistics all
command takes a long time
to execute. [PR/509303]
On J-EX4200 switches, the headers in ARP requests sent from a virtual IP address
contain the virtual IP address as the source address instead of the virtual MAC address.
[PR/512488]
On J-EX8200 switches with a 10-gigabit uplink port, when the Routing Engine is
switched over, the 10-Gigabit uplink port stops forwarding traffic in the egress direction.
[PR/515011]
On J-EX8200 switches, the output of an SNMP walk on
jnxOperatingTemp
and
jnxFruTemp
does not show the temperature for line cards. [PR/524112]
Interfaces
On J-EX8200 switches, aggregated Ethernet interfaces might go down and come back
up for a few minutes while the switch is updating many routes. [PR/416976]
On J-EX8200 switches, after enabling GRES. you might not be able to connect to the
management interface on the backup Routing Engine using Telnet, and an existing
Telnet session with the management interface on the backup Routing Engine might
become inactive. [PR/520966]
On J-EX8200 switches, the following message is logged frequently in the
/var/log/mastership
file:
mcontrol_refresh_mastership: time 6
These messages are harmless.
10
JUNOS 10.2 Software Release Notes