Fujitsu PRIMERGY RX2530 untuk Virtualization & Enterprise Workloads
Status: Tanya Ketersediaan
Butuh bantuan sizing (VM/RAM/storage), perbandingan model, atau rencana deployment? Tim Intilogy membantu konsultasi infrastruktur enterprise — bukan hanya quotation part number.
Products in the Intilogy catalog are reference listings for IT procurement. Availability, pricing, configuration, warranty, and lead time may change based on distributor or vendor stock. Use Check Stock or Request a Quote for the latest information from our team.
General specifications
- Brand
- Fujitsu
- Category
- Servers
- Use case
- Virtualisasi, Database, Aplikasi ERP/CRM, Disaster recovery
- Warranty
- Per official vendor/distributor terms
- Availability
- Tanya Ketersediaan
Reference specifications
| Komponen | Spesifikasi |
|---|---|
| Faktor Bentuk | Rack 1U |
| Prosesor | 1 atau 2 x Intel Xeon Scalable (Generasi ke-3 atau ke-4) |
| Chipset | Intel C621A atau C741 |
| Memori | 16 slot DDR4 ECC RDIMM/LRDIMM, maks. 2 TB (dengan prosesor Gen ke-4) |
| Penyimpanan Internal | Hingga 10 x 2.5 inci SAS/SATA/SSD atau 4 x 3.5 inci + 2 x 2.5 inci |
| RAID Controller | RAID 0/1/5/6/10 (opsional hardware RAID) |
| Slot Ekspansi | 2 x PCIe 4.0 x16 (low-profile), 1 x PCIe 4.0 x8 (internal) |
| Jaringan | 2 x 1 GbE (terintegrasi), opsi 10/25/40 GbE |
| Manajemen | iRMC S6 (Integrated Remote Management Controller) dengan IPMI 2.0 |
| Daya | 1 atau 2 PSU hot-plug 450W/800W/1200W (redundan) |
| Sistem Operasi | Windows Server, Red Hat Enterprise Linux, SUSE Linux Enterprise Server, VMware ESXi |
| Dimensi (T x L x D) | 43 x 435 x 605 mm |
| Berat | Maks. 18 kg |
Ideal for
- Virtualisasi
- Database
- Aplikasi ERP/CRM
- Disaster recovery
Need a quote or alternative configuration?
Use Check stock or Request a quote for the latest availability, pricing, warranty, and lead time. Our team also helps with BoQ/BoM preparation, multi-brand comparison, and configuration alternatives.
Need a quotation or IT solution recommendation?
Send a short brief — our team will follow up on BoQ, sourcing, and implementation steps.
