We had to change the IP address of our Publisher too. We had a couple of problems despite extensive planning on the front end. We forgot to change it in the "Configuration and Repository" section within the IVR. Also, the database replication broke which required the "DBHelper" utility. Expect the replication to break.
Be sure that DNS is updated with the new IP address. Some things in our setup look for the ip address and other stuff uses the server name. It's my own fault for not being consistent. :)
Something else to be aware of is making sure the routing and the vlans are correct. We had both the publisher and subscriber in the same vlan even though they are physically 15 miles apart (spanned vlan over a MAN connection). We created a new vlan for the Publisher (and other IPT servers) to end the spanning of the vlan (spanned vlans over a MAN is not the best practice). I believe our network guy had to setup the access lists to enable the routing over the MAN. I don't know routers yet, so I'm not 100% sure.
Do lots of planning on the front end and have a good test plan. You may want to have a backout plan too. There are so many places that reference the publisher's ip. Expect something to go wrong. We opened up a TAC case on the front end and I've attached the pdf they recommended. It helped.
Hopefully, others will share their experience on this thread.
Stu
