![]() ![]() ![]() Non-Profit Virtual Machine Windows Server Questions (Licensing & Best practice) Industry-Specific IT.Lamborghinis? Spiceworks Originalsįlashback: May 31, 1943: Construction of ENIAC starts (Read more HERE.)īonus Flashback: May 31, 1926: John Kemeny, Co-inventor of BASIC is born (Read more HERE or HERE if that. Snap! - Cables, Gloom, Origami, Nanocomputers, Flowers, and.All fans will run at maximum RPM and throttling will occur with the blades while the CMC is removed, so there will be reduced performance on the blades. If the issue still occurs with the CMCs removed then I would feel confident in saying it is a midplane issue.īlades cannot be powered on without a CMC, so you would need to remove the CMC after everything is up and running. It will help you determine whether or not the CMC has anything to do with the issue. That will remove almost all logic from the chassis. You can also try running the system without either CMC installed for testing purposes. If you have reseated the blades and there are no environmental issues that would cause them to come loose then I would look at replacing the midplane. I see places in the logs where it appears that you are moving things around and reseating blades, but there are other locations where it appears that the issue starts from the blade either losing communication with the chassis or going to a removed state.Īt this point it looks like a midplane issue. Throughout the log I'm seeing loss of connection with the blades or what appears to be the blades going to a removed state. It looks like the blades are losing connection with the chassis, going to a critical state, and then a power on attempt is made, virtual reseat attempted, or a physical reseat is taking place. Firmware incompatibility with the CMCs can cause odd issues, so I would resolve that issue before doing anything else. Check to make sure that they are both at the same firmware revision. Are the blades fully seated into the midplane? Is there a lot of vibration in the chassis/rack? Is the chassis level?Īlso, during startup the CMC log is showing a firmware difference between the two CMCs. It looks like this is a connection issue between the blades and the midplane. Those errors are only a symptom of the loss of connection and not an indication of what the actual problem is. That will cause a lot of voltage and other errors. It would be the equivalent of pulling all of the power and data cables out of the server at the same time. If the blades are going into a removed state then that means all connections from the chassis are being dropped from the blade. The CMC log you posted is missing time stamps, so that makes it more difficult to compare against other logs.įrom what I can tell by the logs it looks like the blades are going into a removed state. It is difficult to read logs without context. these issues in blade slots 6 and 11 and recently 14, it happen before in slot 2 and 15.- these errors occurs frequently, i changed 2 complete servers and 3 motherboards so far.Īttached a screen capture of the CMC interface after receiving one of these errors or both of them the failed server goes down and its color in CMC interface turns to red with an red X on it, and stops respond to power on command neither from the iDRAC interface nor the server front panel power button. The system board fail-safe voltage is outside of the allowable range. The system board Current Latch current is outside of the allowable range. the exact errors as reported in the logs are i meant there is no power supply related errors in the logs, since it's a voltage error i thought may be its a power supply failure but i didn't found any power supply reported errors and they all light green in the enclosure and in the CMC interface. these errors reported in both the CMC Hardware Log Events and in the individual failed server iDRAC Hardware Log. ![]()
0 Comments
Leave a Reply. |