- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Kernel parameters
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
03-05-2002 01:45 PM
03-05-2002 01:45 PM
Do u guys have any idea about this problem?
Thanks,
Arockia.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2002 01:55 PM
03-05-2002 01:55 PM
Re: Kernel parameters
Really dumb question for you. Did you happen to run the 'kmupate' program after generating your kernel with the new parameters? If you didn't and rebooted you would have all of the old parameters. This would also occur if you loaded a patch bundle. You can only generate and use one kernel at a time. I have this bundle loaded on six boxes none having this problem.
-Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2002 02:07 PM
03-05-2002 02:07 PM
Re: Kernel parameters
mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2002 02:17 PM
03-05-2002 02:17 PM
Re: Kernel parameters
I have done through sam. I have changed 10 parameters (static & dynamic - including
shmmax & shmseg) and rebuild the kernel and rebooted the system. It was having the modified kernel parameter values. System got rebooted 4 to 5 times. I didn't have any problem. After installing the patches (GOLDPQK11i) system got rebooted and then only shmmax and shmseg got changed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2002 12:50 AM
03-06-2002 12:50 AM
Re: Kernel parameters
How are viewing these kernel parameters? Is it through SAM or are you using kmtune command.
Both of them might show misleading information because your /stand/system might not be updated and so these tools get the information from /stand/system.
One way to determing if really the parameters are changed or not is to get their current values from the running kernel. Use the command below :
echo shmmax/D | adb -k /stand/vmunix /dev/mem
If you see the values you updated with, then its okay.
Hope this helps!
Bye,
Raghu.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2002 02:31 AM
03-06-2002 02:31 AM
Re: Kernel parameters
Steps for building the new Kernel (tuning) manually :
1. Change directories to /stand/build.
cd /stand/build
2. Create a new system file from the running kernel.
/usr/lbin/sysadm/system_prep -s system
3. Edit the kernel with the planned changes.
kmtune -S /stand/build/system -s parm_name=value
4. Build the new kernel.
/usr/sbin/mk_kernel -s ./system
5. Move the old system and vmunix files so if anything goes wrong, the system
can be booted from the old kernel.
mv /stand/system /stand/system.prev
mv /stand/vmunix /stand/vmunix.prev
mv /stand/dlkm /stand/dlkm.vmunix.prev
6. Move the new system file and new kernel into place, ready to be used when
rebooting the system.
mv /stand/build/system /stand/system
kmupdate /stand/build/vmunix_test
7. Reboot the system off the new kernel.
shutdown -r
Hope this helps.
Vasu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2002 08:03 AM
03-06-2002 08:03 AM
Re: Kernel parameters
On the plus side, this should only affect dynamic tunables - so you can reset your values back quickly.
On the minus side -- you really shouldn't be expected to do that.
I'll check into this and see what I can find out.
Don
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2002 08:33 AM
03-06-2002 08:33 AM
Re: Kernel parameters
Dynamic tunable changes _are_ propagated to the system file just as static tunable changes are, so the rebuild of the kernel after the patch process should have kept your values.
Did you perchance restore your system file from a backup before patching?
Don
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2002 08:37 AM
07-03-2002 08:37 AM
Solution-----Original Message-----
From: HARPER,CHERYL (HP-USA,ex1) [mailto:cheryl_harper@hp.com]
Sent: Friday, June 21, 2002 9:22 AM
Subject: Proactive Notification: HPUX 11i Dynamic Kernel Parameters - Don 't survive patching activities!
Are you running HP-UX 11i? If so, read on...
HPUX 11i allows certain kernel parameters to be changed on the fly without rebooting.
When installing kernel intrusive patches with SD-UX, where a kernel rebuild is required, any previously set Dynamic Kernel Parameters (in almost all cases) will be set back to their original default values.
The issue is based on the get_sysfile command that is used to extract the current kernel settings is apparently unaware of the dynamic parameter settings. This issue has been reported to the lab and will be fixed in the near future.
Workaround
Prior to patching, issue a command to save the currently tuned parameters in a file for future use:
#kmtune | grep Y | egrep -v "-" | awk '{print $1, $2}' > /tmp/dyn_parms
After the patch installation, in order to stage the changes needed, issue the command :
#kmtune -u -S /tmp/dyn_parms
HPUX will read the file, and attempt to change to all kernel parameters. Those that it can't update (fixed parameters) it will issue WARNINGS on, and those dynamic parameters it can set, it will set to change pending. To verify the pending state, you could issue the following command:
#kmtune | grep Y | egrep -v "-"
To make the activate the changes, enter the command:
#kmtune -u
Since the parameters that you are setting are dynamic, no reboot will be required.
Hope this helps!