- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vparenv issue
Operating System - HP-UX
1759773
Members
3585
Online
108889
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
тАО03-06-2010 03:22 PM
тАО03-06-2010 03:22 PM
hello
i hv an issue that this machien doenst come up in vpar mode with the below error from vpmon.
HPUX> boot /stand/vpmon
> System Memory = 333 MB
loading section 0
... (complete)
loading section 1
......................................................................................................... (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
......Launching /stand/vpmon
SIZE: Text:1485K + Data:53301K + BSS:10761K = Total:65548K
Console is on virtual console - via PCDP
Current ILM granule countis 1022.
Memory object size (12032) of exceedsgranule size (128). Rebooting thesystem. Increase granule size.
The vpar was created as below:
db-prod::/# vparenv
vparenv: The next boot mode setting is "nPars".
vparenv: The ILM granule size setting is 128.
vparenv: The CLM granule size setting is 128.
vparenv: Note: Any changes in the above settings will become effective
only after the next system reboot.
db-prod::/#
db-prod::/#
db-prod::/# vparcreate -p vpar0_db -a cpu:::1:8 -a cpu::2 -a mem::8192 -a io:5.0.8 -a io:5.0.6 -a io:5.0.10 -a io:5.0.8.1.0.4.0.0.0:BOOT -a io:5.0.8.1.0.4.0.2.0:ALTBOOT
db-prod::/# vparenv -m vPars
vparenv: Note: To match the configured memory on the system, the ILM granularity has been increased to 256.
db-prod::/#
db-prod::/# vparenv
vparenv: The next boot mode setting is "vPars".
vparenv: The ILM granule size setting is 128.
vparenv: The CLM granule size setting is 128.
vparenv: Note: Any changes in the above settings will become effective
only after the next system reboot.
vparenv: Note: The maximum possible CLM granules per cell is 64.
vparenv: Note: The maximum possible ILM granules for this system is 1024.
db-prod::/# shutdown -ry 0
has anyone come across such issue ?
i hv an issue that this machien doenst come up in vpar mode with the below error from vpmon.
HPUX> boot /stand/vpmon
> System Memory = 333 MB
loading section 0
... (complete)
loading section 1
......................................................................................................... (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
......Launching /stand/vpmon
SIZE: Text:1485K + Data:53301K + BSS:10761K = Total:65548K
Console is on virtual console - via PCDP
Current ILM granule countis 1022.
Memory object size (12032) of exceedsgranule size (128). Rebooting thesystem. Increase granule size.
The vpar was created as below:
db-prod::/# vparenv
vparenv: The next boot mode setting is "nPars".
vparenv: The ILM granule size setting is 128.
vparenv: The CLM granule size setting is 128.
vparenv: Note: Any changes in the above settings will become effective
only after the next system reboot.
db-prod::/#
db-prod::/#
db-prod::/# vparcreate -p vpar0_db -a cpu:::1:8 -a cpu::2 -a mem::8192 -a io:5.0.8 -a io:5.0.6 -a io:5.0.10 -a io:5.0.8.1.0.4.0.0.0:BOOT -a io:5.0.8.1.0.4.0.2.0:ALTBOOT
db-prod::/# vparenv -m vPars
vparenv: Note: To match the configured memory on the system, the ILM granularity has been increased to 256.
db-prod::/#
db-prod::/# vparenv
vparenv: The next boot mode setting is "vPars".
vparenv: The ILM granule size setting is 128.
vparenv: The CLM granule size setting is 128.
vparenv: Note: Any changes in the above settings will become effective
only after the next system reboot.
vparenv: Note: The maximum possible CLM granules per cell is 64.
vparenv: Note: The maximum possible ILM granules for this system is 1024.
db-prod::/# shutdown -ry 0
has anyone come across such issue ?
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2010 12:05 AM
тАО03-07-2010 12:05 AM
Solution
You should set ILM size bigger.
"The goal to avoid slow boot times is to have the number of granules to be close to 50. Any quantity up to 100 will show reasonable boot times, but HP recommends a value close to 50."
Check out the link:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02029116/c02029116.pdf (BSC link updated by admin)
Boot your system in npar mode and set approprite ILM size
vparenv -g ILM:1024:y
"The goal to avoid slow boot times is to have the number of granules to be close to 50. Any quantity up to 100 will show reasonable boot times, but HP recommends a value close to 50."
Check out the link:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02029116/c02029116.pdf (BSC link updated by admin)
Boot your system in npar mode and set approprite ILM size
vparenv -g ILM:1024:y
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2010 12:58 AM
тАО03-07-2010 12:58 AM
Re: vparenv issue
The resolution is to re-create all VPARs as follows:
Boot to NPAR mode
Create the first VPAR with -g clm:1024:y -g ilm:1024:y option.
Create all other VPARS.
Boot to NPAR mode
Create the first VPAR with -g clm:1024:y -g ilm:1024:y option.
Create all other VPARS.
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