Allied Telesis Patch 89262-08 Manuel d'utilisateur Page 12

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 38
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 11
12 Patch Release Note
Patch 89262-09 for Software Release 2.6.2
C613-10402-00 REV I
When both Load Balancer and Firewall were configured, the very first TCP
session was established after rebooting. Subsequent TCP session startup
packets may have been routed out to an incorrect interface causing sessions
to not be established. This issue has been resolved.
A customer port in one nested VLAN could be set to be a core port in
another nested VLAN. This issue has been resolved.
When a particular model of SFP is fitted, and a switch reboot occurs, the
switch could get locked in a reboot cycle, and never manage to finish
booting. This issue has been resolved.
When the status of an interface changed, the BGP revaluation of IP routes
for redistribution (via the add /jointfilesconvert/391269/bgp import or add /jointfilesconvert/391269/bgp network commands)
was incorrect. This gave inconsistent BGP route tables depending on the
order of events. This issue has been resolved.
Multicast data failed to be forwarded by PIM-SM if an MLD report was
received on the switch before the corresponding multicast stream had
arrived. This issue has been resolved.
Problems could occur if hardware filters or QOS policies were created using
a classifier matching on: a Layer 2 attribute other than MAC Destination
(e.g. MACSA or VLAN ID), and one or more other parameters that match
on IPv4 frames (e.g. IP address, UDP/TCP parameters), and another
classifier matching on Layer 2 attributes only.
The possible problems were; a generic Layer 2 match only succeeding if the
frame was not of IP type, or false-positive matches when a frames had the
same MAC Destination as a classifier designed to match on MAC Source
address. This issue has been resolved.
If a classifier was created that used the ethformat and protocol parameters,
the resulting entry in a script created using the create config command or
show config dynamic commands was not always correct. This issue has
been resolved.
When a Novell IPX packet was received by a port in a a protocol-based
VLAN, it was being flooded out all ports on the default VLAN. This issue
has been resolved.
1.) A port was remaining in the default VLAN after having been added to
a nested VLAN.
PCR: 40530 Module: IPG Level: 2
PCR: 40531 Module: VLAN Level: 2
PCR: 40535 Module: SWMX Level: 2
PCR: 40537 Module: BGP Level: 2
PCR: 40538 Module: IP6, SWI Level: 2
PCR: 40540 Module: SWI Level: 2
PCR: 40541 Module: CLASSIFIER Level: 2
PCR: 40543 Module: SWMX Level: 2
PCR: 40544 Module: VLAN Level: 2
Vue de la page 11
1 2 ... 7 8 9 10 11 12 13 14 15 16 17 ... 37 38

Commentaires sur ces manuels

Pas de commentaire