Hubbry Logo
Sun FireSun FireMain
Open search
Sun Fire
Community hub
Sun Fire
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Sun Fire
Sun Fire
Sun Fire
View on Wikipedia
from Wikipedia
Sun Fire X4100 cluster
Sun Fire X4150 Motherboard
Sun Fire X4200 servers

Sun Fire is a series of server computers introduced in 2001 by Sun Microsystems (since 2010, part of Oracle Corporation). The Sun Fire branding coincided with the introduction of the UltraSPARC III processor, superseding the UltraSPARC II-based Sun Enterprise series. In 2003, Sun broadened the Sun Fire brand, introducing Sun Fire servers using the Intel Xeon processor. In 2004, these early Intel Xeon models were superseded by models powered by AMD Opteron processors. Also in 2004, Sun introduced Sun Fire servers powered by the UltraSPARC IV dual-core processor. In 2007, Sun again introduced Intel Xeon Sun Fire servers, while continuing to offer the AMD Opteron versions as well.

SPARC-based Sun Fire systems were produced until 2010, while x86-64 based machines were marketed until mid-2012. In mid-2012, Oracle Corporation ceased to use the Sun Fire brand for new server models. [1][2]

Operating systems

[edit]

UltraSPARC-based Sun Fire models are licensed to run the Solaris operating system versions 8, 9, and 10. Although not officially supported, some Linux versions are also available from third parties, as well as OpenBSD and NetBSD.

Intel Xeon and AMD Opteron based Sun Fire servers support Solaris 9 and 10, OpenBSD, Red Hat Enterprise Linux versions 3 - 6, SUSE Linux Enterprise Server 10 and 11, Windows 2000, Windows Server 2003, 2008, and 2008 R2 .

Model nomenclature

[edit]
Sun Fire V40z with 4× AMD Opteron CPU
Sun Fire T2000 (top)

Later Sun Fire model numbers have prefixes indicating the type of system, thus:

  • V: entry level and mid-range rackmount and cabinet servers (UltraSPARC, IA-32 or AMD64)
  • E: high-end enterprise class cabinet servers with high-availability features (UltraSPARC)
  • B: blade servers (UltraSPARC or IA-32)
  • X: rackmount x86-64 based servers
  • T: entry level and mid-range rackmount servers based on UltraSPARC T-series CoolThreads processors

When Sun offered Intel Xeon and AMD Opteron Sun Fire servers under the V-Series sub brand, Sun used an x suffix to denote Intel Xeon processor based systems and a z suffix for AMD Opteron processor based systems, but this convention was later dropped. The z suffix was also used previously to differentiate the V880z Visualization Server variant of the V880 server.

Sun's first-generation blade server platform, the Sun Fire B1600 chassis and associated blade servers, was branded under the Sun Fire server brand. Later Sun blade systems were sold under the Sun Blade brand.

In 2007, Sun, Fujitsu and Fujitsu Siemens introduced the common SPARC Enterprise brand for server products. The first SPARC Enterprise models were the Fujitsu-developed successors to the midrange and high-end Sun Fire E-series. In addition, the Sun Fire T1000 and T2000 servers were rebranded as the SPARC Enterprise T1000 and T2000 and sold under the Fujitsu brands, although Sun continued to offer these with their original names. Later T-series servers have also been badged SPARC Enterprise rather than Sun Fire.

Since late 2010, Oracle Corporation no longer uses Sun Fire brand for their current T series SPARC servers, and since mid-2012 for new X series x86-64 machines based on Intel Xeon CPUs. x86-64 server models which had been developed by Sun Microsystems before its acquisition, and were still in production, have all been rebranded as Sun Server X-series.

Sun Fire model range

[edit]

Some servers were produced in two versions, the original version and a later RoHS version. Since a general maintenance and upgrade guideline is that RoHS components and spares may be installed into the original non-RoHS versions of that server, the end-of-life (EOL) date of a server is deemed the EOL date of the RoHS version of that server in this listing.

UltraSPARC architecture

[edit]
Model Codename RU Max processors Processor frequency Max memory Max disk capacity EOL Date
280R Littleneck 4 2× UltraSPARC III/III Cu 750, 900, 1015, 1200 MHz 8 GB Two 3.5" FC-AL Disks January 2005
V100 Flapjack-LiteCD500 1 1× UltraSPARC IIe/IIi 500 (IIe), 550 (IIi), 650 MHz (IIi) 2 GB (4GB) Two 3.5" IDE Disks June 2006
V120 Flapjack2 plus 1 1× UltraSPARC IIi 550, 650 MHz 4 GB Two 3.5" SCSI Disks June 2006
V125 1 1× UltraSPARC IIIi 1.0 GHz 8 GB Two 3.5" Ultra160 SCSI Disks April 2008
V210 Enchilada 1U 1 2× UltraSPARC IIIi 1.0, 1.33 GHz 16 GB Two 3.5" Ultra320 SCSI Disks September 2007
V215 Seattle 1U 1 2× UltraSPARC IIIi 1.5 GHz 16 GB Two 2.5" SAS Disks April 2008
V240 Enchilada 2U 2 2× UltraSPARC IIIi 1.0, 1.28, 1.33, 1.5 GHz 16 GB Four 3.5" Ultra160 SCSI Disks September 2007
V245 Seattle 2U 2 2× UltraSPARC IIIi 1.5 GHz 16 GB Four 2.5" SAS Disks April 2008
V250 Enchilada 2P Tower 5 (90° tilted) 2× UltraSPARC IIIi 1.06, 1.28 GHz 8 GB Eight 3.5" Ultra160 SCSI Disks September 2005
V440 Chalupa 4 4× UltraSPARC IIIi 1.062, 1.28, 1.593 GHz 32 GB Four 3.5" Ultra320 SCSI Disks September 2007
V445 Boston 4 4× UltraSPARC IIIi 1.593 GHz 32 GB Eight 2.5" SAS Disks April 2008
V480 Cherrystone 5 4× UltraSPARC III Cu 900, 1050, 1200 MHz 32 GB Two 3.5" FC-AL Disks December 2005
V490 Sebring 5 4× UltraSPARC IV/IV+ 1.05, 1.35, 1.5, 1.8 GHz 64 GB Two FC-AL 3.5" April 2009
V880 Daktari 17 8× UltraSPARC III 750, 900, 1050, 1200 MHz 64 GB Twelve 3.5" FC-AL Disks October 2005
V880z Nandi 17 8× UltraSPARC III 750, 900, 1050, 1200 MHz 64 GB Twelve 3.5" FC-AL Disks March 2005
V890 Silverstone 17 8× UltraSPARC IV/IV+ 1.2, 1.35, 1.5, 1.8, 2.1 GHz 128 GB Twelve FC-AL 3.5" April 2009
V1280 Lightweight 8 12 12× UltraSPARC III Cu, IV, IV+ 900, 1050, 1200 (III Cu), 1050, 1200, 1350 (IV), 1500 MHz (IV+) 192 GB Two 3.5" UltraSCSI Disks October 2007
3800 Serengeti 8 8.5 8× UltraSPARC III Cu 750, 900, 1050, 1200 MHz 64 GB StorEdge D240 Media Tray August 2003
4800 Serengeti 12 17.5 12× UltraSPARC III, III Cu, IV, IV+ 750 (III), 900, 1050, 1200 (III Cu), 1050, 1200, 1350 (IV), 1500, 1800 MHz (IV+) 192 GB StorEdge D240 Media Tray May 2005
4810 Serengeti 12i 21 12× UltraSPARC III, III Cu, IV, IV+ 750 (III), 900, 1050, 1200 (III Cu), 1050, 1200, 1350 (IV), 1500, 1800 MHz (IV+) 192 GB StorEdge D240 Media Tray June 2003
6800 Serengeti 24 28 24× UltraSPARC III, III Cu, IV, IV+ 750 (III), 900, 1050, 1200 (III Cu), 1050, 1200, 1350 (IV), 1500, 1800 MHz (IV+) 384 GB StorEdge D240 Media Tray May 2005
12K StarKitty N/A 52× UltraSPARC III Cu, IV 900, 1050, 1200 (III Cu), 1050, 1200, 1350 (IV) MHz 288 GB Two SCSI Disks February 2005
15K StarCat N/A 106× UltraSPARC III Cu or 72× UltraSPARC IV 900, 1050, 1200 (III Cu), 1050, 1200, 1350 (IV) MHz 576 GB Two SCSI Disks February 2005
E2900 Amazon 2 12 12× UltraSPARC III Cu, IV or IV+ 0.9, 1.2 (III Cu), 1.05, 1.2, 1.35 (IV), 1.5, 1.8 GHz (IV+) 192 GB Two Ultra320 SCSI 3.5" January 8, 2009
E4900 Amazon 4 17.5 12× UltraSPARC III Cu, IV or IV+ 0.9, 1.05, 1.2 (III Cu), 1.05, 1.2, 1.35 (IV), 1.5, 1.8 GHz (IV+) 192 GB None January 8, 2009
E6900 Amazon 6 28 24× UltraSPARC III Cu, IV or IV+ 0.9, 1.05, 1.2 (III Cu), 1.05, 1.2, 1.35 (IV), 1.5, 1.8 GHz (IV+) 384 GB None January 8, 2009
E20K Amazon 20 N/A 36× UltraSPARC III Cu, IV or IV+ 0.9, 1.05, 1.2 (III Cu, 1.05, 1.2, 1.35 (IV), 1.5, 1.8 GHz (IV+) 576 GB None January 8, 2009
E25K Amazon 25 N/A 72× UltraSPARC IV or IV+ 0.9, 1.05, 1.2 (III Cu, 1.05, 1.2, 1.35 (IV), 1.5, 1.8 GHz (IV+) 1152 GB None January 8, 2009
T1000 Erie 1 1× UltraSPARC T1 1.0 GHz 32 GB One 3.5" SATA or Two 2.5" SAS January 2010
T2000 Ontario 2 1× UltraSPARC T1 1.0, 1.2, 1.4 GHz 64 GB Up to four 2.5" SAS January 2010
T5120 Huron 1U 1 1× UltraSPARC T2 1.2, 1.4, 1.6 GHz 128 GB Up to eight 2.5" SAS May 2012
T5140 Maramba 1U 1 2× UltraSPARC T2 Plus 1.2, 1.4 GHz 128 GB Up to eight 2.5" SAS August 2011
T5220 Huron 2U 2 1× UltraSPARC T2 1.2, 1.4, 1.6 GHz 128 GB Up to sixteen 2.5" SAS August 2011
T5240 Maramba 2U 2 2× UltraSPARC T2 Plus 1.2, 1.4 GHz 256 GB Up to sixteen 2.5" SAS November 2011
T5440 Batoka 4 4× UltraSPARC T2 Plus 1.2, 1.4 GHz 512 GB Up to four 2.5" SAS August 2012
The SunFire X4540 was used as Wikimedia servers in 2010

x86/x64 architecture

[edit]
Model Codename RU Max processors Processor models Max memory Max disk capacity GA Date - EOL Date
V20z Stinger 1 2× AMD Opteron 242, 244, 248, 250, 252, 270, 275 16 GB 2x SCSI 3.5" Ultra320 November 8, 2007
V40z Stinger 3 4× AMD Opteron 844, 848, 850, 852, 854, 856, 870, 875, 880, 885 64 GB 6× SCSI 3.5" Ultra320 March 30, 2007
V60z / V60x 1 2× Intel Xeon 2.8, 3.06, 3.2 GHz 6 GB 3× SCSI 3.5" Ultra320 January 2005
V65z / V65x 2 2× Intel Xeon 2.8, 3.06, 3.2 GHz 12 GB 6× SCSI 3.5" Ultra320 January 2005
X2100 Aquarius 1 1× AMD Opteron 146, 148, 152, 154, 156, 175, 180 8 GB 2× SATA 3.5" April 2007
X2100 M2 1 1× AMD Opteron 1218, 1214, 1210 8 GB 2× SATA 3.5"
X2200 M2 1 2× AMD Opteron 2218HE, 2222, 2218, 2210, 2220, 2214 64 GB 2× SATA 3.5"
X2250 1 2× Intel Xeon X5482, E5472, X5472, E5462, X5272, X5460, E5405, L5420 32 GB 2× SATA 3.5"
X2270 M2 1 2× Intel Xeon 5600 series 96 GB 4× SATA 3.5" 2010
X4100 1 2× AMD Opteron 248, 252, 254, 256, 275, 280, 285 16 GB 4× SAS 2.5" May 28, 2008
X4100 M2 1 2× AMD Opteron 2220, 2222SE, 2218HE, 2222, 2210, 2218, 2220SE, 2216 32 GB 4× SAS 2.5"
X4140 Dorado 1 2× AMD Opteron 2218 HE, 2222 64 GB 8× SAS 2.5"
X4150 Doradi? 1 2× Intel Xeon 5160, L5310, L5320, E5345, E5355, E5335, E5410, E5440 64 GB 8× SAS 2.5"
X4170 1 2× Intel Xeon 5500 series 144 GB 8× SATA/SAS 2.5" 2009
X4170 M2 1 2× Intel Xeon 5600 series 144 GB 8× SAS 2.5" 2010
X4200 2 2× AMD Opteron 248, 252, 254, 256, 275, 280, 285 16 GB 4× SAS 2.5" May 28, 2008
X4200 M2 2 2× AMD Opteron 2210, 2216, 2218, 2220SE, 2222SE, 2220, 2222, 2218HE 32 GB 4× SAS 2.5"
X4240 2 2× AMD Opteron 2218 HE, 2222, 2224 SE, 2347 HE, 2356 64 GB 8× SAS + 8× SATA 2.5" (up to 16 in total)
X4250 Aries 2 2× Intel Xeon X5482, E5472, X5472, E5462, X5272, X5460, E5405, L5420 64 GB 16× SAS 2.5"
X4270 2 2× Intel Xeon 5500 series 144 GB 16× SATA/SAS 2.5" 2009
X4270 M2 2 2× Intel Xeon 5600 series 144 GB 12× SATA/SAS 3.5" or 24× SATA/SAS 2.5" 2010
X4275 2 2× Intel Xeon 5500 series 144 GB 12× SATA/SAS 3.5" August 2009 - ?
X4440 2 4× AMD Opteron 8218, 8222, 8224 128 GB 8× SAS 2.5" or 6× SATA 2.5"
X4450 Argo 2 4× Intel Xeon E7220, L7345, E7320, E7340, X7350 128 GB 8× SAS 2.5" or 6× SATA 2.5"
X4500 Thumper 4 2× AMD Opteron 285, 290 16 GB 48× SATA 3.5"
X4540 Thor 4 2× AMD K10 128 GB 48× SATA 3.5"
X4470 3 4× Intel Xeon 7500 series 512 GB 6× SATA/SAS 2.5" 2010
X4470 M2 3 4× Intel Xeon E7-4800 series 1024 GB 6× SATA/SAS 2.5" 2011
X4600 4 8× AMD Opteron 856, 885 256 GB; 32x8 GB 4× SAS 2.5" August 8, 2007
X4600 M2 4 8× AMD Opteron 8218, 8220SE, 8220, 8216, 8360SE 512 GB; 64x8 GB 4× SAS 2.5"
X4800 5 8× Intel Xeon 7500 series 1 TB 8× SATA/SAS 2.5" 2010
X4800 M2 5 8× Intel Xeon 8800 series 2 TB 8× SATA/SAS 2.5" 2011

Sun Server / Oracle Server

[edit]

As of 2012, the x86 server range continued under the "Sun Server" or "Oracle Server" names.

Model RU Max processors Processor models Max memory Max disk capacity GA Date
X2-4 / X4470 M2 3 4× Intel Xeon E7-4800 series 1 TB 6× SAS 600 GB July 2011
X2-8 / X4800 M2 5 8× Intel Xeon E7-8800 series 4 TB 8× SAS 600 GB July 2011
X3-2 / X4170 M3 1 2× Intel Xeon E5-2600 series 512 GB 8× SAS 600GB April 2012
X3-2L / X4270 M3 2 2× Intel Xeon E5-2600 series 512 GB 24× SAS 600 GB April 2012
X4-2 1 2× Intel Xeon E5-2600 v2 series 512 GB 8× SAS-2 600 GB September 2013
X4-2L 2 2× Intel Xeon E5-2600 v2 series 512 GB 24× SAS-2 600 GB September 2013
X4-4 3 4× Intel Xeon E7-8895 v2 3 TB 6× SAS-2 1.2 TB April 2014
X4-8 5 8× Intel Xeon E7-8895 v2 6 TB 8× SAS-2 1.2 TB June 2014
X5-2 1 2× Intel Xeon E5-2600 v3 series 768 GB 8× SAS-2 1.2 TB December 2014
X5-2L 2 2× Intel Xeon E5-2600 v3 series 768 GB 24× SAS-2 1.2 TB December 2014
X5-4 3 4× Intel Xeon E7-8895 v3 3 TB 6× SAS-2 1.2 TB June 2015
X5-8 5 8× Intel Xeon E7-8895 v3 6 TB 8× SAS-2 1.2 TB July 2015
X6-2 1 2× Intel Xeon E5-2600 v4 series 768 GB 8× SAS-2 1.2 TB April 2016
X6-2L 2 2× Intel Xeon E5-2600 v4 series 768 GB 24× SAS-2 1.2 TB April 2016
X7-2 1 2× Intel Xeon Xeon Platinum 8160 1.5 TB 8× SAS-3 October 2017
X7-2L 2 2× Intel Xeon Xeon Platinum 8168 1.5 TB 12× SAS-3 October 2017
X7-8 5 8× Intel Xeon Xeon Platinum 8168 6 TB 8× SAS-3 October 2017
X8-2 1 2× Intel Xeon Xeon Platinum 8260 1.5 TB 8× SAS-3 April 2019
X8-2L 2 2× Intel Xeon Xeon Platinum 8268 1.5 TB 12× SAS-3 April 2019
X8-8 5 8× Intel Xeon Xeon Platinum 8268 6 TB 8× SAS-3 April 2019

See also

[edit]

References

[edit]
[edit]

Sun timeline

[edit]
Sun BladeSun FireSun FireSun EnterpriseSun Ultra EnterpriseSPARCserverSun Ultra seriesSun Ultra seriesSun Ultra seriesSun Ultra seriesSun Blade (workstation)Sun 386iSun Java WorkstationSun Ultra seriesSPARCstationSun-3Sun-2Sun-1
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Sun Fire

View on Grokipedia
from Grokipedia
Sun Fire is a series of enterprise-class server computers introduced by in 2001, initially centered on the SPARC-based UltraSPARC III processor architecture and designed to provide high reliability, scalability, and performance for demanding applications such as workloads running on the Solaris operating system. The inaugural models, unveiled at the trade show in , , on March 23, 2001—following a formal introduction in New York the day prior—included the midrange Sun Fire 3800, 4800, 4810, and 6800 servers, which offered mainframe-like capabilities including full hardware redundancy, redundant storage and network connections, and support for live operating system upgrades without downtime. These systems were engineered for 100% binary compatibility with existing Sun hardware and software, positioning them as top platforms for enterprise while targeting competitors like , , , and HP. Performance highlights included the 12-processor Sun Fire 4800 achieving 60,000 operations per second and the 24-processor Sun Fire 6800 reaching 109,000 operations per second on the SpecJBB benchmark. The Sun Fire lineup subsequently broadened to encompass entry-level rackmount servers, high-end systems like the Sun Fire 15K flagship announced in October 2001—which supported up to 106 UltraSPARC III processors for massive scalability in environments—and later x86-based models such as the Opteron-powered Sun Fire V20z and V40z servers launched in 2004, enabling 32-bit and for high-performance applications, , and cost-effective expansion. Following Corporation's acquisition of , completed on January 27, 2010, for $7.4 billion, the Sun Fire branding persisted on various and x86 servers to support ongoing enterprise deployments before transitioning to 's unified server portfolio.

History

Launch and Early Development

Sun Microsystems introduced the server line in 2001 as a successor to the series, emphasizing platforms built around the UltraSPARC III processor to address enterprise demands for scalable and reliable systems. The branding shift marked a new era for server offerings, focusing on enhanced interconnect technology like the Sun Fireplane, which delivered up to 9.6 GB/s sustained throughput for improved system performance. The initial announcement occurred at the trade show in , , on March 23, 2001, where Sun unveiled details of the midrange Sun Fire servers, positioning them as a direct competitor to IBM's pSeries and HP's Superdome lines in the Unix server market. Key early models included the Sun Fire 6800, a system supporting up to 24 processors, which achieved general availability on April 16, 2001. This launch highlighted Sun's emphasis on architecture advantages, such as superior reliability through features like hot-pluggable components and error-correcting memory, alongside of hardware with the Solaris operating system for optimized performance. In 2000 and 2001, Sun expanded the Sun Fire portfolio to and entry-level segments, with models like the rack-optimized Sun Fire 280R providing enterprise-class availability in a compact form factor for smaller deployments. First shipments of initial models, such as the 3800-6800 series, commenced in May 2001, with the integration of UltraSPARC III Cu variants announced in July 2001 for further performance gains. The servers featured tight Solaris OS integration, starting with Solaris 8 support, which enabled advanced resource management and compatibility with existing applications. A standout scalability innovation was dynamic system domains, allowing hardware partitioning into multiple isolated environments without downtime, a capability that predated similar features in competitors' high-end Unix servers by several years. This early development phase solidified Sun Fire's market positioning against and HP by underscoring SPARC's reliability—evidenced by sustained uptime in mission-critical environments—and Sun's end-to-end control over the hardware-software stack, reducing integration complexities for customers. Through the mid-2000s, these foundations enabled Sun Fire to capture significant share in , with dynamic domains and Solaris synergy driving adoption in sectors requiring fault-tolerant partitioning.

Oracle Acquisition and Phase-Out

In January 2010, Oracle Corporation completed its acquisition of for $7.4 billion in an all-cash transaction, marking a significant shift in the strategic direction of Sun's hardware portfolio, including the Sun Fire server line. This deal, finalized after regulatory approvals from the U.S. Department of Justice and the , integrated Sun's hardware expertise with Oracle's software dominance, emphasizing engineered systems that combined servers, storage, and database technologies for optimized performance. Under Oracle's ownership, the focus pivoted from standalone hardware innovation to tightly integrated solutions, such as Exadata and Exalogic, which bundled Sun Fire-derived components with Oracle to target enterprise centers. Sun Fire production continued post-acquisition, with SPARC-based T-series models, such as those powered by the SPARC T3 processor launched in September 2010, continued production until 2012 as Oracle introduced the new lineup at its OpenWorld conference. x86-based Sun Fire servers, including high-end models such as the X4800, persisted until mid-2012, when Oracle announced the phase-out of the Sun Fire branding for new products. In 2012, remaining lines were rebranded under Oracle's nomenclature, transitioning SPARC systems to the Oracle SPARC T-series and x86 variants to the Oracle Sun Server X-series, effectively ending the Sun Fire era as a distinct product family. For instance, the Sun Fire X4800 server achieved end-of-life status in May 2012, ceasing new orders and shipments. Oracle provided legacy support for Sun Fire systems through its Premier Support program, which concluded between 2018 and 2023 for most models depending on their release date; for example, the Sun Fire X4800's Premier Support ended on April 19, 2022. Extended Support from Oracle was available for an additional three years in some cases, but for select x86 variants, third-party maintenance providers offered continued service up to 2025, ensuring operational continuity beyond official end-of-support dates. This phase-out reflected broader industry trends, as Oracle redirected resources toward cloud infrastructure and pre-integrated appliances, diminishing the role of standalone Sun Fire hardware in favor of subscription-based cloud services and hybrid systems.

Model Nomenclature

System Type Prefixes

The Sun Fire server line employed a consistent prefix system in its model nomenclature from 2001 to 2012 to denote system form factors, levels, and intended market segments, applicable across both SPARC-based and x86-based architectures. This approach facilitated rapid identification of a server's target use cases, from small-scale deployments to large enterprise environments. The "V" prefix designated volume or entry-level servers, typically low-cost, rackmount systems aimed at small and medium-sized businesses (SMBs) or departmental applications, such as the Sun Fire V20z, a 1U Opteron-based server offering basic compute and storage for cost-sensitive environments. In contrast, the "E" prefix indicated enterprise or high-end servers designed for mission-critical, large-scale operations with advanced high-availability features, exemplified by the Sun Fire E25K, a cabinet supporting up to 72 UltraSPARC IV+ processors for massive scalability. The "B" prefix denoted servers within modular for dense, shared infrastructure, as seen in the Sun Fire B200x series, which integrated multiple compute nodes into a compact for efficient resource utilization in clustered setups. Additionally, the "X" prefix was reserved for x86-specific servers, often optimized for storage or , such as the Sun Fire X4500 (codenamed Thumper), a 4U system with up to 48TB of internal storage for data-intensive workloads. The "T" prefix highlighted throughput-oriented servers emphasizing multi-core or multi-threaded designs for parallel processing, like the Sun Fire T2000, powered by the UltraSPARC T1 processor with eight cores and 32 threads to maximize application throughput under power constraints. These prefixes remained uniform across the product lines, enabling users to discern scalability and deployment suitability at a glance. Following ' 2007 partnership with , the high-end models underwent a partial rebranding to SPARC Enterprise (e.g., M-series for former E-series equivalents), yet the core Sun Fire prefix conventions persisted for continuity in naming T-series and x86 lines. This system was phased out around 2012 after Oracle's acquisition of Sun in , transitioning to simplified "Sun Server" branding that dropped the Fire designation and prefixes for newer x86 models.

Processor Suffixes and Evolution

The processor suffixes in Sun Fire model names were introduced to denote specific CPU architectures during the early expansion into x86 systems, allowing differentiation without altering established system type prefixes. In , amid a market shift toward open architectures, Sun launched its first x86-based servers using the processor, incorporating the "x" suffix in models like the Sun Fire V60x and V65x, which supported up to two processors at speeds of 2.8 to 3.2 GHz. The following year, in 2004, the "z" suffix was employed for Opteron-based variants to highlight their architecture, as in the Sun Fire V20z (dual Opteron) and V40z (quad Opteron) servers. UltraSPARC-equipped Sun Fire models, such as the V440 with up to four UltraSPARC IIIi processors, omitted any such suffix, relying solely on the base nomenclature. This suffix convention enabled clear identification of processor types alongside system form factors (e.g., "" for volume servers), supporting compatibility assessments for software and peripherals across the lineup. By preserving core prefixes, the approach minimized disruption to existing naming while signaling architectural shifts. The evolution of these suffixes emphasized simplification over time. After 2006, Sun discontinued the "x" and "z" designations, standardizing on the "X" prefix for all models regardless of or processors, as demonstrated by the 2006 Sun Fire X4100 (up to two ) and the 2007 Sun Fire X4150 (dual ). In 2007, integration with Fujitsu's Enterprise series introduced M-class naming for high-end systems, such as the M4000 with 64 VI processors, eliminating processor suffixes entirely in favor of series-based identifiers. Following 2008, Sun Fire's T-series emphasized Niagara-based (UltraSPARC T) processors without introducing new suffixes, continuing the streamlined approach in models like the T5440 with up to four UltraSPARC T2 Plus chips. This progression led to the complete abandonment of processor suffixes by 2012, aligning nomenclature with broader product unification.

Server Models

UltraSPARC-Based Servers

The Sun Fire series of UltraSPARC-based servers, introduced starting in 2001, represented ' enterprise-grade computing platforms built around the RISC architecture, emphasizing reliability, scalability, and integration with Solaris for demanding workloads. These systems ranged from entry-level to high-end configurations, supporting up to 106 processors in the largest models like the Sun Fire 15K, though later iterations such as the E25K scaled to 72 processors. They featured hot-swappable components for , including redundant power supplies, fans, and I/O modules, enabling minimal during maintenance. The inaugural midrange models, launched in 2001, included the Sun Fire 3800 (up to 8 UltraSPARC III processors at 750-900 MHz, 64 GB RAM, 8U rackmount), 4800 and 4810 (up to 12 processors at up to 900 MHz, 96 GB RAM, 8U), and 6800 (up to 24 processors at up to 900 MHz, 192 GB RAM, 10U). These provided mainframe-like and dynamic domains for up to 4 (3800), 6 (4800/4810), or 8 (6800) isolated partitions. High-end models like the Sun Fire 12K (up to 60 processors, 480 GB RAM, 18U) and 15K (up to 106 processors, 864 GB RAM, 25U) extended with up to 16 domains for partitioning. Key entry-level models included the Sun Fire 280R, released in 2002, which supported up to two UltraSPARC III Cu processors at speeds of 900 MHz to 1.2 GHz, with a maximum of 8 GB RAM across eight DIMM slots. The Sun Fire V245, launched in 2003 as a 2U rackmount server, offered up to two 1.5 GHz UltraSPARC IIIi processors, 16 GB of DDR-1 , and four hot-swappable 2.5-inch SAS drives for entry-level enterprise tasks. Midrange options like the Sun Fire (2005) and T2000 (2005) introduced the Niagara family of processors; the featured a single 1.0 GHz UltraSPARC T1 with eight cores and 32 hardware threads, supporting up to 32 GB of DDR-2 in a 1U form factor, while the T2000 scaled to four such processors for 32 cores and 128 threads, with up to 64 GB RAM. High-end models such as the Sun Fire E20K and E25K, released between 2004 and 2006, provided massive scalability with up to 36 and 72 UltraSPARC IV processors respectively, each board supporting four CPUs, and dynamic system domains for partitioning into up to 9 or 18 isolated environments. This domain architecture allowed independent OS instances with fault isolation, enhancing security and for multi-tenant setups. The T2000 was the first production server to implement Sun's CMT technology via the UltraSPARC T1, enabling efficient handling of up to 128 concurrent threads for throughput-oriented applications. These servers incorporated Solaris-specific optimizations, such as integrated J2EE support through and zones, which virtualized environments without performance overhead, ideal for consolidating Java-based workloads. Scalability spanned from single-processor entry systems to high-end configurations, leveraging the RISC-based architecture's advantages in instruction efficiency and error correction for mission-critical operations. Common use cases included database servers for deployments, where dynamic domains isolated transactions, and (HPC) for scientific simulations, benefiting from SPARC's balanced pipeline and multithreading for parallel processing. Most UltraSPARC-based Sun Fire models reached end-of-life (EOL) between 2005 and 2010, with the 280R ending sales in 2005, the V245 in 2008, the and T2000 in 2009-2010, and the E20K/E25K in 2007.

x86/x64-Based Servers

Sun Microsystems entered the x86 server market with the Sun Fire V20z and V40z models in early 2004, marking a strategic shift toward processors to complement its SPARC-based offerings. These 1U and 3U rackmount servers utilized processors for cost-efficient 64-bit x86 performance, supporting 1-2 sockets in the V20z (up to 16 GB ECC DDR RAM) and 2-4 sockets in the V40z (up to 32 GB ECC DDR RAM). Both models included integrated Lights-Out Management (ILOM) for , enabling reliable deployment in data centers for tasks like web serving and entry-level , where the x86 architecture broadened compatibility with and Windows operating systems. The V-series reached end-of-life in 2008, with last shipments occurring in 2007. Building on this foundation, Sun expanded its x86 lineup with the Sun Fire X4100 in 2006, a 2U server optimized for storage-intensive applications using 1-2 sockets and up to 16 GB DDR2 RAM. This model emphasized cost-efficiency through processors while providing enhanced I/O with four ports and support for multiple hot-swap drives, making it suitable for scale-out environments. In 2007, the Sun Fire X4500, codenamed "Thumper," introduced groundbreaking storage density with 2 sockets, up to 16 GB RAM, and 48 hot-swappable bays capable of 48 TB total capacity in a 4U form factor. This innovation facilitated petabyte-scale storage solutions when clustered, targeting data warehousing and media streaming use cases with ILOM for simplified management. By 2009, Sun transitioned to processors with the Sun Fire X4800, a 7U server featuring 4 sockets (via dual-socket compute modules) powered by 7500 series CPUs and up to 1 TB DDR3 RAM, prioritizing performance for demanding workloads like and . The shift to 's Nehalem and Westmere architectures in later x86 models, including the 2010 Sun Fire X4275—a 2U server with 2 5500 series sockets supporting 4-8 cores and up to 144 GB DDR3 RAM—delivered improved scalability and efficiency for web serving and virtualized environments. These servers retained ILOM for , enhancing operational reliability. The X-series models were phased out between 2012 and 2014 as part of the broader Sun Fire brand transition.

Operating System Support

Solaris and SPARC Systems

Sun Fire servers based on UltraSPARC processors were primarily supported by the Solaris operating system, with native compatibility ensuring optimal performance on SPARC architecture. Solaris 8, released in 2000, provided initial support for UltraSPARC III processors in systems like the Sun Fire 280R, enabling 64-bit computing and enhanced scalability for enterprise workloads. Solaris 9, introduced in 2002, extended compatibility to a broader range of Sun Fire models. Solaris 10, launched in 2005, became the flagship OS for UltraSPARC-based Sun Fire servers, introducing full Solaris Zones for containerization and the ZFS filesystem for advanced data management and reliability. Support for Solaris 10 on SPARC continued through Update 11 in 2013, with patches available until its end-of-support in 2021. SPARC-specific optimizations in Solaris enhanced the efficiency of Sun Fire servers, providing native binary compatibility that allowed seamless execution of SPARC-compiled applications across UltraSPARC generations without recompilation. Dynamic Resource Management (DRM), integrated with Solaris, facilitated real-time reconfiguration of hardware domains in Sun Fire high-end systems, enabling addition or removal of CPUs, memory, and I/O without downtime. Additionally, Solaris on Sun Fire achieved J2EE certification for key application servers, such as Sun Java System Application Server, ensuring reliable deployment of enterprise Java applications on UltraSPARC hardware. Factory-configured Sun Fire servers typically shipped with Solaris pre-installed, streamlining deployment for UltraSPARC models and allowing immediate configuration via the system's OpenBoot . Boot options included support for SAN environments, where servers could initiate from or storage arrays, optimizing for clustered and virtualized setups. Compatibility was strictly limited to UltraSPARC processors, as SPARC binaries were not executable on x86 systems without emulation, maintaining architectural isolation for performance-critical applications. Key Solaris features tailored for Sun Fire SPARC systems included Predictive Self-Healing, which proactively diagnosed and isolated faults in hardware components like and CPUs to prevent failures. Resource pools enabled dynamic partitioning of CPU, , and other assets across multiple domains, supporting efficient workload consolidation and isolation in multi-domain Sun Fire configurations. These capabilities, combined with Solaris Zones, allowed administrators to create secure, lightweight virtual environments within a single OS instance, maximizing resource utilization on UltraSPARC-based servers.

Linux, Windows, and Other Systems

The x86-based Sun Fire servers provided extensive support for distributions, enabling deployment in enterprise environments with optimized performance for Opteron and Intel Xeon processors. Red Hat Enterprise Linux versions 3 through 6, released between 2003 and 2010, were certified on models such as the Sun Fire V40z and X4450, with kernel enhancements for multi-core scalability and NUMA architectures common in these systems. Similarly, Server versions 9 through 11 were supported, including service packs like SLES 10 SP3 and 11 SP1, offering features such as virtualization integration for models like the X4170 M2 and X4270 M2. These certifications included Oracle's Unbreakable Enterprise Kernel for on later releases, providing stability patches and hardware-specific drivers for improved I/O throughput on Sun Fire x86 platforms. Windows operating systems were also fully supported on Sun Fire x86 servers, broadening their appeal for Microsoft-centric workloads from the early 2000s onward. Certifications covered Windows 2000 Server through , with the latter available up to 2012 on servers like the X4450 and X4170 , including Standard, Enterprise, and Datacenter editions in both 32-bit and 64-bit configurations. Drivers for the Integrated Lights Out Manager (ILOM) and controllers, such as those for SAS HBAs, were provided via Oracle's Hardware Management Pack, ensuring remote management and storage redundancy. Additionally, these servers received certifications for , as demonstrated on the Sun Fire X4600 , which supported high-availability clustering and database performance tuning. End-of-support for aligned with Microsoft's extended security updates until January 2020, coinciding with many Sun Fire x86 models reaching hardware end-of-life around 2014-2018. Beyond mainstream enterprise OSes, Sun Fire x86 servers accommodated niche and platforms, enhancing their versatility for specialized applications. and x86 ports were compatible due to the standard x86 architecture, supporting security-focused and portable workloads on models like the V40z. ESX Server 4.0 Update 2, ESX 4.1, and ESXi variants up to 5.1 were certified, with installation guides for remote media on servers such as the X4170 , enabling consolidated environments. support was more limited, primarily through community ports for x86 hardware, without official certifications or pre-built drivers for ILOM integration. Installation options for these operating systems emphasized ease of deployment in data centers. Oracle offered OEM pre-installs for and Windows on select Sun Fire x86 models, such as on the V40z, reducing setup time for volume purchases. Network-based installations via (PXE) were standard, allowing automated imaging over LAN for large-scale rollouts on servers like the X4170 and X4270. Support lifecycles for installed OSes typically ended with hardware end-of-service dates, such as September 2016 for the Sun Fire X4270, after which third-party maintenance was recommended for legacy patches. The x86 architecture of Sun Fire servers facilitated a broader compared to SPARC-based systems, allowing integration with diverse software stacks and enabling hybrid deployments across , Windows, and virtualized environments. This flexibility supported mixed workloads, such as combining database servers running SQL Server with -based application tiers, without the proprietary constraints of SPARC hardware.

Rebranding and Successors

Transition to Sun Server

In 2007, , in collaboration with , introduced the Enterprise server series as a replacement for the high-end Sun Fire E and T lines, targeting mission-critical applications with enhanced scalability and performance. The series included models such as the M3000, M4000, M5000, M8000, and M9000 for enterprise workloads and the T5120 and T5220 for throughput-oriented tasks, all co-developed to leverage Fujitsu's mission-critical expertise while running the Solaris operating system. This shift marked a strategic evolution in Sun's -based offerings, emphasizing joint innovation to sustain competitiveness in Unix server markets. By 2010-2012, following Oracle's acquisition of Sun in 2010, the x86-based Sun Fire models underwent rebranding to the Sun Server lineup, simplifying nomenclature by dropping the "Fire" designation for broader appeal. For instance, the Sun Fire X4170 M3 was renamed the Sun Server X3-2, and the Sun Fire X4270 M3 became the Sun Server X3-2L, with no alterations to hardware features or functionality. The final x86 models under the Sun Fire brand were released in 2012, concluding the transition. This rebranding was driven by the need to streamline product naming amid declining sales of systems, which had been eroding due to competition from x86 architectures in Unix server markets. Sun and later shifted emphasis toward x86 platforms to better support and integrated solutions like Exadata, aligning server offerings with growing demands for cost-effective, scalable . Key modifications included retaining the Integrated Lights Out Manager (ILOM) for remote management while incorporating -specific management tools to enhance integration within 's ecosystem. These changes facilitated seamless compatibility with software stacks without disrupting existing deployments. The improved market positioning for small and medium-sized businesses (SMBs) by presenting a more approachable, unified x86 server family that emphasized versatility for and database clustering. Models like the Sun Server X3-2L, with its high storage capacity, exemplified this focus on practical, expandable solutions for emerging workloads.

Oracle Server Branding

Following Oracle's acquisition of Sun Microsystems, the company rebranded its x86 server lineup from the Sun Fire series to the Oracle Server brand starting in , emphasizing integration with 's engineered systems and software stacks for enterprise applications. This rebranding applied primarily to x86-based successors, aligning hardware optimizations with , , and cloud services. Key models in this era included the Oracle Server X7-2, a two-socket rack server introduced in 2017 and powered by first-generation Scalable processors, supporting up to 3 TB of DDR4 memory across 24 slots and configurations for tasks. The Oracle Server X8-8, available from 2019 to 2020, represented a high-end eight-socket configuration using Xeon Platinum 8200 series processors, scalable up to 12 TB of DDR4 memory and designed for demanding workloads such as large-scale databases and in-memory analytics. These servers featured modular designs with up to eight CPU modules, each supporting 12 DIMMs, and extensive I/O options including PCIe Gen3 slots for NVMe flash storage up to 25.6 TB in low-profile form factors. Oracle positioned these systems for compatibility with engineered systems like Exalogic Elastic Cloud, enabling seamless integration for Java-based applications, , and processing through optimized networking and storage management software. Remote management was enhanced via Integrated Lights Out Manager (ILOM) firmware version 4.0 and later, providing secure KVM over IP, fault monitoring, and automated firmware updates across the server fleet. In 2020, Oracle introduced the Server X9-2 series powered by third-generation Scalable processors, with dual-socket configurations supporting up to 28 cores per socket, 4 TB of DDR4 memory, and enhanced PCIe 4.0 bandwidth for and AI workloads. Oracle later shifted to processors in the X10-2 series introduced in 2022, supporting up to 96 cores per socket with 9004 () for improved core density and efficiency in subsequent models through 2025. While x86 lines evolved under the Oracle Server branding, -based development concluded with the M8 processors in 2017, marking the last new SPARC server release as Oracle prioritized x86 and cloud-native architectures. Legacy Sun Fire systems received updates through 2023 via Sun System Firmware releases based on ILOM 5.1, extending compatibility for critical environments. For end-of-life Sun Fire servers, third-party maintenance providers offer extended support beyond Oracle's premier support, including hardware repairs and parts into 2025 and later, ensuring continuity for on-premises deployments reluctant to migrate. By 2025, Oracle has phased these hardware lines into its Cloud Infrastructure ecosystem, offering hybrid on-premises options through dedicated regions and distributed hybrid infrastructure that combine OCI services with customer-owned hardware for secure, low-latency workloads. This approach supports seamless transitions to cloud while retaining control over sensitive and legacy applications.

References

  1. https://www.cnn.com/2001/TECH/internet/03/23/cebit.sun.servers.idg/index.html
  2. https://www.washingtontechnology.com/2001/10/channel-news/350428/
  3. https://docs.oracle.com/cd/E19121-01/sf.v40z/817-5249-17/chapter1.html
  4. https://www.oracle.com/corporate/pressrelease/oracle-buys-sun-042009.html
  5. https://www.crn.com/news/components-peripherals/222600081/oracle-sun-acquisition-a-done-deal
  6. https://sparc.org/2001/02/27/
  7. https://www.theregister.com/2001/03/21/sunfire_servers_to_trash_hp/
  8. https://dogemicrosystems.ca/pub/Sun/System_Handbook/Sun_syshbk_V3.4/Systems/SunFire6800/SunFire6800.html
  9. https://www.oracle.com/technetwork/server-storage/solaris/solaris-sparc-white-paper-167888.pdf
  10. https://sparc.org/2001/
  11. https://www.hpcwire.com/2001/12/07/sun-announces-900-mhz-ultrasparc-iii-processor/
  12. https://shrubbery.net/~heas/sun-feh-2_1/Systems/common-docs/3800-6800_JTF.pdf
  13. https://sparc.org/2001/sun-and-ti-release-copper-interconnect-based-ultrasparc-iii-processors-to-systems-manufacturing/
  14. https://www.hpcwire.com/2002/02/08/sun-fire-srvrs-offer-dynamic-sys-domains-and-reconfiguration/
  15. https://phys.org/news/2010-01-oracle-acquisition-sun-microsystems.html
  16. https://www.idc.com/downloads/OracleSunRoadMap.pdf
  17. http://www.oracle.com/us/corporate/analystreports/idc-sparc-roadmap-193784.pdf
  18. https://www.centroid.com/wp-content/uploads/2020/06/Oracle_Hardware_with_Last_Ship_Dates.pdf
  19. https://www.pcmag.com/encyclopedia/term/sun-fire
  20. https://www.scribd.com/document/756161744/List-of-Oracle-Hardware-with-Support-End-Dates-1525631-1
  21. https://www.parkplacetechnologies.com/eosl/sun-oracle/
  22. https://siliconangle.com/2025/09/11/sun-microsystems-acquisition-made-oracle-cloud-company-today/
  23. https://www.spectra.com/wp-content/uploads/sunfiree25k.pdf
  24. https://docs.oracle.com/cd/E19045-01/b200x.blade/index.html
  25. https://docs.oracle.com/cd/E19469-01/819-6562-17/819-6562-17.pdf
  26. https://docs.oracle.com/cd/E19076-01/t2k.srvr/819-2548-14/819-2548-14.pdf
  27. https://www.theregister.com/2007/04/10/sun_fujitsu_misformainframe/
  28. https://docs.oracle.com/cd/E22368_01/pdf/E22356.pdf
  29. https://docs.oracle.com/cd/E19088-01/v60x.srvr/817-2023-11/CH1_Introducing.html
  30. https://docs.oracle.com/cd/E19121-01/sf.v40z/817-5248-21/chapter1.html
  31. https://docs.oracle.com/cd/E19088-01/v440.srvr/816-7728-10/816-7728-10.pdf
  32. https://dogemicrosystems.ca/pub/Sun/System_Handbook/Sun_syshbk_V3.4/Systems/SunFireX4100_shared/documents/SunFireX4100-X4200_JTF.pdf
  33. https://docs.oracle.com/cd/E19121-01/sf.x4150/820-1852-13/doradi-overview.html
  34. https://www.fujitsu.com/global/about/resources/news/press-releases/2007/0417-01.html
  35. https://docs.oracle.com/cd/E19065-01/servers.e25k/817-4136-13/1_Introduction.html
  36. https://docs.oracle.com/cd/E19095-01/sf6800.srvr/805-7362-13/805-7362-13.pdf
  37. https://docs.oracle.com/cd/E19088-01/280r.srvr/806-4806-10/806-4806-10.pdf
  38. https://docs.oracle.com/cd/E19088-01/v215.srvr/819-3041-10/gettingstarted.html
  39. https://docs.oracle.com/cd/E19076-01/t1k.srvr/819-3245-12/819-3245-12.pdf
  40. https://docs.oracle.com/cd/E19076-01/t2k.srvr/819-2543-12/Sys-Feat.html
  41. https://docs.oracle.com/cd/E19065-01/servers.e25k/817-4136-13/2_Domains.html
  42. https://www.oracle.com/technetwork/server-storage/solaris10/documentation/solarisnhm-ex-wsm-111610-188029.pdf
  43. https://sparc.org/2005/sun-java-application-platform-suite-achieves-best-in-class-priceperformance-results/
  44. https://www.spectra.com/wp-content/uploads/sunfiree20k.pdf
  45. https://dogemicrosystems.ca/pub/Sun/System_Handbook/Sun_syshbk_V3.4/Systems/SE_T1000/documents/SE_T1000_JTF.pdf
  46. https://www.nbcnews.com/id/wbna4231880
  47. https://www.filibeto.org/sun/lib/hardware/datasheets/v40z-ds.pdf
  48. https://www.spectra.com/wp-content/uploads/x4100.pdf
  49. https://www.infoworld.com/article/2189687/sun-fire-x4500-server-crams-48-drives-into-4u.html
  50. https://www.spectra.com/wp-content/uploads/x4500.pdf
  51. https://dogemicrosystems.ca/pub/Sun/System_Handbook/Sun_syshbk_V3.4/Systems/SunFireX4800/spec.html
  52. https://docs.oracle.com/cd/E19269-01/820-5830-13/overview.html
  53. https://www.parkplacetechnologies.com/eosl/family/sunfire/
  54. https://www.hpcwire.com/2000/02/04/ultrasparc-iii-microprocessor-pushes-solaris-performance/
  55. https://docs.oracle.com/cd/E19088-01/280r.srvr/816-2726-10/ch%2Blneck.htm
  56. https://docs.oracle.com/cd/E19683-01/806-5202/806-5202.pdf
  57. https://docs.oracle.com/cd/E19253-01/817-0547/index.html
  58. https://www.oracle.com/docs/tech/solaris-10-faqs-general.pdf
  59. https://www.oracle.com/a/ocom/docs/support/advanced-customer-support/solaris-linux-vm-lsp.pdf
  60. https://blogs.oracle.com/oracle-systems/post/an-update-on-oracle-solaris-and-sparc-infrastructure
  61. https://docs.oracle.com/cd/E19065-01/servers.12k/819-4658-10/dr.html
  62. https://www.spec.org/jappserver2004/results/res2007q3/jAppServer2004-20070619-00069.html
  63. https://docs.oracle.com/cd/E19253-01/817-6337/chapterHPG.html
  64. https://www.dell.com/community/CLARiiON/San-Boot-on-Solaris/td-p/6713179
  65. https://www.edaboard.com/threads/sun-solaris-programs-on-x86-platform.883/
  66. https://www.oracle.com/technetwork/server-storage/solaris10/overview/self-healing-149839.pdf
  67. https://www.oracle.com/technetwork/systems/containers/820-0040-150137.pdf
  68. https://www.usenix.org/event/lisa04/tech/full_papers/price/price.pdf
  69. https://docs.oracle.com/cd/E19150-01/820-2703-32/820-2703-32.pdf
  70. https://docs.oracle.com/cd/E19762-01/821-0483-13/z4000f3e1294757.html
  71. https://www.oracle.com/servers/technologies/support-matrix-v21a.html
  72. https://dogemicrosystems.ca/pub/Sun/System_Handbook/Sun_syshbk_V3.4/Systems/SunFireX4600_shared/documents/SunFireX4600_X4600_M2_JTF.pdf
  73. https://docs.oracle.com/cd/E20781_01/html/E20790/z40004b61392429.html
  74. https://docs.oracle.com/cd/E19477-01/820-5829-11/820-5829-11.pdf
  75. https://www.sun.com/servers/nsp/so2007docs/820-3895-10.pdf
  76. https://www.fujitsu.com/global/about/resources/news/press-releases/2007/1009-01.html
  77. https://www.zdnet.com/article/sun-fujitsu-to-launch-joint-sparc-servers/
  78. https://docs.oracle.com/cd/E22368_01/pdf/E22357.pdf
  79. https://static6.arrow.com/aropdfconversion/267ae71d4c06befc0b91f4248a6c2286ac2006a/e23397.pdf
  80. https://www.nytimes.com/2008/10/30/business/worldbusiness/30iht-31sun.17397617.html
  81. https://www.nytimes.com/external/idg/2009/04/24/24idg-The-downfall-of.html
  82. https://www.greentecsystems.com/product/oracle-sun-x3-2l-x4270-server/
  83. https://www.oracle.com/docs/tech/x7-2_datasheet-v1.pdf
  84. https://docs.oracle.com/en/servers/x86/x7-2/installation-guide/gqqsx.html
  85. https://www.oracle.com/a/ocom/docs/products/servers/x86/x8-8-8socket-datasheet.pdf
  86. https://www.oracle.com/a/ocom/docs/products/servers/x86/x8-8-dual-4socket-datasheet.pdf
  87. https://www.oracle.com/technetwork/server-storage/engineered-systems/exalogic/overview/exalogic-elastic-cloud-x4-2-ds-2196778.pdf
  88. https://docs.oracle.com/en/servers/x86/x9-2/product-notes/oracle-server-x9-2-product-notes.pdf
  89. https://docs.oracle.com/en/servers/x86/x9-2/service-manual/oracle-server-x9-2-service-manual.pdf
  90. https://www.oracle.com/a/ocom/docs/sparc-t8-m8-server-architecture.pdf
  91. https://www.oracle.com/servers/technologies/firmware/release-history-jsp.html
  92. https://www.oracle.com/servers/x86-servers/
  93. https://www.parkplacetechnologies.com/third-party-maintenance/sun-oracle-storage-and-server-maintenance/
  94. https://www.oracle.com/cloud/hybrid-cloud/
  95. https://www.oracle.com/news/announcement/oracle-recognized-as-a-leader-in-the-2025-gartner-magic-quadrant-for-distributed-hybrid-infrastructure-2025-09-10/
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.