Cisco MDS 9000 Series Configuration Manual page 49

Chapter 2 Configuring Interfaces
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Private loop devices refer to legacy devices that reside on arbitrated loops. These devices are not aware
of a switch fabric because they only communicate with devices on the same physical loop.
The legacy devices are used in Fibre Channel networks and devices outside the loop may need to
communicate with them. The communication functionality is provided through TL ports. See the
Interface Modes" section on page
Follow these guidelines when configuring private loops:
A maximum of 64 fabric devices can be proxied to a private loop.
•
Fabric devices must be in the same zone as private loop devices to be proxied to the private loop.
•
• Each private device on a TL port may be included in a different zone.
• All devices on the loop are treated as private loops. You cannot mix private and public devices on
the loop if the configured port mode is TL.
• The only FC4-type supported by TL ports is SCSI (FCP).
• Communication between a private initiator to a private target on the same private loop does not
invoke TL port services.
Table 2-6
examples of TL port translation support.
Table 2-6
Translation from
Private initiator
Private initiator
Private initiator
Public initiator — N port
Public initiator — NL port
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
2-3.
lists the TL port translations supported in Cisco MDS 9000 Family switches.
Supported TL Port Translations
Translation to
Private target
Public target — N port
Public target — NL port
Private target
Private target
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
TL Ports for Private Loops
"About
Figure 2-3 shows
Example
From I1 to T1 or vice versa
From I1 to T2 or vice versa
From I4 to T3 or vice versa
From I2 to T1 or vice versa
From I3 to T1 or vice versa
2-29