Asset ID: |
1-71-1617531.1 |
Update Date: | 2017-06-06 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1617531.1
:
How to reset CP3260 ILOM password when all passwords (ILOM and OS) are not available
Related Items |
- Sun Netra CP3260 ATCA Blade Server
|
Related Categories |
- PLA-Support>Sun Systems>SPARC>Usx/Blade/Netra>SN-SPARC: Netra Cxxxx
|
In this Document
Created from <SR 3-8328506021>
Applies to:
Sun Netra CP3260 ATCA Blade Server - Version Not Applicable and later
Information in this document applies to any platform.
Goal
Know how to reset CP3260 ILOM password when previous one is lost.
Solution
There are TWO possible situation:
- ILOM password is still known/available (could access ILOM), only need to reset it back to the default (changeme)
- ILOM password is NOT known/available (no access to ILOM), and need to reset the password (changeme) to set a new one
For #1, the steps are as following:
- Log into ILOM using the existing password
- Change directory to /SP
- Set the parameter "reset_to_defaults" to "factory"
- Reset SP
Example output of the above steps:
SUNSP-1B000N login: root
Password:
Waiting for daemons to initialize...
Daemons ready
Sun(TM) Integrated Lights Out Manager
Version 3.0.9.2 r50482
......
->
-> cd /SP
/SP
-> ls
/SP
......
Properties:
customer_frudata = (none)
hostname = (none)
reset_to_defaults = none
system_contact = (none)
system_description = Netra CP3260, ILOM v3.0.9.2, r50482
system_identifier = (none)
system_location = (none)
......
->
-> set reset_to_defaults=factory
Set 'reset_to_defaults' to 'factory'
->
-> reset /SP
Are you sure you want to reset /SP (y/n)? y
Performing reset on /SP
INIT: Switching to runlevel: 6
......
For #2, the steps to reset the blade password are:
- Connect serial cable to CP3260 blade
- Install CP3260 in CT900 chassis, and power on the blade ([clia] activate board <slot #>) if not powered up automatically
- Watch blade boot and look for "Booting Linux in 5 seconds..."
- At "Booting Linux in 5 seconds..." type "xyzzy". You don't have to press "Enter"
- You will be taken to "u-boot>" command prompt.
- Type "setenv preserve_conf no" and press "Enter"
- Type "setenv factory_default yes" and press "Enter" (some blades don't have this option)
- Type "saveenv"
- Type "boot" u-boot> boot
- Wait for system to complete booting and verify you can login to the ILOM using the default username and password. "root" and "changeme"
Example of output from step 3-5:
U-Boot 1.1.1
custom Sun Microsystems U-Boot 1.3 (Dec 1 2009 - 14:44:32) r50482
CPU: MPC885ZPnn at 133 MHz: 8 kB I-Cache 8 kB D-Cache FEC present
Board: SPARC885
Watchdog enabled
I2C: ready
DRAM:
trying 128 MBytes
(64 MB SDRAM) 64 MB
Memory Tests: DA A1 A2 00 FF 55 AA T2 T3 T4
POST memory PASSED
FLASH: 32 MB
In: serial
Out: serial
Err: serial
Net: FEC ETHERNET
POST i2c 48 49 51 52 53 54 56 68 70 PASSED
POST cpu PASSED
POST ethernet PASSED
Booting linux in 5 seconds... <<--- type "xyzzy" without enter
u-boot>
Example of output from steps 6-8:
u-boot> printenv
bootcmd=setenv bootargs root=/dev/mtdblock4 rootfstype=squashfs ro mtdparts=phys:384K(u1),128k(e1),1536K(k1),14M(r1),384K(u2),128K(e2),1536K(k2),14M(r2); bootm 0xfe080000
bootdelay=5
ethaddr=00:21:28:7f:a3:8f
preserve_conf=yes
set_factory_defaults=no
baudrate=9600
scc_has_moved=no
stdin=serial
stdout=serial
stderr=serial
ethact=FEC ETHERNET
Environment size: 343/16380 bytes
u-boot> setenv preserve_conf no
u-boot> setenv set_factory_defaults yes
u-boot> saveenv
Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1/1 sectors
Writing to Flash... done
Protected 1 sectors
u-boot>
Example of output from step 9:
u-boot> boot
## Booting image at fe080000 ...
Image Name: Linux-2.4.22
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 812258 Bytes = 793.2 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
do_bootm_linux():
argv[0]=bootm
argv[1]=0xfe080000
## Current stack ends at 0x03D388B8 => set upper limit to 0x00800000
No initrd
## cmdline at 0x007FFF00 ... 0x007FFF80
.
.
. (booting messages)
Attachments
This solution has no attachment