NetApp, Inc. — 4 prefixes (MA-L)
Summary
- // what this is
- NetApp is registered to MAC prefix
00:80:E5and 3 more in the IEEE OUI database. When a device's MAC address begins with00:80:E5, that block was registered by NetApp — the OUI identifies the maker of the network hardware, which is not always the brand on the device. - // analyst note
- These OUIs on a network signal enterprise storage infrastructure (NetApp FAS/AFF/E-Series) present, typically inside a datacenter/SAN rather than an end-user segment. Company substance is well-established (4 OUIs, public NASDAQ company, first-party device documentation) — this is not a single-OUI shell registration.
About this vendor.
A MAC address beginning with 00:80:E5, 00:A0:98, 00:A0:B8, or D0:39:EA belongs to NetApp, Inc., typically seen on enterprise storage-array network interfaces rather than consumer devices — specifically ONTAP-based FAS/AFF clustered storage systems and E-Series storage arrays.
NetApp holds four separate MA-L OUI assignments, all registered to the identical organization name and address (1395 Crossman Ave, Sunnyvale, CA 94089, US). Per NetApp's own knowledge base, 00:A0:98 is the original OUI block for ONTAP and E-Series hardware; 00:A0:B8 and 00:80:E5 are used on E-Series hardware; D0:39:EA is a newer block added for ONTAP and E-Series systems starting at ONTAP 9.1P17, rolled out across FAS, AFF, and SAN systems.
IEEE's public OUI data publishes no assignment or registration date for any of these four blocks. Third-party aggregator maclookup.app lists dates such as 1998-04-22 for two of the prefixes and 2019-01-29 for D0:39:EA, but these are database artifacts from a third-party scrape, not facts sourced from IEEE, and should not be presented as an IEEE registration date.
These OUIs typically appear on management and data-network interfaces of enterprise storage arrays deployed inside datacenters and SANs, not on end-user or IoT segments. No vulnerability or exploit is tied specifically to the OUI itself; the general best practice — changing default admin credentials on storage-management interfaces after deployment — applies as it would to any enterprise device.
- IEEE assignment
- 4 prefixes → NetApp, registered Sunnyvale, CA, US [Confirmed] — the IEEE MA-L registry (IEEE MA-L mirror)
- Registry / block size
- MA-L (24-bit OUI); holds 4 IEEE prefixes: 00:80:E5, 00:A0:98, 00:A0:B8, D0:39:EA [Confirmed] — the IEEE MA-L registry, the Wireshark manufacturer database
- HQ / country
- 1395 Crossman Ave, Sunnyvale, CA 94089, US [Confirmed] — the IEEE MA-L registry (identical on all 4 registrations)
- Company status
- active, NASDAQ: NTAP [Confirmed] — kb.netapp.com, community.netapp.com (netapp.com itself returned HTTP 403 to direct fetch)
- Device types
- ONTAP FAS/AFF clustered storage (00:A0:98 original block; D0:39:EA added at ONTAP 9.1P17+), E-Series storage arrays (00:A0:B8, 00:80:E5) [Confirmed] — kb.netapp.com
- Notable products
- NetApp ONTAP (FAS/AFF), NetApp E-Series [Confirmed] — kb.netapp.com
- Verified sample prefixes (all MA-L, NetApp)
- 00:80:E5, 00:A0:98, 00:A0:B8, D0:39:EA [Confirmed] — the IEEE MA-L registry, the Wireshark manufacturer database
- Registration dates
- Unknown per IEEE (no date field published in the IEEE MA-L registry/manuf); third-party maclookup.app shows dates (00:A0:98/00:A0:B8 "1998-04-22", 00:80:E5 "2000-11-09", D0:39:EA "2019-01-29") but these are database artifacts, not IEEE facts [Confirmed] — maclookup.app/vendors/netapp
- Security/usage note
- OUIs appear on enterprise storage management/data-network interfaces in datacenter/SAN deployments; no OUI-specific vulnerability advisory found; general guidance is to change default admin credentials on storage-management interfaces [Likely] — community.netapp.com, security.netapp.com/advisory
- Registry coverage
- MA-L only; no MA-M or MA-S registrations found for NetApp [Confirmed] — grep of the IEEE MA-M registry and the IEEE MA-S registry (no matches)
- Analyst note
- Four independent MA-L assignments to the identical org/address plus first-party KB corroboration of device usage is clear company-substance, well past the bare single-OUI-shell threshold [Confirmed] — the IEEE MA-L registry, kb.netapp.com