Goal

Reprogram the chassis and/or motherboard serial number after system mainboard replacement.

Solution

DISPATCH INSTRUCTIONS
- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
A Field Engineer must have ILOM version 2.x and 3.x training and be able to login with the sunservice account on fw2.x

ILOM and know how to create a user in fw3.x ILOM.
- TIME ESTIMATE: 30min
- TASK COMPLEXITY: 2

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
- PROBLEM OVERVIEW: When a server motherboard is replaced, the serial number for the motherboard and/or the chassis is usually set to all zero's. Sometimes the serial numbers become all zero's when a firmware upgrade is done. The serial numbers need to be reprogrammed for ASR and service validate in MOS.

- WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?:  The system must be connected to AC power, and it does not matter if the server is in production since this process does not affect the production side of the system.

- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE: The process is the same for several systems. This document will explain how to reprogram the serial number for the following systems: Sun Fire X4100, X4100 M2, X4200, X4200 M2, X4600, X4600 M2, X4640, X4500 and X4540. There are 2 sections to this document the first containing instructions for 2.x firmware and the second containing instructions for 3.x firmware.

Systems that have ILOM firmware v2.x

Step one to reprogramming the motherboard record for the chassis serial number is to login using the sunservice account. The sunservice account in ILOM firmware v2.x uses the same password as the root user account. The utility used to reprogram the serial number is "servicetool" and when you use the servicetool command with no options, the utility will print what command options are available. For example:

[(flash)root@SUNSP0003BAD87B31:~]# servicetool
Usage: servicetool OPTIONS
OPTIONS:
--board_replaced=BOARD update FRU information for BOARD after board has been replaced
--fru_product_part_number write a new product part number to the mainboard FRU
--fru_product_serial_number write a new product serial number to the mainboard FRU
--fru_chassis_serial_number write a new chassis serial number to the mainboard FRU
--fru_asset_tag write a new asset tag to the mainboard
FRU BOARD may be one of: 
mainboard service_processor

The following is an example of reprogramming the chassis serial number:

[(flash)root@SUNSP0003BAD87B31:~]# servicetool --fru_product_serial_number

Servicetool is going to update the mainboard FRU product serial number
Do you want to continue (y|n)? y
When entering values, do not use quotes; If you require embedded
quotes, escape them with three backslashes; e.g. \\\"
What is the new chassis serial number? 0650AMT024
The chassis serial number has been updated.
The new serial number is: "0650AMT024"
Updating FRUs... done

[(flash)root@SUNSP0003BAD87B31:~]#

To complete the process the SP must be reset. While logged in under the sunservice account, you can use "init 6" or "reboot". You can also logout of the SP and log back in as root, then "-> reset /SP". Resetting the SP by command will have no affect on the production side of the system.

Systems that have ILOM firmware v3.x

Note: The x4640 is documented below in a separate section

The actual command that is used with ILOM 3.x firmware is the same as used with an ILOM 2.x system. The ILOM engineering team decided that customers were not to use the sunservice account, so by default it is disabled in ILOM v3.x. The account can be enable but that requires that the SP be set to Escalation Mode and requires the assistance of someone who has access to the internal Oracle ILOM SP password site. Having the password generated requires that the on-site employee create a new user account with specific permissions since the root user account can't be use to enable Escalation Mode. The following is an example of setting up such an account:

-> cd /SP/users
/SP/users

-> create escalate
Creating user...
Enter new password: ********
Enter new password again: ********
Created /SP/users/escalate

-> show /SP/users/escalate role
/SP/users/escalate
Properties:
role = o

-> set /SP/users/escalate role=aucros
Set 'role' to 'aucros'

-> show /SP/users/escalate role
/SP/users/escalate
Properties:
role = aucros

It's a good idea to program one other setting in the SP as part of enabling Escalation mode. That is the check_physical_presence parameter.  The command used to check_physical_presence is:

-> show /SP check_physical_presence
/SP
Properties:
check_physical_presence = true

-> set /SP check_physical_presence=false
Set 'check_physical_presence' to 'false'

Use of this setting is explained below.

Once the escalation mode user is created, information from the SP must be collected and provided to the person that is generating the Escalation Mode password. The commands to use for gathering this additional data is (can be logged in as root or escalate userid):

-> version
SP firmware 3.0.2.50
SP firmware build number: 40153
SP firmware date: Thu Dec 11 17:47:27 PST 2008
SP filesystem version: 0.1.22

-> show /SYS product_serial_number
/SYS
Properties:
product_serial_number = 0825QAC003

-> show /SP/clock
/SP/clock
Targets:
Properties:
datetime = Fri Dec 9 18:22:37 2011
usentpserver = disabled
Commands:
cd
set
show
->

When the "show /SP/clock" command is run, the local time for the server needs to be noted and provided with the collected data to the person creating the Escalation Mode password. The Escalation Mode password site uses the clock time to reliably generate the 30 word password phrase. By noting the local time when the SP clock information is collected helps if any time delay is experienced between when "show /SP/clock" is run vs when the password is generated and can be compensated for. The password can be used for the next 48 hours as long as the SP clock is properly in sync with the password web site when the password was generated. An example of what the web site generates and should be sent to the field employee is:

BRAND : sun
MODE : escalation
VERSION : 3.0.2.50
SERIAL : 0825QAC003
UTC DATE : 12/09/2011 18:22

HURL GEAR TUBA GUSH HER CRAM GEM TWIT POP GULF BUNT ORGY JUTE WORM IRE BARK AMY BOOM FORT IDEA BIG AFRO OAR BOW SHOE GEM BUT ELK FIST ABE

Note: When the 30 words are typed in, the SP will represent each keystroke as an *. The use of copy and paste can be used, and typing each letter and space in by hand works as well.

An example of the actual process for enabling Escalation Mode is as follows:

Remember, you must logout as userid root, then login using the newly created escalate account. After doing so, enter the 30 words password provided from password generator web site
-> set /SP/users/escalate/escalation/ escalation_password=true
Password:**** **** **** **** *** **** *** **** *** **** **** **** ****
**** *** **** *** **** **** **** *** **** *** *** **** *** *** *** **** ***
Short form password is: OATH SHAY LOAN
Enter short form password

-> set SESSION mode=escalation
Short Form Password:**** **** ****   <Currently in escalation mode.
If check_physical_presence is not set to "false" as mentioned previously, you must be on a console connection and will be prompted to prove physical presence. The following example:

-> set SESSION mode=escalation
Short Form Password:*** **** ***
If "check_physical_presence = true", then press and release the physical presence button.
Press return when this is completed...

A Linux # prompt indicates that you are in escalation mode. Now you can use features available in escalation mode. With the bash prompt, the sunservice account needs to be enabled:

bash-2.05b# /usr/local/bin/sunserviceacct enable

Follow the same instructions in the firmware 2.x section above to reprogram the chassis and/or motherboard serial number. When you are finish with service mode, the sunservice account needs to be disabled, and it is best to invalidate the password using this command:

bash-2.05b# /usr/local/bin/sunserviceacct disable

-> set /SP/users/escalate/escalation escalation_password=false
Mode password has been removed.


X4640 System
The Sun Fire X4640 has a different set of commands that need to be used. Since this system has ILOM V3.x, the SP needs to be set to Escalation Mode, the FSE must login the sunservice account after it is enabled as documented above. The default password for the x4640 sunservice account is "changeme", even if the root account password is changed. Once logged into the sunservice account, the following steps are to be taken:

Export the original motherboard's product information

# frutool -t mb --read_cmm_product_area > /dev/shm/product.info

product part_number "PHOENIXXATO"
product asset_tag NULL:16 <----Tag is incorrect
chassis serial_number 1003AMP050
chassis part_number    541-4153-00

Edit /dev/shm/product.info to contain the correct serial number, since you are at a Linux prompt (#), you can use the vi editor. When we create /dev/shm/product.info file product asset_tag NULL:16 should be set to product serial_number "1003AMP050"

Verify the product.info file contains the proper serial number and write the change back to the system files:

# frutool -t mb --write_cmm_product_area < /dev/shm/product.info

Then read it back, just to be sure:

# frutool -t mb --read_cmm_product_area

product part_number "PHOENIXXATO"
product serial_number "1003AMP050"
chassis serial_number 1003AMP050
chassis part_number    541-4153-00

Remove the /dev/shm/product.info file you created.

Finally, with the change complete, reboot the SP by using "init 6" or "reboot". Be sure to log back into the SP as the escalate user so that you can disable the sunservice account with:

-> set SESSION mode=escalation
Short Form Password:*** **** ***
bash-2.05b# /usr/local/bin/sunserviceacct disable
bash-2.05b# exit

-> set /SP/users/sun1/escalation escalation_password=false
Mode password has been removed.

Once the sunservice account is disabled and escalation mode is disabled also, the process is complete and the system can be released to the customer.

OBTAIN CUSTOMER ACCEPTANCE
- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
n/a

PARTS NOTE:
n/a

REFERENCE INFORMATION:

This solution has no attachment