Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1010705.1 : Reboot of one domain, 2 others dstop with “Timeout on head of CI queue”
PreviouslyPublishedAs 214778
Applies to:Sun Fire 12K ServerSun Fire 15K Server Sun Fire E20K Server Sun Fire E25K Server Sun SPARC Sun OS All Platforms SymptomsA platform has been upgraded from sms 1.3 to sms 1.4.1. After the sms 1.3 upgrade to sms 1.4.1, the domains needed to be rebooted to take the new firmware in effect.One domain has been shutdown with setkeyswitch and within a short time frame 2 other domains crashed with a dstop. The dstops look like this: redxl> dumpf load dsmd.dstop.040916.1721.32 CauseIt turns out, an out-of-date, sms-backup file was restored during the sms upgrade. Causing conflicting information in the .pcd files and in the platforms registers. So a part of the PCD, the Platform Configuration Database, the files in $SMSVAR/SMS/.pcd/ contain information inconsistent with the current domain layout reality. And this will cause problems during setkeyswitch operations.SolutionSetkeyswitch off and on the domains, this will rewrite the PCD information.This preferably done when the applications have been shutdown on the domains. This because it is very difficult to anticipate what is going to happen in the scenario. Product Sun Fire E25K Server Sun Fire E20K Server Sun Fire 15K Server Sun Fire 12K Server Internal Comments Reboot of one domain, 2 others dstop with “Timeout on head of CI queue” This is related to CASM bug 6592200 submitted Aug 13 2007. If this timeout is received check the casm allocations to make sure they are ok. Each slot that has a system board should also have a casm assigned Please escalate any cases that fit this bug reboot, domain, dstop, keyswitch, pcd, corruption, inconsistency, smsbackup, smsrestore, setkeyswitch, crash, panic Previously Published As 78300 Attachments This solution has no attachment |
||||||||||||
|