- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: memory increase in vPar
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
10-27-2011 07:33 AM
10-27-2011 07:33 AM
memory increase in vPar
Increased memory in a vPar by 8GB
dmesg grep physical shows old memory.
whereas swapinfo output shows new increased memory.
Can you please help me understand why is it so?
Now whats the actual RAM in this vPar?
Do we need any reboots?
or is it already increased but dmesg isnt updated?
# swlist | grep -i "integrity vm"
VMGuestLib A.03.50.0803 Integrity VM Guest Support Libraries
# uname -a
HP-UX B.11.31 U ia64 0051955873 unlimited-user license
vparstatus -A showed
[Available ILM (MB)]: 58451
vparmodify - increased the vpar memory by 8GB
Then vparstatus -A shows :
[Available ILM (MB)]: 51451
earlier :
# dmesg |grep -i physical
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 12532720 Kbytes, lockable: 8992132 Kbytes, available: 10267700 Kbytes
# swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 7120 5334 1786 75% 0 - 1 /dev/vg00/lvol2
dev 5008 0 5008 0% 0 - 2 /dev/vg00/lv-sswap
reserve - 6653 -6653
memory 11654 8526 3128 73%
total 23782 20513 3269 86% - 0 -
After increasing the memory by 8GB:
dmesg | grep -i physical doesnt change..but everything else(regarding memory) changes.
# dmesg |grep -i physical
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 12532720 Kbytes, lockable: 8992132 Kbytes, available: 10267700 Kbytes
# swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 7120 5328 1792 75% 0 - 1 /dev/vg00/lvol2
dev 5008 0 5008 0% 0 - 2 /dev/vg00/lv-sswap
reserve - 6742 -6742
memory 16646 8752 7894 53%
total 28774 20822 7952 72% - 0 -
#
# /opt/ignite/bin/print_manifest |grep -i memory
Main Memory: 17486 MB
#
# machinfo|grep -i memory
Memory: 17486 MB (17.08 GB)
:#
cstm>info
-- Updating Map --
Updating Map...
cstm>il
-- Converting a (8072) byte raw log file to text. --
Preparing the Information Tool Log for IPF_MEMORY on path memory File ...
.... le00odb2 : 172.17.19.197 ....
-- Information Tool Log for IPF_MEMORY on path memory --
Log creation time: Thu Oct 27 15:10:11 2011
Hardware path: memory
Basic Memory Description [1]
Module Type: MEMORY
Page Size: 4096 Bytes
Total Physical Memory: 131072 MB
Total Configured Memory: 131072 MB
Total Deconfigured Memory: 0 MB
Memory Board Inventory [1]
DIMM Location Size(MB) State Serial Num Part Num
-------------------- -------- ------- ---------------- ------------------
Cab 0 Cell 0 DIMM 0A 8192 Config PRY08271K3 AB456-60101
Cab 0 Cell 0 DIMM 0B 8192 Config PRY08271KE AB456-60101
Cab 0 Cell 0 DIMM 1A 8192 Config PRY08271KF AB456-60101
Cab 0 Cell 0 DIMM 1B 8192 Config PRY08271KH AB456-60101
Cab 0 Cell 0 DIMM 2A 8192 Config PRY08271N6 AB456-60101
Cab 0 Cell 0 DIMM 2B 8192 Config PRY08271K4 AB456-60101
Cab 0 Cell 0 DIMM 3A 8192 Config PRY08271N1 AB456-60101
Cab 0 Cell 0 DIMM 3B 8192 Config PRY08271P9 AB456-60101
Cab 0 Cell 0 DIMM 4A ---- ---- ---- ----
Cab 0 Cell 0 DIMM 4B ---- ---- ---- ----
Cab 0 Cell 0 DIMM 5A ---- ---- ---- ----
Cab 0 Cell 0 DIMM 5B ---- ---- ---- ----
Cab 0 Cell 0 DIMM 6A ---- ---- ---- ----
Cab 0 Cell 0 DIMM 6B ---- ---- ---- ----
Cab 0 Cell 0 DIMM 7A ---- ---- ---- ----
Cab 0 Cell 0 DIMM 7B ---- ---- ---- ----
Cab 0 Cell 0 Total: 65536 (MB)
===========================================================================
DIMM Location Size(MB) State Serial Num Part Num
-------------------- -------- ------- ---------------- ------------------
Cab 0 Cell 1 DIMM 0A 8192 Config PRY08271K2 AB456-60101
Cab 0 Cell 1 DIMM 0B 8192 Config PRY08271JM AB456-60101
Cab 0 Cell 1 DIMM 1A 8192 Config PRY08260XX AB456-60101
Cab 0 Cell 1 DIMM 1B 8192 Config PRY08260XP AB456-60101
Cab 0 Cell 1 DIMM 2A 8192 Config PRY08260YX AB456-60101
Cab 0 Cell 1 DIMM 2B 8192 Config PRY08260XC AB456-60101
Cab 0 Cell 1 DIMM 3A 8192 Config PRY08260XF AB456-60101
Cab 0 Cell 1 DIMM 3B 8192 Config PRY08260XE AB456-60101
Cab 0 Cell 1 DIMM 4A ---- ---- ---- ----
Cab 0 Cell 1 DIMM 4B ---- ---- ---- ----
Cab 0 Cell 1 DIMM 5A ---- ---- ---- ----
Cab 0 Cell 1 DIMM 5B ---- ---- ---- ----
Cab 0 Cell 1 DIMM 6A ---- ---- ---- ----
Cab 0 Cell 1 DIMM 6B ---- ---- ---- ----
Cab 0 Cell 1 DIMM 7A ---- ---- ---- ----
Cab 0 Cell 1 DIMM 7B ---- ---- ---- ----
Cab 0 Cell 1 Total: 65536 (MB)
===========================================================================
Memory Error Log Summary [2]
The memory error log is empty.
Page Deallocation Table (PDT) [2]
The Page Deallocation Table is empty.
PDT Entries Used: 0
PDT Entries Free: 1600
PDT Total Size: 1600
------------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2011 12:01 PM
10-31-2011 12:01 PM
Re: memory increase in vPar
Dmesg gives you content of kernel message buffer, i.e. the information in there doesn't change. The memory line is printed at boot time so unless you reboot the message was already printed and won't reflect new size.
Note that 'integrity vm' has nothing to do with vPars, these are different virtualization technologies.