[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] swapping raqs
- Subject: [cobalt-users] swapping raqs
- From: Josh Kuperman <josh@xxxxxxxxxxxxxxxxxx>
- Date: Wed Jun 25 08:06:01 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
I need to figure out how to move everything running from one RaQ to
another and back. I asked before about the migration utility and going
from an XTR to a 550 .. but I didn't get any replies which makes me
think it won't be easily done. I can use the migration utility info as
a guide, but ther is no XTR to 550 migration utility. So I will be
using the migration utility in the sense of reading what must be done
and probably running it on the XTR to see what files it will create,
it doesn't appear to be option for a rapid switch over.
I am now thinking it would be easiest if I had both machines up on the
network for a few days or so. I have some question about WAN vs LAN
connection and what will happen. I am picturing the following
scenario:
The XTR is managing my local network running DNS, DHCP, SMTP, WEB, and
everything that is accessed from the outside. I need to move most
of what I'm running to 550. If I pull the WAN ethernet connection on
the XTR and plug it into the 550, then connect the LAN connection on
the 550 to the LAN can I use iptables to forward everything to the XTR
until I have moved it all over?
I want to make sure I only have one path out. If both the XTR and 550
are simultaneous connected to the outside I see too many problems. I
want to just swap which machine has the WAN connection and forward all
the forward all the outside traffic, mail, web, or even everything to the
XTR until I configure those services on the 550. That way I can move
DNS, and the rest over one service at a time.
I am very unfamiliar with iptables..I have asked various questions
which I'm sure are still in the archive, where the answer was
basically I needed iptables and a newer kernel which is to a large
extent the reason for this project.
--
Josh Kuperman
josh@xxxxxxxxxxxxxxxxxx