E/Osc Versus E/Osn And E/Osi - Fibre Channel Protocol-Related Differences - McDATA StorageWorks 2/140 - Director Switch Planning Manual

Products in a san environment
Hide thumbs Also See for StorageWorks 2/140 - Director Switch:
Table of Contents

Advertisement

Firmware Summary

E/OSc versus E/OSn and E/OSi - Fibre Channel Protocol-Related Differences

Table B-2
Feature
Expansion port (E_Port)
staging
ESS payload
processing and domain
port number zoning
Registered state
change notification
(RSCN) coalescing
Generating fabric
format RSCNs after
CTP failover (directors)
Hop count restriction
Exchange switch
capabilities (ESC)
support
McDATA Products in a SAN Environment - Planning Manual
B-4
E/OSc 8.0
E_Port staging not supported.
E/OSc Version 6.0 (or earlier)
handshakes the ESS sequence
but does not apply content of
ESS payload to calculate port
numbering (PN) to logical port
address (PA) mapping. Legacy
directors and switches are
assumed to use an offset of four
for PN to PA mapping.
Only fabric login (FLOGI) and
Name Server events are
coalesced.
Does not replicate RSCN event
triggers, therefore transmits a
fabric format RSCN to all
attached devices after CTP card
failover.
Hop count of up to three is
supported. Devices more than
three hops away cannot be
reached.
SW_ILS ESC sequence not
supported.
E/OSn 6.0
The Intrepid 10000 Director
supports E_Port staging. The
director allows only one E_Port
connection to a neighbor switch
to take part in a fabric build
process. Upon process
completion, subsequent E_Ports
to neighbor switches are brought
up (staged). In addition, staged
E_Ports are brought up in
groups to minimize Class F
traffic and avoid overloading.
The Intrepid 10000 Director
sends and accepts payloads
specifying minimum and
maximum logical port addresses
and processes payload content
to calculate PN to PA mapping.
A correct mapping scheme
interprets domain port number
zoning enforcement across the
fabric and allows the director to
participate in a legacy fabric with
domain port number zoning.
The Intrepid 10000 Director
coalesces all events that trigger
and transmit RSCNs to N_Ports.
This minimizes the number of
RSCNs generated.
Replicates events that trigger
RSCNs to the backup CTP,
therefore does not generate a
fabric format RSCN after CTP
failover.
No hop count restriction is
applied.
The Intrepid 10000 Director
processes SW_ILS ESC
sequences to identify
neighboring director ports.
E/OSi 4.6
E_Port staging not supported.
E/OSi handshakes the ESS
sequence. However, domain port
number zoning not supported.
SAN routers coalesce all RSCN
events.
RSCNs after CTP failover not
supported.
No hop count restriction is
applied.
SW_ILS ESC sequence not
supported.

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents