Adding first NW 6 Server into Tree

[jaybo71]

Have a mixed NW 5.0 and 4.11 environment ( mostly NW5 ). I am looking to add a NW 6 server int existing tree which I will use to migrate data off of the older NOS's. My goal is to have a Several NW6 servers as the core of the environment in the near future.

Anything I should be concerned about when adding a single NW6 box into the current production environment?

Just simply get it in the tree softly. Unfortunaltley I don't have the luxury of a test lab where I run these scenarios out myself.

Thanks.

 

[marvhuffaker]

If your tree is healthy, you should be okay. Some people prefer to upgrade the Master replica of [ROOT] first, but this is not really necessary. Just make sure you go through the deployment manager (on the nw 6.x CD) to extend the Schema. Go through the other pre-install steps in the deployment manager as well to verify that your tree is ready for NetWare 6.x. Also put the latest DS patch on each 4.x and 5.x server

When you update the schema, you have to do it to one of the servers with a replica of the [root] partition. But when you're ready to install the first server, it can really be anywhere.

Most important of all, make sure your tree is healthy and time is in sync. I've helped many companies recover from failed upgrades that would have been successful if they would have done some health checks prior to the upgrade.


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[Provogeek]

The schema stuff will be your most pain the the rump issue to deal with. To help you with the issues you will deal with having 4.11 servers in the mix with 6 server, try to make it so the 4.11 servers and the 6 server to not partitipate in the same replica ring. They can be in the same tree, but I run into access rights issues when they share a replica ring. This is caused by the fact that 4.11 does not understand many of the new atributes eDirectory introduces.

the DS on the 4.11 MUST be over 6.16, or kiss you database goodbye. Boy, that was a fun weekend when I found that one out.

Since you do not have any 5.1 servers in the mix, this new 6 server will also be your Certificate Authority. So comeup with an IP address for it, and stick to it. Don't ever change it. It is much easier to saw your own arm off with a spork from KFC than it is to change an IP address in a NetWare 6 box that also hosts the Certificate Authority. It can be done, but both Marv and I make a lot of money in billable hours doing it for customers that tried, and wacked their whole security infostructure. So be sure you do your home work, or just leave the IP as is once you set it. None of this, oh, I'll just use this IP address for now and change it later crap.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer

http://www.kiscc.com

 

[terry712]

what issues do you have with the CA
unfortunately i'm about to have to do it

 

[marvhuffaker]

Terry, are you serious? I don't recommend it, but here is a full discussion of what happens and what you need to do.

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10064111.htm

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[terry712]

afraid i need to do it

will rack bains and see if i can do it another way but no matter what way you do it - causes probs in other places
just a matter of how to minimise the hassle

is have the CA on a clustered server an issue - i know it will only be associated to one member of the cluster

problem with CA seems to be you end up (probably through stupidity - lack of planning or crystal ball) - on your main server - where get the impression - it's better on a small underused one