Changing network IP Addresses

[kstakem]

Hi all,

I need to re-IP our network to a new range and I was wondering if I could get some advice. I know to change the IP on the switch and the VM Server, but there has to be more. I know i need to change the configuration of the Shoretel Software but I don't see a way to do that. Any help would be great!

Thanks

Kevin

[Forum]

Here's what I would do...
Change the IP address of the server in Shoreware Director first. After you do this, you will not be able to get back in until AFTER you change the IP on the address on the network card, AND REBOOT!

So, now Director, and the server have new IP's. Chyange the IP of the switches in Director, then change them on the switches (assuming htey are static IP's). This is done from the console port on the switch. (It can also be done by telnet, but this is much harder. Also, you have to use the telnet option from the Shoreware Server..so if your gonna do it via telnet, then YOU MUST DO THIS FIRST!...Once you change the IP of the server, they'll be on different subnets!)

Now...Director/Server, and Switches are done...make sure they're all communicating. If you have remote sites, then those switches will also have to be changed. There is a setting on each static switch that tells it where the server is, so you will have to adjust that.

Once you have all DVM's and Remote switches connected and up, change the DHCP scope. Then you will have to go around and physically reboot the phones. You might also consider changing the DHCP scope first, and rebooting the phones via director, not sure if that will make it any easier (the phones won't come up, as no switches would be configured at this point.)

Well...that's the gist of it. Make sense, or help at all???

Charles

[kstakem]

Thank You!

Charles you rock!

Everything makes perfect sense. I screwed up the order of things which was causing my confusion. Thanks for a great site

[Forum]

Charles you rock!

Everything makes perfect sense. I screwed up the order of things which was causing my confusion. Thanks for a great site

If you end up getting a Kadota.util error when logging into Director, then this usually means that the Director DB does not match the Server's IP address. If you just changed this, it won't sync until you do the reboot. If you reboot, and you are still getting the Kadota error, then you will need to modify the DB with Access. Changing the server is usually the hardest part to those who have never done it. I build systems at my office, prior to install, and then change IP's once I install the system, so I've done it a few times .

Charles

[kstakem]

Works like a charm!

Thanks for all the help