How to configure SMS on NetWare 5 or NetWare for Small Business 4.2?

(Last modified: 18Oct2002)

This document (10017412) is provided subject to the disclaimer at the end of this document.

goal

fact

Formerly TID 2946745

fix

This TID will detail the procedure to create the objects within NDS and configure SMS to work.

To verify that the server is at a clean state, it may be necessary to completely reconfigure the SMS objects. If this is what is needed follow the next 3 steps:

1. Login to the server with Admin rights, and change to the SYS:ETC\SMS directory.
2. There are two files within the this directory, SMDR.CFG and SBACKUP.CFG. Both of these files are text based and can be viewed with any text editor. Either delete or rename the files.
3. Go into NWAdmin (NWADMN32.EXE, or something equivalent), and look for three objects in the tree. Usually the objects will be in the container where the server object is located. If the objects are not there, look through the tree for them and delete them. The default names of the objects are:

SMS SMDR Group
<SERVER NAME> Backup Job Queue
<SERVER NAME> SMS RPC

These three objects will be configured again soon. With the files in the sys:etc\sms directory gone, and the objects in the tree deleted, the SMS configuration is as if the server were first installed and never configured yet.

Here are the 2 steps to reconfigure SMS for the server:

1. At the server console prompt type "LOAD SMDR NEW" and hit <ENTER>. If a message is presented saying, "This modules is ALREADY loaded and cannot be loaded more than once," it means that smdr.nlm must be unloaded. So, type "UNLOAD SMDR.NLM". If there are further messages about SMDR.NLM not being able to be unloaded until other nlms are unloaded, unload the other modules first and then unload smdr.nlm.

When SMDR can be loaded with the 'new' switch, a new screen will appear (SMDR Configuration Screen) and ask for some information to be entered at the server prompt. The first information needed is the default context for the SMDR group. If <ENTER> is pressed here without any data being input, the default context will be assumed. If a different place in the tree is desired, enter is appropriately as shown on the screen; i.e., "ou=servers.o=novell".

The next information asked for after this is the default SMDR context. Again, a default is given and can be accepted without any data being entered with a press of the <ENTER> key. If a different context is desired, enter the context appropriately and press <ENTER>.

Finally the SMDR configuration screen will ask for the name of the user that has managing rights to the object that will be created in the tree. An example of a user name is given. When a user name is entered, follow the example explicitly; e.g., ".CN=Admin.OU=Servers.O=Novell". After <ENTER> is pressed the password for the user will be asked for. Enter it. If the password is entered incorrectly or if any other information on the screen was entered incorrectly an error could result and message will be displayed saying:

Could not obtain configuration information/create configuration file.

If this happens, unload smdr.nlm and then "load smdr new" and try the procedure again.

The process of asking the smdr.nlm to create a new configuration file will also cause the file in the sys:etc\sms directory to be overwritten. So, it may not be necessary to delete the file in the SMS directory; however it was mentioned here so as to not leave anything out.

2. At the server console prompt type, "LOAD QMAN NEW". If a message appears at the console prompt stating that QMAN is already loaded, follow the steps outlined above to fix it; i.e., unload nlms.

After <ENTER> is pressed here, a the SMS Queue Manager Configuration Screen is presented and additional information is asked from the administrator to create the queue manager object within the NDS tree.

Follow similar procedures to step one in creating the SMS Job Queue and Job Queue Name. After the job queue name is created the name of the user who has managing rights is requested. This time, however, an example of what to enter is not given. Follow step one's suggestions for assigning a user. It is suggested that the same user be given rights to the queue object as the SMS group object.

If everything is entered correctly, the screen will disappear and a message stating the following:

Started service the job queue .CN=<SERVER NAME> Backup Job Queue.OU=Servers.O=Novell
Using transfer buffer size 65536 bytes.

The process of creating the queue object will overwrite the file in the SYS:ETC\SMS directory also (just as in the case with "SMDR NEW"). Again, the information is provided here to be as complete as possible.

This document assumes that the tape device has been installed correctly and is recognized by NetWare..

document

Document Title:	How to configure SMS on NetWare 5 or NetWare for Small Business 4.2?
Document ID:	10017412
Solution ID:	1.0.27047969.2338878
Creation Date:	27Sep1999
Modified Date:	18Oct2002
Novell Product Class:	NetWare

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.