Allied Telesis Patch 89262-08 manual PCR 40413 Module QOS Level, PCR 40416 Module QOS Level

Patch 89262-08 For AT-8900 Series Switches 13

PCR: 40411 Module: IP6 Level: 2

In certain cases where static routes in a multi-path environment were used and routes were changed on the switch, the IPv6 flow table of the switch wasn't refreshed correctly, i.e. an entry in the flow table had no outgoing interface and ND entry. This issue has been resolved.

PCR: 40413 Module: QOS Level: 3

The command reset qos accel was generating an unexpected error message.

This issue has been resolved.

PCR: 40415 Module: VRRP Level: 2

When a master VRRP router was configured from a bootup script, the transition to the MASTER state occurred before the Layer 2 interface had been initialised, preventing the gratuitous ARP from being sent. This issue has been resolved.

PCR: 40416 Module: QOS Level: 3

The output of the show qos trafficclass=x command was not correctly indicating the state of the parameter "Ignore BandwidthClass". This issue has been resolved.

PCR: 40417 Module: OSPF Level: 3

When LS Acks (Link State Advert acks) were received, they were compared against the transmitted LSA (Link State Advert). If it was the same, the LSA was removed from the re-transmission list. The algorithm used in this check has been changed to be compliant with the algorithm specified in section

13.1of RFC2328, to determine if the LS Ack received is the instance as the LSA.

PCR: 40418 Module: SWMX Level: 3

When the IPv6 Accelerator card was enabled in loopback mode, and you used an SNMP management station to display the forwarding database, a random value was displayed for one CPU MAC entry. This issue has been resolved.

PCR: 40422 Module: FIREWALL Level: 3

A problem existed when setting non-default Firewall attack trigger levels for SMTP attacks. The show firewall policy attack output and dynamically generated configuration scripts were incorrect. This issue has been resolved.

PCR: 40425 Module: VLAN Level: 2

When a private VLAN had a tagged uplink, and at least one untagged private port, a configuration generated using the create conf command would contain incorrect information. This issue has been resolved.

Patch 89262-08 for Software Release 2.6.2 C613-10402-00 REV H