Dell POWEREDGE M1000E Bedienungsanleitung Seite 5

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 62
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 4
Fabric OS v6.4.1 Release Notes v1.0 Page 5 of 62
Quick Look
Fabric OS (FOS) v6.4.1 is a maintenance release based on FOS v6.4.0. All hardware platforms and
features supported in FOS v6.4.0 are also supported in v6.4.1. This release also contains fixes for
many defects including those from the FOS v6.4.0a, b, and c patch releases.
In addition to the fixes noted above and listed in the defect tables at the end of this document, FOS
v6.4.1 also includes support for several features.
Overview
New Features & Support
In addition to fixes for defects, there is new support in FOS v6.4.1 including:
Support for N_Port Trunking
N_Port TrunkingN_Port Trunking
N_Port Trunking when used in conjunction with Brocade HBAs with v2.3.0 (and later)
software. N_Port Trunking allows two physical 8 Gbps links to be combined into a single logical 16
Gbps link. Use of this feature requires that the Brocade Trunking and SAO licenses are installed on
the FOS-based switch to which the Brocade HBA is connected.
Support for DCBX Application Protocol Type Length Values (TLV), aka “iSCSI TLV
iSCSI TLViSCSI TLV
iSCSI TLV.” This enables priority
mapping and announcement of support for this mapping to attached devices for iSCSI protocol traffic
over DCB links. This feature is supported and available only for the Brocade 8000.
The Brocade FS8-18 Encryption Blade and the Brocade Encryption Switch now support
I
II
IBM’s Tivoli
BM’s Tivoli BM’s Tivoli
BM’s Tivoli
Key Lifecycle Manager
Key Lifecycle ManagerKey Lifecycle Manager
Key Lifecycle Manager. IBM Tivoli® Key Lifecycle Manager provides a centralized key management
service for IT organizations that enables them to manage their encryption key lifecycle throughout the
enterprise.
Bottleneck Detection Enhancements
FOS v6.4.0 enhances bottleneck detection
enhances bottleneck detectionenhances bottleneck detection
enhances bottleneck detection capability by adding support for congestion detection at E, Ex and F
support for congestion detection at E, Ex and F support for congestion detection at E, Ex and F
support for congestion detection at E, Ex and F
ports.
ports.ports.
ports. Bottleneck monitoring configuration has been greatly simplified in FOS v6.4.0 by allowing switch-level
enablement of this feature for both latency and congestion bottleneck monitoring. New enhancements allow
users to configure separate thresholds for detecting latency bottleneck and congestion bottleneck conditions.
Bottleneck monitoring alerts can be configured on a per port basis and are delivered through SNMP traps and
RAS logs.
FOS v6.3.1b introduced several changes and enhancements that are also included in FOS v6.4. These
changes are not fully documented in existing Admin Guides or other materials but will be captured in future
documentation and existing documentation updates and revisions. A brief summary of these enhancements
follows:
General improvements to Bottleneck Detection on both 4G and 8G platforms including improved
improved improved
improved
accuracy on reporting latency
accuracy on reporting latencyaccuracy on reporting latency
accuracy on reporting latency and reporting of latency va
reporting of latency vareporting of latency va
reporting of latency values
lueslues
lues in Bottleneck Detection events.
Identify credit lost condition
Identify credit lost conditionIdentify credit lost condition
Identify credit lost condition on 4G and 8G E_Ports and generate a RASLOG message (C2-5021) when
detected. Unlike previous reporting that indicated when all credits for a VC were missing, this new
capability reports on individual credit loss. This capability is enabled by default and is not
configurable.
New option to configure the switch
option to configure the switchoption to configure the switch
option to configure the switch “edge hold time,
edge hold time,edge hold time,
edge hold time,” allowing the switch to timeout frames for F_Ports
sooner than for E_Ports. Proper use of this capability (disabled by default) reduces the likelihood of
devices with high latencies causing frame drops in the core of the fabric and impacting other
unrelated flows. Details on usage and recommended settings will be available in separate
documentation.
Seitenansicht 4
1 2 3 4 5 6 7 8 9 10 ... 61 62

Kommentare zu diesen Handbüchern

Keine Kommentare