NAAS Quick Start Guide

(Last modified: 27Feb2004)

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

goal

fact

Novell NetWare 6.0

NW6SP1

Novell Advanced Audit Service

NAAS v 1.0

NAAS is a discontinued product. The replacement product is Nsure Audit. For information on downloading, installing, and configuring Nsure Audit, please see TID 10091433.

fix

This document describes the basic installation and configuration of Novell Advanced Audit Service on a NetWare 6 file server with SP1 installed. MAKE SURE Sp1 (or the current patch for NetWare 6) has been installed on the server BEFORE configuring NAAS, as many changes have been made since the initial release of NetWare 6. This document includes troublehooting ideas as well as the required steps for configuring NAAS. You can skip the steps marked "troubleshooting" unless you have problems.

Steps for installing and configuring NAAS 1.0 (each step explained below)
A. Install NAAS
B. Activate and configure the SQL database.
C. Configure NAAS

A. INSTALL NAAS

1. NAAS will be installed by default with the installation of NetWare6. If it was deselected during server installation, it can be added later through the Java interface at the server console. Steps:
- Mount the NetWare6 cd as a volume (type CDROM at the server console).
- Load startx , click on Novell, Install, Add, and browse to the Product.ini file at the root of the NW6 cd.
- Select Novell Advanced Audit Service, and follow the prompts to install.

2. Install the latest patch available for NAAS. Go to http://support.novell.com/filefinder/ and search for naas* to find the latest. Follow the installation instructions included with the patch.

3. Install the NAAS Snapins by running SYS:\Audit\N_Snapin.exe.

4. Download the current JNET.JAR and JSSE.JAR files from the Sun Microsystems website, and copy these into the directory SYS:\PUBLIC\mgmt\ConsoleOne\1.2\ConsoleOneExt. These .jar files are needed to run NAAS reports in ConsoleOne, and can be downloaded from  http://java.sun.com/products/jsse/index-103.html

Alternatively, you can download and install the complete, current JAVA engine on the administrator workstations (the workstations that will be running ConsoleOne to administer NAAS).   This is found at the same url shown above.

5. Troubleshooting: Make sure NICI versions 1.5.7 and 2.0.2 (or later) are both installed on the workstation from which Console One will be run. These are available on the NW6 client cd, or on the download page off of WWW.Novell.com.

6. Troubleshooting:  an NDS:PKI Key Material object named NAASKMO should have been created in the same container as the NAAS server during installation. If this object was not created, you can create it manually (make one in each container where a NAAS Agent or NAAS Server will reside). When creating the KMO, assign the certificate name of NAASKMO, and take the defaults from there.

B. ACTIVATE AND CONFIGURE THE SQL DATABASE.

Use the Steps below if you are using the Pervasive SQL database engine. For Oracle, see the Oracle documentation.

Install the Pervasive SQL 2000i Service Pack 4 or later update. Before installing this update you will need to modify the SYS:\SYSTEM\BTI.CFG file. Make sure the file is not read only and then add the following lines replacing the i drive with the drive letter that is mapped to the sys: volume of the server you are going to install the patch to:

[InstallInfo]
InstallDir=i:\pvsw
SystemDir=i:\system
VersionLevel=7.90
PatchLevel=3
BuildLevel=230

1. Start the Pervasive database engine on the server by entering the following at the server console:
MGRSTART

2. Create the database that will be used by NAAS. -  Install the Pervasive Control Center on the workstation. Launch SYS:\PVSW\Clients\Win\Setup.exe     and follow the prompts. This will install the Pervasive Control Center on the workstation.

- Launch the Pervasive Control Center and create a Pervasive database for NAAS. To launch the Pervasive Control Center, click on Start, Programs, Pervasive, Pervasive Control Center. Note that the exact mouse clicks for configuring the database may vary depending on the version of the Pervasive Control Center being run.  Steps using the Pervasive.SQL Control Center Version 7.90 running on a Windows 2000 workstation:
- Right click on ·Pervasive .SQL 2000i · and register a new engine (browse to or enter the name of the file server ).
- Open the newly registered engine (it will have the name of your file server)
- Right click on Databases, and then New Database
- Create a Pervasive database called NAASADMN (this name is case sensitive and note the spelling - No I) on a volume of your choice. The database can grow quite large depending on the events you will be auditing. Be sure to select a location that has plenty of free space.
- NAASADMN will appear as an entry under ·Databases.·

- Verify that "Security" is disabled in properties of the NAASADMN database. Besides showing that security is disabled, this troubleshooting step will test the connection between the administrative workstation and the Pervasive database. You will be unable to view properties of the database unless you have an IP connection to the server.

3. Troubleshooting: If problems are suspected with Pervasive licensing, you can enable the pervasive license with these commands:

NWUCINIT ·C11 -Q sys:\pvsw\license2
NWUCUTIL ·g11

4. Troubleshooting note for servers upgraded from a prior version of NetWare:
- Make sure the file SYS:\SYSTEM\BTI.CFG is NOT marked read only.
- Make sure the file SYS:\SYSTEM\BTI.CFG contains the following section:
[Database Names]
DBNamesDirectory=SYS:SYSTEM

C. CONFIGURE NAAS

1. Using ConsoleOne, configure NAAS in the tree. Right click on a the desired container, (this must be a partition root), choose Configure NAAS, then
- Click 'Setup a NAAS Agent' and select the file server that is to be the NAAS Agent.
- Click 'Setup a NAAS Server' and select the file server that is to be the NAAS Server. This can be the same as the NAAS Agent
- Click 'Setup the NAAS database' and enter the database server's IP address, and the desired NAAS auditing password. *** The password must be 8 or less characters or the configuration will fail. ***
- Click 'Configure the NAAS Framework' and enter the name of the desired NAAS Auditor (make sure the auditor user is in the same partition being audited).

2. Troubleshooting: If you have problems creating the naas database, you can delete any database files by following the directions in the document "Cleaning up after a failed NAAS installation'' and create the Pervasive portion of the NAAS database manually with the steps above.

NAAS is now installed and configured.

To use NAAS to capture and report audit data, see Guide to Auditing with NAAS

document

Document Title:	NAAS Quick Start Guide
Document ID:	10067500
Solution ID:	NOVL68700
Creation Date:	11Jan2002
Modified Date:	27Feb2004
Novell Product Class:	Management Products 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.