Sun Fire 15K Server
 
Sun Fire E20K Server
 
Sun Fire E25K Server
 
Sun Fire 12K Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
 
_Old GCS Categories>Sun Microsystems>Servers>High-End Servers
 

Applies to:

Goal

This article will describe the structure describing the persisted database files used by the "pcd" service.

Solution

The platform configuration database (pcd) daemon provides and manages controlled access to platform, domain, and system board configuration data. It is a System Management Software (SMS) daemon running on the system controller (SC) and a key component of SMS configuration. All system management applications access the database information through the "pcd" daemon.



The "pcd" service maintains three distinct and separate sets of configuration data through which it uses to facilitate notifications to registered system management (SMS) applications when pertinent database changes have occurred. These notifications are registered as events and transparent to the user.
Platform Configuration Data
Located at the following location on the System Controller (SC):

/var/opt/SUNWsms/.pcd/platform_info

This file provides (in persistent storage) the specific database information specific to the platform configuration.

When "pcd" is initiated and reads this database file, it will first check for the format version of this file where "pcd" will compare the file's version format against what it supports.
At this present moment, SMS 1.2 based "pcd" service will support version 1, SMS 1.3 based pcd service supports file version 2 and SMS 1.4 / SMS 1.4.1 / SMS 1.5 / SMS 1.6 based pcd service supports file version 3.
The SMS version vs file format version correlation is always automatically facilitated in SMS installations and requires no user intervention.

The platform configuration data for each version are structured as follows:

<Platform type> | <Platform Name> | <Rack ID> | <Coherent Mem Addr Slice Map>
| <Clock Freq> | <Clock Device Type> | <SC IP Addr> | <SC Logical IP Host
Addr>| <SC Host Netmask> | <SC0 to SC1 IP Addr> | <SC1 to SC0 IP Addr> | <SC to
SC Netmask>

<Platform type> | <Platform Name> | <Rack ID> | <Coherent Mem Addr Slice Map>
<Clock Freq> | <Clock Device Type> | <SC IP Addr> | <SC Logical IP Host Addr> |
<SC Host Netmask> | <SC0 to SC1 IP Addr> | <SC1 to SC0 IP Addr> | <SC to SC
Netmask> | <COD Head Room>

<Platform type> | <Platform Name> | <Rack ID> | <Coherent Mem Addr Slice Map>
| <Clock Freq> | <Clock Device Type> | <SC IP Addr> | <SC Logical IP Host
Addr>| <SC Host Netmask> | <SC0 to SC1 IP Addr> | <SC1 to SC0 IP Addr> | <SC to
SC Netmask> | <COD Head Room> | <Chassis Serial Number>

Domain Configuration Data

Located at the following location on the System Controller (SC):

/var/opt/SUNWsms/.pcd/domain_info

This file provides (in persistent storage) the specific database information specific to the domain configuration.

When "pcd" is initiated and reads this database file, it will first check for the format version of this file where pcd will compare the file's version format against what it supports.
At this present moment, SMS 1.2 based "pcd" service will support version 1 while SMS 1.3 / SMS 1.4 / SMS 1.4.1 / SMS 1.5 / SMS 1.6 based pcd service supports file version 2.
The SMS version vs file format version correlation is always automatically facilitated in SMS installations and requires no
user intervention.

The domain configuration data for both versions are structured as follows:

<domain#> | <domain tag> | <OS Ver> | <OS Type> | <Slot 0 Avail Board List> |
<Slot 1 Avail BL> | <Slot 0 Assigned Board List> | <Slot 1 Assigned BL> | <Slot
0 Active Board List> | <Slot 1 Active BL> | <Golden SRAM exp.slot> |
<keyswitch> | <Active Ethernet exp.slot> | <Creation Time> | <Domain State> |
<Bringup Priority> | <IP Host Address> | <Hostname> | <Host Netmask> |
<Broadcast Address> | <OBP Virtual Addr> | <OBP Physical Addr>

<domain#> | <domain tag> | <OS Ver> | <OS Type> | <Slot 0 Avail Board List> |
<Slot 1 Avail BL> | <Slot 0 Assigned Board List> | <Slot 1 Assigned BL> | <Slot
0 Active Board List> | <Slot 1 Active BL> | <Golden SRAM exp.slot> |
<keyswitch> | <Active Ethernet exp.slot> | <Creation Time> | <Domain State> |
<Bringup Priority> | <IP Host Address> | <Hostname> | <Host Netmask> |
<Broadcast Address> | <OBP Virtual Addr> | <OBP Physical Addr> | <Domain
Reserved RTU>

System Board Configuration Data

Located at the following location on the System Controller (SC):

/var/opt/SUNWsms/.pcd/sysboard_info

This file provides (in persistent storage) the specific database information specific to the system boards' configuration.

When "pcd" is initiated and read this database file, it will first check for the format version of this file where pcd will compare the file's version format against what it supports. At this present moment, SMS 1.2 based "pcd" service will support version 1, SMS 1.3 / SMS 1.4 / SMS 1.4.1 based pcd service supports file version 2, SMS 1.5 based pcd service supports file version 3 and SMS 1.6 based pcd service supports file version 4.
The SMS version vs file format version correlation is always automatically facilitated in SMS installations and requires no user intervention.

The system board configuration data for both versions are structured as follows:

NOTE
It is not supported to edit any of these pcd files. Contact Oracle Support Services for assistance in dealing with any pcd file corruption.

This solution has no attachment