1.3 What’s New or Changed in OES 11 SP2

1.3.1 Install and Upgrade

In addition to bug fixes, the following enhancements and behavior changes are provided in OES 11 SP2:

Express Install

Beginning with OES 11 SP2, Express Install has been introduced to help you install OES 11 SP2 with minimal user intervention. For more information, see Typical and Custom OES Configuration in the OES 11 SP2: Installation Guide.

Cloning Post Install or Upgrade

Beginning with OES 11 SP2, you can clone an OES server after the installation or upgrade. For more information, see Cloning an OES Server Post OES Installation and Configuration in the OES 11 SP2: Installation Guide.

NCPFS Package Dependency Replaced with Novell Client for Linux

Beginning with OES 11 SP2, the OES dependency on the NCPFS open source package has been replaced with the Command Line Utilities for Novell Client, novell-qtgui-cli. The NCPFS package is no longer supported or bundled.

Reconfiguring iManager

If iManager is not configured or installed properly, you can use the reconfiguration scripts to reinstall it. For more information, see Re-configuring iManager in the OES 11 SP2: Installation Guide.

Interoperability with Partnering Vendors

Interoperability with some antivirus and Hierarchical Storage Management (HSM) partner products has been improved in OES 11 SP2.

1.3.2 Archive and Version Services

The Archive and Version Services in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3.

IMPORTANT:Beginning with OES 11 SP2, no further enhancements are planned for Archive and Version Services. For more information, see the Notice about certain OES services.

1.3.3 Novell AFP

The AFP service in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, OES 11 SP2 provides the following enhancements and changes for AFP:

Managing AFP Services

novafp - A new command line utility to configure, monitor, and manage the AFP service (afptcpd daemon). You can also monitor and manage the AFP service using the Manage AFP Services menu option provided in NRM. For more information, see AFP Monitoring and Management in the OES 11 SP2: Novell AFP for Linux Administration Guide.

1.3.4 Novell CIFS

The CIFS service in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, OES 11 SP2 provides the following enhancements and changes for CIFS:

Changes to the CIFS Delete Mechanism

The file and folder delete functions for the NSS file system in Novell CIFS were modified to use the POSIX APIs. This change leads to generating three new Vigil NSS auditing events, namely, OPEN, MODIFY, and CLOSE when CIFS protocol is used to delete a file or folder on an NSS file system. These are generated in addition to the DELETE event.

Enhanced Open Connections and Files Monitoring

  • The CIFS service now provides the capability to monitor open files and CIFS connections.

    You can monitor the CIFS service using the newly added command line options in the novcifs utility or the Manage CIFS Services option in NRM. For more information, see CIFS Monitoring and Management in the OES 11 SP2: Novell CIFS for Linux Administration Guide.

  • The novcifs long option for active connection count has been changed in OES11 SP2 from -C | --conn-count to -C | --Conn.

CLI Commands to View the NetBIOS Name of Servers and Change the Behavior of Exporting Volumes by Default

With the new command options introduced in novcifs, administrators can choose to export all mounted volumes as shares or export only the required volumes as shares.

novcifs --list-servers

Displays the NetBIOS name of physical and virtual CIFS servers.

novcifs --share-vols-default=SERVER_NAME --value=yes|no

Enables or disables all volumes being exported as shares by default.

For more information, see Viewing the NetBIOS Names of Servers and Changing the Behavior of Exporting Volumes by Default under novcifs(8) in the OES 11 SP2: Novell CIFS for Linux Administration Guide.

Pass-through Information Levels Capability

The Novell CIFS server now implements the pass-through information levels capability. This is a configurable option and is turned off by default. It can be enabled or disabled using the novcifs --info-level-passthru=yes|no command.

Pass-through Information Levels are used to set or to query file or folder information on the server. These Information Levels allow SMB clients to directly query Information Levels that are native to the underlying object store or file system.

User-level quota is not supported if this option is disabled.

For more information, see “Enabling or Disabling the Pass-through Information Levels Capability” under novcifs(8) in the OES 11 SP2: Novell CIFS for Linux Administration Guide.

Support for DOS Names

The CIFS Service now supports file operations using the short file name format to accommodate applications that require file names to be in the 8.3 name format, for example, ABPXPS~1.PPT.

1.3.5 Novell Cluster Services

Novell Cluster Services 2.2 supports OES 11 SP2 services and file systems running on 64-bit SUSE Linux Enterprise Server (SLES) 11 Service Pack (SP) 3. In addition to bug fixes, Novell Cluster Services provides the following enhancements and behavior changes in the OES 11 SP2 release.

Changing the Nodes or Failover Order in the Preferred Nodes List

When you change the nodes or failover order in a resource’s Preferred Nodes list, the change takes effect immediately when you click OK or Apply if the resource is running. Otherwise, it takes effect the next time the resource is brought online. Previously, the change did not occur until the cluster resource was taken offline and brought online. See Configuring Preferred Nodes and Failover Order for a Resource in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

With this new capability, changes for any resource attributes (such as the resource mode settings, preferred nodes list, and RME groups) other than the scripts take effect immediately.

Availability for prior releases: April 2013 Scheduled Maintenance for OES 11 SP1

Applying Updated Scripts for a Resource

When you modify the load, unload, and monitor scripts for a resource and click Apply or OK, the updated resource scripts can take effect in any of the following ways:

  • When an administrator takes the resource offline and then brings it online.

  • When the resource fails over to another node, if both the source and destination nodes have received the updated scripts from eDirectory.

  • When an administrator uses the cluster migrate command to load the resource on another node, if both the source and destination nodes have received the updated scripts from eDirectory.

Previously, script changes did not take effect until the resource was taken offline and then brought online.

For more information, see Applying Updated Resource Scripts by Offline/Online, Failover, or Migration in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

Availability for prior releases: April 2013 Scheduled Maintenance for OES 11 SP1

Modifying Resource Scripts Outside of iManager

You can use the /opt/novell/ncs/bin/ncs_resource_scripts.pl script to modify resource scripts without using iManager. You can add, remove, or modify the commands in the script, or retrieve its scripts to search for information from the script. You can issue the command from the command line or in a script. This capability is very useful when you need to make the same script change to multiple resources in a cluster. See ncs_resource_scripts.pl (Modifying Resource Scripts Outside of iManager in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

Monitoring the Status of the eDirectory Daemon (ndsd)

Some clustered services rely on the eDirectory daemon (ndsd) to be running and available in order to function properly. In this release, NCS provides the ability to monitor the status of the eDirectory daemon (ndsd) at the NCS level. It is disabled by default. The monitor can be set independently on each node. On a node, if the eDirectory daemon does not respond to a status request within a specified timeout period, NCS can take one of three configurable remedy actions: an ndsd restart, a graceful node restart, or a hard node restart. See Configuring NCS to Monitor the eDirectory Daemon in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

Reporting Logged Events for a Specific Time Range

You can get a report of logged events that occurred during a specified time range. The time range filter displays events that occurred during the interval of time before a specified date/time and after a specified date/time. The search includes the specified before and after values. For example, you might want to see events that occurred for a cluster resource before the date/time that a failover event was triggered and after the date/time of its previously known good state. See Viewing Events in the Cluster Event Log in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

DotOutParser Utility

The DotOutParser utility (/opt/novell/ncs/bin/dotoutparser.pl) prints summaries of failed or incomplete events that have been recorded in a specified /var/opt/novell/log/ncs/ <resource_name>.<script>.out log file. It also prints output (if any) from any commands that failed or got stuck. You can include ignored errors if desired. Line numbers allow you to easily refer the summary output to the source lines in the *.out file. You can omit the line numbers if desired. See DotOutParser Utility in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

Ability to Manage a Cluster in Case of a Faulty Master IP Address

The Clusters > My Clusters page in iManager provides the ability to manage the cluster with the IP address of a specified node (preferably the master node) if the master IP address for the Cluster object is experiencing problems. For example, a CIMOM error in iManager can prevent you from connecting to the master IP address, or an IP address conflict can prevent the Master IP Address Resource from coming online. See Viewing or Modifying the Cluster Master IP Address or Port in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

Support for VLAN on NIC Bonding

Novell Cluster Services added support for VLAN on NIC bonding. No modifications to scripts are required. You can use ethx or vlanx interfaces in any combination for nodes in a cluster.

Availability for prior releases: September 2013 Scheduled Maintenance for OES 11 SP1

Updates for the DHCP_Template

In the DHCP_Template for DHCP cluster resources, the PID file location was changed to /var/lib/dhcp/var/run/dhcpd.pid. This is the location used by DHCP since OES 11 SP1. The change applies automatically to any newly created DHCP cluster resources.

The following line in the load script for the DHCP_Template was modified to use the $MOUNT_POINT variable that is defined at the beginning of the script:

exit_on_error /opt/novell/dhcp/bin/cluster_dhcpd.sh -m $MOUNT_POINT

For information about configuring DHCP cluster resources, see Configuring DHCP with Novell Cluster Services for the Linux File System in the OES 11 SP3: Novell DNS/DHCP Services for Linux Administration Guide.

Availability for prior releases: The PID path change is available in the May 2013 Scheduled Maintenance for OES 11 SP1.

SLP Refresh Interval for Cluster Resource Virtual NCP Servers

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 SP2: Novell Cluster Services for Linux Administration Guide.

Availability for prior releases: May 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

Enforcing Name Restrictions for NCP-Enabled LVM Volumes

For NCP-enabled LVM volumes, the NSSMU utility and nlvm create linux volume command have been modified to enforce the NCP length restriction of 14 characters, and to use uppercase letters for the name in the Novell Cluster Services cluster resource scripts for a shared LVM volume. Previously, a new LVM volume cluster resource would go comatose immediately after creation if the name specified with the NCP_VOLUME parameter in the script was more than 14 characters or if it included lowercase letters. See Creating an LVM Volume Group Cluster Resource with NSSMU and Creating an LVM Volume Group Cluster Resource with NLVM Commands in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

Availability for prior releases: November 2012 Scheduled Maintenance for OES 11 SP1

Unsharing a Device without Stopping NCS

NSS management tools have been modified so that it is not necessary to stop NCS from running in order to disable the Shareable for Clustering setting for a device. The device should not contribute space to an SBD partition or to a shared pool or a cluster-enabled pool that is used in any cluster resource. This change is consistent with how unsharing a device works on OES 2 SP3 and earlier. See Stopping Novell Cluster Services in the OES 11 SP2: Novell Cluster Services for Linux Administration Guide.

Availability for prior releases: September 2013 Scheduled Maintenance for OES 11 SP1

Linux Multipath I/O Changes in SLES 11 SP3

The Linux Device Mapper - Multipath software deprecated some attributes and modified some default settings for attributes in the /etc/multipath.conf file in SUSE Linux Enterprise Server 11 SP3. After upgrading to SLES 11 SP3, the multipathd daemon might not work with your existing multipath configuration file. Ensure that you verify your /etc/multipath.conf file before you start the multipathd daemon after an upgrade to OES 11 SP2. For information about the latest attributes and default settings, see the multipath.conf(5) man page after you install or upgrade the server.

Key changes to the /etc/multipath.conf file:

  • udev_dir

    The udev_dir attribute is deprecated. After you upgrade to SLES 11 SP3, you must remove or comment out the following line from the defaults section of your /etc/multipath.conf file:

    udev_dir /dev
  • getuid_callout

    In the defaults section of the /etc/multipath.conf file, the getuid_callout attribute is deprecated and replaced by the uid_attribute attribute. This is a udev attribute that provides a unique path identifier. The default value is ID_SERIAL.

    After you upgrade to SLES 11 SP3, modify the attributes in the defaults section of your /etc/multipath.conf file as follows:

    • Remove or comment out the following line from the defaults section:

        getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
    • Add the following line to the defaults section:

        uid_attribute "ID_SERIAL"
  • path_selector

    In the defaults section of the /etc/multipath.conf file, the default value for the path_selector attribute was changed from "round-robin 0" to "service-time 0". The service-time option chooses the path for the next bunch of I/O based on the amount of outstanding I/O to the path and its relative throughput.

    After you upgrade to SLES 11 SP3, you can modify the attribute value in the defaults section of your /etc/multipath.conf file to use the recommended default:

      path_selector "service-time 0"
  • user_friendly_names

    The user_friendly_names attribute can be configured in the devices section and in the multipaths section.

  • max_fds

    The default setting for the max_fds attribute was changed to max. This allows the multipath daemon to open as many file descriptors as the system allows when it is monitoring paths.

    After you upgrade to SLES 11 SP3, you can modify the attribute value in your /etc/multipath.conf file:

    max_fds "max"

These key changes are shown in the following defaults section for the /etc/multipath.conf file. This example comments out the old settings and adds the new or revised settings:

defaults {
  verbosity                 2
  # udev_dir is deprecated in SLES 11 SP3
  # udev_dir               /dev
  polling_interval          10
  # path_selector default value is service-time in SLES 11 SP3
  # path_selector          "round-robin 0"
  path_selector            "service-time 0"
  path_grouping_policy     "failover"
  # getuid_callout is deprecated in SLES 11 SP3 and replaced with uid_attribute
  # getuid_callout          "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
  # uid_attribute is new in SLES 11 SP3
  uid_attribute             "ID_SERIAL"
  prio                      "const"
  prio_args                 ""
  features                  "0"
  path_checker              "directio"
  alias_prefix              "mpath"
  # rr_min_io was deprecated in SLES 11 SP2
  # rr_min_io                100
  # rr_min_io_rq is new in SLES 11 SP2
  rr_min_io_rq               1
  # max_fds default is max in SLES 11 SP3
  # max_fds                  8124
  max_fds                    "max"
  rr_weight                  "uniform"
  queue_without_daemon       "yes"
  flush_on_last_del          "no"
  user_friendly_names        "no"
  fast_io_fail_tmo           5
  bindings_file              "/etc/multipath/bindings"
  wwids_file                 "/etc/multipath/wwids"
  log_checker_err            "always"
  retain_attached_hw_handler "no"
  detect_prio                "no"
  failback                   "manual"
  no_path_retry              "fail"
  }

For information about the requirements, configuration, and management of multipath I/O, see Managing Multipath I/O for Devices in the SUSE Linux Enterprise Server 11 SP3 Storage Administration Guide.

1.3.6 Distributed File Services

Novell Distributed File Services in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, OES 11 SP2 provides the following enhancements and changes for DFS:

Setting the [Public] Trustee for a Distributed File Services Junction in iManager

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 SP2: Novell Distributed File Services Administration Guide for Linux.

1.3.7 Dynamic Storage Technology

Dynamic Storage Technology supports OES 11 SP2 file systems running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, the following enhancements are available:

  • Directory and User Space Quotas Management for DST Volumes: DST provides a unified quota management system that allows you to manage your disk space usage policy for DST shadow volume pairs. The ncpcon quotas command allows you add, modify, or delete directory quotas or user space quotas on the primary volume, and then easily set related quotas on the secondary volume based on those settings. The NSS file system independently enforces the quotas set on each volume.

    Previously, a unified quotas management approach across both volumes was not available for DST shadow volume pairs. See Managing Directory and User Space Quotas on DST Volumes in the OES 11 SP2: Dynamic Storage Technology Administration Guide.

  • ShadowFS: The Load ShadowFS (enable only if using Samba) label has been modified to Load ShadowFS (Enable only to give LUM-enabled users merged-view access via Samba or Linux file access protocols). The change was made for clarity; there is no change in functionality.

    Availability for prior releases: May 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

1.3.8 Domain Services for Windows

Domain Services for Windows in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3.

IMPORTANT:To use the DSfW features introduced in the OES 11 SP2 release, you must upgrade all domain controllers in the DSfW domain to OES 11 SP2.

In addition to bug fixes, Domain Services for Windows provides the following enhancements in the OES 11 SP2 release:

Configuring DSfW Server as a WINS Server

Duplicate workstation names in a domain lead to several issues such as slow user logins. Configuring a DSfW server as a WINS server helps to prevent having two workstations with the same name in a domain. For more information, see “Configuring DSfW Server as a WINS Server” in the OES 11 SP2: Domain Services for Windows Administration Guide.

Sites and Subnets

The sites and subnets feature enables you to configure multiple sites and distribute domain controllers over different geographical locations. When a client tries to log in to a domain, the request goes to the nearest available domain controller, thus ensuring faster domain login. For more information, see “Configuring Sites and Subnets” in the OES 11 SP2: Domain Services for Windows Administration Guide.

Mac Client Support

Beginning with OES 11 SP2, DSfW supports the OS X 10.8 and OS X 10.9 clients. This support enables you to join a Mac client to a DSfW domain, log in to the domain using DSfW credentials, and access NSS shares. For more information, see “Using Mac Client” in the OES 11 SP2: Domain Services for Windows Administration Guide.

SASL NTLMSSP Bind Support

DSfW now includes NTLM support for LDAP authentication. If Kerberos is down or a legacy third-party application is limited only to NTLM authentication, the NTLM support for LDAP authentication goes into effect. This NTLMSSP support is layered over the SASL GSS-SPNEGO mechanism. For more information, see “Support for SASL NTLMSSP Bind in LDAP” in the OES 11 SP2: Domain Services for Windows Administration Guide.

Novell Client Support

DSfW now enables co-existence of Novell Client with DSfW. Users can now authenticate to a DSfW server using Novell Client. You can now join a workstation pre-installed with Novell Client to a DSfW domain without affecting the DSfW communication.

With Novell Client support, Windows operations such as domain login, password change, GPO policy, content redirection, roaming profile, folder redirection, and advanced login parameters will work.

This feature also enables you to leverage Novell Client features such as login scripts, LDAP contextless login, login with profile, and automated login. For more information about Novell Client features, see the Novell Client 2 SP3 for Windows Administration Guide.

Windows 8 Client Support

Beginning with OES 11 SP2, DSfW supports Windows 8 as a client workstation.

Windows 2012 Support

Beginning with OES 11 SP2, DSfW supports Windows 2012 as a member server.

DSfW Install

DSfW install has been modified to not install NSS by default. This is to ensure that the DSfW server is used only as a domain controller with no other services installed by default. Novell recommends that you not install other services such as file, print, or iManager on the same server as DSfW.

Script to Address NTP-Signed Requests

NTP-signed requests from Windows clients can now be addressed by using the cross_partition_ntp_setup.pl script. Execute this script only if /var/lib/ or /var/opt/ directory hierarchies are in different partitions. For more information, see "DSfW Fails to Set Up Signed NTP for Clients to Trust" in the OES 11 SP2: Domain Services for Windows Administration Guide.

1.3.9 DNS and DHCP

The DNS and DHCP services in OES 11 SP2 have been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, DNS and DHCP services provide the following enhancements and behavior changes in the OES 11 SP2 release:

Updates for the DHCP_Template

In the DHCP_Template for DHCP cluster resources, the PID file location was changed to /var/lib/dhcp/var/run/dhcpd.pid. This is the location used by DHCP since OES 11 SP1. The change applies automatically to any newly created DHCP cluster resources.

The following line in the load script for the DHCP_Template was modified to use the $MOUNT_POINT variable that is defined at the beginning of the script:

exit_on_error /opt/novell/dhcp/bin/cluster_dhcpd.sh -m $MOUNT_POINT

For information about configuring DHCP cluster resources, see “Configuring DHCP with Novell Cluster Services for the Linux File System” in the OES 11 SP2: Novell DNS/DHCP Services for Linux Administration Guide.

Deleting Dynamic Leases

Java Console now enables you to delete dynamic leases. For more information, see "Deleting Dynamic Leases" in the OES 11 SP2: Novell DNS/DHCP Services for Linux Administration Guide

The DHCP Server Maintenance Utility Command

The DHCP server maintenance utility command now offers the -es option. For more information, see “DHCP Server Maintenance Utility” in the OES 11 SP2: Novell DNS/DHCP Services for Linux Administration Guide.

1.3.10 NetIQ eDirectory

In OES 11 SP2, eDirectory 8.8.8 is included with IPv4 support only. For more information about eDirectory, see the eDirectory Documentation web site.

Novell eDirectory has been rebranded to NetIQ eDirectory beginning with eDirectory 8.8.8. The eDirectory entitlement to OES customers remains the same as before.

1.3.11 Novell iFolder

Novell iFolder in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. There are no other changes in the OES 11 SP2 release of Novell iFolder.

1.3.12 Novell iPrint

Novell iPrint supports OES 11 SP2 services and file systems running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. iPrint provides the following enhancements and behavior changes in the OES 11 SP2 release:

iPrint Windows Client

The iPrint Client has been upgraded to version 5.94 and is available for Windows XP/Vista/Win 7/Win 8. You can download iPrint Client 5.94 from the OES 11 SP2 welcome page or from the iPrint Printer List web page. You can download the latest version of the iPrint Client from the iPrint Client for Windows XP/Vista/Win 7/Win 8 download site.

iPrint Macintosh Client

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).

Direct Print Accounting for iPrint Macintosh Client

You can now perform accounting operations for iPrint Direct Printers on the iPrint Mac Client 5.74.

1.3.13 Novell FTP

Novell FTP in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. There are no other changes in the OES 11 SP2 release of Novell FTP.

1.3.14 Novell Linux Volume Manager

Novell Linux Volume Manager (NLVM) supports OES 11 SP2 file systems running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. For information about NLVM commands and usage, see the OES 11 SP2: NLVM Reference.

In addition to bug fixes, the following changes and enhancements were made to NLVM in the OES 11 SP2 release:

General

  • Novell Type Partitions: NetWare type partitions are now referred to as Novell type partitions in guides, help, and error messages.

  • NLVM options: The following enhancements were made to NLVM Options:

    • NLVM options can appear in any order in the command after nlvm. Previously, the NLVM options had to follow immediately after nlvm.

    • The --terse option can be used with nlvm list commands to display the output in a format for parsing. Values are labeled in the format ParameterName=value. Information about a storage object is output in a single line. If the target object contains storage objects (such as partitions on a device or segments in a software RAID), subsequent lines contain information about each of its member objects.

  • Common options: The common options more and all were added for use with the following nlvm list commands to provide additional details beyond the standard output. You can use them with or without the --terse NLVM option.

    nlvm [-t] list devices [exclude] [more|all]
    nlvm [-t] list linux volumes [more|all]
    nlvm [-t] list moves [more|all]
    nlvm [-t] list partitions [device] [mask] [more|all]
    nlvm [-t] list pools [exclude] [more|all]
    nlvm [-t] list snaps [more|all]
    nlvm [-t] list volumes [more|all]

    See Common Options.

  • Viewing Error Code Messages: The NSS utility now provides an /err switch that can be used from the command prompt. You can use this option to view an error message if a failed NLVM command line operation provides an error code without a corresponding message.

    nss /err=<error_code_number>

    For information about error codes, see NLVM Error Codes.

    Availability for prior releases: November 2012 Scheduled Maintenance for OES 11 SP1

Devices

  • Unsharing a device: The nlvm unshare <device_name> command allows you to disable the Shareable for Clustering state for a device without stopping Novell Cluster Services on the node. The command fails if the device contributes space to an SBD partition, or to a shared pool or a cluster-enabled pool that is used in any cluster resource. Previously, it was necessary to temporarily stop Novell Cluster Services in order to unshare a device after you disabled clustering for a pool.

Partitions

  • Creating a partition: The type=<partition_type> option in the nlvm create partition command added support for partition type 1ac for snap partitions.

Linux Volumes

  • Creating a Linux volume: The following enhancements and changes were made to the nlvm create linux volume command:

    • Devices option: The device=<device_name> option was modified to allow you to alternatively specify a shared device with no data partitions or an uninitialized device for a clustered LVM volume. Previously, you could specify only an unshared initialized device.

    • Partition option: The part=<partition_name> option allows you to specify an existing partition as the location for a non-clustered Linux volume. It can be used instead of the device and size options.

    • Size: The minimum size for a Linux volume was increased from 1 MB to 8 MB. This change is consistent with the minimum size allowed in NSSMU.

    • NCP volume ID for clustered LVM volumes: The volid=<ncp_volume_id> option can be used in combination with the shared and ncp options to specify an NCP volume ID for an NCP-enabled clustered LVM volume. If the volid option is not used, an ID is automatically assigned by Novell Cluster Services when the resource is created. This allows you to assign an NCP volume ID that is unique across all nodes in a cluster, and across all nodes in every peer cluster in a Business Continuity Cluster.

    • Enforcing name restrictions for NCP-enabled LVM volumes: For NCP-enabled LVM volumes, the nlvm create linux volume command has been modified to enforce the NCP length restriction of 14 characters, and to use uppercase letters for the name in the Novell Cluster Services cluster resource scripts for a cluster-enabled LVM volume. Previously, a new LVM volume cluster resource would go comatose immediately after creation if the name specified with the NCP_VOLUME parameter in the script was more than 14 characters, or if it included lowercase letters.

      Availability for prior releases: November 2012 Scheduled Maintenance for OES 11 SP1

    • Linux POSIX Volumes Are Not Supported on NSS Software RAIDs: Linux POSIX file systems should not be created on NSS software RAIDs. NLVM commands have been modified to block NSS software RAIDs from being used as a device when you create a Linux POSIX volume.

      Availability for prior releases: September 2012 Scheduled Maintenance for OES 11 and OES 11 SP1

  • Listing details for a Linux volume: The nlvm list linux volume <lx_volume_name> command displays detailed information for a specified Linux volume.

  • Mounting a Linux volume: The nlvm linux mount <lx_volume_name> command allows you to mount non-LVM and LVM volumes in Linux using the mount parameters stored in the /etc/fstab file. You can optionally specify the mount options. If the Linux volume is NCP-enabled, it also automatically mounts the volume for NCP, and NCP assigns it a volume ID.

  • Unmounting a Linux volume: The nlvm linux unmount <lx_volume_name> command allows you to unmount non-LVM and LVM volumes in Linux. If the Linux volume is NCP-enabled, it also automatically dismounts the volume for NCP before it dismounts it in Linux.

NSS Pools and Volumes

  • Creating a volume: The volid=<ncp_volume_id> option in the nlvm create volume command can be used in combination with a clustered NSS pool to assign an NCP volume ID for a clustered NSS volume. If the volid option is not used, an ID is automatically assigned by Novell Cluster Services when the resource is created. This allows you to assign an NCP volume ID that is unique across all nodes in a cluster, and across all nodes in every peer cluster in a Business Continuity Cluster.

  • Listing attributes for an NSS volume: The nlvm list volumes command displays attribute information for NSS volumes when you use the more or all option.

  • Logging NCP and NSS volume dismounts: NCP Server has been modified to automatically log dismounts of NSS volumes and NCP volumes.

    Availability for prior releases: January 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

  • Pausing a pool move: The nlvm move command uses NSS software RAID mirroring underneath to copy the data to the target location. If server performance is too slow during a move, you can temporarily pause the mirroring with the nlvm pause move command. While the move is paused, the pool move status is reported as Not Enabled.

  • Resuming a pool move: If you have paused a pool move, you can resume the mirroring with the nlvm resume move command. The pool move continues from where it was paused.

  • Unmounting a pool: The nlvm unmount <poolname> command has been modified to additionally remove the Device Mapper object for the pool, the link to the Device Mapper object, and the mount point for the pool. This allows you to gracefully log out of the server from an iSCSI device that contains a pool.

    See Logging Out of an iSCSI Device that Contains an NSS Pool.

    Availability for prior releases: January 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

NSS Pool Snapshots

  • Creating a snapshot: The following enhancement and change were made for the nlvm create snap command:

    • Partition option: The part=<snap_partition> option allows you to specify an existing snap partition as the target location for an NSS pool snapshot. It can be used instead of the device and size options.

    • Size: The minimum snapshot size was increased from 1 MB to 50 MB. This change is consistent with the minimum size allowed in NSSMU.

NSS Software RAIDs

  • Creating an NSS software RAID: The following enhancements and changes were made to the nlvm create raid command:

    • Mirroring an Existing Partition: The following options have been modified:

      • Name option: The name option is mandatory except when you mirror an existing SBD partition. If you specify a name (which should be the cluster name), the RAID1 is given that name. If the name is not specified, the RAID1 name defaults to the SBD partition’s name.

      • Type option: The type option is optional when you mirror an existing NSS or SBD partition. It uses the type of the existing partition.

      Availability for prior releases: November 2012 Scheduled Maintenance for OES 11 and OES 11 SP1

    • Mirroring MSDOS Devices: The command has been modified to transparently accommodate the metadata size differences required by GPT and MSDOS partitioned devices. When mirroring a pool that consumes an entire MSDOS partitioned disk, you can use an MSDOS or GPT partitioned device of the same size. Previously, the GPT device had to be at least 4 MB larger than the MSDOS partitioned device.

      Availability for prior releases: November 2012 Scheduled Maintenance for OES 11 and OES 11 SP1

  • Renaming an NSS software RAID: The nlvm rename raid command is new. Use this command to rename a specified NSS software RAID device.

    Availability for prior releases: September 2012 Scheduled Maintenance for OES 11 and OES 11 SP1

1.3.15 Linux User Management

Linux User Management in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, Linux User Management provides the following enhancement and behavior change in the OES 11 SP2 release:

Changes to the LUM Configuration

The LUM configuration now includes two new parameters: dont-deny-pamservice and non-posix-members. For more information, see “Editing the nam.conf File”in the OES 11 SP2: Novell Linux User Management Administration Guide.

Adding External LDAP Servers

LUM now enables you to add external LDAP servers during LUM configuration. For more information, see “Setting Up Linux Computers to Use eDirectory Authentication” in the OES 11 SP2: Novell Linux User Management Administration Guide.

1.3.16 Migration

The Migration Tool in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, the Migration Tool provides the following enhancements and behavior changes in the OES 11 SP2 release.

Enhanced View of Migration Progress

The progress of the file system migration and sync now captures the total number of files and folders, and the size of the data to be migrated, along with migration start and end time. It also displays the total number of errors encountered during migration or sync, along with a link to view the logs.

For more information, see Service Information in the OES 11 SP3: Migration Tool Administration Guide.

Enhanced View of Migration Logs

The logs of all services are displayed in a single Migration Log window. You can select a service and use the search functionality to filter logs for specific types of error messages and keywords.

For more information, see View Logs in the OES 11 SP3: Migration Tool Administration Guide.

1.3.17 NetWare Core Protocol (NCP)

NCP in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, OES 11 SP2 provides the following enhancements and changes for NCP:

Changes to the NCP Delete Mechanism

The file and folder delete functions for the NSS file system in NCP were modified to use the POSIX APIs. This change leads to generating three new Vigil NSS auditing events, namely, OPEN, MODIFY, and CLOSE when NCP is used to delete a file or folder on an NSS file system. These are generated in addition to the DELETE event.

Path Visibility is Updated Immediately When a Folder or File is Deleted

NCP Server has been modified to immediately update the path visibility when a folder or file is deleted, if the logged in or mapped user had trustee rights assigned on it. The deleted file or folder and its parent path are no longer displayed unless the user has rights set at a higher level in the directory tree. In previous releases, the parent path remains visible until the NCP Server is restarted.

Command Options to Clear All NCP Server Connections

Two new command options have been added to manage NCP server connections: connections clearALL and connections clearALL except <connection_number>. These parameters help the NCP server clear all user connections that are open. You can optionally specify connection numbers that you do not want to close in the exception list. NCP server exempts those connections from closing. Specify multiple connection numbers by separating them with commas. For more information, see Managing NCP Server Connections in the OES 11 SP2: NCP Server for Linux Administration Guide.

Command Options to Update UID Number for non-LUM Users

UID_UPDATE_ENABLED

Controls the maintenance thread to update UIDs.

UID_UPDATE_PERIOD

Sets the frequency in hours. This option is applicable only if UID_UPDATE_ENABLED is set to 1.

For more information, see Enabling or Disabling UID Updates in the in the OES 11 SP2: NCP Server for Linux Administration Guide.

NOTE:These command options are also available in OES 2 SP3 (April 2013 Patches) and OES 11 SP1 (April 2013 Patches).

NCPCON's Whitespace Support in File Path and Trustee Names

The ncpcon utility allows spaces in file path or trustee names. If the file path or trustee names contain spaces, enclose them within double or single quotes. This change affects the following commands:

rights, irm, files, create shadow_volume, remove shadow_volume, and shift.

For more information, see Commands and Utilities for NCP Server and NCP Volumes in the OES 11 SP2: NCP Server for Linux Administration Guide.

Auditing Closed User Connections and Deleted eDirectory User Entries

NCP audits the graceful and forced termination of user connections, and deleted eDirectory user entries for connections. For more information, see Auditing Closed User Connections and Deleted eDirectory User Entries in the OES 11 SP2: NCP Server for Linux Administration Guide.

1.3.18 Linux POSIX Volumes

The NLVM and NSSMU management tools support Linux POSIX volumes on OES 11 SP2 running on 64-bit SUSE Linux Enterprise Server (SLES) 11 Service Pack (SP) 3.

NSSMU

In addition to bug fixes, the following changes and enhancements were made in NSSMU for Linux POSIX volume management in the OES 11 SP2 release.

General

  • Novell Type Partitions: NetWare type partitions are now referred to as Novell type partitions in guides, help, and error messages.

Devices

  • Unsharing a device: The NSSMU Devices page allows you to disable the Shareable for Clustering state for a device without stopping Novell Cluster Services on the node. The command fails if the device contributes space to an SBD partition, or to a shared pool or a cluster-enabled pool that is used in any cluster resource. Previously, it was necessary to temporarily stop Novell Cluster Services in order to unshare a device after you disabled clustering for a pool.

Linux Volumes

  • Creating Linux Volumes:

    • Devices: The device selection was modified to allow you to alternatively select a shared device with no data partitions or an uninitialized device for a clustered LVM volume. Previously, only unshared initialized devices were available for selection.

    • Enforcing Name Restrictions for NCP Enabled LVM Volumes: For NCP-enabled LVM volumes, the NSSMU utility has been modified to enforce the NCP length restriction of 14 characters and to use uppercase letters for the name in the Novell Cluster Services cluster resource scripts for a cluster-enabled LVM volume. Previously, a new LVM volume cluster resource would go comatose immediately after creation if the name specified with the NCP_VOLUME parameter in the script was more than 14 characters, or if it included lowercase letters.

      Availability for prior releases: November 2012 Scheduled Maintenance for OES 11 SP1

    • Linux POSIX Volumes Are Not Supported on NSS Software RAIDs: Linux POSIX file systems should not be created on NSS software RAIDs. NSSMU has been modified to block NSS software RAIDs from being presented as device options when you create a Linux POSIX volume.

      Availability for prior releases: September 2012 Scheduled Maintenance for OES 11 and OES 11 SP1

  • Mounting a Linux volume: The NSSMU Linux Volumes menu option F7 allows you to mount non-LVM and LVM volumes in Linux using the mount parameters stored in the /etc/fstab file. You can optionally specify the mount options. If the Linux volume is NCP-enabled, it also automatically mounts the volume for NCP, and NCP assigns it a volume ID.

  • Unmounting a Linux volume: The NSSMU Linux Volumes menu option F7 allows you to unmount non-LVM and LVM volumes in Linux. If the Linux volume is NCP-enabled, it also automatically dismounts the volume for NCP before it dismounts it in Linux.

  • Logging NCP volume dismounts: NCP Server has been modified to automatically log dismounts of NCP-enabled volumes, including NSS volumes and NCP-enabled Linux volumes.

    Availability for prior releases: January 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

NLVM Commands

In addition to bug fixes, the following changes and enhancements were made in NLVM commands for Linux POSIX volume management in the OES 11 SP2 release. For information about NLVM commands and usage, see the OES 11 SP2: NLVM Reference.

General

  • Novell Type Partitions: NetWare type partitions are now referred to as Novell type partitions in guides, help, and error messages.

  • NLVM options: The following enhancements were made to NLVM Options:

    • NLVM options can appear in any order in the command after nlvm. Previously, the NLVM options had to follow immediately after nlvm.

    • The --terse option can be used with nlvm list commands to display the output in a format for parsing. Values are labeled in the format ParameterName=value. Information about a storage object is output in a single line. If the target object contains storage objects (such as partitions on a device or segments in a software RAID), subsequent lines contain information about each of its member objects.

  • Common options: The common options more and all were added for use with the following nlvm list commands to provide additional details beyond the standard output. You can use them with or without the --terse NLVM option.

    nlvm [-t] list devices [exclude] [more|all]
    nlvm [-t] list linux volumes [more|all]
    nlvm [-t] list moves [more|all]
    nlvm [-t] list partitions [device] [mask] [more|all]
    nlvm [-t] list pools [exclude] [more|all]
    nlvm [-t] list snaps [more|all]
    nlvm [-t] list volumes [more|all]

    See Common Options.

  • Viewing Error Code Messages: The NSS utility now provides an /err switch that can be used from the command prompt. You can use this option to view an error message if a failed NLVM command line operation provides an error code without a corresponding message.

    nss /err=<error_code_number>

    For information about error codes, see NLVM Error Codes.

    Availability for prior releases: November 2012 Scheduled Maintenance for OES 11 SP1

Devices

  • Unsharing a device: The nlvm unshare <device_name> command allows you to disable the Shareable for Clustering state for a device without stopping Novell Cluster Services on the node. The command fails if the device contributes space to an SBD partition, or to a shared pool or a cluster-enabled pool that is used in any cluster resource. Previously, it was necessary to temporarily stop Novell Cluster Services in order to unshare a device after you disabled clustering for a pool.

Partitions

  • Creating a partition: The type=<partition_type> option in the nlvm create partition command added support for partition type 1ac for snap partitions.

Linux Volumes

  • Creating a Linux volume: The following enhancements and changes were made to the nlvm create linux volume command:

    • Devices option: The device=<device_name> option was modified to allow you to alternatively specify a shared device with no data partitions or an uninitialized device for a clustered LVM volume. Previously, you could specify only an unshared initialized device.

    • Partition option: The part=<partition_name> option allows you to specify an existing partition as the location for a non-clustered Linux volume. It can be used instead of the device and size options.

    • Size: The minimum size for a Linux volume was increased from 1 MB to 8 MB. This change is consistent with the minimum size allowed in NSSMU.

    • NCP volume ID for clustered LVM volumes: The volid=<ncp_volume_id> option can be used in combination with the shared and ncp options to specify an NCP volume ID for an NCP-enabled clustered LVM volume. If the volid option is not used, an ID is automatically assigned by Novell Cluster Services when the resource is created. This allows you to assign an NCP volume ID that is unique across all nodes in a cluster, and across all nodes in every peer cluster in a Business Continuity Cluster.

    • Enforcing name restrictions for NCP-enabled LVM volumes: For NCP-enabled LVM volumes, the nlvm create linux volume command has been modified to enforce the NCP length restriction of 14 characters, and to use uppercase letters for the name in the Novell Cluster Services cluster resource scripts for a cluster-enabled LVM volume. Previously, a new LVM volume cluster resource would go comatose immediately after creation if the name specified with the NCP_VOLUME parameter in the script was more than 14 characters, or if it included lowercase letters.

      Availability for prior releases: November 2012 Scheduled Maintenance for OES 11 SP1

    • Linux POSIX Volumes Are Not Supported on NSS Software RAIDs: Linux POSIX file systems should not be created on NSS software RAIDs. NLVM commands have been modified to block NSS software RAIDs from being used as a device when you create a Linux POSIX volume.

      Availability for prior releases: September 2012 Scheduled Maintenance for OES 11 and OES 11 SP1

  • Listing details for a Linux volume: The nlvm list linux volume <lx_volume_name> command displays detailed information for a specified Linux volume.

  • Mounting a Linux volume: The nlvm linux mount <lx_volume_name> command allows you to mount non-LVM and LVM volumes in Linux using the mount parameters stored in the /etc/fstab file. You can optionally specify the mount options. If the Linux volume is NCP-enabled, it also automatically mounts the volume for NCP, and NCP assigns it a volume ID.

  • Unmounting a Linux volume: The nlvm linux unmount <lx_volume_name> command allows you to unmount non-LVM and LVM volumes in Linux. If the Linux volume is NCP-enabled, it also automatically dismounts the volume for NCP before it dismounts it in Linux.

Linux Volume Support in SLES 11 SP3

For information about Linux volume support changes in SUSE Linux Enterprise Server 11 SP3, see What’s New in SLES 11 SP3 in the SUSE Linux Enterprise Server 11 Storage Administration Guide.

1.3.19 NetStorage

NetStorage in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. There are no other changes in the OES 11 SP2 release of NetStorage.

IMPORTANT:Beginning with OES 11 SP2, no further enhancements are planned for NetStorage. For more information, see the Notice about certain OES services.

1.3.20 QuickFinder

QuickFinder in OES 11 SP2 has been modified to run on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. There are no other changes in the OES 11 SP2 release of QuickFinder.

IMPORTANT:Beginning with OES 11 SP2, no further enhancements are planned for QuickFinder. For more information, see the Notice about certain OES services.

1.3.21 Novell Remote Manager

Novell Remote Manager provides the following enhancements and changes in OES 11 SP2:

Managing AFP Services

The AFP plug-in for Novell Remote Manager allows you to manage AFP connections and open files for Novell AFP users. For an overview of the AFP plug-in, see Managing AFP Services in the OES 11 SP2: Novell Remote Manager Administration Guide.

Managing CIFS Services

The CIFS plug-in for Novell Remote Manager allows you to manage CIFS connections and open files for Novell CIFS users. For an overview of the CIFS plug-in, see Managing CIFS Services in the OES 11 SP2: Novell Remote Manager Administration Guide.

Ganglia and Nagios Health Monitoring Tools

Ganglia and Nagios open source health monitoring tools replace the Health Monitor function in Novell Remote Manager in OES 11 SP2. Unlike the Health Monitor, Ganglia and Nagios tools do not use SFCB for management communications. See Diagnosing Problems Using Ganglia and Nagios (OES 11 SP2) in the OES 11 SP2: Novell Remote Manager Administration Guide.

Ganglia and Nagios Monitoring Tools Obsolete the NRM Health Monitor

The Health Monitor function in Novell Remote Manager is obsoleted in OES 11 SP2. It is replaced by the Ganglia and Nagios open source monitoring tools, which do not use the Small Footprint CIM Broker (SFCB) for communications. For information about configuring and using Ganglia and Nagios to monitor the health of the server and services, see Diagnosing Problems Using Ganglia and Nagios in the OES 11 SP2: Novell Remote Manager Administration Guide.

For information about using the Health Monitor in OES 11 SP1 and earlier releases, see Diagnosing Problems Using Health Monitor (OES 11 SP1) in the OES 11 SP2: Novell Remote Manager Administration Guide.

Nagios Alert Notification Obsoletes HTTPSTKD Email Notification

The Novell Remote Manager email notification system is obsoleted in OES 11 SP2. For health monitoring, it is replaced by the Nagios alert notification system, which is used to send alerts from the Ganglia and Nagios health monitoring tools.

After you install or upgrade to OES 11 SP2, the Novell Remote Manager email notification system is not available. The commands mailserver and mailto are not found in the HTTPSTKD configuration file (/etc/opt/novell/httpstkd.conf) for a new install, and they are no longer supported after an upgrade.

Other functions or plug-ins that leveraged the HTTPSTKD email notification commands do not work with the Nagios alert notification system. Thus, they do not work in OES 11 SP2. For example, the NCP Server plug-in Manage NCP Services, the Send option in the Email Report column no longer works on the NCP Inventory Reports page and the NCP Trustee Reports page. This issue will be addressed in a future release.

In order to receive health monitoring alerts from Ganglia and Nagios, you must configure Nagios and its alert notification system. You must set up an email address for the nagiosadmin user. You can define other Nagios contacts. You can set up various notification methods for each Nagios contact, and assign the contacts to receive notifications for designated monitored services. For more information, see Configuring Nagios and Configuring Nagios Notification System for Contacts in the OES 11 SP2: Novell Remote Manager Administration Guide.

Support for Internet Explorer 10

Web-based access to Novell Remote Manager is supported for the Internet Explorer 10 web browser in the desktop user interface view for Windows 7 clients and Windows 8 clients.

Availability for prior releases: January 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

Support for Safari 6.0 on Mac OS X 10.8

Web-based access to Novell Remote Manager is supported for the Apple Safari 6.0 web browser on Mac OS X 10.8 clients.

Availability for prior releases: January 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

1.3.22 Novell Storage Services (NSS)

In addition to bug fixes, NSS provides the following enhancements and changes in OES 11 SP2:

  • _admin supports up to 64 concurrent requests: The re-entrance issue in the _admin for user space calls has been resolved, and it can handle up to 64 concurrent requests.

  • file.cmd Supports All NSS Namespaces and Nametypes: The file.cmd interface now works with all the NSS supported nametypes (regular, deleted file) and namespaces (DOS, UNIX, LONG, Macintosh).

  • NSS Change Owner Utility (nsschown): The nsschown utility has been introduced in OES 11 SP2 to identify the files and directories that have obsolete owners, and to list or change the files owned by existing or obsolete owners for directories or files in an NSS volume. For more information, see nsschown in the OES 11 SP3: NSS File System Administration Guide for Linux.

  • Rights to Files and Folders: Using the Users or Groups plug-in, you can add or modify rights to files and folders for a user or group on a specified volume from a Rights to Files and Folders tab. You can do this even while creating users or groups. You can also verify the explicit rights of a user or group on a given volume. For more information, see Managing Rights in the OES 11 SP3: NSS File System Administration Guide for Linux.

  • View Effective Rights: In iManager, using the Files and Folders plug-in, you can view the effective rights that a trustee has on a folder or file. For more information, see Managing Rights in the OES 11 SP3: NSS File System Administration Guide for Linux.

  • Linux Multipath I/O Changes in SLES 11 SP3: The Linux Device Mapper - Multipath software deprecated some attributes and modified some default settings for attributes in the /etc/multipath.conf file in SUSE Linux Enterprise Server 11 SP3. After upgrading to SLES 11 SP3, the multipathd daemon might not work with your existing multipath configuration file. Ensure that you verify your /etc/multipath.conf file before you start the multipathd daemon after an upgrade to OES 11 SP2. For information about the latest attributes and default settings, see the multipath.conf(5) man page after you install or upgrade the server. For more information, see Linux Multipath I/O Changes in SLES 11 SP3 in the OES 11 SP3: Novell Cluster Services for Linux Administration Guide.

  • New metamig Export Option: A new export option (-p) has been added to metamig. This option exports the metadata of all the files under a given path. For more information, see the metamig man page. For more information, see metamig in the OES 11 SP3: NSS File System Administration Guide for Linux.

1.3.23 Storage Management Services

Novell SMS supports OES 11 SP2 services and file systems running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. There are no other changes in the OES 11 SP2 release of SMS.

1.3.24 File Systems Management (Storage)

In addition to bug fixes, OES 11 SP2 provides the following enhancements and changes for file systems management:

Path Visibility Is Updated Immediately When a Folder or File Is Deleted

NCP Server has been modified to immediately update the path visibility when a folder or file is deleted, if the logged in/mapped user had trustee rights assigned on it. The deleted file or folder and its parent path are no longer displayed unless the user has rights set at a higher level in the directory tree. In previous releases, the parent path remains visible until NCP Server gets restarted.

Setting the [Public] Trustee for a Distributed File Services Junction in iManager

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 SP3: Novell Distributed File Services Administration Guide for Linux.

Availability for prior releases: May 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

Rights to Files and Folders

The Files and Folders plug-in to iManager provides a Rights to Files and Folders view that lists the directories and files where a specified user or group has been assigned explicit rights as a trustee. This reverse look-up shows the locations where rights are set; it does not list all locations where the user has access through rights granted by inheritance or [Public]. See Managing Effective Rights in the OES 11 SP2: File Systems Management Guide.

Novell Client Support for Windows 8 and Server 2012

The Novell Client 2 SP3 for Windows added support for the following:

  • Windows 8 (32-bit and 64-bit), excluding Windows 8 RT

  • Windows Server 2012 (64-bit)

Novell Client 2 SP3 for Windows documentation is available online. Documentation for earlier versions is available under Previous Releases.

Availability for prior releases: January 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

OES Client Services Support for Windows 8 and IE 10

OES client services (that is, OES-related products that support access to files stored on OES servers) added support for user access from Windows 8 clients (excluding Windows 8 RT) effective in January 2013 Scheduled Maintenance.

Domain Services for Windows (DSfW) supports Windows 8 beginning with OES 11 SP2.

Client applications are supported to run on Windows 8 clients in the desktop user interface view.

Web-based client access is supported for the Internet Explorer 10 web browser in the desktop user interface view for Windows 7 clients and Windows 8 clients.

Availability for prior releases: January 2013 Scheduled Maintenance for OES 11 and OES 11 SP1

OES Client Services Support for Windows Server 2012

OES client services added support for user access from Windows Server 2012 servers.

OES Client Services Support for Mac OS X 10.8 and Safari 6.0

OES client services added support for user access from Mac OS X Mountain Lion (version 10.8) clients with the exception of Novell iFolder.

Web-based client access is supported for the Apple Safari 6.0 web browser on Mac OS X 10.8 clients with the exception of Novell iFolder:

The Novell iFolder client does not run on Mac OS X 10.8 clients and does not support them. Novell iFolder does not support the Safari 6.0 browser.

Availability for prior releases: January 2013 Scheduled Maintenance for OES 11 and OES 11 SP1. DSfW support begins in OES 11 SP2.

1.3.25 NSS Auditing Client Logger (VLOG)

The NSS Auditing Client Logger (VLOG) Utility supports OES 11 SP2 running on 64-bit SUSE Linux Enterprise Server (SLES) 11 SP3. In addition to bug fixes, VLOG provides the following enhancements:

  • MaxFileCount: The default value for maxStreamFileCount has changed from 50 files to 4096 files.

    Availability for prior releases: July 2013 Scheduled Maintenance for OES11 and OES 11 SP1

  • Four Events Are Logged for a File or Folder Delete from an NCP or CIFS Client: The file and folder delete functions for the NSS file system in NCP Server and Novell CIFS were modified to use the POSIX APIs. When you use an NCP client or a CIFS client to delete a file or folder on an NSS file system, three new auditing events are logged in addition to the DELETE event: OPEN, MODIFY, and CLOSE.

    For OES 11 SP1 and earlier, the delete action triggers only a DELETE event.

1.3.26 Web Services

The web services and applications in Novell Open Enterprise Server (OES) 11 Support Pack 2 (SP2) are Novell software and open source software that support SUSE Linux Enterprise Server (SLES) 11 Service Pack 3 (SP3).

Upgrading from MySQL 5.0 to MySQL 5.5 Introduces a New Database Format

SUSE Linux Enterprise Server 11 SP3 introduces an upgrade of MySQL from version 5.0 to version 5.5. This upgrade involves a change of the database format. You must manually migrate your existing MySQL database to the new format before MySQL can run again. After you upgrade to MySQL 5.5, its daemon is not automatically started. We recommend that you back up the database before you migrate it to the new format.

To migrate an existing MySQL database to the version 5.5 database format:

  1. Log in to the server as the root user, then open a terminal console.

  2. At the command prompt, enter

    touch /var/lib/mysql/.force_upgrade

    This assumes a local database setup path.

    If the database is clustered with Novell Cluster Services, take the MySQL cluster resource offline on a node, manually mount the volume locally, then issue the command using the path to the location on the mounted volume. For example:

    touch /mnt/mysql/var/lib/mysql/.force_upgrade

    After the database is reformatted, dismount the volume locally.

  3. After the migration to the new database format is complete, start MySQL. At the command prompt, enter

    rcmysql restart
  4. If the database is clustered with Novell Cluster Services, bring the MySQL cluster resource online.

Upgrading from PostgreSQL 8.3 to PostgreSQL 9.1 Introduces a New Database Format

SLES 11 SP3 introduces an upgrade of PostgreSQL from version 8.3 to version 9.1. This upgrade involves a change of the database format. You must manually migrate your existing PostgreSQL database to the new format before PostgreSQL can run again. After you upgrade to PostgreSQL 9.1, its daemon is not automatically started. We recommend that you back up the database before you migrate it to the new format.

A new pg_upgrade tool is provided to migrate the PostgreSQL database to the new format. Both the 8.3 version and 9.1 version of the software are included in SLES 11 SP3 to accommodate the use of this tool. For information about how to perform a database migration using the pg_upgrade tool, see the pg_upgrade tool documentation (/usr/share/doc/packages/postgresql91/html/pgupgrade.html) on the server (requires the postgresql91-docs package).

  1. Ensure that you apply the latest patches for PostgreSQL 8.3.

    The latest patch relocates the software from its standard location to a versioned location such as /usr/lib/postgresql83/bin. Symbolic links are used to make the software available in the standard location.

  2. Install PostgreSQL 9.1 and its dependent packages. The pg_upgrade tool is found in the postgresql91-contrib package.

    The packages are installed to a versioned location such as /usr/lib/postgresql91/bin. Symbolic links are used to make the software available in the standard location instead of version 8.3.

  3. Use the pg_upgrade tool to migrate the PostgreSQL database format from version 8.3 to version 9.1.

    Unless the tool is used in link mode, the server must have enough free disk space to temporarily hold a copy of the database files. You can run the du -hs command to determine if enough space is available:

    du -hs /var/lib/pgsql/data

    This directory is the default PostgreSQL location for databases. Use the actual database path for your system.

PHP 5.3 Replaces PHP 5.2

PHP 5.3 is supported in SLES 11 SP3. The PHP 5.2 package has been removed. Both PHP 5.2 (deprecated) and PHP 5.3 were available in SLES 11 SP2.

WebSphere Application Server CE Is Removed in SLES 11 SP3

The WebSphere Application Server CE package has been removed from SLES 11 SP3. It is no longer supported.