Building OES 2 Linux servers for on a local network is fairly straight forward. You build your server, virtual or physical, configure your resources and services and you are pretty much done. Deploying OES 2 Linux servers to a remote location is something quite different. There are questions as to replicas, remote IP addressing schemes, printing, etc.
In the days of NetWare, reconfiguring a server to be deployed was simple. Take any replicas off the server, in case it got lost in shipping. Had a server bound for Australia and ended up on a dock in Singapore for several weeks before I knew and had shipped out another server. Not a good thing to have when the server has a replica on it. There was getting the IP changes to Apache and Tomcat, but for the most part, not too difficult.
OES 2 Linux hard codes the server's IP address in many locations throughout the configuration. This means that, not only do you have to change them in certain objects in eDirectory, you also have to edit a few files also. Now, you might be thinking, “Why not just build the server with the remote IP address?” That would be fine if you had a VLAN and routes set up for that scheme, locally. I, like most large organizations, have a separate group or department that handles layers 1-4 type devices, and they have their own projects and tasks. It may not be viable for them to set up a separate VLAN for your convenience.
In this article, we will walk through preparing an OES 2 Linux server for remote deployment and what is needed after the server is back on line. I'll point out some pitfalls and gotchas that I have experienced while deploying OES 2 Linux servers to remote locations. This will also include international deployment and things, such as export laws, that normally we don't consider when we ship servers around the United States.
We will not walk through an actual OES 2 Linux server installation. There are several articles that cover that subject exhaustively and I assume that you already have that part covered. I will point out that there are several packages that need not be configured until the server is on site, thus saving you time in the long run.
The OES 2 Linux server we will use is installed with the following packages:
Novell eDirectory Novell DNS Novell DHCP Novell iManager Novell iPrint Novell Linux User Management (LUM) Novell NCP Server / Dynamic Storage Technology Novell Remote Manager (NRM) Novell Storage Services (NSS)
When you install your OES 2 Linux server do not configure the following services:
Novell DNS Novell DHCP Novell iPrint
We will configure these services when the server is on site.
This server is to reside in it's own Organization Unit. I did not create a partition for this container before the server install and therefore, did not have to remove any replicas off this server after installation. Once the server is on site, on line and communicating with the tree, then we will create a partition for this site which will be covered later in this article.
You can add any additional software your organization requires, such as virus protection. As a rule, install any software that might require the use of the console and the server's own physical resources, such as the CD/DVD drive. I don't use any fancy scripts or complex installation repositories for my installs. Also, move any large data bundles, such as Novell ZENworks Applications (NAL applications) over to the new server at this time.
When all of this is complete, we're almost ready to shut this server down and ship it. Continue to the next section, when you are ready to ship.
Now, we are ready to shut down the server, box it up and ship it out. But first there are a few things we need to change before we shut it down. Using your favorite vi editor, make the following changes to each file listed.
preferred-server=<server's new IP address>
n4u.server.interfaces=<server's new IP address>@524
http.server.interfaces=<server's new IP address>@8028
https.server.interfaces=<server's new IP address>@8030
/etc/sysconfig/novell/ldap_servers/<server's old IP address> - Rename this file to the new IP
CONFIG_LDAP_SERVER=”<server's new IP address>”
CONFIG_LUM_LDAP_SERVER=”<server's new IP address>”
CONFIG_SMS_LDAP_SERVER=”<server's new IP address>”
CONFIG_NSS_LDAP_SERVER=”<server's new IP address>”
CONFIG_IPRINT_LDAP_SERVER=”<server's new IP address>”
CONFIG_DHCPSRV_LDAP_SERVER=”<server's new IP address>”
CONFIG_DNS_LDAP_SERVER=”<server's new IP address>”
<server's new IP address> Servername.myorg.com servername
If you have any other applications that have references to the server's IP address, edit them as well.
After you have completed all that editing, run YaST lan and change the IP addresses on your NIC cards and don't forget your Default Gateway.
When you are done, shut down the server and power it off.
Now you are really ready to box it up and ship it off.
International Export Considerations
Everything that leaves the United States is subject to Export Control. This is especially true for software. Each item has an Export Classification Control Number (ECCN). This number defines what is needed to export a particular item, if at all. Novell has a list of ECCNs for each of their products. To determine what can be exported, look here.
The add process begins and you can view the progress by clicking Replica View and selecting the new server. When the status listed changes from Add to On, the partition operation is complete and a Read / Write replica will reside on the new server. Run an ndstrace to check the replication status and ensure that your new partition is healthy along with the rest of the tree.
Using iManager, you can proceed to configure your SLP, iPrint, DNS and DHCP, if applicable. I'm not going to walk you through configuring these services. They are configured no differently than what the documentation provides.
Deploying Open Enterprise Server 2 Linux to a remote location has a few more steps that are not widely documented. Hopefully, you can create your own script or process for automating this deployment more smoothly.