Network+ Guide to Networks, Fourth Edition Chapter 10 Netware-Based Networking
Objectives <ul><li>Identify the advantages of using the NetWare network operating system </li></ul><ul><li>Describe NetWar...
Introduction to NetWare <ul><li>Novell released first NetWare in 1983 </li></ul><ul><ul><li>NetWare versions prior to 4.11...
Introduction to NetWare (continued) <ul><li>NetWare 6.5’s key features (continued): </li></ul><ul><ul><li>Multiple, integr...
Introduction to NetWare (continued) <ul><li>Noteworthy changes in NetWare 6.5: </li></ul><ul><ul><li>iManager </li></ul></...
NetWare Server Hardware Requirements  Table 10-1:  Minimum hardware requirements for NetWare 6.5 servers
A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel  <ul><li>Core of NetWare 6.5 OS </li></ul><ul...
A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) <ul><li>Load or unload NLMs throu...
A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) Figure 10-1:  A ConsoleOne client...
A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) Figure 10-2:  Remote Manager Heal...
NetWare File System <ul><li>Novell Storage Services (NSS): </li></ul><ul><ul><li>64-bit interface </li></ul></ul><ul><ul><...
NetWare File System (continued) <ul><li>NSS-based system may have up to four partitions </li></ul><ul><ul><li>One must be ...
NetWare File System (continued) Figure 10-3:  A storage pool in Novell Storage Services
eDirectory  <ul><li>NetWare 6.5’s directory database </li></ul><ul><ul><li>System for organizing and managing multiple ser...
eDirectory (continued) Figure 10-4:  eDirectory objects
eDirectory (continued) <ul><li>Schema: defined set of object classes and their properties </li></ul><ul><ul><li>Base schem...
eDirectory (continued) <ul><li>Trees and OUs (continued): </li></ul><ul><ul><li>Below root is an organization object </li>...
eDirectory (continued) Figure 10-5: A simple eDirectory tree
eDirectory (continued) Figure 10-6:  Ways of grouping objects in an eDirectory tree
eDirectory (continued) Figure 10-6 (continued):  Ways of grouping objects in an eDirectory tree
eDirectory (continued) Figure 10-7:  A more complex eDirectory tree
Planning for Installation <ul><li>Poor planning results in more work for installer, potential downtime for users, and head...
Planning for Installation (continued) <ul><li>Critical preinstallation decisions (continued): </li></ul><ul><ul><li>What w...
Installing and Configuring a NetWare 6.5 Server: The Installation Process <ul><li>Installed from CD or another server on n...
The Installation Process (continued) <ul><li>Tasks to set up server: </li></ul><ul><ul><li>Name server </li></ul></ul><ul>...
Establishing Users and Groups <ul><li>Need to add objects—including user objects—to eDirectory tree </li></ul><ul><ul><li>...
Establishing Users and Groups (continued) <ul><li>To start iManager, point browser to /nps/imanager.html page on server </...
Establishing Users and Groups (continued) Figure 10-8:  The iManager Create User window
Establishing Users and Groups (continued) Figure 10-9:  The iManager Create Group window
Client Services <ul><li>Several ways for different types of clients to access server and its resources </li></ul><ul><ul><...
Traditional Client Access <ul><li>Clients running Windows, Macintosh, and UNIX-type of OSs traditionally connected via a N...
Traditional Client Access (continued) Figure 10-10:  Novell Login dialog box
Native File Access <ul><li>NetWare capable of providing clients with direct access to NSS using clients’ native file acces...
Native File Access (continued) <ul><li>Client must run same protocols and software normally used to connect to a server na...
Native File Access (continued) Figure 10-11:  NetDrive connection dialog box
Browser-Based Access <ul><li>Users can navigate directories and manage files via Novell’s NetStorage tool </li></ul><ul><u...
Internetworking with  Other Operating Systems <ul><li>Novell has adopted LDAP directory standards </li></ul><ul><li>DirXML...
Internetworking with Other Operating Systems (continued) <ul><li>Nterprise Linux Services: Simplifies NetWare access for u...
Summary <ul><li>With NetWare 6.x, Novell has maintained its NOS’s traditional file- and print-sharing strengths while addi...
Summary (continued) <ul><li>Using ConsoleOne, administrators can manage servers, volumes, disks, and eDirectory objects </...
Summary (continued) <ul><li>eDirectory is NetWare 6.x’s system for organizing and managing multiple servers and their reso...
Summary (continued) <ul><li>User and Group objects can be created through ConsoleOne, Remote Manager, or iManager </li></u...
Upcoming SlideShare
Loading in …5
×

Linux Guide to Linux Certification

836 views
764 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
836
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
29
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Linux Guide to Linux Certification

  1. 1. Network+ Guide to Networks, Fourth Edition Chapter 10 Netware-Based Networking
  2. 2. Objectives <ul><li>Identify the advantages of using the NetWare network operating system </li></ul><ul><li>Describe NetWare’s server hardware requirements </li></ul><ul><li>Understand NetWare’s file system and directory structure </li></ul><ul><li>Plan for and perform a simple NetWare server installation </li></ul><ul><li>Explain how NetWare supports multiple clients and integrates with other network operating systems </li></ul>
  3. 3. Introduction to NetWare <ul><li>Novell released first NetWare in 1983 </li></ul><ul><ul><li>NetWare versions prior to 4.11 require IPX/SPX protocol suite </li></ul></ul><ul><ul><li>Refined to run over TCP/IP in version 4.11 </li></ul></ul><ul><li>NetWare 6.5’s key features: </li></ul><ul><ul><li>Support for multiple processors, multitasking, and SMP </li></ul></ul><ul><ul><li>Flexible use of virtual and physical memory </li></ul></ul><ul><ul><li>eDirectory </li></ul></ul><ul><ul><li>Simple, centralized management of multiple clients, resources, and services </li></ul></ul>
  4. 4. Introduction to NetWare (continued) <ul><li>NetWare 6.5’s key features (continued): </li></ul><ul><ul><li>Multiple, integrated Web development and delivery services </li></ul></ul><ul><ul><li>Support for multiple modern protocols </li></ul></ul><ul><ul><li>Excellent integration with other NOSs and support for many different clients </li></ul></ul><ul><ul><li>Remote client services </li></ul></ul><ul><ul><li>Built-in clustering services </li></ul></ul><ul><ul><li>Provisions for monitoring server performance, automatic backups, and resource utilization </li></ul></ul>
  5. 5. Introduction to NetWare (continued) <ul><li>Noteworthy changes in NetWare 6.5: </li></ul><ul><ul><li>iManager </li></ul></ul><ul><ul><li>DirXML </li></ul></ul><ul><ul><li>Capability for continuously backing up a server as it runs </li></ul></ul><ul><ul><li>Server Consolidation Utility </li></ul></ul><ul><ul><li>Popular open source Web development tools </li></ul></ul><ul><ul><li>Virtual Office </li></ul></ul><ul><ul><li>Branch Office </li></ul></ul><ul><ul><li>Nterprise Linux Services </li></ul></ul>
  6. 6. NetWare Server Hardware Requirements Table 10-1: Minimum hardware requirements for NetWare 6.5 servers
  7. 7. A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel <ul><li>Core of NetWare 6.5 OS </li></ul><ul><ul><li>Oversees all critical server processes </li></ul></ul><ul><ul><li>Started by server.exe, which runs from server’s DOS partition </li></ul></ul><ul><li>Takes advantage of SMP </li></ul><ul><ul><li>Up to 32 processors </li></ul></ul><ul><li>NetWare loadable modules (NLMs): Enable server to run variety of programs and services </li></ul><ul><ul><li>Each consumes some of server’s memory and processor resources </li></ul></ul>
  8. 8. A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) <ul><li>Load or unload NLMs through server’s console </li></ul><ul><ul><li>Enables network administrator to manage disks and volumes and modify server parameters </li></ul></ul><ul><ul><li>Monitor: text-based menu system </li></ul></ul><ul><ul><li>ConsoleOne: graphical menu system </li></ul></ul><ul><li>X Server: NetWare 6.5 server’s graphical desktop </li></ul><ul><li>Remote Manager: access console commands via Web browser on another network computer </li></ul>
  9. 9. A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) Figure 10-1: A ConsoleOne client window
  10. 10. A Closer Look at the NetWare 6.5 Operating System: NetWare Integrated Kernel (continued) Figure 10-2: Remote Manager Health Monitor
  11. 11. NetWare File System <ul><li>Novell Storage Services (NSS): </li></ul><ul><ul><li>64-bit interface </li></ul></ul><ul><ul><li>Files or directories up to 8 TB </li></ul></ul><ul><ul><li>A trillion files in single directory </li></ul></ul><ul><ul><li>File compression </li></ul></ul><ul><ul><li>User and directory space restrictions </li></ul></ul><ul><ul><li>Advanced fault-tolerance techniques </li></ul></ul><ul><ul><li>Efficient use of memory </li></ul></ul><ul><ul><li>Browser-based volume management </li></ul></ul><ul><ul><li>Split volumes over multiple storage devices </li></ul></ul>
  12. 12. NetWare File System (continued) <ul><li>NSS-based system may have up to four partitions </li></ul><ul><ul><li>One must be a DOS partition </li></ul></ul><ul><ul><ul><li>Primary boot partition </li></ul></ul></ul><ul><ul><li>Unlimited volumes on each partition </li></ul></ul><ul><li>Volumes are basis for organizing files and directories </li></ul><ul><li>NSS can combine free storage space from multiple storage devices into a storage pool </li></ul><ul><ul><li>Provides flexibility </li></ul></ul><ul><li>iManager: GUI tool used to manage objects </li></ul>
  13. 13. NetWare File System (continued) Figure 10-3: A storage pool in Novell Storage Services
  14. 14. eDirectory <ul><li>NetWare 6.5’s directory database </li></ul><ul><ul><li>System for organizing and managing multiple servers and their resources </li></ul></ul><ul><ul><li>Similar to Active Directory in Windows Server 2003 </li></ul></ul><ul><ul><ul><li>Treat every networked resource as separate object with distinct attributes </li></ul></ul></ul><ul><ul><ul><li>Objects belong to classes </li></ul></ul></ul><ul><li>eDirectory information stored in database that supports LDAP </li></ul><ul><ul><li>Compatible with other NOS and Internet directories </li></ul></ul>
  15. 15. eDirectory (continued) Figure 10-4: eDirectory objects
  16. 16. eDirectory (continued) <ul><li>Schema: defined set of object classes and their properties </li></ul><ul><ul><li>Base schema: simple schema installed by default with eDirectory </li></ul></ul><ul><ul><li>Extended schema: changes made to base schema </li></ul></ul><ul><li>Trees and OUs: </li></ul><ul><ul><li>Hierarchical organization </li></ul></ul><ul><ul><li>Tree can have one root </li></ul></ul><ul><ul><ul><li>Tree Object </li></ul></ul></ul>
  17. 17. eDirectory (continued) <ul><li>Trees and OUs (continued): </li></ul><ul><ul><li>Below root is an organization object </li></ul></ul><ul><ul><ul><li>Branches out in hierarchical arrangement of OUs </li></ul></ul></ul><ul><ul><li>A user is a leaf object </li></ul></ul><ul><li>Naming Conventions: </li></ul><ul><ul><li>Each eDirectory tree object has a context </li></ul></ul><ul><ul><ul><li>Indicates where object belongs in the tree </li></ul></ul></ul><ul><ul><ul><li>Consists of object’s OU names, arranged from specific to general, plus organization name </li></ul></ul></ul><ul><ul><li>Typeful and typeless contexts </li></ul></ul>
  18. 18. eDirectory (continued) Figure 10-5: A simple eDirectory tree
  19. 19. eDirectory (continued) Figure 10-6: Ways of grouping objects in an eDirectory tree
  20. 20. eDirectory (continued) Figure 10-6 (continued): Ways of grouping objects in an eDirectory tree
  21. 21. eDirectory (continued) Figure 10-7: A more complex eDirectory tree
  22. 22. Planning for Installation <ul><li>Poor planning results in more work for installer, potential downtime for users, and headaches for whomever supports server after installation </li></ul><ul><li>Critical preinstallation decisions: </li></ul><ul><ul><li>Where does the server fit in the eDirectory tree? </li></ul></ul><ul><ul><ul><li>After server’s context established, cannot change it </li></ul></ul></ul><ul><ul><li>What name will the server have? </li></ul></ul><ul><ul><li>How many and what kinds of NICs will the server use? </li></ul></ul><ul><ul><li>What protocols and network services should the server use? </li></ul></ul>
  23. 23. Planning for Installation (continued) <ul><li>Critical preinstallation decisions (continued): </li></ul><ul><ul><li>What will the Administrator password be? </li></ul></ul><ul><ul><li>What kind of disk controllers does the server have? </li></ul></ul><ul><ul><li>How many, how large, and what kind of volumes will the server require? </li></ul></ul><ul><ul><ul><li>Initially all free space on hard disk assigned to default volume, SYS </li></ul></ul></ul><ul><ul><li>What server pattern, or type, will the server be? </li></ul></ul><ul><ul><li>What kind of license do I have? </li></ul></ul><ul><ul><li>How can I remember all of this information? </li></ul></ul>
  24. 24. Installing and Configuring a NetWare 6.5 Server: The Installation Process <ul><li>Installed from CD or another server on network </li></ul><ul><li>Installation tasks: </li></ul><ul><ul><li>Select language </li></ul></ul><ul><ul><li>Select regional settings </li></ul></ul><ul><ul><li>Accept License Agreements </li></ul></ul><ul><ul><li>Choose Default or Manual installation </li></ul></ul><ul><ul><li>Prepare boot partition </li></ul></ul><ul><ul><li>Choose pattern </li></ul></ul><ul><ul><li>Select components to install (Manual installation) </li></ul></ul><ul><ul><li>Copy files </li></ul></ul>
  25. 25. The Installation Process (continued) <ul><li>Tasks to set up server: </li></ul><ul><ul><li>Name server </li></ul></ul><ul><ul><li>Enable cryptography </li></ul></ul><ul><ul><li>Specify network protocols for each network adapter </li></ul></ul><ul><ul><ul><li>If TCP/IP, specify server’s IP addressing information </li></ul></ul></ul><ul><ul><li>Enter server’s host and domain name </li></ul></ul><ul><ul><li>New eDirectory tree or add server to existing tree? </li></ul></ul><ul><ul><li>Enter eDirectory information </li></ul></ul><ul><ul><li>Choose an Administrator ID and password </li></ul></ul><ul><ul><li>Select login method </li></ul></ul>
  26. 26. Establishing Users and Groups <ul><li>Need to add objects—including user objects—to eDirectory tree </li></ul><ul><ul><li>Use ConsoleOne, Remote Manager, or iManager </li></ul></ul><ul><li>To run ConsoleOne, computer must have ConsoleOne client installed </li></ul><ul><ul><li>Running same protocols as server </li></ul></ul><ul><li>To run Remote Manager, point Web browser to IP address of server management interface </li></ul><ul><ul><li>By default, port 8008 on server </li></ul></ul>
  27. 27. Establishing Users and Groups (continued) <ul><li>To start iManager, point browser to /nps/imanager.html page on server </li></ul><ul><li>After eDirectory objects created, may want to change properties </li></ul><ul><li>Home directory: directory in which user can store files </li></ul><ul><ul><li>By default, users have full access privileges to files and subdirectories within their home directories </li></ul></ul>
  28. 28. Establishing Users and Groups (continued) Figure 10-8: The iManager Create User window
  29. 29. Establishing Users and Groups (continued) Figure 10-9: The iManager Create Group window
  30. 30. Client Services <ul><li>Several ways for different types of clients to access server and its resources </li></ul><ul><ul><li>Traditional client access </li></ul></ul><ul><ul><li>Native file access </li></ul></ul><ul><ul><li>Browser-based access </li></ul></ul>
  31. 31. Traditional Client Access <ul><li>Clients running Windows, Macintosh, and UNIX-type of OSs traditionally connected via a Novell client specifically designed for that client </li></ul><ul><ul><li>Client must have appropriate protocol suite installed </li></ul></ul><ul><ul><li>May require additional client software </li></ul></ul><ul><li>Novell provides utilities to automatically install client software (and updates) on all clients </li></ul>
  32. 32. Traditional Client Access (continued) Figure 10-10: Novell Login dialog box
  33. 33. Native File Access <ul><li>NetWare capable of providing clients with direct access to NSS using clients’ native file access protocols </li></ul><ul><ul><li>Users can browse folders and directories as if connected to server running same file access protocols </li></ul></ul><ul><li>All file access protocols installed by default </li></ul><ul><ul><li>Network administrator must set up network share for each protocol </li></ul></ul><ul><ul><ul><li>Via iManager </li></ul></ul></ul>
  34. 34. Native File Access (continued) <ul><li>Client must run same protocols and software normally used to connect to a server natively running its file access protocols </li></ul><ul><li>NetDrive: When installed on Windows clients, allows access to directories on NetWare 6.5 server </li></ul><ul><ul><li>Uses IPs such as HTTP and FTP </li></ul></ul>
  35. 35. Native File Access (continued) Figure 10-11: NetDrive connection dialog box
  36. 36. Browser-Based Access <ul><li>Users can navigate directories and manage files via Novell’s NetStorage tool </li></ul><ul><ul><li>Only need to have TCP/IP protocols installed and configured </li></ul></ul><ul><ul><li>Uses standard Internet application protocols </li></ul></ul><ul><ul><li>Users connect to URL on server </li></ul></ul><ul><ul><ul><li>By default, server’s IP address (or host name) plus /NetStorage </li></ul></ul></ul>
  37. 37. Internetworking with Other Operating Systems <ul><li>Novell has adopted LDAP directory standards </li></ul><ul><li>DirXML: Novell’s tool for integrating eDirectory and Windows Active Directory or Windows NT domain data </li></ul><ul><ul><li>Can synchronize Windows and Novell server’s directories </li></ul></ul><ul><ul><li>Can configure so that Active Directory or eDirectory is authoritative source for directory information </li></ul></ul>
  38. 38. Internetworking with Other Operating Systems (continued) <ul><li>Nterprise Linux Services: Simplifies NetWare access for users running Linux NOS </li></ul><ul><ul><li>Client tools for accessing eDirectory </li></ul></ul><ul><ul><li>Development tools for integrating Linux servers with DirXML </li></ul></ul><ul><ul><li>Browser-based file and print services </li></ul></ul><ul><li>Novell purchased two companies that write and distribute Linux software </li></ul><ul><ul><li>NetWare 7.0 will combine NetWare and Linux kernels </li></ul></ul><ul><ul><ul><li>Full compatibility </li></ul></ul></ul>
  39. 39. Summary <ul><li>With NetWare 6.x, Novell has maintained its NOS’s traditional file- and print-sharing strengths while adding browser-based management tools; popular open source Web development tools; a fast, efficient file system; and flexible methods for managing multiple servers, volumes, and storage objects </li></ul><ul><li>The NetWare Integrated Kernel is responsible for overseeing all critical NetWare server processes </li></ul><ul><li>NLMs are routines that enable the server to run a range of programs and offer a variety of services </li></ul>
  40. 40. Summary (continued) <ul><li>Using ConsoleOne, administrators can manage servers, volumes, disks, and eDirectory objects </li></ul><ul><li>iManager is the primary means of managing eDirectory objects in NetWare 6.5 </li></ul><ul><li>NSS offers many advantages over traditional file systems, including faster access, more efficient use of memory, file compression, support of files or directories as large as 8 TB, support for sharing a single application over multiple servers, capability to limit user directory and volume size, and browser-based management tools </li></ul>
  41. 41. Summary (continued) <ul><li>eDirectory is NetWare 6.x’s system for organizing and managing multiple servers and their resources, including storage devices, users, volumes, groups, printers, and so on </li></ul><ul><li>The word “schema” refers to eDirectory’s defined set of object classes and their properties </li></ul><ul><li>eDirectory follows a tree structure </li></ul><ul><li>Each object has a context that indicates where that object belongs in the eDirectory tree </li></ul><ul><li>NetWare recognizes two naming conventions for a user’s context: typeful and typeless </li></ul>
  42. 42. Summary (continued) <ul><li>User and Group objects can be created through ConsoleOne, Remote Manager, or iManager </li></ul><ul><li>Clients can connect to a NetWare 6.5 server, browse directories, and manage files in one of several different ways </li></ul><ul><li>NetWare 6.5 uses the DirXML tool to share data between eDirectory and Active Directory or Windows NT domains </li></ul><ul><li>Nterprise Linux Services integrates NetWare and Linux clients and servers </li></ul>

×