Planning Considerations for Fibre Channel Topologies
Figure 23: Public device connectivity
Note:
connected and using the B_Port to communicate with a fabric device.
66
Public devices support normal fabric operational requirements, such as fabric
busy and reject conditions, frame multiplexing, and frame delivery order.
Private device — A loop device that cannot transmit an FLOGI command to
the switch nor communicate with fabric-attached devices is a private device.
As shown in
Figure
24, device D
communicate with any fabric-attached device. However, device D
communicate with switch-attached server S
Public and private devices are partitioned into two separate address spaces
defined in the Fibre Channel address, and the switch's embedded FL_Port
ensures that private address spaces are isolated from a fabric. The switch does
not support any other form of Fibre Channel address conversion (spoofing)
that would allow private device-to-fabric device communication.
A private device can connect to the switch (loop) while a public device is
is a private loop device that cannot
2
(using private addressing mode).
2
SAN High Availability Planning Guide
can
2