Fujitsu M10-4S: XSCF "BB-ID is illegal" with 01a10010

Asset ID:	1-72-1941641.1
Update Date:	2017-08-28
Keywords:

Solution Type Problem Resolution Sure

Solution 1941641.1 : Fujitsu M10-4S: XSCF "BB-ID is illegal" with 01a10010

Applies to:

Fujitsu M10-4S - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

When you try to connect more than 2 BBs(Building Blocks), you might get errors such as the example below in showlogs error and showhardconf will not see the building block at all.

Date: Mar 25 13:33:40 UTC 2014
   Code: 10000000-003bff0000ff0000ff-01a100100000000000000000
   Status: Information            Occurred: Mar 25 13:33:29.578 UTC 2014
   FRU: /BB#0
   Msg: BB-ID is illegal
   Diagnostic Code:
       00000000 00000000 0000
       00000000 00000000 0000
       00000000 00000000 0000
       00000000 00000000 00000000 00000000
       00000000 00000000 0000

Date: Mar 25 12:53:50 UTC 2014
   Code: 10000000-003bff0000ff0000ff-01a100100000000000000000
   Status: Information            Occurred: Mar 25 12:53:40.399 UTC 2014
   FRU: /BB#0
   Msg: BB-ID is illegal
   Diagnostic Code:
       00000000 00000000 0000
       00000000 00000000 0000
       00000000 00000000 0000
       00000000 00000000 00000000 00000000
       00000000 00000000 0000

Date: Mar 25 12:29:24 UTC 2014
   Code: 10000000-003bff0000ff0000ff-01a100100000000000000000
   Status: Information            Occurred: Mar 25 12:29:15.009 UTC 2014
   FRU: /BB#0
   Msg: BB-ID is illegal
   Diagnostic Code:
       00000000 00000000 0000
       00000000 00000000 0000
       00000000 00000000 0000
       00000000 00000000 00000000 00000000
       00000000 00000000 0000

Cause

You may also see "BBID is conflict BB 0" messages during the XSCF boot. It means that there are multiple BBs who have the same BB-ID in the same Building Blocks due to an incorrect procedure, such as changing the BB-ID after the first poweron, etc. The BB-ID needs to be changed before the first poweron. Changing the BB-ID after the first poweron doesn't work if it's BB#00 or BB#01. In case if it is necessary to change the BB-ID after the first poweron, the restoredefaults needs to be executed.

Solution

Here are the general procedure to restore a BB-ID from an incorrect setting.

1) Connect the system management terminal to the chassis serial port.
2) Log in to the XSCF by using the default user account and authentication method.
3) Execute the restoredefaults -c factory command to return the entire system to the factory default settings.
4) Confirm that all LEDs on the operation panel are off.
5) Remove the power cords from the power supply units.
6) Change the BB-ID to the correct settings.
7) Perform steps 1 to 6 for all chassis.
8) Connect the power cords of all chassis to the power supply units.

Note: Please don't swap the step 6) and 8). Change the BB-ID before step 8).

For more details, please refer to the Installation Guide, Appendix A.3 "How to Restore a BB-ID from an Incorrect Setting."

Fujitsu M10/SPARC M10 Systems Installation Guide

Internal only procedure without using the restoredefaults command.

NOTE: The information contained in this doc should not be shared with a customer.
If it is necessary to perform this procedure then a FSE will need to be dispatched.

Attach a terminal to the XSCFU serial port of the BB, you want to change, so you can monitor the process.
Change the building block ID number via front panel switches to '55' and power cycle the BB.

Following the power cycle, you will see the XSCFU boot with some messages like this:

FACTORY mode clear : start
FACTORY mode clear : sun_setdefault complete
FACTORY mode clear : sun_initdbs complete
FACTORY mode clear : REMCS initialization complete
FACTORY mode clear : SPI-FMEM clear complete
Initializing COMMON_PANEL.db DUAL.db FIRMUP.db... complete
Removing FRU.db... complete
Removing SETUP*.db... complete
FACTORY mode clear : XSCF DB clear complete
FACTORY mode clear : restore user accounts from default settings complete
FACTORY mode clear : BACK UP DB clear complete
FACTORY mode clear : NRCI initialization complete
Cleaning under /data/log/sync recursively... complete
Cleaning under /data/log/nosync recursively... complete
Initializing SCF log... complete
Cleaning under /data/apcs recursively... complete
Cleaning under /data/log/monitor_log recursively... complete
Cleaning under /data/audit recursively... complete
Cleaning under /data/sptrace_backup recursively... complete
Cleaning under /data/var recursively... complete
Removing whole /data/md_store... complete
Removing whole /data/firm/cmu... complete
Removing whole /data/firm/obp... complete
Removing whole /data/firm/pcibox... complete
Removing /data/panel_fru.flg... complete
Removing /data/procdown_info... complete
Removing /data/var/sp/home/.ssh/authorized_keys.*... complete
Removing /data/tmp/ntp/peerstats*... complete
Removing /data/tmp/ntp/loopstats*... complete
Removing /data/var/sp/home/.bash_history... complete
Removing /data/var/sp/home/.lesshst... complete
Cleaning under /var/log recursively... complete
Cleaning under /sp/log/core recursively... complete
Cleaning under /root/.ssh recursively... complete
Removing /sp/log/monitor.log*... complete
Cleaning /hcp0/usr/local/ssl/servercert.pem... complete
Cleaning /hcp0/usr/local/ssl/serverkey.pem... complete
Cleaning /hcp0/usr/local/ssl/csr.pem... complete
Cleaning /hcp0/usr/local/ssl/cert.pem... complete
Cleaning /hcp0/etc/pki/CA/... complete
Cleaning /hcp0/etc/ssh/ssh_host_key.pub... complete
Cleaning /hcp0/etc/ssh/ssh_host_key... complete
Cleaning /hcp0/etc/ssh/ssh_host_rsa_key.pub... complete
Cleaning /hcp0/etc/ssh/ssh_host_rsa_key... complete
Cleaning /hcp0/etc/ssh/ssh_host_dsa_key.pub... complete
Cleaning /hcp0/etc/ssh/ssh_host_dsa_key... complete
Cleaning /hcp0/etc/localtime... complete
Cleaning /hcp0/etc/ntp/drift... complete
Cleaning /hcp0/sp/etc/bash_history... complete
Cleaning /hcp0/sp/tmp/... complete
Cleaning /hcp1/usr/local/ssl/servercert.pem... complete
Cleaning /hcp1/usr/local/ssl/serverkey.pem... complete
Cleaning /hcp1/usr/local/ssl/csr.pem... complete
Cleaning /hcp1/usr/local/ssl/cert.pem... complete
Cleaning /hcp1/etc/pki/CA/... complete
Cleaning /hcp1/etc/ssh/ssh_host_key.pub... complete
Cleaning /hcp1/etc/ssh/ssh_host_key... complete
Cleaning /hcp1/etc/ssh/ssh_host_rsa_key.pub... complete
Cleaning /hcp1/etc/ssh/ssh_host_rsa_key... complete
Cleaning /hcp1/etc/ssh/ssh_host_dsa_key.pub... complete
Cleaning /hcp1/etc/ssh/ssh_host_dsa_key... complete
Cleaning /hcp1/etc/localtime... complete
Cleaning /hcp1/etc/ntp/drift... complete
Cleaning /hcp1/sp/etc/bash_history... complete
Cleaning /hcp1/sp/tmp/... complete
FACTORY mode clear : cleaning log files on XSCF complete
Cleaning under /ssd/apcs recursively... complete
Cleaning under /ssd/core_save recursively... complete
Cleaning under /ssd/fer recursively... complete
Cleaning under /ssd/rsync_cache recursively... complete
Cleaning under /ssd/snapshot recursively... complete
Cleaning under /ssd/snapshot_col recursively... complete
Removing whole /ssd/md_store... complete
FACTORY mode clear : cleaning files on USB-SSD complete
FACTORY mode clear : syncing file systems... complete
FACTORY mode clear : complete

Please turn off the breaker after XSCF halt.

setdefaults_boot -- complete
tracerotate.sh -- complete
mainte_dbcopy.sh -- complete
init -- complete
init: rc3 main process (1262) killed by TERM signal^M

localhost login: -- process stoped (spinit)
Sending all processes the TERM signal... init: console main process (3978) killed by TERM
localhost login: Sending all processes the KILL sinit: console main process (3997) killed by KILL signal^M
init:
localhost login: Saving random seed: [ OK ]^M
Syncing hardware clock to system time [ OK ]^M
Sync file systems
Unmounting file systems: [ OK ]^M
mount: /dev/shm not mounted already, or bad opti[ 594.677746] ff72e000: 00000000 00010000 00000000 00000000
[ 594.743431] ff72e010: 00000000 00000000 00000000 00000000
[ 594.809115] ff72e020: 00000000 ff8d00f8 00000020 00008008
[ 594.874812] ff72e030: 00000000 007f0003 007f0003 00000000
[ 594.940495] ff72e040: 05f30000 10101010 00000000 00000000
[ 595.007160] Starting new kernel
setup_arch: bootmem
mpc85xx_rdb_setup_arch()
arch: exit

[ 644.402275] ===== DEBUG =====
[ 644.436863] FMEM bank/reset      : 0080
[ 644.482631] timeout control      : 00cf
[ 644.528346] =================
1.FMEM(NAND) Test                 >> OK
Booting : [1/1]
REBOOT: BOOT STOP (recover by NFB-OFF/ON)    <<<<<------------------- REMOVE POWER HERE   -------------------------

Remove power from the Building Block for 60 seconds
Set the BB ID via front panel switches to the desired number.
Re-connect power to the BB

After the XSCFU on the building block boots, showhardconf on the master XSCFU on the XBBox, should be able to see the building block's hardware components.

Attachments

This solution has no attachment