OES 11 SP1 includes new or changed features in the following components:
Novell AFP in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, Novell AFP provides the following enhancements and behavior changes in the OES 11 SP1 release:
Subtree search feature is introduced for searching AFP users in subtrees in eDirectory. For more information, see Subtree Search in the OES11 SP1: Novell AFP Administration Guide.
The Archive and Version Services in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. There are no other changes in the OES 11 SP1 release of Archive and Version Services.
Novell CIFS in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, OES 11 SP1 provides the following enhancements and changes for CIFS:
Novell CIFS will now be able to display the list of trustees associated with the specified file or folder as per the CIFS cache record, import the trustee information from the trustee_database.xml file associated with the specified volume into the CIFS cache, and display the count of new, modified, and removed trustees for the specified volume. For more information, see Viewing the Trustees Associated with a File or Folder,
Synchronizing the Trustee List for a Volume,
and Viewing Statistics of Trustees for a Volume
in the OES 11 SP1: Novell CIFS for Linux Administration Guide.
Novell Distributed File Services in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, OES 11 SP1 provides the following enhancements and changes for DFS:
The Distributed File Services plug-in for iManager was modified to allow the [Public] trustee to be selected as a trustee of a junction. For information about setting trustees on DFS junctions, see Adding or Deleting Trustees for the Junction in the OES 11 SP1: Novell Distributed File Services Administration Guide for Linux.
The DNS and DHCP Services in OES 11 SP1 have been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, the following enhancements are available:
In OES 11, the DHCP process ID is located in /var/run/dhcpd.pid.
In OES 11 SP1, the DHCP process ID is located in /var/lib/dhcp/var/run/dhcpd.pid. The path for dhcpd.pid was changed because the /opt/novell/dhcp/bin/cluster_dhcpd.sh script was modified to support DHCP-4.2.3-P2 in SLES 11 SP2. To improve security, SLES 11 SP2 included a security update that enables dhcpd to run in a chroot environment. For information about this security update, see “The SUSE Linux Enterprise Server Version” in the SLES 11 Administration Guide.
The cluster_dhcpd.sh script was modified to alter the location of the dhcpd.pid file to /var/lib/dhcp/var/run, and set the ownership of the path to the dhcp user instead of the root user.
If you use DHCP in a cluster with Novell Cluster Services, you must manually modify the path for the dhcpd.pid file in the unload script for the DHCP resource. This allows the process to be gracefully unloaded from a node when the DHCP cluster resource fails over to a different node. For information on how to modify the path, see “Changing the Path for dhcpd.pid”.
Beginning in OES 11 SP1, the Java Console supports resource record names specified in the Chinese language. You can now specify resource record names with a combination of English, Chinese, and numeric characters. You can specify a maximum of three Chinese characters during resource record creation.
Domain Services for Windows in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, Domain Services for Windows provides the following enhancement in the OES 11 SP1 release:
DSfW installation and configuration using the YaST administrative tool has been modified. The configuration screens have been reorganized to enable you to deploy a Domain Controller in a fast and easy manner. DSfW now enables you to deploy a domain controller using the Express Install option. Express Install minimizes the number of configuration screens and assigns default values for certain configuration parameters. For more information, see Installing Domain Services for Windows in the OES 11 SP1: Domain Services for Windows Administration Guide.
DSfW AutoYaST enables you to install DSfW for a new forest domain, new domain in an existing forest, and new domain controller in an existing domain without any manual intervention. For information, see Installing DSfW Using AutoYast in the OES 11 SP1: Domain Services for Windows Administration Guide
Dynamic Storage Technology supports OES 11 SP1 file systems running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, the following enhancements are available:
Search Pattern: You can specify file names with spaces in them.
ShadowFS: The Load ShadowFS now and at boot time option has been renamed as Load ShadowFS. When you select the Load ShadowFS check box and click Submit, Dynamic Storage Technology starts an instance of ShadowFS by issuing the /etc/init.d/novell-shadowfs start command when you click the button, and configures the server to load ShadowFS at system restart. Only one instance of ShadowFS should be running at a time. ShadowFS should be enabled only if you are using Novell Samba or supported Linux file access protocols to access the DST volume.
Subdirectory Restrictions: The Subdirectory Restrictions filter has been modified as follows:
Precede subdirectory paths with a forward slash (/), such as
/subdir1/subdir2
In addition to subdirectory paths, the Exclude Subdirectory option allows you to specify a directory name that might exist in multiple places on a volume. You indicate this intended action by specifying only a directory name with no forward slashes, and the directory name must contain at least one wildcard (such as ? or *). All instances of directories that match the specified directory name are excluded from the policy run.
For example, to exclude all GroupWise archive subdirectories, specify the following directory name with wildcards:
of???arc
For information, see Subdirectory Restrictions
in the OES 11 SP1: Dynamic Storage Technology Administration Guide.
The Graphical DS Repair Utility has been added to OES 11 SP1. This tool is automatically installed during a new OES 11 SP1 installation. If you are upgrading to OES 11 SP1, you must manually select novell-ndsgrepair under the eDirectory pattern.
The eDirectory team is updating the documentation for the Graphical DS Repair. When the documentation is completed, a link will be posted here and in the OES 11 SP1 online documentation pages on the Web.
The storage file systems, management tools, and file access protocols support OES 11 SP1 running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. The following changes and enhancements are available for file system management in Novell Open Enterprise Server 11 SP1:
Btrfs: Support was added for the Btrfs file system. The Novell Storage Services (NSS) Management Utility (NSSMU), Novell Linux Volume Manager (NLVM) Linux commands, NCP Server, and Novell Cluster Services were modified to support the Btrfs file system for Linux volumes. The Btrfs file system is now available as an alternative to other supported file systems (Ext2, Ext3, Reiserfs, and XFS) when you create a Linux volume. The btrfsprogs package is required. You can use NSSMU or NLVM to manage the Btrfs volumes as you would manage other Linux data volumes. Btrfs volumes can also be configured for NCP file access and for clustering with Novell Cluster Services.
SUSE Linux Enterprise Server (SLES) 11 Service Pack 2 (SP2) also supports the Btrfs file system in the YaST2 Partitioner. You can use the Partitioner during the system installation to configure a Btrfs solution for the system device. YaST2 automatically installs the btrfsprogs package if you use Btrfs for the root (/) file system. Bootloader support for /boot on Btrfs is not available in SLES 11 SP2; it is planned to be available beginning in SUSE Linux Enterprise 12.
For information about the features of Btrfs, see Btrfs
in the OES 11 SP1: Linux POSIX Volume Administration Guide.
NCP Volumes: You can NCP enable Linux volumes as you create them by using NSSMU or the nlvm create linux volume command. For information, see the following:
NCP Trustee Report:
The NCP Trustee Report in Novell Remote Manager can be used to generate reports for an NSS volume, including a Dynamic Storage Technology shadow volume comprised of two NSS volumes. For information, see Generating and Viewing NCP Trustee Reports for NSS Volumes
in the OES 11 SP1: Novell Remote Manager Administration Guide.
Unattended upgrade from OES 2 or OES 11 to OES 11 SP1 has been enhanced and has undergone some changes. For more information, see Using AutoYaST for an OES 11 SP3 Upgrade
in the OES 11 SP3: Installation Guide.
A single integrated ISO to install or upgrade OES 11 SP1 is now available. This ISO contains both SLES 11 SP2 and OES 11 SP1.
Channel upgrade support is added in OES 11 SP1. It supports upgrade from OES 11 to OES 11 SP1.
This section describes enhancements and changes to Novell iPrint for Novell Open Enterprise Server (OES) 11 SP1.
Novell iPrint now runs on the OES 11 SP1 platform. Novell iPrint supports the SLES 11 base completely, along with its enhancements and hardware for its lifecycle.
Novell secure printing and iPrint Client Management features can now function without the Novell Client component. Users working on Windows / Active Directory environments now can have ICM and shared login abilities with or without the Novell Client.
Print driver transfer methods in iPrint Migration have been improved, and dependencies on other stacks have been reduced to increase reliability and robustness. iPrint Migration has also been enhanced in areas such as Print Driver transfer and Driver Platform selection.
The iprintman utility now runs on Windows, Mac, and Linux clients, and has been rewritten to use the Java IPP libraries for performing various operations.
NOTE:This feature is under development and might not function as expected in all cases. Novell plans to complete development in a future OES release.
Novell iPrint in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, iPrint provides the following enhancements and behavior changes in the OES 11 SP1 release:
You can download iPrint Clients from the OES 11 SP1 welcome page or from the iPrint Printer List web page. You can download the latest version of the iPrint Client from the iPrint Client download site.
A new version of the iPrint Client 5.94 is available for Windows XP/Vista/Win 7/Win 8/Win 8.1.
A new version of the iPrint Client for Macintosh 5.74 is available for Mac OS X 10.7 and later. The 5.74 client includes support for Mac OS X 10.9 (Mavericks).
You can now perform accounting operations for iPrint Direct Printers on the iPrint Mac Client 5.74.
The NLVM and NSSMU management tools support Linux POSIX volumes on OES 11 SP1 running on 64-bit SUSE Linux Enterprise Server (SLES) 11 Service Pack (SP) 2.
In addition to bug fixes, NSSMU provides the following changes and enhancements for Linux POSIX volume management in the OES 11 SP1 release:
Create Linux Volume:
The NCP Enable option can be used to enable the Linux POSIX file system on the volume to be accessed with the NetWare Core Protocol (NCP).
Support was added for the Btrfs file system. The Btrfs file system is now available as an alternative to other supported file systems (Ext2, Ext3, Reiserfs, and XFS) when you create a Linux volume. The btrfsprogs package is required. You can use NSSMU or NLVM to manage the Btrfs volumes as you would manage other Linux data volumes. Btrfs volumes can also be configured for NCP file access and for clustering with Novell Cluster Services.
Confirmation Prompt: You are automatically prompted to confirm actions for certain commands that destroy data, such as when you initialize a device or delete Linux POSIX volumes.
File System Types: When you create a Linux POSIX volumes, the supported file system types are now listed in alphabetical order: btrfs, ext2, ext3, reiserfs, and xfs.
Linux Volume Details: On the Linux Volumes page, a volume’s information includes the NCP Enabled parameter and status (Yes or No).
Mount Point Path: The default mount point path for Linux volumes is /usr/novell/<volume_name>.
Partitions: On the NSSMU Partitions page, the Partitions list panel has been widened to accommodate long partition names. If you widen the NSSMU display screen, it widens the Partitions list panel and allows you to see the partitions' full names.
In addition to bug fixes, NLVM commands provide the following changes and enhancements for Linux POSIX volume management in the OES 11 SP1 release:
Sizes: The following enhancements are available for the size option:
The default multiplier for sizes was changed from M (megabytes) to G (gigabytes). If no multiplier is provided, the value is assumed to be in gigabytes. For example:
size=20 (20 gigabytes is used)
Use the T multiplier to specify sizes in terabytes (TB).
All sizes can be entered as whole numbers or with fractional parts such as 200.45G and 3.98T.
Multiple Devices: You can specify multiple devices for the following commands:
Init: You can specify multiple devices to be initialized at the same time. Each device is formatted with the same specified partitioning scheme and share state.
Share: You can specify multiple devices to be shared at the same time.
Unshare: You can specify multiple devices to be unshared at the same time.
No Prompt: The --no-prompt NLVM option can be used with the nlvm delete linux volume command and the nlvm init command to prevent a confirmation message from being displayed.
Confirmation Prompt: You are automatically prompted to confirm actions to initialize a device or to delete a Linux POSIX volume.
Create Linux Volume:
Support was added for the Btrfs file system. The Btrfs file system is now available as an alternative to other supported file systems (Ext2, Ext3, ReiserFs, and XFS) when you create a Linux volume. The btrfsprogs package is required. You can use NSSMU or NLVM to manage the Btrfs volumes as you would manage other Linux data volumes. Btrfs volumes can also be configured for NCP file access and for clustering with Novell Cluster Services
The ncp option for the nlvm create linux volume command can be used to enable the Linux POSIX file system on the volume to be accessed with the NetWare Core Protocol (NCP).
List Linux Volumes: The volume information displays NCP if the Linux volume is enabled for NCP.
NSSMU, NLVM Linux commands, NCP Server, and Novell Cluster Services were modified to support the Btrfs file system for Linux volumes. The Btrfs file system is now available as an alternative to other supported file systems (Ext2, Ext3, Reiserfs, and XFS) when you create a Linux volume. The btrfsprogs package is required. You can use NSSMU or NLVM to manage the Btrfs volumes as you would manage other Linux data volumes. Btrfs volumes can also be configured for NCP file access and for clustering with Novell Cluster Services.
SUSE Linux Enterprise Server (SLES) 11 Service Pack 2 (SP2) also supports the Btrfs file system in the YaST2 Partitioner. You can use the Partitioner during the system installation to configure a Btrfs solution for the system device. YaST2 automatically installs the btrfsprogs package if you use Btrfs for the root (/) file system. Bootloader support for /boot on Btrfs is not available in SLES 11 SP2; it is planned to be available beginning in SUSE Linux Enterprise 12.
For information about the features of Btrfs, see Btrfs
in the OES 11 SP1: Linux POSIX Volume Administration Guide.
NSSMU and NLVM were modified to support the creation of NCP volumes on Linux POSIX file systems. You can NCP enable Linux POSIX volumes, an LVM volumes, and clustered LVM volumes as you create them. When you enable NCP for a Linux volume, an NCP volume of the same name (using all capital letters) is automatically created. An NCP share is created at the root of the Linux volume.
For clustered LVM volumes, the NCP Virtual Server object is automatically created and the NCP mount, dismount, and status commands are added to the scripts for the LVM volume group cluster resource. The Novell Cluster Services Generic File System template is used to specify the default cluster policies and scripts for the cluster resource. After you create the resource, you can use the Clusters plug-in for iManager to set up preferred nodes for the resource and to manage the resource.
For information about Linux volume support changes in SUSE Linux Enterprise Server 11 SP2, see What’s New in SLES 11 SP2
in the SUSE Linux Enterprise Server 11 Storage Administration Guide.
Linux User Management in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, Linux User Management provides the following enhancements and behavior changes in the OES 11 SP1 release:
Enabling Multiple Users for Linux in a LUM Group:
The LUM iManager plug-in provides a new tab that allows you to linux-enable multiple users in a group in a simplified manner. For more information, see Enabling Multiple Users for Linux in a LUM Group
in the OES 11 SP1: Novell Linux User Management Administration Guide.
Enabling Multiple Users for Linux in a Container:
You can now Linux-enable multiple users in a container. The LUM iManager plug-in provides a new tab that allows you to linux-enable multiple users in a container. For more information, see Enabling Multiple Users for Linux in a Container
in the OES 11 SP1: Novell Linux User Management Administration Guide.
You can linux-enable multiple users using the command line as well. The namuseradd command provides the -A option that allows you to enable all non-LUM users in the specified context. For more information, see the namuseradd utilityin the OES 11 SP1: Novell Linux User Management Administration Guide.
Option to Select administrator group in YaST: The LUM configuration in YaST always adds the administrator to a group called the admingroup. LUM configuration in YaST now provides an option to browse and specify an already existing group instead of creating a new admingroup.
The Migration Tool in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, the Migration Tool provides the following enhancements and behavior changes.
You can now migrate services from OES 2 SP2, OES 2 SP3, OES 11, and OES 11 SP1 source servers to an OES 11 SP1 target server using service-specific migration scripts. For information, see Service Migration
in the OES 11 SP3: Migration Tool Administration Guide.
The Migration Tool data synchronization feature has been enhanced. You must upgrade the source server with the latest patches before performing migration.
If the source server is NetWare, contact Novell Technical Support (NTS) for information on patching the server.
Synchronizes trustees only at the directory level. Trustees at the file level are not synchronized.
Trustees on the source server are not synchronized to the target server; only data is synchronized.
NCP in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, NCP provides the following enhancements and behavior changes in the OES 11 SP1 release:
NCP Server was modified to refresh its OpenSLP registration of cluster resource virtual NCP servers based on the setting for the eDirectory advertise-life-time (n4u.nds.advertise-life-time) parameter. The n4u.nds.advertise-life-time parameter is set by default to 3600 seconds (1 hour) and has a valid range of 1 to 65535 seconds. Previously, NCP Server re-registered the virtual NCP servers with SLP every 30 minutes regardless of the eDirectory advertise-life-time setting. For information about setting the eDirectory advertise-life-time parameter in a cluster, see SLP in the OES 11 SP1: Novell Cluster Services 2.1 for Linux Administration Guide.
Introduced NCP_TCP_KEEPALIVE_INTERVAL parameter to configure keep alive timeout for all the TCP client connections accepted by the NCP server.
The maximum value of CONCURRENT_ASYNC_REQUESTS parameter has been increased to 256 from the earlier value of 128.
The default value of CONCURRENT_ASYNC_REQUESTS and ADDITIONAL_SSG_THREADS has been increased to 25.
Added a new switch /v to ncpcon volumes command to list the volume IDs.
NCP server does not support NFS and AFP namespaces and hence it will not return these namespaces in response to NCP requests regardless of what namespaces are supported on that volume by NSS.
Configuration options are provided to update UID number for non-LUM users.
NetStorage has been modified to run on OES 11 SP1. There are no other changes in the OES 11 SP1 release of NetStorage.
Novell Cluster Services 2.1 supports OES 11 SP1 services and file systems running on 64-bit SUSE Linux Enterprise Server 11 SP2. In addition to bug fixes, Novell Cluster Services provides the following enhancements and behavior changes in the OES 11 SP1 release:
In the Clusters plug-in to iManager, when you cluster-enable an existing Novell Storage Services (NSS) pool, the Online Resource after Creation option on the Cluster Pool Information page is available and deselected by default. If the pool is deactive when you cluster-enable it, you can select this option to automatically bring the resource online, which activates the pool on a preferred node and mounts the pool’s volumes.
Previously, the option was deselected and dimmed, the resource was automatically placed in an offline state, and no action was taken for the state of the pool and its volumes.
For information, see Cluster-Enabling an Existing NSS Pool and Its Volumes
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
When you enable Novell CIFS as an advertising protocol for a cluster-enabled pool, the default name is based on the NCP virtual server object name. If you change the NCP virtual server name in NSSMU or in the Storage plug-in for iManager, the CIFS virtual server name is updated accordingly. For information, see Novell CIFS for Linux
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
When you create a cluster-enabled Linux POSIX volume group with NSSMU or with the nlvm create linux volume command, you can use the ncp option to enable users to access the Linux POSIX file system on the volume with the NetWare Core Protocol (NCP). Previously, the NCP volume (share) was created manually after the resource was created and brought online.
For information, see Configuring an LVM Volume Group Cluster Resource with NSS Management Tools
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
The SUSE Linux Enterprise Server 11 SP2 operating system supports the Btrfs file system. The btrfsprogs package must be installed.
Novell Cluster Services supports using the Btrfs file system when you create a clustered Linux LVM volume group by using the NSS Management Utility (NSSMU) or Novell Linux Volume Manager (NLVM) commands. If you use Linux commands to create the LVM volume group, you can use the mkfs.btrfs(8) command to add the Btrfs file system to the volume. You specify btrfs as the file system type for the LVM volume group cluster resource. You can enable NCP file access for the Btrfs volume.
For information, see Configuring an LVM Volume Group Cluster Resource with NSS Management Tools
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
The cluster migrate command now offers the -list, -most, and -next options. For information, see MIGRATE
in the Cluster Management Commands table of the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
The Clusters plug-in for iManager 2.7.5 has been reorganized. In Roles and Tasks under Clusters, the Cluster Manager, BCC Manager, Cluster Event Log, and Cluster Options menu items have been replaced with two options: My Clusters and My Resources. Links on the these pages take you to the familiar cluster options presented as tabs: Cluster Manager, BCC Manager, Cluster Event Log, and Cluster Options.
My Clusters:
The logged-in cluster administrator can set up a personalized list of clusters to manage. This allows an administrator to view at a glance the status of multiple clusters. An administrator can also customize the display to sort the entries, modify the columns, or filter the entries. The list of clusters and display preferences persist between the administrator’s logins to iManager on the same server. For information, see Setting Up a Personalized List of Clusters to Manage
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
My Resources:
The logged-in cluster administrator can set up a personalized list of cluster resources to manage. This allows an administrator to view at a glance the status of multiple cluster resources for multiple clusters. An administrator can also customize the display to sort the entries, modify the columns, or filter the entries. The list of cluster resources and display preferences persist between the administrator’s logins to iManager on the same server. For information, see Setting Up a Personalized List of Resources to Manage
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
The Clusters plug-in supports the management of OES and NetWare clusters and resources. It cannot be installed on a NetWare server.
If you use Role-Based Services (RBS), upgrading the Clusters plug-in does not automatically update the RBS settings. The RBS Configuration page reports that the Clusters plug-in is out-of-date. The plug-in must be reinstalled on the RBS Configuration page in order to pick up the My Clusters and My Resources menu options. For information, see Updating Role-Based Services for the Clusters Plug-in for OES 11 SP1
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
A comparison of the old and new interface is available in Clusters Plug-In Changes for Novell iManager 2.7.5
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
Availability for prior releases: January 2013 Scheduled Maintenance for OES 11
The STONITH (shoot-the-other-node-in-the-head) capability allows Novell Cluster Services to kill a suspect node by using remote power control. Unlike a poison pill, it does not require a response from the suspect node. STONITH is used after a poison pill is issued; it does not replace the poison pill. For information, see Configuring STONITH
in the OES 11 SP1: Novell Cluster Services for Linux Administration Guide.
Novell Cluster Services for OES 11 SP1 introduces some intelligence in the master election process when the master leaves a cluster (voluntarily or involuntarily). The same master is elected under both the old and new algorithms, but the conclusion is reached sooner, especially for larger clusters. The new algorithm substantially reduces the time needed for master election in some cases.
For information about the old and new algorithms, see Electing a Master Node
in the OES 11 SP1: Novell Cluster Services NetWare to Linux Conversion Guide.
Availability for prior releases: September 2012 Scheduled Maintenance for OES 11
When you convert NetWare 6.5 SP8 clusters to OES 11 SP1, if the AFP or CIFS protocols are configured as advertising protocols for an NSS pool cluster resource on the NetWare cluster, the corresponding monitoring commands are automatically added to the monitor script for the resource on OES 11 SP1. Monitoring is not available for NetWare clusters and is disabled while the cluster is in mixed mode. Monitoring can be enabled for the resource after the final cluster conversion is complete. For information, see File Access Protocols for Monitor Scripts
in the OES 11 SP1: Novell Cluster Services NetWare to Linux Conversion Guide.
The DHCP process ID file location was changed from /var/run/dhcpd.pid to /var/lib/dhcp/var/run/dhcpd.pid. During a cluster upgrade from OES 11 to OES 11 SP1, you must modify the location of the dhcpd.pid file in the DHCP cluster resource’s unload script. After you modify the script, you should bring the resource online only on OES 11 SP1 nodes. This is necessary to ensure a graceful shutdown of the dhcpd.pid process when the DHCP resource fails over to a different node. For information, see Path Change for dhcpd.pid
and Changing the Path for dhcpd.pid
in the OES 11 SP3: Novell DNS/DHCP Services for Linux Administration Guide.
The default sequence of commands has changed for the load script and unload script of newly created NSS pool cluster resources. In the load script, the secondary IP address is added after the volumes are mounted. In the unload script, the secondary IP address is removed before the pool is deactivated.
The new sequence improves the handling of client reconnects because it leverages the clients’ auto-reconnect mechanisms. With the previous order, clients might attempt to connect to the IP address before the data is ready or after the data is unavailable, which results in an Object Not Found error. Some clients might automatically try again to connect, but some do not. Thus, it is more efficient to add the IP address after data is available and remove it before the data is not available.
Newly created pool cluster resources use the following sequence for commands in a load script. The order is reversed in an unload script.
Existing scripts are not modified during a cluster upgrade. We recommend that you modify the command sequence accordingly in your existing load scripts and unload scripts for pool cluster resources.
Novell Linux Volume Manager (NLVM) supports OES 11 SP1 file systems running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. For information about NLVM commands and usage, see the OES 11 SP1: NLVM Reference.
In addition to bug fixes, the following changes and enhancements were made in the OES 11 SP1 release:
General
Sizes: The following enhancements are available for the size option:
The default multiplier for sizes was changed from M (megabytes) to G (gigabytes). If no multiplier is provided, the value is assumed to be in gigabytes. For example:
size=20 (20 gigabytes is used)
Use the T multiplier to specify sizes in terabytes (TB).
All sizes can be entered as whole numbers or with fractional parts such as 200.45G and 3.98T.
Multiple Devices: You can specify multiple devices for the following commands:
Init: You can specify multiple devices to be initialized at the same time. Each device is formatted with the same specified partitioning scheme and share state.
Share: You can specify multiple devices to be shared at the same time.
Unshare: You can specify multiple devices to be unshared at the same time.
Multiple Device and Size Instances: You can specify multiple device and size instances for the following commands. Each device entry must have a corresponding size entry.
Create Pool: You can specify multiple device and size instances to be used for a new pool.
Expand Pool: You can specify multiple device and size instances to be added to an existing pool.
Confirmation Prompt: You are automatically prompted to confirm actions for certain commands that destroy data, such as when you initialize a device or delete Linux POSIX volumes, pool moves, partitions, pools, RAIDs, RAID segments, snapshots, and NSS volumes.
No Prompt: The --no-prompt NLVM option can be used with certain commands to prevent a confirmation message from being displayed, such as when you initialize a device or delete Linux POSIX volumes, pool moves, partitions, pools, RAIDs, RAID segments, snapshots, and NSS volumes.
Linux Volumes
Create Linux Volume: The following enhancements were made for the nlvm create linux volume command:
Btrfs: Support was added for the Btrfs file system. The Btrfs file system is now available as a alternative to other supported file systems (Ext2, Ext3, Reiserfs, and XFS) when you create a Linux volume. The btrfsprogs package is required. You can use NSSMU or NLVM to manage the Btrfs volumes as you would manage other Linux data volumes. Btrfs volumes can also be configured for NCP file access and for clustering with Novell Cluster Services.
NCP option: The ncp option for the nlvm create linux volume command can be used to enable the Linux POSIX file system on the volume to be accessed with the NetWare Core Protocol (NCP).
When you enable NCP for a Linux volume, an NCP volume of the same name (using all capital letters) is created. An NCP share is created at the root of the Linux volume. For clustered LVM volumes, the NCP Virtual Server object is automatically created and the NCP mount, dismount, and status commands are added to scripts for the LVM volume group cluster resource.
List Linux Volumes: The nlvm list linux volumes command displays NCP if the Linux volume is enabled for NCP.
NSS Pools and Volumes
Create Pool: The following enhancements were made for the nlvm create pool command:
Device and Size: You can specify multiple device and size instances to be used for a new pool. Each device entry must have a corresponding size entry.
CIFS Virtual Server Name: When creating a cluster enabled NSS pool, the default CIFS virtual server name is based on the NCP virtual server name.
Expand Pool: The nlvm expand pool command allows you to specify multiple device and size instances to be added to an existing pool. Each device entry must have a corresponding size entry.
List Move: The following enhancements have been made to the nlvm list move command:
You can alternatively specify the pool name instead of the pool move name.
The display includes the names of the devices that are being used in the move with the from parameter and to parameter.
The concept of move blocks has been renamed as regions.
The complete parameter (formerly the percentage parameter) displays the number of regions moved so far and the percentage of regions moved so far.
Delete Move: The following enhancements were made for the nlvm delete move command:
You can alternatively specify the pool name instead of the pool move name.
The abort option has been deprecated.
The nlvm delete move command deletes the move request, returns the pool to its original location, and removes the new location. You can delete the move at any time while the move is in progress, even if it is pending only the nlvm complete move command to be finalized.
Rename Volume: You can use the nlvm rename volume command to rename a specified NSS volume. This option is new.
Novell Remote Manager supports OES 11 SP1 running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, the following enhancement is available:
Under Manage NCP Services, the new View Trustee Reports option opens the NCP Trustee Reports page where you can generate a trustee report for a specified NSS volume. You can display the last trustee report in the web browser, or send the report to the email addresses that you have preconfigured for Novell Remote Manager. The trustee report shows the rights settings by folder for each user or group that is a trustee on the NSS volume. For information, see Generating and Viewing NCP Trustee Reports for NSS Volumes
in the OES 11 SP1: Novell Remote Manager Administration Guide.
Novell Samba file services now run on the SLES 11 SP3 platform as part of OES 11 SP1.
Novell Storage Services in OES 11 SP1 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. In addition to bug fixes, NSS provides the following enhancements and behavior changes in the OES 11 SP1 release:
Support was added for the Btrfs file system. The Btrfs file system is now available as an alternative to other supported file systems (Ext2, Ext3, ReiserFs, and XFS) when you create a Linux volume. The btrfsprogs package is required. You can use NSSMU or NLVM to manage the Btrfs volumes as you would manage other Linux data volumes. Btrfs volumes can also be configured for NCP file access and for clustering with Novell Cluster Services. For more information, see Overview of Linux POSIX File Systems
in the OES 11 SP3: Linux POSIX Volume Administration Guide.
The NCP option for the NSSMU or nlvm create linux volume command can be used to enable the Linux POSIX file system on the volume to be accessed with the NetWare Core Protocol (NCP).
The clear option is introduced to remove the user quota, directory quota, and volume quota restriction.
The nssquota utility now supports Volume quota. You can use this utility to set, get, or clear the volume quota on NSS volumes.
For more information, see nssquota utility in the OES 11 SP1: NSS File System Administration Guide for Linux.
metamig can restore trustee information gathered by TRUSTEE.NLM. For more information, see metamig in the OES 11 SP1: NSS File System Administration Guide for Linux.
--delete command is introduced to delete the existing NSS Admin User from eDirectory.
On the NSSMU Partitions page, the Partitions list panel has been widened to accommodate long partition names. If you widen the NSSMU display screen, it widens the Partitions list panel and allows you to see the partitions' full names.
The NSS Auditing Client Logger (VLOG) Utility supports OES 11 SP1 running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2.
Novell QuickFinder has been modified to run on OES 11 SP1. There are no other changes in the OES 11 SP1 release of Novell QuickFinder.
Novell SMS supports OES 11 SP1 services and file systems running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP2. There are no other changes in the OES 11 SP1 release of SMS.
The web services and applications in Novell Open Enterprise Server (OES) 11 SP1 are Novell software and open source software that support SUSE Linux Enterprise Server (SLES) 11 Service Pack 2 (SP2).
The PHP 5.3 package is available in SLES 11 SP2.
The PHP 5.2 is still available, but is deprecated in SLES 11 SP2.