Upgrading

When upgrading to a new version of PATROL for Linux and PATROL for Red Hat Enterprise Virtualization in any of the following environments, there are no additional steps to upgrade. 

• PATROL 
• ProactiveNet Performance Management 
• TrueSight (while using the TrueSight console)

You can deploy the Knowledge Module available for PATROL for Linux as discussed in the Installing section.

Migration process overview for PATROL for Linux and PATROL for Red Hat Enterprise Virtualization

This section contains the common queries you might encounter when migrating to the latest versions of PATROL for Linux and PATROL for Red Hat Enterprise Virtualization.

• • • Migration process overview for PATROL for Linux and PATROL for Red Hat Enterprise Virtualization
      • • Do you need specific steps or permissions for upgrading from PATROL for Linux 1.1 and Red Hat Enterprise Virtualization 1.0 to Linux 1.2.00?
        • Do you need to update Infrastructure Policies to use the new features?
        • Are there any conflicts created if you push this KM before updating the Infrastructure Policies?
        • What is the best way to implement the KM updates in the TrueSight console?
        • For any updated KMs in the repositories have there been any new attributes added or removed?
        • For any updated KMs in the repositories have there been any Monitor Type, Monitor Name or Attribute name changes that would affect any given Global and Instance threshold or any Advanced Event Rules?
        • For any updated KMs check for the following potential incompatibilities:
        • An earlier version Infrastructure Policy pointing to the PATROL Agent with the NEW version of the KM
        • A NEW version Infrastructure Policy pointing to the PATROL Agent with an OLD version of the KM
        • How many versions back of either above scenario creates an incompatibility?
        • Upgrading PATROL for Red Hat Enterprise Virtualization
        • For any updated KMs check for the following potential incompatibilities:
        • An earlier version Infrastructure Policy pointing to the PATROL Agent with the NEW version of the RHEV KM
        • A NEW version Infrastructure Policy pointing to the PATROL Agent with an OLD version of the RHEV KM

Do you need specific steps or permissions for upgrading from PATROL for Linux 1.1 and Red Hat Enterprise Virtualization 1.0 to Linux 1.2.00?

No. Upgrading from PATROL for Linux 1.1.00 and Red Hat Enterprise Virtualization 1.0.00 to Linux 1.2.00 does not require any additional permissions or steps.

Do you need to update Infrastructure Policies to use the new features?

Yes, you need to create new Infrastructure Policies to use the latest features provided by the KM.

Are there any conflicts created if you push this KM before updating the Infrastructure Policies?

PATROL for Linux 1.2.00 supports backward compatibility. The KM will continue to monitor your environment with the old configuration. Note that, to use the latest features provided by the KM, you must create new policies.

What is the best way to implement the KM updates in the TrueSight console?

You can implement the KM updates in the following sequence. 

1. Identify PATROL Agents that might benefit from the KM update
2. Push the KM to the applicable PATROL Agents
3. Update Infrastructure Policies
4. Update Global Policies
5. Update repository packages

For better KM management, it is recommended that all the PATROL Agents must have the same version of the KM. This approach is useful in managing the policies.

For any updated KMs in the repositories have there been any new attributes added or removed?

The Partition-Metrics-NUK_PARTITION_METRICS monitor type has been introduced to support local monitoring of Linux operating system running on PPC64le. 

For any updated KMs in the repositories have there been any Monitor Type, Monitor Name or Attribute name changes that would affect any given Global and Instance threshold or any Advanced Event Rules?

No there are no changes in the monitor type and attribute names that impact the global or instance threshold.

For any updated KMs check for the following potential incompatibilities:

• An earlier version Infrastructure Policy pointing to the PATROL Agent with the NEW version of the KM

  Monitoring continues with the old policy configuration. Features introduced in the latest version of the KM will not be included. 
  
  

• A NEW version Infrastructure Policy pointing to the PATROL Agent with an OLD version of the KM

  This combination is not recommended. A policy created by using the latest version of Infrastructure Management is not compatible with an older version of the KM 

How many versions back of either above scenario creates an incompatibility?

A policy created with 1.2.00 version of the KM is not compatible with 1.1.00 version of KM. BMC recommends creating separate policies for 1.1.00 and 1.2.00 version of the KM.

Upgrading PATROL for Red Hat Enterprise Virtualization

PATROL for Red Hat Enterprise Virtualization KM has been merged with PATROL for Linux KM. An option to create the instances based on display names has been introduced in 1.2.00 version of the RHEV KM. This feature is disabled by default.

For any updated KMs check for the following potential incompatibilities:

• An earlier version Infrastructure Policy pointing to the PATROL Agent with the NEW version of the RHEV KM

Although this combination works, BMC recommends that new KMs must be deployed on the PATROL Agents.

• A NEW version Infrastructure Policy pointing to the PATROL Agent with an OLD version of the RHEV KM

Although this combination works, BMC recommends creating new policies with the latest Infrastructure Management version. New features will not be available with old PATROL Agent.