Jump to content

Recommended Posts

Posted

We have a current project where we are performing an upgrade to one of our applications. Part of which is to replace the existing VM with a physical box (due to requirements). Due to FW rules we want to keep the IP Address the same as the existing box. The process will be roughly the following.

  • Install new application
  • Sync data/config
  • Turn off old VM
  • Update the IP address of the new Physical Server to Old VM.
  • Make sure we still have access to application

 

Normally I would not have any issues with this as I have done it with VM in the past. In that case it was easy enough as we have the console access to check the IP address and update it accordingly. However, as this box is a physical box and we do not have access to this I am a little cautious with this step. What steps can I take to ensure that when it comes to changing the IP the server will come back up and we will still have access?

Posted

I don't personally have access, we would need to request it. But this is how I assume it will be done. Does this mean that we would need to remove the old reservation and replace it with the new server MAC, Sync everything and it should do it on the fly or requires a reboot?

 

My main concern is basically loosing connection and not being able to get access to the server to force the new IP.

Posted

I'd be tempted to have a back-up admin account on the box in case there is some problem and you need somebody onsite to lay hands on the box.

 

Rather than DHCP you should be to add a second IP to the machine, and verify that you can remote in via that IP, then change the primary IP.

 

(IPv4 TCP/IP Properties->Advanced->Add)

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...