ncla novell_Novell网络| 第2部分

ncla novell

NetWare 3.x (NetWare 3.x)

Starting with NetWare 3.x, was added to 32-bit protected mode, which allowed the operating system to eliminate the limit of 16mb memory NetWare 2.x This paved the way to support larger hard disk, since NetWare 3.x held in cache (copied) in full for the RAM File Allocation Table (FAT) and directory entry table (DET), resulting in improved performance.

从NetWare 3.x开始，已添加到32位保护模式，这使操作系统消除了16mb内存的限制。NetWare 2.x这为支持更大的硬盘铺平了道路，因为NetWare 3.x保留在缓存中(已复制)完整的RAM文件分配表(FAT)和目录条目表(DET)，从而提高了性能。

NetWare version 3 eased development and administration by modularization. Each functionality was controlled by a software module called NetWare Loadable Module (NLM), or loaded at startup or when needed. Became possible to add features like anti-virus software, backup software, database and web servers, support for extended file names (file names were limited to standard eight characters plus a three-letter extension, such as MS-DOS) or Macintosh style files.

NetWare版本3通过模块化简化了开发和管理。 每个功能都由称为NetWare可加载模块(NLM)的软件模块控制，或者在启动时或需要时加载。 可以添加功能，如防病毒软件，备份软件，数据库和Web服务器，对扩展文件名的支持(文件名仅限于标准的八个字符以及三个字母的扩展名，例如MS-DOS)或Macintosh样式文件。

Continue to be administered using NetWare utilities in text mode. The file system introduced by using the default Netware 3.x to Netware 5.x was NetWare File System 386, or 386 NWFS, which significantly expanded the capacity of volumes (1 TB, with up to 4 GB files) and could handle volume up to 16 segments that could span multiple physical disks. The volume segments could be added while the server was in use and the volume mounted, allowing the server to be expanded without interruption.

继续使用NetWare实用程序以文本模式进行管理。 通过使用默认的Netware 3.x到Netware 5.x引入的文件系统是NetWare文件系统386或386 NWFS，它显着扩展了卷的容量(1 TB，最多具有4 GB的文件)，并且可以处理卷到16个可跨越多个物理磁盘的段。 可以在使用服务器和安装卷时添加卷段，从而可以在不中断的情况下扩展服务器。

The NetWare Bindery services were initially used for authentication. It was a stand-alone database system, in which all data access and security of people residing on each server. When a facility contains more than one server, users had to authenticate to each individually, and each server must be configured with a list of all authorized users.

NetWare Bindery服务最初用于身份验证。 它是一个独立的数据库系统，其中所有数据访问和驻留在每台服务器上的人员的安全性。 当一个设施包含多个服务器时，用户必须分别对每个服务器进行身份验证，并且必须为每台服务器配置所有授权用户的列表。

“NetWare Name Services” was a product that extends the user’s data across multiple servers, and the concept of “domain” used by Windows is functionally equivalent to NetWare v3.x Bindery services with the addition of NetWare Name Services (or a two-dimensional database, with a flat namespace and a static scheme).

“ NetWare名称服务”是一种将用户数据扩展到多个服务器的产品，Windows使用的“域”概念在功能上等同于NetWare v3.x Bindery服务，并添加了NetWare名称服务(或二维)。数据库，具有平面名称空间和静态方案)。

For a short time Novell also marketed an OEM version of NetWare 3, called Portable NetWare, along with manufacturers such as Hewlett-Packard, DEC and Data General, which led to the source code for NetWare to run on their Unix operating systems. Portable NetWare had only marginal success.

在短时间内，Novell还销售了称为可移植NetWare的NetWare 3的OEM版本，以及诸如Hewlett-Packard，DEC和Data General这样的制造商，从而使NetWare的源代码可以在其Unix操作系统上运行。 便携式NetWare仅取得很小的成功。

In the era 3.x, Novell introduced its first high-availability clustering system, named NetWare SFT-III, which allowed a logical server to be “mirrored” on a completely separate physical machine. Implemented as a shared-nothing cluster, SFT-III with the operating system was logically divided into an I / O interrupt-driven engine and a generic event-driven system. The I / O engine serialize their interrupts (disk, network, etc.) In a combined flow of events that was fed to two identical copies of the engine system, through a fast link (typically 100 Mbit / s) between the two server. Because of its non-preemptive, the core operating system, stripped of the I / O is not deterministic, deterministically behaving like a big finite state machine.

在3.x时代，Novell推出了它的第一个高可用性群集系统，名为NetWare SFT-III，该系统允许在完全独立的物理计算机上“镜像”逻辑服务器。 作为无共享集群实现，带有操作系统的SFT-III在逻辑上分为I / O中断驱动引擎和通用事件驱动系统。 I / O引擎通过两个服务器之间的快速链接(通常为100 Mbit / s)将事件的组合(磁盘，网络等)序列化为事件的组合流，这些事件被馈送到引擎系统的两个相同副本。 由于其非抢占性，剥离I / O的核心操作系统不是确定性的，确定性地表现得像一个大型有限状态机。

The output of the two engine system was compared to ensure proper operation, and two copies were sent back to the I / O engine. Using the existing functionality of SFT-II software RAID in the kernel, the disks could be mirrored between the two machines without using special hardware. The two machines could be separated up to the maximum allowed by the linked server. In case of failure to a server or a disk, the server could survive, after a brief pause, take over client sessions transparently, since it had all the status information and should not, for example, replace the volumes ( a process in which NetWare was notoriously slow). Incidentally, SFT-III was the first version of NetWare in a position to make use of SMP hardware (I / O engine could optionally be run on a dedicated CPU).

比较了两个引擎系统的输出以确保正常运行，并将两个副本发送回I / O引擎。 使用内核中SFT-II软件RAID的现有功能，可以在两台计算机之间镜像磁盘，而无需使用特殊的硬件。 可以将两台机器分开，直到链接服务器允许的最大数量。 如果服务器或磁盘出现故障，则服务器可以在短暂的暂停后幸存下来，透明地接管客户端会话，因为它具有所有状态信息，并且不应该例如替换卷(NetWare在此过程中非常慢)。 顺便说一句，SFT-III是可以使用SMP硬件的NetWare的第一个版本(I / O引擎可以选择在专用CPU上运行)。

NetWare SFT-III, being ahead of its time in many ways, was a partial success. It should also be noted that the modern incarnation of NetWare’s clustering, called Novell Cluster Services (introduced with NetWare 5.0), is very different from SFT-III.

NetWare SFT-III在许多方面都处于领先地位，取得了部分成功。 还应注意，NetWare群集的现代化身，称为Novell群集服务(与NetWare 5.0一起引入)，与SFT-III有很大不同。

NetWare 3.x was designed to run all the applications on servers at the same level of memory protection, known as “ring 0”. This gave the best performance possible, but sacrificing reliability. The result was the possibility of system outages, (known as Abend, contraction of Abnormal End, abnormal end). From NetWare 5.x, software modules (NetWare Loadable Modules or NLM) could be allocated to the performance in different rings (rings) security processor, thus ensuring that a software error is not blocking the system.

NetWare 3.x旨在以相同的内存保护级别(称为“ ring 0”)运行服务器上的所有应用程序。 这样可以提供最佳性能，但会牺牲可靠性。 结果是系统中断的可能性(称为异常终止，异常终止收缩，异常终止)。 从NetWare 5.x，可以将软件模块(NetWare可加载模块或NLM)分配给不同环(环)安全处理器中的性能，从而确保软件错误不会阻塞系统。

In comparison, even up to Windows NT v4.0, many “recommended practices” included monthly or even weekly reboot of Windows servers to overcome the loss of memory.

相比之下，甚至在Windows NT v4.0之前，许多“推荐做法”包括每月或每周一次重新启动Windows服务器以克服内存损失。

NetWare 4.x (NetWare 4.x)

Version 4, released in 1993, introduced the Novell Directory Services (NDS), based on the X.500 protocol, which replaced the bindery services with a global directory service, where the infrastructure was described and managed in one place. In addition, NDS provides an extensible framework, allowing the addition of new types of objects. This allowed a single user authentication to NDS that governed access to any server in the directory tree. Users could then access the network resources, regardless of the server where it lies, even if the user license count was still tied to individual servers (the large companies could opt for a licensing model, which essentially allows an unlimited number of users for if allowed to Novell server to verify the total number of users)

1993年发布的版本4引入了基于X.500协议的Novell目录服务(NDS)，该目录服务用全局目录服务代替了平构数据库服务，该目录服务在一个地方进行了描述和管理。 此外，NDS提供了可扩展的框架，允许添加新类型的对象。 这允许对NDS进行单用户身份验证，从而控制对目录树中任何服务器的访问。 然后，即使用户许可证数量仍与单个服务器绑定，用户也可以访问网络资源，而不管服务器位于何处(大型公司可以选择许可模式，如果允许的话，实质上允许无限数量的用户使用)到Novell服务器以验证用户总数)

Version 4 also introduced several features and tools, such as transparent compression of files on the file system level encryption and RSA public / private.

第4版还引入了一些功能和工具，例如在文件系统级别加密透明地压缩文件和RSA public / private。

At this point, however, the strategic mistakes became clear.

然而，在这一点上，战略错误变得很明显。

战略错误 (Strategic errors)

The strategy of Novell NetWare 2.x and 3.x had been very successful. Before the arrival of Windows NT 3.5, Novell held 90% of the market for servers based on PC architecture. The assumption by Novell was to extend this domain by adding the directory services in NetWare 4.x NDS The crucial error was to make NDS a requirement and not an option. If NDS was an option for NetWare 4, or even a product purchased separately, many people would continue to use NetWare instead of switching to Windows NT. This was especially true for smaller networks, where the NDS, as conceptually they were far more advanced than Bindery services or Windows domains, will require some initial effort of training IT staff.

Novell NetWare 2.x和3.x的策略非常成功。 在Windows NT 3.5到来之前，Novell拥有90％的基于PC体系结构的服务器市场。 Novell的假设是通过在NetWare 4.x NDS中添加目录服务来扩展此域。关键的错误是使NDS成为一项要求，而不是一种选择。 如果NDS是NetWare 4的选件，甚至是单独购买的产品，许多人将继续使用NetWare而不是切换到Windows NT。 对于较小的网络来说尤其如此，因为从概念上讲，NDS比Bindery服务或Windows域要先进得多，在这些网络中，NDS需要一些初步的培训IT人员的工作。

While the design of NetWare 3.x and later provided a DOS partition to load the NetWare file system, this feature became a constraint, since new users preferred the Windows graphical user interface to have to learn DOS commands to build a NetWare server. Novell could remove this constraint while maintaining the technical design of NetWare 2.x, which installs the system files on a NetWare partition and allowed the server to boot from this, without having to create a bootable DOS partition. Novell finally added support for this mode in a Support Pack for NetWare 6.5.

尽管NetWare 3.x和更高版本的设计提供了一个DOS分区来加载NetWare文件系统，但是由于新用户更喜欢Windows图形用户界面来学习DOS命令来构建NetWare服务器，因此此功能成为了限制。 Novell可以在维护NetWare 2.x的技术设计时消除此限制，该技术设计将系统文件安装在NetWare分区上，并允许服务器从此启动，而无需创建可启动的DOS分区。 Novell最终在NetWare 6.5支持包中添加了对该模式的支持。

Given that Novell used IPX / SPX instead of TCP / IP, was poorly positioned to take advantage of the Internet in 1995. The first implementation of TCP / IP for NetWare 3.x, was not fully compatible with IPv4. This meant that the overrun on the NetWare server, for routing and access to the Internet, the router hardware (like Cisco) and Linux servers for the functionality of web servers.

由于Novell使用IPX / SPX代替TCP / IP，因此在1995年无法利用Internet。NetWare3.x的TCP / IP的第一个实现与IPv4并不完全兼容。 这意味着NetWare服务器的超支，用于路由和访问Internet，路由器硬件(如Cisco)和Linux服务器，以实现Web服务器的功能。

NetWare 4.02、4.1x NetWare小型企业版：Novell开始恢复 (NetWare 4.02, 4.1x NetWare for Small Business: Novell begins to recover)

Novell NetWare 4.2 released shortly after the release of NetWare 4.01, by introducing a simple installation of the NDS. In 1996, Novell released version 4.11, which included many enhancements that make the operating system easier to install, easier to operate, faster and more stable.

通过引入NDS的简单安装，在NetWare 4.01发布之后不久发布了Novell NetWare 4.2。 1996年，Novell发布了4.11版，其中包括许多增强功能，这些功能使操作系统更易于安装，易于操作，更快，更稳定。

This version also included the first fully 32-bit client for Microsoft Windows-based workstations, SMP support and NetWare Administrator (or NWADMIN NWADMN32), a graphical administration tool for NetWare.

此版本还包括第一个完整的32位客户端(用于基于Microsoft Windows的工作站)，SMP支持和NetWare管理员(或NWADMIN NWADMN32)，这是用于NetWare的图形管理工具。

Novell NetWare 4.11 fashioned with its Web server, supporting TCP / IP and the Netscape browser, in a bundle called IntranetWare. A version designed for networks with up to 25 people were baptized IntranetWare for Small Business and happy a limited version of the NDS and tools for simplified administration. IntranetWare was abandoned with NetWare 5.

Novell NetWare 4.11带有Web服务器，并在称为IntranetWare的捆绑软件中支持TCP / IP和Netscape浏览器。 为最多25人的网络设计的版本已通过IntranetWare for Small Business受洗，并希望使用NDS的有限版本和简化管理的工具。 IntranetWare被NetWare 5所放弃。

During this time Novell also realized the importance of building on the directory service, NDS, linking to them even its other products. The e-mail system, GroupWise, was integrated with NDS, and Novell released many other products “directory-enabled” as ZENworks and BorderManager.

在此期间，Novell还意识到了建立目录服务NDS(甚至将其其他产品链接到它们)的重要性。 电子邮件系统GroupWise与NDS集成在一起，Novell发布了其他许多“启用目录”的产品，如ZENworks和BorderManager。

At that point it was still tied to Novell IPX / SPX protocol dependence on PCN at that, but Novell began to recognize the request for the TCP / IP with NetWare 4.11, adding tools and utilities that make it easier to create intranets and networks connecting to the Internet. Novell attachments practical tools, such as Gateway IPX / IP, were used to facilitate the connection between IPX workstations and IP networks. He also began to incorporate Internet technologies and their support through features such as a native Web server.

那时，它仍然与Novell IPX / SPX协议对PCN的依赖关系联系在一起，但是Novell开始使用NetWare 4.11识别对TCP / IP的请求，并添加了工具和实用程序，这些工具和实用程序使创建与之连接的Intranet和网络更加容易。互联网。 Novell附件实用工具(例如网关IPX / IP)用于简化IPX工作站与IP网络之间的连接。 他还开始通过本机Web服务器等功能将Internet技术及其支持纳入其中。

Continued…

继续…

翻译自: https://www.eukhost.com/blog/webhosting/novell-network-part-2/

ncla novell