Which Bull servers are certified to use amounts of memory in excess of the posted limits for Red Hat Enterprise Linux 3, 4, or 5?

Updated -

Issue

  • The Red Hat Enterprise Linux (RHEL) version comparison guide located at https://access.redhat.com/articles/rhel-limits lists both a certified and a theoretical maximum memory limit for each version of RHEL.
  • Are there any Bull systems that have been certified to use memory amounts in excess of the posted limits?

Environment

  • Red Hat Enterprise Linux 3, 4 and 5

Resolution

  • The memory limits displayed on the version comparison guide (link above) are shown in “a/b” format. The “a” value indicates the supported limit for memory in that particular version of RHEL. The "a" value reflects the current state of system testing by Red Hat and its partners for mainstream hardware - this limit is based on actual testing and verification. actual tested and verified limit for memory in that particular version of RHEL. The “b” value indicates an untested theoretical maximum amount of RAM that may be addressable.
  • In some situations, hardware vendors work in conjunction with Red Hat to certify their systems using memory amounts greater than the verified maximum limits for general mainstream hardware (the "a" values) listed on the comparison guide. Bull and Red Hat have worked together in this manner to raise the supported memory limits on the systems in the table below.
  • Please note that the operating system versions listed in the table are the only versions that supports the extended memory amounts. If you wish to use a different version of the operating system with one of these servers, applicable supported limits will be the lower "a" values displayed on the comparison page.
Bull Server Model Certified Memory Amount Operating System Version
NovaScale R480 F2 1TB
  • RHEL5.5 or newer
  • RHEL5.4 with kernel 2.6.18-164.9.1 (from RHSA-2009-1670-1 *) or later

* Customers wishing to run RHEL5.4 must use a specific 5.4 errata kernel or newer. For more information about this topic, please see the following kbase article: http://kbase.redhat.com/faq/docs/DOC-28841 .

Comments