Operational Defect Database
BugZero found this defect 4260 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Hewlett Packard Enterprise | c01006246
Notice: (Revision) VMware ESX/ESXi 4.x/5.x - Guidelines for Accurately Troubleshooting Reported System Memory Errors on ProLiant Servers Running VMware ESX/ESXi 4.x/5.x Operating Systems
Last update date:
2/29/2024
Affected products:
HPE ProLiant BL280c G6 Server Blade
HPE ProLiant BL2x220c G6 Server Blade
HPE ProLiant BL420c Gen8 Server Blade
HPE ProLiant BL460c G6 Server Blade
HPE ProLiant BL465c G6 Server Blade
HPE ProLiant BL465c Gen8 Server Blade
HPE ProLiant BL480c Server Blade
HPE ProLiant BL490c G6 Server Blade
HPE ProLiant BL495c G6 Server Blade
HPE ProLiant BL660c Gen8 Server Blade
HPE ProLiant BL685c G6 Server Blade
HPE ProLiant DL160 G6 Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
Document Version Release Date Details 2 09/20/2012 Revised content to include guidelines for memory troubleshooting with VMware ESX/ESXi 4.x/5.x. 1 04/19/2007 Original Document Release. Reported system memory errors on ProLiant servers running the VMware ESX/ESXi operating system (OS) are erroneously being attributed to DIMM failures. Replacing system memory in ProLiant servers should not be performed before executing the proper troubleshooting steps. HP is providing the following system memory troubleshooting guidelines to more accurately diagnose reported system memory issues before replacing DIMMs in ProLiant servers running VMware ESX/ESXi operating systems. Accurately troubleshooting system memory issues in ProLiant server configurations is an important process that can help prevent disruption and downtime associated with hardware component replacement, particularly when the hardware may not need to be replaced. Following standard troubleshooting guidelines each time a memory issue is suspected helps to minimize the disruption.
Scope
None
Resolution
None
