Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2108027.1
Update Date:2016-02-23
Keywords:

Solution Type  Problem Resolution Sure

Solution  2108027.1 :   Solaris 11 systems showing a different Serial Number when activating ASR  


Related Items
  • Sun SPARC Enterprise T5220 Server
  •  
  • Sun SPARC Enterprise T5240 Server
  •  
  • Sun SPARC Enterprise T5140 Server
  •  
  • SPARC T5-8
  •  
  • SPARC T5-2
  •  
  • SPARC T5-4
  •  
  • Sun SPARC Enterprise T5120 Server
  •  
  • Sun SPARC Enterprise T5440 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>SPARC-MISC>SN-SPARC: ASR Configuration
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-11935404881>

Applies to:

Sun SPARC Enterprise T5120 Server - Version All Versions and later
Sun SPARC Enterprise T5140 Server - Version All Versions and later
Sun SPARC Enterprise T5220 Server - Version All Versions and later
Sun SPARC Enterprise T5240 Server - Version All Versions and later
Sun SPARC Enterprise T5440 Server - Version All Versions and later
Oracle Solaris on SPARC (64-bit)

Symptoms

 When activating and registering ASR Assets for Solaris 11 Systems, the assets are displayed with a wrong Serial Number. 

Cause

 The Serial Number is incorrectly set in asr-notify.

Solution

An integral component to ASR functionality is the hardware telemetry sources resident on the ASR assets.
Solaris 11 can be configured to send events to the ASR Manager via http(s) using the Solaris asradm command via the asr-notify service.

Prerequisites

The system running Solaris 11 must be qualified for ASR and must support Solaris 11 FMA as telemetry source, as described in the
Auto Service Request Qualified Server Products list :

http://docs.oracle.com/cd/E37710_01/doc.41/e37285/toc.htm

Also, it is assumed that the activation and registration process was performed as described in the ASR documentation :

http://docs.oracle.com/cd/E37710_01/install.41/e18475/ch3_asr_assets.htm#ASRUD165

1. Log in to the ASR asset and get root privileges

2. Verify what S/N is displayed by asr-notify :

#svcprop asr-notify | grep system_id

#svcprop asr-notify | grep system_id
reg/system_id astring 1234345754

The S/N might be incorrect or the command will have an empty output in case there is no S/N set-up in asr-notify.

3. Un-register the asset :

#asradm unregister

4. Set the correct S/N in asr-notify :

#svccfg -s asr-notify:default 'setprop config/system_id = astring: 123456789' 

Numerical string represents the placeholder for the correct serial number.

There is no need for a restart of the service after the correct S/N is set in asr-notify.
asr-notify will read its new configuration once the asset is registered.

5. Register the asset, this time with the correct S/N :

#asradm register

6. Check if the registration was successful :

#asradm list

#asradm list
PROPERTY VALUE
Status Registered Thu Feb 18 05:58:03 2016
System Id 123456789
Asset Id 602f4703-19c9-4bd9-9b16-b504fa97217b
User email.address@mycompany.com
Endpoint URL https://transport.oracle.com

7. Complete the activation process by logging in My Oracle Support(MOS) and approve ASR for the asset.

Doc ID 1329200.1 - How To Manage and Approve Pending ASR Assets In My Oracle Support

 

References

<NOTE:1329200.1> - How To Manage and Approve Pending ASR Assets In My Oracle Support
http://docs.oracle.com/cd/E37710_01/index.htm

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback