Allied Telesis 86253-07 User Manual

Page 13

Advertising
background image

Patch 86253-07 For Rapier Series Switches

SHOW IGMPSNOOPING ROUTERADDRESS

13

Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E

The port counters were not incremented:

ifInDiscards

ifinErrors

ifOutDiscards

ifOutErrors

This issue has been resolved.

The following SNMP MIB objects could not be set:

Dot1dStpPriority

Dot1dStpBridgeMaxAge

Dot1dStpBridgeHelloTime

Dot1dStpBridgeForwardDelay

This issue has been resolved.

DHCP was incorrectly using the directly connected network interface
source IP address as the source IP address of packets it generates. This issue
has been resolved. DHCP now uses the local IP address as the source
address for the packets it generates when a local IP interface address is set.
If a local IP interface address is not set, then it uses the IP address of the
interface where packets are sent from as the source address.

When the device rebooted with PIM or PIM6 enabled, it sometimes did not
send a Hello packet quickly enough. This issue has been resolved.

When a DHCP client was in the renewing state, and it sent a DHCP Request,
the device did not add the ARP entry to the ARP table. Instead, the device
generated an ARP Request in order to transmit the DHCP Ack. This caused
a broadcast storm in the network when the client kept sending DHCP
Requests. This issue occurred because the ciaddr field, not the giaddr field,
was checked in the Request packet when the device determined whether to
add the ARP entry. This issue has been resolved.

The current implementation of RSTP conforms to the IEEE standard
802.1w-2001. However, several minor deviations from the standard are
possible without having a functional impact on the behaviour of RSTP.
These changes are useful for debugging RSTP, and tidy up aspects of RSTP
that sometimes have no purpose. The following three variations have been
implemented:

The Learning and Forwarding flags are set in BPDUs to indicate the state
of the Port State Transition state machine.

The Agreement flag is set in BPDUs only when a Root Port is explicitly
agreeing to a proposal from a designated port. Do not set the Agreement
flag in BPDUs transmitted by Designated Ports.

PCR: 31145

Module: SWI

Level: 3

PCR: 31146

Module: SWI

Level: 3

PCR: 31147

Module: DHCP

Level: 3

PCR: 31148

Module: PIM, PIM6

Level: 2

PCR: 31152

Module: DHCP

Level: 2

PCR: 31154

Module: STP

Level: 4

Advertising