Chapter 27 San Device Virtualization - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

Fabric manager configuration guide, release 4.x
Hide thumbs Also See for AP775A - Nexus Converged Network Switch 5010:
Table of Contents

Advertisement

About SDV
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
Figure 27-2
While most of the examples in this chapter describe target virtualization, the initiator virtualization
Note
functions similarly.
Typically, today's deployments for handling device failures are designed for high availability (HA), with
redundancy being a key part of this design. Consider the situation where a target is designed to be
redundant. Two arrays are deployed–a primary and secondary in this situation. Enterprises often use
some type of consistency technology (such as EMF SRDF) between the primary and secondary arrays
to ensure that the secondary is a mirrored copy of the production LUN. However, if the primary array
fails, it must be replaced by the secondary because all I/O must occur on the secondary array. Problems
can occur because the time required to bring the secondary array up and have it working often takes
longer than most can afford
Figure 27-3
If a storage array is replaced without using Cisco SDV, then it may require the following actions:
Taking down a server to modify zoning and account for the new array.
Changing the Cisco NX-OS configuration to accommodate Fibre Channel IDs (FC IDs) and
pWWNs of the new array.
Changing a server configuration to accommodate the new FC IDs and pWWNs.
More specifically, without SDV you might experience the following conditions:
It can take a considerable amount of time to configure a secondary device for a typical production
environment.
In the zoning configuration, all the initiators must be rezoned with the secondary device, and certain
initiators must also be reconfigured. For example, the WWN and FC ID of the secondary device are
different, so driver files must be changed and the server must be rebooted.
Cisco MDS 9000 Family Fabric Manager Configuration Guide
27-2
Initiator Virtualization
Primary
initiator
Virtual
initiator
Secondary
initiator
(Figure 27-3
Typical Deployment for Handling Device Failures Before SDV
Servers
SAN
Traffic from
server
illustrates this dilemma).
I/O - Normal
I/O - After primary
failure
Chapter 27
SAN Device Virtualization
Primary
Device
Asychronous
Replication
Secondary
Device
OL-17256-03, Cisco MDS NX-OS Release 4.x

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents