AGSH, 03LG019 and 03NK829 identify different things
A parts request may arrive with a feature code from the configuration and a different number from the drive label. Keep both. They help us match the offered module to the installed FlashSystem.
| Identifier | What it tells you |
|---|---|
| AGSH | The 38.4 TB FlashCore Module 4 feature in applicable 4662-family configurations. |
| 4662-AGSH | The machine-type and feature-code ordering reference. |
| 03LG019 | An IBM service FRU for the 38.4 TB FCM4. |
| 03NK829 | A related hardware part number in our 38.4 TB FCM4 catalog mapping. |
AGSH is the configuration feature
AGSH identifies the capacity and FlashCore generation within its machine family. The 4662 prefix adds the ordering context. Neither number alone confirms the replacement procedure, firmware level or RAID arrangement for an installed system.
03LG019 and 03NK829 belong with the installed drive label
03LG019 is the service-FRU reference in IBM's control-enclosure parts list. Our catalog also associates 03NK829 with this capacity and FCM4 generation. Preserve the number printed on your module rather than replacing it on the request with a number found elsewhere.
A shared part-family mapping is useful for identification. It does not make every feature code or offered drive interchangeable across all FlashSystem models.
38.4 TB module capacity is different from 115.2 TB effective capacity
AGSH provides 38.4 TB of usable capacity at the module level. IBM publishes up to 115.2 TB of logical or effective capacity for this FCM4 size. That larger figure depends on the data reduction your workload achieves; it is not extra physical flash.
| Capacity measure | Example |
|---|---|
| One AGSH module | 38.4 TB module capacity; up to 115.2 TB effective at 3:1 data reduction. |
| Twelve AGSH modules | 12 × 38.4 TB = 460.8 TB aggregate nominal module capacity. |
| Twelve modules at 3:1 | 12 × 115.2 TB = 1,382.4 TB, approximately 1.38 PB effective before array overhead. |
What twelve AGSH modules mean in a 5200 or 5300
Both controllers have twelve internal NVMe positions. Filling them with AGSH modules gives the aggregate figures above. Distributed RAID parity and rebuild reserves reduce the capacity available to applications. Metadata and other system overhead also matter.
Already compressed backups or encrypted data may reduce little. Size the system from the RAID-usable capacity and measured reduction of your data, then allow for growth. Do not use the largest effective-capacity figure as the space you can promise an application.
AGSH fits the 4662 family; ADSH and AHSH retain their own model context
The same FlashCore generation and capacity can appear under different feature codes. Match the code to the control enclosure before ordering.
| FlashSystem model | Feature and configuration context |
|---|---|
| FlashSystem 5200 4662-6H2 | AGSH; 4662-AGSH ordering context. Check the installed software and supported array arrangement. |
| FlashSystem 5300 4662-7H2 | AGSH in the dedicated 5300 configuration source; twelve internal NVMe positions. |
| FlashSystem 7300 4657-924 | ADSH; 4657-ADSH ordering context. |
| FlashSystem 9500 | AHSH in applicable 4983 and 4666 configurations. |
AGSH is an internal NVMe module for a supported control enclosure. It does not install in the 4662-12G, 4662-24G or 4662-92G SAS expansion shelves. Those shelves use their supported SAS drives.
AGSH versus AGSD and AGS8: capacity alone does not identify a replacement
| Feature | Generation and replacement consideration |
|---|---|
| AGS8 | FCM2; 38.4 TB module capacity and up to 87.96 TB logical capacity. |
| AGSD | FCM3; 38.4 TB module capacity and up to 115.2 TB logical capacity. |
| AGSH | FCM4; 38.4 TB module capacity and up to 115.2 TB logical capacity, with FCM4 computational-storage capabilities. |
AGS8 is the earlier FCM2 option
AGS8 has its own firmware and service-part family, including 02YC419 and 03GH472. An AGSH purchase is not a like-for-like FCM2 replacement merely because both labels say 38.4 TB. Check the supported upgrade design before changing generations.
AGSD is the FCM3 option
AGSD identifies the third-generation module, with service references including 03JK079 and 03JK165. Supported FCM3-to-FCM4 replacement or expansion can retain FCM3 behavior when generations share an array. Adding one FCM4 does not turn that array into an all-FCM4 design.
AGSH adds FCM4 computational storage
FCM4 uses PCIe Gen4 and performs inline compression within the module. It also supports self-encryption and T10-DIF data-integrity protection. Its computational-storage functions collect I/O statistics that help Storage Virtualize identify suspicious changes in data behavior.
For the workload, compare measured latency and throughput as well as capacity. A module benchmark is not an enclosure benchmark, and multiplying a per-module figure does not establish the performance an application will receive.
FCM4 ransomware detection needs the right array, software and firmware
Installing an AGSH module is one part of enabling FCM4-assisted detection. Array creation and feature enablement have separate requirements.
- Confirm the array's history. IBM's drive documentation requires an all-FCM4 array created at Storage Virtualize 8.6.2 or later for the computational-storage capability.
- Confirm detection enablement. IBM's FlashCore guide specifies Storage Virtualize 8.6.3 or later together with FCM firmware 4.1 or later for ransomware threat detection. Check the supported levels for the actual system.
- Confirm operational readiness. Check monitoring, alert delivery and the response procedure. Suspicious activity needs investigation; detection does not replace tested backups or a recovery plan.
FCM3 and FCM4 can share an array where the model and configuration rules permit it, but the FCM4 then operates with FCM3-level functionality. Keep a repair of an existing array separate from a project to enable FCM4-specific functions.
AGSE, AGSF and AGSG are smaller FCM4 capacity choices
Smaller FCM4 options can fit a separately sized array. Their feature codes identify different capacities, so a smaller drive should not be selected as an AGSH replacement.
For a quote, distinguish the immediate failed-drive replacement from additional capacity or a new all-FCM4 array. The best configuration depends on the capacity and generation already installed, the target RAID layout and the workload.
Industry-standard NVMe SSDs are another supported media class in applicable configurations. They do not provide FlashCore's internal compression or computational-storage functions. Compare standard NVMe and FlashCore media before making a capacity-only choice.
What to send for an AGSH replacement or upgrade quote
Send us the installed configuration and the result you need. A drive-label photo and a current storage inventory help connect the feature code to the physical module.
- Complete FlashSystem machine type, model and serial number.
- Installed feature code and every part or FRU number on the module label.
- Module capacity and FlashCore generation.
- Storage Virtualize version and FCM firmware level.
- Array members, RAID type and array-creation history where detection enablement matters.
- Whether this is a failed-drive replacement, capacity expansion or new-array project.
- Required RAID-usable capacity, growth and the available maintenance window.
Follow the system's service procedure for a fault. A matching capacity or a hot-swappable drive description does not by itself authorize removing a healthy array member.
AGSH catalog and technical references
Catalog and technical references checked October 24, 2026.
- Our FlashSystem 5300 catalog configuration supplies AGSH and the other 4662 FCM4 feature contexts.
- Our FlashSystem 7300 parts catalog preserves the cross-family feature and hardware-part mapping.
- IBM FlashSystem 5200 Product Guide lists the 5200 FCM4 features.
- IBM 5x00 drive documentation gives module capacities and the array-creation requirement.
- IBM control-enclosure service parts identifies 03LG019.
- IBM FlashCore Module Product Guide explains FCM4 detection software and firmware requirements.