HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RH Patching best practice and Management Method
Operating System - Linux
1830938
Members
1693
Online
110017
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
05-24-2006 06:22 PM
05-24-2006 06:22 PM
RH Patching best practice and Management Method
Hi all,
I have about 10 servers running RH AS 4.x. Here are my questions;
1) What is the best way/method to setup a patching scheme?
2) Dose it cost me to Setup RHN Satellite? how much?
3) What is proxy? and difference between proxy and Satellite setup?
4) What is the added value or advantages to purchase RHN entitlement through HP?
5) What is the best practice in my case?
Please send me any doc in-regards to above questions.
I thank you for any help.
Dary.
I have about 10 servers running RH AS 4.x. Here are my questions;
1) What is the best way/method to setup a patching scheme?
2) Dose it cost me to Setup RHN Satellite? how much?
3) What is proxy? and difference between proxy and Satellite setup?
4) What is the added value or advantages to purchase RHN entitlement through HP?
5) What is the best practice in my case?
Please send me any doc in-regards to above questions.
I thank you for any help.
Dary.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2006 08:18 PM
05-24-2006 08:18 PM
Re: RH Patching best practice and Management Method
Shalom Dary,
Due to security issues, patching must be done frequently, especially if there is any exposure to the Public Internet, even browsing.
I would suggest a few alternatives.
1) With 1 RHN license, you can set up a yum respository inside your network. Download the patches to the server using up2date, have settings to save all the rpms, which will be copied to the yum server.
2) Patchlink, permits you to fine tune what patches to use andn ot use.
3) Answer to question 4. HP support which substantially outshines RH support.
SEP
Due to security issues, patching must be done frequently, especially if there is any exposure to the Public Internet, even browsing.
I would suggest a few alternatives.
1) With 1 RHN license, you can set up a yum respository inside your network. Download the patches to the server using up2date, have settings to save all the rpms, which will be copied to the yum server.
2) Patchlink, permits you to fine tune what patches to use andn ot use.
3) Answer to question 4. HP support which substantially outshines RH support.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2006 08:12 AM
05-25-2006 08:12 AM
Re: RH Patching best practice and Management Method
1) What is the best way/method to setup a patching scheme?
IMHO, in your situation up2date working against RHN will do it work.
BTW, AFAIK SEP solution (10 computers using 1 RHN subscription) isn't legal.
2) Dose it cost me to Setup RHN Satellite? how much?
It's very expensive
3) What is proxy? and difference between proxy and Satellite setup?
see http://www.redhat.com/rhn/ for details.
IMHO, you don't need RHN proxy
IMHO, in your situation up2date working against RHN will do it work.
BTW, AFAIK SEP solution (10 computers using 1 RHN subscription) isn't legal.
2) Dose it cost me to Setup RHN Satellite? how much?
It's very expensive
3) What is proxy? and difference between proxy and Satellite setup?
see http://www.redhat.com/rhn/ for details.
IMHO, you don't need RHN proxy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2006 03:00 AM
05-26-2006 03:00 AM
Re: RH Patching best practice and Management Method
Any best practice patching scheme should start with (1) documention of the setup prior to patching, (2) a full backup prior to patching, (3) manual patching, (4) testing of the patch in a simulated production environment prior to general release, and (5) a rollback change control plan.
Yes, this involves a lot more work than simply automating the whole thing, but it can save you a lot of headaches in the long run.
Yes, this involves a lot more work than simply automating the whole thing, but it can save you a lot of headaches in the long run.
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP