!!! Service Passwords should NEVER be given to customers !!!
MODE : service
VERSION : 01.09.0002
SERIAL : BEF10285D8
DEAF HAWK LIME ILL SLAY COON
HOME ALMA VOID KERN BARE KNOT
BEAR EST EDIT SKY SHE VICE
SUN JAR RYE TALL WAVE ROSE
HERO SCAR JUT SWAY WIN A
!!! This password is valid for 48 hours !!!
!!! Remember to run "disablemodes" command before exiting the session. !!!
---------------------------------
*** Start System Error Message ***
* IOU#0 Status:Degraded;
---
Date: Sep 01 07:45:19 UTC 2010 Code: 60000000-ffffffff-0109001500000000
Status: Warning Occurred: Sep 01 07:41:39.331 UTC 2010
FRU: /UNSPECIFIED
Msg: XSCF command: System status change (OS panic) (DID#00, path: 00)
...
Date: Sep 01 07:58:40 UTC 2010 Code: 40000000-b7010000-0300003600000000
Status: Information Occurred: Sep 01 07:58:38.686 UTC 2010
FRU: /IOU#0
Msg: Device error (FCode informed error)
Diagnostic Code:
00000001 00000000 00000000
43484543 4b204465 7461696c 204c6f67
00000000 00000000 00000000 00000000
UUID: ee2ae160-d66d-4b1b-a7ec-fff4dfc7360b MSG-ID: SCF-8002-0X
Diagnostic Messages
*** End System Error Message ***
WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
1. get service passwrod
2. clearfault /IOU#0 degraded status first
3. setup domain dump configuration
4. monitor the system , if issue persist , collect domain&XSCF explorer
& coredump , to decide if need to replace IOU#0 .
========
Document Audience: INTERNAL
Document ID: 204029
Old Document ID: (formerly 91335)
Title: Accessing service mode on the Sun SPARC[R] Enterprise
M9000/M8000/M5000/M4000 Platform
Copyright Notice: Copyright ? 2008 Sun Microsystems, Inc. All Rights
Reserved
Update Date: Mon Sep 08 00:00:00 MDT 2008
Solution Type Technical Instruction
Solution 204029 : Accessing service mode on the Sun SPARC[R] Enterprise
M9000/M8000/M5000/M4000 Platform
Related Categories
* Home>Product>Systems>Servers
Description
Accessing service mode on the Sun SPARC[R] Enterprise Mx000 Series platform
Steps to Follow
Enabling and using servicemode
Step 1.
Log into the XSCF as fieldeng and verify you have the appropriate
privileges.
XSCF> showuser
User Name: fieldeng
UID: 101
Status: Enabled
Minimum: 0
Maximum: 99999
Warning: 7
Inactive: -1
Last Change: Feb 07, 2007
Password Expires: Never
Password Inactive: Never
Account Expires: Never
Privileges: mode <------ Needed
fieldeng <---- Needed
*** NOTE If you do not have these privilege you will need to do the
setprivileges command. ***
Very important - setprivileges overwrites a user's current privileges
and does NOT append privileges to the existing list. To add privileges
to a user, you must re-list all existing privileges as well as the new
privileges.
Example:
XSCF>setprivileges platadm useradm platop fieldeng mode
Step 2.
Create a Password. This is done at There is a
backup server at
Changes have been made to the OPL Password Generators to allow TSC to
collect some minor additional information when a password is generated.
We will use this data to improve our processes, gather support for
fixing bugs, or perhaps indicate where additional user features are
necessary to reduce costs associated with servicing the product. We are
soliciting your support by requesting that you enter valid data when you
generate service or escalation mode passwords.
If you are generating a password for a customer, please select Customer,
then supply a reason for generating the password, including a CR# if you
know it, in the REASON field and a valid case # in the CASE# field. If
you are generating a password for internal use, REASON is still
required, but CASE# is not.
Please try to provide accurate and useful information considering our
intended usage. It only takes a few extra seconds to record useful data,
and it will benefit everyone.
Here are some examples of useful information in the REASON field:
- need to clear the deconfigured status on MBU_A due to a power failure
(see CR 6729779)
- customer is running XCP 1060 and has a "degraded" IOU after a boot
failure (see CR 6586462 & 6639839)
Here are some examples of less useful information in the REASON field:
- need it
- deconfigured parts, clearfru, clear faults, enable faulted components
In order to create a password you will need the following data from the
XSCF.
The verion of XSCF: version -c xscf
The serial number: showhardconf
***** WARNING: The data you input into this site is CASE SENSITIVE. Be
sure to
use the appropriate case, or you will NOT be able to log into service
mode. ****
One of the commands used is showhardconf. showhardconf -M makes it a little
easier to get the serial number, which is at the top of the output.
The password will be a long list of words. You can copy and paste them
into the passwd prompt when it comes time.
*******************************************
The generated password is good for 48 hours from the time of generation
Make sure the date has been set on the XSCF with showdate
*******************************************
Step 3.
There are two steps to gain access to service mode. The service password
can be pasted into the below password prompt. Hit a return afterwards
and wait.
You may need to hit another return. You will get a secondary password to
plug ito the service command.
XSCF> enableservice
Service Password:
**** **** **** *** *** ***
**** **** *** ** **** ****
*** **** **** *** **** ****
**** **** **** *** *** ****
**** **** **** **** **** *
Mode password is: WALL CAT BY
XSCF> service
Mode password: **** *** **
Step 4.
Clear the fault. The clearfault command has an excellent manpage which gives
the paths to the frus should you not be 100% sure of the path to input into
the command.
Example:
service> clearfault /MBU_A/MEMB#0/MEM#0A
clearfault: Fault cannot be cleared for this FRU.
FRU will be marked to clear fault on next circuit breaker off and on.
Continue? [y|n]: yes
Fault will be cleared after circuit breaker off and on
The fault should now be cleared. Depending on the component you will be
prompted with extra instructions as indicated above. Form more
information on clearing faults, and FMA related errors consult <
Solution: 203335 > Fault clearing and LEDs behavior
Step 5. Verify the fault is cleared.
XSCF> showstatus
