![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1006676.1 : Sun Fire[TM] V1280, E2900, or Netra 1280, 1290: a Solaris[TM] shutdown followed by a lom poweroff and poweron sequence can cause an unplanned SC reset.
PreviouslyPublishedAs 209307
Applies to:Sun Netra 1280 ServerSun Fire V1280 Server Sun Fire E2900 Server Sun Netra 1290 Server - Version: Not Applicable and later [Release: N/A and later] All Platforms SymptomsSystem Controller (SC) reset could occur unexpectedly.A Sun Fire[TM] V1280, E2900, or Netra 1280, or 1290 can suffer an unplanned System Controller(SC) reset if Solaris[TM] on the domain is shutdown followed by an immediate poweroff and then poweron sequence at the lom prompt. CauseThe behavior appears something like the following:
The following example comes from the console log of a system that encountered this exact issue: lom> poweron/N0/PS0: powered on SolutionThe SC reset caused by this sequence of events is very rare (and harmless). But, you can avoid being surprised by this behavior by running "resetsc" at the lom prompt before running the poweron command. lom> poweroff Executing resetsc will free up SC resources and place it in a "known" state. The poweron command will then power on all boards without any issues.
The unplanned SC reset is harmless and the subsequent execution of POST usually results in all boards passing without any issues. The SC is capable of resetting itself when necessary, but to avoid the inconvenience of running POST on all system boards (and any delays as a result), run resetsc before powering on all components and save yourself some time and hassle of worrying if there is a problem. Product Sun Fire V1280 Server Netra 1280 Server Netra 1290 Server Sun Fire E2900 Server 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. Bug 5060577 describes the above problem and is unresolved. Attachments This solution has no attachment |
||||||||||||
|