Open Enterprise Server Readme

1.2 Issues
8.0 eGuide
9.0 iPrint
24.0 TCP/IP
24.1.3 Virtual IP
24.1.9 Ipflt.nlm
24.1.10 Iptrace.nlm
24.1.11 Routecon.nlm
31.1.1 PHP
31.1.2 Perl

This Readme contains information regarding issues that affect the installation and usage of Novell® Open Enterprise Server (OES) Support Pack 2.

This document contains only a list of issues. For information on all of the features and components in Open Enterprise Server, see the Novell Open Enterprise Server Web site.

For planning and information, see the Novell OES SP2 Planning and Implementation Guide.

For complete information on setting up and using OES, see the Novell Open Enterprise Server online documentation.

Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items within a cross-reference path.

A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as UNIX* or Linux*, should use forward slashes as required by your software.

User Comments

We want to hear your comments and suggestions about this manual and the other documentation included with OES. To contact us, use the User Comments feature at the bottom of any page in the online documentation.

1.0 General Issues

This section contains information regarding general issues for Novell® Open Enterprise Server (OES) Support Pack 2 (SP2). For information about issues for specific components, see the sections pertaining to those components.

This document contains only a list of issues at the time OES Support Pack 2 released. For information on all of the features and components in Open Enterprise Server, please see the Novell Open Enterprise Server Web site or the Novell Open Enterprise Server online documentation. This document contains only a list of issues at the time OES Support Pack 2 released.

For a list of software fixes included in Support Pack 2, see the Open Enterprise Server Support Pack 2 List of Fixes. To view fixes included in NetWare 6.5 Support Pack 6, see NetWare 6.5 Support Pack 6 List of Fixes

1.1 Open Enterprise Server Platforms

Open Enterprise Server consists of two server platforms, SUSE® LINUX Enterprise Server 9 (SLES 9) with Support Pack 2 and NetWare®, as well as services that run on those server platforms.

1.1.1 Linux Support

OES SP2 is supported only on SUSE LINUX Enterprise Server 9 for x86 SP2, included with OES. There is no direct upgrade path from Novell Nterprise™ Linux Services 1.0.

1.1.2 NetWare Support

Installing OES Support Pack 2 for NetWare is the same as installing NetWare 6.5 with Support Pack 5. The codebase of OES Support Pack 2 and NetWare 6.5 Support Pack 5 are the same. You can upgrade to OES from previous versions of NetWare. Upgrading to OES on NetWare is essentially the same as upgrading from previous versions of NetWare to NetWare 6.5 SP5 and OES SP2 for NetWare. Unless otherwise noted, all previously available functionality of NetWare 6.5 still works.

1.2 Issues

This section contains information about issues that affect the general operation of OES after it is installed and initially configured. Other component-specific issues are noted in the Readme sections for those components.

1.2.1 Not All OES Client Components Have Been Tested in Windows XP SP2 Environment

Some problems might occur when accessing an OES server from a Windows* XP client with SP2 installed. For example, a pop-up might appear, saying that the publisher is unknown. Please report to Novell any additional problems that occur.

1.2.2 Installation Method When Creating a New eDirectory Tree

If you want to create a new eDirectory™ tree that contains both NetWare and Linux servers, you must start the tree creation using a NetWare server first.If you use a Linux server to create a new tree and subsequently add a NetWare server to it, you will not be able to install any client or server licenses. Any features that require either a NetWare Server license and/or Novell Client™ Access license will be inaccessible.For more information, see Adding a NetWare Server to an OES Linux Tree in the Novell OES SP2 Planning and Implementation Guide.

1.2.3 Linux Issues

The following issues exist on OES Linux:

Linux User Management (LUM) for passwd Utility Not Functional

Do not use the passwd utility to change the password for Linux User Management (LUM)-enabled users. To change the password for those users, use iManager or namusermod.

Linux User Management (LUM) for Pure-FTP Service Not Functional

Do not use the pure-FTP service. Use vsftp instead.

Occasional Server Hangs Due To Power Save Daemon

If your OES Linux server occasionally freezes up, it could be caused by powersaved. To resolve this, disable powersaved by completing the following:

  1. In YaST, select System > Runlevel editor > Powersaved

  2. Click Disable > OK.

  3. Click Finish to exit the Runlevel editor, then OK to exit YaST.

To disable kpowersave from displaying reminder messages and from loading at start up:

  1. From the KDE desktop, right-click the kpowersave icon in the menu bar.

  2. Click Quit, and then select to not have kpowersave loaded at startup.

1.3 Caveats

As you plan to install and implement OES, be sure to leverage the information in the Novell OES SP2 Planning and Implementation Guide, especially in Implementation Caveats and Installation/Upgrade/Migration Caveats.

2.0 NetWare 6.5 Support Pack 6 Issues

This section contains issues for NetWare® 6.5 Support Pack 6. Issues from previous Support Packs are in the OES Support Pack 2 Readme.

2.1 What’s New

In addition to software fixes, enhancements have been made to some of the components in NetWare 6.5 Support Pack 6. See the What’s New sections in the following administration guides:

2.2 Software Fixes List

To view fixes included in NetWare 6.5 Support Pack 6, see NetWare 6.5 Support Pack 6 List of Fixes.

2.3 Novell Audit 2.0.2 Update Available

A free update to Novell® Audit 2.0.2 is available separately at Novell Downloads. If you are using Novell Audit, you should download and install Novell Audit 2.0.2 Starter Pack. Updates to Novell Audit 1.0x are included in the Support Pack, but Novell Audit 1.0x is not included in the Overlay install.

2.4 NWConfig and Passwords

NWConfig has the ability to run installation scripts that include logging in to servers. Previously, NWConfig has uppercased passwords before passing them on to authentication. To be compatible with Novell’s future direction with case-sensitive passwords, this has been changed. We have seen a few issues in our testing when bindery logins are attempted. We have not seen any issues when the user and context are included, resulting in a directory login. If you are using bindery logins, this could be an issue.

2.5 Universal Password Support Added to Scrsaver.nlm

A new option has been added to scrsaver.nlm to support Universal Password. If you enable Universal Password and you also use scrsaver.nlm, you need to set the Universal Password option to Yes so that you can unlock your screen saver.

Table 2-1 Option Values for Universal Password

Value

Description

No

(Default) The password is uppercased.

Yes

Password case is not changed.

If you experience the following issues, see the correpsonding TID:

2.6 Upgrading iManager

If iManager 2.5 is installed on the NetWare server and you apply Support Pack 6, iManager and its plug-ins are automatically upgraded to version 2.6. For more information about iManager 2.6, see the iManager 2.6 Documentation.

If you are using iManager 2.02, iManager is not upgraded.

If you are already using iManager 2.6, no updates are installed, including plug-ins.

For more information about iManager 2.6 install scenarios with NetWare 6.5 Support Pack 6, see TID 3968737.

2.7 Using Web Bench

Beginning with NetWare 6.5 Support Pack 5, security was increased. If you are running tests using the Web Bench client that supports weak security, you might receive an error. To lower the server’s security so you can use Web Bench, see TID2974359.

2.8 Updates for Config.nlm

For more information about the latest changes to config.nlm, see TID 2974476.

2.9 Restart Tomcat to Avoid 500 Error

If you are updating Virtual Office or iManager by applying the Support Pack, you might receive a 500 error when Virtual Office or iManager loads the first time. Restarting Tomcat resolves the issue.

To restart Tomcat:

  1. At the system console, enter tc4stop.

  2. To start Tomcat, enter tomcat4.

    You should wait about 30 seconds after stopping Tomcat before starting it again.

  3. To see the two Tomcat classes running, enter java -show.

2.10 Java Out-of-Memory Issue

To avoid Java out-of-memory issues with Virtual Office and iManager, you can increase the memory allocated by editing the sys:\tomcat\4\tomcat4.ncf and increase the -Xmx256m setting up to -Xmx512. Then restart Tomcat.

2.11 Support for Server Hardware with No PS/2 Keyboard Port

In NetWare 6.5 SP6, support for keyboard polling has been added to enable NetWare to run on newer machines that do not have a legacy PS/2 keyboard port. This enables NetWare to be installed and to run before the USB keyboard drivers are loaded.

2.12 Changes to Daylight Saving Time Start and End Dates

NetWare 6.5 SP6 contains changes to the default values for the Start and End dates for Daylight Saving Time for those time zones affected by the change. Effective starting in 2007, Daylight Saving Time starts on the second Sunday in March and ends on the first Sunday in November.

These new settings will be in place for any new server installed using the NetWare 6.5 SP6 overlay CDs. They are applied only if you select a time zone that is adopting the new start and end dates.

Applying SP6 to an existing NetWare 6.5 server does not make any changes to the Daylight Saving Time start and end dates. A separate utility, DSTshift, is available in \tools of the Support Pack and on the Support Web site. The utility is also available on support.novell.com. See the readme.txt file for more information about using the utility.

The DSTshift utility automatically adjusts the start and end dates for Daylight Saving Time on existing NetWare 4.x, 5.x, and 6.x servers. You can also adjust the settings manually at the server console and by editing the autoexec.ncf file.

2.13 Applying the Support Pack to Servers Running eDirectory 8.8

If your server is running NetWare 6.5 Support Pack 5 with eDirectory™ 8.8 SP1 installed, you should apply the edir881ftf_1.exe patch prior to applying the Support Pack to prevent the Support Pack install from hanging.

If you did not apply the patch before installing the Support Pack and the installation hangs, apply the patch and rerun the NetWare Support Pack install.

You can also copy the dhost.nlm file from the /tools/edir88 directory of the Support Pack to the server's sys:\system directory and reboot the server before applying the Support Pack.

2.14 Upgrading to eDirectory 8.8 SP1

If your server is running NetWare 6.5 Support Pack 5 or earlier and you also want to upgrade the server to eDirectory 8.8 SP1, you should first apply NetWare 6.5 Support Pack 6 and then apply eDirectory 8.8 SP1. eDirectory 8.8 SP1 downgrades several security modules in NetWare 6.5 SP6; therefore, you should download and apply the latest Security Services update.

2.15 Remote Post-installing eDirectory 8.8 after Support Pack 6

If post-installing products with eDirectory 8.8, you should deselect Certificate Server and NMAS products so these do not get downgraded. The local post-install warns you about this, but a remote post-install does not.

2.16 BTCPCOM Abend During Nessus Scan

Beginning with NetWare 6.5 Support Pack 6, changes were implemented for Pervasive* to resolve an abend in BTCPCOM during Nessus* scans. For more information, see TID 3174344.

2.17 Unloading iSCSI Causes Server to Stop

Unloading iSCSI while snapshots are active causes the server to stop responding. To avoid this, deactivate snapshots before unloading iSCSI.

2.18 Applying Support Pack to Novell BorderManager 3.8

If you apply NetWare 6.5 Support Pack 6 to a server already running Novell BorderManager® 3.8 Support Pack 5, filtserv.nlm is downgraded. To resolve this, manually copy the filtserv.nlm from the sys\system directory in the Novell BorderManager 3.8 Support Pack 5 to the server's sys:\system directory. The correct filtserv.nlm file is version 1.61.13, dated Thursday, November 24, 2005.

2.19 Using NWDEPLOY

2.19.1 iManager Does Not Run

If you are using nwdeploy.exe to do a remote upgrade, and if Tomcat does not load after rebooting and iManager won't run, the catalina.jar file has become corrupted. To resolve this, copy the catalina.jar file from \products\tomcat4\tomcat4.zip on the overlay ISO path to the server’s \tomcat\4\server\lib directory.

To prevent this in future remote upgrades, unload Tomcat and unload Java prior to doing the upgrade by completing the following:

  1. At the server console, enter: tc4stop.ncf admsrvdn.ncf to

  2. To unload JAVA, cut and paste the following items into an NCF file named javadown.ncf : Console 'unload silvermasterinit',1 Console 'stopx',10 Console 'unload UCS2JAVA', 1 Console 'unload XFSVGA', 1 Console 'unload XFVGA16', 1 Console 'java -shutdownall',10 Console 'java -killall', 5 Console 'unload java ', 1 Console 'java -exit', 1

2.19.2 Post-installing Certificate Server

Doing a remote post-install of Certificate Server using the Deployment Manager may not complete the installation from the Supoort Pack 6 overlay. Since Certificate Server is installed by default in most cases, you should not need to post-install it again.

If Certificate Server needs to be post-installed such as when migrating server to new hardware, you should post-install Certificate server using the local server’s gui.

2.20 iPrint Printers Not Bound

If printer agents come up in a Not Bound state, you need to load netdb.nlm by completing the following.

  1. Unload ndpsm.nlm.

  2. Load netdb.nlm.

  3. load ndpsm.nlm.

2.21 Storage Management Services (SMS) Issues

2.21.1 Unsupported SSL File Types

For SSL private key files, file type Der is not supported.

2.21.2 Space Is Not supported in SSL Filenames

Do not include spaces in filenames for public key certificate, private key, and trusted certificate files.

2.21.3 Chain of Multiple Certification Authorities (CA) Signers Not Supported

Certificates with more than one CA signer in the certificate chain are not supported. Use certificates having a single CA signer.

2.22 Novell Branch Office Issues

The following are issues when applying the Support Pack to Novell Branch Office (NBO).

2.22.1 Boot Volume Files Are Not Backed Up

If the install detects a Branch Office appliance, no files on the C: drive are backed up during the install. This change was made to prevent the appliance from running out of disk space on that drive.

2.22.2 Ongoing Novell Branch Office Issues

Ongoing issues from earlier releases are available in the Novell Nterprise Branch Office 2.0.5 Readme.

2.22.3 Replication

If you continue to receive error -10 and error -30, even after following suggetions in section 2.2 of the NBO 2.0.5 Readme, and you have large Data sets to replicate, try the following:

  1. On Novell Branch Office, set replication timeout=10000.

  2. On the Corporate side, use Novell Remote Manager and increase the timeout for the branch from the default of 3600 to 10000.

  3. Stop processors (on both Corporate and Branch Office) and set auto start processors=off so that on your next reboot, you are running with only one processor.

  4. Have only one NIC enabled on both the Corporate and Branch Office.

Using IDE Drivers

After installing NW65SP6 on a Novel Branch Office server with IDE drives, the server might hang after rebooting. To resolve this, copy the ideata.ham and ideata.ddi files from the Support Pack’s \tools directory to the servers c:\nwserver\drivers directory.

3.0 Support Pack 2 Issues

This section contains issues for Open Enterprise Server (OES) Support Pack 2. Issues from Support Pack 1 and the initial release are listed in the individual product sections.

3.1 Linux Issues

The following issues exist on OES Linux:

3.1.1 Deploying eDirectory 8.8

Open Enterprise Server Support Pack 2 includes updates for eDirectory 8.73. If you want to deploy eDirectory 8.8, see “Using YaST to Install and Configure eDirectory 8.8” in the Novell eDirectory 8.8 Installation Guide and TID 10100450 for known issues.

3.1.2 Patching OES 2 SP2

If updating from OES 1 SP2 FCS, and applying the entire channel, you must refresh the channel one more time to get the latest kernel-update-tool. This is because a prior kernel-update-tools patch is needed to be applied from the channel (patch 11961) before the new one can be applied (patch-12086).

3.1.3 Additional Configuration after Applying Patches

After applying SP2 patches, you need to do additional configuration for several components as outlined in Configuring Services After Applying an OES Support Pack of the OES Linux Installation Guide.

3.1.4 Virtual Office Updates Not Included in SP2

The Virtual Office component and updates are not included in Open Enterprise Server Support Pack 2. Existing Virtual Office installations will continue to run on servers updated to OES SP2. If you are creating a new server and want to install Virtual Office, install it using the Open Enterprise Server SP 1 CDs, then update or patch the server to SP 2.

To obtain the Virtual Office 1.6.1 for Linux update, download vo_linux1_6_1.tar.gz from the support.novell.com.

3.1.5 I/O through NSS Software RAID 5 Devices on SATA Drives Might Cause Extreme Slowness

For NSS on Linux, I/O through an NSS software RAID 5 device on some SATA drives might be so slow that the machine appears to hang. Only certain SATA drives experience this I/O slowdown when used in RAID 5; other SATA drives perform as expected. We are not aware of any problems for NSS software RAID 0 or RAID 1 devices on SATA drives.

We are currently working to address this issue. Meanwhile, we recommend that you conduct a small I/O test prior to implementing NSS software RAID 5 on your SATA drives.

3.1.6 SecretStore Stops Functioning after Patching

If you patch a server running Novell® SecretStore™ to OES SP2, SecretStore stops functioning because the configuration files were overwritten by the patches. To resolve this, you must reconfigure SecretStore using the following commands:

  1. /usr/sbin/ssscfg -d

  2. /secretstore_download_path/ss-uninstall

  3. /secretstore_download_path/ss-install

  4. /usr/sbin/ssscfg -c

3.1.7 iPrint Issues

  • Mac OS (Tiger): Secure printing from workstations using Mac OS X Tiger does not currently work.

  • Certificates after Patching: After patching your server from the initial release to SP2, you might be prompted to trust certificates again.

  • Printers Not Connected after Migration: After migrating from NetWare®to Linux, your printers might appear as not connected. To resolve this, shut down and restart the Print Manager.

  • Losing Role-Based Services: In a mixed Linux and NetWare Tree, Role-Based Services (RBS) are lost when you set up RBS for one platform such as iPrint on Linux and attempt to manage the other platform, such as iPrint on NetWare.

3.1.8 Multi-byte Character Issues

  • NCP Server: Does not identify Japanese ZENKAKU/HANKAKU characters in NCP™ file share services on NSS volumes.

    Figure 3-1 Multi-byte Example

    If you migrate data contained in NetWare NSS volumes to an OES Linux NSS volume, some characters of half width and full width cannot be in the same directory. Only one file is in a directory, and the other file is lost.

    To avoid this, change filenames that have the same conditions as above before migrating from NetWare NSS to OES Linux NSS volumes.

  • Lost Trustees after Salvaging Files and Folders: You should check the file trustees after salvaging files and folders. If the trustees were lost, set the trustee assignments again.

  • iPrint: Uploading a printer driver that contains multi-byte characters might cause the iPrint Driver Store to stop running. To resolve this, remove any comments containing multi-byte characters from the printer driver .inf files.

  • iManager: The Login Script page in iManager does not handle multi-byte characters. For example, you cannot use the following type of command:

    Figure 3-2 Login Command Example

    Instead, you should use ConsoleOne® to create login scripts using multi-byte characters. You can also use the Novell Client32™ to edit the user login script, which is accessed from the red N menu on the client.

3.1.9 Cannot Install exteNd Director

Before installing exteNd v5.2.1, you must disable the Name Services Cache Daemon (nscd) on OES SP2 before the exteNd suite install. The daemon can be disabled in Yast > System > Runlevel Editor. The nscd service should be enabled after the exteNd suite install is completed.

This does not affect updating servers that already have exteNd Director already installed.

3.1.10 Extending Schema for exteNd v5.2.1

To add the schema extension for exteNd v5.2., you need to use a version of iManager from OES SP1 or earlier, ConsoleOne or the command line version of ICE1 schema extension. You can build the ICE command in iManager, and then cut and paste it to the command line in Linux and extend the schema that way.

3.1.11 GroupWise Connection Error

GroupWise® cannot use the updated glibc that is included with OES SP2; if you install it, you receive errors that the POA cannot connect to the MTA via IP.

To resolve this, do not update the glibc package. If you have already installed the new package, you can backrev to the previous version by doing the following:

  1. In YaST2, select Add/Remove Programs.

  2. Select the Filter drop-down menu, then choose Selections.

  3. From the Installed Components list on the right, select glibc, then click Accept.

    This lets you use the original CDs to backrev to the previous package.

Applying any of the current GroupWise 7 SP1 Field Test patches or beta, allows the GroupWise agents to run as root. After the application of the GroupWise patch files, it is no longer necessary to backrev the glibc patch

3.1.12 NSS Does Not Support Clustering for RAID 5 on Linux

NSS software RAID 5 is not supported with clustering on OES Linux. NSS does support software RAID 5 if the disk is not shared in a cluster.

3.2 NetWare Issues

The following issues exist on OES Linux:

3.2.1 Deploying eDirectory 8.8

Open Enterprise Server Support Pack 2 includes updates for eDirectory 8.73. If you want to deploy eDirectory 8.8, see TID 10100450 for known issues.

3.2.2 Empty List of Domain Names

If sys:\etc\resolv.cfg is not accessible, then both inetcfg.nlm and the Configure TCP/IP option in Novell Remote Manager for NetWare do not show any domain names and name servers.

3.2.3 Virtual Office Updates Not Included in SP2

The Virtual Office component and updates are not included in Open Enterprise Server Support Pack 2. Existing Virtual Office installations will continue to run on servers updated to OES SP2. If you are creating a new server and want to install Virtual Office, install it using the Open Enterprise Server SP 1 CDs, then update or patch the server to SP 2.

To obtain the Virtual Office 1.6.1 for NetWare update, download vo_netware1_6_1.exe from support.novell.com.

3.2.4 Available Memory Health Status in Novell Remote Manager for NetWare

The server health item for Available Memory in Novell Remote Manager for NetWare is configured by default with threshold values calculated as a percentage of the total server memory. Starting with OES SP2, adjustments have been made to the server's memory handling that allow for lower values for these thresholds, so the defaults for Suspect and Critical levels have been changed.

These changes to the default threshold values are in place on a new server install with OES SP2 (NW6.5 SP5), but the defaults are not automatically changed on a server that is being upgraded to the latest Support Pack, to avoid overwriting any custom values you have already set for these thresholds.

If you see the Available Memory server health item showing a status of Suspect (yellow) or Critical (red) after applying the Support Pack (that might not occur depending on the server memory and existing settings), adjust the threshold values to the new defaults for Available Memory.

  1. In Novell Remote Manager, click Health Monitor under the Diagnose Server heading.

  2. Click Threshold Configuration > Available Memory > Restore Default Values > OK.

3.2.5 CE1000 Driver Change

The CE1000 LAN Driver has been removed from this support pack and replaced with the E1000 LAN Driver. If you install using the overlay (CD Image) method, the replacement E1000 driver is used automatically.

If you install using the support pack script install (using nwconfig.nlm), the old CE1000 LAN driver on the server is used. To run the new driver, run inetcfg to configure the new driver, or edit the autoexec.ncf file if you load Lan drivers from autoexec.ncf.

3.2.6 Error When Migrating Printers with the Server Consolidation Migration Toolkit

When using the Server Consolidation Migration Toolkit to move printers from one NetWare server to another, you might see the following error message:

Dropped printer agent is invalid. It has either been deleted, been disassociated with PSM, the source PSM no longer exists or the destination PSM no longer exists. Do you want to delete this object from the project database?

Click either Yes or No because the printer agent was already moved to a target PSM. Refreshing the objects shows that the move was completed.

3.2.7 Time Stamp Issue on FTP Server

It is not possible to set a time stamp on a subdirectory or file, from a directory that has white-space characters in its name. To resolve this, specify the absolute path of file or directory in quotes. This can also be done from the parent directory that doesn't have spaces in its name, then you can set the time stamp for the files or directories with the relative path specified in quotes.

3.2.8 iPrint Issues

  • Mac OS (Tiger): Secure printing from workstations using Mac OS X Tiger does not currently work.

  • iPrint Pattern Installs: When installing a new server, if you select the iPrint pattern install, the iPrint plug-in for iManager might not be configured correctly. To resolve this, reinstall the iPrint plug-in.

  • Cannot Move Print Jobs: If you cannot move a print job in iManager, update to the latest iPrint plug-in.

  • Losing Role-Based Services: In a mixed Linux and NetWare Tree, Role-Based Services (RBS) are lost when you set up RBS for one platform such as iPrint on Linux, and attempt to manage the other platform, such as iPrint on NetWare.

3.2.9 Novell Branch Office

Before installing this Support Pack on a Novell Branch Office (NBO) server, delete any previous backups on c:\nwserver\backspx, where x can be 2 to 4. This prevents the server from running out of disk space on the c: drive during the Support Pack installation, which could cause an abend.

4.0 OES for Linux Installation

This section describes issues related to the integrated installation of Novell® Open Enterprise Server SP2 (OES) for Linux and SLES 9 SP3.

For complete instructions on installing OES for Linux, see the OES Linux File and Data Locations.

4.1 Installation Information

You have the option of doing a new installation or upgrading an existing SLES 9, SLES 9 SP1, SLES 9 SP2 server to OES for Linux SP1.

For detailed installation information, see the OES Linux File and Data Locations.

4.2 Linux Issues

This section contains the known installation issues for OES SP2 for Linux release.

4.2.1 Cacerts File Moved to New Location

Beginning with OES SP1, the Tomcat certificate file for cacerts was changed to /var/opt/novell/tomcat4/conf/cacerts. This change might affect services running inside Tomcat that make a connection to an SSL-enabled service and in multiple server configurations or for signed certificates obtained from a third-party.

Before applying the Support Pack, you should back up your the cacerts file in /usr/lib/SunJava2-1.4.2/jre/lib/security as described in TID 10098127.

4.2.2 Download of Latest Release Notes Fails

If installing OES sp2, the internet connection test and downloading of release notes might fail and the YaST online update is populated with the wrong server. To resolve this issue, go to the Yast Online Update screen. Change the Installation Source to "User-Defined Location" and enter http://update.novell.com/YOU as the server. You should now be able to connect to the YaST online update server.

If this fails, check that you have DNS setup on your network. Currently there are no YOU patches available for the install so this step can be skipped.

5.0 OES for NetWare Installation and Upgrade

The NetWare® server platform for Novell® Open Enterprise Server (OES) Support Pack 2 (SP2) is NetWare 6.5 with Support Pack 5 (SP5).

NetWare 6.5 SP5 and OES SP2 on NetWare are the same. Installing OES SP2 on NetWare is the same as installing NetWare 6.5 with Support Pack 5. Applying the NetWare 6.5 SP5 update is the same as upgrading to OES on NetWare; therefore, they both use the same CD set. ISO images of the NetWare 6.5 SP5 Operating System overlay CD and the NetWare 6.5 SP5 Products overlay CD are included with the Open Enterprise Server software, along with an ISO for the SP5 update CD.

For complete instructions on installing and upgrading to OES for NetWare, see the OES for NetWare Installation Guide.

5.1 What's New in This Release

This section lists new and enhanced features in this release of OES SP1 and later.

5.1.1 NetWare Install Program

Novell no longer distinguishes between a NetWare 6.5 Support Pack installation and the OES for NetWare installation. The ability to choose between Open Enterprise Server and NetWare 6.5 SP5 has been removed from the Install program.

If you are upgrading from NetWare 6.5 FCS or later, Novell recommends that you run NWCONFIG and use Product Options to apply the SP5 updates from the update CD. This method upgrades QuickFinder™ to version 4.1 and Virtual Office to version 1.6. It also detects the version of iManager and applies either iManager 2.0.2 or iManager 2.5 updates as required.

If you want to upgrade iManager 2.0.2 to iManager 2.5, do a product install of iManager 2.5 using the NetWare 6.5 SP5 overlay CDs after you have applied the SP5 updates in NWCONFIG.

Before upgrading from NetWare 5.1 or NetWare 6.0 using the overlay CDs, you should back up any configuration files that you have customized. After the upgrade, you can restore the customized files if necessary.

In order to be upgraded to OES NetWare, NetWare 5.1 servers must have SP7 or later applied; NetWare 6.0 servers must have SP5 or later applied.

5.1.2 Migration and Consolidation Tools

The NetWare Migration Wizard and the Novell Server Consolidation Utility have been combined under a single launch interface called the Novell Server Consolidation and Migration Toolkit. The new launch interface asks you what type of consolidation or migration project you want to perform and then launches the appropriate utility automatically: Novell Server Consolidation Utility 4.1 or NetWare Migration Wizard 8.1.

In NetWare Migration Wizard 8.1, the option to perform a full backup of the source server's trustees has been removed. Novell encourages customers to always do a full tape backup of their source server before beginning the migration. If this is done, there is no need to separately back up all the source server's trustees within the Migration Wizard.

NetWare Migration Wizard 8.1 now supports NetWare 4 as a source server, which was previously supported only in Migration Wizard 6.5.

New features in Server Consolidation Utility 4.1 include the ability to run a project as a server-based process. This means the utility does not control or monitor the actual data copying; rather, an agent running on the server processes the project. You also have the ability to migrate iPrint Print Managers and Printer Agents from a NetWare 6.5 SP3 or later environment to an OES Linux environment.

5.2 NetWare Issues

This section contains the known install/upgrade issues for this release of OES for NetWare (NetWare 6.5 SP5).

5.2.1 Installing Multiple Servers

You should install one NetWare server at a time into a tree, waiting for the installation program to complete before installing an additional server into the same tree.

5.2.2 Avoid Some eDirectory Operations during OES Installation

While installing OES, you should not initiate heavy eDirectory operations such as partitioning, mass user creation, and mass Linux User Management enabling due to slow performance. You should perform these operations after OES is installed.

5.2.3 No CD Switch When Installing NetWare 6.5 SP5/OES on VMWare

When installing or upgrading to NetWare 6.5 SP5/OES on VMWare, the switch between the OS and Products CDs might not mount the Products CD. To fix this, go into the VMWare devices, disconnect the CD-ROM IDE channel, and then reconnect. The NetWare Install program should now detect and mount the Products CD.

5.2.4 Overlay Install Issue with ULTRA Driver

If the ULTRA driver has been selected during the NetWare installation but refuses to load, load the IDEATA driver instead:

  1. Return to the installation program's Drivers screen.

  2. Select and delete the ULTRA driver.

  3. Press Insert to select the IDEATA driver to replace it.

5.2.5 Installing the Support Pack Causes ZENworks Imaging to Stop Functioning

After installing the Support Pack, ZENworks Imaging might stop functioning. To resolve this follow the instructions in TID 10098801 on the Support Web site.

5.2.6 ZENworks Server Management Does Not Work on Servers after Upgrade

When a NetWare 6.5 server is upgraded to OES NetWare, a newer JVM* is installed that is incompatible with the zencommon.jar file in ZENworks® 6.5, so the Server Policies and Server Software Package functionalities no longer work.

To resolve this, upgrade Server Management to ZENworks 6.5 Support Pack 1 after upgrading NetWare to obtain an updated zencommon.jar file.

5.2.7 NetWare Support Pack Install Overwrites ZENworks Middle Tier Components

The OES NetWare installation overwrites ZENworks middle tier (XTier) components and upgrades XTier from version 2.0x to 3.01. However, ZENworks Desktop Management (ZDM) 6.5 and 7.0 require xTier version 2.0x for proper functionality.

ZDM 6.5 and 7.0 users must reinstall XTier after upgrading from a previous version of NetWare to OES NetWare SP1 (NetWare 6.5 SP5). Note that this impacts NetStorage functionality.

5.2.8 Configuring Virtual Device for NSS When Installing OES NetWare on VMWare

When installing OES NetWare Support Pack on a VMWare ESX Server, keep the following guidelines in mind as you configure the virtual device for your Novell Storage Services™ (NSS) volumes.

Whenever possible, you should create the virtual device in persistent mode (not undoable). In this mode, all writes are committed to the device immediately without creating a redo file.

If you create the virtual device in undoable mode, be sure to leave enough free space for the redo file to grow to the size of the partition created for the virtual server. To avoid possible problems, the virtual device should be set at twice the size of the NSS partition.

If you create the virtual device in undoable mode and don't have enough free space for the redo file, you might experience issues such as the NSS pool being deactivated or the NSS partition being deleted.

6.0 Apache Web Server/Tomcat Servlet Container

This release includes the Apache Web Server and the Jakarta-Tomcat Servlet Container. These Web service components are available on both the SUSE® LINUX Enterprise Server 9 (SLES9) and NetWare® 6.5 platforms.

6.1 Linux Issues

6.1.1 Apache Restart Problem Might Cause a Service to Hang

If a service uses Apache, the service might hang if any module using the Apache instance does not exit immediately in response to the Apache Restart command. To avoid this problem, use the Apache Reload command instead of Restart or Start and Stop.

6.1.2 Cacerts File Moved to New Location

Beginning with OES SP1, the Tomcat certificate file for cacerts was changed to /var/opt/novell/tomcat4/conf/cacerts. This change might affect services running inside Tomcat that make a connection to an SSL-enabled service and in multiple server configurations or for signed certificates obtained from a third-party.

To resolve any of these issues, you must reimport your certificates as described in TID 10098127.

6.2 NetWare Issues

6.2.1 Apache Restart Problem Might Cause a Service to Hang

If a service uses Apache, the service might hang if any module using the Apache instance does not exit immediately in response to the Apache Restart command. To avoid this problem, use the Apache Reload command instead of Restart or Start and Stop.

6.2.2 Using the Internal HTTP stack of Tomcat

By default, the internal HTTP stack of Tomcat is disabled on NetWare. If you want to use the Tomcat secure internal HTTP stack, additional configuration is required because the default NetWare SSL certificates stored in Tomcat’s keystore are not compatible with Tomcat’s secure HTTP stack.

To use the internal HTTP stack:

  1. Uncomment out the secure and nonsecure connectors in Tomcat’s server.xml file.

  2. (Optional) Change the ports in these connectors.

    For example, if you are going to have your webapp served by Tomcat only with no Apache running at all, you probably want to change the nonsecure port to 80 and the secure port to 443. (Defaults are 8080 and 8443, respectively). Also, set the correct redirect port on the nonsecure connector to match the port set on the secure connector.

  3. Fix the certificate problem by doing one of the following:

    • Create a new self-signed certificate in sys:/adminsrv/conf/.keystore.

    • Import a certificate from a trusted Certificate Authority (GeoTrust, Thawte, Verisign, etc.) into sys:/adminsrv/conf/.keystore.

Creating a new self-signed certificate

  1. Create a new NCF file containing the following text and replacing appropriate items in ‑dname

    keytool -keystore sys:/adminsrv/conf/.keystore -storepass apache -keypass apache -genkey -alias tomcat 
    
    -keyalg RSA -validity 9999 -dname "CN=ip_address,OU=organizationl_unit, O=organization, L=city, S=state, C=countryCode" -J-ns
    
  2. At the console, execute the newly created NCF file.

Importing a certificate purchased from a Certificate Authority

To import the certificate, run the following command at the console:

keytool -import -alias tomcat -file certificatename.cer -keystore sys:/adminsrv/conf/.keystore

6.2.3 Remote NetWare Upgrade Does Not Configure Apache2 Admin Server Properly

If, during a remote upgrade of NetWare, you accept the defaults for the LDAP server (specifically, Require TLS for Simple Binds), the Apache2 Admin Server will not get configured properly.

Any of the following resolves this issue:

  • Deselect the Require TLS for Simple Binds check box during installation.

  • Give administrative rights to additional users by adding their User objects to the apchadmn-Administrators group.

  • Run a local post-install of the Apache2 Admin Server from the NetWare GUI console to fix the configuration issues automatically.

6.2.4 Preventing Potentially Large mod_jk Log File

Extremely high traffic volumes on the Tomcat Servlet Container can cause the mod_jk log file to grow large enough to consume the hard drive space on your server's sys: volume.

To prevent this potential problem, disable the log file:

  1. Open the sys:\apache2\conf\httpd.conf file and locate the following lines:

    JkLogFile "logs/mod_jk.log"
    
    JkLogLevel error
    
  2. Add a pound sign (#) to the beginning of each of these lines to comment them out.

  3. Restart the Apache Web server by entering ap2webrs at the NetWare console.

  4. (Optional) Delete the sys:\apache2\logs\mod_jk.log file, especially if it is considerably large in size to free disk space.

6.2.5 Broken Links in the Tomcat Web Application Manager

In the Tomcat Web application manager utility (http://domain_name/tomcat/htmlmanager/html/), some hypertext links to various Web applications might not work. This is because while the manager utility can identify the names of each installed application, it has no method for discovering the exact paths (including port numbers) to all of the applications on your server. In addition, Apache requires a trailing forward slash (/) at the end of its URL, which the manager utility does not append by default.

In most cases, this issue can be resolved by adding a forward slash (/) at the end of the URL. For example, if you clicked the /tomcat/manager link, the referenced URL might be

https://airport.newyork.digitalairlines.com/tomcat/manager

Because this URL is missing a required trailing forward slash, the browser returns an Object Not Found error message. You could then add a forward slash to the end of the URL to access the application:

https://airport.newyork.digitalairlines.com/tomcat/manager/

If the trailing slash does not fix the issue, you can access the application some other way, such as through the NetWare Welcome Web page or through Virtual Office if you have installed it.

6.2.6 Server Certificate Issues

Tomcat sometimes fails to start if there are problems with the server certificate.

If the server certificate has changed since the time of installation, you might need to export the SSL CertificateIP Trusted Root Object to sys:/public/RootCert.der using ConsoleOne® and then execute the following command at the system console:

keytool -import -v -noprompt -trustcacerts -file sys:/public/RootCert.der -keystore sys:/adminsrv/conf/.keystore -storepass changeit

6.2.7 Tomcat 5 Not Supported

Although Tomcat 5 can be installed, it has had limited testing and is unsupported in this release.

7.0 DNS/DHCP

This chapter provides information about DNS/DHCP issues in Novell® Open Enterprise Server (OES).

7.1 NetWare Issues

  • Occasionally, a few error messages containing references to the source code might be displayed on the NAMED screen. In most cases, these error messages can be ignored. Please report occurrences of this to Novell Technical Support.

  • Upgrading a server to OES using GUI methods (using NWDEPLOY and server GUI) removes the NAMED command from autoexec.ncf. In such a situation, the administrator has to manually add the required entries in autoexec.ncf.

8.0 eGuide

This section describes issues with eGuide in this release. For Novell® eGuide issues, see the Novell eGuide Readme.

8.1 eGuide Authentication Fails

The eGuide Service does not authenticate against a remote server over SSL. The Virtual Office home page displays the error message Error: Authentication failed: improper configuration. Please contact your administrator. Also, the Advanced Search and Link buttons ask for credentials.

To correct this error, import the correct Trusted Root Certificate into the JVM on the server that Virtual Office uses. For detailed instructions on importing the certificate, see Step Six: Import the Trusted Root Certificate in the Novell eGuide 2.1.2 Administration Guide

9.0 iPrint

This section describes issues with iPrint.

9.1 Linux Client Issues

9.1.1 Issue with Firefox 1.0.4

If you are using Firefox* 1.0.4, and set the Home Page to your own preference, JavaScript-enabled Web pages, such as iPrint's Printer List page, might not work properly. You should upgrade to Firefox 1.0.6 or later.

9.1.2 Deploying the Latest iPrint Client

After applying the Support Pack, you should deploy the iPrint Client that is included with the Support Pack. For more information about deploying the iPrint Client, see Windows: Distributing the iPrint Client in the iPrint Administration Guide..

9.2 NetWare Issues

9.2.1 After Post-Install ippsrvr.nlm Not Always Loading

If after a post-install of iPrint you cannot perform iPrint functions, ippsrvr.nlm might not be loaded. Either manually load iPrint at the server or reboot the server.

9.2.2 Linux Drivers Not Supported on NetWare 6.0 and NetWare 5.1

You cannot manage Linux drivers on a NetWare 5.1 or NetWare 6.0 server from iManager running on a NetWare 6.5 SP4 or later server. Although the Linux Driver tab appears, clicking the tab results in the following error:

Exception reading resource print drivers configuration
NDPS Library Error Category: 1060004h
Other Error: FFFFFC5Bh

9.2.3 Deploying the Latest iPrint Client

After applying the Support Pack, you should deploy the iPrint Client that is included with the Support Pack. For more information about deploying the iPrint Client, see Windows: Distributing the iPrint Client in the iPrint Administration Guide..

9.3 Macintosh Client Issues

When using the Safari Web browser to install a secure printer from a custom map or the iPrint Printer List Web page, the browser closes after clicking the desired printer and you are prompted for your username and password. However, the desired printer is installed and functions properly. If you choose to save your username and password on the workstation, the browser won't close.

10.0 iSCSI for NetWare

This section contains information and issues for iSCSI for NetWare. For additional iSCSI information, see the iSCSI online documentation.

10.1 NetWare Issues

  • After executing the LIST DEVICES command at the server console, there might be a delay before the device list is displayed.

  • Occasional slow performance or dropped iSCSI connection problems might occur with certain router, switch, and hub configurations.

    These network configurations might require that SACK (Selective ACK) be turned off for the TCP/IP stack running on the initiator. You can do this at the NetWare server console by entering

    set tcp sack option=off

  • Do not run the ioff.ncf command on the iSCSI target server until the iSCSI target devices have deactivated. iSCSI target devices are not deactivated until after the iSCSI initiator connection to the iSCSI target has been terminated. There is a timeout delay of 2.5 minutes after the connection to the iSCSI targets is terminated before iSCSI target devices are deactivated at the server. If you try to unload and reload the Initiator modules before this timeout, the server might abend.

11.0 MySQL for NetWare

This section describes the features and issues of MySQL* for NetWare®.

11.1 NetWare Issues

  • When using the pipe ( | ) functionality of Bash with MySQL NLM™, always provide the password at command line, otherwise the server abends.

    For example, instead of the following:

    mysqldump -u root -p database_name | mysql -h remote_host -u root -p remote_database_name
    

    Use this

    mysqldump -u root -ppassword database_name | mysql -h remote_host -u root -premote_password  remote_database_name
    
  • The -a option used to close the NLM screen is no longer supported. The --autoclose option can be instead used to automatically close the screen.

    mysqladmin -u root -ppassword shutdown --autoclose
    

12.0 Novell Archive and Version Services

This section contains the issues for Novell® Archive and Version Services.

12.1 NetWare Issues

12.1.1 One Source Volume Can Have Only One Job

For any source volume, you can define only one versioning job. If you attempt to define multiple jobs for a volume on the same or different server, Archive and Version Services does not run as designed and data integrity in the archive database is compromised.

  • The archive server can be the same or different server as the source server.

  • A single archive server can archive many volumes with only one job defined per volume.

  • A given volume cannot have multiple jobs defined for it, even if the jobs run on different archive servers.

12.1.2 Missing Parameter in ArkSQL.cnf after Upgrade from NetWare 6.5 SP1 Might Cause Data Corruption

The Transaction Isolation parameter in the sys:\arkManager\arkSQL.cnf file is missing or is set to the wrong value after you upgrade from NetWare 6.5 SP1 to any later versions of NetWare. This does not happen if you are upgrading from NetWare 6.5 or NetWare 6.5 SP2 or later.

To prevent possible data corruption, set the parameter to Read_Committed before restarting ArkManager after the upgrade:

  1. Stop ArkManager 2.0 by entering

    arkstop

  2. Upgrade the server to OES NetWare.

  3. Verify that the server is operating as expected, but do not start ArkManager.

  4. Compare and modify values of non-system-specific information in sys:\arkManager\arkSQL.cnf with the ones defined in sys:\arkManager\arkSQL_sample.cnf.

    Most importantly, add the following variable setting to the end of the file:

    set-variable = transaction_isolation=READ_COMMITTED

  5. Start ArkManager 2.0 by entering

    arkstart

If you are configuring a new archive server after the upgrade, this setting is part of the updated sample arkSQL.cnf file, sys:\arkManager\arkSQL_sample.cnf. Use the updated sample file as a guide when setting up additional archive servers.

13.0 NetWare FTP Server

This section contains information about issues with NetWare® FTP Server.

13.1 NetWare Issues

13.1.1 Limitations with FTP iManager Plug-Ins

The iManager plug-in for FTP has the following limitations:

  • You can monitor only a server running OES NetWare or NetWare 6.5 Support Pack 3 or later.

  • The Monitor Active FTP session link on the FTP Server Administration page does not work in a clustering scenario.

  • When you click to load or unload an FTP instance, it does not change the sequence of displayed instances in the list. However, clicking Refresh or adding a new instance might change the sequence of displayed instances.

    To ensure successful loading or unloading of an FTP instance, click Start or Stop for an instance only after it completes the operation, and then click Load or Unload for another instance.

14.0 Novell Certificate Server, NICI, and NMAS

This section contains the security services issues in this release. For additional information about using Novell Certificate Server™, NICI, and NMAS™, see the Security Services Readme.

14.1 NetWare Issues

14.1.1 Updating Login Methods

Simple password methods are not automatically updated when you install the Support Pack. To update the simple password methods, see Updating Login and Post-Login Methods in the Novell Modular Authentication Services (NMAS) 2.3 Administration Guide.

15.0 Novell Clients

16.0 Novell Cluster Services

This section explains the Novell® Cluster Services™ Issues.

16.1 Linux Issues

16.1.1 Reboot Required to Restart Cluster Software

If you have Cluster Services running on a node and you want to restart the cluster software, you must reboot the node. Also, if a cluster server cannot find the cluster partition (SBD partition), you must reboot the node after resolving the problem that caused the SBD partition to be nonaccessible.

16.1.2 SBD Partition Not Used If Created after Cluster Installation

If you create the SBD partition (cluster partition) after installing Novell Cluster Services, that partition will not be used by cluster nodes. If cluster nodes don't use the SBD partition, they continue to function as cluster servers with no SAN.

To work around this problem, you must set the shared disk flag in eDirectory™.

  1. Start iManager and click View Objects on the button bar at the top of the screen.

  2. Browse to and click the cluster object.

  3. Select Modify Object.

  4. Select the NCS Shared Disk Flag, then click Edit.

  5. Check the NCS: Shared Disk Flag checkbox.

  6. Click OK >Apply to save your changes.

16.1.3 Cluster-Enabled Pool Objects Might Not Create Correctly

Sometimes after cluster enabling an NSS pool, the process appears to function correctly but the pool is not actually cluster enabled. The cluster-enabled pool and virtual server eDirectory objects are not created and the pool is left as a non-cluster enabled pool. To fix this problem, perform the process again to cluster enable the pool and ensure the eDirectory objects are created and the pool is cluster-enabled. This problem occurs as a result of eDirectory synchronization between replicas used by NSS and Novell Cluster Services.

16.1.4 Unknown Error Messages in iManager

Error messages 528 and 529 are not recognizable by iManager and display as unknown errors. See Novell Cluster Services Error Codes for information on these errors.

16.1.5 Problems Authenticating to Remote Servers during Cluster Configuration

If, during the OES cluster installation and configuration, you select Remote System on the NCS LDAP Configuration page and you have LDAP configured to point to a NetWare 6.0 or earlier NetWare server, the cluster configuration fails. To work around this problem, you must edit the etc/openldap/ldap.conf file and either disable certificates (TLS_REQCERT <level> line) or change the file that contains the certificates (TLS_CACERT <filename> line).

See the ldap.conf man page for more information.

16.1.6 Locale Problems in Cluster-Enabled Pool Contexts

You cannot cluster enable an existing NSS pool if the fully distinguished name for the pool has a locale (country, etc.) in the eDirectory context for the Pool object. This problem does not occur if you cluster enable a pool at the same time it is created.

16.1.7 Cluster Configuration Changes Using iManager Require a Running Cluster

You must have Novell Cluster Services software loaded and running on at least one cluster node in order to use iManager to make cluster configuration changes. If you want to make cluster configuration changes with the cluster down (all cluster nodes either down or without cluster software loaded) you can use ConsoleOne®. Some configuration changes can also be made with the cluster down using cluster console commands.

16.1.8 NSS RAID 0 and NSS RAID 5 Not Supported in Linux Clusters or Mixed NetWare and Linux Clusters

If you have an OES Linux cluster or a mixed OES NetWare and Linux cluster and have configured NSS RAID 0 or NSS RAID 5, do not attempt to fail over or migrate an NSS pool from a NetWare cluster server to a Linux cluster server or from a Linux cluster server to another Linux cluster server. If you do this, it is possible that the NSS partition where the pool is located could be lost, which would result in data loss or corruption.

16.1.9 Do Not Create an NSS Pool and RAID Device With the Same Name

If you create an NSS pool on an NSS RAID device with the same name, you cannot delete that NSS pool or the RAID device. To reclaim the disk space used by the NSS pool, you must reinitialize all devices used by the RAID device, which would result in the loss of all data on those devices.

16.1.10 NetWare Snapshot Functionality Not Supported on Linux

The snapshot functionality that exists on NetWare is not yet supported in Linux. Therefore, all snapshots must be deleted on NSS pools on NetWare that are to be migrated or failed over to Linux. This is very important for mixed clusters that have both NetWare and Linux nodes in them. Moving a pool with a snapshot on it from a NetWare server to a Linux server and back to a NetWare server will corrupt the snapshot data. However, the pool data will still remain intact.

16.2 NetWare Issues

16.2.1 Cluster Node Fails to Auto-Start after Installation

If Cluster Services (clstrlib.nlm) does not automatically start on a node immediately after installation, start it manually by entering ldncs at the server console.

16.2.2 Create NSS Pools and Volumes on RAID Devices from the Same Server Node in Clustered Solutions

In a clustered solution using Novell Cluster Services, if you use software RAID 0 or RAID 5 devices on shared disks, you must create a pool and volume on that RAID device from the same server node before that pool can be migrated.

16.2.3 Pool Level SnapShot of Cluster Shared Pool Causes Pool Deactivation

A pool might deactivate when you attempt to take a snapshots, if there are no blocks available for the snapshot. In this case, the server’s logger screen displays the message Error finding a free snapshot block, and the pool is deactivated.

16.2.4 Changing Cluster Pool IP Address With CIFS Enabled Returns an Error

If you have a cluster-enabled NSS pool that has the CIFS protocol enabled and you attempt to change the IP address assigned to the cluster-enabled pool, the following error will be displayed:

CfgPropertiesCannot turn on CIFS unless there is a CIFS server name.

To resolve this error, change the IP address of the pool that CIFS deselected. This removes CIFS-specific lines from the resource load and unload scripts. After changing the IP address, select CIFS and then apply the changes. This adds the appropriate CIFS lines back to the resource load and unload scripts.

See Cluster Enabling Pools and Volumes in the OES Novell Cluster Services 1.8 Administration Guide for more information on cluster-enabled pools.

16.2.5 NSS Volumes Must Be Created, Moved, or Split on the Cluster Server Where the Volume's Shared Pool Was Created

If you attempt to create a volume on an NSS pool, and that pool resides on a cluster server other than the server where the pool was originally created, the eDirectory objects for that volume might not be created. However, the volume is created.

Also, you cannot do a volume move or split when the volume’s pool resides on a cluster server other than the server where the pool was originally created.

To work around these problems, always create volumes or do volume moves or splits on the cluster server where the pool was created.

16.2.6 Problems Cluster Enabling an Existing NSS Pool

If you have an existing NSS pool on shared storage and then install Novell Cluster Services, you might be unable to cluster enable that NSS pool. An error is displayed in iManager, ConsoleOne®, or Novell Remote Manager when you attempt to cluster enable the pool.

To resolve this delete all eDirectory objects associated with the NSS pool and the volumes on that pool. After deleting the Pool and Volume objects, re-create them and then cluster enable the pool.

Using NSSMU, select the pool or volume and then use the Update NDS option to re-create the necessary Pool or Volume objects.

17.0 Novell eDirectory 8.7.3

This section contains the Novell® eDirectory™ 8.7.3 SP7 issues in this release. For additional eDirectory issues, see the Readme files located with the eDirectory 8.7.3 online documentation.

17.1 Linux Issues

17.1.1 Installing OES into a NetWare 6.5 SP2 Tree

Installing OES for Linux into a NetWare® 6.5 SP2 tree causes the NetWare server to abend (due to an issue in SP2 that has been fixed in SP3).

Before installing an OES for Linux server into a NetWare 6.5 SP2 tree, upgrade any NetWare 6.5, NetWare 6.5 SP1, and NetWare 6.5 SP2 LDAP servers that will be pointed to by the OES install to NetWare 6.5 SP4 or OES NetWare or later servers.

17.1.2 Avoid Some eDirectory Operations during OES Installation

While installing OES, you should not initiate heavy eDirectory operations such as partitioning, mass user creation, and mass LUM enabling due to slow performance. You should perform these operations after OES is installed.

17.2 NetWare Issues

17.2.1 Avoid Some eDirectory Operations during OES Installation

While installing OES, you should not initiate heavy eDirectory operations such as partitioning, mass user creation, and mass LUM enabling due to slow performance. You should perform these operations after OES is installed.

18.0 Novell iFolder 2.1.7

This chapter contains information on known issues about Novell® iFolder® 2.1.7 in this release.

For additional Novell iFolder 2.1.x issues, see the Readme located with the Novell iFolder 2.1 online documentation

18.1 Linux Issues

18.1.1 iFolder Server Issues

Installation Issues

  • If you do a post-install on an iFolder 2.x server using the rpm -ivh command or through the path YaST2 Modules > Software > Install and Remove Software, you need to run the yast2 ifolder2 command to configure the iFolder 2.x server.

    If you do a post-install using YaST2 Modules > Network Services > iFolder 2.x, the configuration is completed as part of the install and you do not need to execute the yast2 ifolder2 command.

  • After attaching a Linux server to the existing tree, restart the iFolder server by running the following command at the terminal before logging to the Admin page of iFolder Linux server:

    /etc/init.d/novell-ifolder restart

Coexistent Mode Configuration

  • If you have multiple NICs with multiple primary IP addresses in the Coexistent mode of installation, then the first bound interface (eth0) is selected for binding the iFolder-specific IP address entered through yast2. For example: eth0:ifdr

  • If iFolder is installed in Coexistent mode, NetStorage can run on the same machine.

Standalone Configuration

If iFolder is installed in the standalone mode, NetStorage cannot run on the same machine and the Login link on the main iFolder page does not work because NetStorage is not installed on the local machine. However, you can install NetStorage on a separate machine and configure it to point to the standalone iFolder server. Then the user can use https://netstorage_server_ip_address/NetStorage to access NetStorage.

NetStorage Configuration

NetStorage needs to be configured with the iFolder 2.x server IP address; otherwise, NetStorage cannot be used to access iFolder.

Private Host DNS Not Supported

When adding or modifying an iFolder Server object using iFolder Management Console > Global Settings > iFolder Servers, do not specify a value for the Private Host DNS or IP for a Linux iFolder Server object. This feature is not supported in iFolder 2.1.7 on OES Linux in the Coexistence mode.

18.1.2 iFolder Client Issues

FAT32 Support

The FAT32 partition not fully supported in the current release of iFolder 2.1.7 for Linux.

Client Installation

  • If you face any issue in bringing up the iFolder client, then do one of the following:

    • Run export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/novell/ifolder/lib and then run novell-ifolder-client

    • Add /opt/novell/ifolder/lib to /etc/ld.so.conf

  • In SuSE® 9.2, run the rpm -ivh novell-ifolder-client-2.1.7-x.rpm --nodeps command. This installs iFolder client without checking for dependencies. Run ldconfig /opt/novell/ifolder/lib command and then run the iFolder client.

Using the Russian iFolder Client

The iFolder Linux client downloaded from a Russian Linux or NetWare server is not localized to the Russian language. Instead, it retains the default language (English).

Updating Novell Linux Desktop Clients

If Novell Linux Desktop users attempt to update their iFolder client from an OES server, the update will probably fail because of a difference in the rpm architecture. (see table below).

Client

RPM Information

Novell Linux Desktop

2.1.4-2.12.i586.rpm

Novell Linux Desktop SP1

2.1.5-0.2.i586.rpm

Client included with OES

2.1.5-6.4.i386.rpm

Client included with OES SP1

2.1.6-1.8.i586.rpm

Client included with OES SP2

2.1.7-1.8.i586.rpm

Although the Red Carpet client will not show updates for the iFolder Client as available, users can run the following command to install the updated OES Linux client on their workstations:

rug in novell-ifolder-client

18.1.3 NetWare Issues

iFolder Server Issues

Users Must Log Out before Upgrading iFolder

All the iFolder users must be logged out of the iFolder server before it is upgraded. The users can log in again after the upgrade is complete.

iFolder Client Issues

Updating Novell Linux Desktop Clients

If Novell Linux Desktop users attempt to update their iFolder client from an OES server, the update usually fails because of a difference in the RPM architecture, as outlined in the following table:

Client

RPM Information

Novell Linux Desktop

2.1.4-2.12.i586.rpm

Novell Linux Desktop SP1

2.1.5-0.2.i586.rpm

Client included with OES

2.1.5-6.4.i386.rpm

Client included with OES SP1

2.1.6-1.8.i586.rpm

Client included with OES SP2

2.1.7-1.8.i586.rpm

Even though the Red Carpet® client does not show updates for the iFolder client as available, users can run the following to install the updated OES Linux client on their workstations:

rug in novell-ifolder-client

NetStorage

iFolder Web client running over NetStorage supports only UTF-8 encoding.If you also want to use NetStorage for synchronizing data, make sure the Linux client as well as the NetStorage server is running on UTF-8 encoding.

19.0 Novell iFolder 3.1

For Novell iFolder 3.1 server and client issues, see the Novell iFolder 3.1 Readme located with the Novell iFolder 3.1 online documentation.

20.0 Novell iManager

For all Novell® iManager 2.5 issues, see the Readme included with the Novell iManager 2.5 documentation. iManager 2.5 is installed if you install a new NetWare® OES server.

See the iManager 2.0.2 Readme included with the Novell iManager online documentation. Installing NetWare 6.5 Support Pack 5 on an existing NetWare 6.5 server updates the installed version of iManager. iManager 2.0.2 is not upgraded to iManager 2.5.

20.1 Plug-in Module Installation

If you have downloaded new plug-ins, or, when you updated to OES SP1, not all of your plug-ins were installed, see the iManager 2.5 Install Guide.

20.2 Updating Plug-in Modules Returns an Error Message Instead of a Success Message on Linux

When upgrading to SP1 on Linux, in Available Novell Plug-in Modules there are several modules to update due to the patch to SP1, including the iManager Maintenance update.

If you choose to update all of the plug-ins at once, an error message appears at the end of the install:

Can’t find bundle for base name DevResources, locale en.

The plug-ins have actually installed successfully. Just log out of iManager and restart Tomcat to complete the installation of the updated plug-in modules.

20.3 After Upgrading to eDirectory 8.8, iManager Cannot Log In to Other Trees

After upgrading to eDirectory 8.8 on NetWare, you cannot log in to a remote tree through iManager. To resolve this, add the following to the beginning of c:\nwserver\startup.ncf file, then restart the serve:

env NDSD_TRY_NMASLOGIN_FIRST=true

21.0 Novell Native File Access Protocols on NetWare

This section contains information about issues for Novell® Native File Access Protocols on NetWare® in this release.

21.1 NetWare Issues

21.1.1 Disabling the Software

To disable CIFS and AFP, see Enabling and Disabling CIFS in the OES Native File Access Protocols Guide.

To disable NFS, complete the following steps on each server running NFS:

  1. Run nfsstop at the server console.

  2. Remark or remove the NFSSTART line from the autoexec.ncf file.

21.1.2 Macintosh/AFP Issues

Case-Insensitive Long Filenames Supported

Please refer to the OES Native File Access Protocols Guide for details on how to enable this feature as well as convert existing long Mac names to case-insensitive names.

21.1.3 UNIX/NFS Issues

  • In this release, NFS Administration through iManager does not work in the Spanish language.

  • If you are using NFS exported paths, be sure to unmount and remount those paths on the NFS clients when upgrading from NetWare 6.5 (FCS, SP1, and SP22) to OES NetWare.

22.0 Novell NetStorage

This section contains information about Novell® NetStorage issues in this release.

22.1 Linux Issues

22.1.1 Logging In As a Different User

There are three different scenarios to be aware of if, after logging in to Novell NetStorage, you intend to log in again as a different user.

  • If you are using WebDAV, you must close WebDAV and then delete Internet cookies and log out, or you cannot log in again as a different user.

  • If you are using a browser with Internet cookies enabled, you must logout.

  • If you are using a browser with Internet cookies disabled, you must close all browser windows.

22.1.2 NetStorage and iManager Are Required to Be on the Same Server

In order to use iManager to manage NetStorage, iManager must be installed on the same server as NetStorage.

If you do not have iManager installed on the same server as NetStorage, you can do either of the following:

  • Install iManager on each server where NetStorage is installed and point your browser to the IP address or URL of that server when you want to make NetStorage changes.

  • Access NetStorage directly from your browser and do not use iManager.

    Not all NetStorage configuration options can be performed using this method. For example, you cannot create Storage Location objects using this method. The URL for this method is http://ip address or DNS name of server/oneNet/nsadmin.

22.1.3 Using the File Access Link in iManager to Access NetStorage Configuration

If you use the link in iManager to access NetStorage, multiple logins might be required before you gain access if you have NetStorage set to use cookieless authentication.

22.1.4 NSS File System Administration Is Limited to Administrator Unless Using SSH

If you are using the default NCP™ file access method for NetStorage (The NCP Services component of OES is running on your Linux server), users other than Admin cannot administer and manage the following NSS file system functions using NetStorage:

  • Change file attributes

  • Change file rights

  • Change trustee assignments

  • Purge and salvage files

  • Change quota restrictions

  • Any other properties on the NetStorage file or directory properties page

This limitation does not apply if using the SSH file access method.

22.1.5 NetStorage Configuration Changes Require Xtier Restart

If you make changes to the NetStorage configuration, you must restart Xtier for the changes to take effect. To restart Xtier, run the following commands at the Linux server console:

/etc/init.d/novell-xsrvd restart

This does not include creating, removing, or changing storage locations.

22.1.6 Invalid NetStorage Authentication Domains

If you change the default NetStorage Authentication Domain to an invalid domain, either during the OES installation (NetStorage installation) or afterward with iManager, users might get a blank screen or Service Not Available error when trying to access NetStorage. Also, you will not be able to change the Authentication Domains setting to a valid domain using iManager.

If this happens, you can change the Authentication Domains value using the /opt/novell/xtier/bin /xsrvcfg command at the Linux server console:

LD_LIBRARY_PATH=/opt/novell/xtier/lib /opt/novell/xtier/bin/xsrvcfg -d authentication_domain -c authentication_context

Replace authentication_domain with a valid authentication domain. Replace authentication_context with a valid authentication context. See Authentication Domains in the NetStorage Administration Guide for Linux for more information on authentication domains and authentication contexts.

22.1.7 iManager NetStorage Plug-in Options

The iManager options to manage NetStorage appear in iManager even if NetStorage is not installed. The NetStorage iManager plug-in is installed even if NetStorage is not. If NetStorage is not installed, the NetStorage iManager options are not functional. This is also applies if NetStorage and iManager are installed on different servers. See Section 22.1.2, NetStorage and iManager Are Required to Be on the Same Server.

22.1.8 Using the Cookieless Option

If you change the NetStorage Cookieless option to 1 (enabled), users accessing NetStorage through Virtual Office are prompted to log in to both Virtual Office and NetStorage to gain access to NetStorage.

22.1.9 Accessing NetStorage through Virtual Office

When accessing NetStorage through Virtual Office from a NetIdentity equipped workstation, users are prompted to log in to Virtual Office, as expected. Additionally, users see a NetIdentity-style login prompt for NetStorage authentication. To gain access to NetStorage users must log in to both Virtual Office and NetStorage.

22.2 NetWare Issues

22.2.1 Logging In As a Different User

There are three different scenarios to be aware of if, after logging in to Novell NetStorage, you intend to log in again as a different user.

  • If you are using WebDAV, you must close WebDAV and then delete Internet cookies and log out, or you will not be able to log in again as a different user.

  • If you are using a browser with internet cookies enabled, you must logout.

  • If you are using a browser with internet cookies disabled, you must close all browser windows.

22.2.2 NetStorage and iManager Are Required to Be on Same Server

In order to use iManager to manage NetStorage, iManager must be installed on the same server as NetStorage.

If you do not have iManager installed on the same server as NetStorage, you can do either of the following:

  • Install iManager on each server where NetStorage is installed and point your browser to the IP address or URL of that server when you want to make NetStorage changes.

  • Access NetStorage directly from your browser and do not use iManager.

    Not all NetStorage configuration options can be performed using this method. For example, you cannot create Storage Location objects using this method. The URL for this method is http://ip address or DNS name of server/oneNet/nsadmin.

22.2.3 Using the File Access Link in iManager to Access NetStorage Configuration

If you use the link in iManager to access NetStorage, multiple logins might be required before you gain access if you have NetStorage set to use cookieless authentication.

22.2.4 Using the Cookieless Option

If change the NetStorage Cookieless option to 1 (enabled), users accessing NetStorage through Virtual Office are prompted to log in to both Virtual Office and NetStorage to gain access to NetStorage.

22.2.5 NetStorage Configuration Changes Require Xtier Restart

If you make changes to the NetStorage configuration, you must restart Xtier for the changes to take effect. To restart Xtier, restart your NetStorage server.

This does not include creating, removing, or changing storage locations.

22.2.6 Invalid NetStorage Authentication Domains

If you change the default NetStorage Authentication Domain to an invalid domain, either during the OES installation (NetStorage installation) or afterward with iManager, users might get a blank screen or a Service Not Available error when trying to access NetStorage. Also, you will not be able to change the Authentication Domains setting to a valid domain using iManager.

If this happens, you can change the Authentication Domains value by entering the following at the NetWare server console where NetStorage is running:

regsvr

regsvr set_static_configuration

regsvr domain1=ip_address:context

regsvr username=user.context

regsvr password=password

Replace ip_address:context with the IP address of the NetWare server where NetStorage is running and the eDirectory™ context of that server. Replace user.context with the NetStorage proxy user and the eDirectory context for that proxy user. The proxy user was defined when NetStorage was installed, and by default it is the eDirectory admin user. Replace password with the password for the NetStorage proxy user.

See Authentication Domains in the NetStorage Administration Guide for NetWare for more information on authentication domains and authentication contexts.

23.0 Novell Storage Services

This section contains known issues for Novell® Storage Services™ (NSS).

23.1 Linux Issues

23.1.1 Pool Names Must Be Unique on the Server

Pool names must be unique on the server. They cannot have the same name as any existing physical or logical device or partition, including software RAID devices. If a pool name is the same as any existing device or partition on the server, you cannot create the pool. If you later create a device or partition with the same name as a pool, you cannot delete the pool.

To avoid this problem, give every pool a unique name and make sure you do not later name any devices or partitions by that name.

23.1.2 Some Serial ATA Controller Drivers Might Cause the Server to Reboot

Some Serial ATA Controller drivers might cause the server to hang or reboot. If this occurs, check for an updated driver from the manufacturer.

23.1.3 NSS RAID 0 and NSS RAID 5 Not Supported in Linux Clusters or Mixed NetWare and Linux Clusters

If you have an OES Linux cluster or a mixed OES NetWare and Linux cluster and have configured NSS RAID 0 or NSS RAID 5, do not attempt to fail over or migrate an NSS pool from a NetWare cluster server to a Linux cluster server or from a Linux cluster server to another Linux cluster server. If you do this, it is possible that the NSS partition where the pool is located could be lost, which would result in data loss or corruption.

23.1.4 NetWare Snapshot Functionality Not Supported on Linux

The snapshot functionality that exists on NetWare is not yet supported in Linux. Therefore, all snapshots must be deleted on NSS pools on NetWare that are to be migrated or failed over to Linux. This is very important for mixed clusters that have both NetWare and Linux nodes in them. Moving a pool with a snapshot on it from a NetWare server to a Linux server and back to a NetWare server will corrupt the snapshot data. However, the pool data will still remain intact.

23.2 NetWare Issues

23.2.1 Upgrading Media Format for NetWare 6.5 SP5 or OES SP2 NetWare

For NetWare 6.5 SP5 and OES SP2 NetWare, the metadata structure for NSS volumes on NetWare has been enhanced to remove a name space limitation on hard links. After upgrading your NetWare server to NetWare 6.5 SP5 or OES NetWare SP2, you must upgrade the media format on its NSS volumes.

Before you convert from the old media format to the new media format, any existing hard links on your system's NSS volumes are visible, and they can be opened, closed, read, and written. However, you cannot create, delete, or rename an old-style hard link until the server's NSS volume media has been converted to use the new media format. Attempts to do so are rejected with an appropriate error.

IMPORTANT:After a volume has been converted to the new media format for NetWare 6.5 SP5 or OES NetWare SP2, it cannot be rolled back to the previous NetWare 6.5 SP3 or OES NetWare version.

For information about how to upgrade the media format, see Upgrading the Media Format for NSS Volumes on NetWare in the Novell Storage Services File System Administration Guide for OES.

23.2.2 Do Not Pull Drives When Restriping NSS RAID 5 or RAID 0 Devices

Pulling a drive in an NSS RAID 5 or RAID 0 device during restriping is not supported.

23.2.3 Moving NSS Volumes Cross-Platform

You can move devices containing NSS volumes from NetWare servers to OES Linux Servers. When you move an unshared NSS volume cross-platform from OES NetWare to OES Linux, you must decomission its volumes in eDirectory for the current server and then recommission them for the new server. For shared NSS volumes, Novell Cluster Services provides this service automatically. For details, see the following information in the Novell Storage Services File System Administration Guide for OES:

Scripts are available online to automate the process of decommissioning nonshared NSS volumes on OES NetWare or NetWare 6.5 servers and recommissioning them on OES Linux servers. To download the scripts, go to Decommissioning Script and Recommissioning Script for Moving NSS Volumes Cross-Platform. For information about using the scripts, see Using Scripts to Decommission and Recommission NSS Volumes in the Novell Storage Services File System Administration Guide for OES.

23.2.4 Activating Encrypted NSS Volumes from a Command Line

Placing the password for an encrypted NSS volume in a batch file, such as autoexec.ncf, is a security risk. To prevent potential password exposure, the volume:password syntax in the following NSS commands is now invalid.

nss /activate=volume:password
nss /volumeactivate=volume:password

Enter one of the following commands, then enter the password when prompted.

nss /activate=volume
nss /volumeactivate=volume

The password is required only when you activate an encrypted NSS volume for the first time after a system reboot. With this solution, the volume's password can only be entered from the keyboard in response to a prompt; the password never resides in a file on the disk.

23.2.5 Console or Application Hangs after You Delete a Pool-Level Snapshot Out of Sequence

If you delete a pool-level snapshot that is not the oldest snapshot of a given pool, the console (or application) might hang, requiring the server to be restarted.

To avoid this problem, delete pool-level snapshots in a first-created, first deleted manner, deleting the oldest snapshot of the pool first. If there is only one snapshot of the pool, deleting the snapshot does not cause the hanging problem.

23.2.6 Problems Following DFS Junctions in the Latest Windows 2000/XP Releases

The latest releases of Windows (Windows 2000 Service Pack 4 and later, Windows XP Service Pack 2) might have problems following DFS junctions over CIFS because of a defect in Windows. (This problem exhibits itself in a pure Windows environment.)

To avoid this problem for users with the advanced releases of Windows, install the Novell Client on their desktops. For alternate resolutions, see Problems Following DFS Junctions in Windows 2000/XP Releases (NetWare) in the Novell Storage Services File System Administration Guide for OES.

23.2.7 Using nsscpt.nlm

Nsscpt.nlm is a utility that helps you manage file names in cross-platform and cross-language deployments. For more information, see the following:

23.2.8 NSS Volumes Must Be Created, Moved, or Split on the Cluster Server Where the Volume's Shared Pool Was Created

If you attempt to create a volume on an NSS pool, and that pool resides on a cluster server other than the server where the pool was originally created, the eDirectory objects for that volume might not be created. However, the volume is created.

Also, you cannot do a volume move or split when the volume’s pool resides on a cluster server other than the server where the pool was originally created.

To work around these problems, always create volumes or do volume moves or splits on the cluster server where the pool was created.

23.2.9 Running NetWare under VMware’s ESX server

The NSS pool might become deactivated or the NSS partition might be deleted because the virtual device was configured in undoable mode. This causes the redo file to grow to the size of the data written. At this point, the virtual NetWare® server console displays a message that the redo file is out of space. You are prompted to create some free space or abort the operation. Selecting to abort might cause the NSS partition to be deleted because the partition had never been committed to the virtual device that was created in undoable mode.

To avoid this issue, do one of the following:

  • Create the virtual device in persistent mode not using redo file. All changes are committed immediately.

  • Create the virtual device in undoable mode leaving enough free space for the redo file to grow to the size of the partition created for the virtual server.

24.0 TCP/IP

This chapter provides information about TCP/IP issues in Novell® Open Enterprise Server (OES).

24.1 NetWare Issues

24.1.1 Fault Tolerance

  • Fault tolerance is supported on ODI™ compliant drivers, such as CE100B, IBMFE, PCNTNW, 3C90XC, and N100.

  • Fault tolerance does not work for multicast applications. When the NIC which contains the multicast group address information goes down, the multicast group address information is not transferred to the other members in the group. For example, applications like SLP will not work when the associated NIC goes down.

24.1.2 Per-Packet Load Balancing

  • To maintain communication, the card properties (such as checksum, offloading, and support) should be the same.

  • All cards on the same network should be grouped; otherwise, the packet will also reach an ungrouped member.

24.1.3 Virtual IP

  • Virtual IP currently works only in an environment configured for RIP-based routing.

  • Virtual IP will not work with applications that time out before the Routing Expiration Time Out Interval. Therefore, the applications will not get a chance to switch to the next-best hop for the route. For example, NCP™ and GroupWise® applications will time out before the routing expiration takes place and they will need to re-establish their connections.

24.1.4 Web-based TCP/IP Configuration

The following configurations are not supported in the Web-based TCPIP configuration (nirman.nlm) through NetWare® Remote Manager (NRM):

  • User-specified protocol (NIC Teaming)

  • BOOTP

  • EGP

  • SNMP

NOTE:Click the Configure TCPIP link in the left pane of NRM main page to access the Web-based TCP/IP configuration utility.

24.1.5 NIC Teaming

Currently, only one user-specified protocol is supported.

24.1.6 Configuration through INETCFG

  • If the netinfo.cfg file is corrupted and upon loading INETCFG you get a message asking you to reconfigure, delete the tcpip.cfg file.

    After the network configuration of the server is complete, we recommend that you back up the netinfo.cfg, netinfo.chk, and tcpip.cfg files located in sys:\etc. Then, in case of corruption, you can restore from the backed-up configuration.

  • In machines with multiple NICs, when already-in-use IP addresses are selected for binding, an ARP conflict error message for each binding is displayed in the system console screen. The system should automatically trigger unbinding of the IP addresses. If the binding persists, manually delete the bindings and reinitialize the system.

24.1.7 Supernetting

  • After a server is configured as a router (forwarding enabled), it cannot be configured with a supernet mask. Therefore, if a server is configured with a supernet mask, forwarding is disabled.

    If the mask is changed to a nonsupernet mask and the system is reinitialized, the INETCFG protocol configuration indicates that forwarding is enabled, even though it is not. To re-enable forwarding, you will need to make an explicit configuration change in INETCFG.

    To verify the status of forwarding, check the Forwarding tab in TCPCON.

24.1.8 Pragmatic General Multicast (PGM)

  • PGM is a reliable multicast transport protocol that works on a multicast-enabled network. Therefore, the network from the PGM sender to all the PGM receivers should be multicast enabled. If there are any routers on the path between the sender and the receivers, multicast forwarding must also be enabled in them.

24.1.9 Ipflt.nlm

If more than one board is bound to the same IP address, the filter should be configured for all boards; otherwise filtering will take place only for the configured member

24.1.10 Iptrace.nlm

The iptrace.nlm program will not be able to display the information of traces where destination addresses and intermediate hops do not respond to the source

24.1.11 Routecon.nlm

Currently, the option routecon monitor is not supported.

24.1.12 Set parameter "Preserve Secondary IPaddress after Reinitialize System"

TCPIP will try to preserve the secondary IP addresses added from the system console via the set preserve secondary ipaddress command after reinitialize system. Set this parameter to OFF if such secondary IP addresses are not to be preserved after reinitialize system

25.0 Novell IPv6

This section provides information about IPv6 issues in this release.

25.1 IPsec for IPv6

IPsec does not determine the key quality before the key is used, and no keys are automatically generated. Also, IPsec is not MP enabled. And key lengths must be of the same length as specified in the IPv6 Administration Guide.

25.2 RIPng for IPv6

A default route cannot be specified for IPv6.

25.3 Apache2 for IPV6

To use Apache2 for IPv6, copy the Winsock NLM™ files from sys:\research\ipv6\winsock to c:\nwserver. Copy the folders and NLM files from sys:\research\ipv6\apache2 to sys:\apache2.

25.4 Deleting Boards

If there are multiple boards of the same type, removing one board might result in unbinding IPv6 addresses from all of the boards. This is because the driver unloads and reloads when a board is deleted.

25.5 Range Checking

Range checking for the variables in ip6.cfg and rtadvd.cfg is not yet implemented.

25.6 Memory Leakage

On every unload and reload of the IPv6 stack, 728 resources of 4 KB are not freed and they remain in the memory unless the machine is rebooted.

25.7 Across the Routers

The server abends during pmtu determination by the sender, when the host sends data across a router to another host.

26.0 Nsure Audit

This section contains information about Nsure™ Audit for NetWare® issues in this release.

26.1 NetWare Issues

26.1.1 Nsure Audit 1.0.3 Secure Logging Server required for NetWare Service Pack 4

The Nsure Audit Platform Agent included with in OES SP1 or later has been updated to the 1.0.3 release to fix communication issues between the Platform Agent and the Secure Logging server. Existing Secure Logging Servers (SLS) that are connected to by existing NetWare instrumentation should be upgraded to Nsure Audit 1.0.3 release prior to applying Support Pack in order to avoid logging event issues.

The 1.0.3 SLS is backward compatible and accepts events from version 1.0.2 of the Platform Agent until such servers are also upgraded to 1.0.3. If the SLS is not upgraded prior to installing the Support Pack, the process could hang until it timeouts attempting to connect to a 1.0.3 SLS, and then it will cache events on the local server. Once the SLS is upgraded, the events that have been cached will be delivered to the newly upgraded SLS.

26.1.2 Server Unresponsive during Upgrade

If the server becomes unresponsive while upgrading Nsure Audit after you receive a message stating that AUDIT is being unloaded, you must restart the server and unload AUDITNW before restarting the Support Pack installation.

26.1.3 Auditagt.ncf Overwritten When Applying Service Packs

When applying NetWare 6.5 Support Packs, auditagt.ncf might be overwritten. To prevent this, create a backup copy of this file before applying the Support Pack.

27.0 Nterprise Branch Office

This section contains information about Nterprise™ Branch Office™ (NBO) issues in this release. For additional information, see the Readme located with the Nterprise™ Branch Office™ online documentation.

27.1 NetWare Issues

27.1.1 Nterprise Branch Office Pattern Has Been Removed

Beginning in NetWare® 6.5 SP3, the pattern install option for the Nterprise Branch Office - Central Office Server (Rsync) has been removed from the NetWare installation program.

28.0 NTPv3 iManager Plug-in

This section describes the known issues about NTPv3 in this release.

28.1 Known Issues

  • The Migration link in iManager does not display TimeSync servers if they are in a different context.

  • The NTP migration is not supported on Firefox* and Mozilla* browsers.

  • iManager help files are not localized.

29.0 OpenSSH on NetWare

This section contains information about OpenSSH on NetWare® issues in this release.

29.1 NetWare Issues

There are no issue for OpenSSH for this release.

30.0 QuickFinder Server 4.2

This section contains information about QuickFinder™ issues in this release.

NOTE:QuickFinder was formerly know as NetWare® Web Search.

30.1 Linux Issues

30.1.1 Generating Indexes of NSS Volumes

To generate an index of a Linux-mounted NSS volume, you must give the novlwww user and/or www group read/write access to the NSS volume.

30.1.2 Administering with eDirectory Credentials

To administer QuickFinder using your eDirectory™ credentials, make sure your User object in eDirectory is LUM-enabled, and then add it to the www group.

30.1.3 Cannot Log In To QuickFinder

If you are unable to log in to the QuickFinder Manager as a LUM-enabled admin that you created during the installation, then you might need to update the LUM cache by entering the following command at a console prompt:

namconfig cache_refresh

30.1.4 Upgrading from a Previous Version

After upgrading from a previous version of Web Search or QuickFinder, the new template files are not placed in the <qfsearch>/Templates directory because this would overwrite any changes you might have made to them. The new template files are placed in the <qfsearch>/Templates/Samples directory. To take advantage of the functionality the new templates provide, copy the template files from the <qfsearch>Templates/Samples directory to the <qfsearch>/Templates directory.

30.2 NetWare Issues

30.2.1 IP Management

When changing an IP address on a server, you can use the IP management portion of NRM to update individual product configuration files. The QuickFinder 4.0.0 Application might report “Invalid” even after it has been corrected and refreshed. To display the correct “Valid” status, log out and log back in to NRM.

30.2.2 Upgrading from a Previous Version

After upgrading from a previous version of Web Search or QuickFinder, the new template files are not placed in the <qfsearch>/Templates directory because this would overwrite any changes you might have made to them. The new template files are placed in the <qfsearch>/Templates/Samples directory. To take advantage of the functionality the new templates provide, copy the template files from the <qfsearch>Templates/Samples directory to the <qfsearch>/Templates directory.

30.2.3 Upgrading to OES SP1 or Later

If you apply OES SP1 or later to an OES for NetWare server running Web Search, Web Search is automatically upgraded to QuickFinder.

The OES NetWare installation program lists QuickFinder as version 4.1.0 for both new installations and upgrades, but the QuickFinder version number is 4.0 for this release.

31.0 Scripting Products

This section describes the known issues about scripting products in this release

31.1 Known Issues

31.1.1 PHP

For PHP 5.0 NetWare specific limitations and issues, see NetWare Specific Issues.

31.1.2 Perl

For Perl 5.8.4 NetWare specific limitations and issues, see NetWare Specific Issues.

31.1.3 Universal Component System

  • Accessing the TextWindow component from Perl and PHP is not fully supported.

For more information on UCS issues, see Readme.

31.1.4 Novell Script for NetWare

  • The date data type for the MySQL* parameter object is not supported in this release.

For more information on NSN issues, see the Readme

32.0 Storage Management Services (SMS)

This section contains information about Storage Management Services™ (SMS) issues in this release.

32.1 Linux Issues

32.1.1 NSS File System

  • Hardlinks are backed up as normal files and the link information is not maintained. This results in restoration of these files as normal files.

32.1.2 POSIX Compliant File Systems

  • Backup and Restore of Extended Attributes is supported within the same file system, while restoration is not supported across different file systems.

  • During restoration, a non-root user cannot overwrite the read only files to the POSIX-complaint file systems, as write access is required for updating the files.

33.0 Third-Party Adapters, Drivers, and Applications

This section contains information about third-party adapters, drivers, and application issues with NetWare in this release.

If you are using third-party software with Open Enterprise Server, check with the software vendor about the most current version to use with OES.

33.1 NetWare Issues

33.1.1 Update Open File Manager before Applying the Support Pack

If you are running St Bernard’s Open File Manager 9.4, you should upgrade to Open File Manager 9.401m before installing OES NetWare SP1 or NetWare 6.5 SP4 or later a later Support Pack. Upgrading to build 9.401m fixes a possible abend during backup. To obtain the upgrade, contact St Bernard Technical Support .

33.1.2 Dell Server Management Software (AppCD)

Prior to installing the Support Pack, temporarily disable the Dell OpenManage Software by editing the autoexec.ncf file and commenting out the OpenManage load statement(s) by adding a preceding semicolon (;) or pound sign (#).

For OpenManage version 4.3 or newer comment out the following line: sys:\system\omdata\config\omnwstrt.ncf

For OpenManager versions prior to version 4.3 comment out the following lines: arraymgr.ncf sys:system/dell/omanage/iws/bin/netware/omastart If a DRACIIIXT, ERA, or ERA/O card is present, also comment out the following line: sys:system\dell\omanage\rac\d3start

Restart the server and install the Support Pack. After the Support Pack is installed, you can uncomment the lines and restart the server to finalize the installation. Failure to follow these steps might cause the Support Pack install to stop.

See Dell's Support Web site for the latest information about OpenManage and other Dell products.

33.1.3 Hewlett-Packard SmartStart

SmartStart* versions earlier than 7.00 are not supported in the deployment of NetWare® 6.5. Updated driver, Health, and Management agents are available in the ProLiant* Support Pack (PSP) for NetWare version 6.41 or later, which is available on the Hewlett-Packard Web site.

If versions earlier than SmartStart 7.00 or PSP 6.41 are used, ensure that all of the Health and Management agent modules have been removed from the c:\nwupdate subdirectory before restarting the server and that all of the health and agent load lines have been removed from the autoexec.ncf file.

For updates to SmartStart and the ProLiant Support Pack, check with your Hewlett-Packard representative or the Hewlett-Packard Web site.

33.1.4 Symantec Norton Anti-Virus v8

Symantec* Norton Anti-Virus* v8 is not supported on NetWare 6.5. Contact your Symantec Sales Representative to purchase the upgrade (v8.1) in order to continue to run Symantec NAV on NetWare 6.5. For detailed information, see TID 10085603 in the Novell® KnowledgeBase.

33.1.5 CPQSHD.CDM Driver

If servers running cpqshd.cdm experience any drive deactivation issues, could be caused by cpqshd.cdm. Check with your Hewlett-Packard representative or the Hewlett-Packard Web site for updates to this driver.

33.1.6 QLogic QLA2x00.HAM Driver

The QL2300.HAM QLogic storage controller driver has been superseded by the QL2X00.HAM driver in this support pack. If you install using the overlay (CD Image) method, the new QL2X00.HAM driver is used automatically. If you install using the support pack script install (using nwconfig.nlm), the old QL2300.HAM driver on the server is used. To use the new driver, edit the startup.ncf file and replace the reference to the QL2300 driver with QL2X00.

For detailed information on the QLogic QLA2x00 HAM Driver for NetWare, see TID 10085142 in the Novell KnowledgeBase.

33.1.7 ISA Adapters Are Not Supported

For performance and scalability reasons, all ISA adapter drivers were removed with the NetWare 6.0 release. There is a possibility that a family driver might support adapters which run on more than one bus type (PCI and ISA). In this case, any ISA adapter would be considered a noncertified driver and would not be supported by Novell.

33.1.8 Promise Adapter Support

The drivers that support the Promise Technology* FastTrak S150 TX2plus and SATA150 TX2plus cards do not support CD-ROM drives.

34.0 Virtual Office

This section contains information about Virtual Office 1.5 issues in this release.

NOTE:Virtual Office 1.5 is installed as part of OES Support Pack for NetWare and Linux. Any previous installation of Virtual Office 1.3 will be upgraded.

34.1 Linux Issues

34.1.1 Restart Tomcat to Avoid 500 Error

After upgrading Virtual Office by applying the Support Pack, you might receive a 500 error when Virtual Office loads the first time. Restarting Tomcat resolves the issue.

To restart tomcat, enter the following at the system console enter /etc/init.d/novell-tomcat4 restart

To monitor Tomcat coming up, enter tail /var/opt/novell/tomcat4/logs/catalina.out

34.1.2 Single Sign-On between Virtual Office and NetStorage Does Not Work with NetIdentity

When NetIdentity workstations access NetStorage through Virtual Office running on OES Linux, users are prompted for login to both Virtual Office (via login form) and NetStorage (via NetIdentity pop-up). There is no resolution for this issue.

34.1.3 Japanese Filenames Do Not Display Correctly

When using Internet Explorer on Windows to upload files to a Virtual Team, files with a Japanese filename might not upload with the correct filename. To work around this problem, perform the following steps on your Linux server:

  1. Run YaST Control Center.

  2. Select System, then click Selection Language.

  3. Select Japanese as the system language, Then click Details.

  4. Change the drop-down box for Locale Settings for User Root from “ctype only” to “yes.”

  5. Restart Apache and Tomcat.

34.2 NetWare Issues

34.2.1 LDAP Connections Held Open

If the number of concurrent connections is limited to a single connection, subsequent logins might not succeed when LDAP connections do not close properly. To make sure you can log back in to Virtual Office, always log out using the Log Out button.

In addition, there is currently an issue with eDirectory™ leaving open LDAP connections that should close when a user logs out of Virtual Office. The resolve this, do not use SSL for the communication between Virtual Office and eDirectory. With Virtual Office and eDirectory on the same machine, this does not pose a security risk.

To make this change:

  1. Disable the Require TLS for Simple Binds with Password option in iManager.

    This allows non-SSL LDAP communication. See Requiring TLS for Simple Binds with Passwords in the Novell eDirectory 8.7.3 Administration Guide for more information.

  2. Modify the webapps/vo/WEB-INF/PortalServlet.Properties file to not use SSL by changing the System.DirectoryAddress property to use the non-SSL port (389) and changing the System.DirectorySSL property to False.

34.2.2 Restart Tomcat to Avoid 500 Error

After upgrading from Virtual Office 1.5 (NetWare 6.5 SP3) by applying the Support Pack, you might receive a 500 error when Virtual Office loads the first time. Restarting Tomcat resolves the issue.

To restart tomcat

  1. At the system console, enter tc4stop.

  2. To start Tomcat, enter tomcat4.

  3. To see the two Tomcat classes running, enter java -show.