From unixreview.com:
http://www.unixreview.com/documents/s=7459/uni1037646901804/
Under the Hood of Xserve November 2002
Dorian Cougias
While it may look pretty, its still Unix, which is the underlying, driving force behind Apples new Xserve, Unix-based multiprocessor enterprise server. In a recent conversation with Tom Goguen, the Director of Server Software for Apple Computer, Tom clarified some issues about the Apple GUI interface and the way most Unix admins are accustomed to working:
The user interface that you know and love on the Mac OS X desktop obviously exists within the server software, however, everything that you need to do with the server, you can do remotely in a headless environment. Installing software, and setting up the server with all network configurations can be done by communicating with the server through HTTPS easily and securely. You can also telnet into the system through Secure Shell and run whatever scripts you have set up for management.
Weve made sure that you can access the server even if the network is down by adding a (DB9) serial port to the Xserve. You can hook the server up to a terminal concentrator and run SSH over the network and manage it that way if you want.
The Xserve is designed by default to run headless. The GUI is on the client (if you choose to use the client instead of a command line interface), not on the server. You communicate with the Xserve in a secure XML environment.
That sounds pretty Unix to me. And not only is it Unix, but its a truly open standard version of the BSD Unix operating system called Darwin that offers advanced networking, services such as the Apache Web server, and support for both Macintosh and Unix file systems. Open Directory is a part of this standard and its technologies form the foundation of how Mac OS X accesses all authoritative configuration information (users, groups, mounts, managed desktop data, etc.). Mac OS X and Mac OS X Server obtain this information via abstraction APIs, enabling use of virtually any directory system. One of the things you will notice is that if you go into the etc directory, youll find that its pretty barren because weve moved everything into an open directory standard, said Goguen, adding and weve published the source code as well. You can find all of the source code you are looking for at
http://developer.apple.com/darwin/.
Not only can the system be managed through Apples software or command-line interface, they are also shipping the servers with fully implemented SNMP MIBs, and direct support for HPs OpenView software. When we interviewed our customers about which heterogeneous management platform to work with first, HPs OpenView came to the top of the list, said Goguen.
A first in the server world, Apples new SMART hard-drive management system is able to leverage the Unix operating system to fully connect with their hardware. Unix admins running automatic notification will get an email, page, or phone message that a drive is heading for failure before it happens and can respond proactively. Starting with the pre-fail standards that IBM and Seagate has for hard drives, they asked what are the typical pre-fails that they have and how would that apply in the use of a server? Once they had their data set, they then processed this information into an XML file as a set of management rules. As soon as a drive meets the standards for a pre-fail bit at any one of the SMART data points, we announce that information to the SNMP MIB and management software explained Goguen. Because of the tight integration between Unix software and Apple hardware, notification lights are set on both levels and XML data is not only written to the log file, but to the hard drive itself.
Why would Apple want to write an XML file containing drive pre-failure info to the drive itself? Because the XML file contains all of the data about the exact point of failure (such as on head 4 of track 71 the drive had 10 retries). And the drive can then be sent back to Apple and swapped for a new drive. AppleCare gets the information that is contained both in the log and on the drive so we can learn for the future, Goguen explained. AppleCare is a part of the support package Unix admins can get with the server. The service, like Unix servers themselves, runs 24 hour a day and promises 4 hour response time meaning that within 4 hours you should have your answer for what is going on and how to fix the problem. Because this is a secure Unix system, and management can be done remotely, the admin can allow Apple technicians secure remote access for working on the system if need be, according to Goguen.
Secure, remote management. Close ties between hardware and software. Telnet through a serial port if all else fails. Even without a GUI interface, the Xserve is a beautiful Unix implementation if you appreciate the inner beauty of Unix.