Asset ID:	1-72-1006432.1
Update Date:	2017-05-23
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1006432.1 :   Can't login to the ALOM console on V210/V240 after replaced M/B  


PreviouslyPublishedAs
209017

Symptoms

On V210/V240, M/B replaced from P/N;375-3122 to P/N;375-3150, then can not
loginto the ALOM console. If M/B replaced from 375-3122 to 375-3150,
the parameter on SCC card has been reset by ALOM. Therefore, need to set
the SCC parameter again.
P/N          Discription
---------------------------------
375-3119     CPU x1, V210 only
375-3122     CPU x2, V210 only
375-3149     CPU x1, V210/V240
375-3150     CPU x2, V210/V240
- Replace from failed M/B to the same P/N :  Problem not occurs
- Replace from failed M/B to different P/N : Problem occurs
- Example
The following symptom occurred at login phase on ALOM.
Please login:
SC Alert: Host system has shut down.
Please login: admin
Please Enter password: ********
Invalid login.
Please login: admin
Please Enter password: ********
Invalid login.
Please login: admin
Please Enter password: ********
And the following messages was logged on ALOM log buffer.
SEP 09 06:46:14 dbk-dev01: 00060003: "SC System booted."
SEP 09 10:33:32 dbk-dev01: 00040029: "Host system has shut down."
SEP 10 06:30:29 dbk-dev01: 0004003e: "Different SCC detected. SC will reset itself momentarily."
SEP 10 06:30:30 dbk-dev01: 00040064: "SCC platform data is not valid, will be replaced by SC nvram data."
SEP 10 06:31:05 dbk-dev01: 00060003: "SC System booted."
SEP 10 06:36:11 dbk-dev01: 00040002: "Host System has Reset"

Resolution
If you replaeced V210 M/B from P/N;375-3122 to P/N;375-3150, you set SCC parameter again.

- Exsample
1. Boot up your system.
2. Login to Solaris.
3. Try scadm command as the following.
# scadm userpassword admin
4. Set new password.
5. Re-enter new password.
6. Login to ALOM.
7. Set SCC parameter using setupsc command

Product
Sun Fire V210 Server

Internal Comments
- PTS comment is the following.
The customer cannot login to the ALOM console because the customers SCC data has been reset by ALOM and the user and password information is stored on the SCC card.

Therefore, the users, passwords and parameters on the SCC card have been set back to defaults.
The reason for this set-defaults is because the SCC is tied to the part number of the motherboard.
If you replace a 375-3150 with a 375-3122 then ALOM will consider the SCC card too different to be workable therefore it will issue a set-defaults to the SCC card.
This is because the configuration is regarded as different by ALOM because the part number of the motherboard is different.
V210, Enchilada, SCC data, ALOM, reset, data clear
Previously Published As
78895

Change History
Date: 2004-12-29
User Name: 31620
Action: Approved
Comment: Verified Metadata
Verified still correct for audience - internal
Checked review date 2005-10-26
Checked for TM - none needed
Publishing
Version: 9
Date: 2004-12-29
User Name: 31620
Action: Accept
Comment:
Version: 0
Date: 2004-12-29
User Name: 35315
Action: Approved
Comment: Andy

I would say to go with it being internal.

thanks

Tony
Version: 0
Date: 2004-12-29
User Name: 31620
Action: Rejected
Comment: See previous comments.
Version: 0
Date: 2004-12-29
User Name: 31620
Action: Add Comment
Comment: HI Anthony,

Thank you for doing the TR on this article.

Just before I publish this article, (which I am happy to do), I notice that the "audience" is set to "free" for this article....is this correct ? .... should it not be "internal" ?

If you can answer a couple of questions for me, I'll be happy to publish :

o Does this article cause a security issue ?
o Would a customer be expected to execute this procedure without our intervention?
o If it was "free" or "contract", could our competitors use it to their own advantage ?

I suppose the question is, Should this be public knowledge or kept within Sun ?

If you can address my concerns, I'll publish it right away.

Best Regards,

Andy MacBain
Knowledge Engineer
Version: 0
Date: 2004-12-29
User Name: 31620
Action: Accept
Comment:
Version: 0
Date: 2004-12-27
User Name: 35315
Action: Approved
Comment: Thanks for making the updates,looks good now.

Tony
Version: 0
Date: 2004-12-27
User Name: 35315
Action: Accept
Comment:
Version: 0
Date: 2004-12-26
User Name: 31906
Action: Approved
Comment: Updated. Pleas review this document.
Version: 0
Date: 2004-12-21
User Name: 35315
Action: Rejected
Comment: You ignore my comment from 11-22-2004.Yes it does apply to v240.Document that says 3122 was not used in v240 is wrong.I actually receive v240's with that part number as do many others.When my system needed systemboard to be replaced,I ran into problem you described because I replaced it with part number other than 3122.As the PTS NPI lead for this product I will not approve this SRDB until the v240 is included.
thanks

Tony
Version: 0
Date: 2004-12-21
User Name: 35315
Action: Accept
Comment:
Version: 0
Date: 2004-12-20
User Name: 31906
Action: Approved
Comment: The same failure NOT occurs on V240. Because V240 can not install P/N;375-3119/3122.
This has been written on this document.
Please review.
Version: 0
Date: 2004-12-20
User Name: 31906
Action: Add Comment
Comment: The same failure NOT occurs on V240. Because V240 can not install P/N;375-3119/3122.
This has been written on this document. Could you please provide a detail info that I need
to update?
Version: 0
Date: 2004-12-20
User Name: 35315
Action: Rejected
Comment: Please see prevoius comments.I don't see that changes were made.

thanks

Tony
Version: 0
Date: 2004-12-20
User Name: 35315
Action: Accept
Comment:
Version: 0
Date: 2004-12-20
User Name: 35315
Action: Add Comment
Comment: I still don't see the changes to include v240.Below is what I see,please explain where
the changes were made.

Problem Statement:

On V210, M/B replaced from P/N;375-3122 to P/N;375-3150, then can not login
to the ALOM console. If M/B replaced from 375-3122 to 375-3150, the parameter
on SCC card has been reset by ALOM. Therefore, need to set the SCC parameter
again. It doesn't occurr on V240. Because V240 uses 375-3150/3149, and can't
install 375-3122/3119. The M/B type on V240 not changed on any replacing.

P/N Discription
---------------------------------
375-3119 CPU x1, V210 only
375-3122 CPU x2, V210 only
375-3149 CPU x1, V210/V240
375-3150 CPU x2, V210/V240

- Replace and problem
From To Problems
-------------------------------------------
375-3119 375-3149 Occurs
375-3122 375-3150 Occurs
375-3149 375-3149 Not occurrs
375-3150 375-3150 Nor occurrs
375-3149 375-3119 Occurs
375-3150 375-3122 Occurs



Also the title needs to be changed
Version: 0
Date: 2004-12-19
User Name: 31906
Action: Approved
Comment: I updated. Please review this document until 12/23.
Version: 0
Date: 2004-12-17
User Name: 35315
Action: Rejected
Comment: Hello

Perhaps there is some miscommunication on my part.I have rejected
this document and asked that the v240 be included since I have
v240 delivered here with the affected part number boards.Please
update document to include v240.

thanks

Tony
Version: 0
Date: 2004-12-06
User Name: 35315
Action: Accept
Comment:
Version: 0
Date: 2004-12-05
User Name: 31906
Action: Approved
Comment: Updated. Please review this document.
Version: 0
Date: 2004-12-01
User Name: 89705
Action: Rejected
Comment: Hi,

I'll put this document back to the draft state for you
to update, and then re-submit the document again for
review. The state will show rejected, FYI.

Once you have finished updating the document, please
re-submit for review.

Regards
Bong
Version: 0
Date: 2004-11-22
User Name: 35315
Action: Add Comment
Comment: The problem starement looks better.Please note that this problem is also applicable to the v240 so make changes that implicate that system as well.The resolution section could be upgraded a little.I would suggest reminding the reader of the fact that the user/password would be set back to the default of admin/admin1.

thanks

Tony
Version: 0
Date: 2004-11-20
User Name: 89705
Action: Accept
Comment:
Version: 0
Date: 2004-11-18
User Name: 108410
Action: Unlock
Comment:
Version: 0
Date: 2004-11-12
User Name: 108410
Action: Accept
Comment:
Version: 0
Date: 2004-11-11
User Name: 31906
Action: Approved
Comment: I updated. Please review.
Version: 0
Date: 2004-11-11
User Name: 35315
Action: Rejected
Comment: please see comments section

thanks

Tony
Version: 0
Date: 2004-11-11
User Name: 35315
Action: Add Comment
Comment: I have recreated this problem in the lab.It is very good subject matter for an SRDB in my opinion.I do however feel that the problem statement and resolution need to be completely re written.If possible the problem statement should include screen output showing the error messages.The resolution should show an example of what needs to be done.

thanks

Tony
Version: 0
Date: 2004-10-29
User Name: 35315
Action: Accept
Comment:
Version: 0
Date: 2004-10-26
User Name: 31906
Action: Approved
Comment: Please review.
Version: 0
Date: 2004-10-26
User Name: 31906
Action: Created
Comment:
Version: 0
Product_uuid
dc751a7c-eece-4157-8e4e-376351aa49fa|Sun Fire V210 Server

Attachments

This solution has no attachment