Manually upgrading client agents via device groups on Linux systems

Agents can be upgraded via device groups instead of individually. To use this type of upgrade one or more Linux device groups need to be created. While it is possible to create these groups during the upgrade procedure it, BMC recommends that you prepare them beforehand.

To upgrade client agents via a device group, you need to execute the following two procedures:

1. Creating the Linux target groups:
    For Linux systems, two different upgrade packages are available, one for 32-bit Linux and another for 64-bit Linux . Depending on the population of your network, you might therefore only need to create one of the following groups or both. These groups must contain all clients and relays that are running on the respective Linux operating system. To populate these groups, two queries need to be created: One that finds all devices with the respective operating system version and a second one that finds either the clients or the relays. Both can be based on existing queries.
2. Upgrading the BCM agents on Linux devices via device groups

Creating the 32-bit Linux group

1. Go to the Queries node.
2. Select the folder Operating Systems .

3. Select the folder UNIX .

   Note:

   If you already have a query that collects all 32-bit Linux devices you can skip the following procedure and continue directly with step 14.

4. Select the query Linux Devices , duplicate it and give it a new name, for example, 32 Bit Linux Devices .
5. Select the new query and go to its Criteria tab.
6. Select AND as the Query Operator above the criteria table.
7. Select Edit > Add Criterion .
    The Select Criterion pop-up menu displays.
8. Select the criterion Operating System Name .
9. Change the Operator to Contains .
10. Enter 32 in the Value box.
11. Click Add to add the criterion to the list.
12. Click OK to confirm the new query content and to close the window.
13. Activate the query by selecting the green colored option active instead of the currently displayed red option inactive in the Query Status list box above the table.
14. Now select the new query in the hierarchy to the left, right-click and select the Create Device Group menu option.
     The new group is automatically created directly under the Device Groups top node with the same name as that of the query, that is, 32 Bit Linux Devices .

15. Find the query Client Devices , duplicate it and give it a new name, for example, All Clients and Relays .

    This query is located either in the folder Client Management - database or Numara Asset Management Platform Architecture , depending on which version you have currently installed.

    Note:

    If you already have a query that collects all client devices and all relays you can skip the following procedure and continue directly with step 26.

16. Select the new query and go to its Criteria tab.
17. Select OR as the Query Operator above the criteria table.
18. Select Edit > Add Criterion .
     The Select Criterion pop-up menu displays.
19. Select the criterion Topology Type .
20. Click Find .
     The Search Criteria pop-up window appears.
21. Select the Relay topology type and click OK .
22. Modify the Operator to Equal to .
23. Click Add to add the criterion to the list.
24. Click OK to confirm the new query content and to close the window.
25. Activate the query by selecting the green colored option active instead of the currently displayed red option inactive in the Query Status list box above the table.
26. Go to the Device Groups top node and select the group 32 Bit Linux Devices .
27. Select its Dynamic Population > Queries subnode.
28. Click Assign Query .
29. Find the newly created query All Clients and Relays , select it and click OK .
     A Properties window appears.
30. Select the Only Devices with an Agent option as the Device Type and click OK .
     The second query is directly assigned to the group.

The new group is now created using both queries to find its population and is ready to be used for upgrading all 32-bit Linux agents.

Creating the 64-bit Linux group

1. Go to the Queries node.
2. Select the folder Operating Systems .

3. Select the folder UNIX .

   Note:

   If you already have a query that collects all 64-bit Linux devices you can skip the following procedure and continue directly with step 14.

4. Select the query Linux Devices , duplicate it and give it a new name, for example, 64 Bit Linux Devices .
5. Select the new query and go to its Criteria tab.
6. Select AND as the Query Operator above the criteria table.
7. Click Edit > Add Criterion .
    The Select Criterion pop-up menu displays.
8. Select the criterion Operating System Name .
9. Change the Operator to Contains .
10. Enter 64 in the Value box.
11. Click Add to add the criterion to the list.
12. Click OK to confirm the new query content and to close the window.
13. Activate the query by selecting the green colored option active instead of the currently displayed red option inactive in the Query Status list box above the table.
14. Now select the new query in the hierarchy to the left, right-click and click the Create Device Group menu option.
     The new group is automatically created directly under the Device Groups top node with the same name as that of the query, that is, 64 Bit Linux Devices .

15. Find the query Client Devices , duplicate it and give it a new name, for example, All Clients and Relays .

    This query is located either in the folder Client Management - database or Numara Asset Management Platform Architecture , depending on which version you have currently installed.

    Note:

    If you already have a query that collects all client devices and all relays you can skip the following procedure and continue directly with step 26.

16. Select the new query and go to its Criteria tab.
17. Select OR as the Query Operator above the criteria table.
18. Select Edit > Add Criterion .
     The Select Criterion pop-up menu displays.
19. Select the criterion Topology Type .
20. Click Find .
     The Search Criteria pop-up window appears.
21. Select the Relay topology type and click OK .
22. Modify the Operator to Equal to .
23. Click Add to add the criterion to the list.
24. Click OK to confirm the new query content and to close the window.
25. Activate the query by selecting the green colored option active instead of the currently displayed red option inactive in the Query Status list box above the table.
26. Go to the Device Groups top node and select the group 64 Bit Linux Devices .
27. Select its Dynamic Population > Queries subnode.
28. Click Assign Query .
29. Find the newly created query All Clients and Relays , select it and click OK .
     A Properties window appears.
30. Select the Only Devices with an Agent option as the Device Type and click OK .
     The second query is directly assigned to the group.

The new group is now created using both queries to find its population and is ready to be used for upgrading all 64-bit Linux agents.

Upgrading the CM agents on Linux devices via device groups

Now that all necessary groups have been created, the upgrade packages can be created, assigned and distributed to these target groups. Proceed as follows:

1. In the console select the Tools> Create Upgrade Packages menu item.
    One custom package ( .cst ) per .zip file is created in the same location together with its respective operational rule and is placed in a specifically created folder called Client Management Upgrade or BMC Client Management Oneoff under the Packages / Operational Rules top nodes.

   Note:

   If you performed previous upgrades, for example, 6.1.2 to 6.1.3, the operational rules/packages are placed under the previously created folder called, for example, PrecisionUpgrade , NumaraAssetManagementPlatformUpgrade or FootprintsAssetCoreUpgrade . No new folder is created.

2. Go to the Operational Rules> Client Management Upgrade node and select the operational rule to upgrade the agents, for example,
   • Linux32Upgrade / Linux32Oneoff for agents on 32-bit Linux devices
   • Linux64Upgrade / Linux64Oneoff for all agents installed on 64-bit Linux systems.
3. Go to the Assigned Objects> Device Groups subnode.
4. Select Edit> Assign Device Group .
    A pop-up window appears in which you can define if the operational rule is automatically activated with the default schedule.

5. Click Yes .

   If you select No here, the operational rule must be specifically activated afterwards.The Assign to Device Group pop-up window appears.

6. Click the All button in the left window bar.
    The list in the right part of the window now displays all available device groups.
7. Select the device group created in the preceding step, which contains all devices of the operating system to be upgraded, for example
   • 32 Bit Linux Devices all Linux 32-bit devices
   • 64 Bit Linux Devices all Linux 64-bit devices
8. Click OK to confirm the assignment and close the window.
   The device group is assigned with the default timer, which schedules the execution once and immediately.
9. Go to the Assigned Objects> Devices subnode.

After the assignment process is finished and the upgrade package has arrived at the targets, the agents are automatically upgraded.

This is the case when the status is green and Executed displays in the Status box for the respective device.

The attributes Agent Version Major and Agent Version Minor should display the values 12 and 0 now. If you are applying a hotfix, the Agent Revision number should have increased by one.