2. Lesson 12 – NETWORK SERVERS

3. Distinguish between servers and workstations. Choose servers for Windows NT and Netware. Maintain and troubleshoot servers. OVERVIEW

4. Servers incorporate several features not found in workstations. Servers serve up data/services to a number of users. DISTINGUISH BETWEEN SERVERS AND WORKSTATIONS

5. Server processors Bus capabilities RAM Disk subsystems Features of servers

6. Disk topologies: RAID I2O Server state monitoring Hot-swap components Features of servers

7. Xeon processors are: Optimized for server-type duties. More suited to a multiprocessor system. Server processors

8. Intel Clones: AMD K6 series of processors DEC Alpha HP PA-RISC PowerPC Server processors

9. Data on the server is moved in lots. A bus is the backbone for data transfer. Network cards, processors, and system’s memory are connected to the bus. The bus can handle five times more data than other system components. Bus capabilities

10. Types: Nonparity Parity Error Checking and Correcting (ECC) RAM

11. Nonparity: Eliminates the parity bit. Is unable to detect memory error. Is a cost-cutting technique. RAM

12. Parity: Uses an extra bit for every byte to store a checksum of the byte’s contents. Stops the system and reports an error if the checksum does not match when memory is read. The system is unable to correct errors. RAM

13. Error Checking and Correcting (ECC): Detects up to two bits of errors. Corrects one bit of error automatically. Provides added protection. RAM

14. Is the slowest component. Is most likely to be a bottleneck. A reliable disk configuration is of great importance. Disk subsystems

15. Redundant Array of Inexpensive Disks: Uses many disks to do the work of one. Spreads a server’s data across many disks. Disk Topologies: RAID

16. Disks can independently find data and send it to be assembled. Performance increases as you add more disks. The chance of disk failure increases as data is spread across disks. Disk Topologies: RAID

17. Intelligent I/O: Moves I/O processing from the computer’s processor to the disk controller. Relieves some of the computer’s central processor load. I2O

18. Higher-end servers monitor: Proper fan operation System voltage Memory errors In-case temperature Operating system hangs Computer case opening Server state monitoring

19. Can be replaced while the system operates. Are limited to disks, power supplies, and fans running in a redundant configuration. Hot-swap components

20. Defining needs Selecting servers Purchasing the system Installing servers CHOOSE SERVERS FOR WINDOWS NT AND NETWARE

21. Considerations: What is the life of the server? What job will the server perform? How many users will the server support? What are the needs of users? Defining needs

22. Considerations: How reliable must the server be? Will you use clustering for the server? How safe must data on the server be? Defining needs

23. Considerations: What are your backup plans? How do you plan to back up the server? How could demands on the server change? Will the server work with existing hardware? Defining needs

24. Compatibility is the basic prerequisite. The server should meet Novell’s/Microsoft’s hardware requirements. Selecting the server

25. The server brand should have: An established service organization. High-quality support. Technical support databases. In-house engineering. Selecting the server

26. Purchasing the system

27. Test server hardware. Read server documentation. Use automated tools provided by the manufacturer. Install an NOS. Installing servers

28. Run potential NLMs, NT services and processes, or UNIX/Linux daemons together during testing. Check for updates provided before installation. Installing servers

29. Reduce failures Resolve failures MAINTAIN AND TROUBLESHOOT SERVERS

30. Use reliable, tested servers and components. Reduce the number of server tasks (when possible). View the server’s error logs. Reduce failures

31. Install management software. Install special software that supports hot-swap in RAID. Shut down/restart the server periodically. Reduce failures

32. Take backups/test restores before a server goes into production. Preserve purchase data. Retain configuration details. Resolve failures

33. List software needed to rebuild the server. Maintain contact information for service on the server. Document configuration changes and error messages. Document anything special about the server/disk drive configuration. Resolve failures

34. Distinguish between a server and a workstation: Server processors Bus capabilities RAM Disk subsystems Disk Topologies: RAID I2O Server state monitoring Hot-swap components SUMMARY

35. Choose servers for Windows NT and Netware: Defining needs Selecting the server Purchasing the system Installing servers Summary

36. Maintain and troubleshoot servers: Reduce failures Resolve failures Summary