Specifications

B-10
McDATA Products in a SAN Environment - Planning Manual
Firmware Summary
Diagnostics
(port failure state)
Port set to Failed state upon
failing a user- invoked port
diagnostic test.
If external port diagnostics are
performed without a loopback
plug the diagnostic test fails, but
port is not set to Failed.
If external port diagnostics or
management port diagnostics
are performed without a
loopback plug, the diagnostic
test fails, but port is not set to
Failed.
Buffer-to-buffer credit
(BB_Credit) support
BB_Credit subject to a per-port
maximum value
and a product-wide (pool)
maximum value. Refer to
Distance Extension Through
BB_Credit for information.
BB_Credit subject to a per-port
maximum value and a
paddle-pair wide (pool)
maximum value. BB_Credit also
subject to remote fabric PFE
being enabled or disabled. Refer
to Distance Extension Through
BB_Credit for information.
Fibre Channel ports set to a
BB_Credit value of 16. Intelligent
ports support IP network
connectivity and not assigned
BB_Credits. Ports provide 96
MB of TCP packet buffering per
transmission direction.
Audit log entries related
to flexible partitioning
Flexpar feature not supported. When a user downloads
firmware, performs a CTP card
switchover, configures
partitioning, or clears the system
error light (or performs an
operation with system-wide
impact), the corresponding Audit
log entry is recorded only for the
ADMIN partition (0). Log entries
are processed differently for the
ADMIN partition (0) versus other
partitions (1 through 3).
Flexpar feature not supported.
Other log entries
related to flexible
partitioning
Flexpar feature not supported. Log entries (non Audit log) are
processed differently for the
ADMIN partition (0) versus other
partitions (1 through 3).
Flexpar feature not supported.
Audit log entries
(EFCM)
Log contains EFCM user name
and IP address of EFCM client.
Log contains only the IP address
of the EFCM server. Log does
not contain EFCM user name
and IP address of EFCM client.
Remote workstations (clients)
not supported through the
SANvergence Manager
application. The application
supports an APP log that is
functionally equivalent to the
EFCM Audit log. In addition, the
Element Manager application
has an Audit log independent of
SANvergence Manager.
Table B-3 E/OSc versus E/OSn and E/OSi - Management-Related Differences (Continued)
Feature E/OSc 8.0 E/OSn 6.0 E/OSi 4.6