Asset ID: |
1-75-1395544.1 |
Update Date: | 2012-10-06 |
Keywords: | |
Solution Type
Troubleshooting Sure
Solution
1395544.1
:
How to gather information from a dead Mx000- Unable to access XSCF via network and domain is down.
Related Items |
- Sun SPARC Enterprise M9000-32 Server
- Sun SPARC Enterprise M8000 Server
- Sun SPARC Enterprise M9000-64 Server
- Sun SPARC Enterprise M4000 Server
- Sun SPARC Enterprise M3000 Server
- Sun SPARC Enterprise M5000 Server
|
Related Categories |
- PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Mx000
|
Applies to:
Sun SPARC Enterprise M3000 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise M4000 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise M5000 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise M8000 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise M9000-32 Server - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
M3000, M4000, M5000, M8000, M9000, M9000-32, m9000-64
Purpose
This is to aid with gathering information from a Mx000 system that the XSCF is unaccessable via the network.
Troubleshooting Steps
If the system is totally dead and you are unable to access the XSCF via the network port. Then the only way to gather any information is via the serial port on the XSCF.
Connect a console to serial port and power on the system.
You may see errors similar to the following.
Example 1
---------
XSCF uboot 01080001 (May 8 2009 - 15:09:36)
SCF board boot factor = a080
memory test ..
Memory compare test
memory error detect 80000008, address 00000000 data aaaaaaaa -> deadffef
capture_data hi deadffef lo deadbeef ecc eeee
capture_attributes 01113001 address 00000000 <------ Notice that the XSCF stops here so no further information.
---------
Example2
------------
XSCF uboot 01100001 (Feb 3 2011 - 14:43:12)
SCF board boot factor = 4080
memory test ..
Memory compare test
................finish
DDR Real size: 256 MB
DDR: 224 MB
## Booting image at ff800000 ...
Image Name: XSCF kernel 01100001 2.6.11.12-s
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1457363 Bytes = 1.4 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at ff980000 ...
Image Name: XSCF rootfs 01100002 ,2011/05/12
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 5486484 Bytes = 5.2 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC <------ Notice that the xscf stops here so no further information.
----------------
If the XSCF doesn't boot correctly or fails post then no network is configured.
Both these SR ended up with the XSCF being replaced but without this information we have no idea what is happening on the XSCF.
Once the XSCF was replaced this booted normally and the customer could administer the system via the network.
As part of your data collection when opening a service request with Oracle, connect to the serial port of the XSCF and gather the boot logs of the XSCF to allow the issue to be investigated in a timely manner.
Attachments
This solution has no attachment