- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- patch for lbolts
HPE 9000 and HPE e3000 Servers
1820902
Members
4001
Online
109629
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
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
тАО07-11-2003 07:14 AM
тАО07-11-2003 07:14 AM
One of my co-workers was installing patches to take care of an lbolt issue that caused bogus messages related to plasmon drives. They stopped because it stated that it had failed. They were loading dependancy patch so primary was not installed. When I do a swlist -l patch '*.*, c=patch' it shows that PHKL_24187.Core-KRN Applied. Attached is what the swagent.log gave them. I did correct a space problem that was identified in the logfile but I don't know if the patch is really installed. Can I trust what it says so I can schedule reboot time because I still have another patch to install PHKL_29041 to correct my original problem.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2003 11:18 AM
тАО07-11-2003 11:18 AM
Solution
Patches must be in the configured state. Applied just means it is in place but the configure scripts have not yet been run.
You can combine patches to be installed at the same time :
Creating SD-UX depot
If you have several individual patches which you need to install
it is useful to package them all together into one patch depot.
This way you do not need to run update or swinstall multiple
times and if patches require a reboot the system will reboot
only once.
Example of creating a SD-UX depot containing 3 different patches.
1. Retrieve the patches for instance from a patch server or web site :
# mkdir /tmp/patches
# cd /tmp/patches
Copy patches via ftp, rcp ... into this directory.
# ls
PHCO_5400 PHCO_6573 PHCO_6587
2. Unpack all patches :
# sh PHCO_5400
# sh PHCO_6573
# sh PHCO_6587
3. Create a patch depot :
# mkdir /tmp/patch_depot
# swcopy -v -x enforce_dependencies=false -s /tmp/patches/PHCO_5400.depot PHCO_5400 @ /tmp/patch_depot
...
# swcopy -v -x enforce_dependencies=false -s /tmp/patches/PHCO_6587.depot PHCO_6587 @ /tmp/patch_depot
...
# swcopy -v -x enforce_dependencies=false -s /tmp/patches/PHCO_6573.depot PHCO_6573 @ /tmp/patch_depot
4. Register the depot (optional)
# swreg -l depot /tmp/patch_depot
5. Now call swinstall and specify /tmp/patch_depot as your source.
If you need to copy the depot to a tape use the following command :
# swpackage -s /tmp/patch_depot -x target_type=tape -d /dev/rmt/0m "*"
You can combine patches to be installed at the same time :
Creating SD-UX depot
If you have several individual patches which you need to install
it is useful to package them all together into one patch depot.
This way you do not need to run update or swinstall multiple
times and if patches require a reboot the system will reboot
only once.
Example of creating a SD-UX depot containing 3 different patches.
1. Retrieve the patches for instance from a patch server or web site :
# mkdir /tmp/patches
# cd /tmp/patches
Copy patches via ftp, rcp ... into this directory.
# ls
PHCO_5400 PHCO_6573 PHCO_6587
2. Unpack all patches :
# sh PHCO_5400
# sh PHCO_6573
# sh PHCO_6587
3. Create a patch depot :
# mkdir /tmp/patch_depot
# swcopy -v -x enforce_dependencies=false -s /tmp/patches/PHCO_5400.depot PHCO_5400 @ /tmp/patch_depot
...
# swcopy -v -x enforce_dependencies=false -s /tmp/patches/PHCO_6587.depot PHCO_6587 @ /tmp/patch_depot
...
# swcopy -v -x enforce_dependencies=false -s /tmp/patches/PHCO_6573.depot PHCO_6573 @ /tmp/patch_depot
4. Register the depot (optional)
# swreg -l depot /tmp/patch_depot
5. Now call swinstall and specify /tmp/patch_depot as your source.
If you need to copy the depot to a tape use the following command :
# swpackage -s /tmp/patch_depot -x target_type=tape -d /dev/rmt/0m "*"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2003 12:58 PM
тАО07-11-2003 12:58 PM
Re: patch for lbolts
In addition to Scott's - how to check if patch configured or not
swlist -l fileset -a state
Eugeny
swlist -l fileset -a state
Eugeny
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.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP