6.30 Agents - Replace corr memory

[Rob Buxton]

Hi All,

Updated the Agents on several W2000 servers to 6.30A. And, on reboots we're now seeing "Replace Corr Memory" Events. As this has happened on several servers I'm less than convinced that we've got a sudden outbreak of flakey memory.
Anyone else seen this?

[Stephen Jones_3]

We have also updated several of our boxes and they are producing these events.

I also presume this is some sort of bug in the agents code.

Regards,
Stephen

[Anthony Cohn]

Yep, we are also getting this error. Anything to worry about?

Anthony

[Gotink]

I guess it is a false translation of the Intergrated Management Log.
When you clear the intergrated management log, the errors do not return.

On one server I have got correctable memory Log instead of Intergrated Management Log (homepage - Logs).
Does anyone know how to fix this?

[Rob Buxton]

Thanks All,

Anyone from the HP Insight Manager team want to comment?

I'll test the results of any Servers rebooting with a clean Integrated Log. It could be as Albert has suggested a result of some incorrect processing of the log.
It certainly seems as though it's a bug though.

[James Kennedy_4]

Had this on my servers as well. Replaced each memory module one after one at a time, definately not a memory problem.

This was actually a cluster box that was disconnected from its shared storage. Once reconnected to the shared array, the error messages have dissapeared.

Must be a bug in 6.30 when external SCSI controller not connected to anything? Very wierd though. They shouldn't have to be terminated by anything when nothing is connected.

[James Kennedy_4]

Well, just installed 6.30A on my DL-360 G2 test box. The same errors are now in the event logs.

This box does not have any external SCSI connectors, so now I know there really is something buggy with these agents.

Did HP do any testing???

[James Kennedy_4]

Well, just installed 6.30A on my DL-360 G2 test box. The same errors are now in the event logs.

This box does not have any external SCSI connectors, so now I know there really is something buggy with these agents.

Did HP do any testing???

[Meier Daniel]

Yep, we are also getting this error. I' dont worry about and i'm sure in the next release of smartstart it's fixed.

[Greg Hooper_1]

Yes, I have gotten the same errors on my 6.3 updates. About 10 servers so far.

[Rob Buxton]

Hi All,

I'm no longer sure what triggers these errors and under what circumstances. A new install on a DL380, which had un-cleared errors in the Integrated log didn't produce any of the "corr memeory" errors.

But, the Integrated Log showed up as Green even though there were uncleared serious errors in the Log.

[J._1]

There seems to be some problems with the CPQHOST reporting subsystem...

If anyone out there is polling memory usage with SNMP, can you please check if you're also seeing the following:

.1.3.6.1.4.1.232.11.2.13.2.0 (enterprises.compaq.cpqHostOs.cpqHoComponent.cpqHoMemory.cpqHoPhysicalMemoryFree) responds with "1918" and that .1.3.6.1.4.1.232.11.2.13.1.0 (...cpqHoMemory.cpqHoPhysicalMemorySize) responds with "1"

We don't have 1MB RAM installed on our servers ;)

This is occuring on our servers with the 6.3 agents loaded, regardless of the actual installed memory / available memory. All other agent versions up to this point have returned proper values. The CPQHOST.MIB file included with the latest agents lists the above OID's and they're consistent with previous versions.

[Scott Shaffer · Accepted solution]

All - this is a bug, it will be addressed in 6.4. I don't have a good date for that yet, but I expect it by the end of June at the latest.

[Sandy Wood]

Well for what it's worth, I'm getting the same on my Win2k servers.....

correctable memory errors...

[Jerry Brown]

As Scott mentioned above, this is a known Management Agent issue. A customer advisory will be coming out very soon but I wanted to share the resolution with the forum so that you can determine if the error is true or false.

If a correctable memory error occurs on initial system startup, check the Integrated Management Log (IML) for a corresponding correctable memory error message. If a correctable memory error is not logged in the IML, then the error is false and can be ignored. If the correctable memory error is logged in the IML, then the error is valid.

Smart Start 6.4 will have a fix for this issue.

[P.Messerli]

Hi all,

I also collect memory infromation with SNMP on my DL 380 G2.

The OID 1.3.6.1.4.1.232.11.2.13.1 is "NULL" or "1". Before the update everyting was o.k.

Have the same errors in the event logs.

[Fredy Gerber]

good morning,

I use 6.40A on my DL-380 G2. The value for the OID 1.3.6.1.4.1.232.11.2.13.1 is "1". Exists a fix or a solution for this problem?

Regards,
Fredy