About ESXI Change Management network IP considerations

First of all, because the boss think the company network more complex unified into 10.5.x.x network segment, 23-bit mask 512 host extension, but specifically there are not so many machines, because the online platform has previously old network segment 192.168.x.x, so in ESXi host replacement management management Network encountered some problems, here to share;

1, Management network IP company training before the time said don't casually change, otherwise will be big, quack! ...... It is possible!

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6F/CE/wKiom1Wos6HjxW4KAAMWRNjvNg8855.jpg "title=" Manager-network.png "alt=" Wkiom1wos6hjxw4kaamwrnjvng8855.jpg "/>

Gray ground put if not must really don't move, will show a lot of problems, hehe.

1, here to note that the Vmkernel default gateway is preferably the network segment you are currently allocating adapters, that is, the new network segment 10.5.50.X,

Before 192.168.50.X, without change, can be directly on the relevant Swith add management network port namely vmotion and IP storage network, so it can also be used, and is two network segment IP can manage ESXi host, for specific reasons, may be similar to the native dual NIC in the internal bridging, not in-depth study. But now that we have changed, I will change it thoroughly.

2. Replace the gateway here with 10.5.50.1, then replace the management ip:10.5.50.37

Somehow, after the connection is not connected, Vmnic adapter is also the normal VLAN segment 10.5.50.X, it is inconceivable Ah!

3, Vm client are not connected, how to do? Only to the computer room to engage, and so on the keyboard, monitor, enter press F2

Prompt root password, think about should be the connection password ******* make the landing success!

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6F/CB/wKioL1WouLLR_PbVAAJ_cPriTSs331.jpg "title=" Shuoming-mn.jpg "alt=" wkiol1woullr_pbvaaj_cpritss331.jpg "/> Because the connection is not up, I think the adapter does not correspond correctly, see instructions are also about the management of the network, to enter the test!

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6F/CE/wKiom1Wot1fxSKOdAAHm8MSBF0g587.jpg "title=" Shuoming-mn1.jpg "alt=" Wkiom1wot1fxskodaahm8msbf0g587.jpg "/>

Notice here, with (...) ) is now the adapter used by the virtual machine and the normal connection status is Connected.

In order to test, I select each, press ENTER, will prompt

Select the adapters for this host ' s default management network connection,

Use the or more adapters for fault-tolerance and load-balancing.

This means that selecting multiple NICs will do fault tolerance and load.

One or more of the select adapters is already used for other connections.

Remove these adapters from their to current connections;

This means that you are sure you want to move out of a connection that is now running.

There is a second tip to pay special attention when moving out, otherwise the virtual Machine Connection virtual adapter card will be lost, I do too much, do not know that the step to one of the virtual machine to hang up, fortunately time is not long, otherwise to criticized ...

Is it: 650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/6F/CB/wKioL1WoulGim7y3AALKwBk9OFE784.jpg "title=" Manager-network1.png "alt=" Wkiol1woulgim7y3aalkwbk9ofe784.jpg "/>

After the final test one after another look at the end of their own cruel did not see clearly bound on the Mac, of course, on your client to open a ping management ip-t best, so do not run back and forth! A little reaction will be done ...

Here is a description of ESXi management IP and as shown in the IP is not directly related to the first configuration can be managed IP, when the replacement of IP, it is not necessarily, it depends on your experience

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6F/CB/wKioL1Wou3GBSb18AAJt35Cs4Ec776.jpg "title=" Shuoming-mn2.jpg "alt=" wkiol1wou3gbsb18aajt35cs4ec776.jpg "/> For example: The manager Network shown is: 10.5.50.36 but the actual ping does not pass, The connection is 10.5.50.37 because it is a virtual adapter, the two may be configured the same network segment it!

VM Client connection with the use of the IP to connect, or you will be a rib to ask why? Time is life, don't think too much!

Finally, be sure to check the virtual machine adapter is still there, the previous said.

All of the above changes are Vmclient connect ESXi first add VM Management Network and then add the new connection up, delete the old management network IP, please be aware!

Of course, directly in the computer room to change the server host machine is also possible, not to high-level, hehe!

This article from "Technical Achievement Self" blog, reproduced please contact the author!

About ESXI Change Management network IP considerations