Sun SPARC[TM] Enterprise M3000, M4000, M5000 - How to correct an invalid or wrong brandid setting on a NEW xscfu.

Asset ID:	1-71-1313793.1
Update Date:	2018-01-08
Keywords:

Solution Type Technical Instruction Sure

Solution 1313793.1 : Sun SPARC[TM] Enterprise M3000, M4000, M5000 - How to correct an invalid or wrong brandid setting on a NEW xscfu.

Applies to:

Sun SPARC Enterprise M3000 Server - Version Not Applicable and later
Sun SPARC Enterprise M4000 Server - Version Not Applicable and later
Sun SPARC Enterprise M5000 Server - Version Not Applicable and later
Information in this document applies to any platform.

Goal

Correcting an invalid or misconfigured brandid on a new Mx000 xscfu.

An incorrect brandid can be identified by typing <tab><tab> at the XSCF prompt with the current user in "Normal" mode. This sequence will display a list of all available commands. If the command "enablecodboard" is present in the list, then the brandid is set incorrectly.

This procedure is for a new xscfu that doesn't need to retain a configuration.
To perform this same procedure on a previously configured xscfu then use <Document 1313741.1>

Solution

Important note : when implementing this procedure on system running XCP1115, make sure to review the workaround section from 1562888.1. Basically, Patrol Diagnosis should be disabled in Escalation mode before running 'setdefaults'.

Login to the xscf and initiate an escalation mode session.

Refer to <Document 1002928.1> for the necessary steps.
In step #3 'enableescalation' and 'escalation' should be substituted for 'enableservice' and 'service'.

Check the current brandidsetting: ( 1 = SUN, 2 = FUJITSU, 3 = FSC )
escalation# /scf/bin/brandid
SunMC : off
REMCS : on
RCI : on
DIMM-PCE : off
DIDR : off
SPDR : on
SvcTag : off
brandid : 2 <===
display : 2
escalation#

Set the correct brandid:

escalation# /scf/bin/brandid -s brandid=1
brandid : 2 -> 1

Verify the correct brandid is set ( see step 2 ).

Settings will take effect the next time the platform is powered

Clear the fru area:

escalation# /hcp0/scfprog/bin/clearfru # command may be located /scf/bin/clearfru

Restore factory defaults:

escalation# /scf/init/scf_initetc/setdefaults factory
setdefaults will execute
XSCF : all data clear
OPNL : all data clear (exclude SYSTEM ID data)
*** XSCF reboot then execute clear operation automatically. ***
Are you OK? [y|n] : y
..... From here is shown the reboot log ......
***** WARNING *****
XSCF initialization terminate for XSCF/OPNL data clear.
execute "setdefaults factory" (AUTO)
setdefaults : FACTORY mode clear : start
setdefaults : FACTORY mode clear : DBS start
setdefaults : FACTORY mode clear : wait 20s for DBS initialization
initialize OPNL SEEPROM 1/6 -- complete
initialize OPNL SEEPROM 2/6 -- complete
initialize OPNL SEEPROM 3/6 -- complete
initialize OPNL SEEPROM 4/6 -- complete
initialize OPNL SEEPROM 5/6 -- complete
initialize OPNL SEEPROM 6/6 -- complete
setdefaults : FACTORY mode clear : OPNL reset complete

..... output deleted for readability .....
setdefaults : FACTORY mode clear : log data clear complete
setdefaults : FACTORY mode clear : NVRAM(PAGE#0) clear complete
setdefaults : FACTORY mode clear : NVRAM(PAGE#1) clear complete

..... output deleted for readability .....
XSCF BOOT STOP (recover by NFB-OFF/ON)

Power cycle the system.
Log back in and disablemodes:

XSCF> showmodes
Current mode: normal
Enabled for: escalation
Expires: Sun Jan 25 14:44:24 2009
XSCF> disablemodes
XSCF> showmodes
Current mode: normal

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in an appropriate
My Oracle Support Community - Oracle Sun Technologies Community.

References

<NOTE:1002928.1> - Accessing service mode on the Sun SPARC(R) Enterprise M9000/M8000/M5000/M4000/M3000 Platform
<NOTE:1313741.1> - Sun SPARC[TM] Enterprise M3000, M4000, M5000 - How to correct an invalid or wrong brandid setting on a configured XSCFU.

Attachments

This solution has no attachment