Public Works and Government Services Canada
Symbol of the Government of Canada

Common menu bar links

Annex A1

Microcomputer NMSO E60EJ-11000C/xxx/EJ

Annexes


ANNEX A1: TECHNICAL SPECIFICATIONS - UNIX

1.0 INTRODUCTION

This document addresses the requirement for three (3) UNIX System categories delineated using an industry recognized third-party benchmark test. These Systems must be based on the following 64-bit RISC or EPIC architectures:

  1. Category 1.0: Entry-Level

  2. Category 2.0: Mid-Range

  3. Category 3.0: High-End/Performance

1.2 The Systems must:

  1. Be commercially available;

  2. Be certified to operate under one of the currently released UNIX Operating System variants: IBM’s AIX, Hewlett-Packard’s HP-UX, or Oracle’s Solaris;

  3. Provide 100% binary compatibility to any of the existing UNIX OS variants identified in 1.2 (b);

  4. Not be embellished from the original purpose (e.g.: portable/mobile turned server or desktop/workstation turned server); and

  5. Be fully operational and in ready-to-use state, containing all major components and all requisite ancillary items. These include but are not limited to: Chassis / enclosure, motherboard / system board, processor / processor modules, memory / memory cards, UNIX Operating System, power supplies, cooling fans, internal / external cables to the System, I/O cables, etc. to allow the System to satisfy the requirements in the UNIX environment.

2.0 CONFIGURATIONS

2.1 UNIX CATEGORY 1.0 ENTRY-LEVEL:

Systems must meet or exceed the following technical specifications:

  1. Have a SAP 2-Tier SD benchmark score no less than SAPS: 1,100 & Number of Bench Users: 201.

  2. The performance score must be achieved operating under a single instance of a UNIX OS.

  3. Be available in either Tower/Pedestal or Rack-mount form factor chassis.

  4. Support a minimum of 32GB of ECC RAM.

  5. Have three (3) 64bit PCI-X and/or PCI-E slots.

  6. Include an integrated or add-on controller in either Ultra320 SSCI or SAS.

  7. Support RAID 0 and 1 (Mirroring) or equivalent (eg: RAID-Z).

  8. Have two (2) 10/100/1000 Base-T Ethernet ports (RJ-45) (Excluding management port).

  9. Support hot-plug disk drives.

  10. Include a hot-plug / hot-swap power supply.

  11. Include redundant power supply.

  12. Include hot-plug / hot-swap cooling fans.

  13. Include redundant or N+1 cooling fans.

  14. Have a minimum of four (4) Security & Encryption features identified under Section 12.

  15. Have a minimum of five (5) RAS features identified under Section 13.

  16. Support no less than one Partitioning / Virtualization level identified under Section 14.

  17. Support 100v to 240v or 200v to 240v AC.

  18. Include the corresponding UNIX Operating System License identified in 1.2 (b).

2.2 UNIX CATEGORY 2.0 MID-RANGE:

Systems must meet or exceed the following technical specifications:

  1. Have a SAP 2-Tier SD benchmark score no less than SAPS: 10,001 & Number of Bench Users: 2,001.

  2. The performance score must be achieved operating under a single instance of a UNIX OS.

  3. Be available in either Tower/Pedestal or Rack-mount form factor chassis.

  4. Support a minimum of 128GB of ECC RAM.

  5. Have three (3) 64bit PCI-X and/or PCI-E slots.

  6. Include an integrated or add-on controller in either Ultra320 SCSI or SAS

  7. Support RAID 0, 1 and 5 (Single Parity) or equivalent (eg: RAID-Z: raidz1).

  8. Have two (2) 10/100/1000 Base-T Ethernet ports (RJ-45) (Excluding management port).

  9. Support hot-plug disk drives.

  10. Include a hot-plug / hot-swap power supply.

  11. Include redundant power supply.

  12. Include hot-plug / hot-swap cooling fans.

  13. Include redundant or N+1 cooling fans.

  14. Have a minimum of six (6) Security & Encryption features identified under Section 12.

  15. Have a minimum of ten (10) RAS features identified under Section 13.

  16. Support no less than two (2) Partitioning / Virtualization levels identified under Section 14.

  17. Support 100v to 240v or 200v to 240v AC.

  18. Include the corresponding UNIX Operating System License identified in 1.2 (b).

2.3 UNIX CATEGORY 3.0 HIGH-END/PERFORMANCE:

Systems must meet or exceed the following technical specifications:

  1. Have a SAP 2-Tier SD benchmark score no less than SAPS: 26,001 & Number of Bench Users: 5,101.

  2. The performance score must be achieved operating under a single instance of a UNIX OS.

  3. Be available in either Tower/Pedestal or Rack-mount form factor chassis.

  4. Support a minimum of 192GB of ECC RAM.

  5. Have five (5) 64bit PCI-X and/or PCI-E slots.

  6. Include an integrated or add-on controller in either Ultra320 SCSI or SAS.

  7. Support RAID 0, 1, 5 (Single parity) and 6 (Double parity) or equivalent (eg: RAID-Z: raidz1 and raidz2).

  8. Have two (2) 10/100/1000 Base-T Ethernet ports (RJ-45) (Excluding management port).

  9. Support hot-plug disk drives.

  10. Include a hot-plug / hot-swap power supply.

  11. Include redundant power supply.

  12. Include hot-swappable cooling fans.

  13. Include redundant or N+1 cooling fans.

  14. Have a minimum of eight (8) Security & Encryption features identified under Section 12.

  15. Have a minimum of fifteen (15) RAS features identified under Section 13.

  16. Support no less than two (2) Partitioning / Virtualization levels where Level-3 is one of the two features supported identified under Section 14.

  17. Support 100v to 240v or 200v to 240v AC.

  18. Include the corresponding UNIX Operating System License identified in 1.2 (b).

3.0 CERTIFICATIONS - ALL CATEGORIES

3.1 HARDWARE CERTIFICATION:

  1. All high voltage electrical equipment supplied under the Standing Offer must be certified or approved for use in accordance with the Canadian Electrical Code, Part 1, before delivery, by an agency accredited by the Standards Council of Canada. All Systems must bear the certification logo that applies to the accredited agency. Any System not bearing a logo from the accredited agency described below will be considered non-compliant. Current accredited agencies include, but are not exclusively comprised of:

    1. Canadian Standards Association (CSA);

    2. Underwriters' Laboratory Inc. (cUL) (cULus);

    3. Underwriters' Laboratories of Canada (ULC);

    4. Entela Canada (cEntela);

    5. Intertek Testing Services (cETL);

    6. Met Laboratories (cMET); and

    7. OMNI Environmental Services Inc (cOTL).

    8. TUV Rhineland of North America (cTUV).

  2. Systems must comply with the emission limits and labeling requirements set out in the Interference Causing Standard ICES-003, "Digital Apparatus", published by Industry Canada. Systems that have obtained Industry Canada ICES-003 approval that have been assembled from tested components and have not undergone entire system testing will be considered non-compliant. All devices tested must bear the appropriate labels indicating trade name, model number, and the words indicating Industry Canada ICES-003 compliance.

  3. Systems must meet either (i) or (ii):

    1. System with a Published SAP SD 2-Tier Benchmark Scores:

      1. UNIX CATEGORY: 1.0U
        SAPS: 1,100 - 10,000
        Number Of Bench Users: 201 - 2,000

      2. UNIX CATEGORY: 2.0U
        SAPS: 10,001 - 26,000
        Number Of Bench Users: 2,001 - 5,100

      3. UNIX CATEGORY: 3.0U
        SAPS: 26,001 or higher
        Number Of Bench Users: 5,101 or higher

    2. System without a published SAP SD 2-Tier Benchmark Scores:

      1. The Offeror must propose a system with a published SAP score that meets the requirements of (c) (i) above for use as a reference for category placement. The reference system's SAP scores will be used for financial evaluation;

      2. The System must be the next generation product of the referenced system. An OEM product roadmap must be provided indicating this transition;

      3. The System must meet or exceed the technical specification of the reference system in all aspects with the exception of chassis size and number of installable local HDD

      4. Proof of the System's technical compliance must be included for the NMSO's mandatory requirements and for the reference system;

      5. The System must include the highest rated processor model in terms of price and performance; and

      6. If the reference system does not identify the number of processor cores, PWGSC will assume it was configured with the maximum number of processor cores per processor socket. The System must be configured as per the category requirements identified in the List of Products.

  4. The system must be directly supported and certified under the UNIX Operating System.

  5. The system must be IPv6 Gold Ready (Phase 2) Logoed.

4.0 Green Procurement Initiatives

  1. In support of the Canadian Federal Government’s Sustainable Development Strategy which includes policies on Green Procurement, system manufacturers must commit to a comprehensive, nationally recognized environmental standards for:

    1. The reduction or elimination of environmentally hazardous materials

    2. Design for reuse and recycling

    3. Energy efficiency

    4. End of Life Management for reuse and recycling

    5. Environmental stewardship in the manufacturing process

    6. Packaging

  2. All systems must be RoHS Certified.

  3. The OEM must be a member in good standing of EPSC – Electronic Product Stewardship of Canada.

  4. The OEM must be ISO 14001 certified.

  5. The OEM must have a “Contributor Membership” level to The Green Grid in good standing.

  6. The OEM must have a plan or strategy in place for achieving EPA’s Energy Star compliancy requirements for RISC or EPIC based systems.

  7. The OEM must have a plan or strategy in place for achieving 80 PLUS compliancy requirements for RISC or EPIC based systems.

  8. As Category technical requirements are modified and new Categories are added through the processes outlined in this NMSO, additional emerging requirements in support of Green Procurement and Sustainable Development will be introduced.

5.0 VALUE-ADDED VENDOR SUPPORT - ALL CATEGORIES

The following mandatory support services must be provided to support the System(s).

5.1 Personnel Support

  1. The Offeror must have on-staff, or through an authorized national dealer network, an existing and experienced technical support infrastructure, staffed with personnel that is trained on the Offeror's products. This technical support infrastructure must consist of no less than fifteen (15) support personnel available across Canada. Of those fifteen technical support personnel, a minimum of seven (7) must be UNIX Operating System support specialists; must be fully trained or certified and must be direct employees of the system manufacturer. The Offeror must demonstrate that the technical support personnel identified to fulfill the requirements have been formally trained or certified by the system manufacturer.

  2. All technical support personnel as specified above, and telephone support personnel, as specified below, must possess knowledge specific to the Offeror's exact configuration as offered. This must include accreditation for completing the system manufacturer's hardware training course and the UNIX Operating System described in paragraph (c) below.

  3. The Offeror must have an established hardware and OS training program for on-staff technical support personnel and third-party technical support organizations that is specific to the system brand and model (as indicated by the label on the system). The course curriculum must include hardware (which includes the model or model family bid), Operating System, management software, diagnostics and other service utilities as offered by the system manufacturer. This course must be available to federal government employees upon request.

5.2 Telephone Support

  1. The Offeror must provide end-user accessible, telephone-based, bilingual (French and English) technical support involving: Operating System issues, hardware trouble shooting, configuration support, any systemic software/hardware inter-operability issues and/or connectivity issues. The telephone support service must be performed by the manufacturer of the system (as defined by the brand name appearing on the system unit and in all supporting manuals and documentation). The telephone support staffs are obligated to support:

    1. All internal hardware components of the system;

    2. Operating System issues as supplied by the Offeror, as it relates to the Offeror's hardware;

    3. LAN infrastructure, regardless of supplier, as it relates to the Offeror's system; and

    4. All additional components if purchased from the Offeror.

  2. The bilingual telephone support line service must be active and must include the following:

    1. Be a toll-free service;

    2. Employ a minimum staff of ten support personnel, 24 hours a day, seven days a week dedicated to the Offeror's system platform;

    3. Offer this support service in both official languages (French and English) based on the caller’s preference;

    4. Be accessible from all parts of Canada, United States and from international locations where telephone service is available.

    5. Use a serial number tracking system that identifies all components, respective versions and driver versions of the installed system undergoing the troubleshooting. These components must include but are not limited to: motherboard / system board model and revision; firmware model and revision; memory / memory modules model and revision, controller model and revision; hard drive brand, model and revision; Operating System revision;

    6. Use an electronically shared, nationwide knowledge database to be used by support staff for all acquired troubleshooting expertise, product idiosyncrasies and configuration parameters for each specific component supplied;

    7. Provision to escalate issues to plant of manufacture;

    8. Provide a minimum 90% first call connection rate to a trained and qualified support personnel on calls defined as highest priority by the caller on systems where that level or service is specified in the warranty, during the warranty period, or where it has been purchased according to a service contract;

    9. Not exceed an initial on-hold time of more than five minutes on initial call; and

    10. Be available for the life of the product.

5.3 Website Support

The Offeror must have an Internet WEB site referencing the exact make and model(s) of System(s) offered and must contain the following:

  1. Support file areas offering download/upload access for drivers, setup and configuration files and other pertinent software specific to the exact model(s). These files, drivers and documents must be clearly identified as pertaining to the specific make and model of system;

  2. Message areas for technical assistance and problem diagnosis with support personnel if covered under the warranty or service contact on the system;

  3. Technical information library for downloading product information files, pertinent white papers, hardware service manuals or detailed technical manuals (that cover the exact model with all internal components described in the same document);

  4. FAQ (frequently asked questions) areas;

  5. Bulletins pertaining to product announcements, recalls, bug fixes, etc.;

  6. "Plain language" technical support question search engine with immediate response;

  7. Areas detailing system accessories and upgrades;

  8. Offer e-mail notification subscription services to alert clients of device driver revisions, firmware updates that pertain to the exact model family purchased;

  9. The features in articles (a) through (h) must be contained on the OEM's (as defined by the brand name appearing on the system unit and in all supporting manuals and documentation) web site. Links to other manufacturer's web sites cannot be used to achieve the mandatory requirements.

  10. The features in articles (a) through (h) must offer navigation links in French and English up to the final destination page. That destination page may be either French or English. Exceptions for uni-lingual content are allowed for technical descriptions, part number references and technical documentation.

  11. When the Offeror refers specifically to this NMSO on its web site, the information presented must be accurate in that only equipment and related prices listed on the CAG web site may be represented on the Offeror's web site as being available on its NMSO.

6.0 DETAILED SPECIFICATIONS

6.1 PROCESSORS:

All Processors must:

  1. Be any one of the following architectures: RISC and EPIC.

  2. Be the current released models from the OEM. The acceptable models are: Power6, Power7, SPARC64-VI, SPARC64-VII, UltraSPARC-T2, UltraSPARC-T2 Plus, Itanium-2 9100, and Itanium 9300.

  3. Function in a symmetrical multiprocessing (SMP) or Parallel processing mode.

  4. Systems must support ECC on the CPU cache.

6.2 BIOS OR FIRMWARE:

All BIOS or Firmware must:

  1. Be upgradeable through flash ROM technology.

  2. Have the ability to accept a previous version of the BIOS or firmware in the event of an incompatible or corrupted version.

6.3 RAM:

All RAM must:

  1. Be a minimum of 2GB DIMM;

  2. Be accessible for at least 3 years after award of the NMSO;

  3. Be manufactured by an ISO (International Standards Organization) 9001:2008 specs certified manufacturer. The ISO certification applies to the RAM manufacturer's manufacturing process and applies to both the RAM chip manufacturer and the DIMM assembly manufacturer; and

  4. All systems must have advanced ECC, chip-kill functionality or equivalent feature.

6.4 HARD DISK AND CONTROLLER - ALL CATEGORIES:

  1. Ultra320 SCSI

    1. If the proposed storage platform uses Ultra 320 SCSI hard disk drives, the hard disks must:

      1. Have a maximum average seek time of 5 ms. or less and a minimum spin rate of 15,000 revolutions per minute;

      2. Have physical bytes of storage as specified without the use of hardware or software disk compression utilities, as actual data space available to user;

      3. Support all of the capabilities and throughput of the U320 SCSI controller below;

      4. All drives must be hot-pluggable (without downing the system and without disruption of service when configured).

    2. The Ultra 320 disk controller must:

      1. Be a 64-Bit PCI-X running at a minimum of 66MHz or PCI-Express x4 wide;

      2. Support a burst transfer rate of 320MB per second.

  2. Serial Attached SCSI (SAS)

    1. If the proposed storage platform uses Serial Attached SCSI hard disk drives, the hard disks must:

      1. Have a maximum average seek time of 5 ms. or less and a minimum spin rate of 10,000 revolutions per minute;

      2. Have physical bytes of storage as specified without the use of hardware or software disk compression utilities, as actual data space available to user;

      3. Support all of the capabilities and throughput of the SAS controller below;

      4. All drives must be hot-pluggable (without downing the system and without disruption of service when configured).

    2. The SAS disk controller must:

      1. Be a 64-Bit PCI-X running at a minimum of 100MHz or PCI-Express x4 wide;

      2. Support a burst transfer rate of 600MB per second.

  3. Single Level Cell – Solid State Drive (SLC-SSD)

    1. If the proposed storage platform uses Solid-State-Drive hard disk device, the hard disks must:

      1. Have a sustained sequential read of up to 250MB/sec and a sustained sequential write of 70MB/sec;

      2. Have physical bytes of storage as specified without the use of hardware or software disk compression utilities, as actual data space available to user;

      3. Support all of the capabilities and throughput of the SAS controller below;

      4. All drives must be hot-pluggable (without downing the system and without disruption of service when configured).

    2. The SLC-SSD controller must be a 64-Bit PCI-Express supporting a burst transfer rate of 6GB/sec per SAS port.

7.0 EXPANDABILITY – ALL CATEGORIES:

7.1 UNIX CATEGORY 1.0 ENTRY-LEVEL:

The System must have:

  1. A SAP 2-Tier SD benchmark scores of no more than: SAPS: 10,000 and Number of Bench Users: 2,000;

  2. RAM expandable to a minimum of 32 Gigabytes (GB.) of ECC SDRAM; and

  3. No less than two (2) disk drive bays.

7.2 UNIX CATEGORY 2.0 MID-RANGE:

The System must have:

  1. A SAP 2-Tier SD benchmark scores of no more than: SAPS: 26,000 and Number of Bench Users: 5,100;

  2. RAM expandable to a minimum of 128 Gigabytes (GB.) of ECC SDRAM; and

  3. No less than four (4) disk drive bays.

7.3 UNIX CATEGORY 3.0 HIGH-END/PERFORMANCE:

The System must have:

  1. RAM expandable to a minimum of 192 Gigabytes (GB.) of ECC SDRAM; and

  2. No less than four (4) disk drive bays.

8.0 POWER SUPPLY - ALL CATEGORIES:

8.1 POWER SUPPLY - CATEGORY 1.0 ENTRY-LEVEL:

  1. The power supply must run on 100 - 240 volts AC 60Hz or 200 – 240 volts AC @ 60Hz.

  2. If the power supply fails (if the power supply is redundant) there must be a provision to communicate the condition through the system management utility to alert the network administrator.

  3. The power supply must be able to support a fully populated system on its own. A fully populated system is defined as having the maximum installed processors, all internal drive bays, all I/O slots or modules and memory slots populated.

  4. It must operate in temperature and humidity conditions of the normal business office environment, with no special air conditioning required.

  5. System must use a secondary system of one additional cooling fan. This fan is in addition to the power supply fan and any CPU fans (if offered). These fans must either be constantly operational or thermostatically controlled.

  6. All external cabling must be positively secured and resistant to damage.

8.2 REDUNDANT POWER SUPPLIES - CATEGORIES 2.0 MID-RANGE AND 3.0 HIGH-END/PERFORMANCE:

  1. The power supply must run on 100 - 240 volts AC @ 60Hz or 200 - 240 volts AC @ 60 Hz.

  2. If dual power supplies are included in the system, then at least one power supply must operate in a redundant fashion to the other(s) in that in the case of one power supply failing the other will continue to power the system without any interruption of services or performance. If three or more power supplies are included in the system, then they must be configured in an N+1 configuration so that in the case of one power supply failing, the others will continue to power the system without any interruption of services or performance.

  3. If the power supply fails there must be a provision to communicate the condition through the system management utility to alert the network administrator.

  4. If one power supply fails, the remaining functional power supply or supplies must be able to support a fully populated system on its own. A fully populated system is defined as having the maximum installed processors, all internal drive bays, all I/O slots or modules and memory slots populated.

  5. System must use a secondary system of additional cooling fans or provide sufficient cooling to support a fully configured system. If a secondary system of additional cooling fans is provided, these fans must be in addition to the power supply fan and any CPU fans (if included in Default System). These fans must either be constantly operational or thermostatically controlled.

  6. All external cabling must be positively secured and resistant to damage.

9.0 ETHERNET CONTROLLER - ALL CATEGORIES:

Network interface cards must:

  1. Come with a minimum of two-channel two-port 10/100/1000 MB/second unshielded twisted pair network interface controllers (NIC);

  2. Be 10Base-T, 100 Base-TX, and 1000-TX compliant and capable of auto-negotiating;

  3. Be capable of supporting Fault-Tolerance and Load-Balancing;

  4. Meet IEEE 802.3 and 802.3u compliancy;

  5. Support category 5 wiring; and

  6. Capable of being disabled.

10.0 REMOTE SYSTEM MANAGEMENT CONTROLLER - ALL CATEGORIES:

Each System must have available a remote management controller with requisite software. This controller must be manufactured or optimized by the system manufacturer and must bear the same brand label as the System manufacturer. Third party controllers will be considered non-compliant. The controller must:

  1. Provide continuous in-band and out-of-band communication, status/threshold and alert monitoring;

  2. Provide connectivity through an Ethernet LAN, serial port or USB port;

  3. Provide capability for virtual media (eg: CD-ROM, DVD-ROM;

  4. Provide capability allowing for event logging, on-demand remote system power-up, reboot, and power-down;

  5. Provide support for remote ROM updates and system re-configuration;

  6. Provide SSH (Secure Shell) connectivity using military grade ciphers (3DES or AES) and SSL (Secure Socket Layer) through 128-bit encryption while communicating via HTTP; and

  7. Use system management utilities and diagnostics (as detailed item 10.0) to trap out-of-band alerts and generate SNMP traps that will execute corrective measures remotely.

11.0 LIGHTS OUT SYSTEM MANAGEMENT AND DIAGNOSTICS - ALL CATEGORIES:

The System must have:

  1. A ROM based "SELF-TEST" procedure that is automatically executed on system power-up. This built-in test routine must test all installed memory and motherboard / system board based components (including ports), all I/O controller(s), all network interface controllers, and report all malfunctions during boot up.

  2. A system based diagnostics and system management utility that provides configuration information, status/threshold monitoring and failure/pre-failure alerting for:

    1. CPU temperature, thermal warning or failure conditions;

    2. Power supply detection, information and status;

    3. Fan detection, speed and status;

    4. Enclosure/Chassis temperature, thermal warning or failure conditions;

    5. System load and current sensors status; and

    6. Voltages.

  3. All of the above information must be accessible to an SNMP (Simple Network Management Protocol) compatible management service or other management tools/services providing same capabilities.

  4. If a CD/DVD-ROM is provided, it must be a pressed production media and must be written by or optimized by the systems' original equipment manufacturer (O.E.M.) (as defined by the brand name appearing on the system unit and in all supporting manuals and documentation) with a suitable label that identifies it as such, including the system manufacturer's name, applicable model(s) and the revision number. The system O.E.M. specific brand and model must be referenced through the software utility as well. Write-once CD/DVD (CDR/DVD-R or CD-RW/DVD-RW) will not be accepted. All other system diagnostics and system management utility will not be accepted.

12.0 SECURITY & ENCRYPTION FEATURES:

Systems must have a minimum number of industry-standard security ciphers. Category 1.0 must have a minimum of four (4), Category 2.0 must have a minimum of six (6), and Category 3.0 must have a minimum of eight (8) feature items. Acceptable features are:

  1. 3DES;

  2. HMAC or CMAC;

  3. AES;

  4. RC4;

  5. SHA-1;

  6. SHA-2;

  7. MD5;

  8. RSA to 2048 key;

  9. ECC; and

  10. FHMQV.

13.0 (RAS) RELIABILITY-AVAILABILITY-SERVICEABILITY FEATURES:

Systems must have a minimum number of RAS features. Category 1.0 must have a minimum of five (5), Category 2.0 must have a minimum of ten (10), and Category 3.0 must have a minimum of fifteen (15) feature items. Acceptable RAS features are:

  1. RAM: ECC & Extended ECC support;

  2. RAM: Data path integrity;

  3. RAM: SRAM and register protection;

  4. RAM: Configurable memory mirroring;

  5. RAM: Proactive memory scrubbing;

  6. RAM: Double-chip sparing;

  7. RAM: Offlining or Deconfiguation;

  8. Memory page retirement;

  9. CPU: Automatic Offlining or Deconfiguration;

  10. CPU: Error Protection;

  11. CPU: Automatic System Recovery w/ Instruction Retry;

  12. Hot-plug processor boards;

  13. Auto diagnosis and recovery;

  14. Service Processor to monitor system status;

  15. Redundant Management Processor;

  16. Live OS upgrade;

  17. Hardware partition;

  18. Fault-isolated dynamic domains / re-configurable partitions;

  19. System Bus: Redundant data, address, and response crossbar;

  20. Online Addition / replacement of I/O devices;

  21. I/O Bus / Bus Controller: Error checking / correcting of I/O Paths;

  22. I/O Boards / Slots: Dynamic de-allocation;

  23. Redundant network connections; and

  24. Hardened I/O drivers.

14.0 PARTITIONING / VIRTUALIZATION FEATURES:

Systems must support a minimum number of Partitioning / Virtualization Feature level: Category 1.0 must support no less than one (1) level, Category 2.0 must support no less than two (2) levels, and Category 3.0 must support no less than two (2) levels where Level-3 is one of the two features supported.

  1. Level-1 Partitioning / Virtualization Feature:

    System must:

    1. Run a minimum of two ‘isolated partitions’ each running its own instance of the OS, and each having dedicated CPU and memory; and

    2. Dynamically add/install, remove, replace, and re-configure core system components into the system while the OS and applications are running.

  2. Level-2 Partitioning / Virtualization Feature:

    System must:

    1. Run a minimum of two ‘isolated environments’ or ‘workloads’ within a single OS;

    2. Share/provide sharing resources between multiple partitions. This feature must allow for resources to flow between running partitions on the same physical system; and

    3. Perform a Virtual OS abstraction that provides a protected environment in which applications run. This feature must ensure applications are protected from each other to provide software fault isolation.

  3. Level-3 Partitioning / Virtualization Feature:

    System must:

    1. Run a minimum of eight ‘isolated partitions’ each running its own instance of the OS; each having the capability to expand / contract CPU, memory, Ethernet, and HBA resources in each running partition without requiring a partition or system to reboot;

    2. Provide the ability to move or migrate active/running workload or virtual machine from one physical system to another physical system while it continues to run;

    3. Perform resource allocation (eg: CPU, memory, I/O) into logical groupings or domains, where it provides the ability to create multiple discrete systems, each having their own OS, resources, and identity within a single physical system; and

    4. Dynamically add/install, remove, replace, and re-configure core system components into the system while the OS and applications are running. These partitions must be flexible, fault isolated that allows the administrator to run multiple applications/workloads and multiple copies/instances of the OS on a single system.

15.0 TECHNICAL DOCUMENTATION:

The manual(s) must consist of at least the following:

  1. User manual: The user manual for each System must include an accurate description of all hardware components and all their respective features. This must include descriptions of, and installation and configuration instructions for all components.

  2. Diagrams: For the purposes of orientation, and as a compliment to the setup and configuration instructions, the manual must have internal and external diagrams of the system as delivered. These diagrams must accurately illustrate external chassis (front and rear), rear chassis port configuration, hard drive cage assembly (for the purposes of hard disk configuration), cover removal, motherboard / system board, jumper locations, processor modules / cards and Memory boards and modules.

  3. The manual(s) must include documentation for power, power management, environmental or site preparation requirements.

  4. The manual(s) must include diagnostics/troubleshooting section referencing errors generated through power-on self-test (POST), system Firmware/BIOS and any other hardware errors. This section must also include appropriate explanations and troubleshooting advice for each error described.

  5. The features in articles (a) through (d) must be included in the same document, in the same format and their respective chapters must be referenced properly in a table of contents and indexes.

  6. If the system undergoes a major configuration change (e.g.: changes in motherboard / system board, Firmware/BIOS make, setup/configuration routines, external cabinet and chassis) during the life of the Standing Offer, the manuals must reflect that change in the form of a manual re-issue or an addendum shipped with the original manual. The addendum must be the same quality, typeface and page size as the original manual.

  7. The manuals must not describe components that are obsolete and are not included in the system.

  8. The manual(s) must be published by the system OEM with a suitable label that identifies it as such, including the system manufacturer's name and applicable model(s).

  9. The manuals described in this annex must be available electronically (contained on an accompanying CD/DVD-ROM or available on the manufacturer's web site specified in this annex). The manual must be bundled with an applicable reader. The reader must have a table of contents, index, hypertext links and word search capabilities. "Read me" files to be viewed by a text editor are unacceptable. The on-line versions must have the mandatory illustrations with the same level of detail as a paper equivalent. If a CD/DVD-ROM is submitted it must be a pressed production CD/DVD and must be written by the original equipment manufacturer with a suitable label that identifies it as such, including the manufacturer's name and applicable model(s) and the revision number.