SuperCluster: OES/ID SMF Service does not exist in some SuperCluster LDoms and Zones

Asset ID:	1-72-2165959.1
Update Date:	2017-08-08
Keywords:

Solution Type Problem Resolution Sure

Solution 2165959.1 : SuperCluster: OES/ID SMF Service does not exist in some SuperCluster LDoms and Zones

Applies to:

SPARC SuperCluster T4-4 - Version All Versions and later
SPARC SuperCluster T4-4 Half Rack - Version All Versions and later
SPARC SuperCluster T4-4 Full Rack - Version All Versions and later
Oracle SuperCluster T5-8 Half Rack - Version All Versions and later
Oracle SuperCluster T5-8 Full Rack - Version All Versions and later
Information in this document applies to any platform.
All T4-4 SuperClusters are impacted, All manually created database or application zones are impacted , All database zones created prior to October 2015 could be impacted.
Can prevent proper SR filing via platinum , Can prevent certain tools starting with April 2016 QFSDP and beyond from working properly

Symptoms

All T4-4 SuperClusters are impacted, All manually created database or application zones are impacted , All database zones created prior to October 2015 could be impacted. Can prevent proper SR filing via platinum , Can prevent certain tools starting with April 2016 QFSDP and beyond from working properly. This includes the Infiniband switch upgrade tools. So this needs to be done prior to patching windows. If the following command does not return oes/id then you will have to create the smf service following the procedure in the solution . This check and remediation needs to be done in every single LDom and zone. Also remember to add the SMF service in any future created application zones.

If the following does not return a result, this note applies to you.

svcs -a |grep oes

Changes

None

Cause

The early installation procedures and tool sets did not require this service. However it was determined that this service is the easiest way to ID that a particular virtual host is part of a SuperCluster.

Solution

Data to be collected for installing the service

Build type:
- For zones in LDoms that have an OES/ID service Build type = svcprop –p configuration/build oes/id
- For LDoms and zones that have the older version Build type = ssc/identification service = svcprop –p configuration/build ssc/identification
- For the earliest systems without either oes/id nor ssc/identification Build type = 1.0
- For zones in LDoms that have an OES/ID service Rack Serial Number = svcprop –p rack/serial_number oes/id
- For LDoms and zones that have the older version svcprop –p rack/serial_number ssc/identification
- For the earliest systems without either oes/id nor ssc/identification obtain serial_number form the Service processor on the first compute node.
Type : this will be one of the following
- app = Application domain
- db = Database domain
- root = Root domain
- SSC-ExaVM = Database Zone
- SSC-VM = Application Zone
Domain Type and Domain Subtype (Both will be the same) : this will be one of the following
- app
- db
- root
OVM Domain Type : this will be one of the following
- ldom
- zone

To install the service

Copy the oes_id.xml file to the node/ldom/zone

cat /lib/svc/manifest/system/oes/oes_id.xml
<?xml version="1.0"?>
<!--

-->
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<service_bundle type="manifest" name="OES-identification">
<service name="system/oes/id" type="service" version="1">
<property_group name="startd" type="framework">
<propval name="duration" type="astring" value="contract"/>
</property_group>
<instance name="default" enabled="true">
<dependency name="filesystem-local" grouping="require_all" restart_on="none" type="service">
<service_fmri value="svc:/system/filesystem/local:default"/>
</dependency>
<exec_method type="method" name="start" exec=":true" timeout_seconds="0"/>
<exec_method type="method" name="stop" exec=":true" timeout_seconds="0"/>
</instance>
<stability value="Unstable"/>
<template>
<common_name>
<loctext xml:lang="C"> OES identification information </loctext>
</common_name>
<description>
<loctext xml:lang="C"> Provides OES identification information </loctext>
</description>
</template>
</service>
</service_bundle>

Create the directory /lib/svc/manifest/system/oes

mkdir –p /lib/svc/manifest/system/oes
Change the group owner of the directory to sys

chgrp sys /lib/svc/manifest/system/oes
Copy the oes_id.xml to this directory

cp oes_id.xml /lib/svc/manifest/system/oes
Change the group ownership of the oes_id.xml

chgrp sys /lib/svc/manifest/system/oes/oes_id.xml
Restart the manifest-import service to load the new service

svcadm restart manifest-import
Configure the properties for the service

svccfg -s svc:/system/oes/id:default addpg oes application
svccfg -s svc:/system/oes/id:default setprop oes/type= astring: <app|db|SSC-ExaVM>
svccfg -s svc:/system/oes/id:default setprop oes/node= astring:<node name>
svccfg -s svc:/system/oes/id:default addpg configuration application
svccfg -s svc:/system/oes/id:default setprop configuration/domain_type= astring: <db|app>
svccfg -s svc:/system/oes/id:default setprop configuration/domain_subtype= astring: <db|app>
svccfg -s svc:/system/oes/id:default setprop configuration/ovm_domain_type= astring: <ldom|zone>
svccfg -s svc:/system/oes/id:default setprop configuration/build = astring: <build type>
svccfg -s svc:/system/oes/id:default addpg rack application
svccfg -s svc:/system/oes/id:default setprop rack/serial_number= astring:<Rack Serial Number>
Refresh the service to make all the new properties active

svcadm refresh svc:/system/oes/id:default
Verify the rack serial number

svcprop -p rack/serial_number oes/id

Attachments

This solution has no attachment