It's worth a shot. I've gone through the db manually, and changed all the
places where I could see the old IPs, but your way is much more efficient.
Doing it now and will report back soon. Thanks.

Best Regards,



Adam Scarcella


On Mon, Oct 28, 2013 at 6:53 PM, Andrija Panic <[email protected]>wrote:

> one of the crazy tries:
> backup your database, search for all IP addresses inside SQL file, map old
> to new IP addresses (old1 --> new1, old2 -->new2...) and then do
> search/replace each old one with new one.
> This is for netowrking/ip addresses (guest, public,etc), same for NFS
> serves, same for NFS host, etc...
>
> Not sure if that is going to make you UP again, but...
>
>
> On 28 October 2013 22:59, Adam <[email protected]> wrote:
>
> > Hi All,
> >
> > I know what I'm about to ask may seem like crazy talk, but I have a
> > situation at work where our CloudStack "box" was moved to another
> network.
> > This single server is a self-contained cloud with everything on one box.
> > I'm running CS 4.1.1 on CentOS 6.4 x86_64 with KVM and NFS for primary
> and
> > secondary storage mounts. It's a very basic configuration, but my company
> > moved from one town to another, and the IT dept decided to move our
> server
> > to a different switch and subnet without asking. So now literally every
> > single IP address of any importance has been changed.
> >
> > I've been trying in vain to get this CS up and running again, but it
> seems
> > like everything has changed including the guids, or at least that seems
> to
> > be the case since I cannot match up guids from the database to guids on
> the
> > primary/secondary NFS.
> >
> > I'm sure if each piece were separate and moved one piece at a time, it
> > would be fairly straightforward, but since this box is self-contained and
> > everything changed at the same time, it is proving to be very difficult.
> >
> > Does anyone have any suggestions for me to attempt to recover my CS?
> >
> > Best Regards,
> >
> >
> >
> > Adam Scarcella
> >
>
>
>
> --
>
> Andrija Panić
> --------------------------------------
>   http://admintweets.com
> --------------------------------------
>

Reply via email to