Professional Documents
Culture Documents
Novell Network Management Netware 6 Instructor Guide Volume 2
Novell Network Management Netware 6 Instructor Guide Volume 2
Novell Network Management Netware 6 Instructor Guide Volume 2
Management
Novell Education w w w. n o v e l l . c o m
COURSE 3004
I N S T R U C TO R G U I D E
Vo l u m e 2
100-004813-001
Version 1
Proprietary Statement Novell, Inc. Trademarks
Copyright © 2002 Novell, Inc. All rights reserved. AppNotes, ConsoleOne, GroupWise, NDS, NDPS, NetWare, the N-Design, and
Novell are registered trademarks of Novell, Inc. in the United States and other
No part of this publication may be reproduced, photocopied, stored on a retrieval countries.
system, or transmitted without the express prior consent of the publisher. This
manual, and any portion thereof, may not be copied without the express written BorderManager, eDirectory, IPX, IPX/SPX, NCP, NetWare Core Protocol, the
permission of Novell, Inc. NetWare Logotype (teeth logo), NetWare Peripheral Architecture, NLM, Novell
Certificate Server, Novell Client, Novell Distributed Print Services, SPX,
Novell, Inc. Transaction Tracking System, TTS, and ZENworks are trademarks of Novell,
1800 South Novell Place Inc.
Provo, UT 84606-2399
Certified Novell Engineer is a service mark and CNE is a registered service mark
of Novell, Inc. in the United States and other countries.
Disclaimer
Other Trademarks
Novell, Inc. makes no representations or warranties with respect to the contents
Apple, AppleShare, and AppleTalk are registered trademarks of Apple
or use of this manual, and specifically disclaims any express or implied
Computer, Inc.
warranties of merchantability or fitness for any particular purpose.
BindView is a registered trademark of BindView Development Corporation.
Further, Novell, Inc. reserves the right to revise this publication and to make
changes in its content at any time, without obligation to notify any person or Drive Image is a trademark of PowerQuest.
entity of such revisions or changes.
Linux is a registered trademark of Linus Torvalds.
Further, Novell, Inc. makes no representations or warranties with respect to any
Macintosh is a registered trademark of Apple Computer, Inc.
NetWare software, and specifically disclaims any express or implied warranties
of merchantability or fitness for any particular purpose. NetDirector is a registered trademark of UB Networks.
Further, Novell, Inc. reserves the right to make changes to any and all parts of Netscape Navigator is a registered trademark of Netscape Communications
NetWare software at any time, without obligation to notify any person or entity Corporation.
of such changes.
OpenView is a registered trademark of Hewlett-Packard Company.
This Novell Training Manual is published solely to instruct students in the use of
Pentium is a registered trademark of Intel Corporation.
Novell networking software. Although third-party application software packages
are used in Novell training courses, this is for demonstration purposes only and PS/2 is a registered trademark and WebSphere is a trademark of International
shall not constitute an endorsement of any of these software applications. Business Machines Corporation.
Further, Novell, Inc. does not represent itself as having any particular expertise Solaris is a registered trademark of Sun Microsystems, Inc.
in these application software packages and any use by students of the same shall
Tru64 is a trademark of Digital Equipment Corporation.
be done at the students’ own risk.
UNIX is a registered trademark in the United States and other countries, licensed
exclusively through X/Open Company, Ltd.
Software Piracy Windows and Windows NT are registered trademarks of Microsoft Corporation.
Throughout the world, unauthorized duplication of software is subject to both
criminal and civil penalties.
If you know of illegal copying of software, contact your local Software
Antipiracy Hotline.
For the Hotline number for your area, access Novell’s World Wide Web page at
http://www.novell.com and look for the piracy page under “Programs.”
Or, contact Novell’s anti-piracy headquarters in the U.S. at 800-PIRATES (747-
2837) or 801-861-7101.
Trademarks
Novell, Inc. has attempted to supply trademark information about company
names, products, and services mentioned in this manual. The following list of
trademarks was derived from various sources.
Novell Network Management / Instructor Guide Contents
Contents
Course Setup
Set Up the Classroom . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup-1
Setup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup-2
Setup Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup-4
Setup Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setup-4
Introduction
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-1
Prerequisite Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-1
Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-2
Relationship to Other Courses in the Curriculum . . . . . . . Intro-2
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-2
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-3
Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-4
Departments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-6
Company Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-7
Executive Staff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-7
Exercise Intro-1 Use ConsoleOne to
Manage Objects in the Tree . . . . . . . . . . . . . . . . . . . . . . . . . Intro-8
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Objective 1 Describe the 6-Step Network Troubleshooting Model . . . . . . 1-2
Step One: Try a Quick Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Step Two: Gather Basic Information . . . . . . . . . . . . . . . . . . . . 1-4
Step Three: Develop a Plan to Isolate the Problem . . . . . . . . . 1-5
Step Four: Execute the Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Step Five: Ensure User Satisfaction . . . . . . . . . . . . . . . . . . . . . 1-7
Step Six: Document the Solution . . . . . . . . . . . . . . . . . . . . . . . 1-7
Objective 2 Prepare for Network Problem Recurrence . . . . . . . . . . . . . . . . 1-8
Objective 3 Document Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
The Components of the Network . . . . . . . . . . . . . . . . . . . . . . . 1-9
The History of the Network . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Resources Used with the Network . . . . . . . . . . . . . . . . . . . . . 1-13
Exercise 1-1 Identify the Basic Principles of Network
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Objective 1 Identify Support Information on the Novell Web Site. . . . . . . 2-2
Identify Online Novell Support Information and Services . . . 2-3
Objective 2 Use Novell Support Links to Troubleshoot Problems . . . . . . . 2-6
Exercise 2-1 Use Novell Support Links . . . . . . . . . . . . . . . . . . . 2-7
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Objective 1 Use the Novell Client to Manage and Troubleshoot User
Connectivity Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
How to Access the Novell Client Software and Options . . . . . 3-4
Common Novell Client Options Used to
Manage and Troubleshoot Connectivity . . . . . . . . . . . . . . . . . 3-5
Objective 2 Identify Client Access Guidelines and
Components for NetWare Networks . . . . . . . . . . . . . . . . . . . 3-17
Guidelines for Providing Client Access . . . . . . . . . . . . . . . . . 3-17
Components of Client Access . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Objective 1 Identify NetWare 6 TCP/IP Components. . . . . . . . . . . . . . . . . 4-2
Dynamic Host Configuration Protocol (DHCP) . . . . . . . . . . . 4-3
Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . 4-3
Domain Name System (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Dynamic DNS (DDNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Service Location Protocol (SLP) . . . . . . . . . . . . . . . . . . . . . . . 4-5
TCP/IP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Objective 2 Identify How DHCP Services Work . . . . . . . . . . . . . . . . . . . . 4-6
Client Addressing on a TCP/IP Network . . . . . . . . . . . . . . . . . 4-6
What DHCP Is . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
How DHCP Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
How NetWare 6 Implements DHCP . . . . . . . . . . . . . . . . . . . 4-10
Objective 3 Configure DHCP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
DHCP Configuration Essentials . . . . . . . . . . . . . . . . . . . . . . 4-13
DHCP Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Exercise 4-1 Configure NetWare 6 to use DHCP Services . . . 4-16
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Objective 1 Identify NetWare 6 Server Management Utilities . . . . . . . . . . 5-2
Objective 2 Use NetWare Remote Manager . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Remote Manager System Requirements . . . . . . . . . . . . . . . . . 5-3
How to Access Remote Manager . . . . . . . . . . . . . . . . . . . . . . . 5-4
The Basic Functions Available in Remote Manager . . . . . . . . 5-5
Exercise 5-1 Explore Remote Manager
Administration Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Objective 3 Identify Adjustable NetWare 6 Resources . . . . . . . . . . . . . . . 5-12
How NetWare 6 Self-Tunes . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
NetWare 6 Adjustable Resources . . . . . . . . . . . . . . . . . . . . . 5-14
Objective 4 Manage and Optimize LAN Communications . . . . . . . . . . . . 5-16
Packet Receive Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Service Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Exercise 5-2 Manage and Optimize LAN
Communication Using Remote Manager . . . . . . . . . . . . . . . . . 5-19
Objective 5 Manage and Optimize the Disk and
Traditional File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Volume Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Volume Block Suballocation . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
File Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Exercise 5-3 Manage and Optimize Disk and
File Systems Using Remote Manager. . . . . . . . . . . . . . . . . . . . 5-25
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Internal Security Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
External Security Measures Using a Firewall . . . . . . . . . . . . . 6-3
Objective 1 Describe Public Key Cryptography . . . . . . . . . . . . . . . . . . . . . 6-9
The Components of Public Key Cryptography . . . . . . . . . . . . 6-9
How to Acquire Certificates . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Objective 2 Identify How Public Key Cryptography Works. . . . . . . . . . . 6-18
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Encryption and Decryption . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20
Exercise 6-1 Test Your Understanding. . . . . . . . . . . . . . . . . . . 6-22
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Objective 1 Define eDirectory Replication and Synchronization . . . . . . . . 7-1
Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Why You Should Partition and Replicate Your Tree . . . . . . . 7-7
Replica Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Synchronizing eDirectory Changes . . . . . . . . . . . . . . . . . . . . . 7-9
Understand Partition and Replication Rules . . . . . . . . . . . . . 7-12
Exercise 7-1 Describe eDirectory Partitions and Replicas . . . . 7-16
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Objective 1 Identify What iMonitor Is and How to Use It . . . . . . . . . . . . . 8-2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
How to Access iMonitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Navigation Frame Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Assistant Frame Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
How to Customize the iMonitor Configuration . . . . . . . . . . . 8-10
Objective 2 Use iMonitor to Diagnose and Repair
eDirectory Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Agent Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Agent Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Objective 1 Prepare for Upgrading to eDirectory 8.6 . . . . . . . . . . . . . . . . . 9-1
Apply the Latest Support Packs . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Update the eDirectory Schema . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Install or Upgrade Novell Certificate Server . . . . . . . . . . . . . . 9-2
Perform an eDirectory Health Check . . . . . . . . . . . . . . . . . . . . 9-5
Exercise 9-1 Verify that eDirectory is Functioning
Properly after an Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Objective 1 Identify How Server and User Licensing Works . . . . . . . . . . 10-2
Server and User Licensing Models . . . . . . . . . . . . . . . . . . . . 10-2
UAL Coexisting with SCL . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
How the Licensing Models Differ . . . . . . . . . . . . . . . . . . . . . 10-8
License Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Objective 2 Identify Key NLS Components . . . . . . . . . . . . . . . . . . . . . . 10-10
License Service Provider (LSP) . . . . . . . . . . . . . . . . . . . . . . 10-10
NLS Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
eDirectory Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
License Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Activation Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Envelope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Unlicensed Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Objective 3 Manage License Certificates in the eDirectory Tree . . . . . . 10-19
The License Container Object . . . . . . . . . . . . . . . . . . . . . . . 10-20
The License Certificate Object . . . . . . . . . . . . . . . . . . . . . . 10-22
Objective 4 Install NLS Certificates and View NetWare Usage . . . . . . . 10-23
Guidelines for Installing License Certificates . . . . . . . . . . . 10-24
License Certificates and Envelopes . . . . . . . . . . . . . . . . . . . 10-25
How to Install License Certificates . . . . . . . . . . . . . . . . . . . 10-25
How to Use the NetWare Usage Tool . . . . . . . . . . . . . . . . . 10-27
Exercise 10-1 Install a User License and
View Network Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Objective 1 Set Up and Configure NSS . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Convert a Traditional Volume to an NSS Volume . . . . . . . . 11-2
Configure User Space Restrictions . . . . . . . . . . . . . . . . . . . . 11-6
Configure Directory Space Restrictions . . . . . . . . . . . . . . . . 11-8
Set Cache Buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Set Up File Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Enable Transaction Tracking System (TTS)
on Logical Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Exercise 11-1 Test Set Up and Configuration for
Digital Airlines Web Files on an NSS Volume . . . . . . . . . . . 11-11
Objective 2 Monitor, Manage, and Rebuild NSS Storage Space . . . . . . 11-23
View the Status of NSS Volumes . . . . . . . . . . . . . . . . . . . . 11-23
Mount or Dismount NSS Logical Volumes . . . . . . . . . . . . . 11-25
Activate or Deactivate NSS Pools and Logical Volumes . . 11-25
Delete NSS Pools and Logical Volumes . . . . . . . . . . . . . . . 11-27
Restore or Purge Deleted NSS Logical Volumes . . . . . . . . 11-27
Increase the Size of an NSS Pool . . . . . . . . . . . . . . . . . . . . . 11-30
Verify and Rebuild NSS Pools . . . . . . . . . . . . . . . . . . . . . . 11-31
Exercise 11-2 Test NSS Management Tasks
on the WEBMEDIA Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-36
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Objective 1 Set Up SMS for SBCON and NWBACK32 . . . . . . . . . . . . . 12-2
The Components of SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Data Sets and SMS Services . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
How to Set Up and Start SBCON and NWBACK32 . . . . . . 12-9
SMS Log and Error Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
Exercise 12-1 Set Up SMS to Use SBCON and
NWBACK32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
Objective 2 Back Up Data with SBCON and NWBACK32 . . . . . . . . . . 12-25
How to Back Up Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
How to Verify Backed Up Data . . . . . . . . . . . . . . . . . . . . . . 12-31
Guidelines for Backing Up Data with SMS Services . . . . . 12-33
Exercise 12-2 Back Up Directory, Volume, and
eDirectory Data for Your Digital Airlines Office. . . . . . . . . . 12-39
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Objective 1 Identify the Purpose of Novell Web Services . . . . . . . . . . . . 13-2
The Purpose of Each Novell Web Services Component . . . . 13-2
How Novell Web Service Components Support
Novell Net Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Objective 2 Install, Configure, and Manage Enterprise Web Server . . . . 13-5
How to Install Enterprise Web Server . . . . . . . . . . . . . . . . . . 13-6
The Role of Web Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
How to Access Web Manager . . . . . . . . . . . . . . . . . . . . . . . . 13-8
How to Configure Enterprise Web Server with
Web Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Exercise 13-1 Install and Configure Enterprise
Web Server to Access the Digital Airlines Web Site . . . . . . . 13-14
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Objective 1 Review NetWare 6 Operating System Requirements . . . . . . 14-2
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Required eDirectory Rights . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Objective 2 Upgrade Network and Server Hardware . . . . . . . . . . . . . . . . 14-4
Objective 3 Prepare the Network for the Migration or Upgrade . . . . . . . . 14-5
Back Up eDirectory and the File System . . . . . . . . . . . . . . . . 14-5
Prepare the Network for NetWare 6 with Deployment
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Objective 4 Create an Upgrade or Migration Plan . . . . . . . . . . . . . . . . . . . 14-9
Determine a Server Strategy . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Determine an eDirectory Strategy . . . . . . . . . . . . . . . . . . . . 14-12
Create a Flow of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Assign Roles and Responsibilities . . . . . . . . . . . . . . . . . . . . 14-17
Exercise 14-1 Creating a NetWare 6 Upgrade Plan . . . . . . . . 14-18
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22
Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Objective 1 Perform an In-Place Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Objective 2 Perform a Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Prepare the Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Prepare the Source Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Prepare the Destination Server . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Run the Migration Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . 15-11
Copy Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16
Edit Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-21
Begin the eDirectory Migration . . . . . . . . . . . . . . . . . . . . . . 15-24
Finish eDirectory Migration . . . . . . . . . . . . . . . . . . . . . . . . 15-30
Objective 3 Perform Post-Migration or Post-Upgrade Tasks . . . . . . . . . 15-32
Run the Backlinker Process . . . . . . . . . . . . . . . . . . . . . . . . . 15-32
Upgrade Existing NSS Volumes . . . . . . . . . . . . . . . . . . . . . 15-33
Perform Other Post-Installation Tasks . . . . . . . . . . . . . . . . . 15-34
Exercise 15-1 Upgrade to NetWare 6 . . . . . . . . . . . . . . . . . . . 15-35
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-44
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Objective 1 Prepare Your Existing Network . . . . . . . . . . . . . . . . . . . . . . . 16-2
Objective 2 Prepare Your Server for NetWare 6 . . . . . . . . . . . . . . . . . . . . 16-3
Install and Upgrade Computer and Network Hardware . . . . 16-3
Access the Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Duration: 1 hour In this section you learn how to optimize eDirectory performance
using partitions and replicas. You also learn how eDirectory
manages changes to objects within the tree.
Objectives
1. Define eDirectory Replication and Synchronization
2. Identify Basic eDirectory Administrative Procedures
3. Design and Implement a Time Synchronization Strategy
Partitioning
Tell students that in previous Partitioning is the process of dividing the eDirectory database. You
versions of the Directory, the can divide the eDirectory database into logical units that can be
standard for partitions was no distributed among multiple servers.
more than 3500 objects.
A large eDirectory tree can contain information on millions of
objects. If you were to have a single server at a remote site, you
wouldn’t want users to cross a WAN link just to print to an NDPS
printer across the hall.
Parent
OU=Engineering OU=Marketing
Child
The name of the partition root object is also the name of the
partition.
In this example, point out that Therefore, engineering.novell is a parent partition and
Novell is a parent partition and that dev.engineering.novell and test.engineering.novell are child
Engineering is a child. partitions.
Replication
A server can contain many replicas, but the server can contain only
one replica of each partition.
Replica Ring
A replica ring (or replica list) contains a list of servers that hold a
copy or replica of a partition.
You can view a replica ring for each partition in ConsoleOne and
iMonitor. The replica ring includes
■ A list of each server containing the replica
■ The type of replica
■ The replica’s current state
Each partition root object holds a replica attribute, which lists the
servers in the replica ring. When changes are made to objects within
a partition, they are sent to other replicas of that partition using the
replica ring.
When changes are made to an object, only the changes are sent to
other replicas, not the entire object. For example, if a user changes a
phone number, only the new phone number is sent.
Replica Ring
x Changes are passed through all types of replicas, except subordinate and
filtered replicas, which share their changes but do not pass changes.
Replica Ring
No Replica
Master Read/Write Read/Write
Replica
Removed
Read-Write (R/W)
O=JKL
Subordinate
Reference (SR)
OU=Administrative
2 2
S2 S1 S4 S5 S3
3 5 6 4
Services JKL-TREE JKL-TREE JKL-TREE Production
Here’s an explanation:
1. JKL-Tree was created during the first server installation, S1. This
installation also creates the tree root partition called JKL-Tree.
2. Two additional partitions were created: the Services partition,
and the Production partition. The master replicas for these
partitions reside on server S1.
3. Server S2 is installed in the Services partition. eDirectory creates
a read/write replica of the Services partition and places it on this
server. This is the second replica of the Services partition.
4. Server S3 is installed in the Production partition. eDirectory
creates a read/write replica of the Production partition and places
it on this server. This is the second replica of the Production
partition.
5. Server S4 is installed in the JKL-Tree partition. eDirectory
creates a read/write replica of the JKL-Tree partition and places
it on this server. This is the second replica for the JKL-Tree
partition.
eDirectory also creates 2 subordinate references of the Services
and Production partitions and places them on server S4.
6. Server S5 is installed in the JKL-Tree partition. eDirectory
creates a read/write replica of the JKL-Tree partition and places
it on this server. This is the third replica for the JKL-Tree
partition.
eDirectory also creates 2 subordinate references of the Services
and Production partitions and places them on server S5.
If server S6 was installed into the JKL-Tree partition,
eDirectory would not create replicas. However, if S6 was
installed in either the Services or Production partition,
eDirectory would create a read/write replica.
ACME
AAA Corp
(End of Exercise)
Size of each replica ring The more servers on a replica ring, the longer
synchronization takes.
Speed of the WAN links The slower the speed of WAN links, the
connecting the remote longer the synchronization and access times.
replicas
CPU speed of the replica The slower the CPU speed, the longer
server synchronization takes.
Cache size for the The smaller the cache size for the database,
database the longer synchronization takes.
Rate of change for objects The more frequent the changes to objects,
in each partition the longer synchronization takes.
Loc 1 Loc 2
When you design the partitions for the upper layers of the
eDirectory tree, keep the following in mind:
■ Design your eDirectory tree in a pyramid shape, with fewer
container objects in the upper layers and more container and
leaf objects in the lower layers.
To achieve a pyramid design, always create the partitions
relatively close to the leaf objects (particularly the users).
■ Design your partition structure with fewer partitions at the top
of the tree and more partitions as you move toward the bottom.
When designing partitions for the lower layers of the tree, keep the
following in mind:
■ Use organizational divisions, departments, and workgroups, and
their associated resources, to define lower-layer partitions.
■ Whenever possible, make sure all objects in each partition are
at a single location. This ensures that updates to eDirectory can
occur on local servers.
■ Lower layers are more likely to have frequent changes so, if
possible, partition lower layers locally.
Partition Partition
Before implementing a lot of objects, make sure all tools you need
to run, manage, and repair the network can handle that number.
The partition that includes the tree root is the most important
partition of the eDirectory tree, so you must make sure you replicate
the tree root partition.
You can use a replica table to plan replica placement and map where
eDirectory will place subordinate replicas. It will also help you
remember where your replicas are located. The table helps you see
the partition view and server at the same time.
For every company, the design guidelines you use and the
requirements are different. Review all the design guidelines in this
course to determine the design guidelines and requirements for your
company.
For the JKL tree, Paul mapped the location of each replica and the
replica type on each server, as seen in the following:
Master (M)
Read-Write (R/W)
O=JKL
Subordinate
Reference (SR)
OU=Administrative
S2 S1 S4 S5 S3
After you decide where each replica will reside, create a replica
table. You put all replica information in the replica table. Do this:
1. Fill in the server and partition names.
2. Place a master replica of each partition.
3. Place read/write replicas to facilitate user access and fault
tolerance.
4. Note where subordinate references are automatically created.
The following shows a replica table for JKL:
S2 Read/Write
S3 Read/Write
Over time, you might find the need to change the way you have
partitioned eDirectory. To make changes, you must be familiar with
the following:
■ Create a Partition
■ Merge Partitions
■ Replicate a Partition
■ Move a Partition
■ Delete a Replica
Create a Partition
Merge Partitions
Replicate a Partition
Move a Partition
For example, you cannot move an organizational unit under the root
of a tree because rules for the root allow locality, country, or
organization containers, not organizational unit containers.
When you move a partition, you could choose the option to create
an Alias object for the container you’re moving. Doing so allows
users to continue to log in to the network and find objects in their
original directory location.
The alias object that is created has the same common name as the
moved container and references the new distinguished name of the
moved container.
Because the context of the object changes when you move it, users
whose name context references the moved object need to update
their NAME CONTEXT parameter so that it references the object’s
new name.
Delete a Replica
(End of Exercise)
Back Up eDirectory
b For more on Backing up eDirectory, see “Perform Backup and Restore Tasks
with NetWare 6 Backup Utilities.”
x Restore a Directory backup only when all other options for restoring the
information, such as resolving synchronization errors or recreating the
replica from a valid replica, have failed.
Volume SYS stores NetWare files that are critical for network
operations. In addition, SYS stores eDirectory files in a hidden
directory. Therefore, make sure SYS never runs out of disk space.
However, if you must bring down a server for more than a few days,
consider taking following actions:
Client Symptoms
The following client problems might indicate that replicas are not
synchronized:
■ The client prompts for a password when none exists for a user
account.
■ The client login takes significantly more time than usual.
■ Modifications made to eDirectory seem to disappear.
■ Previously assigned eDirectory rights seem to disappear.
■ Client performance is inconsistent; errors cannot always be
duplicated.
Many error codes display only a few digits of the hexadecimal error
code. Usually a number code is truncated to 2 digits, so it is not the
actual decimal equivalent of the hexadecimal code.
b For more on Novell error codes, see the online documentation, NetWare
Novell Error Codes at www.novell.com/documentation/lg/nwec/index.html.
5. What action should you take if you are going to take a server
down that contains only a replica of a partition?
(End of Exercise)
NTP assumes that the time it gets from an Internet time source is the
correct time. It changes its own time according to the time it
receives.
NTP uses the term stratum to indicate the accuracy of a time source.
The stratum ranges from 1 to 16: 1 is the time source itself, 2 is the
first server referencing that time source, 3 is the server referencing
stratum 2, etc.
Internet time sources are typically public domain NTP time sources
that are at stratum 1 or 2.
All NetWare 4.x or later servers are time servers of some kind. To
provide useful time stamps, time servers must have time
synchronization established on them.
Clients receive their time from any time servers, secondary time
servers receive their time from primary time servers, and primary
time servers receive their time from reference time servers.
Reference time servers receive their time from the most accurate
source possible, an NTP time source or hardware clock.
Figure 7-15
Figure 7-16
123 is the default UDP port that NTP uses to provide time
synchronization.
If you aren’t using NTP time sources, you can configure
other servers as time sources in a configured list. When
using a configured list, enter DNS names or IP addresses of
several time servers, separated by commas:
Figure 7-17
If your network has fewer than 30 servers and only 1 site, use the
single reference time synchronization implementation, as seen in the
following:
Secondary
Benefits
Considerations
Primary
Secondary
Before setting up time provider groups, you must know the network
layout. This helps you know where to place time providers.
Benefits
Considerations
LAX ATL
Primary
External
Primary
Time Source
DAL
Secondary
United States
Time Provider Group
LON
Reference
PAR FRA
Configured Primary Primary
Lists
GEN
Secondary
Europe Time
Provider Group
x Using a reference server with primary servers allows for faster time
stabilization.
2. How many primary servers should you use for every reference
server?
4. Can you use both configured lists and SLP at the same time as the
communication method? Why?
(End of Exercise)
Summary
The following is a summary of the objectives in this section.
Objectives Summary
Exercise Answers
ACME
ACME
5. What action should you take if you are going to take a server
down that contains only a replica of a partition?
Use ConsoleOne to move the replica to another server first.
2. How many primary servers should you use for every reference
server?
For every reference server, you should have at least 2 primary
servers.
4. Can you use both configured lists and SLP at the same time as
the communication method? Why?
Yes. If a particular server cannot contact a configured time
source, it then uses SLP to find an available time provider.
Duration: 3 hours In this section you learn the fundamentals of managing and
maintaining eDirectory.
Objectives
1. Identify What iMonitor Is and How to Use It
2. Use iMonitor to Diagnose and Repair eDirectory Problems
3. Repair eDirectory Using iMonitor
4. Maintain and Optimize eDirectory Using Cache Options
Introduction
eDirectory is the hub around which your entire network runs. The
successful running of eDirectory is critical for a network to
function. As a result, it is important to manage eDirectory
efficiently.
System Requirements
Figure 8-1
Navigation
Frame
Main
Content
Frame
Assistant Frame
Point out the navigation frame, the Depending on your eDirectory access rights, iMonitor provides
main content frame, and the
assistant frame in the figure. ■ Navigation Frame Tools
■ Assistant Frame Tools
The Navigation frame also contains the identity you are using to
view eDirectory and server information.
For clarity, navigation icons are divided into 2 groups: the left group
has nonfeature-related items such as login/logout, help, and home
icons; the right group has feature-related buttons.
b For more about DirXML, see Course 992: Directory and Database
Integration using DirXML.
The Assistant frame is at the left side of the page. This frame lists
additional navigational aids that help you navigate data in the Main
Content frame. The Assistant frame provides the following links:
■ Agent Synchronization. Use to view the number and types of
replicas you have and the length of time since they were
synchronized.
You can also view the number of errors for each replica type. If
there is only one replica or partition to view, the heading is
“Partition Synchronization Status.”
Figure 8-2
For example, iMonitor does not require the user to establish a public
identity. By using a browser to access an instance of iMonitor, you
can see whatever public is configured to see in your eDirectory
environment.
You use the following iMonitor links to identify problems with your
system:
■ Agent Health
■ Agent Configuration
■ Agent Synchronization
■ Trace Configuration
Agent Health
Figure 8-3
From the initial Agent Health dialog, you can obtain information
regarding the following:
■ Health Check: Agent
■ Health Check: Partition
■ Health Check: Ring
Figure 8-4
Figure 8-5
From the Health Check: Partition section, you can select Replica
Synchronization to display the replica status for each replica in the
ring.
The results field is a summary and status of the ring and replica
checks. For fault tolerance, you should replicate partitions to 3
servers.
When you have fewer than 3 replicas, the results button displays
yellow, indicating that there might be a potential problem with the
partition or replication.
For example, if the max send delta is greater than 4 hours, or if there
are fewer than 3 readable replicas, a warning is displayed under
Results.
x The state of the replica is server-based. This means that the state of a
server’s replica can be different on different servers.
Replica States
New Replica This is the state a replica is put into when it begins
the operation of adding itself to the replica list.
The server receiving the new replica establishes
communication with the server holding the master
replica. The new replica is assigned a replica
timestamp and is set to a state of New Replica.
Dying Replica When you remove a replica, the replica being deleted
is designated as Dying.
Agent Configuration
From the Agent Configuration page you can control and configure
the DS agent.
Figure 8-6
Agent Synchronization
Figure 8-7
■ Maximum Ring Delta. Lists the amount of data that might not
be successfully synchronized to all replicas in the ring.
For example, if a user changes their login script within the past
30 minutes, and the maximum ring delta has a 45-minute
allocation, the user's log in might not be successfully
synchronized.
They might receive their previous login script if they log in
before the allocation timeframe.
If Unknown is listed, the transitive synchronized vector is
inconsistent.
The maximum ring delta cannot be calculated because of a
problem, such as replica/partition operations in progress.
■ Replica's Perishable Data Delta. Lists the amount of data on
the partition that has not been replicated yet and which would
be lost if the server went down immediately.
Trace Configuration
Define TRACE as how eDirectory This is a server-centric feature; in other words, this feature is only
gets synchronized in real time. available on the local server where iMonitor is running. If you need
to access this feature on another server, you must switch to the
iMonitor running on that server.
For this reason, you must first enter your username and password so
your credentials can be verified before you can access information
on this page.
Figure 8-8
DS Trace Options
Trace Line prefixes are displayed The trace line prefixes let you choose which pieces of data are
when you preform a trace. Tell added to the beginning of any trace line. All trace line prefixes are
students you will point out the selected by default.
prefixes in a few minutes.
Prefixes include
■ Time Stamp. Shows the time of day the trace line was
generated.
■ Thread ID. Shows which eDirectory agent thread generated the
trace line.
■ Option Tag. Shows the tag string that identifies the trace
option that generated the event on each line output by trace.
Trace History
Selecting the trace detail icon opens the trace data generated for the
specified item.
The trace data pages are linked so that any distinguished name is
linked to the object's Browse page, error codes are linked to error
information pages, addresses are linked to the Agent Information
page, and schema names are linked to the Schema page.
The information you see depends on the trace options you select.
When the trace feature is enabled, you see a trace file in the History
table listed as Current. Selecting the current trace file detail icon
takes you to the current trace data being generated (called the Live
Trace page).
■ Submit. Lets you submit changes to trace options and trace line
prefixes. If DS Trace is off, click Submit to turn it on. If DS
Trace is on, click Submit to submit changes to the current trace.
■ Trace On/Off. Let you turn Trace on or off. The button
changes based on the current DS Trace state.
Clicking the button turns DS Trace off and vice versa. When DS
Trace is off, clicking the Trace On button is equivalent to
selecting Submit.
Perform a Trace
Figure 8-9
Point out the time stamp, the You can select any link to provide details regarding the selected
thread ID, and the option tag at the item.
beginning of each line of
information in the trace. In the previous figure, an error was generated. By selecting that
link, the Errors Index appears, enabling you to identify possible
Remind students that these are causes and solutions for the error.
the Trace Line Prefixes discussed
From this dialog, you can also update the contents displayed on
earlier.
your screen by configuring the refresh options.
5. Close the Live trace dialog by selecting Trace Configuration.
6. From the Assistant Frame, select the Trace Triggers link.
The following dialog appears:
Figure 8-10
Trace Triggers
This shows the Trace flags that must be set to display the specified
DS agent information in DS Trace.
For this reason, you must first log in so your credentials can be
verified to access information on this page.
Figure 8-11
The options on this page are determined by the selections you make
prior to accessing this page.
For example, if you browse a Partition object and select Repair, the
Replica Repair option is shown.
Repair Parameters
When you run Repair available files are listed under Download on
the Assistant frame.
x This action is irreversible. When you select this option, the old DIB set is
purged from the file system.
Figure 8-12
Obituaries are defined on the next ■ Report Move Obits. Use to remove the Obituary attribute from
page. objects in the database.
Obituaries are attributes applied to an object. There are
approximately 11 obituary types. For example, there is an
obituary for move, one for rename, and one for delete.
The Obituary attribute remains on the object until the process is
replicated.
■ Repair Network Address. Use to repair the servers network
address in replica rings and server objects in the database.
■ Repair Volume Object. Use to check all mounted volumes on
the server for valid volume objects and trustees on the volumes.
■ Repair Volume Object and Do Trustee Check. Use to check
all mounted volumes on the server for valid volume objects and
trustees on the volumes.
■ Support Options. Use when troubleshooting with Novell
Technical Support.
Schedule Report
x When you run REPAIR from a server, it affects only parts of the database
stored on the server. To fix the entire database, you must run the utility on
each server that contains the replicas of the partitions that are affected.
❑ Current Time:
❑ Time Synchronized:
7. Open the Live Trace file by selecting the View icon next to the
creation time on the file.
(End of Exercise)
In other words, the entry cache provides a map to the data in the
block cache. Although there is some redundancy between the
caches, each cache type boosts performance for different operations.
With eDirectory 8.6, you can specify a block cache limit and an entry cache
limit.
The more blocks and entries that can be cached, the better the
overall performance. The ideal is to cache the entire database in
both the entry and block caches, although this might not be possible
for extremely large trees.
You can use either setting, but you cannot use both at the same time
because they are mutually exclusive. The last method used always
replaces the prior setting.
Along with the percentage, you can set a maximum and minimum
threshold. The threshold is the number of bytes that eDirectory will
adjust to.
With the dynamically adjusting limit, you also specify the interval
length. The default is 15 seconds.
The shorter the interval, the more the memory consumption is based
on current conditions. However, shorter intervals are not necessarily
better because the recalculation requires more CPU overhead.
You can view and modify the eDirectory cache using iMonitor.
(End of Exercise)
Summary
The following is a summary of the objectives in this section.
Objective Summary
Exercise Answers
2. Select Help and record the options for verifying inbound and
outbound synchronization.
❑ DS Agent
❑ Inbound Synchronization
❑ Outbound Synchronization
Duration: 2 hours In this section you learn to perform eDirectory upgrade tasks, to do
object management tasks, and to handle schema extensions.
Objectives
1. Prepare for Upgrading to eDirectory 8.6
2. Use the eDirectory Import/Export Wizard to Manage LDIF Files
3. Redirect Resources in the Tree
4. Extend the eDirectory Schema
This program guides you through the steps to make sure the version
of eDirectory on your servers is updated to the latest revision level.
You only complete this procedure once.
The first server installed in the tree creates and stores the Security
container object and organizational CA object for the entire tree.
Both objects are created, and must remain, at the top of the tree.
b For a method to move the CA to another server, see TID 10060118 and TID
10056795.
x Make sure the first eDirectory server is the server you intend to permanently
host the organizational CA object and that the server is reliable and
accessible.
Certificate Server 1.x is not If your organizational CA is running Certificate Server 1.x, you
compatible with Certificate Server must upgrade eDirectory on the server hosting the organizational
2.0 or later. CA before upgrading eDirectory on any other servers in your tree.
If PKIS is not version 2.0 or later, you must upgrade the CA server
first before installing or upgrading NetWare 6 or eDirectory 8.6 on
any other servers in your tree.
x You might want to perform this task after hours. It locks the database.
6. Now that you’ve completed the health check, enter the following
commands to turn off DSTRACE:
SET DSTRACE=nodebug (erases DSTRACE SET
commands)
SET DSTRACE=+min (sets DSTRACE to minimum settings)
SET DSTRACE=off (turns off the DSTRACE screen)
If left running, DSTRACE uses server resources that can slow
the processing of critical procedures.
You must now perform health check tasks to assure that eDirectory
is functioning properly after the upgrade.
Do the following:
1. Display server-to-server synchronization:
a. At your server console, enter the following:
SET DSTRACE=ON
SET DSTRACE=+S
SET DSTRACE=*H
b. Press Ctrl + Esc and select Directory Services from the
Current Screens list.
If there are errors, try entering the SET DSTRACE=+S and
SET DSTRACE=*H commands again (to issue the
heartbeats one more time).
c. Check for the following message:
All Processed = YES
(End of Exercise)
Before you use the wizard, you need to understand the following:
■ LDAP Basics
■ About LDIF Files
■ About ICE
■ How to Use eDirectory Import/Export Wizard
■ How to Use the LDAP Bulk Update/Replication Protocol
LDAP Basics
b The remainder of this subsection assumes that you are familiar with LDAP.
If not, see http://www.intranetjournal.com/foundation/ldap.shtml.
Only the DN and at least one object class definition are required.
Attributes required by object classes you define for the entry must
also be defined. Other attributes and object classes are optional.
You can specify object classes and attributes in any order. The
following describes the LDIF fields shown in the previous
definition:
dn: cn=amousis,o=Users
changetype: add
uid: amousis
otherGUID:: bsaWkLmDlk+Sdcy8z17PpA==
givenName: Alex
fullName: c
Language: ENGLISH
title: Career Planning Administrator
sn: Mousis
ou: Users
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: ndsLoginProperties
objectClass: top
l: Hong Kong
cn: amousis
ACL: 2#subtree#cn=amousis,o=Users#[All Attributes
Rights]
ACL: 6#entry#cn=amousis,o=Users#loginScript
ACL: 2#entry#[Public]#messageServer
ACL: 2#entry#[Root]#groupMembership
ACL: 6#entry#cn=amousis,o=Users#printJobConfiguration
ACL: 2#entry#[Root]#networkAddress
About ICE
ICE receives data from a source handler, processes the data, and
then passes the data to a destination handler.
Figure 9-1
3. Enter the name of the LDIF file containing the data you want to
import; then select Next.
The following appears:
Figure 9-2
Figure 9-3
Figure 9-4
6. Specify the search criteria for the entries you want to export:
7. Select Next.
8. Enter the name of the LDIF file that will store the export
information; then select Next.
9. Select Finish to begin the LDIF export.
7. Select Next.
8. Select the LDAP server where the data will be migrated.
9. Select Next > Finish.
Figure 9-5
To save time you export an LDIF file, that contains all their users,
from their non-eDirectory network directory. Now you must import
that LDIF file into your tree.
Do the following:
1. Start ConsoleOne and, if necessary, authenticate as Admin.
This is not the exact export 2. Export the SLC container:
mentioned in the scenario.
a. In ConsoleOne, browse to and select DigitalAir.
Classroom constraints make it b. Select Wizards > NDS Import/Export.
difficult to follow the scenario c. In the Select Task screen, select Export LDIF File > Next.
exactly.
d. In the Select Source LDAP Server screen, select New.
These steps give students the e. In the Description field, enter SLCExport.
opportunity to perform an LDIF
export as if they were following the f. In the Server DNS Name/IP Address field, enter 192.168.x.1.
scenario. g. In the Port field, enter 636.
h. In the DER File field, browse to and select
DAx:\SYS\PUBLIC\ROOTCERT.DER.
i. In the User DN field, enter
cn=admin,ou=SLC,o=DigitalAir.
Make sure you use commas (,) instead of periods to
separate contexts. (The comma is an LDIF syntax rule.)
j. Select OK.
k. In the Select Source LDAP Server screen, select
SLCExport.
l. In the Password field, enter novell.
m. Select Next.
(End of Exercise)
Demonstrate the ConsoleOne In the left pane of ConsoleOne you see the NDS container, which
interface during this discussion. holds the eDirectory trees you are logged in to. You can cause
additional eDirectory trees to appear in the NDS container by
logging into other trees.
When you are in an eDirectory tree or context and its objects are
listed in the right pane, you can use the techniques described in this
section to locate the specific objects you want to manage.
The most common objects you move are users and printers because
employees and printers are the most commonly moved resources.
Students who have questions You are less likely to move things like servers or other objects that
about moving servers should be have a more critical functional or geographical relationship to their
referred to a more advanced place in the tree. They can be moved but, due to the number of
course. dependencies, the process for moving them is more complicated.
Demonstrate moving an object. Following are the general steps for moving an object:
1. In the ConsoleOne right pane, select the objects you want to
move.
Demonstrate both the shift-click Shift-click or Ctrl-click the objects to select more than one.
and Ctrl-click features.
2. Right-click your selection; then select Move.
3. Next to the Destination field, select the browse button; then
select the container to move the objects to; then select OK.
a 15 minutes You must give users in the PDX container access to volume USER
on your server. You choose to create an alias object to accomplish
this. Do the following:
1. Create an alias in PDX to volume DAx_USER:
a. Right-click PDX; then select New > Alias.
b. As the name the alias, enter USER_VOLUME.
c. To fill in the Object field, browse to and select
DAx_USER.SLC.DIGITALAIR.
d. Select Define Additional Properties; then select OK and
note that PDX.DIGITALAIR is a trustee of
USER_VOLUME.
This gives users in this container the same rights by
inheritance.
e. Close the Properties window by selecting Cancel.
2. Add PDX as a file system trustee to the USER_VOLUME alias:
a. Right-click USER_VOLUME; then select Properties.
b. Select Trustees > Add Trustee.
c. Change the “Look in” context to DIGITALAIR.
d. Select PDX > OK.
3. Give users in PDX the Write and Create rights to the
USER_VOLUME alias:
a. Under Access rights, select Write and Create; then select
OK.
b. From the PDX container, right-click USER_VOLUME;
then select Properties.
c. Select Effective Rights and note that PDX.DIGITALAIR
has Read, Write, Create, and File Scan rights to
USER_VOLUME.
d. Select the Browse button and change the “Look in” context
to PDX.
e. Select LMcCarter > OK and note that LMcCarter has the
same rights as PDX.
(End of Exercise)
The eDirectory schema defines the classes of objects that the tree
can contain, such as users, groups, and printers.
You can view the schema to evaluate how well the schema meets
your organization's informational needs, and then extend the
eDirectory schema to meet your organization’s needs.
The larger and more complex your organization, the more likely it is
that you need to customize the schema, but even small organizations
might have unique tracking needs.
You then use the new class to create temporary employee user
objects.
Emphasize that Schema Manager Schema Manager lets those with the Supervisor right to a tree
is not a tool for everyday use. customize the schema of that tree. Schema Manager is available
from the Tools menu in ConsoleOne.
Viewing the schema can help you determine if you need to extend
the base schema.
Do the following:
1. In ConsoleOne, select any object in the eDirectory tree whose
schema you want to view.
2. Select Tools > Schema Manager.
A list of available classes and properties appears. Double-click
a class or property to see information about it.
Create a Class
Delete a Class
You can delete unused classes that aren't part of the base schema of
your eDirectory tree. ConsoleOne only prevents you from deleting
classes that are being used in locally replicated partitions.
You might also want to consider deleting a class from the schema in
the following instances:
■ After merging trees and resolving class differences
■ Any time a class has become obsolete
Create an Attribute
You can create your own custom types of properties and add them
as optional attributes to existing object classes. However, you can’t
add mandatory attributes to existing classes.
An example of an optional attribute One way you can extend the eDirectory schema is by adding
of a User object class is a pager optional attributes to existing classes. (Mandatory attributes can
number attribute. only be defined while creating a class.) This might be necessary if
■ Your organization's information needs change
■ You are preparing to merge trees
Do the following:
1. From the ConsoleOne menu, select Tools > Schema Manager.
2. Select Classes > the class you want to modify > Add.
3. In the list on the left, double-click the properties you want to add.
If you add a property by mistake, double-click it in the list on
the right to remove it.
4. Select OK.
Objects you create of this class will have the attributes you added.
To set values for an object for the added attributes, use the Other
property page of the object.
Delete an Attribute
You can delete unused attributes that aren't part of the base schema
of your eDirectory tree. You might also want to delete an attribute
from the schema in the following instances:
■ After merging trees and resolving attribute differences
■ Any time an attribute has become obsolete
To delete an attribute,
1. From the ConsoleOne menu, select Tools > Schema Manager.
2. Select Attributes > the attribute to delete > Delete > Yes.
An example of an auxiliary class With Schema Manager, you can define your own auxiliary classes.
you can define is “users who have You can then extend individual objects with the properties defined
pagers.” in your auxiliary classes.
This lets you group a type of user Do the following:
to be easily identifiable in the tree.
1. From the ConsoleOne menu, select Tools > Schema Manager.
2. Select Classes > Create.
3. Follow the instructions in the wizard to define the auxiliary class.
Make sure to select Auxiliary Class when setting the class flags. If
you need to define custom properties to add to the auxiliary class,
cancel the wizard and define the custom properties first.
a 15 minutes Digital Airlines has started to issue guns to its pilots. You choose to
extend the eDirectory schema to create an auxiliary class to keep
track of the serial numbers of the guns issued to each pilot.
(End of Exercise)
Summary
The following is a summary of the objectives in this section.
Objective Summary
4. Extend the ■ How to View the Schema. You can use Schema
eDirectory Manager to view the schema to evaluate how well
Schema the schema meets your organization's informational
needs and to determine if you need to extend the
base schema.
■ How to Extend the Schema. You can use Schema
Manager to extend the schema of a tree by
performing the following schema tasks:
■ Create a Class
■ Delete a Class
■ Create an Attribute
■ Add an Optional Attribute to a Class
■ Delete an Attribute
■ Create an Auxiliary Class
Duration: 1 hour In this section you learn the fundamentals of Novell Licensing
Services (NLS) for NetWare 6, including how to install and manage
license certificates.
Objectives
1. Identify How Server and User Licensing Works
2. Identify Key NLS Components
3. Manage License Certificates in the eDirectory Tree
4. Install NLS Certificates and View NetWare Usage
Introduction
Novell’s licensing technology allows you to manage license units
required to comply with the licensing requirements of Novell.
x You are bound by the licensing terms and conditions of your agreement with
Novell to manually determine if usage is exceeding the licensing agreement.
Server and user licenses are separate files. They can be installed
anywhere in the eDirectory tree.
If the user doesn’t log in again for 90 days or more, the license
is released and made available to the next user who needs a
license assignment.
x User licenses can be released from the originally assigned user through
iManager. This is helpful when license units have been assigned to users
who log in infrequently and you want to release the license for use by
others who require more regular network access.
With UAL, you purchase licenses for the total number of user
objects who will log in to the network.
Server licenses are still required for NetWare 6 servers, but they
don’t correspond to connections made and services requested
by users and nonuser objects.
User licenses aren’t assigned to servers. User licenses should be
installed in or above the container containing the user objects
that will use the licenses.
You must have enough user licenses for each user who will log
in to a NetWare 6 server. This is very different from previous
licensing models used by Novell for NetWare.
For example, in NetWare 4 and NetWare 5 implementations,
you could have 200 users who work in 2 shifts each day, with
100 users working one shift and the remaining 100 users
working the other shift.
On a network made up of NetWare 4 and NetWare 5 servers,
you would need enough server connection licenses to cover
each shift’s connection needs.
So, if every user on each shift logs in, at least 100 server
connection licenses are needed for each shift.
Additional server connection licenses for each shift would be
needed if printers were being used on the network, or if users
established multiple drive mappings.
For each NetWare 4.x or 5.x server THarvey logs in to, a NetWare
SCL unit is used.
The following shows the differences between the SCL model and
the UAL model:
Point out that a UAL unit is not License released No. Yes.
released when a user logs out. when user logs out
License Types
Define license service provider. A license service provider (LSP) is licensing software that you
install and run on NetWare servers. This software is contained in the
NLSLSP.NLM program running on a NetWare 4.11 or later server.
The replica can be a master or read/write replica. You can run LSPs
on other servers without replicas as long as they can communicate
with the LSP that has a writable replica.
The server with the writable replica can make changes to eDirectory
on the other server's behalf.
NLS Clients
Define NLS client. An NLS client is software that requests licensing services from
LSPs. An NLS client runs on either a workstation or a server or on
both the workstation and the server.
eDirectory Components
NLS_LSP_servername Object
LSP objects are created in the same context as the server running
the LSP software (NLSLSP.NLM).
Define the license certificate The license certificate object is an object in eDirectory that
object. represents a license certificate. The icon for a license certificate
object looks like a single sheet of paper.
When you view the object in iManager, the object typically displays
the serial number or certificate name.
Define license container object. The license container object is a container object in eDirectory that
contains one or more license certificate objects. License container
object names include the publisher, product, and version of the
product.
Figure 10-2
Define stop. Stop is a policy in a license certificate object. The terms and
conditions of your license agreement determine which policy is in
place for the licensed product.
Define hard stop policy. ■ A hard stop policy informs users that they are out of
compliance with the terms and conditions of the license
agreement.
A hard stop prevents users from accessing a license unit. The
hard stop could result from all available license units already
being used.
Define soft stop policy. ■ A soft stop policy informs users that they are out of compliance
but allows them to continue using license units under certain
conditions.
Define no stop policy. ■ A no stop policy ignores situations in which no license units are
available. NLS keeps track of the overage by logging the
noncompliance, but does not inform or warn the user.
License Unit
Activation Key
Define activation key. The activation key is a sequence of numbers and letters. It allows
you to complete the installation of a license certificate for a product
you purchased.
Envelope
Define envelope. An envelope is an NLF file that contains one or more license
certificates. This is a convenient way of packaging multiple license
certificates to be distributed as a single file.
Policy
Notification
Define notification. A notification is a message that informs you about the licensing
service or a problem concerning your compliance with the terms
and conditions of the licensing agreement.
Unlicensed Access
Define unlicensed access. Unlicensed access is an allowance beyond the number of license
units purchased.
Unlicensed access does not grant licenses. The terms and conditions
of your license agreement specify how the product is to be used.
There are 2 property tabs for the license product container object:
■ General. The license product container object’s General tab
includes information related to
❑ The product, such as the publisher name, product name,
and product version number
❑ The installed licenses, including the number of licenses
installed, in use, and available
Use the General tab of license product container objects to
determine the licensed application version when you are
investigating licensing issues. It is very important to have the
same version of NLS running on network servers.
When you troubleshoot licensing issues, look at the properties
of each NetWare 6 license container object on your network to
determine the version of NLS running on the server.
■ Units in Use. The Units in Use tab can be very helpful when
tracking denials for license certificates.
In environments where users are limited to a single connection,
the information on this tab can help you identify who has
established a connection and used a certificate.
Usage information for each user connected to the network can
be viewed in the Units in Use window.
When users connect to the network from various workstations
and use a license, this property page helps you identify how
many connections a user has established.
In the following figure you see a single connection has been
established, using a single NetWare license.
Figure 10-3
b You can solve many NLS problems by accessing the Licensing FAQ web
page at http://www.novell.com/documentation/lg/nw6p/index.html.
The Configuration page lets you determine how the NetWare usage
tool is used on your network. To set configuration options, do the
following:
1. Log in to NetWare Remote Manager.
2. Under NetWare Usage, select Configuration.
3. Modify the settings.
4. Select Update Configuration.
For more about these settings, select the NetWare Usage page
help.
These parameters can also be set at the server console. Use the
command NLSLRUP HELP to display the commands for
setting the configuration options at the server console.
For more about these advanced settings, select the NetWare Usage
page help.
Advanced parameters can also be set at the server console. Use the
command NLSLRUP HELP to display the commands for setting the
configuration options at the server console.
a 20 minutes The new Digital Airlines employees you prepared workstations for
will start in a few days and will need access to the DAx server.
Windows Excel must be installed You need to install a license certificate to add enough user licenses
for Part IV of this exercise so for all current and new employees to access the DAx server.
students can view NetWare Usage
information. In this exercise you do the following:
■ Part I: Install License Certificates
■ Part II: Set Configuration Options
■ Part III: Set Advanced Options
■ Part IV: Access NetWare Usage Information
16. Verify your license was successfully installed; then select Done.
(End of Exercise)
Summary
The following is a summary of the objectives in this section.
Objective Summary
Objective Summary
2. Identify Key NLS You must understand how the following help you
Components maintain licensing and license units on your
network:
■ License Service Provider (LSP)
■ NLS Clients
■ eDirectory Components
■ NLS_LSP_servername object
■ License Certificate object
■ License Container object
■ The Stop policy
■ License Unit
■ Activation Key
■ Envelope
■ Policy
■ Notification
■ Unlicensed Access
Objective Summary
Duration: 4 hours In this section, you learn to set up and configure Novell Storage
Services (NSS) and implement several server file system access
components.
Objectives
1. Set Up and Configure NSS
2. Monitor, Manage, and Rebuild NSS Storage Space
3. Set Up User Access to the Server File System
Introduction
If you do not have time in class to After installing NetWare 6 and NSS on your server, you might need
complete the iFolder, NFAP, to perform additional setup and configuration tasks such as
NetDrive, and NetStorage configuring user space restrictions and resetting the cache.
exercises (11-3 through 11-6),
consider giving students the You also need to know how to monitor and manage NSS storage
choice of completing one or more space and provide remote access to NSS volumes for your users.
of the exercises.
In this section, you perform basic NSS setup, configuration, and
Exercises 11-3 through 11-6 are management tasks, and implement iFolder, Novell Native File
designed to be completed Access Pack (NFAP), NetDrive, and NetStorage for remote access.
independent of each other.
VCU copies the data from the traditional volume to an NSS logical
volume in an existing NSS storage pool. The new logical volume
keeps the original volume name with _NEW added unless you
rename the volume before converting.
Remind students that after you To convert a traditional volume to an NSS logical volume, you need
convert a traditional volume to a to know the following:
logical volume in NetWare 6, you
cannot access the logical volume ■ VCU Command Syntax
under prior versions of NetWare. ■ How to Convert a Traditional Volume With VCU
Parameters:
■ /p: Do not print directory file names.
■ /l: Do not write errors to log file (Dst_Vol:ERROR.OUT).
■ /i: Keep file COMPRESS_FILE_IMMEDIATELY_BIT.
■ /d: Delete the original volume if the copy process is successful.
(If you delete the traditional volume, the new volume retains the
name of that volume.)
Do the following:
1. Make sure you have an NSS pool to store the converted volume.
You can create a pool specifically for the converted volume, or
add the converted volume to an existing pool.
2. From the NetWare 6 server console prompt, enter VCU
traditional_volume nss_pool.
For example, to convert a traditional volume named APPS to an
NSS logical volume in a pool named POOLONE, from the
server console prompt enter the following:
VCU APPS POOLONE
Figure 11-1
Figure 11-2
Figure 11-3
Figure 11-4
Figure 11-5
6. Select Restrict Size and enter the size limit (increments of 4 KB).
7. Close the properties dialog by selecting OK.
You can change the NSS cache buffer allocation by using Monitor
(Server Parameters > Novell Storage Services) or by using the
following commands from the server console:
This sets the minimum number of cache buffers allocated for NSS
file system access. The range is 256 - 1,048,576.
The File Snapshot feature lets your backup utility (such as SBCON
or Backup Exec for NetWare) keep an original copy of all data files.
The File Snapshot feature captures the most recent closed copy of
the file. This means that if you lose data between backup cycles, you
still have a solid copy of the previously saved file on the backup
tape.
To enable the File Snapshot feature for an NSS volume, from the
server console prompt enter the following NSS command:
NSS /FileCopyOnWrite=<volName>
To enable the File Snapshot feature for all NSS volumes, enter the
following:
NSS /FileCopyOnWrite=all
NSS /NoFileCopyOnWrite
If your server stores both traditional and logical volumes, TTS is set
(by default) to work only on traditional volumes. If you want to use
it on logical volumes instead, do the following:
1. Add DISABLE TTS to the AUTOEXEC.NCF file; then restart
your server.
2. From the server console prompt, enable TTS on each logical
volume you want it on by entering the following:
NSS/TRANSACTION=volume_name.
Exercise 11-1 Test Set Up and Configuration for Digital Airlines Web Files
on an NSS Volume
You also need to restrict the space used by several directories and
users on those volumes.
Do the following:
1. From your workstation, make sure you are logged in as admin to
DAx; then start ConsoleOne.
2. In the SLC.DIGITALAIR container, right-click the DAx
object; then select Properties.
3. Select Media > Traditional Volumes; then select New.
If you don’t see the Media tab in the properties dialog, try
starting ConsoleOne from SYS:PUBLIC\MGMT
\CONSOLEONE\1.2\BIN on your NetWare server.
4. For the volume name, enter WEBFILES; then select Next.
A list of available space appears.
5. Select the unpartitioned storage space; then in the Used field
enter 200.
This sets the size of the volume to 200 MB.
6. Continue by selecting Next.
Do the following:
1. Create a WEBMEDIA NSS pool:
a. From ConsoleOne, right-click the DAx object; then select
Properties.
b. Select Media > NSS Pools; then select New.
c. For the pool name, enter WEBMEDIA; then select Next.
d. Select the unpartitioned disk space; then in the Used field,
enter 500.
e. Continue by selecting Next.
The Attribute Information dialog appears.
f. Make sure Activate on Creation is selected; then select
Finish.
g. Create the pool by selecting Yes.
The WEBMEDIA pool appears in the Pools on Server list.
h. Close the properties dialog by selecting Cancel.
2. From your NetWare 6 server console prompt, convert the
WEBFILES traditional volume by entering the following:
VCU WEBFILES WEBMEDIA
A Volume Copy Upgrade screen appears.
When the conversion is complete, you are prompted to rename
the volume.
WEBFILES is still the traditional volume; WEBFILES_NEW is
the converted NSS volume.
Because VCU doesn’t create eDirectory objects, a
DAx_WEBFILES_NEW object doesn’t exist in SLC.
Do the following:
1. Make sure the NSS attributes for restricting size are selected:
a. From ConsoleOne on the workstation, right-click the
DAx_WEBFILES volume object; then select Properties.
b. Select Attributes > NSS Attributes.
c. Make sure Directory Quotas and User Space Restrictions
are selected.
Without these options selected, you cannot use the space
restriction features of NSS.
d. Do one of the following:
❑ If you made changes to the properties, close the
properties dialog by selecting OK.
❑ If you did not make changes, close the properties
dialog by selecting Cancel.
2. Restrict the size of the FTPFILES directory to 10 MB:
a. From ConsoleOne on the workstation, double-click the
DAx_WEBFILES volume object.
b. Double-click the DAWEB folder; then right-click the
FTPFILES directory and select Properties.
c. Select Facts.
d. Select Restrict Size: then in the Limit field enter 10000 (for
10 MB).
e. Select OK.
3. Restrict the amount of storage space for Jeff McMurdie (the
Marketing Specialist) to 5 MB on the WEBFILES volume:
a. From ConsoleOne, right-click the DAx_WEBFILES
volume object; then select Properties.
b. Select Users with Space Restrictions; then select Add.
c. Browse to and display the objects in the
MARKETING.SLC.DIGITALAIR container.
d. Select JMCMURDIE; then select OK.
A User Space Restriction dialog appears.
e. In the Limits field, enter 5200 (for approximately 5 MB);
then select OK.
JMCMURDIE appears in the User Restrictions list with a
limit of a little over 5 MB.
f. Close the properties dialog by selecting OK.
4. Give Jeff McMurdie access rights to the WEBFILES volume:
a. From ConsoleOne on your workstation, right-click
DAx_WEBFILES; then select Properties.
b. Select Trustees; then select Add Trustee.
c. Browse to the MARKETING.SLC.DIGITALAIR
container and select JMCMURDIE; then select OK.
d. From the Access Rights list, make sure that Read, Write,
Create, and File Scan are selected; then select OK.
5. Map a drive to the FTPFILES directory for admin:
a. From your workstation desktop, right-click the red N in the
system tray; then select Novell Map Network Drive.
b. Select an unassigned drive letter to map; then select Browse.
(End of Exercise)
You can view and monitor the status of an NSS volume from one of
the following dialogs:
■ Server object properties dialog. This dialog provides
information such as the volume state (active/deactive,
mounted/dismounted), available storage space, and creation
date.
The information in this dialog helps you identify volumes when
performing management tasks such as activating and
deactivating a volume.
■ Volume object properties dialog. This dialog provides volume
statistics (such as disk usage, directory entries, delete file
count), NSS quota usage, and NSS statistics.
The information in this dialog helps you closely monitor the
usage and status of the NSS volume.
Do the following:
1. Start ConsoleOne.
2. Authenticate to the server object by logging in as admin user.
3. Right-click the server object and select Properties.
4. Select Media > NSS Logical Volumes.
5. Select the NSS volume you want to mount or dismount.
6. Select one of the following:
❑ Mount
❑ Dismount
The button label changes to Dismount when you mount the
NSS volume; it changes to Mount when you dismount the NSS
volume.
7. When you finish, select Close.
When you deactivate a pool, all volumes in the pool are deactivated
and dismounted. When you activate the pool, you must activate and
mount each volume individually.
If you delete an NSS pool, you cannot restore the logical volumes in
that pool. However, if you delete an NSS logical volume from an
NSS pool, you can restore it within a specified time (see “Restore or
Purge Deleted NSS Logical Volumes” on 11-27).
You must restore an NSS volume before the Purge Delay time
elapses; otherwise, the NSS volume is removed from the system and
you can no longer restore it.
The default setting for the Purge Delay time is 4 days. After this
time expires, NSS purges any deleted logical volumes.
You can change the Purge Delay time from the server console
prompt by entering the following:
NSS /LOGICALVOLUMEPURGEDELAY=delaytimeinseconds
Figure 11-6
6. Select an NSS logical volume from the list; then select one of the
following:
❑ Purge. Use to immediately purge the volumes.
❑ Prevent Purge/Allow Purge. Use to stop or allow the
volume from being purged.
❑ Salvage. Use to restore the volume.
❑ Refresh. Use to refresh and update the list of deleted
volumes.
7. (Conditional) If you select Salvage, do the following:
a. Enter a new volume name or keep the original volume name;
then select Finish.
b. Close the Deleted Logical Volumes dialog by selecting
Close.
c. Verify that the volume has been restored by selecting Media
> NSS Logical Volumes.
The volume appears as active and mounted in the list of
NSS logical volumes.
8. When you finish, close the Deleted Logical Volumes dialog by
selecting Close.
9. Close the properties dialog by selecting Close.
You can increase the size of an NSS pool by adding storage objects
(such as unpartitioned space) to the pool.
x You can lose data if you span an NSS storage pool across multiple
devices and a device or a partition goes bad.
7. Enter the amount of space you want to include from the storage
object in the Used column.
8. Add the storage space by selecting Finish.
If you select unpartitioned storage space, a message indicates
that the space will be partitioned with hotfix space and a mirror
object.
9. (Conditional) Create the partition and add the storage space to
the pool by selecting Yes.
10. Verify that the new space has been added by selecting the NSS
pool; then select Show Segments.
A Segment Information dialog appears that lists the added
storage space (segment).
11. When you finish viewing the segment information, select Close.
If you cannot activate an NSS pool, you can use the VERIFY and
REBUILD utilities to solve the problem.
You can also use VERIFY any time you want to check the health of
a pool or volume (such as after restoring a volume).
NSS keeps a journal of all file system transactions. After your file
system crashes, NSS scans the journal to ensure that all transactions
are either completed or undone.
This means that volumes do not require any repair when you mount
them again after the crash. Instead you use repair utilities called
VERIFY and REBUILD on the storage pools that contain the
logical volumes:
x When you deactivate a storage pool, all volumes in the pool deactivate
and dismount.
Figure 11-7
Figure 11-8
Figure 11-9
2. When prompted that the logical volumes in the NSS pool will be
dismounted, select Yes.
This verifies and accounts for all blocks in the system. If the
NSS logical volumes have errors, the errors are listed on the
screen.
3. After the errors are fixed, enter the following at the server
console prompt to activate the pool:
NSS /POOLACTIVE=pool_Name
4. Activate and mount each volume by entering the following at the
server console prompt:
NSS /ACTIVATE=volumename
MOUNT volumename
Do the following:
1. From your NetWare 6 server console prompt, enter VOLUMES.
The WEBFILES volume is listed as mounted.
2. From your workstation make sure you are logged in as admin to
DAx; then start ConsoleOne.
3. From ConsoleOne, browse to and right-click the DAx object and
select Properties.
4. Select Media > NSS Logical Volumes.
5. Select WEBFILES; then select Delete.
The WEBFILES volume is deleted and removed from the list of
NSS logical volumes.
13. Verify that the volume has been restored by selecting Media >
NSS Logical Volumes.
The WEBFILES volume appears as active and mounted in the
list of NSS logical volumes.
14. Close the properties dialog by selecting Cancel.
Part II: Verify the File System Integrity of the WEBMEDIA Pool
Do the following:
1. At the server console prompt, enter the following:
NSS /POOLVERIFY=WEBMEDIA.
A message appears indicating the NSS volumes on the pool will
be dismounted.
2. Dismount and verify the WEBFILES volume by selecting Yes.
After a few moments, a verification report appears.
3. View information for the pool, volume, and files by pressing the
spacebar.
4. View any errors or warnings by pressing F1.
No errors or warnings are listed for the pool, volume, and files.
5. When you finish viewing the report, exit by pressing Esc.
You might need to press Esc more than once.
6. At the server console prompt, activate and mount the
WEBFILES volume by entering the following:
NSS /ACTIVATE=WEBFILES
MOUNT WEBFILES
The WEBFILES volume is mounted successfully.
Do the following:
1. From ConsoleOne on the workstation, browse to and right-click
the DAx object; then select Properties.
2. Select Media > NSS Pools.
3. Select the WEBMEDIA pool.
The current total space for the pool is approximately 500 MB.
4. Select Increase Size.
A list of available storage objects appears.
5. Select an unpartitioned space storage object with at least 500
MB of free space.
6. Increase the pool size to 1 GB by entering 500 in the Used
column.
7. Add the storage space by selecting Finish; then select Yes.
Notice that the total storage space for the pool has increased to
1 GB.
8. Verify that the new space has been added by selecting
WEBMEDIA; then select Show Segments.
A Segment Information dialog appears that lists 2 segments
associated with the pool. Segment 1 is the latest segment added.
9. View segment information (specifically the size) by selecting 1.
10. When you finish viewing segment information, select Close.
(End of Exercise)
After iFolder is running, you can access the following to manage the
iFolder accounts:
■ The Default iFolder Web Site
■ The Server Management Console
The iFolder web site home page contains the iFolder Client Quick
Start Guide and other important information about iFolder, as
shown in the following:
Figure 11-10
You can also download the iFolder client and access iFolder files
using a browser. You can modify this page to meet your company's
needs.
Figure 11-11
Do the following:
1. From the Server Management Console, select User Accounts.
2. Select the user ID you want to remove; then select Remove.
Do the following:
1. At the Server Management Console, select User Accounts.
2. Roll your mouse pointer over the user’s ID and look at the ID that
appears in the bottom of your browser.
The ID identifies the user folder.
3. Restore this folder from the backup media to a secondary iFolder
server that the user can attach to and restore the files.
The only way to reset the pass phrase for a user in the standard
version of iFolder is to remove the user account and have the user
resynchronize data from the local iFolder directory on the
workstation.
The files stored on the local workstation are not encrypted. When
the iFolder client downloads an encrypted file from the iFolder
server, the file is decrypted by the iFolder client and then saved in
the local iFolder directory.
However, if the encrypted data on the iFolder server has not yet
been synchronized with the local directory, when you delete the user
account, any unsynchronized data is lost.
To change a pass phrase for a user, contact the user and remain in
contact during the process. Do the following:
1. Prepare for the pass phrase change by doing the following:
❑ Ask the user to log out of iFolder.
❑ Verify that the user has a relatively fast connection.
❑ Verify that all of the user’s current data is in his or her local
iFolder directory.
2. Access the Server Management Console at the workstation by
entering the following:
https://iFolder_server_ipaddress/iFolderServer/Admin
11. Verify that the user account was created by selecting User
Accounts.
a 15 minutes You have received a request from the SLC office administrative
assistant (Anita Valdez) to increase her storage space on the iFolder
server and to reset her pass phrase (she’s forgotten it).
As a result of this request and many others like it, you also decide to
decrease administration of pass phrases by setting the Remember
pass phrase option to be selected by default in the iFolder client.
Do the following:
1. Verify the current storage space allocated to AVALDEZ by
logging into the account:
a. From your workstation desktop system tray, right-click the
iFolder icon and select Login.
b. Enter the following:
❑ User ID: AVALDEZ
❑ Password: novell
❑ Server: your iFolder server IP address or DNS name
Use the following IP addresses and DNS names:
c. Select Login.
d. For the pass phrase, enter novell; then select OK.
(End of Exercise)
You can use NFAP to eliminate the need to rely on Novell client
software to access NetWare server resources and files from a
Windows, Macintosh, and Linux/UNIX platform.
With NetWare 6 and NFAP, you can use the native client of the your
workstation operating system. Access to NetWare resources is
administered through user objects in eDirectory.
NFAP uses protocols such as CIFS to make the NetWare server look
like a Windows server, a Macintosh server, or a Linux/UNIX server.
NW Client
NetWare
File protocols/open standards
b In this objective, you learn how to install and configure NFAP for Windows.
For information on setting up NFAP with the Macintosh, UNIX and Linux
operating systems, see “Novell Native Access File Protocols” at
http://www.novell.com/documentation/lg/nw6p/index.html.
11. From the server remove the NetWare 6 CD; then from the server
console prompt restart the server by entering RESTART
SERVER.
Figure 11-13
Users can now use their native access methods (such as Network
Neighborhood or My Network Places) to access network resources.
Figure 11-14
You can create simple passwords for users one at a time using
ConsoleOne, but if you want to create passwords for many network
users, use NetWare Remote Manager.
Figure 11-15
Do the following:
■ Part I: Install NFAP for Windows
■ Part II: Set Up Client Access
■ Part III: Test Native File Access for Windows
10. From the Summary window, make sure Native File Access for
Windows and Port Resolver are listed; then select Finish.
A Product Conflict message appears indicating that you have a
newer or identical version of LDAP services on your computer.
11. Continue by selecting No.
14. From the server console prompt, restart the server by entering
RESTART SERVER.
x If your password is the same for Windows as it is for CIFS access, you
are not prompted for a password and the user credentials are passed to
the NetWare CIFS server.
x If you want to test Native File Access for Windows without the Novell client
installed, remove the client by running C:\NOVELL\NETWARE
CLIENT\CLIENT32\NOVELL\ENG\WIN95\ADMIN\UNC32.
(End of Exercise)
What NetStorage Is
NetStorage gives users secure file access from any Internet location,
with nothing to download or install on the workstation. Files and
folders on a Novell network can be accessed using either a browser
or Microsoft Web Folders.
Your network and its user workstations must meet the following
requirements to support NetStorage:
■ There must be at least one NetWare 6 server in the eDirectory
tree where NetStorage will be installed.
■ Workstations must have Netscape Navigator 4.7 or later or
Internet Explorer 5.0 or later, or Microsoft Web Folders.
12. From the server, remove the NetWare 6 CD; then from the
server console prompt, restart the server by entering RESTART
SERVER.
To use NetStorage from the client, you need the date and time on
the server and on any workstation used to access NetStorage to be
reasonably close.
x If entering server_ip_address does not work, try adding the Apache web
server port number (such as http://192.168.2.1:80/NetStorage).
The default port number for the Apache web server is 80 or 443.
The NetStorage web page then displays the network files and
folders accessible to you in a page similar to the following:
Figure 11-16
Folders and files are displayed that you can manipulate as you do in
Windows Explorer. The same conventions are used to expand and
close directories and to open, move, delete, copy, and rename files.
Local files and folders are not accessible. Also, you cannot map
drives or change login scripts from within the NetStorage web page.
The directories and files in all contexts and eDirectory trees that you
specify during NetStorage installation are available.
Do the following:
■ Part I: Install and Configure NetStorage
■ Part II: Test Your Installation of NetStorage
13. From the server console prompt, restart the server by entering
RESTART SERVER.
Do the following:
1. From your workstation, use ConsoleOne to create a
CSWENSON user object:
a. Start ConsoleOne.
b. Right-click the SLC.DigitalAir container; then select New
> User.
c. Enter the following:
❑ Name: CSWENSON
❑ Surname: SWENSON
d. Select Create Home Directory; then select the browse
button.
e. Browse to and select the USERS directory in the
DAx_DATA volume; then select OK.
f. Continue by selecting OK.
g. For the password enter novell; then select Set Password.
2. From your workstation, use the Novell client to log in as
CSWENSON with a novell password.
3. Map a drive to the home directory for CSWENSON in
DAx_DATA:
a. From your workstation desktop, right-click My Network
Places and select Novell Map Network Drive.
b. Select a drive letter to map; then select Browse.
c. Select the CSWENSON directory in DATA\USERS on
DAx; then select OK.
d. Select Check to make folder appear as the top most level
and Map Search Drive; then select Map.
(End of Exercise)
FTP includes functions to log in, list directories, and copy files.
It can also convert between the ASCII and EBCDIC character
codes.
FTP operations can be performed at a command prompt or
through an FTP utility running under a graphical interface such
as Windows. FTP transfers can also be initiated from within a
web browser by entering ftp:// followed by the URL.
FTP handles binary files directly and does not add the overhead
of encoding and decoding the data.
NetWare FTP Server provides the service for transferring files
to and from NetWare volumes. FTP Server can be used to post
or retrieve files from your NetWare file server.
■ iFolder. iFolder is a Novell product that allows you to access
files from anywhere. You install the iFolder client and log in
and your files are downloaded to your workstation.
You use the iFolder protocol with NetDrive if you are
connecting to iFolder servers in a thin-client environment.
Install NetDrive
Using NetDrive
Figure 11-17
Add a Site
When you complete these steps, you create a site, but you must still
map a drive and connect to a NetWare 6 server to use NetDrive.
Figure 11-18
Figure 11-19
Copy Files
To copy files, use the DOS COPY command or cut and paste with
Explorer. To disconnect from the server, right-click the drive icon in
Explorer and select Disconnect.
Do the following:
1. From your workstation, make sure you are logged in as admin to
DAx.
2. Install NetDrive on your workstation:
a. From your workstation, insert the Novell Client CD.
b. From the Novell Client Installation window, select English;
then select Novell NetDrive Client 4.0.
c. From the Choose Setup Language dialog, select English;
then select OK.
d. From the Welcome window, select Next.
e. Accept the Software License Agreement by selecting Yes.
f. From the Choose Destination Location window, select Next.
g. Do one of the following:
❑ If a NetDrive Install Complete window appears, select
Yes I want to restart my computer now; then select
Finish and remove the Novell Client CD.
❑ If a NetDrive window appears, close the window and
close the Novell Client Installation window; then
remove the Novell Client CD and restart the
workstation.
3. After Windows 2000 restarts, add a site to NetDrive on your
workstation:
a. Log in to DAx as admin with a password of novell.
b. Select Start > Programs > NetDrive > NetDrive.
c. In the NetDrive window, select New Site.
(End of Exercise)
Summary
The following is a summary of the objectives in this section.
Objective Summary
Objective Summary
2. Monitor, Manage, After you set up and configure NSS, you might
and Rebuild NSS need to perform the following to monitor,
Storage Space
manage, and rebuild NSS storage space:
■ View the status of NSS volumes
■ Mount or dismount NSS logical volumes
■ Activate or deactivate NSS pools and logical
volumes
■ Delete NSS pools and logical volumes
■ Restore or purge deleted NSS logical volumes
■ Verify and rebuild NSS pools
Duration: 3 hours In this section, you learn to back up and restore NetWare file
systems, eDirectory, and workstation file systems using the
SMS-compliant backup utilities provided with NetWare 6.
Objectives
1. Set Up SMS for SBCON and NWBACK32
2. Back Up Data with SBCON and NWBACK32
3. Restore Data with SBCON and NWBACK32
4. Identify eDirectory Recovery Procedures
Introduction
The exercises in this section use a Novell Storage Management Services (SMS) is a collection of
tape drive emulator. software components that provides backup and restore services
independent of operating systems and hardware.
Because the emulator does not
accurately represent the length of Using an SMS-compliant backup application (such as SBCON or
time required for backing up and VERITAS Backup Exec for NetWare) with installed SMS
restoring data and cannot restore components, you can back up data from eDirectory, file systems,
data, consider using a hardware and cluster-enabled pools to backup media (such as a tape) that can
tape drive to demonstrate the
be stored on or offsite.
backup process.
If you have a hardware failure, natural catastrophe, corrupted data,
or incorrectly deleted or changed data, you can recover a previous
version of the data from the backup media.
Scenario
You install the latest service pack for NetWare 6 and notice that
your backup and restore software begins having problems.
Before setting up and using these utilities, you need to know the
following:
■ The Components of SMS
■ Data Sets and SMS Services
■ How to Set Up and Start SBCON and NWBACK32
■ SMS Log and Error Files
NetWare 6 TSA600
eDirectory TSANDS
When using an SME such as SBCON, you can configure data sets
to back up or restore specific data.
To understand how to specify these data sets, you need to know the
following:
■ Parent and Child Classifications
■ Subsets and Include and Exclude Options
Items in a data set for either a parent or child should be items that
do not frequently change.
To back up a small part of the file system structure, use the include
options of SBCON and NWBACK32 to specify the data you want.
Everything you do not specifically include is excluded.
When you select only part of the file system structure to include
(such as a volume), all directories, subdirectories, and files under
that selection are included in the backup by default.
Mary Directories
Subdirectories
Files
Thomas Directories
Subdirectories
Files
All other areas of the file system structure (such as volume HOME)
are excluded from the backup or restore. You can exclude some
subdirectories or files beneath your selection (such as the SYSTEM
directory) if necessary.
The same principle applies when you specify a directory with the
include option.
Mary Directories
Subdirectories
Files
Thomas Directories
Subdirectories
Files
All other areas of the file system structure are excluded from the
backup.
Make sure you have installed the controller and storage device
according to the hardware manufacturer’s instructions.
LIST DEVICES
To register the storage device with the system, enter the following at
the server console prompt:
x Remember that a host server is the server from which you are controlling
backup and restore of information on a target server or workstation.
After loading the controller, device drivers, and TSAs, you can load
the SMS NLMs on the host server (the server from which you are
controlling backup and restore).
To load the SMS NLMs, from the server console prompt enter
SMSSTART.
If you do not use the correct name space and name space
formats when entering paths and file names, files can't be
restored.
Whenever you back up files and directories, data files are created on
the storage media (such as a tape) that can be used to restore the
data to a server or workstation.
You might want to create individual log directories for the different
types of backup or restore session targets or different organizational
units.
The following provides information about the log and error files to
help you effectively manage backup and restore jobs:
■ Location of Log and Error Files
■ Log File Contents
■ Error File Contents
■ Access Log and Error Files Through SBCON and NWBACK32
The log and error files of a backup session are stored in a default
directory (such as SYS:SYSTEM\TSA\LOG). If you prefer, you can
create your own directory for the log and error files as long as it
resides on the host server.
The log and error files of a restore session are stored in the directory
(SYS:SYSTEM\TSA\RESTORE). You cannot modify the location
for the files.
You can access the log and error files through the SBCON main
menu (Log File Administration) or from a Windows 95, 98, 2000
or Windows NT workstation using the NWBACK32 Report menu
(Session or Error).
SBCON and NWBACK32 keep a list of all log and error files. The
list includes the following information:
■ The description you enter for the session
■ The date and time you started a backup or restore session or, in
the case of a delayed session, the time the session was
scheduled
■ The name of the target the data was backed up from
While waiting for a software patch for your normal backup and
restore utility, you decide to test SBCON as an interim backup and
restore solution.
x If you receive an error that stops the loading of the modules, (such
as a QMAN.NLM error message), reset the server at the console
prompt by entering RESET SERVER; then try entering SBSC
again (step b).
f. From the server console prompt, load the TSA for eDirectory
by entering TSANDS.
Do the following:
1. From the workstation, make sure you are logged in to DAx as
admin with a novell password.
2. Find out which local area connection to configure for the TSA:
a. Select Start > Run; then enter CMD and select OK.
If you do not select C:\, SBCON will not give you access to the
hard drive.
12. Select Registration; then register the TSA by selecting Register.
x If you receive error messages or SBCON does not load, reset the server
from the console prompt by entering RESET SERVER; then start the
exercise again.
x Although you do not use NWBACK32 in the section exercises, you can
explore the utility on your own from your workstation by double-clicking the
NWBACK32.EXE file in the SYS:SYSTEM\PUBLIC directory on your
NetWare 6 server.
(End of Exercise)
x This objective covers basic backup, verification, and restore tasks using
SBCON and NWBACK32. For more information, see “Storage Management
Services (Backup and Restore)” at http://www.novell.com/documentation/
lg/nw6p/index.html.
If you do not see the server you want on the list, the TSA might
not be loaded on the host or the target.
17. View the job queue from the main menu by selecting Job
Administration > Current Job List.
18. Do one of the following:
❑ View the details of a job by selecting the job.
❑ View the job progress by pressing Insert.
19. When the backup job is complete, press Esc until you return to
the main menu.
20. Exit SBCON by selecting Exit; then select Yes.
21. Unload the SMS modules from the server console prompt by
entering SMSSTOP.
Make sure you have met the prerequisites listed in “How to Set Up
and Start SBCON and NWBACK32” on 12-9, and then do one of
the following:
■ Verify From a Host Server Using SBCON
■ Verify From a Workstation Using NWBACK32
x As part of your backup plan, test backed up data regularly to verify the
reliability of your backup procedures and equipment. Whenever possible,
test restoring the backed up data on a server in a lab (instead of in the
production environment).
If a user object is deleted and re-created with a new ID, the user's
trustee assignments in the file system can be restored.
As long as an object with the same name on the backup media exists
in the eDirectory tree structure when the file system is restored, the
TSA can interact with eDirectory to rebuild the directory entry table
(DET) to reflect new object ID numbers.
Backing Up eDirectory
Object ID Numbers
When NetWare is backed up, the SME stores the objects' fully
distinguished names (not the objects' ID numbers) on the backup.
If an object with the same name does not exist in the eDirectory tree
structure, it is assigned a new object ID when it is restored.
A scan option allows backup of only those objects for which the
backup user has the Supervisor right.
Exercise 12-2 Back Up Directory, Volume, and eDirectory Data for Your
Digital Airlines Office
a 20 minutes After setting up and starting SBCON, you are ready to test backing
up data.
x Make sure you complete Parts I and II of Exercise 12-2 before starting this
exercise.
6. Select the tape emulator for the device and label the device media
as Test Backups:
a. Select Device/Media Name and select
EMULATOR_TAPE 1.
A list of media (the tape in the tape drive) appears with an
“unidentifiable media” label.
SBCON needs a media label for the tape before you can
back up data to it.
b. Display the media utilities by pressing Insert; then select
Change the Media Label.
c. Delete the existing data by selecting Yes.
d. For the media label, enter Test Backups and press Enter
twice; then press Esc.
7. Use Advanced Options to back up only the WEBSITE
directory:
a. Select Advanced Options; then select Subsets of What to
Back Up.
b. Select Include directories (full path); then press Insert.
c. Select LONG namespace.
d. For the data set name, enter C:WEBSITE; then press Enter.
e. Return to the Backup Options dialog by pressing Esc 3
times.
8. Submit and check the status of the backup job:
a. Submit the backup job to the queue by pressing Esc and
selecting Yes.
In a moment, you see several components loaded by SMS.
b. Display the Storage Management Console by pressing
Ctrl+Esc; then select Novell Storage Management
Console.
c. From the Select Job dialog, select Current Job List.
The WS WEBSITE 1 backup job is listed as running.
d. View the runtime status of the job by highlighting the job (do
not press Enter); then press Insert.
The runtime status screen displays the data sets being
processed, statistics on the data size, and error messages.
When the backup job is completed, an information message
appears.
e. Continue by pressing Enter.
f. Return to the main menu by pressing Esc twice.
9. View the job and error logs for WS WEBSITE 1:
a. View the job log for the WS WEBSITE 1 job by selecting
Log File Administration > View a log file: then press
Enter.
b. Select the WS WEBSITE 1 backup job.
Several items of information appear, including the session
date and time, target, and all data sets (directories and
files).
c. View the contents of the log by pressing Page Down several
times.
d. When you finish, return to the Error/Log File Administration
dialog by pressing Esc twice.
e. View the error log for the WS WEBSITE 1 job by selecting
View an error file: then press Enter.
f. Select the WS WEBSITE 1 backup job.
g. Check for errors or data sets skipped.
h. Return to the main menu by pressing Esc 3 times.
After testing the connection between the NetWare 6 server and the
TSA on the workstation, and verifying the backed up directory, you
decide to try backing up a volume on the NetWare 6 server.
Do the following:
1. From the main menu, select Job Administration > Backup.
The Backup Options dialog appears.
2. Connect to the NetWare 6 server as the target service:
a. Display a list of servers by selecting Target Service.
b. From the list, select DAx.
c. From the list of target services, select DAx.NetWare File
System.
You are prompted to log in to your NetWare 6 server.
d. For the username, enter admin.slc.digitalair; for the
password, enter novell.
e. When you are connected to DAx, continue by pressing
Enter.
3. Select the WEBFILES volume to back up:
a. Select What to Back Up.
An empty list of resources appears.
b. Press Insert, select WEBFILES:; then press Esc.
c. Return to the Backup Options dialog by selecting Esc.
4. In the Description field, enter SRVR WEBFILES 1
(End of Exercise)
The TSA evaluates each data set according to the following criteria:
■ Is this data set a subset of what is being restored?
■ Is this data set found on the hard disk?
For a custom restore session, you can specify exactly which data to
restore by using options that allow you to do the following:
■ Choose subsets of data to restore. You can choose specific
subsets of a backup session to include in or exclude from the
restore session by selecting major resources (such as volumes,
server-specific info, or containers) or minor resources (such as
directories, paths, files, or objects).
■ Open mode options. Open mode options let you customize
data for restoration. File system data can either be included or
excluded for the session. The speed of the restore depends on
the options you set.
■ Overwrite an existing parent (such as a container) or child
(such as an object). Be careful when you perform a selective
restore and choose whether to overwrite existing parents or
children, especially eDirectory objects.
Objects such as groups and users have references to other
objects in the eDirectory tree structure that will be affected by a
selective restore.
For example, suppose a part of the eDirectory tree structure gets
corrupted and several users are deleted from the tree.
There is a group that contains those users, but after the users are
gone, the group purges the membership list to remove those
users; the group, however, continues to exist in the eDirectory
tree structure.
If you perform a selective restore and choose not to overwrite
existing objects, the group membership list remains empty even
if you restore the users.
You need to either add the users manually to the group
membership list or restore the original group.
9. Select the device and media you want to restore from by pressing
Enter.
10. From the Select a Session screen, select the Session to Restore.
11. Specify the path to the session log file of the session you want to
restore by pressing Enter to accept the default.
A list of sessions appears.
12. Select the session you want to restore.
18. From the main menu, select Exit; then select Yes.
19. Unload the SMS modules from the server console prompt by
entering SMSSTOP.
a 15 minutes To complete your test of SBCON, you decide to restore some of the
data you backed up.
With SMS and the TSAs loaded and running, you can restore the
WEBSITE directory to the workstation.
Do the following:
1. From the NetWare 6 server console prompt, enter SBCON.
2. From the main menu, select Job Administration > Restore.
The Restore Options dialog appears.
You use this dialog to configure the restore job you want to
submit to SMS.
3. Connect to the workstation as the target service:
a. Display a list of servers by selecting Target Service.
b. From the list, select DAx.
c. From the list, select DAx.Workstations.
You are prompted to log in to your workstation.
To access full rights to the file system, you need to log in as
Administrator.
d. For the username, enter Administrator; for the password,
enter novell.
If you have problems logging in, try entering an uppercase
“A” in “Administrator.”
e. When you are connected to your workstation, continue by
pressing Enter.
4. In the Description field, enter RESTORE WEBSITE 1.
5. Select the tape emulator for the device and Test Backups media:
a. Select Device/Media Name and select
EMULATOR_TAPE 1.
b. Select the Test Backups media by pressing Enter.
c. Return to the Restore Options dialog by pressing Esc.
Do the following:
1. From the main menu, select Job Administration > Restore.
The Restore Options dialog appears.
You use this dialog to configure the restore job you want to
submit to SMS.
2. Connect to eDirectory as the target service:
a. Display a list of servers by selecting Target Service.
b. From the list, select DAx.
c. From the list, select DAx.Novell Directory.
You are prompted to log in to the eDirectory tree.
d. For the username, enter .ADMIN.SLC.DIGITALAIR; for
the password, enter novell.
e. When you are connected to your eDirectory tree, continue
by pressing Enter.
3. In the Description field, enter RESTORE DEL 1.
4. Select Session to Restore.
5. Select EDIR TREE 1.
6. View the Advanced Restore Options by selecting Advanced
Options.
7. Select Subsets of What to Restore; then select Include sub tree
by container name.
A Selection List Options dialog appears.
8. Press Insert; then select Directory Name Space.
(End of Exercise)
x Whenever possible, use intact replicas of the eDirectory tree for restoring
data. If this is not possible, restore the eDirectory tree from a backup.
Loss of a volume other than SYS does not affect eDirectory. The
only requirement is to restore the file system data and trustee rights.
A hard disk failure involving volume SYS affects the entire server
and halts all NetWare operating system activities.
The same situation exists if the failure affects only the hard disks
containing volume SYS.
The same situation exists if the hard disks containing volume SYS
on one server gets damaged, causing the failure of the entire server.
Summary
The following is a summary of the objectives in this section.
Objective Summary
Objective Summary
Duration: 2 hours In this section you learn how to install and manage Novell web
services, Enterprise Web Server, and FTP Server.
Objectives
1. Identify the Purpose of Novell Web Services
2. Install, Configure, and Manage Enterprise Web Server
3. Install and Configure NetWare FTP Server
Introduction
The Digital Airlines executive committee has decided to take
advantage of the Novell web services and Novell net services
included with NetWare 6 to deliver web content and services to
employees, customers, and partners.
Although you are familiar with and have previously used a web
server and an FTP server, you need to know more about Novell web
services and how to install and manage Enterprise Web Server and
FTP Server.
Internet
Laptop PC
Firewall
NetWare
For example, you can use Enterprise Web Server to host all types of
web content, from simple HTML web sites to complex, dynamically
generated web pages and web applications.
Only select the Allow Clear Text Passwords option if you want
to allow unencrypted passwords and data to be accepted by the
LDAP server.
12. Install Enterprise Web Server on DAx by selecting Finish.
13. After the Enterprise Web Server files are copied and processed,
complete the installation process by selecting Close.
14. From your NetWare 6 server, remove the NetWare 6 CD.
You can load and unload the web server from the NetWare server console
prompt by entering NSWEB and NSWEBDN.
x If you have a firewall, you must configure it to allow the NetWare Web
Manager port number to be made available. By default, the port number
assigned is 2200.
However, you can change the port number using Admin Preferences in
NetWare Web Manager.
Figure 13-2
You can use Web Manager to configure and manage Enterprise Web
Server.
When you select the link to the NetWare server, the Enterprise Web
Server configuration page appears:
Figure 13-3
b For more on configuring these files, see the Novell Developer Kit web
site at http://www.developer.novell.com/ndk/nscomp.htm.
However, as you build your own web site, you should store it on
your NetWare server in a volume besides SYS.
Exercise 13-1 Install and Configure Enterprise Web Server to Access the
Digital Airlines Web Site
a 25 minutes After learning about Enterprise Web Server, you are ready to install
it on your NetWare 6 server to provide access to the Digital Airlines
web site.
You have received the web site files on a CD from your webmaster
to install on your Netware 6 server in a WEBFILES volume.
Do the following:
■ Part I: Install Enterprise Web Server
■ Part II: Test Enterprise Web Server Access
■ Part III: Install the Digital Airlines Web Site Files
■ Part IV: Configure Enterprise Web Server to Access the Digital
Airlines Web Site Home Page
The host name is in the field at the right of the IP address and is
currently the server IP address.
13. Continue by selecting Next.
Do the following:
1. Load Novell web services on DAx using the NSWEB command:
a. From DAx, switch to the console prompt by pressing
Ctrl+Esc and selecting 1.
b. From the server console prompt, enter NSWEB.
Several Novell web services are loaded onto DAx using the
NVXALLUP.NCF file.
Now that you have installed and tested Enterprise Web Server, you
can install the Digital Airlines web site files.
If you have completed Exercises 11-1 and 11-2 in Section 11, the
Digital Airlines web site files are already installed in a WEBFILES
volume on DAx. You can skip this part of the exercise and continue
to Part IV.
1. Create an NSS pool (WEBMEDIA) and NSS logical volume
(WEBFILES) for the web site files:
a. Make sure ConsoleOne is running on your workstation and
that you are logged in as admin to DAx.
b. From the SLC container in ConsoleOne, right-click the DAx
object; then select Properties.
c. Select Media > NSS Logical Volumes; then select New.
d. For the logical volume name, enter WEBFILES; then select
Next.
e. From the list of available storage, select the unpartitioned
space; then select Allow volume quota to grow to pool size.
f. Continue by selecting Next.
g. For the pool name, enter WEBMEDIA; for the pool size,
enter 400.
Although you have installed the Digital Airlines web site files on
your NetWare 6 server, Enterprise Web Server currently displays the
sample web pages in SYS:NOVONYX/SUITESPOT/DOC.
You can change this setting and give customers and employees
access to the Digital Airlines files by using Novell Web Manager.
Do the following:
1. From your workstation desktop, open Internet Explorer.
2. For the URL enter https://DAx.digitalairlines.com:2200.
If Novell Web Manager does not display, try restarting your
NetWare 6 server; then enter the URL again.
3. (Conditional) If a security alert dialog appears, continue by
selecting Yes.
The NetWare Web Manager page appears.
4. From NetWare Enterprise Web Servers, select the DAx link.
An Enter Network Password dialog appears.
5. For the user name, enter .admin.slc.digitalair; for the password,
enter novell.
Make sure you include a period at the left of admin.
6. Select OK.
The NetWare Web Server page for your Enterprise Web Server
appears.
7. Change the directory where Enterprise Web Server looks for web
site documents (specifically INDEX.HTML):
a. In the left frame, select View Server Settings.
b. In the right frame, scroll down until you find a Primary
Document Directory link.
The current setting directs Enterprise Web Server to locate
the home page (INDEX.HTML) in
/NOVONYX/SUITESPOT/DOCS.
c. Select Primary Document Directory; then enter
WEBFILES:/DAWEB.
d. Select OK; then select Save and Apply.
When the changes have been applied, a dialog appears.
e. Select OK.
8. Give your Digital Airlines employees access to the new web site:
a. From the left frame, select Restrict Access.
b. Scroll down to Public Directory Designations.
c. Select Insert Directory.
d. In the New Public Directory field, enter
WEBFILES:/DAWEB; then select OK.
e. Scroll to the bottom of the web page and select Save
Changes.
You are notified that the change is successful and that you
need to restart Enterprise Web Server.
f. Restart the web server by selecting OK.
9. Close the NetWare Web Manager window.
10. Test the new configuration by opening Internet Explorer and
entering wwwx.digitalairlines.com.
Instead of the Enterprise Web Server sample web site, the
Digital Airlines home page appears.
11. Test the Digital Airlines home page by selecting one or more
links (such as Who We Are).
12. When you finish, close the Digital Airlines window.
(End of Exercise)
FTP Server can be used to post new web content to your Enterprise
Web Server, or to post or retrieve documents from your NetWare file
server.
11. After the NetWare FTP Server files are copied and processed,
complete the installation process by selecting Close.
12. From DAx, remove the NetWare 6 CD.
You can configure FTP Server with NetWare FTP Server Manager
(accessed from NetWare Web Manager).
After installing FTP Server, the NetWare Web Manager home page
adds a NetWare FTP Server heading with a link to the NetWare
server where the FTP server is installed.
When you select the link to the NetWare server, the following
Server Preferences menu appears:
Figure 13-4
From the Server Preferences menu, you can select from the
following:
■ On/Off. Use to load (Server On) and unload (Server Off)
Enterprise Web Server on your NetWare server.
You can also use the NWFTPD command at the server console
prompt to load FTP Server; you use the UNLOAD NWFTPD
command to unload FTP Server.
■ Server Settings. Use to see general FTP Server settings that let
you set configurations such as the Welcome message text file,
session parameters, and FTP Server port number.
x The configuration changes you make to FTP Server from NetWare Web
Manager Server Preferences are saved in SYS:\ETC\FTPSERV.CFG on your
NetWare server.
b For more on the settings for each configuration option, select Help in the
configuration window for online help.
Do the following:
1. Create an Anonymous user object in eDirectory:
Although you can do this with an administrative tool such as
ConsoleOne, an easier way is to use the NWFTPD command at
the server console prompt.
a. From your NetWare server, switch to the console prompt by
pressing Ctrl+Esc and selecting 1.
b. From the server console prompt, enter NWFTPD -A.
c. Enter your admin username; then enter your password.
This logs you in as network administrator to your container
where an Anonymous user object is created for accessing a
home directory on your NetWare server.
The default home directory is SYS:/PUBLIC, and the
Anonymous user object is given Read and File Scan rights
to the home directory.
d. Do one of the following:
❑ Accept the default SYS:/PUBLIC home directory by
pressing Enter.
❑ Enter another directory on your NetWare server for the
home directory.
The Anonymous user account is initialized.
e. Return to the server console prompt by pressing the
Spacebar.
2. Configure FTP Server to allow anonymous user login:
a. From your workstation, open a web browser.
b. For the URL, enter DAx.digitalairlines.com:2200 or DAx
IP address:2200.
c. From NetWare FTP Server, select the DAx link.
An Enter Network Password dialog appears.
d. Enter your username and password; then select OK.
The Server Preferences menu appears.
Figure 13-5
However, there are times when you want to restrict access to certain
directories and files on the server.
An FTP session creates a connection between the client and the FTP
server to transmit data. You can start an FTP session from a
workstation using one of the following methods:
■ Command-line FTP client. Enter FTP hostname or FTP IP
address, where hostname is the DNS domain name and IP
address is the IP address of the NetWare server running FTP
Server.
■ Web browser or FTP client application. Enter
ftp://hostname or ftp://IP address, where hostname is the
DNS domain name and IP address is the IP address of the
NetWare server running FTP Server.
For example, if the NetWare server IP address is 192.168.1.3,
you would enter ftp://192.168.1.3 in Internet Explorer to access
the default FTP directory.
For restricted FTP sites, you need to know the username and
password to access the directories and files.
Exercise 13-2 Install and Configure FTP Server to Access Your Web Site
Files
a 15 minutes After installing Enterprise Web Server and the Digital Airlines web
site files on your NetWare 6 server, you are ready to install and
configure FTP Server to do the following:
■ Allow the public to access tour information and pictures
■ Allow yourself (as network administrator) secure remote access
to your web server directories
Do the following:
■ Part I: Install FTP Server
■ Part II: Configure an Anonymous User Account
■ Part III: Configure Access to DAWEB and FTPFILES
■ Part IV: Test Account Access to FTP Server
11. From the Summary dialog, make sure NetWare FTP Server and
NetWare Port Resolver are listed.
12. Install FTP Server on DAx by selecting Finish.
13. After the FTP Server files are copied and processed, complete the
installation process by selecting Close.
14. From DAx, remove the NetWare 6 CD.
After installing FTP, you want to test the server to make sure it
works properly. The easiest way to do this is by creating an
anonymous user account with the default settings.
Do the following:
1. Create the anonymous user account:
a. From DAx, switch to the console prompt by pressing
Ctrl+Esc and selecting 1.
b. From the console prompt, enter NWFTPD -A.
You are asked for your user admin name.
c. Enter .admin.slc.digitalair.
Make sure you include a period at the left of admin.
You are asked for a password.
d. Enter novell.
Do the following:
1. From Internet Explorer, select File > New > Window.
A new Internet Explorer window is opened.
2. Access the Anonymous user account directory by entering
FTP://DAx.DIGITALAIRLINES.COM.
3. (Conditional) If you are prompted to log in, select Log in
Anonymously; then select Login.
4. Right-click a file in the folder; then select Copy to Folder.
5. Select the My Documents folder; then select OK.
6. Check the My Documents folder.
The file has been copied (downloaded) from
WEBFILES:/DAWEB/FTPFILES to the MY DOCUMENTS
folder on your workstation.
7. Try copying a file from MY DOCUMENTS to FTPFILES.
An error appears indicating that you do not have the right
(permission) to write a file to the FTPFILES directory.
(End of Exercise)
Summary
The following is a summary of the objectives in this section.
Objective Summary
Objective Summary
Duration: 1 hour In this section, you learn to plan your NetWare 6 migration or
upgrade to mitigate failures and network outages.
Objectives
Prior to starting this section, 1. Review NetWare 6 Operating System Requirements
remove NetWare 6 and install
NetWare 5.1 on student servers 2. Upgrade Network and Server Hardware
using images created in the course 3. Prepare the Network for the Migration or Upgrade
Setup section.
4. Create an Upgrade or Migration Plan
If images are not available, install
NetWare 5.1 on student servers
using the parameters specified in
the Setup section under “Create Introduction
Images.”
Upgrading or migrating an existing NetWare network to NetWare 6
Be sure to leave DA7 blank. is a critical task that must be planned carefully in advance.
Students perform an installation on
it in Section 16. Failure to plan the upgrade or migration process could result in data
loss and network downtime; both of which incur costs for your
organization.
Software Requirements
Hardware Requirements
Emphasize that these are only In addition to the software requirements, the servers in your
minimum requirements. network must meet the following minimum hardware requirements:
Explain that NetWare 6 uses a Disk Space The following are required:
200 MB DOS partition by default. ■ 200 MB DOS partition with at least 35 MB of
free space
Explain that it is advisable to use
■ 2 GB of free space on volume SYS
a DOS partition that is 200 MB +
the size of the server’s RAM. Video SVGA-compatible display required
Point out that the VESA_RSP Network Interface One network board required
command can be issued after
Media Drives One CD drive required
installation to detect new video,
monitor, or mouse hardware. Mouse One of the following is recommended (but not
required):
■ USB
■ PS/2® (Mini-DIN)
■ Serial
Emphasize that failing to perform a Novell Technical Support receives support calls each week from
backup before upgrading or network administrators who experience problems while upgrading
migrating could potentially cost or migrating but who did not back up the network. Such situations
students their jobs. can destroy your network and jeopardize your job.
Emphasize that it is critical that 2 Prior to completing any NetWare 6 upgrade or migration tasks,
verified backups be made, even make 2 full backups of your entire eDirectory tree and the file
though it takes time to complete systems on each server.
the process.
After the backups are made, verify the backups. Creating verified
backups lets you quickly restore your system should errors occur
during the upgrade or migration process.
Emphasize the importance of Before you add a NetWare 6 server to a network, you run NetWare
using Deployment Manger prior to Deployment Manager to update existing NetWare servers. It checks
upgrading or migrating to system files to ensure that NLMs and eDirectory files are updated to
NetWare 6. allow NetWare 6 to be installed.
7. In the NDS Tree Browser window, browse to your tree and select
the top-most container in your tree; then select OK.
8. Mark Include Subordinate Containers; then select Next.
9. Mark the servers in your network that require updating; then
select Next.
Deployment Manager detects which servers need to be updated.
The servers that appear in the Server column are the only
servers that need to have eDirectory updated.
10. Wait while files are copied.
11. When prompted that eDirectory must be reloaded for the changes
to take effect, select Next.
12. When prompted that the servers have been updated, select Exit.
Make sure students understand In addition to updating Directory Services, you also might need to
that this process doesn’t have to update the Novell Certificate Server and the Certificate Authority
be done when upgrading NetWare (CA) object in your tree.
4.x or NetWare 5.1 servers.
x Updating the Certificate Authority only applies to NetWare 5.0 servers. The
NetWare 5.1 CA is automatically updated during the NetWare 6 upgrade.
b For additional details, see TID 10053572. Remember that the server
hosting the CA must remain operational and accessible during the
installation of all NetWare 6 servers into the tree.
There are 2 general strategies you can choose from when upgrading
an existing NetWare 4 or 5 server to NetWare 6:
■ In-Place Upgrade
■ Across-the-Wire Migration
Each strategy has its benefits and its drawbacks. The strategy you
choose is based on your organizational values and needs.
In-Place Upgrade
It’s very fast. An in-place upgrade The risk of data loss is high. If
generally takes 30 to 45 minutes. errors occur, the original server is
no longer operational.
Across-the-Wire Migration
For one company, speed might be the most important factor; making
an in-place upgrade the most advantageous choice. For another
company, data integrity might be most important; making an
across-the-wire migration the better choice.
Emphasize that one strategy isn’t After identifying a server strategy, the next step is to determine an
necessarily better than the other. eDirectory strategy. There are 2 general strategies you can choose
Organizational values will dictate from when designing an upgrade or migration plan:
which approach is best.
■ Top-Down Upgrade
■ Bottom-Up Upgrade
Top-Down Upgrade
Bottom-Up Upgrade
The bottom-up strategy was Alternatively, you can use a bottom-up strategy to plan your
successfully used to upgrade the migration or upgrade. With this strategy, you upgrade or migrate
internal Novell corporate network noncritical servers at the bottom of the eDirectory tree first.
to NetWare 6.
When complete, you then upgrade or migrate servers in order, up
the tree. The last server to be upgraded or migrated is the server
holding the master replica of the root partition.
10. Upgrade or migrate the server using the steps presented in the
next section.
11. When the upgrade is complete, allow eDirectory to normalize for
a period of time to let the schema synchronize throughout the
network.
Depending on the size of your network, this could range from a
couple of hours to several days. Use the green light indicator in
iMonitor to check the status of the tree.
12. To verify that the schema is properly synchronized, trigger a
schema sync operation with DSTRACE.
a. Enter the following commands at the server console:
SET DSTRACE=ON
SET DSTRACE=+SCHEMA
SET DSTRACE=*SS
b. Switch to the Directory Services Trace screen.
c. Check for the following message:
SCHEMA: All Processed = YES
13. Repeat this process for each server in the tree that holds a replica,
working your way from the bottom of the tree to the top.
14. When complete, repeat this process for any servers in your tree
that don’t hold a replica.
Start with the least critical servers and progress to those that are
more important.
Give students examples of After you select a server strategy and an eDirectory strategy, the
upgrade or migration tasks that are next step in creating a migration or an upgrade plan is to create a
dependent upon each other and flow of events. If possible, use project planning software to
tasks that can be done complete this phase.
concurrently.
Do the following:
If project management software 1. Identify and list every task that must be completed in detail.
isn’t available, the network
administrator can list tasks on 2. Identify tasks that must be done in order.
sticky notes arrayed on a wall. 3. Identify tasks that can be done concurrently with other tasks.
They can be easily arranged and 4. Determine the following:
rearranged to create the proper ❑ Which tasks can’t be started until other tasks are completed
flow of events.
❑ Which tasks must start at the same time
❑ Which tasks must end at the same time
5. Identify the amount of time each task must take.
Help students understand the 1. Identify roles that are required to complete the project.
concept of resource allocation.
Give examples; such as one You might need roles such as a backup specialist, an eDirectory
resource working on 2 concurrent specialist, a NetWare specialist, or a hardware specialist. Your
tasks. organization’s values and priorities help define these roles.
a 45 Minutes In this exercise you create a NetWare 6 upgrade plan for Digital
Airlines, Inc.
In this exercise, take the role of the You and your classmates work for a major technology consulting
Digital Airlines CIO. firm. Your firm has been recently hired by Digital Airlines to
upgrade their NetWare 5.1 network to NetWare 6.
You have hired the students as
consultants to upgrade your
NetWare 5.1 network to
Corporate Network Architecture
NetWare 6.
To define your upgrade plan, begin with the following information
Provide students with coaching
and feedback as they prepare their about the Digital Airlines network.
plan. ■ Digital Airlines is headquartered in Salt Lake City, USA and
has terminals in airports around the world:
❑ Salt Lake City International Airport (SLC)
❑ Delhi Indira Gandhi International Airport (DEL)
❑ New York La Guardia International Airport (LGA)
❑ Sydney Australia International Airport (SYD)
❑ Berlin Tegel International Airport (TXL)
❑ London Heathrow International Airport (LON)
■ Each airport terminal has one NetWare 5.1 server.
Project Requirements
The CIO has provided you with the following project requirements:
■ Because of timing issues, servers will be upgraded to
NetWare 6, not migrated.
■ The upgrade must be done using the bottom-up eDirectory
upgrade strategy.
■ The entire network must use a single protocol: TCP/IP.
■ There should be a single authoritative DNS server for the entire
corporation.
■ Each terminal should have its own DHCP server. This server
should provide DHCP clients with a dynamic IP address and
subnet mask. In addition, the following options should be
configured:
❑ DNS server IP address
❑ Default gateway IP address
❑ SLP directory agent IP address
■ The DHCP server should dynamically update the corporate
DNS server with workstation hostnames and IP addresses.
■ Each terminal should have an SLP directory agent running to
help clients locate services. These directory agents should be
statically configured to replicate with each other.
■ Previous management at Digital Airlines had instituted a policy
that allowed only a few individuals to have user accounts.
However, because of new NetWare 6 features such as iFolder,
current management wants every employee to have a user
account. You will be provided an LDIF file created by an HR
system to create the accounts.
■ Licenses for Digital Airlines should be placed as high in the
tree as possible. A replica of the partition that contains the
licenses should be placed on each server so local users don’t
have to use a WAN link to get a license.
■ Every server is to have a SYS and a DATA volume. No user
data or applications are allowed on SYS. Both DATA and SYS
must be NSS volumes.
■ iFolder is to be installed on every server. Each server will
provide iFolder services for only users at the terminal where the
server is physically located. Every user in the tree is to have an
iFolder account.
Depending on the size of the Using the preceding information, meet together as a class and
student group, some students design an upgrade plan for Digital Airlines. Be prepared to present
might need to share roles. your plan in writing to your client (your instructor) when you are
done. To complete the plan, do the following:
Point out that the tree has only a 1. Assign the following roles:
single partition. DA1 has the
❑ Project Lead
master replica, DA2 and DA3 have
read/write replicas. ❑ eDirectory Specialist
❑ NetWare Specialist
❑ Hardware Specialist
❑ Documentation Specialist
Help students identify better ways 2. Determine and write a server upgrade strategy.
to partition and replicate the tree.
3. Determine and write an eDirectory upgrade strategy.
Summary
The following is a summary of the objectives in this section.
Objective Summary
Objective Summary
Exercise Answers
Answers vary.
Duration: 2 hours, 30 minutes In this section you learn the 2 methods that you can use to upgrade
an existing NetWare server to NetWare 6.
Objectives
1. Perform an In-Place Upgrade
2. Perform a Migration
3. Perform Post-Migration or Post-Upgrade Tasks
Introduction
With your migration or upgrade plan complete, you can upgrade
your network to NetWare 6.
After the backups are complete, verify the backups. Do not attempt
an upgrade without a backup.
If you are upgrading a NetWare server with NSS volumes, the NSS
volumes do not appear or mount until they are updated.
Because you are doing an upgrade, you are not prompted to provide
all the information normally required for a new server installation.
Notice your IP address and subnet mask fields are filled in with
their respective information.
12. Enter your DNS information.
When you migrate data the migration wizard copies the file system
and eDirectory database from an existing NetWare 4, 5, or 6 server
to a newly installed NetWare 6 server.
After the original server’s file system and eDirectory database are
migrated, it’s brought down and the NetWare 6 server reboots and
assumes the name and identity of the original server on your
network.
Before you can migrate your data, you must first install a NetWare 6
server in a temporary eDirectory tree.
The source server is the NetWare server that contains the files,
volumes, and eDirectory objects to be copied to the NetWare
destination server. Valid source servers can be running NetWare
4.11, 4.2, 5.0, 5.1, or 6.
Do the following:
1. Verify that you have the Supervisor right to the source server’s
file system and Directory tree.
2. Make sure the destination server can communicate with the
source server:
a. If using IPX, enter Display Servers and make sure the
source server is listed.
b. If using IP, enter Display SLP Services and make sure the
source server is listed.
3. Apply the NW6NSS1A patch to update the version of NSS.
b See TID 2961749. Despite what the abstract implies, this patch can be
applied before applying Support Pack 1.
4. Update the source server with the latest NetWare support pack.
Updates are available at support.novell.com.
5. (Conditional) If you are migrating data from NetWare 4, make
sure the source server’s volumes have long name space support
added to all volumes to be copied.
To add long name space support to a NetWare 4.11 or NetWare
4.2 volume, enter the following at the server console:
LOAD LONG
ADD NAME SPACE LONG TO volume name
The destination server is the new computer that receives the data
from the source server. This server must be installed into a
temporary tree.
x Do not use the same name as the source server’s name or eDirectory tree
name; otherwise, the destination server cannot assume the identity of the
source server after the migration.
x Volume names on the destination server must be the same as the volume
names on the source server.
Do the following:
1. Install migration wizard from the NetWare 6 operating system
CD.
2. Run the migration wizard on the workstation by selecting Start
> Programs > Novell > Netware Migration Wizard >
NetWare Migration Wizard.
Figure 15-1
Figure 15-2
Figure 15-3
Figure 15-4
9. Name the project, choose a place to save it, and then select Next.
By default, the migration wizard saves all projects to
C:\PROGRAM FILES\NOVELL\NETWARE
MIGRATION WIZARD.
Figure 15-5
10. In the Select the Source NDS Tree window, select the Directory
tree that contains your source server; then select Next.
The following appears:
Figure 15-6
11. In the Select the Source Server window, select your source
server from the Directory tree.
12. In the Select the Destination NDS Tree window, select the
eDirectory tree that contains your destination server.
13. In the Select the Destination Server window, select your
destination server from the destination eDirectory tree.
Figure 15-7
14. Save your project and access the Project Window by selecting
Create.
The Project Window now appears.
Figure 15-8
Copy Volumes
x If you copy volumes in phases, at the final volume copy make sure you
select all volumes that you previously copied; then select Cancel.
Otherwise, the migration wizard restores trustee assignments only to the
last volumes that were copied.
Figure 15-9
2. Select each volume you want to copy and select Yes; then select
Next.
x If you decide not to copy any volumes, select No for all volumes, then
select Next and continue with “Edit Configuration Files” on 15-21.
Figure 15-10
Figure 15-11
Figure 15-12
Figure 15-13
Figure 15-14
2. Select the configuration file you want to edit; then select Edit
File.
The following appears:
Figure 15-15
3. Copy and paste the commands from the configuration file on the
source server to the corresponding configuration file on the
destination server.
If you intend to change the IP address on your destination
server to be the same as the IP address of your source server,
edit your configuration files and change the IP address in 2
places: AUTOEXEC.NCF and SYS:ETC/HOSTNAME.
a. Copy the source server’s IP address and paste it into the
destination server’s AUTOEXEC.NCF file.
Figure 15-16
After you complete the volume copy and edit configuration files,
you can migrate eDirectory from the source to the destination
server.
During this phase, the source server is brought down and the
destination server is restarted. The destination server takes on the
source server’s name and place in your network.
Figure 15-17
2. Back up all volumes that you are not planning to migrate and
complete the following tasks before continuing; then select Next.
❑ Make sure all volume data migrated successfully.
❑ Make sure all critical errors from the file copy are resolved.
❑ Make sure the servers in your source tree are in time sync
and that eDirectory is synchronized.
For more information, see step 2 in “Finish eDirectory
Migration” on 15-30.
Figure 15-18
x If you select No to update the schema, by default the second Yes option
is enabled, which causes the migration wizard to compare the source
and destination schemas.
x The migration wizard does not check the health of the tree and will not
prevent you from continuing if your tree is unhealthy. If your tree is
unhealthy the migration might not complete successfully.
Figure 15-19
8. Copy the NICI files from the source server to the destination
server by following the on-screen instructions.
Figure 15-20
9. Delete all user connections (except your own) to the source and
destination servers; then select Next.
10. In the Password Verification window, enter the passwords for the
source and destination trees; then select Next.
Figure 15-21
Figure 15-22
13. View the Error and Success logs; then select Done.
Use the Error log to see errors that occurred during migration.
If there were errors, use the Success log to determine how far
the migration progressed.
If migration failed, restore your servers to their original
configuration.
14. Check the destination server and verify that it has restarted and
taken on the name of the source server.
15. Reboot your workstation and log in to the former destination
server.
In this phase you upgrade the schema, fix volume objects, and
restore trustees to the destination server after the server is restarted.
Figure 15-23
3. Verify that you have completed the tasks by selecting Yes or No;
then select Next.
4. In the Password Verification window, enter the password for the
source tree; then select Next.
5. Resolve any warnings or errors; then select Next.
The following appears.
Figure 15-24
SET DSTRACE=ON
SET DSTRACE=+BLINK
SET DSTRACE=*B
If you switch to the Directory Services screen on the server, you can
watch the objects as they are processed.
If the original server had NSS volumes, you need to upgrade them
to be compatible with the version of NSS shipped with NetWare 6.
To do this, complete the following for each NSS volume:
1. At the command prompt enter
NSS /ZLSSVOLUMEUPGRADE=All
2. At the server console, enter
SET NLS SEARCH TYPE
3. Make sure the value for NLS SEARCH TYPE is set to 0; if not,
at the console prompt enter
SET NLS SEARCH TYPE = 0.
4. At the server console, enter
SET STORE NETWARE 5 CONN SCL MLA USAGE IN
NDS.
5. Make sure the value is set to OFF; if not, enter
SET STORE NETWARE 5 CONN SCL MLA USAGE IN
NDS = OFF.
6. At the server console prompt, enter
FLUSH CDBE
a 2 hours In this exercise you work as a group to upgrade your NetWare 5.1
network to NetWare 6 using the upgrade plan developed in the
previous section. Do the following:
■ Part I: Review Project Requirements
■ Part II: Run a Basic Health Check on Each Server
■ Part III: Prepare Your Network for eDirectory 8.6 Using
Deployment Manager
■ Part IV: Perform an In-Place Upgrade from NetWare 5.1 to
NetWare 6
■ Part V: Complete eDirectory Clean-Up Tasks
■ Part VI: Complete the Upgrade Plan
Do the following:
1. At the console prompt on DA1, enter DSREPAIR.
2. Select Advanced Options Menu > Global Schema
Operations.
3. Authenticate as Admin.SLC.DigitalAir.
4. Select Post NetWare 5 Schema Update.
5. If prompted to perform this update, select Yes.
6. When the update is complete press Esc until you return to the
Available Options menu.
7. In the Available Options menu, select Unattended full repair.
If you receive errors, run an Unattended full repair again until
you receive no errors.
8. In Available Options, select Time synchronization.
If you receive errors, have your instructor assist you.
9. In Available Options, select Report synchronization status.
If you receive errors, have your instructor assist you.
10. Exit DSREPAIR.
SET DSTRACE=ON
SET DSTRACE=+S
SET DSTRACE=*H
12. Switch to the Directory Services screen and make sure succeeded
and All processed = YES appear.
13. At the server console prompt, enter the following commands:
SET DSTRACE=NODEBUG
SET DSTRACE=+SCHEMA
SET DSTRACE=*SS
SET DSTRACE=*SSD
14. Switch to the Directory Services screen and make sure All
processed = YES appears.
15. At the server console prompt, enter the following commands:
SET DSTRACE=NODEBUG
SET DSTRACE=OFF
16. Repeat this process on all servers in the network.
Do the following:
1. From your workstation, log in to DIGITALAIR-TREE as
.admin.SLC.DIGITALAIR with a password of Novell.
2. On your workstation, insert the NetWare 6 operating system
CD into the CD drive.
3. Browse to the root of the CD and run NWDEPLOY.EXE.
4. Select Open; then select OK.
5. In Deployment Manager, double-click the Network
Preparation folder.
6. Select Step 2: View and Update NDS Versions.
7. Browse to and select the DigitalAir-Tree.
8. Mark Include Subordinate Containers; then select Next.
9. When prompted that no servers were found that require an NDS
update, select OK; then select Exit.
14. When you receive the message that the eDirectory tree is
prepared for eDirectory 8.6, select Exit.
15. On all servers, make sure you received the message
NDSEM-5.0-009: Process Completed.
16. Close Deployment Manager by selecting Cancel.
❑ B for Both
5. In the Welcome to NetWare Server Installation screen, read and
select Accept License Agreement.
6. Select Continue with Existing Partition.
7. In the License Agreement for Jreport Runtime screen, read and
select F10 to accept the license agreement.
8. In the Welcome screen, change the type of install to Custom.
9. In the Welcome screen, make sure the type of server is set to
Upgrade; then select Continue.
10. In the Server Settings screen, select Continue.
Notice that your IP address and subnet mask fields are filled in
with their respective information.
15. In the Domain Name Service screen Host name field, enter the
name of the server.
16. In the Domain field, enter DIGITALAIRLINES.COM.
17. In the Name Server 1 field, enter the IP address of the DNS
server designated in your upgrade plan; then select Next.
18. In the Log in to NDS dialog, authenticate as
admin.SLC.DigitalAir; then select OK.
19. On the NDS Summary screen, verify the information; then select
Next.
20. On the License screen, insert your license disk (provided by your
instructor).
21. Browse to and select the server license (nlf); then select OK.
Example: A:\LICENSE\license_number.NLF.
22. In the Licenses screen, highlight the license; then select Next to
install the license.
Step 23 is written with the idea that 23. On the Components screen, select Clear All; then select Next.
students will return after the
installations are complete and 24. On the Novell Certificate Server 2.21 Objects screen, select
install the various products on the Next.
servers. 25. On the LDAP Configuration screen, select Next.
Optionally, students can specify 26. On the eDirectory iManager Install Options screen, select Next.
the products identified in their
27. On the Summary screen, select Finish.
upgrade plan in the Components
screen. Allow the files to copy.
However, the steps required to 28. When you receive the Installation Complete dialog, remove the
complete the install will be different CD and select Yes to reboot the server.
from those listed here.
(End of Exercise)
Summary
The following is a summary of the objectives in this section.
Objective Summary
Objective Summary
Duration: 1 hour, 30 minutes In this section, you learn how to add a NetWare 6 server to an
existing network.
Objectives
1. Prepare Your Existing Network
2. Prepare Your Server for NetWare 6
3. Install NetWare 6
Introduction
From time to time, you might need to add NetWare 6 servers to your
network.
Relate situations you’ve There are many reasons for adding NetWare 6 servers to your
experienced where adding servers existing network. However there are 2 main reasons:
was necessary.
■ To add capacity. As an organization grows, it can quickly
exceed the capacity of its network. Adding servers increases the
capacity of the network, reducing the load on the existing
servers.
The addition of remote offices can also require additional
servers, because it is inadvisable to require users to cross WAN
links to access files.
Be sure students understand that Because NetWare 6 is an advanced operating system, hardware that
working servers must significantly was sufficient to run earlier versions of NetWare will likely be
exceed the minimum inadequate for NetWare 6. Key areas to be aware of are the
requirements. following:
■ CPU. A Pentium Pro is the minimum CPU required. However,
we recommend that you use a multi-processor Pentium III or IV
system.
■ RAM. 256 MB is the minimum amount of RAM required. We
recommend that you upgrade to an RDRAM system and that
you use 1 GB or more of memory.
■ Storage. A 4 GB SCSI or EIDE hard disk is the minimum
storage requirement. We recommend that you upgrade to a
RAID 5 array and a Fiber-Channel Storage Area Network
(SAN).
Teach students how to configure NetWare 6 can be installed from the server’s local CD drive or from
CONFIG.SYS and installation files on the network.
AUTOEXEC.BAT to load a CD
driver. If you don’t have a bootable CD drive, access the NetWare 6
installation files by doing the following:
Make sure they understand that 1. Create a 200 MB or larger DOS partition.
they don’t have to do this if their
server has a bootable CD. Make the partition large enough to also include the contents of
your server RAM in case you need to create a core dump.
2. Copy the DOS CD driver for your CD drive onto the DOS
partition.
DOS CD drivers are provided by the CD drive manufacturer.
3. Edit your CONFIG.SYS file to load the CD driver. For example:
DEVICE=C:\OAKCDROM.SYS /D:ROBBSCD
4. Edit your AUTOEXEC.BAT file to load the Microsoft CD
Extensions driver (MSCDEX.EXE) as shown in this example:
MSCDEX.EXE /D:ROBBSCD /L:E
Make sure the logical filename of your CD drive (specified in
the CONFIG.SYS and AUTOEXEC.BAT files) is not CDROM
or CDINST.
5. Make sure CONFIG.SYS contains the following commands:
FILES=50
BUFFERS=30
Time permitting, show students Alternatively, you can install from files located on a NetWare server.
how to load the DOS IP client on To do this, install the Novell Client for DOS and Windows 3.1x or
the server so they can log into a IP Server Connection utility software located on the Novell client
NetWare server and install CD.
NetWare 6 from there.
After accessing the files for the installation program, you can begin
the installation.
Point out that you might have to 1. Insert the NetWare operating system CD into your CD drive and
adjust the boot order in the boot from it.
server’s CMOS setup program for
it to boot from a CD. The initial screens of the installation program display in
text-based mode. Autodetected and default settings appear on
each screen.
You can accept the detected and default settings, or you can
modify the settings to meet the needs of your network
environment.
2. Choose from the following:
❑ To continue the installation with the standard settings, use
the arrow keys to highlight Continue in the Options box;
then press Enter.
❑ To modify the settings in the installation, do the following:
a. Use the arrow keys to highlight Modify in the Options
box; then press Enter.
b. Highlight the field to be modified; then press Enter.
c. Select or enter the appropriate value.
Accepting the license agreement means that you have read and
accepted the terms and conditions contained in the license
agreement. In NetWare 6, there are 2 license agreements:
■ NetWare 6 Novell Software License Agreement
■ JReport Runtime License Agreement
Figure 16-1
Figure 16-2
Figure 16-3
Express Installation
Custom Installation
Figure 16-4
Choose the country, code page, and keyboard mapping for your
language and computer. The following shows the regional settings:
Figure 16-5
Figure 16-6
After you select the mouse type and video mode, the network
operating system files are copied to your computer’s hard disk.
Figure 16-7
Because one adapter can control more than one type of storage
device, your computer might require only a single HAM, even
though it can have more than one type of storage device—and
therefore multiple CDMs.
To edit the properties of the storage adapter (if required), the storage
adapter must be installed and configured correctly.
Properties such as interrupt, port value, and slot must not conflict
with any other device in the computer. If you need specific storage
adapter properties, contact the storage adapter manufacturer.
Figure 16-8
If your storage device is not detected, choose the driver from the list
provided with NetWare 6 or add a driver from a disk. CDMs can be
obtained from the storage device manufacturer.
To edit the properties of the network board (if required), the board
must be installed and configured correctly.
Properties such as interrupt, port value, and slot must not conflict
with other devices. If you need specific properties, contact the board
manufacturer.
Figure 16-9
Figure 16-10
The server should now have a NetWare partition and one volume
named SYS. If you have space available for creating additional
partitions and volumes, you can create them now.
x If you have allocated all available space to volume SYS, you are not
prompted for NetWare server file system information. You can skip to “Install
Network Protocols” on 16-24.
Create Volumes
Volumes are created from free space. A large disk can be divided
into several volumes during installation. In addition, a volume can
be distributed over multiple disks.
Modify Volumes
Delete Volumes
You can delete any volume except SYS. When a volume is deleted,
all data on the volume is lost.
Mount Volumes
Set Up DNS
The server time and time zone are important for synchronizing
network events.
x For more on time server types, time source, and time synchronization,
see Course 575, NDS Design and Implementation.
Set Up eDirectory
Now that you have created an eDirectory tree or installed the server
into an existing eDirectory tree, the NetWare server object and
volume objects are installed in the container you specified.
NetWare 6 must have a valid license. You can install the license
from the NetWare 6 license/cryptography disk or browse to a
directory that contains NetWare 6 licenses.
x To create the Security container object and the organizational CA object, you
must have Supervisor rights to the Root of the eDirectory tree.
Both objects are created at and must remain at the Root of the
eDirectory tree.
Make sure the server you use to permanently host the organizational
CA object is a reliable, accessible, and continuing part of your
network.
In this exercise, play the role of the A new terminal has been opened in the Tokyo Narita International
Digital Airlines CIO. Airport (TYO) and a NetWare 6 server is needed.
You have hired your students to In this exercise, your team will install and configure a NetWare 6
add a NetWare 6 server to the server and add it to the existing DigitalAirTree.
Digital Airlines network.
Do the following:
Have students complete this 1. For each server on the network, run a basic health check to ensure
exercise on DA7, which should the tree is healthy.
have been left blank when you
reconfigured the classroom at the 2. From a workstation, run Deployment Manager and make sure the
beginning of Section 14. network is ready for a new server.
Disable or remove the second 3. On DA7, insert your NetWare 6 operating system CD into the
network interface in DA7. CD drive.
4. Boot the server.
5. When prompted, select one of the following:
❑ To install from your IDE CD, press I.
❑ To install from your SCSI CD, press S.
6. In the Welcome to NetWare Installation screen, use your arrow
keys to select Accept License Agreement.
7. Select Create a New Boot Partition.
8. In the First Hard Disk screen, select Continue.
9. Verify you want to create a boot partition by using the arrow keys
to select Continue.
10. Reboot your computer by pressing any key on the keyboard.
Be sure to give students diskettes 15. Configure advanced server installation parameters:
with the needed license files.
a. In the Server Properties screen, enter DA7 in the Server
Name field; then select Next.
b. Insert your license disk.
c. In the Encryption screen, browse to your license disk using
the browse button at the right of the Location field.
18. Browse to and select the server license (nlf); then select OK.
x The installation program detects any valid license file on your license
diskette. Verify that only one NetWare 6 server license is listed in the
Licenses to be Installed field. If additional licenses are listed, remove
them.
27. Allow the tree to sit for a few minutes; then run the following
processes with DSTRACE:
❑ Backlinker
❑ Schema sync
Make sure that both processes complete successfully.
(End of Exercise)
Summary
Objective Summary
Objective Summary
Index
A canonical 4-55
CD drive 14-22, 16-4
“A” records 4-55 Certificate Authority 6-9, 14-8
ACL 9-15 certificates 6-45, 6-47
address 4-82, 7-51, 12-23 class Intro-4, Intro-8, 4-23, 4-35, 8-8, 9-10,
administration 12-24, 12-26, 12-29, 9-14, 9-31–9-37, 11-1, 12-5, 14-19,
12-31–12-32, 12-40, 12-43–12-47, 14-21, 15-36
12-50, 12-52, 12-55, 12-57 client 3-1, 11-57, 14-21, 15-43
agent Setup-11, Setup-34, 4-85, 4-90, 4-95,
8-13 cluster 11-55, 12-1, 12-3
compatibility 1-4, 1-14, 1-18, 4-73, 4-86,
Apache Setup-25, Setup-38, 5-11, 11-47, 4-92–4-94, 4-99, 4-103, 7-42, 11-81,
11-73, 13-2–13-3, 13-6, 13-39 16-24
asynchronous 9-21 Compatibility Mode 4-86, 4-93, 4-99, 16-24
autodiscovery 4-72, 4-74 component Setup-35, 1-3, 1-8–1-9,
1-16–1-17, 3-17–3-18, 3-26–3-28,
B 3-43, 4-2, 4-7, 4-17, 4-22, 4-43, 4-73,
4-78, 4-88, 4-92, 4-110, 4-116, 5-7,
background 1-5, 3-22, 5-24, 5-29–5-30, 6-28, 6-9–6-10, 6-23–6-24, 6-39, 7-7,
8-6, 8-8, 8-19, 8-35, 9-6 8-19, 8-33, 10-10–10-12, 10-16,
10-34, 11-1, 11-55, 11-57–11-58,
backlink 9-7, 15-32, 15-42 11-64–11-65, 11-70–11-71, 11-75,
backup 12-30, 12-33, 12-45 12-1, 12-3–12-5, 12-12, 12-42,
bandwidth 1-11, 2-7, 4-86, 14-11 12-45, 12-47, 12-56, 12-58, 12-63,
13-1–13-4, 13-6, 13-15, 13-22,
binary 1-6, 6-45, 6-49–6-50, 6-57, 11-80 13-32, 13-39, 14-2, 14-4, 15-6,
bindery 3-2, 3-8, 3-21, 4-70, 7-40, 15-29 15-42, 16-33
block 5-16 compressed 3-45, 5-24, 15-10
bootable 16-4, 16-34 compression 5-15, 5-24–5-26, 5-55–5-56,
bound 4-29, 4-32, 4-63, 4-89–4-91, 4-97, 5-8, 12-35
8-10, 10-1, 15-10 concurrent 6-65, 14-17
confidential 4-31, 6-25, 6-77
C
cable Setup-26, Setup-33, 1-6, 1-9, 4-35
name
NLM Setup-12, Setup-14, Setup-16, options 3-45, 6-14, 12-11, 12-20, 12-23
Setup-21, Setup-36, 1-4, 4-3–4-6,
4-9–4-10, 4-25, 4-88, 4-91, 4-93,
4-98, 4-105, 4-110–4-111, 5-2, 5-8, P
5-11, 5-14, 5-28, 5-31, 5-41, 5-44,
5-54, 6-30, 6-61–6-63, 7-46, 8-3, packets 6-64
8-19, 9-4, 9-6, 9-10, 9-12, 10-10, parameters 5-10, 5-21, 7-49, 9-19–9-20, 11-9
10-12–10-13, 10-23, 10-27, 12-3, partition 6-28, 7-5, 7-32, 9-7, 9-11
12-12–12-14, 12-20–12-21, 12-24,
12-35, 12-38, 14-13, 14-15, 15-18, pass phrase 11-48
15-23, 15-26, 16-18 password 11-60, 13-30
NMAS 6-29, 6-33, 11-55–11-56 physical 4-8, 4-13, 4-97, 5-31–5-32, 6-61,
node 1-6, 4-1–4-2, 4-4, 4-6, 4-13, 4-40, 4-43, 6-65, 7-22, 7-25, 7-54, 8-34,
4-63, 4-106–4-108, 4-111, 16-24 8-36–8-37, 8-39, 8-42
Notes 14-17, 14-21 PKI 6-7, 6-9, 6-30, 6-33, 9-2
Novell PKIS 9-4, 14-8
Novell Cluster Services 12-3 PKIS entry 9-4
Novell Distributed Print Services 3-23, platform support module 16-14
4-5, 16-8 policies 11-43
Novell International Cryptographic Infra- pool 11-3, 13-18
structure 6-27, 11-56 port Setup-17, Setup-36, 4-26–4-29, 4-113,
Novell Modular Authentication Service 5-5, 5-9, 7-51, 8-4, 9-18, 9-23–9-24,
11-55 11-59, 11-66, 11-72–11-73, 11-76,
Novell Native File Access Pack 3-2, 11-1 11-84, 12-10, 12-23, 13-6,
13-8–13-9, 13-16–13-17, 13-24,
Novell Portal Services 11-69 13-32, 16-15, 16-18
Novell Storage Services 5-47, 11-1 port number 11-73, 13-8
NSS Setup-9, Setup-27–Setup-32, 1-12–1-13, post-installation 11-70, 15-34
5-22, 5-47–5-52, 5-57, 11-1–11-6,
11-8–11-11, 11-14–11-15, 11-17, post-migration 5-4, 15-32
11-23–11-39, 11-55, 11-89–11-90, pre-migration 5-4, 15-11, 16-9
13-18, 14-20, 15-4, 15-8, printer Setup-15–Setup-16, 3-1, 3-23, 4-6,
15-32–15-33, 15-37, 16-19–16-20, 7-2, 9-27–9-28, 9-38, 10-8, 10-33
16-22
processes 5-14, 5-18, 5-54
NWPA 16-15
processor 1-10, 5-2, 5-42, 5-49, 9-21, 16-3
property Setup-25, Setup-38, 3-6, 3-11, 3-16,
O 3-39, 3-43–3-44, 4-21, 4-68, 4-74,
4-80, 4-93–4-94, 4-99, 6-2, 6-41,
object Intro-8, 4-11, 4-49, 6-30, 6-51, 7-6, 6-43, 6-45, 6-47, 6-49–6-50,
7-23, 7-25, 7-27, 10-8, 10-11–10-12, 6-55–6-57, 9-29–9-30, 9-32–9-35,
11-30, 11-56 9-37, 10-20, 10-22, 11-6–11-8,
operating system 5-29
V
version 3-44, 9-5
view 9-26, 11-21
volume 11-3, 11-31, 12-27, 13-18
SYS 16-8, 16-19
W
web
server Setup-25, Setup-38, 4-62, 6-18,
6-24, 6-26, 11-73, 11-79, 11-81,
13-1–13-3, 13-5–13-22, 13-24,
13-31, 13-39–13-40
services 1-11, 4-31, 6-13, 13-1–13-5,
13-7–13-10, 13-17, 13-39, 15-3
Web Distributed Authoring and Versioning
11-79, 13-3
Windows
95/98 3-36
write 3-36, 3-43