05 Dec 07 Setting Up a 2-node Fail-over Cluster with OES 1

Step 4: Install NSS & NCS on Both Servers

The clustering services should be installed by invoking the GUI options from YaST because the process adds dependency checking so that the required packages are actually installed. Where clustering is concerned, the required packages are open-ipmi, heartbeat-stonith, heartbeat, novell-nss-admin-session-openwbem-provider, novell-nss and novell-cluster-services-km (I think).

Prior to installing you should make sure that the following packages are of the indicated version number or later.

novell-ncp-5.0.1-48

novell-ncpserv-1.3-6

novell-nss-4.9.20-1

evms-2.3.3-0.43

novell-cluster-services-km-1.8.2.57

Personally I will take the following steps to set up clustering while ensuring the packages are up-to-date. First I will go to the first server and invoke YaST > System > Novell Storage Services. This step will do the dependency checking and configure NSS for the cluster. There may be additional packages that need to be installed. If this is the case, be sure to invoke the Red Carpet GUI to update the newly installed packages.

The next step is to then configure NCS from YaST > System. Similarly, additional packages may need to be installed. Configure the cluster as descibed by Novell’s documents. If any new packages were installed, they should be updated using Red Carpet after configuration.

I then configured the Role Based Service (RBS) Configuration using iManager. This is to set up the privileges for the different users and modules in eDirectory.

Install NSS on the second server. After doing that (and updating), check the directory /opt/novell/oes_install for a file nssid.sh. If this file is present, run it. It supposedly adjusts the permissions of some files of the server which might be messed up by the installation of NSS.

Finally install NCS for the second server. There is no need to configure RBS as both servers are in the same tree. Reboot both servers after installing and configuring the cluster.

Step 5: Configure the Shared Storage

This is a two step process. First the storage devices have to be configured for use through EVMS. Then the devices have to be cluster-enabled through iManager.

5.1. Configure EVMS to Handle the Shared Storage

Before using EVMS, make sure that NCS is installed on ALL nodes that are in the cluster.

Then (preferably) from the master node start EVMSGUI. This will invoke the evmsd_worker process on the rest of the nodes. This is how the SAN storage devices are locked by EVMS and why EVMSGUI should not be left running unnecessarily.

Follow the steps as described in Novell’s documnetation for configuring the clustered resources. Below is a summary:

1. Check from the Volumes tab to see if the volume is there. If it is there, make sure to remove the Compatibility status from it.
2. Remove the Segment Manager from the disks using the Disks tab. Save.
3. Create a new Container and choose Cluster Segment Manager for it. It should be a private type.
4. Make this newly created container active by modifying its properties from the Container tab. As insignificant as this step may appear, you should NOT skip it! Save. Once saved, the ‘Dirty’ mark on the container should disappear.
5. Create a new EVMS volume on this container. Save.
6. Go to the Volumes tab and create a file system on the volume.

Cluster-enable the Volume

After configuring EVMS to be the volume manager for the storage, the next step is to use iManager to configure the volumes that can be failed over between the nodes. This step is clearly described with Novell’s documentation.

Step 6: Create the iPrint Resource

From iManager, create a cluster resource using the iPrint_Template. Edit the load/unload scripts accordingly.

I named this resource iprint_store.

Change the timeout value to 3 minutes and make sure that the Ignore Quorum option is unchecked.

The scripts are located in /etc/opt/novell/ncs and /var/opt/novell/ncs. I don’t know which one is the one used by iManager because the scripts in both locations should be identical.

Finally start the iPrint resource.

Step 7: Create the Driver Store and Print Manager

Before creating the Driver Store, create an organiztion unit (ou) Printers.main to hold the printer objects (where main is the root of the tree). The purpose of doing so is more for organisation than anything else.

From iManager > iPrint, click on Create Driver Store.

After the Driver Store is created, proceed to create the Print Manager (iManager > iPrint > Create Print Manager).

There might be an eror with the certificate when the Driver Store is first created. Click on the link and accept the certificate.

Edit the following files and remove the extra double quotes (“) at the end of the opening <OBJECT> tag at lines 12, 13 or 14:

• CreatePrinterDriverProfile2.jsp
• ModifyPrinterDriverProfile2.jsp
• PrinterDriverProfile.jsp
• ResourceDriversPage.jsp

I forgot where these files are located, but you can easily use the find or locate command to find these files.

Step 8: Add Printer Drivers

From iManager > iPrint > Manage Driver Store, click on Drivers.

If you are using Xerox Phaser printers, download the Windows drivers from Xerox’s website. Look out for the Microsoft PPD set of drivers. Unzip this file and then use the INF file to upload to iManager to install the printer driver.

Step 9: Create a Printer

iManager > iPrint > Create Printer

If the printer driver is available, it can be assigned to the printer immediately. Otherwise, it can be assigned later by clicking Manager Printer > Drivers.

Optionally, a printer profile may be created and subsequently assigned to the printer.

Step 10: Create a Printer Map

Make sure that ippsrvr.nlm is loaded in iManager.

Copy the map image to the location /var/opt/novell/iprint/htdocs/images/maps and the printer icons to /var/opt/novell/iprint/htdocs/images/printers.

Start Map Designer at http://<dns_name_of_iprint_service>/maptool.htm

Once the map is saved, upload it to the /var/opt/novell/iprint/htdocs folder.

(Next page “Install & Configure iFolder Enterprise & iFolder Web Access”)

Pages: 1 2 3

Tags: oes1