> I'm about to go down the path of migrating DNS/DHCP services from
> physical Netware OES1 boxes to virtual OES2 Linux machines.
>
> I've had a read through the migration doco and was wondering if I can
> accomplish a migration in the following manner:
>
> (I have two servers, each running dhcp and nds.)
> Move dhcp ranges from Server2 to Server1
> remove dhcp/dns from Server2 and remove from tree
> Install new OES2 linux server with same address as Server2
> Install dns/dhcp services on new server
> Add dns zones to server
> move dhcp ranges back to new server
> Repeat for Server1
>
> Or am I completely barking up the wrong tree?
Since you mention moving DHCP/DNS from Server 2 to Server 1 and moving
DHCP ranges back to new server I just want to flag that OES Linux uses
different DHCP objects so it's not a case of moving NetWare DHCP objects
to OES Linux and it will work.
You can use Novell's migration tool (miggui) to do this or do so via a
command line tool /opt/novell/migration/bin/migdhcp.sh. However whilst
it can handle tree, server or subnet level migrations it doesn't quite
offer the granularity that we want - to migrate groups of hosts at a
time rather than all on a subnet - so I'm writing my own script as both
NetWare and OES Linux DHCP info is stored in eDirectory and accessible
via LDAP.
HTH.
--
Simon
Novell Knowledge Partner (NKP)
------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partners (TTP) group. See www.novell.com/ttp for more details.
------------------------------------------------------------------------
> Just so I understand correctly, in the DNS/DHCP management
> console/iManager you can't assign an OES2 linux server, ranges that were
> hosted by a Netware server?
No, different schema = new objects.
See http://www.novell.com/coolsolutions/appnote/19638.html which should
help explain the differences between NetWare and OES Linux handling of DHCP.
When it comes to migrating, I would strongly suggest migrating to a test
tree first (don't worry since NetWare objects will still exist
afterwards) since I've found a few issues in the migration scripts that
could result in a broken state. These have been reported to Novell.
> Sorry, I'd lost this thread. As the objects are different, I should
> have no problem migrating subnets?
I won't say that you'll have no problems (as there are a few bugs in the
DHCP migration scripts) but theoretically yes.
> If I understand correctly, I can migrate everything to the new OES2
> server and if something doesn't work, all the netware information is
> still available, I can just fire up dhcpsrvr.nlm again.
Correct.
If you want to keep things running whilst you do the migration you could
even leave DHCPSRVR running on the NetWare before, during and after the
migration though in order to know the migration worked you should unload
the NLM.