Votes - , Average rating: ( )

User manual Allied Telesis, model 86253-07

Manafacture: Allied Telesis
File size: 170 kb
File name: cd255500-f56d-e4b4-f9af-5c9705292885.pdf

Language of manual:

The document is loading, please wait

Download nowClose

The document is loading, please wait

Download nowClose

This issue has been resolved. PCR: 03723 Module: BGP Level: 2 BGP routes that were added after a summary aggregate route had been formed were not suppressed. This issue has been resolved: all routes added after summary aggregate route creation are also now suppressed. The SHOW BGP ROUTE command displayed unselected routes as the "best" route, until they had been processed. This issue has been resolved. When a single route was deleted from an aggregate route, the aggregate route was deleted, even if it contained other routes. This issue has been resolved. PCR: 03726 Module: TTY, USER Level: 3 The time recorded when a user logged in was overwritten when the same user logged in a second time while the original connection was still active. This meant the SHOW USER command displayed the same time for both connections. This issue has been resolved. PCR: 03733 Module: IPV6 Level: 3 When an oversize packet (PMTU) was received, an error message was not returned, even when IPv6 flow was enabled. This issue has been resolved. PCR: 03734 Module: IPG Level: 2 With static multicasting enabled on two VLANs, only the first few multicast packets of a stream were L3 forwarded. This issue has been resolved. PCR: 03751 Module: MLDS Level: 3 The MLD snooping entries registered on a port were not removed when the port went down or was unplugged. This issue has been resolved. PCR: 03757 Module: BGP Level: 2 Route flapping occurred with BGP when an interface went down. This issue has been resolved. PCR: 03771 Module: SWI Level: 2 When ingress rate limiting was used on Rapier switch ports, TCP sessions sometimes obtained a throughput that was lower than the configured ingress rate limit. This issue has been resolved. Patch 86253-07 for Software Release 2.5.3 C613-10382-00 REV E SHOW IGMPSNOOPING ROUTERADDRESS Patch Release Note PCR: 03780 Module: INSTALL Level: 3 If a configuration file had a long file name, the SHOW CONFIG command displayed the file name using the shortened DOS 8.3 format (where file names are 8 characters long, with extensions of 3 characters). This issue has been resolved so that long configuration file names are now displayed using the DOS 16.3 format (where file names are up to 16 characters long). PCR: 03789 Module: ETH Level: 2 When a 4-port ETH PIC card was installed, the output of the SHOW IP INTERFACE command showed the ETH port as Down, but the link LEDs on the card were lit. This issue has been resolved. The SHOW command now shows the correct link status. The link will go down after 90 seconds if no inbound traffic is received. When inbound traffic is received the link will come up. PCR: 03790 Module: SWI Level: 2 When a tagged port was deleted from a VLAN that was in the default STP, and the port was then added to the VLAN again, communications were sometimes not resumed on that port. This issue has been resolved. PCR: 03798 Module: IKMP Level: 3 ISAKMP did not support the IPSec message option ID_IPV6_ADDR_SUBNET (RFC 2407, 4.6.2.7). ISAKMP was using the ID_IPV6_ADDR (RFC 2407, 4.6.2.6) option instead. This issue has been resolved. PCR: 03801 Module: MLDS Level: 2 MLD and MLD Snooping accepted MLD Query packets with a hop limit greater than 1. Duplicate packets were forwarded when the hop limit was not 1 and the payload was 0::0. This issue has been resolved. MLD and MLD Snooping now require the hop limit to be 1. PCR: 03806 Module: VRRP Level: 4 After the SHOW VRRP command was executed, incorrect trigger messages were entered into the log. This issue has been resolved. PCR: 03809 Module: SWI Level: 2 An additional check has been added for unknown GBIC models to determine if they are copper or fibre. PCR: 03817 Module: IPV6 Level: 2 A fatal error occurred when IPv6 fragmented a packet. Also, when a large fragmented ICMP echo request packet was received, the reply may not have been fragmented and so may have exceeded the MTU for the interface it was sent on. These issues have been resolved. PCR: 03826 Module: BGP Level: 2 When BGP imported routes from IP with the ADD BGP IMPORT command, and there were multiple import choices, the best IP route was not always imported. This issue has been resolved. Patch 86253-07 for Software Release 2.5.3 C613-10382-00 REV E Patch 86253-07 For Rapier Series Switches SHOW IGMPSNOOPING ROUTERADDRESS PCR: 03828 Module: IPV6 Level: 2 The MTU value for IPv6 PPP interfaces was always set to 1280 bytes. This MTU value is now correctly set to 1500 bytes, and 1492 bytes for PPP over Ethernet (PPPoE). PCR: 03836 Module: OSPF Level: 2 OSPF sometimes chose routes with an infinite metric over routes with a finite metric when selecting the best local route. This issue has been resolved. PCR: 03839 Module: IPV6 Level: 2 A fatal error sometimes occurred when an IPv6 ping packet length exceeded 1453 bytes. This issue has been resolved. PCR: 03843 Module: DHCP Level: 2 When some DHCP entries were in Reclaim mode, and all interface links related to the range of these entries went down, th...