HP Cisco Nexus 5000 Cisco MDS 9000 Family CLI Configuration Guide - Release 4. - Page 357

Chapter 13 Configuring Interfaces TL Ports for Private Loops Send documentation comments to [email protected] 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 "About Interface Modes" section on page 13-3. 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 13-6 lists the TL port translations supported in Cisco MDS 9000 Family switches. Figure 13-4 shows examples of TL port translation support. Table 13-6 Supported TL Port Translations Translation from Private initiator Private initiator Private initiator Public initiator - N port Public initiator - NL port Translation to Private target Public target - N port Public target - NL port Private target Private target 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 OL-18084-01, Cisco MDS NX-OS Release 4.x Cisco MDS 9000 Family CLI Configuration Guide 13-31