Hi Steven,
Just to clarify: reset memory errors does not equal reset CIMC.
Actually resetting CIMC should never be done to clear DIMM errors - doing so is equivalent to sweeping a potential problem under the rug and has a side effect of deleting files in CIMC that may be helpful in investigating the cause of the error.
In 1.3 and earlier firmware resetting CIMC was the easiest way to get UCSM to re-evaluate the DIMM status based on what it was seeing from CIMC (another more impacting method would be to decommision and reack the blade). For errors that do not occur frequently this could result in the DIMM status being reset to operable in UCSM without much impact on the operation of the system but if the error returned what have you accomplished?
This behavior changed in 1.4 firmware and later. In 1.4 and later resetting CIMC has no affect on the DIMM status in UCSM. Once a DIMM goes degraded or inoperable the only way to clear that state in UCSM is to change the FRU information on the DIMM (i.e. replace it), decommision and reack the server (i.e. the server starts over from scratch) or use the reset memory errors functionality.
Reset memory errors was added to 1.4 and later firmware because in 1.3 firmware, UCSM essentially ignored correctable errors. During testing of upgrades from 1.3 to 1.4 it was found that if a system had many correctable errors that occurred long ago, once UCSM was upgraded it would suddenly see all those historical correctable errors as new ones and set the DIMM status to degraded. Reset errors was added to clear that specific condition as well as clear any other false positive DIMM degraded or inoperable status. Use of reset errors outside of this context is similar to resetting CIMC - sweeping a potential problem under the rug.
Regarding your specific problem - if the number of correctable errors continues to increase then yes, the recommended course of action would be as you suggest - replace the DIMM.
Hope that helps,
Mike
