Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1011200.1 : Memory mapping for Sun Fire[TM] T1000/T2000
PreviouslyPublishedAs 215390 Description This document describes the memory mapping for Sun Fire[TM] T1000/T2000 and helps to identify the physical memory modules (DIMMs) installed and configured in the system. Steps to Follow The 'prtdiag -v' command on T1000 and T2000 reports only the total memory size in the system and does no longer provide information about the physical memory that is installed and configured. You can get the information for the configured memory from the output of the ALOM command 'showcomponent' in the following format: MB/CMP0/<channel#>/<rank#>/<dimm#> Example for Sun Fire T2000 with 16x DIMMs
installed: Product Sun Fire T1000 Server Sun Fire T2000 Server Internal Comments The memory maps are available in the Sun System Handbook:
For the Sun Fire T1000 Memory Map, refer to Figure 1. For the Sun Fire T2000 Memory Map, refer to Figure 2. T1000, T2000, memory map, dimm, socket number, physical memory, showcomponent Previously Published As 87942 Change History User Name: T209852 Action: Update Started Comment: Reworking article in preparation for IBIS migration. Version: 0 Date: 2007-01-22 User Name: 7058 Action: Approved Comment: Changes implemented. OK to publish. Version: 7 Date: 2007-01-22 User Name: 106061 Action: Approved Comment: Hi NIta, As requested, I replaced the attachments (images) with the links you provided for the customer to access the external memory pages: https://support.oracle.com/handbook_private/Devices/Memory/MEM_SunFireT2000.html The links (images) that are internal to Sun are moved to the Internal section. We need them for internal use, as this document was initially not part of the Normalization project. Let me know if the updated links work on the external sunsolve. Thanks, Dencho Version: 0 Date: 2007-01-19 User Name: 7058 Action: Reassign Comment: Hi T1000/T2000 Normalization team: A customer pointed out a problem with some attachments in doc ID 87942 that slipped right by us. Let me explain. It slipped by because inside SWAN they work, even on external sunsolve within SWAN. But if a customer outside SWAN tries to connect to these files, they cannot see them. Here is the customer feedback about the attachments. I tested it outside SWAN and the customer is correct. -------------------------------------- Email: gareth.randall@uk.easynet.net Contact: Gareth Randall Subject: General Link Problem Comments: Broken links to key images in this page: http://sunsolve.sun.com/search/document.do?assetkey=1-9-87942-1 Links are as follows, and appear to be internal to Sun: https://support.oracle.com/handbook_private/Devices/Memory/images/MEM_SunFireT2000.02.gif https://support.oracle.com/handbook_private/Devices/Memory/images/MEM_SunFireT2000.03.gif -------------------------------------- I think what you can do is remove the attachments and instead, link the customers to these external memory pages as follows: https://support.oracle.com/handbook_private/Devices/Memory/MEM_SunFireT2000.html https://support.oracle.com/handbook_private/Devices/Memory/MEM_SunFireT2000.html I had to unpublish the doc temporarily. I'm moving it over to Dencho's queue now..hope that's the right person to move it to. If not, let me know and I can transfer it to someone elses queue. Once you look it over and add the links instead of the attachments or, maybe decide upon something different? You can submit the corrected doc back to me. Thanks, -nita Attachments This solution has no attachment |
||||||||||||
|