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
40-33
Cisco MDS 9000 Family CLI Configuration Guide
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Chapter 40 Configuring FCIP
Configuring FCIP
amount of data has been buffered at the local Cisco MDS switch, the read operations to the tape drive
are flow controlled by the remote Cisco MDS switch by not issuing any further reads. On completion of
a read operation, when some data buffers are freed, the remote Cisco MDS switch resumes issuing reads.
The default flow control buffering uses the
automatic
option. This option takes the WAN latencies and
the speed of the tape into account to provide optimum performance. You can also specify a flow control
buffer size (the maximum buffer size is 12 MB).
Tip
We recommend that you use the default option for flow- control buffering.
Tip
Do not enable time- stamp control on an FCIP interface with tape acceleration configured.
Note
If one end of the FCIP tunnel is running Cisco MDS SAN-OS Release 3.0(1) or later, and the other end
is running Cisco MDS SAN-OS Release 2.x, and tape acceleration is enabled, then the FCIP tunnel will
run only tape write acceleration, not tape-read acceleration.
Tape Library LUN Mapping for FCIP Tape Acceleration
If a tape library provides logical unit (LU) mapping and FCIP tape acceleration is enabled, you must
assign a unique LU number (LUN) to each physical tape drive accessible through a target port.
Figure 40-16
shows tape drives connected to Switch 2 through a single target port. If the tape library
provides LUN mapping, then all the four tape drives should be assign unique LUNs.
Figure 40-16
FCIP LUN Mapping Example
For the mappings described in
Table 40-1
and
Table 40-2
, Host 1 has access to Drive 1 and Drive 2, and
Host 2 has access to Drive 3 and Drive 4.
Table 40-1
describes correct tape library LUN mapping.
Host 1
Host 2
Switch 1
Switch 2
Drive 1
Drive 2
Drive 3
Drive 4
Tape library
FCIP link
180106
Содержание 9124 - Cisco MDS Fabric Switch
Страница 76: ...Se 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 ck d o c c i s c o c o m ...
Страница 122: ...Se 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 ck d o c c i s c o c o m ...
Страница 328: ...Se 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 ck d o c c i s c o c o m ...
Страница 482: ...Se 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 ck d o c c i s c o c o m ...
Страница 733: ...Se 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 ck d o c c i s c o c o m P A R T 5 Security ...
Страница 734: ...Se 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 ck d o c c i s c o c o m ...
Страница 957: ...Se 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 ck d o c c i s c o c o m P A R T 6 IP Services ...
Страница 958: ...Se 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 ck d o c c i s c o c o m ...
Страница 1182: ...Se 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 ck d o c c i s c o c o m ...
Страница 1214: ...Se 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 ck d o c c i s c o c o m ...
Страница 1307: ...Se 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 ck d o c c i s c o c o m P A R T 9 Traffic Management ...
Страница 1308: ...Se 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 ck d o c c i s c o c o m ...
Страница 1331: ...Se 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 ck d o c c i s c o c o m P A R T 1 0 Troubleshooting ...
Страница 1332: ...Se 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 ck d o c c i s c o c o m ...