(bent pins, cracked
traces, contamination or corrosion) on the FRU connection points and
ensure proper mating/
seating occurs. If the problem persists, replace only one FRU at a time
in the order given
below. Test the system between each FRU replacement.
Replaceable Units(s) :
...
...
...
MCA data is also stored at the OA and can be retrieved by running the OA command show errdump
dir mca as follows:
OA-CLI> show errdump dir mca
Logtype: MCA (Machine Check Abort)
Bundle nPar vPar time
0x011000000000aae6 1 Mon Jan 20 10:30:31 CET 2014
0x011000000000aae5 1 Fri Jan 17 12:23:49 CET 2014
0x011000000000aae4 1 Fri Jan 17 10:51:06 CET 2014
0x011000000000aae3 1 Thu Jan 16 21:43:45 CET 2014
0x011000000000aae2 1 Mon Jan 13 11:44:30 CET 2014
0x011000000000aae1 1 Mon Jan 13 11:43:27 CET 2014
0x011000000000aadf 1 Tue Dec 10 01:07:39 CET 2013
0x013000000000aac0 1 Sun Dec 8 01:12:08 CET 2013
0x011000000000aadd 1 Sat Dec 7 01:58:05 CET 2013
0x011000000000aadc 1 Sat Dec 7 01:57:02 CET 2013
If an MCA of interest is found, it can be captured by running the command show errdump mca bundle
<ID>.
Troubleshooting the blade interface (system console)
Cause
All system console connections are made through the OA CLI via the management network.
Linux uses the OA 10/100 BT LAN connection over a private network to control one or more server blade
operations, locally through Telnet or SSH or remotely over a public network through a web GUI.
Troubleshooting the blade interface (system console) 97
To Next Page
Loading...
