• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 358
  • Last Modified:

lose my Vlan settings when moving server in cluster

hello,
I built a new 2008 std print server and placed in our cluster, when I try to move the server to a new node in the cluster I lose my Vlan settings altogether? Why is this and how can I make the network setting save to right vlan that I set.

0
bryant101
Asked:
bryant101
  • 4
  • 3
1 Solution
 
warddhoogheCommented:
This might be a Hyper-V bug.
After creating and booting the VM with non-default VLAN settings, shut the guest down to allow the settings to be saved to the cluster. Then power the guest again and check if solved after moving.
0
 
bryant101Author Commented:
1st response did not work; I made sure all the setting in the vlan where correct and then did a shutdown. With the Server on line I tried to move it and again I lost the vlan and it went right back to the default settings I have other servers in this cluster but this is the only one that is having issues.
0
 
bryant101Author Commented:
Issue was that I had an ISO mounted to the C drive; once I ejected the ISO I was able to move the Sever without losing my vlan.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
bryant101Author Commented:
Vlan save my setting
0
 
warddhoogheCommented:
what was the problem then? the mounted ISO or saving your Vlan settings?
0
 
bryant101Author Commented:
warddhooghe  pointed me in the right direction, But the ISO was mounted tp the C: drive and for some reason this stop the server from moving.

I add my notes:

Node Migration Issues:  When doing a Live/Quick migration or offline move, if the VLAN setting reverts back to the default setting, check to see if the Integration Tools .ISO (or any other .ISO that is not located on the Cluster volume) is mounted to the VM.  If so, connect to the VM, eject the .ISO and try the migration/move again, it should work.


To check for errors, from the VM’s Summary page, right click the VM, select ‘More Actions…..’ and then select ‘Refresh virtual machine configuration.  When it completes, view the report and look for errors.


When making hardware or even some software changes on a VM and you are prompted to restart the system, do a shutdown instead of a restart and then start the VM through the Cluster Failover Manager.  Note: an OS restart does not reset the physical or virtual hardware like a restart of a physical system does.
0
 
warddhoogheCommented:
Good to know, thanks for sharing!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now