1 2 Previous Next 22 Replies Latest reply on Aug 22, 2012 7:49 AM by Justin Dettmann

    Blade Patching

    Justin Dettmann



      I am planning to do a POC for patching a variety of OS's. The systems I will be testing will be:




      Red Hat Linux




      The confusing part here is, do I need a helper server for each of the different OS's?



        • 1. Blade Patching

          I think you just need the helper service only for Windows patching. A Windows Helper Server is any Windows server with an RSCD Agent installed on it. It can be the BladeLogic Application Server if that server is a Windows system. The Helper Server participates in decrypting files and extracting metadata for Windows patching.

          1 of 1 people found this helpful
          • 2. Blade Patching

            I read that you do need a helper server for redhat to generate the yum metadata.  What version of BBSA are you going to use here?  You will also need a HP SWA server. see https://communities.bmc.com/communities/message/181364#181364

            • 3. Blade Patching
              Justin Dettmann

              I will be using version 8.2


              Thats why Im confused. Some places you read you dont need a helper and some places refer to using one?

              • 4. Blade Patching
                Justin Dettmann

                Doesnt look like I have rights to access that link

                • 5. Re: Blade Patching
                  Bill Robinson

                  You need a helper server for each OS except solaris.  If your appservers are windows or redhat you can use them as the helper for that OS.

                  • 6. Blade Patching
                    Justin Dettmann

                    Great thanks Bill, and idea what space requirements will be needed for these helpers?

                    • 7. Re: Blade Patching
                      Gerardo Bartoccini

                      For HP-UX and Linux you actually build the repository on those servers, which means you need some storage for this.

                      Obviously, it depends on how many different OS versions you want to test.

                      Generally speaking for Linux I consider 10GB for each OS version.

                      On Solaris as Bill said you don’t need a helper.

                      On Windows the helper is used to read patches metadata. I can’t remember whether or not you build the repository on the helper server.

                      I can’t help about AIX

                      • 8. Blade Patching
                        Bill Robinson

                        It depends how many patches you are going to dl.  I don’t have any aix patch repos but here’s everything else:


                        My solaris and windows repos have all patches that I can download.  So for all of that it’s about 500g.


                        111G    ./solaris

                        75G     ./windows

                        8.0G    ./rhel-x86_64-server-6

                        7.5G    ./rhel-x86_64-es-4

                        2.5G    ./rhel-x86_64-as-3

                        2.3G    ./rhel-i386-as-3

                        11G     ./rhel-i386-server-5

                        6.5G    ./rhel-i386-server-6

                        7.9G    ./rhel-i386-as-4

                        6.9G    ./rhel-i386-es-4

                        2.4G    ./rhel-x86_64-es-3

                        13G     ./rhel-x86_64-as-4

                        2.3G    ./rhel-i386-es-3

                        13G     ./rhel-x86_64-server-5

                        1.6G    ./sles-10-x86_64-SP4-Online

                        6.2G    ./sles-11-x86_64-SP1-Updates

                        2.5G    ./sles-10-s390x-SP3-Pool

                        103M    ./sles-11-s390x-Extras

                        1.7G    ./sles-10-s390x-SP3-Online

                        2.9G    ./sles-10-x86_64-SP4-Pool

                        11G     ./sles-10-s390x-SP1-Updates

                        2.7G    ./sles-10-x86_64-SP3-Pool

                        4.9G    ./sles-11-s390x-SP1-Updates

                        4.7G    ./sles-10-x86_64-SP4-Updates

                        2.8G    ./sles-10-s390x-SP1-Online

                        4.1G    ./sles-10-s390x-SP4-Updates

                        7.0G    ./sles-10-x86_64-SP3-Updates

                        2.6G    ./sles-11-x86_64-SP1-Pool

                        2.6G    ./sles-11-s390x-SP1-Pool

                        3.8G    ./sles-11-x86_64-Updates

                        1022M   ./sles-11-x86_64-SP2-Updates

                        8.5G    ./ONLINE-sles-11-x86_64-SP1-Updates

                        2.7G    ./sles-10-s390x-SP4-Pool

                        2.1G    ./sles-10-x86_64-SP3-Online

                        5.3G    ./sles-10-s390x-SP3-Updates

                        3.3G    ./sles-11-s390x-Updates

                        1.5G    ./sles-10-s390x-Updates

                        4.8G    ./sles-10-s390x-SP2-Updates

                        738M    ./sles-11-s390x-SP2-Updates

                        1.1G    ./sles-11-x86_64-SP2-Core

                        1.1G    ./sles-11-s390x-SP2-Core

                        2.5G    ./sles-11-s390x-Pool

                        1.3G    ./sles-10-s390x-SP4-Online

                        3.0G    ./sles-10-s390x-SP2-Online

                        99G     ./suse



                        the windows patches can be stored anywhere.  linux must be kept on a rhel or sles box.

                        1 of 1 people found this helpful
                        • 9. Blade Patching
                          Justin Dettmann

                          Thanks for everyones input. Greatly appreaciated

                          • 10. Re: Blade Patching
                            Justin Dettmann

                            Hi Bill,


                            Sorry Im bombarding you with questions .....


                            I need to confirm, in the environment Im setting up for patching, which comprises of Linux (AppServer), AIX, Windows, HP-UX and Solaris.


                            Lets say there are one of each with an rscd agent and they need patches downloaded. Do they all need access to the internet (At least one of each type of OS), or does only one of the servers in the environment need access to the internet? Eg, the linux application server?




                            • 11. Re: Blade Patching
                              Bill Robinson

                              if you are running the online catalog, the download initiates from the appserver.  for offline catalogs, the download would initate from whereever you run the downloader from.  HPUX will pull from the HPUX box iirc.

                              • 12. Re: Blade Patching
                                Justin Dettmann

                                Thanks Bill. I am planning to just have the appserver (linux) have connection to the internet. This will connect and download the necessary patches to the helper servers for the other OS's.


                                Will it work ok like that?

                                • 13. Re: Blade Patching
                                  Bill Robinson

                                  What version of bladelogic is this?

                                  what OSes do you need to patch – sles, rhel, windows, aix, hpux, solaris?

                                  which one of those are you going to create online catalogs for?

                                  the hpux box will need outbound access.

                                  Aix still uses an offline downloader, so you can run that from the appserver?

                                  • 14. Re: Blade Patching
                                    Justin Dettmann

                                    Version 8.2.01

                                    Initially patching Suse Linux Ent, Oracle Linux and Windows 2008/2003, but will move to doing HP-UX, Solaris and AIX

                                    1 2 Previous Next