Cimc raid monitor solarwinds how to#

SANESX43SEL.txt =ġ06 | 13:52:36 | CIMC | Memory DDR4_P1_D1_ECC #0x8c | read 1 correctable ECC errors on CPU1 DIMM D1 | Assertedġ07 | 05:42:41 | CIMC | Memory DDR4_P1_D1_ECC #0x8c | read 1 correctable ECC errors on CPU1 DIMM D1 | Assertedġ08 | 18:27:56 | CIMC | Memory DDR4_P1_D1_ECC #0x8c | read 1 correctable ECC errors on CPU1 DIMM D1 | Assertedġ09 | 12:17:33 | CIMC | Memory DDR4_P1_D1_ECC #0x8c | read 1 correctable ECC errors on CPU1 DIMM D1 | Assertedġ0a | 23:42:28 | CIMC | Memory DDR4_P1_D1_ECC #0x8c | read 1 correctable ECC errors on CPU1 DIMM D1 | Asserted I've sampled the SEL logs (manually exported) and see the 'correctable ECC' memory errors are quite common: VMware did its job with HA configured and restarted ~30 VMs on the surviving cluster members We had a Cisco UCSB-B200-M5 new blade lock up due to 'uncorrectable ECC' memory error Decrease Patrol Scrub time - frequently checks each memory location to detects & correct errors (20 min) Increase Refresh rate (default is 64 msec) - reduce amount of charge loss, effectively reduce correctable memory error rate, 2x (32ms) is recommended. Results in significant charge loss & possible data loss due to increase leakage in Victim rows. Row hammer pattern means accessing one or a pair of Target rows multiple times within a single refresh period Mostly seen in high performance system frequently accessing shared memory location To allow the host to map out any DIMMs that encounter uncorrectable ECC errors.įor Cisco B-Series blade server, the server firmware must be at Release 2.2(1) or a later release If you enable DIMM blacklisting, Cisco UCS Manager monitors the memory test execution messages and blacklists any DIMMs that encounter memory errors in the DIMM SPD data. A faulty DIMM is a considered a nonfunctional device. When the BIOS encounters a noncorrectable memory error during memory test execution, the DIMM is marked as faulty. In Cisco UCS Manager, the state of the Dual In-line Memory Module (DIMM) is based on SEL event records. I could have proactively caught this when they first ECC errors started happening and moved my vms and took the blade into maintenance. Thanks! The built in alerting doesn't seem to go into this deep of detail in alerting of the SEL logs. We have over 300+ blades to manage and this is causing a nightmare in our environment. The ESXi host will eventually crash and as expected causes our VMs to failover and causes minor outages. These alerts start happening in the SEL log of the blade and eventually the blade crashes in a matter of time. We occasionally get some bad RAM or MB of a blade.

Cimc raid monitor solarwinds how to#

Good afternoon, does anyone happen to know how to manage alerting from SEL logs? I can’t get a straight answer from Cisco.