Installing MLA License Certificates

  • 7000770
  • 27-Jun-2008
  • 26-Apr-2012

Environment

Novell NetWare 5.0
Novell NetWare 5.1
Novell NetWare 6
Novell NetWare 6.5

Situation

Installing MLA License Certificates

Resolution

For more information, see  KB 7000769     
 
Questions and Answers:

Q: How many times can I install MLA licensing?
A.MLA Licenses can be installed repeatedly throughout the tree as the licenses will not conflict with one another. Novell recommends installing an MLA license in each container that contains a Server object.

Q: Which objects are required for each server?
A. Each server MUST have an NLS Licensing Object in order to determine where to look for licensing and to provide the licensing server on each server. The object created takes the form: NLS_LSP_servername. For example, for server MYSERVER in O=NOVELL, the created NLS License object would be CN=NLS_LSP_MYSERVER.O=NOVELL. These objects can only be properly viewed with the NWadmin32.exe contained in the SYS:PUBLICWIN32 directory of a NetWare 5 server. If the NLS_LSP_<servername> object was not created during the server installation, or has been removed, it must be recreated using SETUPNLS or the "Setup Licensing" option of "Licensing Options" in NWCONFIG.

In an MLA environment, license objects are required for each tree but are optional for each server. Once installed, you should see this object:

Novell NetWare 6 Server + 650  (for a NetWare 6.5 license)

When the first NetWare server is installed into the tree, this object will be created in the same container with the first NetWare server. This object can be installed multiple times but do not need to be installed more than once. However, to speed authentication, most administrators will probably want to install licenses into the root of each partition in the tree. Once a workstation has logged in, these objects are cached in server memory thus speeding access.

Because this object is unlimited, it is not necessary to install a license for each server. In fact, you cannot install an MLA license more than once in the same container, so only the first NetWare 5 server into a container can be licensed. If an MLA license is installed to the same container more than once will get error "Can not install this license because it has already been installed into the Directory Services Tree""License_Install 5-9". This means some MLA servers may have an NLS_LSP_<servername> object without any associated license objects.

Q: Where should I install these objects?
A: As stated above, all three objects will be installed in the same container with the first NetWare 5 server into the tree. For servers installed into the tree with the option "Install without a License", only the NLS_LSP_&LT ;servername> object is created. [Note: There are several prerequisites for the creation of the NLS_LSP_<servername> object. In order for this object to be successfully created, the following conditions must exist:

+ There is a read/write replica of the partition into which the server will be installed.
+ This read/write replica must reside on a server that currently contains the NLS Licensing Service

There are scenarios in which this replica cannot be added automatically by NWCONFIG and must be added manually.

+ The server is being installed into a child partition below Root and the above two conditions have not been met already.

Q: Do I need to copy the NICI Foundation Keys to each NetWare 5 server?
A: The MLA License installation document indicates that the NICI Foundation Keys should be copied to each server. NICI is only required for SSL and related security features if implemented on the server in question. however, to prevent problems with the lack of these files if these features are installed in the future, it is a good policy to copy and rename the foundation key as specified below for each NetWare 5 installed without a license.

Q: If a Server has been assigned to a license certificate, can I delete this assignment?
A:Yes, but only in an MLA environment. Double-click the particular license object to reveal the license certificate.
Right-Click the certificate and select "Details". On the details screen that pops-up, select the "Assignments" tab. For Non-MLA licenses, the server assignment must be filled-in. For MLA licenses, specific server assignment prevents more than one server from using the license. If an assignment is listed, highlight it and delete it. Then click OK to exit the screen.

Q: Why can't I install a second server license into a container?
A: A server has been associated with the certificate preventing more than one server from using the license. You must remove the server association so that multiple servers can use the MLA license. To do this:
Double-click the particular license object to reveal the license certificate. Right-Click the certificate and select "Details". On the details screen that pops-up, select the "Assignments" tab. For Non-MLA licenses, the server assignment must be filled-in. For MLA licenses, specific server assignments prevent more than one server from using the license. If an assignment is listed, highlight it and delete it. Then click OK to exit the screen.

Q: Why can't my server find the MLA licenses at the Root of the tree?
A: The NLS_LSP_<servername> object determines how the server can search for licenses. To find this setting, right-click the NLS_LSP_<servername> object. The default setting is "Search to the root of the tree". The object can also be configured to "Search to the root of the local partition". If this second setting has been selected and the license objects are not contained in the current partition, the license search will fail. In either case, the license objects must be contained at the same or higher level (closer to Root) of the tree. A license certificate contained in a container further from root than the server object will not be found.

Q: Can I move my license objects?
A: License objects can be moved to another location as long as the associated NLS_LSP_<servername> object is moved with it to the same destination. Use SYS:PUBLICWIN32NLSMan32.exe to move license certificates. Note: You can only move the certificate, not the license container. A new license container will be
created the NLSMan32.exe. 



        

.

Additional Information

Formerly known as TID# 10013067