McDATA StorageWorks 2/140 - Director Switch Planning Manual page 134

Planning Considerations for Fibre Channel Topologies
3
McDATA Products in a SAN Environment - Planning Manual
3-50
6. Configure PDCM arrays - For each director or switch managed
by the FICON management style, define the allow and prohibit
settings for FICON device connectivity. Use the Element Manager
application's Configure Allow/Prohibit Matrix - Active dialog box.
Port connectivity assignment
PDCM arrays for FICON connectivity management. The baseline
configuration for each fabric element must prohibit
communication between FICON and FCP devices.
— Because PDCM arrays affect port connections at the hardware
level, it is imperative to establish a range of port addresses for
FCP use and another range for FICON use. FCP-assigned
ports should be configured to allow communication with each
other and prohibit communication with FICON-assigned
ports, and vice versa.
— At the Configure Allow/Prohibit Matrix - Active dialog box,
assigning port names to logical port addresses is another
practice that should be followed. For example, the port name
for all FCP devices could begin with FCP or OS to indicate the
associated port addresses attach to open-systems devices. This
information emphasizes which ports are FCP ports and which
are FICON ports and gives a user the ability to better manage
the connectivity matrix.
— Caution should be exercised when using a PDCM array to
prohibit E_Port connectivity. For additional information, refer
to PDCM Arrays.
7. Configure zoning - Well-behaved intermix environments require
the creation of separate zones for FCP and FICON devices. Group
all FICON devices into one zone, then group FCP devices into
multiple zones in traditional fashion to facilitate typical open-
systems communication.
— Be aware that FICON devices do not use the Fibre Channel
name server, therefore name server-based zoning does not
affect FICON connectivity. However, the name server does
affect distribution of registered state change notification
(RSCN) service requests to FICON devices. If a FICON device
is not in the same zone as other devices, state changes are not
properly communicated.
(step 4) should be reflected in