Oracle Confidential (PARTNER). Do not distribute to customers
Reason: Request by Gavin Lai to make internal / Escalation Mode not available to customer.
and later [Release: N/A and later ]
Sun Fire X4600 M2 Server - Version: Not Applicable and later [Release: N/A and later]
Sun Fire X4140 Server - Version: Not Applicable and later [Release: N/A and later]
Sun Fire X4240 Server - Version: Not Applicable and later [Release: N/A and later]
Sun Fire X4440 Server - Version: Not Applicable and later [Release: N/A and later]
Information in this document applies to any platform.
Symptoms
Current case entitlement depends on serial number accuracy, however; SB replacement can lead to to a serial number of '00000000' which will also breaks ASR if SBs are not reprogrammed.
Since entitlement and ASR also depend on serial number accuracy, this issue must be addressed by TSC management in our weekly staff meetings and also via the CAPs development chain through our Community Driver, Sue Evanoff.
As the procedure for S/N reprogramming will not be addressed any service manual but only noted, the responsibility has been placed on our TSC backline and on CAPs documentation.
Refer to URL: (https://sunspace.sfbay.sun.com/pim/Download?id=162938) for information on the latest generation of servers.
Changes
SB replacement
Cause
SB replacement
Solution
AMD Based Servers
ILOM 2.x
- need to be in Service Mode
- Service Mode password is the same as the root password
Note: Login as 'sunservice'
- servicetool (example below)
ILOM 3.x How to enter Escalation mode (Sample: user sun1)
Note: LOM 3.x requires Escalation password from TSC to change serial number
A new user has to be created to assign role 's' as root cannot have this role (Roles: a=Admin,u=userManagement,c=console,r=Reset,o=ReadOnly,s=Service).
-> cd /SP/users
/SP/users
-> create sun1
Creating user...
Enter new password: ********
Enter new password again: ********
Created /SP/users/sun1
? need to be in Escalation Mode (for the full detail, please see <Document 1019946.1>)
-> show /SP/users/sun1 role
/SP/users/sun1
Properties:
role = o
-> set /SP/users/sun1 role=aucros
Set 'role' to 'aucros'
-> show /SP/users/sun1 role
/SP/users/sun1
Properties:
role = aucros
-> show /SP check_physical_presence
/SP
Properties:
check_physical_presence = true
-> set /SP check_physical_presence=false
Set 'check_physical_presence' to 'false'
-> 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
Logout as root, Login as sun1
Escalation Password:
For Escalation password, this is similar to service password (Serial number can be collected by '-> show /SYS
product_serial_number', please use this command to get this, not based on the chassis):Since the password is valid for 48 hours, you can generate a password for a later date.
Enter Long password gathered form pass generator.
->set /SP/users//escalation/ escalation_password=true
Password:**** **** *** *** **** *** *** **** **** **** **** **** ****
**** **** **** *** *** *** *** **** **** **** *** **** **** **** *** *** ***
Short form password is: OATH SHAY LOAN
Enter short From password
-> set SESSION mode=escalation
Short Form Password:**** **** ****
Currently in escalation mode.
If physical presence is on, 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:*** **** ***
Press and release the physical presence button.
Press return when this is completed...
Currently in escalation mode.
A Linux # prompt indicates that you are in escalation mode.
Now you can use features available in service/escalation mode.
When you are done with service mode, it is best to invalidate the password using this command:
-> set /SP/users/sun1/escalation/escalation_password=false
Mode password has been removed.
Sun Fire X4100 M2, Sun Fire X4200 M2
Note: These systems have separate Service Processors (SP/ILOM), servicetool -board_replaced service_processor is required to update the FRU information on the SP.
ILOM 2.x and 3.x (Servicetool Example)
Usage: servicetool OPTIONS
OPTIONS:
--board_replaced=BOARD update FRU information for BOARD after it has been replaced
--fru_product_part_numb er write a new product part number to mainboard and pdb FRUs
--fru_product_serial_numb er write a new product serial number to mainboard and pdb FRUs
--fru_chassis_serial_numb er write a new chassis serial number to mainboard and pdb FRUs
--fru_chassis_part_numb er write a new chassis part number to mainboard and pdb FRUs
--fru_asset_tag write a new asset tag to mainboard and pdb FRUs
BOARD may be one of:
mainboard pdb
To replace a system board: servicetool --board_replaced=mainboard
For example:
[(flash)root@SUNSP00 1E68 1E39FB:~]# servicetool --fru_chassis_serial_numb er
Servicetool is going to update the chassis serial number in mainboard and pdb FRUs.
Do you want to continue (y|n)? y
When entering values, do not use quotes;
What is the new chassis serial number? 0814QAC086
The chassis serial number has been updated.
The new serial number is: "0814QAC086"
Updating FRUs... done
Sun Fire X4640
As documented in CR 6997703
With the bash prompt, the sunservice account needs to be enabled:
bash-2.05b# /usr/local/bin/sunserviceacct enable
Once in 'sunservice' account on ILOM (i.e. escalation mode in ILOM 3.x)
Exporting the original motherboard's product information:
frutool -t mb --read_cmm_product_area > /dev/shm/product.info
Edit /dev/shm/product.info to contain the correct serial number, then
write it back by doing:
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
Remove the /dev/shm/product.info
Reboot the SP for the change to take place.
References
<NOTE:1019946.1> - How to access service mode and escalation mode on ILOM 3.x and later platforms
<NOTE:1280913.1> - How to update product serial number on systems which implement Top Level Identifier functionality
Attachments
This solution has no attachment