Find the exact identity
Search models, full PNs and aliases without treating an alias as proof of equivalence.
Open tool →Servers, components and networking in one searchable catalog. Compare technical records, plan system dependencies and prepare a clearer inquiry.
Catalog counts, not inventory quantities. Baseline records, externally listed identities and reviewed OEM fields have separate evidence status.
Search models, full PNs and aliases without treating an alias as proof of equivalence.
Open tool →Put recorded specifications side by side. Missing fields stay visibly unrecorded.
Open tool →Re-evaluate CPU, memory, chassis, storage, GPU, cooling and PSU arithmetic together.
Open tool →Collect quantities, match a bulk parts list and export a local draft for review.
Open tool →GIGABYTE G593-ZD1-AAX1 — Rack & blade servers
OEM fields reviewed · see remaining checks
GIGABYTE D120-S3G — Rack & blade servers
Inherited technical record
GIGABYTE G150-B10 — Rack & blade servers
Inherited technical record
GIGABYTE G180-G00 — Rack & blade servers
Inherited technical record
GIGABYTE G190-G30 — Rack & blade servers
Inherited technical record
GIGABYTE G190-H44 — Rack & blade servers
Inherited technical record
Plan protection and check the delivered scope.
Read guide →Quote the whole connection, not one isolated switch.
Read guide →Technical identity and stock are different datasets.
Read guide →Mathematical estimates do not establish equipment qualification.
Read guide →Specify rack height, bay size and backplane options.
This guide adds the decisions, documents and next steps that support this page.
Server directory
Plan rack depth, rail kit and airflow before choosing a chassis.
Server directoryIdentify the enclosure, fabric modules and generation-specific interconnects.
Server configuratorSeparate shared power, node count and service access in the request.
Buying guidesSpecify rack height, bay size and backplane options.
Record CPU generation, socket count and DIMM population.
Include input power, PSU redundancy and remote-management needs.
A planning sequence, not a record of completed work.
Counts show records in the site catalog. They do not represent stock, available quantities or verified compatibility.
Snapshot: 2026-09-15
| Decision | Record in your brief | Evidence to retain |
|---|---|---|
| Chassis & drive layout | Specify rack height, bay size and backplane options. | Complete identifier and source revision |
| Processor & memory | Record CPU generation, socket count and DIMM population. | Platform document or written clarification |
| Power & management | Include input power, PSU redundancy and remote-management needs. | Offered-unit details and agreed scope |
Tick items as you prepare them. This is your personal checklist, not a hardware validation.
Saved in this browser when local storage is available.
Reference-based generated scenes; actual-unit photos are available only through an explicit unit-specific request. Related models are separate catalog records, not substitutes for the item on this page.
Continue the relevant directory or service flow.
Open resourceUse the connected tool to develop the requirement.
Open resourceRetain the supporting reference with your project brief.
Open resourceExact chassis model recorded · CPU and DIMM plan attached · Drive backplane and risers identified · Rails and power requirements listed.