Client Management: A quick overview on how packages and patches are sent to the target devices

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Client Management


    COMPONENT:

    Client Management


    APPLIES TO:

    Any version of BCM



    QUESTION:

    How do my devices download the packages and/or patches they are assigned to?

    Do my devices download their packages and/or patches from the master each time they are (re) assigned to a package?


    ANSWER:

    The following A- and B- applies to packages and patches as well.

    Basically, a device receives an assignment, acknowledge it then it will ask to its relay if it has the package (and steps) it needs to download before to execute the package (and/or operational rule).

    These steps/packages transfer from one device to another are managed by the module "Filestore".

    Relay1= Relay is direct child of the master
    Relay2= Relay is child of a Relay1 relay

     

      1- If the package has been published on the master:  
     
    These are the most common scenarios. 
      
     
    A- There is one relay only:  
    The first time any child of Relay1 will request the package to Relay1 then Relay1 will check if it has the package or not. If it doesn't, it'll request it to the master.  
    Once Relay1 will have downloaded the package from the master, the device will be able to get the package from the Relay1, it will not download it from the master.  
     
    Then when another child of  Relay1 will request the same package to Relay1, then as Relay1 still has the package in its filestore, the device will download it from Relay1, not from the master.  
     
    B- There are a level 1 relay and a level 2 relay:  
    The same mechanism applies: the device will request it to Relay2, if it does not have that package yet then it'll request it to its parent relay: Relay1.  
    If Relay1 has the package, then the child relay will download it from Relay1. Once the package will have been downloaded to the Relay2 the target will download it from Relay2.  
    Now, if Relay1 doesn't have it either, then it'll request it to the master. Once downloaded it'll be downloaded by Relay2 then by the client.  
     
    When another child of Relay2 will request the same package to the Relay2, as Relay2 will still have the package in its filestore, the device will download it from Relay2 and not from any other parent. 
      

    2- The package has been published to a relay: 

    Customers running a master on saas will usually publish packages this way. Customers who have many far locations or who want to easily manage the time when the data will reach the relays could also work this way. 

    If the target which is assigned to a package is a child of this relay, then it'll be able to download it from this relay and the master will not be involved at all. 
    If the target parent is a child of the relay where you have published the package then it'll request to it, then if this Relay2 doesn't have it, it'll request it from Relay1. Again, the master will not be involved. 


    3- Your operational rule downloads files from a share: 

    Every time a device will execute an operational rule/a package that is set to download/or execute datas from a share then the device will download it from this share as it "bypasses" the filestore mechanisms. This can be bandwidth costly, depending on your network architecture compared to the filestore mechanism and should therefore probably not be used this way.. 


    Note: depending on the filestore configuration of the devices, packages could be deleted from the relays after a while. 

      

     


    Article Number:

    000148106


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles