Template Version: @(#)onepager.txt 1.35 07/11/07 SMI
Copyright 2007 Sun Microsystems

1. Introduction
   1.1. Project/Component Working Name:

	"New component types in PRI"

   1.2. Name of Document Author/Supplier:

	Sean Ye and Anthony Yznaga

   1.3. Date of This Document:

	07/10/09
	
	1.3.1. Date this project was conceived:

		11/12/07

   1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project:

		Solaris PAC

	1.4.2. The ARC(s) you expect to review your project:

		FWARC

	1.4.3. The Director/VP who is "Sponsoring" this project:

		Bill.Nesheim@sun.com
		Quresh.Dhoon@sun.com

	1.4.4. The name of your business unit:

		Software

   1.5. Email Aliases:
    	1.5.1. Responsible Manager:	Michelle.Lei@sun.com
    	1.5.2. Responsible Engineer:	Sean.Ye@sun.COM
                                        Anthony.Yznaga@Sun.COM
    	1.5.3. Marketing Manager:
	1.5.4. Interest List:

2. Project Summary
   2.1. Project Description:
	The product serial number is required for service entitlement and
	for FRU traceablility where only chassis serial number is not
	adequate, for example, the blade based products.

	This case proposes a new PRI record to store the product
	serial number information in the firmware.  The libtopo and
	topo enumerators will retrieve such information using standard
	libpri interfaces and add it in the authority of hc FMRIs.

        To support FMA diagnosis of a faulted SP, PRI Specofication
        must be updated to allow for a component node of type "sp"
        so that topology including the sp can be built by Solaris. 

	For more details, refer to
	    PSARC/2007/650 Product Serial Number for FMRI
	    6627041 Add a PSN nv-pair to the authority portion of the FMRI 

   2.2. Risks and Assumptions:

	Assumption 1:  The future sparc platforms will store the correct
		       product serial information in the PRI record being
		       proposed.
	
3. Business Summary
   3.1. Problem Area:

	We need to be associate a fault/FRU with the product serial number
	(identity property assigned to some collection of components which
	comprise a "product"), which in turn is the identity property
	against which service entitlement checking is applied. We also don't
	want to loose the unique identity of the physical chassis that the
	identified FRU is located in, which is becoming more the case for
	some of the storage products that incorporate some of the volume
	server products. Its also the case for some of the blade-based
	products as well.

	The product serial information needs to be stored in the
	system firmware.  For x86, it's SMBIOS.  For sun4v, it's PRI.

   3.2. Market/Requester:

	Sun Service

   3.3. Business Justification:

	Required for service entitlement and FRU traceability.

   3.4. Competitive Analysis:

	N/A

   3.5. Opportunity Window/Exposure:

	N/A

   3.6. How will you know when you are done?:

	This project will be complete when the putbacks to firmware
	gates and Solaris are complete.
	

4. Technical Description:
    4.1. Details:

	This case proposes a following type property values in the PRI 
    component node

    product			The product

    chassis			A system chassis

    sp			    A service processor.
    
	The tasks of this project are:
	- Add new PRI record in firmware
	- Change topo enumerators to retrieve product-sn from PRI
	  and add to the authorities of hc FMRi.

    4.2. Bug/RFE Number(s):

	6627041 Add a PSN nv-pair to the authority portion of the FMRI 
    
    4.3. In Scope:

	- All technical changes required for product-sn support.

    4.4. Out of Scope:

	- All non-technical processes: eg, make sure the correct
	  information filled in PRI, be consistent with contract
	  database, etc.
    
    4.5. Interfaces:

    4.5.1  Imported Interfaces :

     Interface                   Classification     Comments
     =========                   ==============     ========

     PRI structures              Sun Private        Defined by FWARC/2008/761
         


    4.5.2 Exported Interfaces:

      Interface                  Classification     Comments
      ================           ==============     ========

      "product" - value for       Sun Private        Defined in section 1.3.1 of
      the "type" property in                         the specification.
      the "component" node

      "chassis" - value for       Sun Private        Defined in section 1.3.1 of
      the "type" property in                         the specification.
      the "component" node

      "sp" - value for            Sun Private        Defined in section 1.3.1 of
      the "type" property in                         the specification.
      the "component" node
 
    4.6. Doc Impact:

	PRI specification needs to be updated.
    
    4.7. Admin/Config Impact:

	The admin will find product-sn in the FRU identifier strings.
    
    4.8. HA Impact:

	None.
    
    4.9. I18N/L10N Impact:

	None.
    
    4.10. Packaging & Delivery:

	The SUNWfmd package will carry the Solaris FMA related
	changes.  System Firmware will include the modifications to
	the Hypervisor on sun4v.
    
    4.11. Security Impact:

	None.
    
    4.12. Dependencies:

	None.

5. Reference Documents:

	http://sac.eng/PSARC/2007/650

6. Resources and Schedule:
   6.1. Projected Availability:

	First putback to Nevada then backport to s10u9.
	 First available in RF RR.

   6.2. Cost of Effort:

	feature implementation:		2 weeks *
	unit testing			1 week
	documentation			1 day
	Code review/RTI			1 week
	
	Need to validate effort required for firmware change.

   6.3. Cost of Capital Resources:

	Need short-term use of RF platform.

   6.4. Product Approval Committee requested information:
   	6.4.1. Consolidation or Component Name:
	
		ON
		System Firmware

	6.4.3. Type of CPT Review and Approval expected:

		FastTrack

        6.4.4. Project Boundary Conditions:

		TBD.

	6.4.5. Is this a necessary project for OEM agreements:

		No.

	6.4.6. Notes:
	
		None.

	6.4.7. Target RTI Date/Release:

		08/03/2009 onnv_121

	6.4.8. Target Code Design Review Date:

		07/30/2009

	6.4.9. Update approval addition:
	
		N/A

   6.6. ARC Exposure:

		open

       6.6.1. Rationale:

		N/A


7. Prototype Availability:
   7.1. Prototype Availability:

	N/A

   7.2. Prototype Cost:

	N/A