Quantcast
Channel: VMware Communities : Unanswered Discussions - vCenter™ Server
Viewing all articles
Browse latest Browse all 3506

ESXI 5.5 Manual Migrations that shouldn't be allowed

$
0
0

Good Afternoon,

My question is can I somehow block hosts in one cluster from migrating to hosts / storage in a second cluster when both clusters are managed by the same Vcenter Server

?

Notes

- All clusters managed by one Vcenter Server running the latest version

- DMZ Cluster has different VLAN's configured (3), and has all cluster settings disabled.

- DMZ Servers are using LOCAL hard drives on the servers to store the files.

- Prod Cluster is using a Dell Compellent SAN which is only configured to allow the 4 Dells blade servers in the cluster access to it).

- Prod Cluster has different VLANS than DMZ and does not have any of the same ones the DMZ has, All Cluster settings enabled.

- This only happens when you try to move from the VM from the Host to another Host, If you attempt to select the cluster it errors out, but if you select a host in the prod cluster it passes all the checks.

- The only error that has to be fixed prior to migration, is for the NIC to be removed as the PROD and DMZ clusters have different Vlans.

 

Here is the situation, We have a DMZ (HA, DRS disabled), cluster with a few hosts (Poweredge R620), now all the VM's on those hosts are running on the servers local storage and do not have access to the SAN which happens to be a Dell Compellent,

 

Then we have our production cluster that has several dell blades running on an Dell Poweredge M1000e, which is connected to a Dell Compellent SAN (In the SAN, only blade servers in the M1000e have access to the SAN).

 

DMZ Cluster (HA Disabled, DRS Disabled, EVC Disabled)

Host 1 (Power Edge R620) Different site, Local storage only, 3 VM's)

-VM 1

-VM 2

-VM-3

Host 2 (Power Edge R630) Different site, Local storage only, 4 VM's)

-VM 4   (MOVED TO PROD CLUSTER, HOST 4)

-VM 5

-VM 6

-VM 7

Host 3 (Power Edge R620) Different site, Local storage only, 2 VMs)

-VM 8

-VM 9

 

Prod Cluster (HA Enabled, DRS Enabled, EVC Enabled)

Host 1 (Slot 1 M1000e M630), Connected to Compellent SCSI San.

-VM 10

-VM 11

 

Host 2 (Slot 2 M1000e M630), Connected to Compellent SCSI San.

-VM12

 

Host 3 (Slot 3 M1000e M630), Connected to Compellent SCSI San.

-VM 13

-VM 14

-VM 15

 

Host 4 (Slot 4 M1000e M630), Connected to Compellent SCSI San.

-VM 16

-VM 17

 

 

Today, I noticed someone was able to move a VM from Host 2 in Cluster DMZ (Lets say VM 4), to Host 4 in Prod Cluster, however the DMZ servers are not blades and do not have access to compellent but if they powered off VM 4 in the DMZ, it allows them to migrate it both datastore and host and I am not sure why it is doing this, as no Vmotion IP are set up on the DMZ.

 

I remember with our older Fibre SAN we had, if the host wasn't added in the san configuration, we would get an error saying the VM did not have access to the destination datastore, which is what we should be getting but we are not (DMZ Servers have 3 Vlans, Prod has around 30 but neither cluster has the same VLANS)


Viewing all articles
Browse latest Browse all 3506

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>