Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1018791.1
Update Date:2009-12-15
Keywords:

Solution Type  Technical Instruction Sure

Solution  1018791.1 :   Sun Fire[TM] V210/Sun Fire[TM] V240:Identifying Memory Size in V210 & V240  


Related Items
  • Sun Fire V240 Server
  •  
  • Sun Fire V210 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  

PreviouslyPublishedAs
230570


Description
This Technical Instruction shows you how to identify the size of the memory dimms in the Sun Fire[TM] V210 & Sun Fire[TM] V240.

Steps to Follow
One method of checking the memory size is at the alom level:
sc> showfru
FRU_PROM at MB.P0.B0.D0.SEEPROM
Timestamp: MON JAN 13 12:00:00 2003
Description: SDRAM DDR, 512 MB  <-----Memory identified as 512mb
Manufacture Location:
Vendor: Samsung
Vendor Part No: M3 12L6420DT0-CA2
FRU_PROM at MB.P0.B0.D1.SEEPROM
Timestamp: MON JAN 13 12:00:00 2003
Description: SDRAM DDR, 512 MB
Manufacture Location:
Vendor: Samsung
Vendor Part No: M3 12L6420DT0-CA2
FRU_PROM at MB.P0.B1.D0.SEEPROM is not present
FRU_PROM at MB.P0.B1.D1.SEEPROM is not present
FRU_PROM at MB.P1.B0.D0.SEEPROM
Timestamp: MON JAN 13 12:00:00 2003
Description: SDRAM DDR, 512 MB
Manufacture Location:
Vendor: Samsung
Vendor Part No: M3 12L6420DT0-CA2
FRU_PROM at MB.P1.B0.D1.SEEPROM
Timestamp: MON JAN 13 12:00:00 2003
Description: SDRAM DDR, 512 MB
Manufacture Location:
Vendor: Samsung
Vendor Part No: M3 12L6420DT0-CA2
FRU_PROM at MB.P1.B1.D0.SEEPROM is not present
FRU_PROM at MB.P1.B1.D1.SEEPROM is not present
In this system,4 memory sticks are installed.
Another method is from the OS level,using the prtdiag command:
#/usr/platform/sun4u/sbin/prtdiag -v
System Configuration: Sun Microsystems  sun4u Sun Fire V240
System clock frequency: 167 MHZ
Memory size: 2GB
============================ Memory Configuration
============================
Segment Table:
----------------------------------------------------
Base Address       Size       Interleave Factor  Contains
----------------------------------------------------
0x0                1GB               1           BankIDs 0
0x1000000000       1GB               1           BankIDs 16
Bank Table:
----------------------------------------------------
Physical Location
ID       ControllerID  GroupID   Size       Interleave Way
---------------------------------------------------
0        0             0         1GB             0
16       1             0         1GB             0
Memory Module Groups:
--------------------------------------------------
ControllerID   GroupID  Labels
--------------------------------------------------
0              0        MB/P0/B0/D0,MB/P0/B0/D1 <------2 dimms are shown
						here in this group, we
						know from above that
						there is 1GB in the group
						-so 512MB dimms.
Memory Module Groups:
--------------------------------------------------
ControllerID   GroupID  Labels
--------------------------------------------------
1              0        MB/P1/B0/D0,MB/P1/B0/D1 <------2 dimms are shown
						here in this group, we
						know from above that
						there is 1GB in the group
						-so 512MB dimms.
Different solaris versions will not give the same output of prtdiag -v and
therefore what is indicated is not always be possible.If a problem DIMM ( dual in-line memory module) were found by POST it would remove it from use and therefore prtdiag would
not see it even though it was phsically there,showfru would still be
accurate.


Product
Sun Fire V240 Server
Sun Fire V210 Server

Internal Comments
Audited/updated 12/03/09 [email protected], Entry Level SPARC Content
Team Member

Memory Configuration, Sunfire, V210, V240
Previously Published As
74267

Change History
Date: 2009-12-15
User name: Silvana Villamil
Action: Updated
Comments: Currency check, audited by Dencho Kojucharov, Entry-Level SPARC Content Lead
Date: 2004-06-15
User Name: 13128
Action: Approved
Comment: KE quality checklist applied

Version: 0
Date: 2004-06-15
User Name: 13128
Date: 2004-06-14
User Name: 35315
Action: Approved
Comment: Yes, the additional information added is correct.
Comment: The only part that is always correct is the use of the showfru command.Different solaris versions will not give the same output of prtdiag -v and therefore what it indicated would not always be possible.If a problem DIMM were found by POST it would remove it from use and therefore prtdiag would not see it even though it was phsically there,showfru would still be accurate.

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback