Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Troubleshooting Sure Solution 1002937.1 : Analyzing "System not contactable" on a Sun Fire(TM) X2100 M2/X2200 M2 System
PreviouslyPublishedAs 204040 Description Description
Summary:
Symptoms:
Steps to Follow The following are the steps to follow Please validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step. Available Documentation Latest documentation on the Sun Fire X2100 M2/X2200 M2 servers can be found at the following locations: This troubleshooting guide makes reference to several of the documents at these locations. Step 1. Verify system powerThis is maybe an obvious step, and very easy to do if you are stood next to the platform - not as easy if the platform is remote. The Documentation in the following links provides details what things should be checked and how to do so using the different platform management tools.
If after you have checked for power and find that the system is powered off refer to the following Document, which explains how and what to check if your system is found to be powered off or will not power-on when checked.
When the system is still powered off or you find any indicator for issues which causes the system to be powered of, please log the data as described in the document above and proceed with step 6 in this document to contact Sun Support. If you checked and the system has Power, please go to the next step. Step 2. Verify SP connectivityBe clear about how you are trying to contact your server. If you are trying to connect via the service processor, refer to the Embedded Lights Out Manager (ELOM) Administration Guide for the Sun Fire X2100 M2 and Sun Fire X2200 M2 Servers at Sun Fire X2200 M2 Server Documentation If you are trying to contact the server via the platform network, go to step 4 NOTE: If after checking your SP connectivity you still have a problem, contact Sun Support. as outlined in step 4 below Step 3. Check for any errors on the systemCheck out the logs as outlined in the ELOM guide above. Any abnormal conditions, raise a a service request as outlined in Step 6. Step 4. Verify network connectivityThe commands to follow to check your network are outlined in the following document: <Document: 1005533.1> "How to verify network connectivity on an x64 platform" Step 5. Check your platform has not hungIf all the above check out, your platform may be hung (although if you can run the commands in Step 4, you can't be hung...) Here are some documents which will be helpful if you are still unsure about whether you have hung:
Step 6. Raise a Sun service requestAt this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required. For additional support contact Sun Support. NOTE: Since you can't contact your server, the amount of data you can gather is limited. For example, if you are running solaris, you will not be able to complete an explorer data capture. However, in the event you can get the data (maybe you have problems contacting on one ethernet port only), the link below will show you how. The following link references support documents assists in the gathering of information from your platform:
A full description of the Sun Explorer package and release notes are available on the following Technical Instruction <Document: 1002383.1> Sun[TM] Explorer 5.10 Data Collector
Product Sun Fire X2200 M2 Server Sun Fire X2100 M2 Server Internal Comments Audited/updated 12/11/09 - [email protected], x64 Content Team Member At this point, if the customer has validated that each troubleshooting step above is true for their environment, and the issue still exists, escalate to your Sun escalation path. This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es) listed below:
Normalization team alias: [email protected] x64, normalized, x2100, x2200, M2, network, ILOM Previously Published As 91529 Change History Change History Date: 2007-12-27 User Name: 31620 Action: Approved Comment: Checked links again and the are in the correct format now. Publishing. Version: 5 Date: 2008-04-01 User Name: 79977 Changed Domain Lead to Tony McNamara Attachments This solution has no attachment |
||||||||||||
|