Could not get the signature for domain X

When showplatform gives out the error:

"Could not get the signature for domain X"

% showplatform
...
Q - - Powered Off
R - - Powered Off
Could not get the signature for domain B
Could not get the signature for domain C
Could not get the signature for domain D


- Troubleshooting:

'showplatform' examines the PCD for domain state. If the PCD
indicates the keyswitch position is ON|DIAG|SECURE, 'showplatform'
attempts to access the domain's Golden IOSRAM to determine the
domain signauture.

- Resolution:

The more common cause of this error is that the PCD does not
accurately reflect the true state of the platform. See "Background
information" for some scenarios that can result in PCD discrepancy.

To correct the discrepancy, perform a 'setkeyswitch standby' followed
by a 'setkeyswitch off' for all domains that report the signature
error. Answer 'y' to any queries.

In cases of extreme PCD corruption, setkeyswitch operations may
not succeed. If this occurs, the PCD for the effected domain(s)
can be returned to defaults. If setkeyswitch is not successful,
do the following to clean up the PCD. Note this will null the
board assignments and available component lists (ACLs) for the
effected domains.

- Note the configuration of affected domain(s). Include board
assignments, ACLs, etc.
- Issue 'setdefaults -d X -p', where X is the domain [A..R]. The
-p preserves the NVRAM settings.
- Reassign boards to the domain(s) with 'addboard' and setup any
ACLs with 'setupplatform'.

- Summary of part number and patch ID's

- References and bug IDs

- Additional background information:

Two scenarios that can lead to the above situation are:

1. Incomplete shutdown of domains prior to a platform poweroff

An 'init 0' is done to the domain, so the domain is down. But, the
PCD still has the keyswitch as ON|DIAG|SECURE. Then the SCs are
shutdown and the platform powered off. When power is restored to
the platform, the PCD doesn't reflect the powered off state of the
domain.

This is different from a total power loss because SMS is shutdown
gracefully. There is no indicator to SMS to indicate that a power
recovery is needed, so domains the PCD lists as ON|DIAG|SECURE are
taken at face value.

2. Restoration of an old/stale smsbackup file

Similar logic to above, but even if the domains were appropriately
sekeyswitched OFF, a stale smsbackup file can restore a PCD that has
incorrect keyswitch states.

Also of note is that setkeyswitch operations to ON|DIAG|SECURE may
not be successful. PCD consistency is verified as part of POST and if
the PCD is inconsistent, POST does not continue as the state of the
platform is in question and further activity could interrupt running
domains. A typical POST failure indicative of PCD inconsistency is:

pcs_pcd_get_domain_info(): Golden sram for domain 7=H = IO14,
Not in active slot1 vector 00000
pcs_pcd_get_domain_info(): MAND Net for domain 7=H = IO14,
Not in active slot1 vector 00000
pcs_pcd_get_domain_info(): Golden sram for domain 8=I = IO16,
Not in active slot1 vector 00000
pcs_pcd_get_domain_info(): MAND Net for domain 8=I = IO16,
Not in active slot1 vector 00000
Exitcode = 44: Error accessing Physical Config Database


Kudos to: Scott Davenport
APPLIES TO: Hardware/Sun Fire /15000, Hardware/Sun Fire /12000

Readers who read this page, also read: