- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: 969KS/200 Memory configuration.
HPE 9000 and HPE e3000 Servers
1748259
Members
3843
Online
108760
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2001 12:23 AM
тАО01-30-2001 12:23 AM
We bought and HP CE installed a 512 MB memory module (P/N A3737A) on a 969KS/200. Resultant memory configuration is like this (Also See Attachment):
NUMBER OF EXTENDERS ----------> 1
CONFIGURED MEMORY SIZE -------> 832 MBYTES
------------------------------------------------------------------------------
MEMORY EXTENDER - 0
PHYSICAL LOGICAL INTERLEAVE
SLOT # BANK STATUS GROUP BANK SIZE
======== ======= ======== ========== ===========
0a/0b 3 ENABLED 1 64 MBYTES
0a/0b 8 ENABLED 1 64 MBYTES
1a/1b 7 ENABLED 0 16 MBYTES
1a/1b 12 ENABLED 0 16 MBYTES
2a/2b 4 ENABLED 0 16 MBYTES
2a/2b 15 ENABLED 0 16 MBYTES
3a/3b 0 ENABLED 1 64 MBYTES
3a/3b 11 ENABLED 1 64 MBYTES
4a/4b 5 ENABLED 2 256 MBYTES
4a/4b 14 ENABLED 2 256 MBYTES
I have read the System Memory Upgrade Guide (O/N A2375-90009, E0898) and have questions:
1. Does the 969KS/200 support 512 MB module?
2. The configuration above does not agree with the guide's memory optimization procedure, should I request the modules to be repositioned?
Many Thanks
Fred Metcalf
NUMBER OF EXTENDERS ----------> 1
CONFIGURED MEMORY SIZE -------> 832 MBYTES
------------------------------------------------------------------------------
MEMORY EXTENDER - 0
PHYSICAL LOGICAL INTERLEAVE
SLOT # BANK STATUS GROUP BANK SIZE
======== ======= ======== ========== ===========
0a/0b 3 ENABLED 1 64 MBYTES
0a/0b 8 ENABLED 1 64 MBYTES
1a/1b 7 ENABLED 0 16 MBYTES
1a/1b 12 ENABLED 0 16 MBYTES
2a/2b 4 ENABLED 0 16 MBYTES
2a/2b 15 ENABLED 0 16 MBYTES
3a/3b 0 ENABLED 1 64 MBYTES
3a/3b 11 ENABLED 1 64 MBYTES
4a/4b 5 ENABLED 2 256 MBYTES
4a/4b 14 ENABLED 2 256 MBYTES
I have read the System Memory Upgrade Guide (O/N A2375-90009, E0898) and have questions:
1. Does the 969KS/200 support 512 MB module?
2. The configuration above does not agree with the guide's memory optimization procedure, should I request the modules to be repositioned?
Many Thanks
Fred Metcalf
Missing MPE :-)
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2001 05:01 AM
тАО01-30-2001 05:01 AM
Solution
1) s969-200 provides support for 512MB SIMM (A3737A) with PDC firmware revision 2.4. To find out if your system is at this revision level, go in SYSDIAG>SYSMAP>CPUMAP and look for PDC FIRMWARE REVISION. If PDC firmware revision is lower than 2.4, then have an HPCE onsite to update the PDC firmware revision.
2) The memory configuration should be like this (in other words, swap SIMMs 3a/3b (64MB) with 1a/1b (16MB):
0a/0b -> 64 MBYTES
0a/0b -> 64 MBYTES
1a/1b -> 64 MBYTES
1a/1b -> 64 MBYTES
2a/2b -> 16 MBYTES
2a/2b -> 16 MBYTES
3a/3b -> 16 MBYTES
3a/3b -> 16 MBYTES
4a/4b -> 256 MBYTES
4a/4b -> 256 MBYTES
Rules are:
A - Install any pairs of modules first (sets of 2 modules); install pairs of modules in decreasing size: start with the largest memory size and end with the smallest. Install pairs of modules with the lowest available slot number, then the next higher slot number.
B - Install any remaining modules, starting with the largest memory size first.
2) The memory configuration should be like this (in other words, swap SIMMs 3a/3b (64MB) with 1a/1b (16MB):
0a/0b -> 64 MBYTES
0a/0b -> 64 MBYTES
1a/1b -> 64 MBYTES
1a/1b -> 64 MBYTES
2a/2b -> 16 MBYTES
2a/2b -> 16 MBYTES
3a/3b -> 16 MBYTES
3a/3b -> 16 MBYTES
4a/4b -> 256 MBYTES
4a/4b -> 256 MBYTES
Rules are:
A - Install any pairs of modules first (sets of 2 modules); install pairs of modules in decreasing size: start with the largest memory size and end with the smallest. Install pairs of modules with the lowest available slot number, then the next higher slot number.
B - Install any remaining modules, starting with the largest memory size first.
King is the customer!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2004 07:38 AM
тАО03-16-2004 07:38 AM
Re: 969KS/200 Memory configuration.
You said:
2) The memory configuration should be like this (in other words, swap SIMMs 3a/3b (64MB) with 1a/1b (16MB):
0a/0b -> 64 MBYTES
0a/0b -> 64 MBYTES
1a/1b -> 64 MBYTES
1a/1b -> 64 MBYTES
2a/2b -> 16 MBYTES
2a/2b -> 16 MBYTES
3a/3b -> 16 MBYTES
3a/3b -> 16 MBYTES
4a/4b -> 256 MBYTES
4a/4b -> 256 MBYTES
I say:
The memory configuration should be like this (in other words, largest to smallest) (64MB) with 1a/1b (16MB):
0a/0b -> 256 MBYTES
0a/0b -> 256 MBYTES
1a/1b -> 64 MBYTES
1a/1b -> 64 MBYTES
2a/2b -> 64 MBYTES
2a/2b -> 64 MBYTES
3a/3b -> 16 MBYTES
3a/3b -> 16 MBYTES
4a/4b -> 16 MBYTES
4a/4b -> 16 MBYTES
2) The memory configuration should be like this (in other words, swap SIMMs 3a/3b (64MB) with 1a/1b (16MB):
0a/0b -> 64 MBYTES
0a/0b -> 64 MBYTES
1a/1b -> 64 MBYTES
1a/1b -> 64 MBYTES
2a/2b -> 16 MBYTES
2a/2b -> 16 MBYTES
3a/3b -> 16 MBYTES
3a/3b -> 16 MBYTES
4a/4b -> 256 MBYTES
4a/4b -> 256 MBYTES
I say:
The memory configuration should be like this (in other words, largest to smallest) (64MB) with 1a/1b (16MB):
0a/0b -> 256 MBYTES
0a/0b -> 256 MBYTES
1a/1b -> 64 MBYTES
1a/1b -> 64 MBYTES
2a/2b -> 64 MBYTES
2a/2b -> 64 MBYTES
3a/3b -> 16 MBYTES
3a/3b -> 16 MBYTES
4a/4b -> 16 MBYTES
4a/4b -> 16 MBYTES
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-19-2004 08:17 PM
тАО03-19-2004 08:17 PM
Re: 969KS/200 Memory configuration.
Blanche, the 2 x 256MB simms make up a SINGLE 512MB module and that is why it is installed after the other module PAIRS.
Missing MPE :-)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP