Practical Cloud Knowledge: Install, Configure, and Manage - Deploying and Managing a Cloud Infrastructure - page 204

■ Every instance of a VSAN is running all of the required protocols, such as FSPF, zoning,
and a domain manager.
■ Fabric-related settings or configurations in one VSAN do not affect other VSANs.
■ Traffic disruptions and other errors in one VSAN are contained there and will not
affect other VSANs.
The VSAN identifier is automatically assigned when you are creating a VSAN through
the console. Just remember that VSAN 1 is the default ID and that it is used for testing,
management, and communications purposes and should not be used as a production envi-
ronment VSAN. This is because it has some features that when configured can interfere
with normal traffic flows in a VSAN. So make sure that upon creation, you specify an ID
from the user-defined space, which is VSAN 2, 4093. VSAN 4094 is also reserved as the
isolated VSAN.
VSAN ID vs. VSAN Name
Take note that a VSAN ID is not the VSAN name. The VSAN name must be unique for
each VSAN. The VSAN ID serves to associate the VSAN with its name and will be used for
configuration and traffic routing, while the VSAN name is mostly useful only to the user
for more humanly understandable identification and easier management. By default, the
VSAN name is the word VSAN concatenated with four digits, which represent the ID. For
example, the default name for VSAN 2 is VSAN0002.
Virtual Resource Migration
Assuming that you have now chosen your cloud service provider or have constructed your
own private cloud, you are now ready to migrate all resources and enjoy the benefits of the
cloud. But before that, along with your research for what sort of cloud service your orga-
nization needs, you should have already planned what resources and services to migrate
and how it should be done in order to minimize downtime and ensure that everything goes
without a hitch. The following sections shed some light on this somewhat arbitrary process.
We say arbitrary because there are no standards set in stone and people usually have to
learn as they go along or from the mistakes and success of others.
Establishing Migration Requirements
When you planned on moving some or all of your business processes to the cloud, you con-
sidered the full extent of the endeavor and had embarked on research and studies before
actually committing to a service or starting construction of your own cloud. This is being