Skip navigation
1 2 3 Previous Next

TrueSight Infrastructure Mgmt

96 posts
Share This:

The wait is over everyone!

BMC has released TrueSight Operations Management 11.3.04. The release date was September 15th, 2020. We encourage users to upgrade as soon as possible.

 

There are three main release themes for this release, they are:

  • Flash – End Of Life – Due to the changes in the status of Flash, BMC needed to move the functionality dependent on the TrueSight Infrastructure Management (TSIM) Console to TrueSight Presentation Server (TSPS). This change brings about the deprecation of the TSIM Console. TSIM is still an active component in the TrueSight Operations Management Suite, it just does not have a visual representation through the TSIM Console. This functionality has been moved to TSPS.

 

  • Improvements in Administration – these include updates to supported operations systems & JDKs, additional authentication and authorization capabilities as well as changes to threshold management reporting.

 

  • Advancements in Visualization – BMC has provided enhancements to the Event and Group Views, updates to Dashboard capabilities, and improvements to the copy to buffer of events.

 

Announcing Adobe Flash End-of-Life and its impact on TrueSight Operations Management

TrueSight Operations Management 11.3.x uses Adobe Flash in the legacy TrueSight Infrastructure Management operator console. Adobe has announced the end-of-life for Flash, after which Adobe Systems will officially stop updating and distributing Adobe Flash.

 

The major browsers, including Google Chrome, Mozilla Firefox, and Microsoft's Internet Explorer, will no longer support Adobe Flash at the end of 2020. Until its removal, Google Chrome and Mozilla Firefox have, by default, disabled Adobe Flash and require explicit permissions from the user to activate it on a website. However, Internet Explorer and Microsoft Edge continue to support Adobe Flash until its removal.

BMC's earlier announcement about this can be accessed here.

Installation and upgrade

Added support for operating system

The TrueSight Presentation Server and TrueSight Infrastructure Management now support Red Hat Enterprise Linux (64-bit version) 8.x.

Discontinued support for operating system

The TrueSight Presentation Server and TrueSight Infrastructure Management no longer support Microsoft Windows Server 2008 R2.

Added support for AdoptOpenJDK

AdoptOpenJDK JRE version 1.8.0_252 is installed with TrueSight Presentation Server, TrueSight Infrastructure Management, and TrueSight Integration Service.

During upgrade, the current JRE is replaced with AdoptOpenJDK JRE version 1.8.0_252.

 

Operator console workflows available in the TrueSight console

View event relationships

You can now view event relationships on the Event Details page in the TrueSight console.

For more information, see Viewing related events in the TrueSight console.

Manage notification rules

TrueSight Infrastructure Management event rules are now available as notification rules in the TrueSight console.

For more information, see Managing notification rules.

Manage attribute sets in the TrueSight console

You can now manage attribute sets in the TrueSight console.

For more information, see Managing attribute sets.

Download the monitor information

You can now download metric and graph data in CSV and PDF formats from the Monitor Details > Performance Overview tab. The PDF format replicates the graph that is displayed on the Performance Overview tab.

For more information, see Viewing monitor information in the TrueSight console.

Execute agent actions

You can now execute agent actions for a monitor on the Device Details page in the TrueSight console.

For more information, see Executing agent actions on a monitor.

Monitor configuration items

You can now monitor configuration items in the TrueSight console.

For more information, see Monitoring configuration items.

View Performance Diagnostics

You can now view the performance diagnostics details on the Managed Devices page in the TrueSight console.

For more information, see Viewing Infrastructure Management performance diagnostic details.

 

Authentication and authorization

Authenticate users with OpenID Connect

TrueSight Presentation Server now supports OpenID Connect (OIDC) built on OAuth 2.0.

For more information, see Setting up OpenID authentication in Remedy SSO.

Synchronize authorization profiles

You can now synchronize authorization profiles from TrueSight Presentation Server to TrueSight Infrastructure Management by using the SYNC_AUTHPROFILES command.

For more information, see Presentation Server tssh commands.

 

Events and groups

Mandate notes for event operations

You can now make the insertion of notes mandatory for various event operations by running the tssh properties command.

For more information, see Performing event operations in the TrueSight console.

 

View a filtered event assignee list

You can now configure event preferences to show a list of users filtered on user groups, while assigning an event. To use this functionality after an upgrade, you must configure it. For more information, see Performing event operations in the TrueSight console.

Disable event annotation insertion

You can now disable insertion of event annotations into the database. By default, it is enabled.

For more information, see Viewing or adding notes to an event.

 

Display a collapsed view of parent nodes

You can now display a collapsed view of parent nodes on the Groups page by running the tssh properties command. By default, the group name displays an expanded view of nodes. For more information, see Changing the view on the Groups page.

 

Data visualization

Copy text from grid-based pages

You can now copy text from specific fields or entire rows on grid-based pages, such as Monitoring > Events.

Note that this functionality is not supported for hierarchical views. To copy text from one or more rows, select the rows and press Ctrl+c.

Image1.png

To copy text from a specific field, select and right-click the text, and click Copy. However, you cannot use Ctrl+c to copy text from a specific field.

Image02.png

 

Thresholds

Download the global thresholds configuration

You can now download the global thresholds configuration in CSV format from the TrueSight console.

For details, see Downloading the global thresholds configuration.

Save the instance thresholds configuration

You can now generate and save the absolute, signature, and abnormality instance threshold configuration values in CSV format by using the pw report threshold instance command. For details, see pw report threshold instance.

 

 

Integrations

Configure integrations from the TrueSight console

You can now use the TrueSight console to configure these integrations:

 

New out-of-the-box Orchestration policies

  • Microsoft Skype Service Down via TSSA
  • Print Spooler Service Down via TSSA
  • SNMP Service Down via TSSA

For more information, see Managing Orchestration policies.

 

 

Administering

Enable SMTPS for email alerts

You can now enable SMTP Secure protocol to receive email alerts from the TrueSight console.

For more information, see  Configuring e-mail settings to receive alerts

 

 

Dashboards and dashlets

Edit shared dashboards

You can now allow other users to edit shared dashboards by running the tssh properties command. For more information, see Sharing and copying dashboards.

Add monitors not directly associated with blueprint groups

You can now add monitors that are not directly associated with blueprint groups to the Monitors - Top or Bottom Performers dashlet.

For more information, see Monitors - Top or Bottom Performers dashlet

 

 

Content findability

You can now easily search for content across documentation spaces for the latest version of TrueSight Operations Management components.  This customized Search filter is accessible from the Home page of each component doc space.

Image03.png

 

Deprecated Features and Components

It is particularly important to take note of dropped features and deprecation within 11.3.04. Support for the following features or components is dropped in TrueSight Operations Management 11.3.04:

TrueSight Infrastructure Management Reports

For details on managing TrueSight Infrastructure Management Reports which were available in previous version, please see the following:

Managing infrastructure reports - Documentation for BMC TrueSight Infrastructure Management 11.3.04 - BMC Documentation

https://docs.bmc.com/docs/TSOperations/11304/technical-bulletin-11-3-04-000-001-hotfix-for-truesight-operations-management-11-3-04-962626955.html

 

Please see this link for more details

https://docs.bmc.com/docs/TSOperations/11304/deprecated-and-dropped-features-and-components-937357168.html

 

Known and Corrected Issues

If you are looking for a list of known and corrected issues, it can be found here

 

For more details on the changes in workflow refer to the following page

 

Be sure to check out the Upgrade paths and details located here

 

Users attempting to login to the TrueSight Infrastructure Management Console will see the following to guide them to the TSPS console.

 

TSIMOpsConsole.png

 

If you need help with the upgrade, develop your upgrade plan and have it reviewed by BMC. The AMIGO process does this for you. It is our free assistance – AMIGO – Assisted Migration Offering. We want you to have a smooth transition to 11.3.04 and with the proper assistance and review of your upgrade plan, we can do just that!

 

AMIGO.jpg

 

Have you been putting off an upgrade?

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

 

Computer.png

 

 

New TrueSight knowledge articles added to the BMC Knowledge Base over the last month:

 

000373043 TrueSight Operations Management Export Tool


000372645 TrueSight Presentation Server (TSPS) - Unable to run tssh ha status command in secondary TSPS server


000372666 TrueSight Infrastructure Management (TSIM) crashes intermittently with "java.lang.OutOfMemoryError: unable to create new native thread" in TrueSight.log


000372848 A relationship that is removed via the Remedy Asset Management Console is not unpublished from TrueSight Infrastructure Management during a normal publish


000373019 Migrate Agent Query Tool (AQT) from BMC ProactiveNet Performance Management (BPPM) 9.6 to TrueSight Operations Management (TSOM) 11.3.04


000373117 What are the TrueSight Infrastructure Management (TSIM) Cell default Knowledge Base (KB) changes between versions 11.3.03 and 11.3.04


000373236 TrueSight Infrastructure Management (TSIM) Cell runs 100% CPU at startup. The mcell-log shows repeated messages "BMC_TS-IMC080020E: Refused to delete a published data with publish environment id AtriumCMDB.PROD"

 

000373478 After upgrading TrueSight Presentation Server (TSPS), the Database Server fails to start with "PANIC: could not find a valid checkpoint record"


000373530 Upgrade of TrueSight Presentation Server (TSPS) to version 11.3.04 - Error occurred while executing Installation Task


000373752 TrueSight Infrastructure Management Error in euem_refine.mrl when compiling cell after adding mcsnmptrapdmibe and mcsnmptrapdmib to .load file

Share This:

Have you encountered the dreaded TSPS "System Error" when attempting to cross launch TSIM from the TSPS Console?

One of the common problems we have been seeing in Support is the inability to cross-launch from TrueSight Presentation Server (TSPS)  to TrueSight Infrastructure Management (TSIM).  When users try to launch the Infrastructure Management console from the TSPS console, the following error can be seen: 'System error. Please contact Administrator or try again later.' This can be a pesky error which can cause aggravation when attempting to cross launch.

 

 

SystemError2.png  SystemError11.png

This error is fairly common and the most likely causes for the issue are the following:

- The TrueSight or ProactiveNet environment is not set correctly

- There is a proxy mis-configured so the ProxyHost details need to be modified

- The Cross Site Request forgery setting is not correct

- If there is a separate installation of the Adminstrator Console on the box - when installing TSPS, the Administration Console is already installed by default, so installing a separate one on the same box mixes up the environment variables.

 

Here are a details on what do to for these scenarios:

 

Problem

When cross launching from TSPS to TSIM, only a blank page appears for the TSIM console (PNet.jsp).
  Going to the TSIM login page directly and logging in (instead of cross launching) works

Cause

Cross site request forgery (CSRF) checking

 

Solution

 

 

Setting the following parameter in the custom/conf/pronet.conf:
  pronet.tsim.csrf.filter=false
Then reloading jproperties with:
pw jproperties reload

* for Linux, also need to validate permissions for "/pw" directory (should be 755) and "umask" should be 0022

This will resolve the problem.

Make sure you have set pronet.tsim.proxy.hosts if needed:
https://docs.bmc.com/docs/display/tsim107/Troubleshooting+Infrastructure+Management

This problem has also been seen on a system that used no load balancer or proxy (just single TSPS and TSIM host).
So it is not always the case that the proxy host is the root cause of the issue.
If the problem persists, also clear the browser's history, cookies, and cache (then restart the browser).


If the issue remains after performing the steps above, please open a Support case and provide the output of the

tssh dump export command as run from the command line on the TSPS server.

Another scenario where users saw similar behavior was while attempting to access the Operations Console for the Diagnostic Report generation options. This resulted in the same System Error reported via the GUI.

 

For this scenario, the best recommendation is to check the environment variables:
This can occur if the BMC_PROACTIVENET_HOME variable is not properly set to the pw directory of your TSIM installation, i.e. C:\Program Files\BMC Software\TrueSight\pw.

If the variable is set to just the TrueSight subdirectoy, i.e. C:\Program Files\BMC Software\TrueSight, this problem will occur. One reason that the variable could be set incorrectly is if the Admin console was installed separately on the same system, after TSIM was installed (this does not need to be done, as TSIM includes the Admin Console).

 

To fix this modify the system BMC_PROACTIVENET_HOME back to the pw directory (i.e. C:\Program Files\BMC Software\TrueSight\pw), then restart TSIM.

 

For Unix:
# echo $BMC_PROACTIVENET_HOME

 

Also check to make sure the link in /usr for pw points to the correct location.

 

For example:
# ls -al /usr/pw
lrwxrwxrwx 1 root root 23 Aug 24 07:02 /usr/pw -> /data1/bmc/TrueSight/pw

 

Ensure the entry for $BMC_PROACTIVENET_HOME is correct in /etc/bmc.profile

If there is a second Admin Console installed on the TSIM server:

- Uninstall the second Admin Console

- Restart all boxes used for TrueSight

- Create a new BMC_PROACTIVENET_HOME variable, and provide the correct path. Remember to set the path through to the pw directory
i.e C:\Program Files\BMC Software\TrueSight\pw.

- In TSPS, edit and save the TSIM component.

 

After all these steps you should be able to cross-launch into TSIM, and open the Diagnostic Reports.

 

 

Similar issues have been reported when trying to login to TSPS and all users can see is a blank white page

 

Problem

The actual URL looks like:
https://abc-test-tsps.bmc.com/

When the page is reloaded, a blank white screen appears and the slash at the end will get automatically removed. If the slash is added again to the same URL, the Console appears .

Cause

We could see in the logs from the TSPS server that it is trying to communicate via different proxy

 

Solution

Turn on debug for all parameters with the following and try to login to TSPS and reproduce the issue

Take the logger name from logback.xml from TruesightInstallationDirectory/conf/logback.xml

tssh logger debug on -n AppContextApplication
tssh logger debug on -n TsimAudit
tssh logger debug on -n com.bmc.sas.ngp.service.message.impl
tssh logger debug on -n ROOT
tssh logger debug on -n UserEntityNotification
tssh logger debug on -n UserAccount
tssh logger debug on -n UserManagement

In the TrueSight.log file, users can see TSPS is trying to resolve a different proxy in logs while accessing the TSPS url

Add that proxy-name to TSPS Properties host proxy list using the steps below:

 

1) run tssh properties list

2) tssh properties set tspsProxyHosts <hostName>,<hostName>, etc...

eg- tssh properties set tspsProxyHosts abc-test-tsps.bmc.com

3) tssh properties reload

After this, the issue will be resolved.

 

More great details!  If you want to track your PATROL Events in TrueSight, take a look at this post from our own Charles Kelley! It is very informative and can help you understand your event flow from the Agent to a cell.

 

Tracking PATROL Events from Agent to a cell destination, via the Integration Service

 

 

index.png

 

**************** NEW EOL DATE ANNOUNCED - Important Note to BPPM 9.x, 8.x user****************

 

BMC has publicly announced the end of life of BPPM 9.6, all through the first half of the year, I have been reporting the date for End of Life for BPPM 9.x. However, we have listened to our customers who have expressed a need for more time to migrate to TrueSight. Time is on your side my friends and the EOL date has been extended! Please do continue to plan an upgrade/migration to TrueSight.

 

Here is the official notice in case you did not receive it:
BMC will continue to provide Limited Support for the current generally available versions of these products as defined at the Product End of Life section of BMC’s Product Support Policy until the end of support date of December 31, 2021. As per this policy, BMC will continue to develop hot fixes for problems of high technical impact; however, this solution is considered functionally stabilized, and therefore, will not receive further enhancements during this period.  

 

Effective today until the end of support date listed above, BMC will continue to provide customers with active support contracts access to BMC Customer Support as described in this letter. You can continue to interact with BMC Customer Support just like you do today to receive such support. 

 

Prior to the end of support date, customers with an active support contract have the option to migrate their ProactiveNet licenses to the replacement offerings.

If you have any questions regarding this transition, please contact your BMC Account Manager at 1-855-834-7487 and press Option 1 for Sales, or BMC Customer Support at 1-800-537-1813. To receive updated information as it becomes available, please subscribe to our Proactive Alerts for ProactiveNet and TrueSight products from our BMC Support Central site. 

 

Thank you.  

Sincerely,

Ron Coleman Director, Product Management
BMC Software  

 

AMIGO.jpg

 

Have you been putting off an upgrade? 11.3.03 is the latest and 11.3.04 is right around the corner – Fall 2020

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

 

New TrueSight knowledge articles added to the BMC Knowledge Base over the last month:

Computer.png

 

 

000371204  How to get the TrueSight Infrastructure Management 11.x "pw certificate create" command to not add unwanted FQDN to CSR when unwanted FQDN was not specified

 

000371531  Seeing error "unread block data" when trying to login to Truesight Infrastructure Management (TSIM) Remote Admin Console


000371586  Unable to add multiple lines under Value in Configuration Variables when configuring TrueSight Presentation Server (TSPS) Monitoring Policy

 

000371949  In TrueSight Console, how can a node jumping issue be avoided?


000372034  TrueSight Presentation Server unresponsive after applying Hot Fix 11.3.02.15


000372059  Requirements for Baseline Calculation in TrueSight Infrastructure Management

 

000372228  Is it possible to change what is recorded in the TrueSight Presentation Server 10.x, 11.x session.stdout log?


000372364  "No Merging of datapoint happened. Will work with the actual datapoint!!!" messages seen in the TrueSight Infrastructure Management's TrueSight.log file

 

000372364https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA33n000000PHMaCAO&type=Solution Incident ID in TrueSight Infrastructure Management (TSIM) and Remedy Force Integration

 

 

Share This:

Have you had the need to make mass changes to policies or update passwords? If so, it can be a time consuming process. BMC has developed a tool which helps manage policies within TrueSight Presentation Server 10.x+

 

The TrueSight Operations Management Auto Policy Generator is here to make policy management easier.  The TrueSight Auto Policy Generator allows users to setup monitoring of their IT using policies.  Data is collected used PATROL agent and KMs.  Policies are used to push monitoring configuration to the different PATROL agents.

In an environment where many PATROL agents reside for monitoring large (and changing) amount of monitored system, multiple policies are required to cover all aspects of IT.

 

In some cases, it is possible monitored systems are provisioned or removed on a daily basis. For that policies need to change changes as well.  This is where the TrueSight Operations Management Automatic Policy Generator (APG) comes to the rescue!

 

This tool helps users setup new policies or helps in making changes across existing policies.

The interface used with it is command line based, to allow automation of the process, thus removing the need for human interaction (in regard to these changes).

               APG, allows the user a specific set of operations:

                          a. Create new policy based on a text based template

                          b. Change value of specific fields within existing policies (e.g. replacing the password)

                          c. Update policies to add or remove monitoring of different systems (servers, applications, services).

 

It utilizes existing interface used by the cmapolicymigration utility.  APG, manipulates the monitors section of policy. It does not set thresholds, target agents or any of the other settings of a policy.

 

The APG supports 5 different commands:

CommandDescription
versionTool version
exportGenerating properties file(s) based on a monitoring policy.
updateApplying a policy change based on provided properties file(s) to an existing or new monitoring policy
listGenerate a list of existing monitor policies
encryptUtility command used to help user generate encrypted strings for passwords consumed by the policies.
upgradeSpecial command for upgrading a specific monitor policy from one version of a KM to the next. Upgrade command is migrating existing .policy definition to one belonging to a new version of the same KM. This is however limited and assumes the policy set of definition has not changed.

 

Why would you want to use it? It is a great time save, makes changing hundreds of policies a breeze.

Well just this week Support case helped a few customers asking how hundreds of policies could easily be modified to change the credentials used to access the servers for monitoring. So if you have the need to change the authentication details on policies easily, you can use the Auto Policy Generator to do that.

 

Here are a few of the use cases for working with the TSOM APG

  • Update passwords: We need to change the password of a given policy to a new on
  • Add more monitor solution environments for any Knowledge Module
  • Upgrade monitor solution
  • Oracle instance monitoring use case

 

The tool is easy to install and setup:

Make sure to install it with TSPS v10.7 or higher

 

Open a command line Windows for running the APG manually.

Windows system:

1. Extract the tool: APG.zip on the Windows server running TSPS.

2. Validate that the environment variable called TRUESIGHTPSERVER_HOME is configure, if this not configured please configure the environment variable called TS_HOME and point it to the i

 

Linux system:

1. Extract the tool: APG.tar inside $TSPS_HOME/truesightpserver/modules directory.

 

Alternatively, if you plan to install AGS in a different location then make sure the environment variable TS_HOME, points to the location of TSPS installation. (example: TS_HOME=”/opt/bmc/TrueSightPServer/truesightpserver” && export TS_HOME)

 

Where can I get this awesome time saver you ask? The TSOM Auto Policy Generator is available on BMC's FTP site

ftp.bmc.com/pub/patrol/APG/1.0-rev-10

There are various versions and revisions with 1.0-rev-10 being the latest

FTP.png

 

Note:

The TrueSight Operations Management APG does not create new policies. It can modify existing or create modified copies of existing policies.  It only works the section of setting definitions for the ‘Monitoring’ tab. Other aspects of the policy  (agent thresholds, Server thresholds, Filtering etc.) are all ignored.

 

There are easy to use commands to help with each of the use cases mentioned above:

 

Supported command usage:

1.  apg.bat/sh export -op <policy name> [-pl <property_location>] [ -port <local default application port> ] [ -protocol <HTTP | HTTPs> ]

 

a -op <policy name> - Name of the policy to export and a properties file, this field is mandatory, if you need to export more than one policy you can use the `, ` sign.

b. -pl <property_location> - Location where the km properties files are saved base on the export policy, when left blank <output directory> is used.

c. -port <local default application port> - may be required when used with TSPS where all communication is routed via a load balancing system

d. -protocol <HTTP|HTTPS> - may be required when used with TSPS where all communication is routed via a load balancing system

 

Use case: this command will export any configure policy into properties file, for each monitoring solution that is configure in the policy a properties file will be created. The properties file will hold all the current configuration of a given monitor solution.  Based on this properties file you will able to add more monitor solution environments, update any value of any given key.

 

2. apg.bat/sh encrypt [ -p <password> ]

 

Use case: This command is to encrypt ant plain text password to one that you can use in your new properties file. -p <password> - will generate an encrypted string for the plain text provided in <password>

If -p is NOT provided them ‘Password:’ prompt is used allowing the user to securely type the password  to generate the encrypted string.

 

3.  apg.bat/sh update [-enable] [-key <key_property>] [-np <new_policyname>] -op <origin_policyname> [-overwrite] -pl <property_location> [ -port <local default application port> ] [ -protocol <HTTP | HTTPs> ]

 

e. -enable - If set policy will be enable after successful update.

f. -key <key_property> - New key property to update the properties file, multi key can be use with  ',' sign.  Key can be full or partial. when fully described then only that key will change e.g. tctgjskit</>GJS_SETUP</>EnvList</>oldGeneric</>hostname The key can also be partial, being the last word only, in this case ‘hostname’. Then that is used then all properties within the file ending with ‘hostname’ will be changed to have the new value.

g. -np <new policy name> - Name of the new policy that will be created in TSPS. Enclose policy name with " " if name contains spaces, if left blank origin_policyname name will be used.  h. -op <origin policyname> - Name of the origin policy (Enclose policy name with " " if name contains spaces).

i. -overwrite – When used, the policy will be overwritten and only be create base on the KM properties file. NOTICE: overwrite will also remove from policy configuration of monitor types not defined within the provided .properties file(s).

j. -pl <property location> - Location where the update km properties file is located -port <local default application port> - may be required when used with TSPS where all communication is routed via a load balancing system

k. -protocol <HTTP|HTTPS> - may be required when used with TSPS where all communication is routed via a load balancing system

 

Use case:  With this command you can update any given policy or new policy with the changes you made for the properties file, you can create a new policy base on a template policy by using the -np flag, you can decide that the policy will be enable after a successfully import by using the -enable flag.

 

4. apg.bat/sh upgrade [-enable] [-np <new_policyname> ] -op <origin_policyname> [-overwrite] -pl <property_location>  [ -port <local default application port> ] [ -protocol <HTTP | HTTPs> ]

 

a. -enable - If set policy will be enable after successful update.

b. -np <new policy name> - Name of the new policy that will be created in TSPS. Enclose policy name with " " if name contains spaces, if left blank origin_policyname name will be used.  c. -op <origin policyname> - Name of the origin policy (Enclose policy name with " " if name contains spaces).

d. -overwrite – When used, the policy will be overwritten and only be create base on the KM properties file.

e. -pl <property location> - Location where the update km properties file is located

f. -port <local default application port> - may be required when used with TSPS where all communication is routed via a load balancing system

g. -protocol <HTTP|HTTPS> - may be required when used with TSPS where all communication is routed via a load balancing system

 

Use case:  With this command you can upgrade monitor solution policy, if TSPS repository hold newer monitor solution the tool will try to upgrade the monitor solution and invoke a report to the output.

 

 

5. apg.bat/sh list [-port <TrueSight presentation server port>] [-host <TrueSight presentation server host/address>] [-protocol https|http]

 

Use case:  generate a list of policies existing on the local TrueSight Presentation Server. notice that using this command on a Presentation Server routed via a load balancing system may require to use the below flags in order to properly get the data.

 

a. -host <host> - TSPS host name , if left blank, 'localhost' will be used

b. -password <password> - TSPS password, if left blank default will be used

c. -protocol <https|http> - Protocol used for connection with TrueSight Presentation Server,  either http (unsecured) or https (secured & default) is accepted.

d. -tenant <tenant> - TSPS tenant name , if left blank default (BmcRealm) will be used

e. -user <user> - TSPS username , if left blank default (admin) will be used

f.  -port <number> - this allow the command to connect to a none default port of the local                     

TrueSight Presentation Server so to get the list of available monitoring policies.  

 

If you have any questions or need additional assistance, please contact Support.

 

 

index.png

 

 

**************** NEW EOL DATE ANNOUNCED - Important Note to BPPM 9.x, 8.x user****************

BMC understands the situation with COVID and how it has impacted many of our customers. We therefore want to give all customers on BPPM 8.x or 9.x ample time to plan their migration to TrueSight Operations Management.

 

Here is the official notice in case you did not receive it:


BMC will continue to provide Limited Support for the current generally available versions of these products as defined at the Product End of Life section of BMC’s Product Support Policy until the end of support date of December 31, 2021. As per this policy, BMC will continue to develop hot fixes for problems of high technical impact; however, this solution is considered functionally stabilized, and therefore, will not receive further enhancements during this period.  

 

Effective today until the end of support date listed above, BMC will continue to provide customers with active support contracts access to BMC Customer Support as described in this letter. You can continue to interact with BMC Customer Support just like you do today to receive such support. 

 

Prior to the end of support date, customers with an active support contract have the option to migrate their ProactiveNet licenses to the replacement offerings.

If you have any questions regarding this transition, please contact your BMC Account Manager at 1-855-834-7487 and press Option 1 for Sales, or BMC Customer Support at 1-800-537-1813. To receive updated information as it becomes available, please subscribe to our Proactive Alerts for ProactiveNet and TrueSight products from our BMC Support Central site. 

 

Thank you.  

Sincerely,

Ron Coleman Director, Product Management
BMC Software  

 

Please reach out to your BMC Account Manager to discuss migration plans and options. If you are not familiar with who your Accoun Manager is, please reach out to Support for assistance as well. We want to ensure a smooth transition for all users of BPPM.

 

AMIGO.jpg

Have you been putting off an upgrade? 11.3.03 is the latest and 11.3.04 is right around the corner – Fall 2020

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

 

Computer.png

 

New TrueSight knowledge articles added to the BMC Knowledge Base over the last month:

 

000370358 Procedure to synchronize the TrueSight Infrastructure Management secondary cell database server with the primary cell

000370485 How to modify configuration for multiple Patrol agents from TrueSight Presentation Server (TSPS) CLI
000370608 Is TrueSight Infrastructure Management Event Adapter supported on Windows 2019?

000370727 With ProactiveNet Cell, is there a limitation on maximum value for Internal ID (data_handle and event_handle slots)?
000370791 How to disable Menu commands on the Integration Service and PATROL Agent devices under Managed Devices page in the TrueSight Presentation Server Console
000370810 TrueSight Presentation Server (TSPS) 11.3.03 - Custom KM successfully imports into the repository, but the KM does not show any where under Global, Server Threshold, or Monitoring Solutions

000370845 We are not able to see events generated by remote port monitoring with a non-admin user even though the corresponding permissions has been given on TrueSight Presentation Server
000371142 "BMC-IMC810355E - Setting Connection status FAIL" seen repeatedly in the TrueSight Presentation Server 11.3.x cellservice.log file
000371172 "Map Not found" error seen in TrueSight Infrastructure Management 11.x Web services log

000371204 How to get the TrueSight Infrastructure Management 11.x "pw certificate create" command to not add unwanted FQDN to CSR when unwanted FQDN was not specified

 

 

Feedback.jpg

Was the information in this blog post helpful? What would you like to see more of? Please let us know... we want to hear from you!

Share This:

BMC Support wants to help all our TrueSight users, specifically in terms of being able to attempt to troubleshoot issue and topics within the TrueSight Presentation Server and TrueSight Infrastructure Management components. The Support team along with our documentation team have been starting to build troubleshooting guides for various TrueSight topics.

 

We would like to have our customer base review them and let us know what you like, what you don’t like, what you would like to see more of, etc. the intention is to help you attempt to diagnose and fix an issue without delay. Users are still welcome to open cases, as Support loves to seize the opportunity to help, but the idea here is to provide some hints, helpful recommendations, and steps to help you avoid issues or troubleshoot issues. Many of the topics covered have content that has been derived from working cases or working internally in the BMC Lab.

 

These troubleshooting guides are living documents and will continue to evolve over time, so if you have any feedback, please login to leave comments, suggestions, etc.

Here are the topics which have been prepared so far:

 

 

Troubleshooting TSIM/TSPS Memory Management:

TSIM - Troubleshooting Java memory management

TSPS - Troubleshooting Java memory management

 

Troubleshooting TSOM Admin Console:

Debugging the Administration Console

 

Troubleshooting High CPU Utilization issues for TSIM/TSPS/ISN:

Troubleshooting monitoring policies

 

Troubleshooting High Availability

Troubleshooting an Infrastructure Management high availability deployment

Troubleshooting a high-availability deployment

 

 

Support will continue to work to add more topics for troubleshooting over time. We want to gauge how useful you as the TrueSight Community feel these are in your day to day operations. So if you have a topic you would like to see, do let us know and we will work on it for you. Most of the topics we are working on arise from Problem Management research specific to the products. The troubleshooting guide project is for most BMC products, but each product group will analyze the most common issues and attempt to extract details and information that is needed and/or used to address a given issue.

 

This is a supplement to the existing documentation and our knowledge base. We still appreciate users searching the knowledge base and documentation. Since these troubleshooting guides are published BMC documents, search results will report these as options depending on the terms used for the search.

BMC is excited to provide options for assistance.

 

Before I close out this tidbit for June, I wanted to be sure you were aware of the recent TrueSight High Availability Webinar presented by Steve Mundy. Here is a link to the recording

High Availability Best Practices and Troubleshooting Webinar

 

If you are interested in past or upcoming Webinar topics, check out this link and check often as the teams continue to develop great content

 

HaveYouHeard.jpg

 

 

**************** NEW EOL DATE ANNOUNCED - Important Note to BPPM 9.x, 8.x users ****************

BMC has publicly announced the end of life of BPPM 9.6, all through the first half of the year, I have been reporting the date for End of Life for BPPM 9.x. However, we have listened to our customers who have expressed a need for more time to migrate to TrueSight. Time is on your side my friends and the EOL date has been extended! Please do continue to plan an upgrade/migration to TrueSight.

 

Here is the official notice in case you did not receive it:


BMC will continue to provide Limited Support for the current generally available versions of these products as defined at the Product End of Life section of BMC’s Product Support Policy until the end of support date of December 31, 2021. As per this policy, BMC will continue to develop hot fixes for problems of high technical impact; however, this solution is considered functionally stabilized, and therefore, will not receive further enhancements during this period.  

Effective today until the end of support date listed above, BMC will continue to provide customers with active support contracts access to BMC Customer Support as described in this letter. You can continue to interact with BMC Customer Support just like you do today to receive such support. 

Prior to the end of support date, customers with an active support contract have the option to migrate their ProactiveNet licenses to the replacement offerings.

If you have any questions regarding this transition, please contact your BMC Account Manager at 1-855-834-7487 and press Option 1 for Sales, or BMC Customer Support at 1-800-537-1813. To receive updated information as it becomes available, please subscribe to our Proactive Alerts for ProactiveNet and TrueSight products from our BMC Support Central site. 

Thank you.  

Sincerely,

Ron Coleman Director, Product Management
BMC Software  

 

 

AMIGO.jpg

 

Have you been putting off an upgrade? 11.3.03 is the latest and 11.3.04 is right around the corner – Early Fall 2020

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

 

Computer.png

000369574 TrueSight Infrastructure Management: HTML links in emailed reports are http: not https:

000369636 TrueSight Presentation Management PATROL Agent ACL precedence

000369749 Launch Orchestration Action in Truesight Presentation Server(TSPS) console not working

000369932 TrueSight Presentation Server (TSPS) - Upgrade to 11.3.03 on secondary node start up is failing over the snapshot

000369950 TrueSight Presentation Server 11.3.03 REST API should not require manual GUI logins to setup a new session

Share This:

Oracle Tablespace Monitoring using PATROL for Oracle:

 

 

Extended Tablespace monitoring is an important part of the database and Patrol for Oracle Knowledge Module can be configured to monitor Tablespace Monitoring using TrueSight infrastructure polices.

 

Activating the ETSM applications

 

The ETSM applications appear only when you load the ORACLE_ETSM.kml file. If you do not want to use the new ETSM monitoring, do not load the ORACLE_ETSM.kml file

 

Monitoring by exception

 

The ETSM application uses the exception-based approach by default. With this approach, all tablespaces are initially monitored for percent used (PctUsed) and space left (SpaceLeft) parameters only. When the container-level parameter thresholds are crossed, additional monitoring for the tablespaces is initiated.

 

Monitoring tablespaces for historic data

 

Using this approach, you can use the ETSM application class to store historic data for all tablespace parameters, irrespective of the threshold limits applied at the container level

 

When you enable historic monitoring, the SpaceLeft and PctUsed parameters defined at the container-level are deactivated, and all tablespaces are discovered in their respective containers.

 

Using Patrol Console:

 

To enable the monitoring of historic data, select ETSM > KM Commands > Tablespace History > ON.

 

To disable the monitoring of historic data, select ETSM > KM Commands > Tablespace History > OFF.

 

Using Infrastructure Policy:

 

To do it from Truesight Policy refer the screenshot and check the check box

 

Using pconfig utility

 

The agent configuration variable to enable history-based ETSM monitoring is
/ORACLE_ETSM.instanceName.StoreTbspHistory.

Valid values are as follows:
_ 0 indicates exception-based ETSM monitoring.
_ 1 indicates history-based ETSM monitoring.

you can use below pconfig to enable the tablespace history on all the instances.


/ORACLE_ETSM.__ANYINST__.StoreTbspHistory
_ 0 indicates exception-based ETSM monitoring.
_ 1 indicates history-based ETSM monitoring.

 

 

To monitor newly added tablespaces after one polling cycle

 

Set the value of the /OracleConfig.ORACLE_SID.UpdateLinksSchedule pconfig variable to 1.

 

For Example

"/OracleConfig.loi1020.UpdateLinksSchedule" = { REPLACE = "1" } where “loi1020” is the Oracle SID

 

When the default value is set to 1, the CollAvailabilty parameter updates the new tablespace information to the P$AUTOEXTENDLINKS table in one polling cycle.

 

To discover newly added tablespaces immediately

 

Set the value of the /OracleConfig.ORACLE_SID.UpdateLinksSchedule pconfig variable to and do one of the following:

 

>> Manually update the CollAvailabilty collector parameter to update the P$AUTOEXTENDLINKS table with the new tablespace information. Now run the Container Resynch menu command under the

ORACLE_ETSM application class.

 

>> Restart the PATROL Agent.

 

ETSM_ tablespace type Parameters

 

  • ColSpaceLeft : collects the data for and calculates the SpaceLeft and PctUsed for the tablespaces monitored by the ETSM_ tablespace type application classes.

 

  • PctUsed : shows the percentage of space that is allocated in the monitored tablespace

 

  • SpaceLeft :

 

  • BlkReads :

 

  • BlkWrites :

 

  • PctUsed :

 

  • PhyReads :

 

  • PhyWrites :

 

  • SpaceLeft :

 

  • TotalSpace :

 

  • PctLeft :

 

  • SpaceUsed : shows the total amount of free space in megabytes in the monitored tablespace

 

Instance using ASM feature:

 

If the instance is using the ASM feature, the PATROL OS account must be a part of the primary DBA group.

 

>> If the patrol OS account is not a part of the primary DBA group then you will see below in the CollPopulateContainer debug :

 

asmQuery  = select 'DATA' dum1, free_mb/decode(type, 'NORMAL',   2,

'HIGH' ,   3,

'EXTERN', 1)

SPACE_AVAIL,

(total_mb - free_mb) SPACE_USED

from v$asm_diskgroup

where name = 'DATA1_DM'

and (state= 'MOUNTED' OR state= 'CONNECTED');

 

asmResult =

no rows selected

 

>> Adding to the primary DBA group allows Patrol OS user to access datafiles stored in ASM storage. Which is used for ETSM parameter calculation.

 

>> And having DBA/ASMADMIN as primary group for a user to access ASM storage is default requirement from Oracle side. Hence in Patrol for Oracle documentation it is listed as pre-requisite in case of ASM.

 

>> To check the correct group assigned we can execute the ‘id’ command, for example:

 

-bash-4.1$id

uid=60000(patrol) gid=6006(dba) groups=6006(patrol),30000(patrol)        

 

In output of id command the group followed by gid is the primary group for that user.

 

Filesystem dependencies

 

To gather operating system space data in PATROL for Oracle, you must install the following .km files and ensure that the parameters listed below each of the following .km files for each of them remain active (they are active by default)

 

  1. FILESYSTEM.km and UNIX_OS.km for PATROL for UNIX

-FSAvailableSpaceMB

-FSUsedSpaceMB

 

NT_LOGICAL_DISKS.km for PATROL for Microsoft Windows

-LDldFreeMegabytes

-LDldFreeSpacePercent

 

UNIX3.kml and REMOTE.kml for PATROL for UNIX

-FSAvailableSpaceMB

-FSUsedSpaceMB

 

The following parameters in PATROL for Oracle are affected if above parameters are not activated and running:

 

AVAILABILITY

-ArchFreeSpace

      -CannotExtend

ARCHIVE

      -ArchFreeSpac

      -ArchFreeSpaceOptional

CAPACITY

    -BGDumpLeft

    -BGDumpUsed

    -BGDumpUsedPct

    -CoreDumpLeft

    -CoreDumpUsed

    -CoreDumpUsedPct

    -UserDumpLeft

    -UserDumpUsed

    -UserDumpUsedPct

ETSM

    -PctUsed

    -SpaceLeft

 

 

Excluding tablespaces

 

You can set the following Agent pconfig variables by using the* and ? characters in

regular expressions:

_ /OracleConfig.oracle-sid.DefaultTablespaces

_ /OracleConfig.oracle-sid.LargeTablespaces

_ /OracleConfig.oracle-sid.VeryLargeTablespaces

_ /OracleConfig.oracle-sid.TemporaryTablespaces

_ /OracleConfig.oracle-sid.RollbackTablespaces

_ /OracleConfig.oracle-sid.UndoTablespaces

_ /OracleConfig.oracle-sid.ReadonlyTablespaces

_ /OracleConfig.oracle-sid.ExcludeTablespaces

 

To set these pconfig variables with regular expressions, use one of the following

methods:

_ From the host, right-click and choose Development => Agent Configuration => Edit

=> Add Variable, and add a variable.

_ Execute the following command in the system output window :

 

%PSL pconfig(“REPLACE“,“/OracleConfig.ORACLE_SID.tablespaceType“,

“RegularExpression|tablespaceName“);

 

For Example :

 

%PSL pconfig(“REPLACE“,“/OracleConfig.kol920db.ExcludeTablespaces“,“T*E?”);

 

Where kol920db is the database name and T*E? is the regular expression for the ETSM tablespaces. After executing the command, PATROL for Oracle excludes all the tablespaces that have the T*E? string in their name from ETSM monitoring.

 

Troubleshooting:

 

  • Using PATROL Console

 

To enable and disable CollPopulateContainers collector debugging

 

To enable the CollPopulateContainers collector debugging, choose ETSM => KM

Commands => CollPopulateContainers Debug => ON.

 

To disable the CollPopulateContainers collector debugging, choose ETSM => KM

Commands => CollPopulateContainers Debug => OFF.

 

To enable and disable container-level debugging

 

To enable the container-level debugging, choose ETSM_containerName => KM

Commands => Debug => ON.

To disable the container-level debugging, choose ETSM_containerName => KMCommands => Debug => OFF.

 

When you enable the container-level debug, by default, debugging is done for an

instance every polling cycle. However, you can use the Force Execution with Debug menu command to force the container-level debug collection in between a polling cycle.

 

For example, to enable the debugging for the ETSM_VERY_LARGE container, rightclick ETSM_VERY_LARGE, and choose KM Commands => Force Execution with Debug.

 

  • Using Truesight Infrastructure polices:

 

Here is the video link to collect Oracle KM debug from Truesight Infrastructure polices:

https://youtu.be/mXiBTe3U7rw

 

You can also refer below Knowledge Article if no access to youtube:

https://bmcapps.my.salesforce.com/kA01O000000oi6a?srPos=0&srKp=ka0&lang=en_US

 

  • Collect the below query outputs while troubleshooting the ETSM parameter offline issue.

 

Login to SQLPLUS as the PATROL database account and run the following below select statements and send the output as a file.

 

=> SQL> select * from p$etsm_cntnref;

=>SQL>select text from user_source where name='P$POPULATE_CONTAINERS';

=> SQL>select * from p$data_os_space;

=> SQL>select * from p$data_ts_spaceleft;

=> SQL>select * from p$autoextendedlinks;

 

 

For problems or queries related to tablespace monitoring please contact BMC customer support

Share This:

 

If you have been using TrueSight for any length of time, you have come to know that users have the option to deploy agents and solutions via packages from the TrueSight Presentation Server. The process is quick and easy based on the diagram below:

 

processdeployment.png

From the TrueSight repository, administrators select monitor installation components, such as the BMC PATROL Agent and monitoring solutions to create a deployable package. Monitoring solutions consist of one or more knowledge modules (KMs). The components can then be installed together using the installation package. You can reuse the installation packages or deploy the packages to managed nodes.

 

After creating a deployable package, administrators can save the package for future use, or download the package on the current host after saving the package. For saved packages, administrators can download and install the package on any host or edit a package.  From the TrueSight console, you can deploy packages that contain monitoring solutions, the PATROL Agent, and PATROL Agent patches. It is not possible to deploy packages that include the PATROL Configuration Manager.

 

There have been some best practices written up in the documentation to help avoid unnecessary issues. BMC recommends following the Best Practices regarding the Deployable packages with monitoring solutions and the PATROL Agent. You have the option to import commonly used packages and policies when you import the base Repository. Predefined packages and policies help you get started quickly and monitor your environment, without the need to create packages and define monitoring policies.

 

Creating packages is quick and easy, as an administrator, you can select PATROL Agent and monitoring solutions to create a deployable package. The components can then be installed together using the deployable package. You can reuse the deployable packages or deploy the packages to multiple computers. Ensure that you have reviewed the deployable packages best practices and have imported the Infrastructure Management PATROL repository before you start creating the deployable packages.

 

  1. Log on to the TrueSight console. In the navigation pane, expand Administration, select Repository, and select the Deployable Packages tab.
  2. Click  Create Deployable Package.
    The Create Deployable Package wizard starts.
  1. On the Installation Package Solution Selection page, select the operating system for which you want to create a package, and then select a platform on which you want to install the package.
    The list of components in the repository that are supported on the specified operating system and platform is displayed.

  jive-list-info='1' style="padding-left:45px;text-indent:-.25in"

  • PATROL Classic console
  • Oracle JRE only

If any of these components are present in the deployable package, the package is not seen in the Deploy and Install Packages screen.

 

  • How many you can deploy at one time is dependent on the amount of Disk space available on the ISN and PATROL Agent.
  • The Integration Service and PATROL Agent host must have enough disk space for deployment and installation.
  • The Integration Service must have free disk space of at least the deployable package size.
  • The PATROL Agent host must have free disk space of at least four times the deployable package size.

 

The following steps summarize the process to deploy packages on PATROL Agents:

 

Users can deploy solutions/KMs to the various agents as needed. As an administrator, you can upgrade PATROL Agents to the latest version using the same functionality used for Deploying packages to PATROL Agents using the TrueSight console. The installation runs silently with the information entered during the package creation.

There are specific requirements for upgrading PATROL Agents and if you are considering upgrading Agents using packages, please review the details here

 

During the PATROL Agent upgrade, the following validations are performed:

  • The current PATROL Agent version must be 10.0 or later.
  • The Integration Service version must be 10.5 or later.
  • The packages must match the operating system of the target PATROL Agent.
  • The Integration Service and PATROL Agent host must have sufficient disk space for deployment and installation.
    • The \pw\pronto\data\KMDEPLOYMENT directory for the Integration Service must have free disk space of at least the deployable package size.
    • The PATROL Agent installation directory must have free disk space of at least four times the deployable package size.
  • The PATROL components such as PATROL Classic Console, PATROL Central Operator, and wpconfig must be closed if the PATROL components and the PATROL Agent are running on the same computer.

Notes
Use the correct root user password to ensure a successful upgrade.

Important: If you are using the Infrastructure Management-PATROL Repository version 10.7.00, ensure to apply Fix Pack 1 that corrects an issue with upgrading PATROL Agents through predefined packages. For more information, see 10.7.00.001: Fix Pack 1

 

There are a few common issues we have seen in Support with regard to failed attempts to deploy installation components and deployable packages, so I wanted to share these details in case you ever run into this situation or perhaps it may help avoid the situation entirely.

 

Debug/Logs needed

For troubleshooting deployment issues please enable logging on the TSPS, using these commands:

Logging related to KM deployment from TSPS and debug can be enabled without any restart.

 

On the TSPS Server:

Execute the following commands on the TSPS server command line to enable high level logging

tssh logger debug on -n CMA
tssh logger debug on -n com.bmc.bpm.patrol.deploykm
tssh logger debug on -n com.bmc.bpm.patrol.kmpush

 

After reproducing the issue, provide the following logs

From TSPS :

  1. Log Files: CMA.LOG and TrueSightCMAKmPush.log
  2. Deployed Packages: <tsps_install_dir>\data\created packages
  3. Share "tssh properties list" output

 

OR send the output of the tssh dump export command with the tssh properties list command output

 

From the Integration Service Node:

  1. Log Files: TrueSightAgent_<ISN_Name>_12124_3183.log
  2. Deployed Packages: <ISN_Install_Dir>\pronto\data\KMDeployment

 

From the Target Agent:

  1. Log file: <PATROL_HOME>\tmp\Install_Log
  2. <PATROL_HOME>/logs

 

Once finished, please set the debug level back to the lower level by executing the following commands in TSPS server

tssh logger debug off -n CMA
tssh logger debug off -n com.bmc.bpm.patrol.deploykm
tssh logger debug off -n com.bmc.bpm.patrol.kmpush

 

Send the details to Support for further review.

 

Common issues/errors/etc

 

Deployment packaged failed to deploy from TSPS, deployments failed for both Linux and Windows agents.

Error message: Deploy Failed - Security certificate not found on the Integration Service

 

QUESTION:

Deployment packaged failed to deploy from TSPS, deployments failed for both Linux and Windows agents.

 

Error message: Deploy Failed
Security certificate not found on the Integration Service

certissue.png
Answer           

This indicates an issue with the Integration Server secure certificates. If you feel you have already applied the certificates, re-apply them. This is an indicator that something has gone wrong with the installation of the certificates.

 

The following is a reference link for applying the TSPS certificate on the IS for version 11.3.x

https://docs.bmc.com/docs/TSOperations/113/applying-truesight-presentation-server-certificate-to-the-truesight-integration-service-843620342.html

 

Once the secure certificates are re-applied, retry the deployment and it will most likely succeed.

 

If the deployment continues to fail, please enable debug for the CMA:

Turn on the following loggers from the TSPS command line:

From TSPS :

  1. 1.  Log Files: CMA.LOG and TrueSightCMAKmPush.log
    2.  Deployed Packages: <tsps_install_dir>\data\created packages
    3.  Share "tssh properties list" output

OR send the output of the tssh dump export command with the tssh properties list command output

From the Integration Service Node:

  1. 1.   Log Files: TrueSightAgent_<ISN_Name>_12124_3183.log
    2.   Deployed Packages: <ISN_Install_Dir>\pronto\data\KMDeployment

From the Target Agent:

  1. 1.  Log file: <PATROL_HOME>\tmp\Install_Log
    2.  <PATROL_HOME>/logs

Then once the logs are captured you can turn off the debug by switching the "on" option to "off" via the TSPS command line:

tssh logger debug off -n com.bmc.bpm.patrol.deploykm
tssh logger debug off -n com.bmc.bpm.patrol.kmpush
tssh logger debug off -n CMA

Send the logs to BMC Support for further review.

 


Unable to deploy KM package via TSPS

PROBLEM:

"Repository contains an earlier version of the BMC Installation Utility. The minimum supported version is 10.5.00." Or
"Repository contains an earlier version of the BMC Installation Utility. The minimum supported version is 10.700."

CAUSE:

Failing while installation utility version check without corresponding Repo version existed

SOLUTION:

Verify the RunSilentInstall and Thorinst versions via CLI:

Windows
=======
<TSPS_HOME>\modules\cma\pproxy\depot_directory\bmc_products\Installer\RunSilentInstall.exe -v
<TSPS_HOME>\modules\cma\pproxy\depot_directory\bmc_products\Installer\Install\instbin\Thorinst.exe -v

Linux
=====
<TSPS_HOME>/modules/cma/pproxy/depot_directory/bmc_products/Installer/RunSilentInstall -v
<TSPS_HOME>/modules/cma/pproxy/depot_directory/bmc_products/Installer/Install/instbin/thorinst -v

Example :
if TSPS version 10.5 then repository version should be 10.5 or higher
If TSPS Version 10.7 then repository version should be 10.7 or higher

If the RunSilentInstall and Thorinst versions do not match the TSPS version then install the respective repository version.
If the RunSilentInstall and Thorinst versions do match the TSPS version then execute the following commands to set the appropriate properties:

tssh properties set REPO_UPDATED_THORIUM_VERSION false
tssh properties set THORIUM_VERSION_SUPPORTED true
tssh properties reload

Then deploy a package.

 

"No packages available" seen when attempting to Install and deploy a package via the TSPS

QUESTION:

"No packages available" seen when attempting to Install and deploy a package via the TSPS

ANSWER:
Confirm that you have actually created a package. Check in TSPS -> Administration -> Repository. The error message implies that a package doesn't exist. Even though you have imported the KM into your Repository, a separate action of creating a package is necessary in order to deploy & install it.

If a package was created, you should see it. If so, edit it and confirm that it is appropriate for your Patrol Agent (e.g. same OS, bit width, etc.).  If you're unsure, send screenshots showing the package contents (all pages) to BMC Support.

 

TSPS 11.3.01 KM deployment port usage

 

QUESTION:
From the doc link https://docs.bmc.com/docs/TSOperations/113/network-ports-for-presentation-server-843619625.html it is evident that the port 8043 on TSPS server (considering TSPS is deployed on Linux) should be reachable from the Integration Service Node(s) to successfully deploy KMs. This is further confirmed in KB article https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA014000000Yo1ICAS&type=FAQ.

Are there any other ports that need to be allowed for successful KM deployment or upgrade using TS Console that is embedded in TSPS 11.3.01 or above?
What is the network flow for KM deployment.


ANSWER:
Ports involved are:
TSPS 8043 (Linux) or 443 (Windows)
ISN 12124, 3183
Patrol Agent 3181

The following is the KM deployment flow and assumes Linux.  Substitute 443 for 8043 if the TSPS is on Windows.

TSPS server contacts the ISN on port 12124 to tell the ISN to download the package.
The ISN pulls the package from the TSPS using port 8043 and then acknowledges receipt of the package via the same port.
The ISN then sends the package to the PATROL Agent using port 3181.
The Patrol Agent acknowledges the package to the ISN on port 3183.
The ISN then sends the update to the TSPS on port 8043 so that the TSPS knows the status.
The TSPS connects to the ISN on port 12124 for the package assembly.
ISN connects to the Patrol Agent on port 3181 for the package assembly
Patrol Agent acknowledges this back to the ISN on port 3183
ISN relays the same to the TSPS on port 8043
TSPS tells the ISN on port 12124 to install
ISN tells the Patrol Agent on port 3181 to install
Patrol Agent acknowledges to the ISN on port 3183
ISN acknowledges to the TSPS on port 8043

 

"Deploy failed" "Checksum mismatch" seen when attempting to deploy packages via the TSPS

QUESTION:

What might cause this error during package deployment via TSPS?

"Deploy failed" "Checksum mismatch" seen when attempting to deploy packages via the TSPS

checksum.png

 

- Trigger the package distribution
Do the following on the TSPS:
cd /opt/bmc/TrueSightPServer/truesightpserver/data/createdPackages/WinPA11P1
sha256sum WinPA11P1.gz_part_.1
sha256sum WinPA11P1.gz_part_.2

Record the two output entries for the sha256sum commands.  Note that the TSPS createdPackages directory will be populated very briefly during deployment.

On the ISN:
cd /opt/bmc/TSIMAgent/pw/pronto/data/KMDEPLOYMENT/WinPA11P1
sha256sum WinPA11P1.gz_part_.1
sha256sum WinPA11P1.gz_part_.2
Record the two output entries for the sha256sum commands.

On the Patrol Agent:
cd D:\BMC Software\Patrol3\\tmp\WinPA11P1
certUtil -hashfile WinPA11P1.gz_part_.1 SHA256
certUtil -hashfile WinPA11P1.gz_part_.2 SHA256

(Note that the SHA256 needs to be uppercase.)
Record the two output entries for the certUtil entries
 
- Disable ISN debug from the TSIM:
pw debug off -a <agent-name>
- Get ISN logs from the TSIM::
pw debug file -a <agent-name>
- Get TSPS dump:
tssh dump export
- Get this from the ISN:
.\Agent\pronto\data\KMDEPLOYMENT\

From the logs, review Agent.stdout, IntegrationService.log & MessageServiceIS.log files.
For example, in TrueSightCMAKmPush.log it will show checksum values.

Ensure that the ISN & Patrol Agent time stamps are in sync (or tell Support the time difference) when comparing files. Send all info to Support.

 

 

KM deployment fails from TSPS

QUESTION:
Why does the KM deployment fail from the TSPS?

ANSWER:

You will notice below information. (TruesightCMAKMpush.log ) - TrueSightPServer\truesightpserver\logs)

INFO 09/01 14:09:24.863 [Thread-2,IS_KM_PUSH-719b720d-35e0-46a8-b42e-eb8e1b8a413c] c.b.b.p.d.j.i.ISWaitForISAckJobState Received Ack Message NGPKMPackageDeployAckMessage{MessageID='IS-0-0-1472728161870-28', CorrelationID='TS-0-0-1472728144626-32580', Timestamp=09/01/2016 14:09:21, Destination=NGPDestination{mAgentID=0, mType=TS, mServerID=2}, ReplyTo=NGPDestination{mAgentID=10003, mType=IS, mServerID=2}, Type='PKG_DEPLOY_ACK', Priority=4, IsAckNeeded=false, AcknowledgementType=Positive, DeliveryMode=NonPersistent, Values=CHUNK_ID=1b441b5b-e519-49cc-a5ff-a56d0fafc6a3,JOB_ID=719b720d-35e0-46a8-b42e-eb8e1b8a413c,STATUS=FAILURE,STATUS_MSG=DEPLOY not successful.Connect to <SERVERNAME>:443 [<SERVERNAME>/<IP_ADDRESS>] failed: Connection refused: connect}

 

This gives indication somehow we are not able to reach to TSPS Server from ISN Machine. HTTPS communicates to the Presentation Server from the TrueSight console or web services.
The KM deployment feature through the TrueSight console uses the HTTPS connector port. Ensure this port is accessible from the Integration Service.


Port requirements for deploying packages through the TrueSight console:

https://docs.bmc.com/docs/display/public/TSOMD105/Network+ports#Networkports-NetworkportsforPresentationServer

https://docs.bmc.com/docs/display/public/TSOMD107/Network+ports#Networkports-NetworkportsforPresentationServer

https://docs.bmc.com/docs/TSOperations/110/network-ports-722059936.html#Networkports-NetworkportsforPresentationServer

https://docs.bmc.com/docs/TSOperations/113/network-ports-for-infrastructure-management-843619731.html

https://docs.bmc.com/docs/TSOperations/113/network-ports-for-infrastructure-management-843619731.html

 

Note that communication is via host name resolution.  Ensure that the TSPS can resolve the ISN & vice versa.

 

 

 

What might cause a TrueSight Presentation Server package deployment to fail with "Chunk deployment failed, check logs for details."?

QUESTION:
What might cause a TrueSight Presentation Server package deployment to fail with "Chunk deployment failed, check logs for details."?

 

ANSWER:
There are known issues with deployments failing with the "Chunk" errors reported as a result of filesystems being full.
For example, the /tmp filesystem on the target  server was full and could not deploy the package.

Free up space or add space and try the deployment again.

 

 

Users can also find a general Troubleshooting link here. Some of these items match what is above which just means that we see these issues frequently enough to attempt to document them for future reference. If you have any questions or encounter any issues with package deployment, please do not hesitate to reach out to Support.

 

ShortOnTime.jpg

 

Important Note to BPPM 9.x, 8.x users

BMC has publicly announced the end of life of BPPM 9.6. This was done at the end of the year and the support will run out at the end of 2020.


Here is the official notice in case you did not receive it:
December 31, 2019 

Dear Customer: 

 

BMC is writing to you today as a customer of BMC ProactiveNet Performance Management.

Effective today and according to terms set out on BMC’s Customer Support site (https://www.bmc.com/support/resources/bmc-product-support-policy.html) BMC is announcing the End of Life for the BMC ProactiveNet Performance Management products as listed in the accompanying product table. 

 

BMC will continue to provide Limited Support for the current generally available versions of these products as defined at the Product End of Life section of BMC’s Product Support Policy until the end of support date of December 31, 2020. As per this policy, BMC will continue to develop hot fixes for problems of high technical impact; however, this solution is considered functionally stabilized, and therefore, will not receive further enhancements during this period.  

 

Effective today until the end of support date listed above, BMC will continue to provide customers with active support contracts access to BMC Customer Support as described in this letter. You can continue to interact with BMC Customer Support just like you do today to receive such support. 

 

Prior to the end of support date, customers with an active support contract have the option to migrate their ProactiveNet licenses to the replacement offerings.

 

If you have any questions regarding this transition, please contact your BMC Account Manager at 1-855-834-7487 and press Option 1 for Sales, or BMC Customer Support at 1-800-537-1813. To receive updated information as it becomes available, please subscribe to our Proactive Alerts for ProactiveNet and TrueSight products from our BMC Support Central site. 

 

Thank you.  

Sincerely,

Ron Coleman Director, Product Management
BMC Software  

 

AMIGO.jpg

Have you been putting off an upgrade?

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

     

 

Computer.png

 

New TrueSight knowledge articles added to the BMC Knowledge Base over the last month:

 

000189182 TrueSight Infrastructure Management - Converting TSIM graphs to pdf displays junk characters in certain fields

000188977 When logging into a TrueSight Infrastructure Management User Console, that is registered into a non-default Realm, how can I login as a user in the default Realm (BmcRealm)?

000191526 TrueSight Presentation Server package deployment fails with "Chunk deployment failed, check logs for details.

000189946 TrueSight Infrastructure Management Health Check Tool Report is flagging active debugging when debug was never enabled

000188871 Predictive Events Queries in TSPS/TSIM (TrueSight Infrastructure Management)

Share This:

The TrueSight Operations Management products can now be configured to use Azul 8 Java. The Azul 8 Java license is included in the BMC license for TrueSight Operations Management. A separate license for Azul is not required. BMC released a Technical Bulletin shortly after TrueSight Operations Management 11.3.01 was released. This was meant to provide customers with another Java option.  There are always concerns and security vulnerabilities with Java and other components which can be problematic for customers. In order to provide options, some TrueSight components now support Azul 8 Java.

 

See also: Java Support link

 

Azul 8 Java is supported on the following components:

  • TrueSight Presentation Server - Only 64-bit
  • TrueSight Infrastructure Management - (Linux) - Only 64-bit and (Windows) - 32-bit and 64-bit
  • TrueSight IT Data Analytics - Only 64-bit
  • TrueSight App Visibility Manager - Only 64-bit
  • Impact Integration Web Services - Only 32-bit
  • Integration Services - 32-bit and 64-bit
  • Remote Administration Console - 32-bit

 

Note: Java applets not supported

The Azul JRE does not support Java applets. If you are using Java applets, you must use the Oracle JRE 8 on the client browser to access SNMP Adapter Configuration Manager.

 

The process to replace Java with Azul 8 Java includes a download of the files and scripts needed. For 11.3.01 and 113.02 users, the files for TSPS and TSIM are on the FTP site.

For 11.3.01, users can download the Azul 8 Java files from the following locations:

  • On the FTP server for TrueSight Presentation Server, TrueSight Infrastructure Management, and Integration Services - 11.3.01, 11.3.02
  • On the BMC Electronic Product Distribution (EPD) website for all other components

 

For 11.3.03 users:

For version 11.3.03, the Azul 8 Java scripts are available with the installer files, and the Azul binaries are available on the EPD.

Azul 8 Java is supported on the following components

ComponentRequired binariesLink to download binaries from the EPD

TrueSight Presentation Server

64-bit only

 

  TrueSight Presentation Server Version 11.3.03  

TrueSight Infrastructure Management

For Linux, 64-bit only

For Windows, 32-bit and 64-bit

  TrueSight Infrastructure Management Version 11.3.03  

TrueSight App Visibility Manager

64-bit only

  TrueSight App Visibility Manager Version 11.3.03  

Integration Services32-bit and 64-bit

  Integration Services Version 11.3.03

Note: Users must copy the Azul library and script files in the same drive where the product is installed.

Details on where to download the scripts needed to use Azul Java are found here

 

Running the Azul script performs the following tasks:

  1. Stops the relevant component.
  2. Takes a backup of the Oracle JRE.
  3. Replaces the Oracle JRE with the Azul JRE.
  4. (Not applicable to TrueSight App Visibility Manager) Copies the jre\lib\security\cacerts file from Oracle JRE to Azul JRE.Important: Restoring customized security files

    The script restores the <product_home>/jre/lib/security/cacerts file from the Oracle JRE. However, ensure that other customizations to the Oracle JRE are manually copied to the Azul JRE.

  5. Starts the services (Windows) or processes (Linux) for the relevant component.

 

Ensure that:

  • The product home environment variable is set.
  • The user who installed the product runs the Azul script.
  • If you are using a PATROL Agent to monitor a server component on the same computer where you are running the Azul script, stop the PATROL Agent before you run the script.

To run the script in a standalone environment

  • Unzip (Windows) or gunzip and untar (Linux) the Azul directory.
  • Use one of the following commands to run the Azul script depending on your component and operating system:
    ProductCommand for WindowsCommand for LinuxLocation of the Azul script
    TrueSight Infrastructure ManagementUpdate_JRE_For_TSIM.bat./Update_JRE_For_TSIM.sh
    • Windows: <installer_directory>\Windows\Utilities\Azul_Scripts
    • Linux: <installer_directory>/Linux/Utilities/Azul_Scripts
    TrueSight Presentation Server
    Update_JRE_For_TSPS.bat./Update_JRE_For_TSPS.sh
    • Windows: <installer_directory>\Windows\Utilities
    • Linux: <installer_directory>/Linux/Utilities
    TrueSight IT Data Analytics (not applicable for version 11.3.03)Update_JRE_For_ITDA.bat./Update_JRE_For_ITDA.sh
    • Windows: <installer_directory>\utility
    • Linux: <installer_directory>/utility
    TrueSight App Visibility ManagerUpdate_JRE_For_AppVis.bat./Update_JRE_For_AppVis.sh
    • Windows: <installer_directory>\utility
    • Linux: <installer_directory>/utility
    Impact Integration Web Services (not applicable for version 11.3.03)Update_JRE_For_IIWS.bat./Update_JRE_For_IIWS.sh
    • Windows: <installer_directory>\Windows\Utilities
    • Linux: <installer_directory>/Linux/Utilities
    Integration ServicesUpdate_JRE_For_IS.bat./Update_JRE_For_IS.sh
    • Windows: <installer_directory>\Windows\Utilities
    • Linux: <installer_directory>/Linux/Utilit

 

  • When the script prompts for confirmation to restart the component, type y to continue.
  • When prompted, enter the directory path where the Azul JRE is located. For example, c:\azul8.
    The script replaces the Oracle JRE with the Azul JRE and starts the services or processes for the relevant component.
  • Verify that your TrueSight Operations Management component is up and running.
  • To verify the changes, run the (Windows) java.exe -version or (Linux) ./java -version command from the appropriate directory in the following table:
    ComponentJRE directory
    TrueSight Infrastructure Management
    • Windows: %BMC_PROACTIVENET_HOME%\jre\bin
    • Linux: $BMC_PROACTIVENET_HOME/jre/bin
    TrueSight Presentation Server
    • Windows: %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\jre
    • Linux: $TRUESIGHTPSERVER_HOME/truesightpserver/modules/jre
    TrueSight IT Data Analytics (not applicable for version 11.3.03)
    • Windows: %BMC_ITDA_HOME%\jre\bin
    • Linux: $BMC_ITDA_HOME/jre/bin
    TrueSight App Visibility Manager
    • Windows: %ADOPSSERVER_HOME%\ADOP_JRE\bin
    • Linux: $ADOPSSERVER_HOME/ADOP_JRE/bin
    Impact Integration Web Services (not applicable for version 11.3.03)
    • Windows: $IIWS_HOME/BMCIIWSJVM/bin
    • Linux: %IIWS_HOME%BMCIIWSJVM\bin
    Integration Services
    • Windows: %BPPM_AGENT_HOME%\jre\bin
    • Linux: $BPPM_AGENT_HOME/jre/bin
  • Stop the standby node.
  • On the primary node, unzip (Windows) or gunzip and untar (Linux) the Azul directory.
  • Use one of the following commands to run the Azul script depending on your component and operating system:
    ProductCommand for WindowsCommand for LinuxLocation of the Azul script
    TrueSight Infrastructure ManagementUpdate_JRE_For_TSIM.bat./Update_JRE_For_TSIM.sh
    • Windows: <installer_directory>\Windows\Utilities\Azul_Scripts
    • Linux: <installer_directory>/Linux/Utilities/Azul_Scripts
    TrueSight Presentation Server
    Update_JRE_For_TSPS.bat./Update_JRE_For_TSPS.sh
    • Windows: <installer_directory>\Windows\Utilities
    • Linux: <installer_directory>/Linux/Utilities
    TrueSight IT Data Analytics (not applicable for version 11.3.03)Update_JRE_For_ITDA.bat./Update_JRE_For_ITDA.sh
    • Windows: <installer_directory>\utility
    • Linux: <installer_directory>/utility
    TrueSight App Visibility ManagerUpdate_JRE_For_AppVis.bat./Update_JRE_For_AppVis.sh
    • Windows: <installer_directory>\utility
    • Linux: <installer_directory>/utility
    Impact Integration Web Services (not applicable for version 11.3.03)Update_JRE_For_IIWS.bat./Update_JRE_For_IIWS.sh
    • Windows: <installer_directory>\Windows\Utilities
    • Linux: <installer_directory>/Linux/Utilities
    Integration ServicesUpdate_JRE_For_IS.bat./Update_JRE_For_IS.sh
    • Windows: <installer_directory>\Windows\Utilities
    • Linux: <installer_directory>/Linux/Utilities
  • When the script prompts for confirmation to restart the component, type y to continue.
  • When prompted, enter the directory path where the Azul JRE is located. For example, c:\azul8.
    The script replaces the Oracle JRE with the Azul JRE and starts the services or processes for the relevant component.
  • Verify that your TrueSight Operations Management component is up and running.
  • To verify the changes, run (Windows) java.exe -version or (Linux) ./java -version command from the appropriate directory in the following table:
    ComponentJRE directory
    TrueSight Infrastructure Management
    • Windows: %BMC_PROACTIVENET_HOME%\jre\bin
    • Linux: $BMC_PROACTIVENET_HOME/jre/bin
    TrueSight Presentation Server
    • Windows: %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\jre
    • Linux: $TRUESIGHTPSERVER_HOME/truesightpserver/modules/jre
    TrueSight IT Data Analytics (not applicable for version 11.3.03)
    • Windows: %BMC_ITDA_HOME%\jre\bin
    • Linux: $BMC_ITDA_HOME/jre/bin
    TrueSight App Visibility Manager
    • Windows: %ADOPSSERVER_HOME%\ADOP_JRE\bin
    • Linux: $ADOPSSERVER_HOME/ADOP_JRE/bin
    Impact Integration Web Services (not applicable for version 11.3.03)
    • Windows: $IIWS_HOME/BMCIIWSJVM/bin
    • Linux: %IIWS_HOME%BMCIIWSJVM\bin
    Integration Services
    • Windows: %BPPM_AGENT_HOME%\jre\bin
    • Linux: $BPPM_AGENT_HOME/jre/bin
  • Wait till the primary node is active, and perform steps 3 to 8 on the standby node.

 

Restoring the backed up Oracle JRE

If the Azul script runs into an error and cannot create the Azul JRE folder, do the following to restore the Oracle JRE:

  1. Stop all services or processes if they are running.
  2. Take a backup of the current JRE folder.
  3. Rename the jre_oracle_* folder as jre.
    For TrueSight Infrastructure Management, repeat this step for the jre_32bit folder.
  4. Start the services and processes.

 

Note possible issue: The Oracle backup folder is not created.

This issue might occur because of any of the following reasons:

  • The JRE folder is open.
  • The computer does not have enough disk space.

Solution

Do the following and run the script again:

  • Close the JRE folder and all command prompt windows.
  • (Windows) Go to the Task Manager and ensure that all Java processes are closed.
  • Ensure that there is enough disk space on the computer where you are running the script.

 

Issues/FAQ for Azul Java for TrueSight Operations Management

 

Azul upgrade script giving error "Access is denied."

User is an Administrator on the PC, but doesn't have System level access. McAfee does, so we cannot rename/kill the McAfee process. That process is named fcag.exe
We enabled batch echoing so that we could get more details. Suggested a manual copy of the Azul files into place, therefore side-step the script and McAfee

 

Is the ZULU build of Open Java supported with BMC TrueSight Infrastructure Management server?

Azul Java 8 and Azul Zulu Java 8 is same. BMC has purchased license for Azul java and following versions are certified by BMC.

1.8.0_202 and 1.8.0_232

This is what we see when we run the Java version command, it shows Zulu
./java -version

openjdk version "1.8.0_232"

OpenJDK Runtime Environment (Zulu 8.42.0.10-SA-linux64) (build 1.8.0_232-b18)

OpenJDK 64-Bit Server VM (Zulu 8.42.0.10-SA-linux64) (build 25.232-b18, mixed mode)

If any updates are needed for Azul Zulu Java, please open a case with Support provide the specific vulnerability reference and request assistance.

 

Do customers have to buy licenses for Azul Java?

BMC entered an agreement with Azul which is why we are able to distribute it. There is no need to purchase a license for Azul. BMC will work to update the documentation.

 

How can I check if the Oracle Java is replaced by Azul8 after running the utility of Update_JRE_For_TSPS.bat?

After downloading the "Azul 64-bit binaries for Windows" and "Azul scripts for Windows", the scripts were run.

Once the script was run, the following version information is reported:

C:\Program Files\BMC Software\TrueSightPServer\truesightpserver\modules\jre\bin>java -version
openjdk version "1.8.0_202"
OpenJDK Runtime Environment (Zulu 8.36.0.2-SA-win64) (build 1.8.0_202-b05)
OpenJDK 64-Bit Server VM (Zulu 8.36.0.2-SA-win64) (build 25.202-b05, mixed mode)

 

So in your environment, have you set the correct environment variable before the replacement? For example, the setting in a test environment is:

TRUESIGHTPSERVER_HOME=C:\Program Files\BMC Software\TrueSightPServer

 

 

ShortOnTime.jpg

Important Note to BPPM 9.x, 8.x users -- this will be your second reminder via the Community. Please reach out to your BMC Account Manager for assistance.

BMC has publicly announced the end of life of BPPM 9.6. This was done at the end of the year and the support will run out at the end of 2020.

Here is the official notice in case you did not receive it:


December 31, 2019 

Dear Customer: 

 

BMC is writing to you today as a customer of BMC ProactiveNet Performance Management.

Effective today and according to terms set out on BMC’s Customer Support site (https://www.bmc.com/support/resources/bmc-product-support-policy.html) BMC is announcing the End of Life for the BMC ProactiveNet Performance Management products as listed in the accompanying product table.  

 

BMC will continue to provide Limited Support for the current generally available versions of these products as defined at the Product End of Life section of BMC’s Product Support Policy until the end of support date of December 31, 2020. As per this policy, BMC will continue to develop hot fixes for problems of high technical impact; however, this solution is considered functionally stabilized, and therefore, will not receive further enhancements during this period.  

 

Effective today until the end of support date listed above, BMC will continue to provide customers with active support contracts access to BMC Customer Support as described in this letter. You can continue to interact with BMC Customer Support just like you do today to receive such support. 

Prior to the end of support date, customers with an active support contract have the option to migrate their ProactiveNet licenses to the replacement offerings.  

If you have any questions regarding this transition, please contact your BMC Account Manager at 1-855-834-7487 and press Option 1 for Sales, or BMC Customer Support at 1-800-537-1813. To receive updated information as it becomes available, please subscribe to our Proactive Alerts for ProactiveNet and TrueSight products from our BMC Support Central site. 

 

Thank you.  

Sincerely,

 

Ron Coleman Director, Product Management
BMC Software  

 

AMIGO.jpg

Have you been putting off an upgrade?

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely

 

 

Computer.png

 

New TrueSight knowledge articles added to the BMC Knowledge Base over the last month:

000186800 A TrueSight Infrastructure Management (TSIM) publish fails with "Class info is not synchronized." due to change with isVirtual attribute

 

000184596 The event and data count between HA cells is not the same, why is this?

 

000184568 Linux OS events are being Forced-closed or RATE_CLOSED and immediately reopened again

 

000184513 Events are propagated between cells that have a firewall between them, but the event flow is very low, therefore the connection is closed due to firewall configuration rules for timing out idle connections.

 

000188341 The /usr/pw/pronto/tmp/nohup.out file for TrueSight Infrastructure Management Server is not automatically pruned

Share This:

A very common problem with HA cells is when they drift out of sync.  The issue occurs when the two cells have different or conflicting information in each cell. This starts to create conflicts between the two cells until it gets to the point where the cells cannot reconcile.  Normally, one or the other cell will die and being on a TSIM it will take down all the processes as the cell is a key component which all of them communicate with. 

 

You can see pending propagation and long stream of “unbuffer sent” messages in the cell logs.  This may or may not be a problem. It could be that the cell at that given time can’t propagate the events or changes for some reason and will on the next attempt.  So, we can’t really go by logs alone but we can determine if there is a need to go further if the problem is constant throughout the logs.  It’s more of a flag really to me.

 

What I normally do in these situations is to check the PRP records in the cell itself by running:

cd $MCELL_HOME/var/<cell>

grep “PRP” mcdb | wc -l

 

If the value returned is say 10 then there is no concern.  If the value is over a 100 this is a concern as this is a clear indication that the HA cell pair has drifted into a state where it is no longer in sync.  This can be further determined by checking the cell size to see if there is a major difference.  If the difference in size is more than say 1 or 2 MB then it is likely to be out of sync.  In one case the difference was several hundred MB and there was no doubt it was out of sync.  The only way to fix the problem is to shutdown both sides and if the primary is actually the active server, copy the mcdb and xact file from the active to the passive node to manually re-sync them.  This is the only way to re-sync the cells.

 

Normally, this will occur if one member has been down for an hour or more.  In those situations, the mcdb and xact should be copied from the server that has been up so it will be in sync before the secondary is restarted.  If the member pair is down for under an hour then it will not be a problem. As it would still have the propagation still waiting.  If it is over an hour then those propagations would have timed out and will never be sent to the passive cell which is what causes the cells to be out of sync.  This sometimes happens during maintenance windows where the VM/Server is brought down to perform OS patching, ESX requires hardware work or something similar.

 

On very rare situations it can happen when it shouldn’t.  The situation would be both primary and secondary cells are in the same data center, there are no firewalls, load balancer or any other device that could cause issues with the propagation between the two cells.  The traffic to the cell is high normal to high.  When that much data has to sync across the cells then there is chances that it could drift out of sync.  What you can generally do is to add these lines to the $MCELL_HOME/etc/<cell>/mcell.conf save the file and restart the cell.

 

TCPKeepAlive=TRUE
DestinationBufferKeepWait=1h
ConnectTimeOut=1000
SynchronizeTimeOut=5000

 

To manually sync the two servers, you can do the following:

***Always take a backup before making any changes***

**This procedure assumes that it is the Primary cell which contains the correct data**

 

1 - Copy the mcell.dir file from MCELL_HOME/etc on the Primary to MCELL_HOME/etc on the Secondary.

2 - Copy the cell KB directory (MCELL_HOME/etc/<cellname>/kb) from the Primary to the Secondary. Take care not to copy the mcell.conf file that is in MCELL_HOME/etc/<cellname>

3 - Stop both the Primary & Secondary cells

4 - Run a statbld on Primary

a - cd MCELL_HOME/var/<cellname>#1

*note if this is a pre 7.4 cell then the directory will be MCELL_HOME/log/<cellname>#1

b - rename xact to xact.1

c - run 'statbld -n <cellname>#1'

5 - Delete the contents of the MCELL_HOME/var/<cellname>#2 directory for the Secondary cell

*note if this is a pre 7.4 cell then the directory will be MCELL_HOME/log/<cellname>#2

6 - Copy the contents of the Primary cell var directory (MCELL_HOME/var/<cellname>#1) over to the Secondary cell var directory.

*note if this is a pre 7.4 cell then the directory will be MCELL_HOME/log/<cellname>#1 to be copied across to MCELL_HOME/log/<cellname>#2

7 - Start the primary cell and shortly afterwards start the secondary cell. Then check the status by running the following:

mgetinfo -n <cellname>#1 -v activity
mgetinfo -n <cellname>#2 -v activity

 

There is a video that walks through the above procedure and it is available on https://www.youtube.com/watch?v=wZ2FyRIVuzo

**Please note that in newer cell versions the windows service status for the standby cell is 'Running' rather than 'Paused'**

 

How to check whether the data in the primary and secondary HA cells are in sync?


You can run:

mquery -n CellName#1 -a CORE_EVENT -s event_handle,CLASS -f csv > EVT1
mquery -n CellName#2 -a CORE_EVENT -s event_handle,CLASS -f csv > EVT2

Then compare files EVT1 and EVT2 (for instance with "diff").

 

Similarly for data:

mquery -n CellName#1 -d -a CORE_DATA -s event_handle,CLASS -f csv > DAT1
mquery -n CellName#2 -d -a CORE_DATA -s event_handle,CLASS -f csv > DAT2

 

 

What other ways do you determine a cell has a sync issue? Let us see your comments and questions.

 

TimeForAction.jpg

Important Note to BPPM 9.x, 8.x users
BMC has publicly announced the end of life of BPPM 9.6. This was done at the end of the year and the support will run out at the end of 2020.

Here is the official notice in case you did not receive it:


December 31, 2019 

 

Dear Customer: 

 

BMC is writing to you today as a customer of BMC ProactiveNet Performance Management.

Effective today and according to terms set out on BMC’s Customer Support site (https://www.bmc.com/support/resources/bmc-product-support-policy.html) BMC is announcing the End of Life for the BMC ProactiveNet Performance Management products as listed in the accompanying product table.  

 

BMC will continue to provide Limited Support for the current generally available versions of these products as defined at the Product End of Life section of BMC’s Product Support Policy until the end of support date of December 31, 2020. As per this policy, BMC will continue to develop hot fixes for problems of high technical impact; however, this solution is considered functionally stabilized, and therefore, will not receive further enhancements during this period.  

 

Effective today until the end of support date listed above, BMC will continue to provide customers with active support contracts access to BMC Customer Support as described in this letter. You can continue to interact with BMC Customer Support just like you do today to receive such support. 

Prior to the end of support date, customers with an active support contract have the option to migrate their ProactiveNet licenses to the replacement offerings.  

If you have any questions regarding this transition, please contact your BMC Account Manager at 1-855-834-7487 and press Option 1 for Sales, or BMC Customer Support at 1-800-537-1813. To receive updated information as it becomes available, please subscribe to our Proactive Alerts for ProactiveNet and TrueSight products from our BMC Support Central site. 

 

Thank you.  

 

Sincerely,

 

Ron Coleman Director, Product Management
BMC Software  

BMCCheck.png

 

 

TrueSight Best Practices Webinar Series

 

Interested in learning more about using TrueSight? If so, keep any eye on this Communities page containing the upcoming Webinar details as well as links to past Webinars.

https://communities.bmc.com/docs/DOC-107967?et=watches.email.document

 

AMIGO.jpg

Have you been putting off an upgrade?

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely

 

 

Computer.png

 

 

 

 

New TrueSight knowledge articles added to the BMC Knowledge Base over the last month:

 

000183822 "Start the previously active node node.company.com first and then start this node" is seen even though node.company.com is running.

000182383 Silent install hang and tsim_server_install_log.txt not created

000183905 How can OpenJDK 11 be added to the TrueSight Repository

000183539 What is the function of the processes associated TSIM

000182339 "The publication was not successful: Publish validation of IM(s) failed" seen when running the publish command

000181448 How to stop the PATROL Agent disconnect event increasing to CRITICAL severity after 5 minutes.

000180946 What are the cell default KB changes between TSIM versions 11.3.02 and 11.3.03

000184596 The event and data count between HA cells is not the same, why is this?

000184568 Linux OS events are being Forced-closed or RATE_CLOSED and immediately reopened again

000184513 Events are propagated between cells that have a firewall between them, but the event flow is very low, therefore the connection is closed due to firewall configuration rules for timing out idle connections.

 

                       

Feedback.jpg

Feedback is always welcome....let us know what you want to see ore of in the blog posts.

Share This:

The Integration Service is the core piece of connection between Truesight and BMC Patrol and other third-party products, such as HP Operations Manager, Microsoft SCOM and IBM Tivoli Monitoring. This component fetches data from the above-mentioned products and provides this data to the BMC TrueSight Infrastructure Management Server. Here is the architecture illustrated:

 

The Integration Service accepts streaming of PATROL data and events using a common connection port. The default port is 3183. After the events arrive at the Integration Service, they are separated and follow a unique path to one of the following based on configuration:

• The Integration Service local cell (default behavior)
• A named event cell
• The BMC TrueSight Infrastructure Management Server associated with the Integration Service

 

Best Practices

• Do not configure or add Integration Services from the Administrator console. Add them from the TrueSight console.
• Always provide a meaningful name for each Integration Service so that it can be properly identified in the environment. For example, include the network domain name where the Integration Service is installed.
• Ensure that you do not install Integration Service on the same computer where you have installed the Infrastructure Management Server.

 

Patrol Agent and Integration Service compatibility

Before you install and configure the connection between Patrol Agent and Integration Service, please check the compatibility matrix as follows:

 

How to define an Integration Server to connect with a PATROL Agent

1. While creating a package from the Truesight CMA Console:
During the process of creating a Deployable Package from the Truesight Console, you may enter one or more known Integration Service(s) to connect to. Each entry is separated by a comma and has a format of 'Protocol:IntegrationServiceHostname:PortNumber'.

For example: tcp:Integration Service Hostname:3183

where 3183 is the port on which Integration Service host is listening for incoming PATROL Agent connection for Auto-Registration.

2. Using PConfig variables:

You may also add the following pconfig variable to the existing configuration in order to define the Integration Server for connecting with the Patrol agent. This pconfig variable can be applied from the Truesight Console or directly from the Patrol Agent server using pconfig utility.

"/AgentSetup/integration/integrationServices" = { REPLACE = "tcp: Integration Service Hostname:3183" }

 

How to check if the configuration is successfully applied to a PATROL Agent?

 

1. From the Patrol Agent Error Log: Once the above configuration is done, open the latest Patrol Agent Error Logs located in the $PATROL_HOME/log directory or %PATROL_HOME%\log folder. A message in the following format should be present in the logs. This message indicates that the configuration is successfully applied, and the Patrol Agent is now connected with the Integration Server.

DAY DATE TIME: ID 1021fa: I: Connection established with Integration Service <IntegrationServerHostname> on port <Default 3183>

 

2. From Truesight Presentation Server: After the successful connection of Patrol Agent with the Integration Service it should be listed on Truesight presentation server under Managed Devices

 

3. From Truesight Infrastructure management Server: A similar entry would also be created on TrueSight Infrastructure management under the Devices option


 

Troubleshooting steps in case of unsuccessful connection between the Patrol Agent and Integration Server

In case there is an unsuccessful connection between the Patrol Agent and the Integration Service, you should see a message in the Patrol Agent Error Logs as below:

Connection with Integration Service CLM-PUN-023030.BMC.COM with port 3183 lost

 

To check the network connectivity between the Patrol Agent and Integration Service, please follow the steps below:

1. Verifying that the Integration Service is running

For Microsoft Windows, to verify that the Integration Service is running, ensure that the Integration Service Ver x.xbuild yyyy (portNumber) service status is started. If the Infrastructure Management Integration Service Ver x.xbuild yyyy (portNumber) service is not running, start it.

For Linux, to verify that the Integration Service is running, navigate to the installationDirectory/pw/pronto/bin/ directory, and run the pw agent status command. Verify that the tsim_agent process is listed. If the tsim_agent process is not listed, run the pw agent start command. This command restarts all the Integration Service processes.

If any exceptions occur, check the following log files that are stored on the BMC TrueSight Infrastructure Management Server at installationDirectory\pw\pronto\logs:
•             TrueSight.log
•             TSIMAgent.log

 

2. Execute a telnet command from the Patrol Agent server as follows:
telnet <Integration Server host/IP> <port on which Integration server is listening:default is 3183>
As a result, if a blank screen appears then the port is open, and the test is successful.

 

3. From the Integration Server, execute a netstat command as follows:
netstat -aon | findstr <port on which Integration server is running:default 3183>
You should be able to see the IP address of the Patrol Agents with “Established” connections as a result.

 

If you continue to face any issues between the Patrol Agent and Integration Server connection, please submit a case with BMC Customer Support for further assistance.

Share This:

BMC is pleased to announce the latest Service Pack for the 11.3 release of TSIM, TSPS, App Vis and ITDA. The release was official just before the end of the year!

 

 

Note: Service packs do not contain all of the files that are required for a complete product installation. Before you install the service pack, you must have previously installed the base version of the product which is 11.3.00.

 

Warning

Before applying this service pack, make sure that you have an OS backup or a VM snapshot of all affected systems. If this is not possible, make sure that you back up the individual TrueSight Operations Management components.

 

Requirements

 

Product    Version required

 

TrueSight Presentation Server

    11.3.01 or 11.3.02

 

TrueSight Infrastructure Management components

    11.3.01 or 11.3.02

 

TrueSight App Visibility Manager components

    11.3.01 or 11.3.02

 

TrueSight IT Data Analytics

    11.3.01 or 11.3.02

Note: The latest version of TrueSight IT Data Analytics is 11.3.02.

 

TrueSight Operations Management service pack version 11.3.03 provides the following enhancements and changes:

 

Review the system requirements at   System requirements and compatibility
Upgrading from an earlier version of TrueSight Operations Management? See Upgrading

The TrueSight Operations Management products can now be configured to use Azul 8 Java. For more information, see Replacing Oracle JRE with Azul 8 Java.

 

The TrueSight Operations Management configured with the Remedy SSO version 19.02 or later can now be enabled for multi-domain support. For more information, see   Enabling multi-domain support for the Presentation Server and Infrastructure Management server

 

 

TrueSight Presentation Server and Infrastructure Management enhancements

 

 

Integration with Proactive Service Resolution

With Proactive Service Resolution (PSR), you can now integrate event management and incident management. This helps you to proactively manage the IT infrastructure risks that can impact the performance of your applications and services. For more information, see   Integrating with Proactive Service Resolution to integrate event management and incident management.

 

 

Role-based access controls for shared dashboards

  • You can now view, create, modify, delete, or share dashboards only if the tenant administrator provides the permissions in the authorization profiles. The relevant roles must also have permissions to view and manage dashboards. However, all shared dashboards from earlier versions are visible under the Shared Dashboards tab and a tenant administrator can restrict these permissions.
  • Tenant administrators now have access to all the non-shared dashboards. This capability helps tenant administrators to manage dashboards that are no longer in use.
  • You can now refresh the list of dashboards and search for dashboards.
  • Adding and modifying dashboards

 

 

Orchestration policies for context-based event selection

  • The Obtain Data from PATROL Agent option is renamed to Obtain Data.
  • The PATROL Agent option from the Thresholds column is moved to the PATROL Agent column and is renamed to Show Thresholds.

Single Metric Analysis in 11.3.03

 

 

AV.SYN Execution Plan 'app1EP' in the 'app1' application was activated by user <username@orgname>.

 

 

 

On the General tab, select Unblock.
  • class="auto-cursor-target"
  • Download and extract the installation files to this folder.
Alternatively, using a third-party tool such as WinRAR also resolves this issue.

 

To install Service Pack 11.3.03, follow the sequence at   Applying feature packs or fix packs.

 

TrueSight Health Check Tool for optimizing your environment

The TrueSight Health Check Tool is now available to check if your environment is optimized for performance and stability. Use the recommendations from the generated report to reconfigure your system. For more information, see   TrueSight Health Check Tool.

 

 

Meta tag filters to group cloud resources

You can now use meta tag filters in rule-based groups to organize cloud resources in various ways, such as their purpose, geographical association, name, and type. The meta tag filters enable you to search or filter cloud resources in TrueSight Operations Management.

For more information, see   Using meta tags to group cloud resources.  

 

 

Ability to update the monitoring solution version

With version 11.3.03, you can change the monitoring solution version to the latest version while editing a monitoring policy.

For more information, see   Defining a monitoring policy.

 

 

Regulate new incoming monitor instances

The addition of new PATROL Agents and Integration Services is blocked when the monitored instance count reaches the configured maximum limit. The new incoming instances are automatically queued in the INSTANCE_WAIT_LIST database table. When you reduce the instance count below the maximum limit, the queued instances are added to the Infrastructure Management server. For recommendations to reduce the number of instances, see   Configuring Infrastructure Management self-monitoring .

 

 

SAP SQL Anywhere upgrade

When you upgrade TrueSight Infrastructure Management to version 11.3.03, the SAP SQL Anywhere (Sybase) database is upgraded from version 16 to 17. For more information, see   Preparing to apply feature packs or fix packs on Infrastructure Management.  

 

 

Automatic node status checks in a high-availability deployment

In a high-availability deployment of TrueSight Infrastructure Management, the pw system start command now automatically runs node status checks to ensure that the nodes are restarted in the correct sequence. For more information, see   pw system start.  

 

 

New event to indicate the out-of-sync status for cell databases

An internal event is now generated to indicate that the cell databases are not synchronized in an application high-availability deployment of TrueSight Infrastructure Management. For more information, see   Configuring a cell to generate an out-of-sync event.  

 

 

Serverless license support

With the serverless license, you can now monitor, view, and export the Serverless Streams - Details Report. This license enables you to monitor containers, such as Docker and Kubernetes, and other cloud computing services that do not require access to underlying hardware assets, such as servers or VMs.

Cloud VMs such as Amazon EC2 and Microsoft Azure are not included in the serverless license.

For more information about the report, see   Consumption Data reports.

 

 

Short-term instances group

You can now clean up the devices and monitoring instances marked for deletion from the system within a short period. You can do this by configuring the new out-of-the-box System: Short-Term Instances group. By default the short-term period is set to 48 hours. You can change this value using the command-line option.

For more information, see   Editing the system short-term instances group.

 

 

Automatic pruning of the nohup.out file

TrueSight Infrastructure Management 11.3.03 introduces automatic log pruning for the nohup.out file on Linux. You can also customize the pruning parameters.

For more information, see   Customizing log pruning parameters for the nohup.out file on Linux.  

 

 

CLI utilities to list and delete instances marked for deletion

You can now list the PATROL Agent details by running the pw patrolagent list command and delete instances marked for deletion in PATROL Agents by running the pw mfdinst command. For more information, see   pw patrolagent list and pw mfdinst.  

 

 

Renamed Single Metric Analysis options

You can now view the following changes on the TrueSight console when you select Single Metric Analysis from Monitoring Details > Performance Overview > Metric Comparison > Edit Settings. There is no feature or functionality impact due to this change.

  • The PATROL Agent Data column is renamed to PATROL Agent.
  • The Obtain Data from PATROL Agent option is renamed to Obtain Data.
  • The PATROL Agent option from the Thresholds column is moved to the PATROL Agent column and is renamed to Show Thresholds.

 

Single Metric Analysis in 11.3.03

Single Metric Analysis in 11.3.02

 

For more information, see   Viewing monitor information in the TrueSight console.

 

 

BMC Remedyforce integration enhancements

This version integrates with BMC Remedyforce 20.19.02 to support:

Downloading the service pack

You obtain the installation files for the TrueSight Operations Management solution from the BMC Electronic Product Distribution (EPD) site. Your ability to access product pages on the EPD website is determined by the license entitlements purchased by your company.

Follow these links to obtain the installation files:

 

Installing the service pack

On some Windows computers, after downloading the service pack installation files from the BMC Electronic Product Distribution (EPD) site, you may be required to unblock the .zip files before extracting them.

  1. Right-click the downloaded .zip file and select Properties.
  2. On the General tab, select Unblock.
  3. class="auto-cursor-target"
  4. Download and extract the installation files to this folder.

Alternatively, using a third-party tool such as WinRAR also resolves this issue.To install Service Pack 11.3.03, follow the sequence at Applying feature packs or fix packs.

 

 

 

Need Help getting to 11.3.03? AMIGO can help!

AMIGO.jpg

 

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

 

Computer.png

TrueSight Knowledge Article Highlights

 

000180134 Is the ZULU build of Open Java supported with BMC TrueSight Infrastructure Management server?

 

000180135 Is 150 concurrent https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA014000000lAk1CAE&type=FAQusers on a TrueSight Presentation server a hard limit?

 

000031216 What are the different ways of enabling cell trace ?

 

000168568 The memory consumption of TSIM can generally be reduced by changing the garbage collection settings

 

000158447 How to check the port connectivity between TSPS/TSIM/LB

 

000137465 When cross launching from TSPS to TSIM, only a blank page appears for the TSIM console (PNet.jsp)

 

000112475 We have noticed that in BPPM and TSIM the Apache logs are not rotated out over time and this means the logs can grow unbounded and cause random performance issues over time.

 

000133526 TSIM Java processes (Rate, Local Agent, Agent Controller) does establish number of connections with remote cell(s) which are added in mcell.dir for use of mcell process.

 

000101942 Self Monitoring Deployment Event:Monitor Instances count

 

000174060 Filesystem monitoring - How to exclude in case of 1000’s of filesystem (Docker and another containers)

 

000154556 When TSIM is in HA setup, how does it determine when to failover?

 

000025456 How to enable trace for publishing server for troubleshooting a publish problem ?

Share This:

The PATROL Agent is the core piece of the PATROL architecture that monitors managed systems. PATROL Agents load information from Knowledge Modules, gather statistics, and send alerts and requested information to various Consoles. To run parameters, recovery actions, and application discovery, the Patrol Agent must use a valid User account.

 

Many application Knowledge Modules use pconfig() in their PSL scripts to edit and add agent configuration variables. The PSL pconfig() function uses the Patrol Agent Default Account.

 

The PATROL Agent uses the default PATROL account for rights to perform the following advanced functions:
• collect information from performance counters
• collect information from the Windows event log
• self-tune for peak performance and non-intrusive use of the processor
• access system-level information
• make debug-level output available from the PATROL KM applications
• access the command interpreter for operating-system-level commands
• create and remove processes in the process table for collecting performance data

 

Type of accounts:

  • In a Windows environment PATROL default account can either be a local or a domain account.
  • In a Unix environment PATROL default account can either be a local or LDAP account.

 

Account prerequisites for a Unix OS:

  • Do not use root account as a patrol default account because this might create security risks.
  • User account should have login shell.
  • Create a local user (or a network user).
  • Patrol default account user should be the owner of the installation directory.
  • Patrol default account user should have write permission set (755) on the installation directory.
  • Patrol default account should have Write permission set (755) on /tmp dir.

 

Account prerequisites for a Windows OS:

  • On Windows platforms PATROL agent runs as its own user.
  • Before installing the Patrol agent a local or domain account must be created/exist on the server.
  • If the local user is being used for the patrol agent installation, then that user should be a part of the local administrator group.
  • If the local\domain user is being used for the patrol agent installation, then that user should be part of the local and domain administrator group.
  • The installation program grants the following advanced user rights to the PATROL Agent default account.

How to change the Patrol Agent Default Account?

The Default Account information is stored in the/AgentSetup/defaultAccount agent configuration variable. By default, it uses the account used to install Patrol. However, you can change the account that the agent runs under.  If there are any changes made to this account on the OS level or if you would like to change the account username or password, you can use any of the following methods to change the Patrol Agent default account:

 

  1. Using the pconfig utility:
  • Run the pconfig +get command to get the current configuration and save it to a file.
    Syntax: pconfig +get -p (PortNumber) > (FilePath)
    For eg: pconfig +get -p 3185 > /tmp/pconfig.txt (For UNIX OS) OR pconfig +get -p 3185 > C:\temp\pconfig.txt (For Windows OS)    
  • Go to the PATROL_HOME\bin directory and run the Encryption Utility to generate the encrypted password. The output of the following command will be the encrypted password.
    Syntax: pwd_encrypt <Enter the plain-text password here>
    For eg: pwd_encrypt patrol1234
  • Enter the Username and Encrypted Password in the /AgentSetup/defaultAccount in the pconfig.txt file generated in the first step.
    For eg: "/AgentSetup/defaultAccount" = { REPLACE = "patrol/$-2$-$A88CA7BD3DADDDFFC85FFF1CCCE8C383" },
  • Reload the configuration back to the Agent
    For eg: pconfig +Reload  /tmp/pconfig.txt (For UNIX OS) OR pconfig +Reload  C:\temp\pconfig.txt (For Windows OS)

 

2. Using Truesight CMA Console (Agent Section):

  • Create an Infrastructure Policy (Configuration=>Infrastructure Policies=>Create Policy)
  • Go to the “Agent” tab
  • Enter the username and password in the “Agent Default Account” Section. Here is a screenshot of this section:

3. Using Truesight CMA Console (Configuration Variables Section):

  • Create an Infrastructure Policy (Configuration=>Infrastructure Policies=>Create Policy)
  • Go to the “Configuration Variables” tab
  • Click on “Add Configuration Variable”
  • Enter “/AgentSetup/defaultAccount” in the Variable section
  • Enter the username/encrypted password (See Method#1 for generating the encrypted password) in the Value section.

 

For any further questions, feel free to comment on this post or contact BMC Customer Support through a support case.

Share This:

Have you heard about the new TrueSight Operations Management Health Check Tool? If not, you came to right place. BMC has developed a quick and easy health check tool to review the environment and compare it to the desired tuning recommendations for your setup. The tool is quick and easy to download and run and there is a tool for both TSPS and TSIM servers. So this new tool will share a lot of details about the configuration settings and parameters set in your environment and will show us how your environment matches up to expected settings.

 

This is a great tool to verify the configuration of the TSPS and the TSIM for and can make recommendations for tuning changes in the environment.  Support will likely ask you to run it if you open a ticket and there is a concern over performance, sizing, etc... so this tool will be used in numerous environments. This is a live tool, but it is one we are looking to continually evolve. If you have any questions or have feedback about the Health Check tool, please let us know and the team will work to deliver what we can.

 

Users can download the Health Check Tool from the FTP site ftp://ftp.bmc.com/pub/TSOM/HealthCheck/ the file would need to be downloaded to the TrueSight Operations Management component you want to verify. If you choose to run on the TSPS, download to the TSPS, if you choose to run on the TSIM server, download the file to the TSIM server. We would recommend both components and on each component… for example, if you have an HA environment, run on each of the servers.

HealtCheckFTP.png

The details for installing and running the health check are quick and easy, see below:

Prerequisites

==============================

Free disk space of approximately 500 MB

 

Installing the tool

==============================

 

1) Download the latest zip file from location ftp://ftp.bmc.com/pub/TSOM/HealthCheck

2) For TSIM, extract the file into %BPPM_SERVER_HOME%

3) For TSPS, extract the file into %TRUESIGHTPSERVER_HOME%

 

Steps to execute the tool

==============================

 

1) Open a command prompt, navigate to %BPPM_SERVER_HOME%/utility/TrueSightHealthCheck or %TRUESIGHTPSERVER_HOME%/utility/TrueSightHealthCheck and as the TrueSight User or the User you installed with, execute the following:

 

TrueSightHealthCheck.bat

or

sh TrueSightHealthCheck.sh

 

Step1.png

Step2.png

 

2) Once the script has executed, it will advise to check the summary report under utility/TrueSightHealthCheck/reports e.g. Please check TrueSight health summary report at C:\Program Files\BMC Software\TrueSight\utility\TrueSightHealthCheck\reports\<TSIM_TruesightHealth_2019082801530>.html for more details.

 

 

step5.png

 

 

Steps To uninstall

==============================

TSIM:

Delete the folder %BPPM_SERVER_HOME%/utility/TrueSightHealthCheck

 

TSPS:

Delete the folder %TRUESIGHTPSERVER_HOME%/utility

 

----------------------------------------------------------------------------------------------------------

If you have any questions about the execution of the Health Check tool, contact BMC Customer Support.

----------------------------------------------------------------------------------------------------------

 

A brief overview of what the Health Check tool does on the TSIM and TSPS servers - the steps are the same on each server, the underlying checks made are TSIM/TSPS specific.

 

Copy the tool to the TSIM server/TSPS server, and then execute the tool by running the .bat or .sh script mentioned in the readme.

 

The command prompt will show the steps which are being processed by the Health Check tool.

 

There are 10 steps taken in the Health Check Tool

 

Step 1 - initializes the tool – sets environment variables needed for the tool

Step 2 - validates the OS prerequisites for running the Health check tool

Step 3 - validates the OS configuration for running TSIM – the same as the installer – checks OS, RAM, CPU, disk space, etc

Step 4 - validates the performance tuning parameters as per our documentation. It includes heap settings, garbage collection settings, etc..

Step 5 - validates the properties most commonly used in the product (TSIM) – looks for duplicate parameters, Control M characters, etc

Step 6-  validates to see if a particular message exists in the log file – any errors or concerns

Step 7 - runs several checks against the database and will check Oracle tuning parameters, MFD counts, instance counts, etc.

Step 8 - validates the ports between components and will validate if there are any issues in connecting the TSIM to the TSPS tool

Step 9 - executes the scripts used for netstat details OS patch levels, important version details, etc.. the details are captured in the Summary Report

Step 10 - consolidates all the reports generated in the steps above and creates the Summary Report – it will show the path to the Report which was generated as a result of running the tool

 

If any of these steps fail, the health check tool will continue past the step which failed but can continue through the rest of the steps. Once the script is run, a report is generated with the results

and the summary report will show in the reports folder with the timestamp. Open the report in either a Browser or via Excel.

 

step6.pngStep7.png

 

 

If you are still not convinced the Health Check tool is for you, register for the upcoming Webinar for the Health Check Tool and see for yourself what it can do!

 

HealthCheck.jpg

 

Webinar - The New Health Check tool | TrueSight Operations Management

Sign up for the TrueSight Webinar on the TrueSight Operational Management Health Check Tool

What     30-minute best practices webinar
When    Wednesday October 9th, 10am CDT (US)
Where   WebEx (see below)
Who      TrueSight Operations Management users of any experience level

 

AMIGO.jpg

 

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

Computer.png

000172277  "Infrastructure Management Servers cannot be accessed" seen when viewing TSPS console -> Monitoring -> Events -> Showing events from all Infrastructure Management Servers

000172295  In TSPS, NOT operator in EventList Dashlet is not working as expected

000172359  Incorrect mapping of hardware KM instances on TSIM console

000172646  Devices not showing up in groups on TSPS Console

000172972  New PATROL Agent is not being created in either TSIM or TSPS

000172747  "Optimistic check for FedCacheRuntime status failed." error in the TrueSight.log file, what is the cause, is it harmless?

000172664  Unable to install TSPS 11.3.02 on Linux in silent mode due to missing library libXrender.so.1

000173205  /usr/pw/pronto/bin/pwstartupWrapperHA script is missing arguments in TrueSight 11.3.02

000173247  How to correlate Application Classes and Parameters in Patrol to Monitor Types and Attributes in TrueSight?

000173377  Can I get a list of Patrol Agents currently experiencing "The following policies could not be applied"?

 

Feedback.jpg

 

We want your feedback! We open to hearing your thoughts on topics and areas of concern which may be of benefit to you! Post your comments regarding what you want to see.

Share This:

Recently, the Support team has seen an increase in the number of PATROL Agent security issues. These security issues can lead to several problems in the TrueSight arena. The most commonly seen error when the PATROL Agent will not connect to Integration Service is found in the PATROL Agent error log:

Enabling Integration Service support subsystem.
ESS Error: ESS_Policy_InitSecurityPolicy() failed >-4<

ESS Error: Security policy is either missing or unreadable: /etc/patrol.d/security_policy_v3.0/proxy.plc/common /etc/patrol.d/security

_policy_v3.0/proxy.plc/client /etc/patrol.d/security_policy_v3.0/proxy.plc/common /etc/patrol.d/security_policy_v3.0/proxy.plc/client >-4<

 

The root cause for almost all of these errors referenced above is permissions on the security files.

 

We also see a PATROL Agent security problem when the Patrol Agent has been deployed some time in an environment where an older version of the Agent is being used. When the older Agent is upgraded to the latest version, some Administrators have been using the overwrite security checkbox set to “Yes” setting. Generally, there really is no reason to set the overwrite security to “Yes”.

 

The recommendation is to leave the security setting to “No” when upgrading the Agent. Using this setting can cause major interruptions in the operation of these Agents if they are used for TSIM or the Integration Service if the Agent is on the same VM or server.  It can also cause issues with certificates and security level settings of the Patrol Agent where the security level is higher than level 2 like the example below in the deployable package creation:

PASecurity.png

  • There are some cases where the PATROL Agent is installed and does not start in the environment. If the install was not done as root, users can run through the details of this Knowledge Article to fix the permissions issue.

 

  • Other cases which looked like a PATROL Security issue ended up being a firewall issue, so it is important to check permissions and firewalls when users cannot connect to the newly deployed PATROL Agents. In the instance where the Agent was not connecting, we found the error “TCP |1537197978| Fd = 924 NumRead = -1 errno = 10054” in the Patrol Console debug log. This error means that the connection got reset by the peer. Error 10054 occurs when the connection is reset by the peer application, usually due to an incorrect firewall configuration. A socket error 10054 may be the result of the remote server or some other piece of network equipment forcibly closing or resetting the connection.
    More details are available at https://docs.microsoft.com/en-us/windows/desktop/winsock/windows-sockets-error-codes-2 and  http://help.logmein.com/articles/en_US/FAQ/What-does-Error-10054-mean
    So, if you are seeing the TCP 10054 error in the Patrol Console debug log, please work with your Network Administrator, to check the firewall setting or any other network setting which is prohibiting cross domain communication.

 

  • We have seen cases where the Patrol Agent is unable to connect to the Integration Service on any IP Address, along with a  Time_Wait when doing a netstat on port 3183. Even after a restart of the OS on both the Integration Server and the Patrol Agent box, the issue remained. Usually if this is still an issue, Support would like to review the following

- %PATROL_HOME%\log\PatrolAgent-hostname-3181.errs on Patrol Agent box
- Agent\pronto\logs folder on IS

 

In this case, the logs did show the common error indicating a permissions issue, see the snippets below:

Enabling Integration Service support subsystem
ESS Error: ESS_Policy_InitSecurityPolicy() failed >-4<
ESS Error: Security policy is either missing or unreadable: /etc/patrol.d/security_policy_v3.0/proxy.plc/common  /etc/patrol.d/security_policy_v3.0/proxy.plc/client /etc/patrol.d/security_policy_v3.0/proxy.plc/common /etc/patrol.d/security_policy_v3.0/proxy.plc/client >-4<
Integration Service Client policy should be at security level 2. Current Level = -1.

 

          This issue was resolved through changing the permissions based on the details below:

          The file /etc/patrol.d/security_policy_v3.0/proxy.plc had been installed with the wrong permissions.

          These are the permissions in place:
          /etc/patrol.d/security_policy_v3.0:
     total 144
          drwxr-xr-x 3 root sys 8192
          drwxr-xr-x 4 root sys 8192
          -rw------- 1 root sys 866 agent.plc
          drwxr-xr-x 2 root sys 96 bak
          -rw-r--r-- 1 root sys 226 client.plc
          -rw-r--r-- 1 root sys 549 esi.plc
          -rw------- 1 root sys 1240 proxy.plc
          -rw-r--r-- 1 root sys 40 signer.plc
          -rw-r--r-- 1 root sys 1459 site.plc
          -rw-r--r-- 1 root sys 46 verifier.plc

                   

              We can see that some of the policy (.plc) files had the correct permissions of 644 (-rw-r--r--), but the agent.plc and proxy.plc files only had 600 permissions (-rw-------).

 

             This meant that the Patrol default account could not read these files. These are the commands run as root during the install or post install using the .log_rootscripts file:

 

         

For the .plc files with correct permissions:

/products/patrol/9.10.00/common/security/config_v3.0/policy_install.sh /products/patrol/9.10.00/common/security/config_v3.0/site_0.plc site.plc FALSE
/products/patrol/9.10.00/common/security/config_v3.0/policy_install.sh /products/patrol/9.10.00/common/security/config_v3.0/esi.plc esi.plc FALSE
/products/patrol/9.10.00/common/security/config_v3.0/policy_install.sh /products/patrol/9.10.00/common/security/config_v3.0/signer.plc signer.plc FALSE
/products/patrol/9.10.00/common/security/config_v3.0/policy_install.sh /products/patrol/9.10.00/common/security/config_v3.0/verifier.plc verifier.plc FALSE
/products/patrol/9.10.00/common/security/config_v3.0/policy_install.sh /products/patrol/9.10.00/common/security/config_v3.0/client.plc client.plc FALSE

The script policy_install.sh has the following line towards the end:
chmod 644 /etc/patrol.d/security_policy_v3.0/$dest_policy_file
This sets the correct permissions.

Now let's look at problem files:

/bin/cp /products/patrol/9.10.00/Patrol3/security/agent.plc /etc/patrol.d/security_policy_v3.0/agent.plc
/bin/cp /products/patrol/9.10.00/Patrol3/security/proxy.plc /etc/patrol.d/security_policy_v3.0/proxy.plc

The files are simply copied with no chmod. If by default, the root account does not create files with a umask of 022, then the permissions on these files will be wrong. In order to resolve this, simply modify the permissions like this:

 

chmod 644 /etc/patrol.d/security_policy_v3.0/agent.plc
chmod 644 /etc/patrol.d/security_policy_v3.0/proxy.plc

Then restart the PatrolAgent. Please note that the Patrol installation assumes that the default umask will be 022. If it is not this, then files may be laid down with

incorrect permissions in some cases.

 

  • The times when the security errors appear in the PATROL Agent error log it is most likely permissions related, please do the following

          Stop the PATROL Agent and take a backup of agent.plc and proxy.plc from /etc/patrol.d/security_policy_v3.0

 

          Copy agent.plc and proxy.plc from /opt/bmc/patrol/patrol/security :

/bin/cp /opt/bmc/patrol3/security/agent.plc /etc/patrol.d/security_policy_v3.0/agent.plc
/bin/cp /opt/bmc/patrol3/security/proxy.plc /etc/patrol.d/security_policy_v3.0/proxy.plc

 

          Ensure that the permissions of the .plc files are 644 (-rw-r--r--). If not, then issue chmod's :      

       chmod 644 /etc/patrol.d/security_policy_v3.0/agent.plc
       chmod 644 /etc/patrol.d/security_policy_v3.0/proxy.plc

 

          Start PATROL Agent and it should now connect to Integration Service.

 

 

Permissions issues are not the only cause of PATROL Security issues, but if you do encounter issues, please open a case with Support for further assistance.

 

Knowledge Articles related to these types of issues

000160869 /etc/patrol.d/patrol.conf permission changes to 600 after Patrol installation/upgrade in some scenarios when umask is set to 0077

000092497 Patrol Agent startup error: Security policy is either missing or unreadable

000099021 Patrol Agent Error: ESS_Policy_InitSecurityPolicy() failed >-4<

000099188 PATROL Agent will not connect to Integration Service

 

 

AMIGO.jpg

TrueSight Operations Management 11.3.02 is out....plan to upgrade.migrate now!

Note: 11.3.02 requires users to upgrade/migrate to 11.3.01 first and the apply the Service Pack to move to 11.3.02

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan, and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case, and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade, and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

Computer.png

 

 

New TrueSight knowledge articles added to the BMC Knowledge Base over the last month:

 

000171371 The -t (timeout) option of mcstat command is not working as expected

 

000171481  Cell blackout policy is reopening event that it did not blackout

 

000171487  Is there a Float option in BMC TrueSight 11.3.x?

 

000171551  Is there a way to create a dynamic event filter in TSPS to show the current User's Assigned Events?


000171914  How to delete an entry from 'tssh properties'?

 

000172006  Secondary TSPS is missing devices and events

 

000172048  Graph Display in TSIM 10.7 FP3 does not show updated thresholds correctly


000172168  TrueSight Presentation Server(TSPS) - is not impacted by 2019-082 Apache Struts security vulnerabilities


000172277 "Infrastructure Management Servers cannot be accessed" seen when viewing TSPS console -> Monitoring -> Events -> Showing events from all Infrastructure Management Servers

 

000172393  How to report the ciphers used for TrueSight Presentation Server and Infrastructure Server

Share This:

TrueSight users are aware of the default realm created in TrueSight. The default realm * contains all the BMC created user roles which are associated with authorization profiles for use in TSPS and the default realm. Many TrueSight users take advantage of multiple realms and would like the ability to copy the default roles to the new realms they have created. Currently, this is not an option in the TrueSight GUI, but BMC has created a script which will copy the default realm user roles to a new realm which has already been created!

 

Create a new realm or use an existing realm and then use the script which BMC has created which will create all of the default roles in the * realm to the realm specified in the script.  For default purposes the script targets the "TSOM" realm as the destination realm for the second realm. If you need to create roles in a different realm, simply edit the .sql and replace "TSOM" with the specific realm name:

FAQ on the script:
1) Does this take all the roles from the default realm?

The script was created using the list of default Roles present in the TSPS database for the * realm.  The script is static so if BMC Creates additional Roles they will not be created in alternate Realms/Tenants.


2) What is the syntax for applying the script? How do we apply it? Can you provide details?
If you are using a standalone setup you can directly run the script and restart TSPS. If you are running an HA setup then you have to follow the additional steps provided.

3) Can you explain a bit more about the details of what the script does?

The default roles are copied from the * realm and a duplicate is made within the new realm and the duplicate roles are inserted into the roles table and given the same permission as the roles  in the  * realm.


4) Are there any restrictions or limitations with using this script?
None that we are aware of at the present time.  None were encountered during testing of the script.


5) What is the expected result of the script? Will the user be able to login to the other realm and see all of the roles from the default realm?
All the default roles and permissions from the * realm will be replicated in the TSOM realm.  By creating and adding the roles to the appropriate Authorization profiles the user will have the same access in the TSOM Realm.

 

You will need the following information before proceeding with the following steps:

 

TSPS Postgres Database name: truesight

Postgres Database User name:

Postgres Database Port Number:

 

This information can be found in the following locations:

 

On the TSPS Server navigate to:

 

Windows: drive:Program Files\BMC Software\TrueSightPserver\

Linux: /opt/bmc/TrueSightPServer/

 

Open the TrueSightPServerInstalledConfiguration.xml file:

 

Look for the following entries:

      <name>TrueSight_database_username</name>

      <value>patrol</value>

 

      <name>TrueSight_database_port</name>

      <value>5432</value>

 

Instructions for a standalone environment:

=============================================================

1.    Establish a connection to the TSPS Server either via RDP or SSH depending on OS

2.    Copy the attached sql script file to the tmp directory of the TSPS Server.

          Note: On Linux ensure that the user has the ability to read the file.

3.    Navigate to the following directory on the TSPS Server

          Windows: drive:Program Files\BMC Software\TrueSightPserver\truesightpserver\modules\pgsql\bin

          Linux /opt/bmc/TrueSightPserver/truesightpserver/modules/pgsql/bin

4.    Execute the psql.exe on windows psql on Linux.  On Windows open an elevated command prompt (Run as Administrator)

5.    psql Syntax

          psql -d truesight -U postgres -p 5432 -a -q -f /home/jobs/Desktop/resources/postgresql.sql

Parameter usage:

-h PostgreSQL server IP address

-d database name

-U user name

-p port which PostgreSQL server is listening on

-f path to SQL script

-a Print all nonempty input lines

-q specifies that psql should do its work quietly

 

6.    psql -d truesight -U patrol -p 5432 -a -q -f /tmp/create_roles_tsom_realm_script.sql

7.    You may be prompted to provide the password for the dbuser.

8.    Execute  tssh server start

9.    Wait for the system to become available.  Login to the TSPS console.  Navigate to Administration -> Roles

 

Roles1.png

 

 

 

 

 

Instructions for an HA environment:

=====================================================================

1.    Establish a connection to the secondary TSPS Server either via RDP or SSH depending on OS and execute.

               tssh server stop

2.    Establish a connection to the Primary TSPS Server either via RDP or SSH depending on OS

3.    Copy the attached sql script file to the tmp directory of the TSPS Server.

               Note: On Linux ensure that the user has the ability to read the file.

4.    Navigate to the following directory on the TSPS Server

               Windows: drive:Program Files\BMC Software\TrueSightPserver\truesightpserver\modules\pgsql\bin

               Linux /opt/bmc/TrueSightPserver/truesightpserver/modules/pgsql/bin

5.    Execute the psql.exe on windows psql on Linux.  On Windows open an elevated command prompt (Run as Administrator)

6.    psql Syntax

               psql -d truesight -U postgres -p 5432 -a -q -f /home/jobs/Desktop/resources/postgresql.sql

Parameter usage:

-h PostgreSQL server IP address

-d database name

-U user name

-p port which PostgreSQL server is listening on

-f path to SQL script

-a Print all nonempty input lines

-q specifies that psql should do its work quietly

 

7.    psql -d truesight -U patrol -p 5432 -a -q -f /tmp/create_roles_tsom_realm_script.sql

8.    You may be prompted to provide the password for the dbuser.

9.    Execute tssh server start on the Primary TSPS server

10.  Execute tssh server start on the Primary TSPS server

11.  Wait for the system to become available.  Login to the TSPS console.  Navigate to Administration -> Roles

 

Roles1.png

 

If you have any questions or need assistance with this script, please open a Support ticket and the team will be glad to help. The script was tested on 11.3.01 only at this time.

 

Please do let us know if these types of scripts and enhancements are useful to you or what you would like to see added to TrueSight!

AMIGO.jpg

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan, and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case, and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade, and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

 

 

Computer.png

 

New Knowledge Added over the last month:

Check out some of the latest knowledge articles added to our Support knowledge base!

 

000168894 BPPM 9.6 compatibility with RedHat Linux 7.6

 

000169052 Download of 11.3.02 TSIM Administration Console package from TSPS failed to install

 

000169132 How to monitor latest log files with a single Log file instance

 

000169202 How to set a Global Table View as my default view when I login to TSPS

 

000169267 ITDA - Console Server Fails to Start/License Key Error “Error while decoding licence key”, Post ITDA 11.3.02 Upgrade from ITDA 11.3.01

 

000169628 TrueSight Report Engine Error ORA-04025

 

000169629 TrueSight Report Engine Error in populating

 

000169685 TrueSight Smart Reporting - Launching Smart Reporting Failed

 

000169709 tssh event reinitialize failed with a NoClassDefFoundError exception

         

000170227 Is it possible to download solution packages from the TrueSight Presentation Server directly via the API?

 

 

 

   

 

Share This:

Events, events, events!

 

TrueSight is definitely used to manage events. Data and events are our focus. When discussing events, there are many different types of events, third party events, internal events, manually created events, and all these events come from various sources. One such source is email. There are many companies using TrueSight which are looking to turn email messages into events and send them along through TrueSight for handling. TrueSight and BPPM both offer the basic email2event functionality. The feature is fairly straightforward and despite some limitations, many users have been able to set it up in their TrueSight environment and use it successfully.

 

The setup is quick and easy! The troubleshooting, not so much, but if you do have issues, do not hesitate to reach out to Support for help!

Setting up unread email as an event in the operator console

The TrueSight Infrastructure Management Server connects to the email server periodically using the configured credentials to retrieve emails. These emails are then converted into events. The subject of the email received is updated in the Message (msg) slot of the event and the content of the email is updated in the Detailed Message (mc_long_msg) slot of the event.

Only an email in plain text format or HTML format can be set as an event. For email in HTML format, only the content is extracted and the tags are removed. If an email has both plain text and HTML formats, then the text of the content that appears first in the email is converted as an event.

 

The severity of the event is determined from the content of the email, if it has any of  the following keywords:

  • State: <severity>
  • Severity: <severity>
  • MINOR
  • MAJOR
  • CRITICAL
  • WARNING

 

Only emails that are in the configured folder of the email server are read. The following properties can be configured in the pronet.conf property file:

 

pronet.email2event.mailserver.fqdn=<email server>

pronet.email2event.mailserver.port=143

pronet.email2event.protocol=imap

pronet.email2event.mailserver.username=<user name>

pronet.email2event.mailserver.password=<encrypyted password>

pronet.email2event.mailserver.ssl.enabled=false

pronet.email2event.folder=inbox

pronet.email2event.delete.read.messages=true

pronet.email2event.mailbox.scan.frequency.mins=15

pronet.email2event.enabled=false

pronet.email2event.email.message.body.newline=false

pronet.email2event.default.severity=INFO

 

Where parameter descriptions:

  • pronet.email2event.enabled: Enable email2event feature by setting this value to true. By default, this value is set to false.
  • pronet.email2event.mailserver.port: Default port number is 143. If you want to enable SSL/TLS, change the port number accordingly.
  • pronet.email2event.folder: Create a folder in the email server and assign the folder name to this parameter. Configure rules in the email server to direct the unread emails to this folder. By default, this parameter is set to INBOX.
  • pronet.email2event.email.message.body.newline: Enable the email new line feature by setting this value to true. By default, this value is set to false. When set to false, the entire email message is displayed on the same line. When set to true, the displayed message resembles the email format.
  • pronet.email2event.mailbox.scan.frequency.mins: Specifies the frequency in minutes at which the Infrastructure Management Server scans the mail box. By default, the Infrastructure Management Server scans the mail box in every 15 minutes. Emails that are already read, or are in draft or deleted modes are not considered.
  • pronet.email2event.delete.read.messages: If you set this value to false, the emails that are already read by the server and marked as seen are not deleted from the email server. If you set this value to true, the emails that are already read by the server and marked as seen are deleted from the email server. By default, this value is set to true. All other Multipurpose Internet Mail Extensions (MIME) content such as attachments, images, and so on are ignored.
  • pronet.email2event.mailserver.ssl.enabled: If you set this value to true, the communication between email server to the Infrastructure Management server is in SSL/TLS mode. If you set this value to false, the communication between the email server to the Infrastructure Management server is in plain text mode. By default, this value is set to false.
  • pronet.email2event.imps.version: TLSv1 and 1.2 are supported. You must enable SSL property to set the TLS version property. When you enable the SSL to true, by default the TLS v1.0 is enabled. Using this property, you can set the version to 1.2. For example,pronet.email2event.imps.version=TLSv1.2.

 

Configuring an email as an event

You can configure an email as an event through the command line interface by running the  pw email2event command:

pw email2event

usage:

pw email2event [-y]|[-c]|[-s]|[-e]

The following parameters are available with the pw email2event command :

-y  Encrypts the mailbox password

-c  Configures email as event

-s  Starts scanning email as event

-e  Stops scanning email as event

 

Example

 

  1. Run the following command to encrypt your mail box password. This command will prompt you to enter the mail box password in plain text, and gives the encrypted password as the output.   $pw email2event -y Assign this encrypted password value to the pronet.email2event.mailserver.password property in the pronet.conf file.
  2. Open the pronet.conf file and configure the following properties:

     pronet.email2event.mailserver.fqdn=<f.e.webmail.bmc.com>

     pronet.email2event.mailserver.username=<username>

     pronet.email2event.mailserver.password=<encrypted password>

     pronet.email2event.delete.read.messages=false

     pronet.email2event.mailbox.scan.frequency.mins=5

           pronet.email2event.mailserver.ssl.enabled=true

     pronet.email2event.enabled=true

     pronet.email2event.email.message.body.newline=true

     3. Restart the server.
     $ pw sys start

 

This is one way of creating and handling events within TrueSight. Please note there are some limitations to this functionality. The hope is to grow the capabilities, so let us know your feedback regarding email2event functionality.

 

These are documented limitations:

 

  • A dedicated email account is required.
  • Only IMAP protocol is supported.
  • IMAP protocol is also supported over SSL or TLS.
  • There is no proxy support in connecting to the email server.
  • NTLM authentication is not supported.
  • The configured user account must have read and write permission for the configured folder.
  • Email servers with HTTP access are not supported.
  • The cell process must be running to create events.
  • Events that are created are assigned to priority 5.

 

We also have several Ideas posted to the Communities requesting new functionality within the email2event feature. Please visit the links below and vote up any Idea you feel is relevant to your TrueSight environment.

 

Request to allow email2event adapter to use a shared non-inbox setting

Request to add email2event functionality to allow multiple unique mailboxes to be used

Mechanism to ignore attachment in Email2Event integration

TrueSight to monitor email2Event integration status

Set up email as an event improvements

email2event EWS support (BPPM 9.6 FP2)

SSL or TLS and NTLM should be supported with POP and IMAP email integration adapters


The troubleshooting of email2event is a bit challenging because the connections to various mailservers have different rules, restrictions, etc.. which can cause any one of a number of communication issues. However, BMC does have several knowledge articles which are commonly used for troubleshooting email2event issues.

 

 

Authentication failed with Email2Event

Queries regarding Email2Event feature in TrueSight/ProactiveNet

Tips for Email2Event problems in BPPM

The command 'pw email2event -s' is failing with message 'Unable to decrypt the string'
When configuring TrueSight Infrastructure Management email2event functionality, how many unique mailbox configurations are allowed?

When setting up email2event functionality in TrueSight Infrastructure Management 10.x, 11.x,  is it possible to use a shared email account?

Does the TrueSight Infrastructure Management email2event feature support the use a shared inbox or shared non-inbox folder when managing events?

email2event events are of class MC_CELL_UNDEFINED_CLASS

Email2event feature in TSIM does not include newlines when processing emails in HTML format

Undefined keyword email2event when running pw email2event command

Email2Event stops working if there is an email with null (blank) subject

Email2Event stops working if there is an email in UTF-7 format

Using BPPM/TrueSight's email2event functionality with a Lotus Notes account via imap is failing with "authentication failed"

 

 

If you are seeing issues and need help, please collect the following basic details and open a case for Support

 

  1. Run 'pw email2event' and see if there are any errors (it should just display usage)
  2. Enable email2event debug based on the command below:

          pw debug on -p jserver -s Email2Event

       Enable cell trace as well:

         mcfgtrace -n cellname ALL ALL stderr

       Reproduce the issue and send the pw dump 1 output to Support

    3. Was email2event working beforehand, or whether a problem has just started happening. If it was recent, let Support know what has changed in the environment

    4. Verify that the email server uses POP or IMAP protocols. BPPM/TrueSight server will not communicate with other protocols (e.g. POP3 over SSL)

    5. Login to the POP3 server via telnet. E.g.:

         telnet <IP address> 110

 

        Then run these commands:

         USER <username>

     PASS <password>

 

        Then run:

           STAT

           LIST

 

What do you see?

   6. Confirm that the email password encryption matches pronet.conf's pronet.email2event.mailserver.password entry by running:

         pw email2event -y

 

AMIGO.jpg

 

TrueSight 11.3.02 is here!!!!!… REMINDER - 11.3.02 is a Service Pack Release which requires 11.3.01 to be installed. If you are not on 11.3 yet, be sure to plan to go to 11.3.01 first then apply the 11.3.02 Service Pack.

The BMC Assisted MIGration Offering, or AMIGO, is a program designed to assist our customers in planning and preparing for product upgrades from an older, to a newer supported version.  By engaging with BMC Technical Support Analysts, you will be provided with materials containing guidelines and best practices to aid in compiling your own upgrade plan. An upgrade expert will then review your plan, and offer advice and suggestions to ensure success through proper planning and testing.

The AMIGO program consists of a Starter Phase and a Review Phase.  Each phase is initiated by opening a support case, and ends when the case is closed.

In the Starter Phase, an AMIGO Starter case is opened.  Reference material will be provided and a call with a Technical Support Analyst will take place to discuss the details of your upgrade, and address any questions you may have.  The AMIGO Starter case will be closed, and the next step will be for you to prepare a documented upgrade plan.

In the Review Phase, an AMIGO Review case is opened preferably two weeks prior to a set upgrade date.  A call will be scheduled with an upgrade expert to review your detailed plan, providing feedback and recommendations, along with answers to any outstanding questions.  As needed, a follow up discussion with a Technical Support Analyst may take place for feedback after the upgrade is performed.

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

To get started, please review the details here:

https://docs.bmc.com/docs/TSOperations/113/amigo-checklist-for-truesight-operations-management-814553031.html

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

 

Computer.png

 

New Knowledge Added this month:

 

000168894  BPPM 9.6 compatibility with RedHat Linux 7.6
000168753
How do the Oracle changes affect TrueSight?

000168568 Reducing memory consumption of TSIM by changing garbage collection settings

000168526 Are there any queries for TSPS to show the list of Agent tags and their devices?

000168519 Is there a query to list the TSIM devices and their associated tags?

000168417 API returns 500 internal error when sending a large size JSON package to TSIM on Linux

000168231 Can the Publish-Subscribe API send to another BPPM cell?

000168108 "Unable to copy the folders" seen when running "tssh dump export"

000168499 Error while installing TSIM 11.3.01 installation with non-root user

000168166 After a TSPS upgrade, the csr and idxsrv processes will not start

Filter Blog

By date:
By tag: