Printed Study Guide from http://www.Cramsession.com

NDS: Design and Implementation

SDLC (System Design Life Cycle) falls into four Phases:

NDS Preparation (Phase 1)

· Assemble and train your Project Team
1. Management

Project Manager	· Coordinate with NDS Expert to ensure efficient transition · Acquire appropriate resources and funding for project · Oversee design phase · Coordinate and manage the implementation
Testing Lab Coordinator	· Test applications for compatibility with Netware 5 · Setup Lab to simulate production environment · Obtain resources for lab from Project Manager · Plan pilot rollout with Project Manager
Education/Training Coordinator	· Train Project Team, Administrators, and users · Setup training lab · Work with Project Manager to establish Training & Education budgets

2. Hardware Specialists

Server Administrator	· Maintain network performance levels · Determine and plan pilot implementation · Implement upgrade and migration · Ensure implementation of logical time synchronization
Workstation Specialist	· Upgrade Client software on all workstations · Solve workstation hardware problems · Create implementation schedule for workstations · Assist NDS Expert with Profile and User login scripts · Determine method for user login and connection
Printing Specialist	· Provide appropriate access to printers · Assist NDS Expert with CAPTURE statements in login scripts · Upgrade workstation drivers and printing software · Enable Bindery Services for non-NDS aware printers

3. Software Specialist

NDS Expert	· Lead project team · Create NDS tree design · Design NDS security · Choose team members · Design partitions, replica placement, time synchronization, and accessibility · Communicate with departments and management to ensure thorough design that meets all needs.
Application Specialist	· Migrate existing apps into Netware 5 · Install new apps · Provide user access to applications · Update menu systems · Work with Testing Lab Coordinator to ensure applications are compatible with Netware 5 · Assist NDS Expert with System, Profile, and User login scripts
Connectivity Specialist	· Determine effects of routing on NDS · Decide on single or multiple protocols on network · Determine efficiency of bandwidth issues · Maintain seamless connectivity to hosts and other non-Netware 5 Operating systems

Gather NDS Information
1. Organizational chart
2. WAN Layout Map
3. Resources List
4. World Location map
5. Workflow Diagram
Determine Project Scope
1. Poll users & IT staff most impacted by design
2. Gather business information related to network design
3. Determine scope of the design process
4. Generate preliminary schedule.

Design (Phase 2)

· Two Design Models

1. Organizational
2. Technical

· Design Criteria

1. NDS Tree
· Upper Tree Design

Location Based Should be used when network spans more than one building or location

Function Based Organized according to OrgChart, workgroups, management, and departments

Required Documentation Naming Standards
WAN Topology
Location Map

· Lower Tree Design

Required Documentation Workflow Chart, OrgChart showing Departments, Management, and workgroupsUpper Tree Desgin

Container Sizes Should not exceed _____ Objects

Login Scripts Group users in common location requiring access to same resources to share login scripts

Optimize Upper & lower levels for easy management and productive for users
Create Naming Standards document

Document Naming standard for each Object Class in tree
Provide accurate Example for each Object Class
Specify Properties for each Object Class Selected

Foundation for partitioning and Time Synchronization
Administration
1. Centralized- One Admin or Admin group manages entire tree
2. Decentralized- Requires more levels in tree, separate administrators for portions of tree
Benefits gained by proper design include:
1. Partitioning & Replication can be designed successfully
  2. Easy tree walking (Name Resolution)
  3. Easily accommodate growth

2. Partitioning and Replica Strategy

Provides Scalability, fault tolerance, and resource access
Partitioning Truths:
- They are logical divisions of NDS that enable the database to be divided among several servers
- They contain only NDS objects and related data.
- Partitions cannot overlap
- Partitions should resemble a pyramid, having fewer partitions at the top of the tree than the lower tree.
- Only the first partition in a tree is created automatically.
- Partitions are named after their Upper most container.
Partitioning Considerations:
1. Default Scheme is sufficient if:
- Number of servers is 15 or less
- No WAN links
- 5000 or less objects
2. Custom Scheme:
- WAN links exist
- More than 15 servers have a replica of a partition- split the partition or reduce the number of replicas
Partition Size Considerations:

Advantages of Small Partitions	Disadvantages of Small Partitions
· Improves performance: Resources are closer to users. · Each server has smaller database · Partition sizes are smaller · Network traffic caused by user access is reduced · Dependency of single network server is reduced	· Need for synchronization is increased · Increased administrative overhead · Additional (SR) replicas · Network complexity is increased · Increases time for tree walking

Default Replication Guidelines:
1. An upgraded Novell 2.x or 3.x server receives a read/write replica for Bindery Services, regardless of the current replica count.
2. Max Replicas per server - 20
3. Max Partition Size - 3500 Objects
4. A partition can have multiple replicas
  - At least 2 or 3 Replicas per partition but NEVER more than
  - Never more than 35-40 Subordinate References
5. Only one replica of a given partition can be stored on a single server.
6. All replicas will participate in the replica synchronization for a partition.
Replica Placement Guidelines:
1. Be sure to replicate the [Root] partition.
2. Create replicas as needed for bindery services
3. Create a minimum of two or three replicas of each partition.
4. Keep replicas close to the users who access them whenever possible.
Replicas DO NOT affect Time Synchronization
Replicas created when:
1. Upgrading from Novell 2 & 3.x to Novell 5
2. Less than 3 replicas exist within partition
3. Server requires bindery servicesTo enable Binder Services : SET BINDERY CONTEXTMax # of containers per Server allowed to support Bindery: 16

Master (M)	Only one master replica permitted per partition. Manages synchronization updates of all other partition types.
Read/Write (RW)	Copy of Master partition. Used for fault tolerance. Can be read from and written to. Receives updates from Master partition. Can support authentication.
Read Only (RO)	NEVER created automatically. Used for searching & viewing objects only. Receives updates from Master replica.
Subordinate Reference (S/R)	NDS will place an S/R of a child partition on a server if that server holds a master, R/O or R/W replica of a parent partition but no replica of the child partition. Cannot be created manually.

NDS Manager allows you to:
1. Create, Merge, and Move Partitions
2. Add & Remove Partitions
3. Change Replica Types
WAN Traffic Manager (WTM)
1. Controls Server-to-Server traffic generated by NDS
2. Can restrict traffic based on cost, time of day, type of traffic, and/or a combination of these
3. Controls periodic events initiated by NDS like replica sync
4. Does not control events initiated by CNEs or users
5. Does not control non-NDS server-to-server traffic like time-sync

3. Time Synchronization

Default or Customized Time Sync
1. Default- if network does not span WAN links AND there are less than 30 servers in the tree.
2. Customized (Time Provider Group)- if WAN links are a consideration or if there are more than 30 servers in the tree
  - At least one server is Reference,
  - If infrastructure forces more than seven Primary time servers in a Time Provider Group, implement additional Time Provider Groups as necessary
  - Place Primary time servers near Secondary servers
  - Uses Configured Lists (Can use SAP for fault tolerance)
Service Advertising Protocol (SAP) -Default protocol used for time communication
Configured Lists: Reduces network SAP traffic, Allows you to specify which time server a server should contact.
Server Types:

Single Reference	1. Standalone Time server for entire network (up to 30 servers and no WAN connections) 2. All other servers are secondaries when this type is on network. 3. Cannot co-exist with Reference or Primary servers 4. Can use external source for time or internal clock 5. Default configuration for first server in the tree 6. Dos not poll any other server for time 7. Provides time to Secondary time servers and clients
Reference	1. Has a voting weight of 16 2. Advertises it is Time Provider 3. Will NOT adjust clock during polling 4. Provides time to Primary, Secondary Time Servers, and clients
Primary	1. Has a voting weight of 1 2. Polls reference and other primary time sources. 3. Gets Time From: Network time determined by time provider group. 4. Adjusts clock to 50% of corrected time per polling interval 5. Provides time to secondary time servers and clients.
Secondary	1. Default configuration for the second or subsequent servers in a tree. 2. Attempts to remain synchronized with only one time source. 3. Does not participate in voting. 4. Adjusts clock 100% to corrected time at each polling interval 5. Provides time to clients or server apps

Configuration & Application Files

TIMESYNC.NLM	Maintains each servers Universal Time Coordinated (UTC)
TIMESYNC.CFG	Lists time server sources when using configured lists.
NTP.NLM	Network Time Protocol (NTP) used in IP and IP/IPX environments Becomes time source for both IP and IPX servers. IPX servers must be set to Secondary servers when using NTP Supports two different time servers: Server and Peer
NTP.CFG	Configuration file created when NTP is installed. Allows configuration of NTP to act as SERVER or PEER type of time server.
MONITOR.NLM	If you want time servers to find other time servers on ANY tree, then set the Directory Tree mode to OFF and set SAP to ON.

Time Synchronization controls:
- NDS operations (sorts changes in NDS database)
- File system (Time stamps for files & directories)
- Messaging (Time stamps for E-mail)
- Printing (Print job flow & queue priorities)
- Resource access and security (network authentication, auditing, access to NDS resources)
- Network Applications (tracks when app/data files are created, modified, archived, and deleted.

4. NDS Accessibility Design

Accessibility Design results in a User Environment Plan (UEP).
1. Perform a Needs Analysis for User Accessibility
  - Physical resource needs
2. Develop Accessibility Guidelines
3. Create an Administrative Strategies Document
  - Z.E.N.Works and client configurations
    - Policies
    - Application Objects
  - Login Scripts
    - Container
    - Profile - allows users in different containers to share a login script
    - User - Use only if absolutely necessary
    - Default - only used if no user script exists. Located in "login.exe"
  - File system and security
    - Backup Admin -Can install servers and have all file system rights to all volumes and servers in the container
    - Server Admin - All Object rights in home container, should have File System rights
    - Special Use Admin - Used for servers not controlled by IS
    - Enterprise-Wide Admin - All rights to everything
    - Container Admin Role - Object rights to manage the role's home container
    - Password Admin - Has limited property rights for user objects, passwords, groups, login script, etc.
  - Legacy network services
    - Locate bindery-based resources
    - Which users, groups, and containers will need access to the bindery resources
  - Remote & Mobile users
    - Remote Users- Dialup users & users logged into one location & accessing resources at another location.
    - Mobile users- login to local workstations at locations other than the user's home container. This user requires access to local resources as well as resources from his/her own container.
    - Special Considerations
      1. Contextless login
      2. Knowledgeable user login
      3. Alias objects
      4. Workstation configurations to change name context
      5. Special login scripts

Implementation (Phase 3)

Project Scope
Training
NDS Implementation
- Naming Standards
- Tree
- Partitions & Replicas
- Time Synchronization
- Accessibility
Security and Auditing (Topic covered as CNA)
Client Migration
- Assess existing clients
- Determine Migration Strategy
- Share client software with admins
- Train Users
- Upgrade clients
Server Migration
Printing Migration
Application Migration
Pilot Program
Rollout

Management (Phase 4)

This phase was covered when you became a CNA

Special thanks to Burke Azbill for contributing the material for this Cramsession

Location Based	Should be used when network spans more than one building or location
Function Based	Organized according to OrgChart, workgroups, management, and departments
Required Documentation	Naming Standards WAN Topology Location Map

Required Documentation	Workflow Chart, OrgChart showing Departments, Management, and workgroupsUpper Tree Desgin
Container Sizes	Should not exceed _____ Objects
Login Scripts	Group users in common location requiring access to same resources to share login scripts