1 / 40


OpenServer 6 Hardware Overview Presented by: Alexander Sack, Senior Developer & Paul Hurford, Director Hardware Technologies. Agenda. Certified Hardware General SCO Hardware Database Statistics OpenServer 6 New Channel Partner Hardware Certification Programs Future Hardware Developments

Télécharger la présentation


An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.


Presentation Transcript

  1. OpenServer 6 Hardware OverviewPresented by:Alexander Sack, Senior Developer & Paul Hurford, Director Hardware Technologies

  2. Agenda • Certified Hardware • General SCO Hardware Database Statistics • OpenServer 6 • New Channel Partner Hardware Certification Programs • Future Hardware Developments • OpenServer 6 Specifics • Basic Requirements • General Device Guide • OSR5 vs. OSR6 • Q & A

  3. Certified Hardware information

  4. OpenServer 6 - Firsts • For the first time with any SCO OS Release, Computer Systems from Hewlett-Packard and Intel were certified and available the day of Product Launch • Fujitsu Siemens, IBM, Maxdata, and Toshiba followed on quickly with additional certifications • SCO Staff wanted the Hardware products for OpenServer to be current with this release. We eliminated all ISA, EISA, and PS/2 Bus types from this release, and selectively grandfathered individual products in each category of hardware to OpenServer 6

  5. OpenServer 6 – Available Hardware

  6. Computer Systems Certified for OSR6

  7. New Channel Partner Hardware Certification Programs

  8. Channel Partner Certification Programs • NEW Hardware Certification Programs for Channel Partners • SCO distributors and channel partners can now certify their white-box server solutions in the SCO Hardware Database. • Two new programs are available to list computer servers under your company name, and model number, and list them as Certified, or compatible products with SCO Operating System Platforms.

  9. Program Mechanics • Providing a low-cost program for SCO channel Partners required: • Creating a computer system test suite for automated test results collection and model data gathering. This program can be downloaded at: • http://www.sco.com/developers/hdk/testsuites/ • This new test called the System Certification Tests (SCT) and is also available on the optional services CD of OpenServer 6 and must be used for both the SLP, and RCP channel partner programs. • This test suite replaces the older Platform Load Test previously used for OEM system testing. • Getting agreement from participating OEM partners to permit pass-through Certifications without retesting by the channel partner

  10. Rebranding Certification Program (RCP) • Rebranding Certification Program (RCP) • This program is available to SCO authorized Distributors and Channel Partners who are customers of major OEM suppliers of computer systems. The channel partner purchases computer system components and then assembles a "White Box" system using their own model name and model number. If a participating original OEM has Certified a specific Server Board, the channel partner can re-certify the same system without retesting - using this program.  • Intel Servers available for the RCT Program: • http://wdb1.sco.com/hch_web/owa/hch_passthru_list_pkg.oem_list

  11. Rebranding Certification Program (RCP) • RCP Specifics • Eligible Products • Any computer system product manufactured by Intel Corporation that has been Certified by Intel for any SCO platform, and Release, and is submitted by an SCO authorized channel partner is eligibile for rebranding. • Submission and testing requirements • Model numbers submitted by the channel partner must be unique and can only describe one system. • The system board used for the certification can not be modified in any way from the original certified OSM platform. • The disk subsystem must be identical to the OEM certified product • BIOS changes from the original OEM Certified product are not permitted. Only BIOS revisions listed as certified in the original OEM certification are valid. • The microprocessor clock and speed must be the equal to or less than the OEM certified product. • The microprocessor must be from the same microprocessor family and the same type as the OEM certified product. • Any alterations to a submission from the original OEM certified model will be rejected.

  12. Computer System Listing Program • Computer System Listing Program (SLP) • This program is available to SCO authorized Distributors and Channel Partners who wish to list a computer system as "Compatible" in the SCO Hardware Database after testing the hardware for 24 hours. The channel partner assumes all support issues requested by their customers who purchased this system.

  13. Computer System Listing Program (SLP) • SLP Specifics: • Eligible Products • Any computer system product that will install the target SCO Operating System platform and release and pass a twenty-four (24) hour stress test using the SCO System Certification Tests (SCT) will be permitted listed in the CHWP. • System Listing requirements • The definition of Compatible Hardware is: “Compatible Hardware” is hardware that is represented to work with the product based on driver availability, but has not been certified by either the OEM vendor or SCO. Any vendor or Channel Partner of SCO whose hardware is listed as compatible becomes the technical support contact point for any issue that may arise. • The product model name and number must be specific and unique and can only describe one (1) system. • The exception to this is a suffix may be added to the model name/number to describe more than one speed of a processor • The SCO Channel Partner has installed and tested for twenty-four 24 hours the SCO operating system platform on each system family and release of the operating system that the product will be marked as compatible in the CWHP. • The SCO Channel partner agrees to support any customer of the channel partner in a timely manner if a problem or issue is discovered after the computer system has been listed.

  14. Certification • Whitebox Checklist • Full ISL is required for both programs • http://www.sco.com/developers/hdk/testsuites/ • SLP Program: • Run System Certification Tests for 24 hours for SLP Program • Collect System Data • Enroll in SLP Program • When tests PASS, submit to SCO for publication • RCP Program: Install target OS and SCT • collect system data • Enroll in RCP Program • Submit collected files to SCO for publication • By running the above tests you can ensure a smooth OSR6 deployment!

  15. Program Pricing

  16. System Certification Program Contact Information • For Further Information • Go to: • http://www.sco.com/chwp/programs/ • (or) Contact your SCO Sales Representative, • For SCO Americas customers phone - 1 (800) 726-6561 • For SCO Americas customers fax all RCP and SLP agreements to 1 (831) 439-9774 • For SCO International customers phone - +44 (0) 870 351 8626 • For SCO International customers fax RCP and SLP agreements to +44 (0) 870 351 8627 • Email sctadmin@sco.com for further information.

  17. Future Hardware Developments for OpenServer 6, and UnixWare

  18. Well, that’s a different Break-Out Session… • Come see us on August 8th in Room 102 • from 3:15 to 4:45

  19. OpenServer 6

  20. OpenServer 6 – A New Beginning • OSR6 has the most current hardware support of any release of OpenServer • Most of the administration of hardware devices is done automatically by the OS • Continue to use SCOadmin and the standard “mkdev” interfaces • Various certification tools are available to validate any new OSR6 server deployment

  21. OpenServer 6 - Basic Requirements

  22. OpenServer 6 - Basic Requirements • AMD64 and EMT64 CPUs are compatible with OSR6 in 32-bit mode. • Intel Hyperthreading Technology is fully supported on OSR6. • Dual Core Support: • Not in the product for FCS • Will arrive as a separate add-on that will allow OSR6 to recognize and distinguish between cores and logical processors. • Supports Hyperthreaded Dual-Core, e.g. Intel Extreme Edition • Intel Xeon certified platforms should be available at release • Licensed like Hyperthreading

  23. OpenServer 6 - Basic Requirements • IDE • Promise Fasttrak and Ultra TX2 • All Intel ICH based controllers • PCI IDE Controller Specification Revision 1.0 • SATA • Advanced Host Controller Interface (AHCI) • Found on ICH6M/R chipsets • Supports SATA II features such as NCQ and Hot-Plug • Whitebox chipsets plan AHCI support, e.g. SiS, Via, etc. • SAS • HP SAS has been certified. • Adaptec and LSI SAS support due in the Fall/Winter timeframe.

  24. OpenServer 6 - Basic Requirements • Intel Pro/100 and Pro/1000 • Note: OEMs rebadge and release their own version of this chipset. • Broadcom BCM5700 NetXtreme Gigabit Ethernet • Marvell Yukon PCI-E Chipset • Driver is available through the Marvell website. • Wireless Intel Centrino • Prism Wireless based chipset

  25. OpenServer 6 - Basic Requirements • OSR6 ships with latest stable X.org server • Supports almost every modern graphics chipset • Also provides support for a wider range of input devices. • Caveats: • If graphics chipset is not recognized, fall back to VESA • 3D Acceleration is typically not supported • No AGP/GART support

  26. General Device Guide

  27. General Device Guide • SCSI devices • MMC-3+ compliant CD/DVD devices • SCSI-2+ disk and tape • Fibre Channel now available for OpenServer 6 • ATA-4+ IDE devices • 48-bit LBA support is ATA-6+ feature • All SATA disks are ATA-6+ • Modern ATAPI drives are at least MMC-3 compliant • Serial/Parallel Cards • Any onboard serial or parallel chipset should get autoconfigured • Limited support for some higher end Digi and Connecttech boards

  28. General Device Guide • USB • Host Controller Interface (HCI) • EHCI, OHCI, and UHCI are all fully supported • Any compliant HCI chipset should just work • Mass Storage • If the device requires a special driver, we don’t support it! • Human Interface Devices (HID) • Compliant mice and keyboards should just work • Limited support for USB HID input with X.org, e.g. touchscreens

  29. OpenServer 5 vs. OpenServer 6

  30. OSR5 vs. OSR6 • mkdev • no need to use mkdev to force OSR6 to recognize new hardware • devices are auto-detected in most cases • new disks on a SCSI bus are detected automatically after a reboot • new controller instances are detected automatically after a reboot • mkdev hd is the only useful command, providing a simple front-end to fdisk and divvy • the rest of the hardware mkdev family ( tape, cdrom, fd, flopti, juke, ls120 ) are unused

  31. OSR5 vs. OSR6 • /dev/string/cfg • “/sbin/resmgr” • “echo pcilong | /usr/sbin/ndcfg” • “/sbin/sdiconfig –l” • “/etc/hw”

  32. OSR5 vs. OSR6 • Nodes • Most OSR5 style nodes should exist on OSR6 • Nodes are auto-created by idmknod/idmknodd/sdimkdev • SCOadmin hardware • OSR6 uses mainly OSR5 SCOadmin toolset • Ties into the mkdev script set • CPU administration • /sbin/psrinfo • /sbin/psradm

  33. OSR5 vs. OSR6 • Video • /etc/xorg.conf • SCOadmin Video now calls X.org configuration utility • NIC • SCOadmin Network • Same interface and procedure for adding and removing NIC cards. • Serial and Parallel ports • Hardware should be auto-detected, configure with SCOadmin Serial

  34. OSR5 vs. OSR6 • Disk • All hard disks on OSR6 are auto-detected • /etc/conf/cf.d/mscsi and /etc/conf/cf.d/hdlist are no longer needed • Hot-plug events for USB and AHCI are automatic and should show up via “/sbin/sdiconfig –l” output • Continue to use “mkdev hd” interface to manage slice and filesystem layout • Ghost Names

  35. OSR5 vs. OSR6 • MPIO • Something new for SCO OpenServer • Multi-Path I/O • Installed by default but disabled • Use “mkdev mpio” to enable/disable • Provides Redundancy

  36. Hardware Device Certification

  37. Certification • SCO Hardware Database (CHWP) • http://www.sco.com/chwp • Fully searchable database of certified hardware on OSR6 • Good place to start when building a whitebox solution • OSR6 is SVR5 so hardware certified on UW7 has been selectively grandfathered • If hardware is not listed, remember to check the OEM’s website for a driver.

  38. Device Certification • Drivers • http://www.sco.com/support/download.html • BTLD’s are no longer used, OSR6 uses UW7 style HBA diskettes and pkg format • Load HBA drivers during ISL via a floppy or ATAPI CD-ROM device • OEM vs. SCO supplied? • In general, use the SCO supplied driver as it has gone through the SCO certification process and has been extensively tested • Look at IHVVERSION package field to compare SCO vs. OEM driver

  39. We appreciate your attendance at this session, and your continued support of SCO Products Q&A • Contact Information: • Alexander Sack, alexs@sco.com – Senior Developer • Paul Hurford, paulhu@sco.com – Director, Hardware Strategies • Mike Drangula, drangula@sco.com – Senior Developer

  40. NOTES • Need to discuss fibre channel in relationship to OSR 6 - alex • Need to discuss Storage solutions from HP - alex • Need to elaborate on wireless futures for OSR6/UW7 - paul • Need to expound on new server certification Programs – paul

More Related