Skip navigation
1 2 3 Previous Next

TrueSight Infrastructure Mgmt

85 posts
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

Share This:

Hi everyone, if you have not heard already, BMC has released TrueSight Fix Pack 11.3.02. This is the latest fix pack for TrueSight Operations Management 11.x and BMC would like to encourage you to download and apply it or consider upgrading to the latest code base and applying the fix pack in your environment.

 

What is so different about 11.3.02? Well let me tell you a bit about some of the changes..see below.

 

However, let's get some of the basic details out of the way first:

It is important to note that Fix packs do not contain all of the files that are required for a complete product installation. Before you install the fix pack, you must have previously installed the base version of the product based on the requirements below:


Product Version required

TrueSight Presentation Server 11.3.01
TrueSight Infrastructure Management components 11.3.01
TrueSight App Visibility Manager components 11.3.01
TrueSight IT Data Analytics 11.3.01

 

There is an order for installation of the fix pack which is shown below:

FixPackInstallProcess.png

 

It is important to follow the preparation steps as well as the post installation activities.  Particularly this set of instructions right here :

Before applying a feature pack or fix 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.

 

The actual instructions and details for applying the fix pack can be found here

Applying feature packs or fix packs - Documentation for BMC TrueSight Operations Management 11.3 - BMC Documentation

 

If you are interested in upgrading from an earlier version of TrueSight Operations Management, please see the details at the link below

Upgrading to 11.3.02

upgrade.png

 

Java Enhancements

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.

 

Additional Remedy SSO authentication types

Configure additional Remedy SSO authentication types
You can now configure the TrueSight Presentation Server with the following Remedy Single Sign-On authentication types:
• Kerberos authentication
• Certificate-based authentication

For more information see Configuring user authentication for the Presentation Server in Remedy SSO - Documentation for BMC TrueSight Presentation…

 

TrueSight Presentation Server and Infrastructure Management enhancements

  • Noise reduction metrics

Noise reduction enables you to avoid looking at endless volumes of incoming events and focus on resolving important events more efficiently.

The noise reduction metrics help you understand the volume and percentage of events received, stored, and suppressed. Events are suppressed based on rules defined at the cell level resulting in reduced operational noise. This capability works across event sources including Infrastructure Management servers and associated remote cells and across historical and streaming data.

For more information, see  Viewing and understanding noise reduction metrics.

 

  • Create and enable a base user group

You can now create a user group in Remedy SSO and manually enable it as a base user group. This is not enabled by default. After you manually enable the base user group, any use belonging to an external identity provider such as LDAP or SAML without an associated user group in the Remedy SSO can now log in to the TrueSight console.

For more information, see Default users and user groups - Documentation for BMC TrueSight Presentation Server 11.3 - BMC Documentation

 

  • Orchestration actions for events

Run out-of-the-box Orchestration actions from recurring events with known remediation steps. This capability reduces the Mean Time to Repair (MTTR) and errors and delays associated with using manual methods for remediating events. This release enables you to easily integrate TrueSight Presentation Server by adding TrueSight Orchestration as a component. After the integration, you can initiate Orchestration actions from the relevant events.

For more information, see  Using Orchestration actions to enable triage and remediation of events

  • tssh command to check for component port availability

The tssh component portcheck command is used to check the availability of a component port in the Presentation Server.

For more information, see Checking a component port availability from the Presentation Server.

  • tssh command to reinitialize events in the Presentation Server

The tssh event reinitialize command reinitializes events in the Presentation Server. If you modify an existing custom event class definition in the Infrastructure Management server, this command is helpful to view the modified events on the TrueSight console.
For more information, see Reinitializing events in the Presentation Server.

  • tssh and pw commands to create and import certificates (Personally, one of my favorite enhancements - we have all had so much fun with certificates in the past! BMC is trying to make the certificate creation/installation much easier- please do provide feedback regarding this and all new features please!)

TrueSight Presentation Server and TrueSight Infrastructure Management server provide a set of CLI commands to create, import, list, delete, and verify the certificates easily quickly. You enter a few basic details, and the certificates are created and imported with minimal user intervention.
For more information, see Implementing certificates in TrueSight Operations Management using scripts.

 

BMC Service Resolution integration enhancements

The following enhancements and changes are available for the TrueSight Infrastructure Management 11.3.02 and BMC Service Resolution 3.5 integration:

  • The BMC Service Resolution integration with Remedy supports only a limited number of temporary fields (10) that can be used for creating incidents based on events in Infrastructure Management. With Infrastructure Management 11.3.02, extend your system by configuring custom fields in addition to the default 10 fields.

For more information, see Configuring additional fields to create incidents with custom information.

  • You can import BMC Service Resolution certificates into TrueSight Infrastructure Management by running the pw certificate import command.

For more information, see  Creating and importing certificates in TrueSight Infrastructure Management.

  • In addition to the TrueSight.log, the logs related to one-click validation are available under the /usr/pw/pronto/logs/bsroneclick.log. Also, with Infrastructure Management 11.3.02, an out-of-the-box propagation policy is automatically created. Each time the one-click validation is run, the policy is enabled and then disabled on completion of the validation.

For more information, see Validating integrations.

  • The mapping files (DefaultMapping.map, outage.map, RemedyForceDefaultMapping.map, and IBRSD.conf) are automatically backed up.

For more information, see Extending your system capabilities.

  • Additional incidents are created when the severity value changes to a lower value.

For more information, see Configuring SIM Notification Registry parameters in the cell.

  • Authentication support for running commands via the Agent Query Tool

With this release, you can configure authentication for all users irrespective of their roles or permissions to run PSL commands via the Agent Query Tool. After you enable authentication,all users will be required to provide user credentials used for installing PATROL Agent before they can run the queries. You can run PSL commands via the Agent Query Tool from both,  the Infrastructure Management Operator Console and the Presentation Server.

For more information, see the following links:

    Working with PATROL Agents through the operator console
    Performing actions on a PATROL Agent

 

TrueSight App Visibility and Synthetic Configuration enhancements

  • Synthetic Blackouts and Time Frames

You now have additional options to configure and manage Synthetic Blackouts and Synthetic Time Frames. The existing Blackout configurations are migrated automatically when you apply the 11.3.02 service pack.
For more information, see the following topics:

   Upgrading Synthetic Blackouts
   Configuring and managing synthetic blackouts
   Managing synthetic configurations with APIs

  • Migrating TM ART Monitor Exclusions

You can now migrate TM ART Monitor Exclusions to the new Synthetic Blackouts.

For more information, see Migrating synthetic configurations.

  • Execution Plan Schedule

You can now set the Initial Execution Schedule from the Execution Plan Schedule > Advanced Settings. The Initial Execution Schedule in Execution Plan can be used to start the initialscript run in one of the following cases:     Execution Plan creation/Execution Plan updates/TEA Agent restart

For more information, see Editing an application's synthetic settings

  • Reclassifying Silk errors in the TEA Agent

You can now reclassify the list of default Synthetic Monitor Accuracy, Execution, and Availability errors produced by Silk Engine in the TEA Agent by editing the App Visibility collector.properties file.

For more information, see Reclassifying Synthetic Monitor Execution errors and Accuracy errors as Availability errors.

  • BDM (AJAX) scripting supported on Firefox and Chrome

Silk Performer BDM scripts are now supported on Firefox and Chrome browsers.

For more information, see Micro Focus Community link.

  • Script to automatically restart HA nodes

You can now use the tsav-check.sh script and set up a Crontab job to automatically restart the TrueSight App Visibility Manager HA nodes running on the Red Hat Enterprise Linux.

For more information, see Standby node in HA stops and does not restart.

  • HTTPS proxy support for URLChecker script

You can now use an HTTPS proxy parameter with the URLChecker script.

For more information, see Using scripts to simulate end-user transactions.

  • Locale options for notification display

For Synthetic Metric Rules, you can now set the event notifications to display in one of the three locale options: English, Chinese (Mandarin), and Deutsche (German). The default locale is English.

For more information, see Managing App Visibility notification channels.


IT Data Analytics enhancements

  • IT Data Analytics Launch Context

You can now set the IT Data Analytics Launch Context from the TrueSight console user preferences. The following options are available:

Launch Analyze Data – Displays analyzed events. Enabled by default and Launch Search – Displays logs and events

For more information, see IT Data Analytics Launch Context.

  • Wizard-based installation for service packs

You can now use a wizard to apply the IT Data Analytics service pack.
For more information, see Applying feature packs or fix packs on IT Data Analytics using the wizard.

  • Deploying Search components in the HA mode

You can now deploy multiple search components in the HA mode without any additional configurations.
For more information, see Deploying multiple search components in a HA mode.

  • calc search command

You can now use the calc search command to perform mathematical operations on extracted fields.
For more information, see calc search command.


Usability improvements

  • Enhanced mmigrate utility

The mmigrate utility now merges .load files in a predefined sequence and retains the sequence of the custom and the standard .load files. This capability is useful when you are upgrading from 10.7 or later versions.
For more information, see Using the mmigrate utility.

  • New event to indicate circular relationship in a service model

The impact status of a service model is not accurately computed if it has a circular relationship. A cell creates a special internal event to indicate that a service model contains a circular relationship. If you are using BMC Atrium CMDB as a source of service model data, you can remove the circular relationship by using BMC Impact Model Designer.
For more information, see Troubleshooting circular relationship in service models.

Documentation enhancements

  • Enhanced feature pack and fix pack installation documentation

The TrueSight Operations Management feature pack and fix pack installation documentation is redesigned for ease of use.

The highlights are:

  • A sequenced path to apply the feature pack or fix pack.
  • Better navigational assistance with the “Where you are” map and information about the next step in the process.
  • Every installation procedure is designed as an end-to-end topic for better readability and to avoid page switching.

For more information, see Applying feature packs or fix packs

  • Troubleshooting documentation for component registration errors

Troubleshoot component registration errors using the newly-added documentation.
For more information, see Troubleshooting component registration errors.

 

Where do I get the fix 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:

    TrueSight Presentation Server Version 11.3.02
    TrueSight Infrastructure Management Version 11.3.02
    TrueSight App Visibility Manager Version 11.3.02
    TrueSight IT Data Analytics Version 11.3.02

 

Installing the fix pack

Warning: Before applying this fix 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. On some Windows computers, after downloading the fix pack installation files from the BMC Electronic Product Distribution

(EPD) site, you may be required to unblock the .zip files before extracting them.

    Right-click the downloaded .zip file and select Properties.
    On the General tab, select Unblock.
    Click OK to save changes and then extract the installation files.

 

To install Fix Pack 11.3.02 for TrueSight Operations Management version 11.3.01, follow the sequence at Applying feature packs or fix packs .

 

There is preparation involved, so be sure to read the details before installing, but the basic sequence is as follows:

Complete preparation for fix pack installation - Preparing to apply feature packs or fix packs on the TrueSight Operations Management solution - Documentation for BMC Tr…
Install on Presentation server - details are found here - Applying feature packs or fix packs - Documentation for BMC TrueSight Operations Management 11.3 - BMC Documentation
Install on Infrastructure Management
Phase A – Install on the Integration Service and Remote Cell using one of these options
Phase B – Install on the Infrastructure Management server using one of these options
Install on App Visibility Manager
Install on IT Data Analytics
Complete the post-installation activities (optional) - Replacing Oracle JRE with Azul 8 Java - Documentation for BMC TrueSight Operations Management 11.3 - BMC Documentation

 

If you have any questions or run into any issues with the 11.3.02 Fix Pack, please contact BMC Support for further assistance.

 

AMIGO.jpg

Now that 11.3.02 has been released, it is the perfect time to look into our free AMIGO offering!

 

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.

 

Knowledge Base.png

 

Knowledge Base – How often do you use the BMC Knowledge Base to search for issues and fixes? Are you frustrated with trying to find the correct results for the products you are using?

Would you like to search the BMC Support Knowledge Base and only see results for just TrueSight/ProactiveNet or if you using these product predecessors, see results for just BEM/SIEM? If so, then take advantage of our pre-filtered search links:

 

Pre-filtered for TrueSight/ProactiveNet

Pre-filtered for BEM/SIEM

NOTE: You will need to be already logged into BMC Support Central for these URL's to work correctly

 

 

Computer.png

 

New Knowledge Added over the last month:

 

 

000165050 TSPS shows a timeout page after applying certificates

000165051 Is there a performance concern when stacking host specific policies using the same precedence in TrueSight Presentation Server 10.x, 11.x?

000165090 TSIM 10.5 not connecting to TSPS after upgrading TSPS to 11.0

000165128 Recently removed KMs from BPPM 9.6 monitoring are not reflected immediately in the license report counter

000165176 How to configure which cells are displayed on the TSIM Admin Console

000166230 "Full Repository with Predefined Packages and Policies" is greyed out when attempting to import a repository into the TSPS

000165235 Event Propagation not working from remote cell to TSIM cell

000165687 SNMPv3 - Error on UDP channel: Read Error'

000165890 How to forward PATROL events to TSIM server cell via Integration Service?

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


Feedback.jpg

Feedback Request:

We want your 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:

Are you getting the most from your TrueSight implementation? Are you in need of more best practice recommendations? Are you interested in real world examples of how TrueSight is implemented? If you answered YES to any of those questions, look no further. BMC has just what you need. Have you heard of the TrueSight Webinar series? If not, you are missing out. The TrueSight Webinar series arranged by the magnificent Seth Paskin is a series designed to help TrueSight users make the most of their TrueSight environment.  The Webinar series has been around for some time now and we hope it continues to help meet your TrueSight needs. The series does not just cover TrueSight Operations Management. There are topics for various suite components such as TrueSight Server Automation, TrueSight Capacity, TrueSight Orchestration, and even TrueSight Smart Reporting.

 

There was even a Webinar session today!!! Do not worry, if you missed it, you can view the recording here:

Recording: Load Balancing in TrueSight Operations Management  - Load Balancing in TrueSight Operations Management

 

Webinars take place every other Wednesday at 10am Central US time. Webinars are hosted on WebEx. Links to RSVP, add to calendar and get more information can be found by clicking on the topic title in the table on the calendar page - TrueSight Best Practices Webinar Calendar

 

The calendar has the links to all previous sessions as well as details about future sessions. For example, you do not want to miss March and April sessions, where we have a lot of our Platinum Engineers presenting hot topics for various components. These sessions will help improve your overall knowledge of the specific topic and if you have any new topics you can share recommendations with the Community as well.

 

3/13/2019Investigate Tool in TrueSight Capacity OptimizationDima Seliverstov
3/27/2019Monitoring Java Memory Utilization in TrueSight Operations MgmtBryan Meranda
4/10/2019Migrating PCM to CMA using Conversion Scripts for TrueSight Operations MgmtJon Brent Fournet
4/24/2019Scalability vs. Availability in TrueSight OrchestrationKapil Dingore
Sumeet Hemnani

 

 

Past topics have included:

 

TrueSight Operations Management

Heartbeat Monitoring in TrueSight Operations Mgmt

Moving Beyond Dynamic Baselines in TrueSight Operations Mgmt

Synthetic Metric Rules in TrueSight Operations Mgmt

Smart Reporting in TrueSight Operations Mgmt 11.3.x

 

TrueSight Capacity

Investigate Tool

Custom Views

Agent based collection

Migrating Custom Views from TrueSight Capacity Optimization from 10.x to 11.x

 

TrueSight Server Automation

Smart groups

Live Reporting

 

Not on the TrueSight Suite just yet, or perhaps you are using an earlier version? BMC has you covered. The Webinar series does date back to BMC ProactiveNet Performance Management and TrueSight 10.x. Click this link to see these sessions - Connect with BMC TrueSight Operations Management v10.0 Best Practices Webinar Series

 

There are endless possibilities for topics, so if you have an area where you want to see more in-depth examples or best practice recommendations, please let us know. These Community Webinars are designed to help you get the most out of TrueSight. So what are you waiting for? Sign up for an upcoming session today!

 

 

 

 

AMIGO.jpg

 

TrueSight 11.3.01 is here!!!!!…

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:

 

 

000164282 How to generate a list of Patrol Agents within the TrueSight Presentation Server database with policies applied

000164118 Timeout when trying to push TSPS CMA packages

000164647 TrueSight Infrastructure Management 10.x, 11.x Support Oracle 18c for the TSIM database

000164465 msend utility on Fedora 28+ says libnsl.so.1 => not found

000164421 Event Rule Administration showing Rule(s) status as ‘None’

000164146 TSPS 11.x - Login Forbidden from accessing 'Integrations' and 'Remedy SSO' Administration options

000163701 Why would one not receive email from the TrueSight/BPPM server with subject ‘x BMC TrueSight/ProactiveNet Process is not running on <host> when the TSIM process is stopped

000164978 Error in the CMAKMPush.log when attempting to deploy a PATROL Agent package in TSPS 11.3.01 - Reason Missing PATROL Agent's home path for mytestserver.com, can not recover as Agent Version is less than 10.7.00, current Agent version : V10.0.00i

000165050 TSPS shows a timeout page after applying certificates

000165051 Is there a performance concern when stacking host specific policies using the same precedence in TrueSight Presentation Server 10.x, 11.x?

Feedback.jpg

 

Feedback Request:

We’re back with our monthly blog and we’re 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:

BMC announces its brand-new version of KM to monitor the Oracle Enterprise Database in most simplified and user-friendly way.

 

While monitoring your Oracle Databases, are you worried about:

  • providing sys credentials user,
  • the foot prints left by monitoring tool,
  • the oracle objects created by monitoring tool,
  • restricting the privileges for monitoring user,
  • and the complexity of configuration?

 

We have heard your concerns and are ready with the solution: “BMC PATROL for Oracle Enterprise Database”.

 

Here are the great features implemented in the first release of PATROL for Oracle Enterprise Database.

  1. Certify Connection using Oracle JDBC connector.
  2. Basic configuration details
  3. Minimal required permissions for the DB monitoring user
  4. Positive and Negative enriched messaging, possible corrective actions
  5. OOTB default configuration settings
  6. Single monitoring user for Data Guard environments.
  7. OS user is no longer required for monitoring
  8. No longer Creating Oracle objects in monitor user schema
  9. SQL Custom Queries for application oriented usage
  10. High level view for Data Guard

 

You can find more details about this new KM at https://docs.bmc.com/docs/display/OE10

 

Here are some short how to videos we have created around this KM:

 

If you get any issues while installing, configuring or using this new KM, feel free to open a support case with BMC (link), we would be glad to assist you.

 

And here is an Article and video that covers how to collect Oracle KM debug, if you need to work with BMC Support.

Oracle Knowledge Module Debug using TrueSight

https://youtu.be/mXiBTe3U7rw

 

Thank you,

BMC Software

Share This:

We want your feedback; do you use queries against the TSPS database? If so, are they helpful? What are your go to queries?

 

While Support does not write queries for customers, there have been some occasions where we have used queries which have been developed by our engineers to help pull data and details from the databases using within the TrueSight Presentation Server PostGres database. These queries have been used primarily for troubleshooting issues and if you haven not worked with Dinesh Goel or Prashant Joshi you are missing out, these gentleman are out go to guys for all things database.

Queries can be used to collect specific data and based on some of the cases open in the last month, there has been an increase in requests for details which may be a bit cumbersome to pull from the GUI or other sources. For example, there have been several cases raised about which policies are applied to which Agents, which thresholds have been set where, and requests of a similar nature. Could there be an easier way to get this information? How can this be done?

 

Through the database! Go directly to the source! It is quick and easy and will give you the details of what you need. The hardest part would be figuring out which tables store which information, which BMC could probably create a whole class on, but for the purpose of this post, we will keep it simple. While we do not recommend using queries for every request and Support will not write a query for you, we would like you to  take this opportunity to share some of the queries which help you navigate the TSPS world.

I will share some of the queries Support has provided recently through case work with customers and engineers. These queries are not official, no further documentation is available, they are straight database queries - simple select statements to pull some of the more popular details out of the database. I would like to give special thanks to Technical Support Professionals Ellen Coleman and @Lee Foster for contributing some of the scripts they use for this post.

 

A few items to note when attempting TSPS scripts:

 

•    Be sure you have a working backup of the TSPS base before you run anything – the queries are usually just select statements but we don’t want to take any chances

•    These queries work with TrueSight 10.x and 11.x versions

•    These queries can be run on Windows or UNIX/Linux machines – Note: On Linux, you must source s the .tmprofile in /usr/pw/pronto/bin before the scripts will work

•    The psql script/exe lives in /opt/bmc/TrueSightPServer/truesightpserver/modules/pgsql/bin OR "%TRUESIGHTPSERVER_HOME%\truesightpserver\modules\pgsql\bin\" where -U <dbusername>-d <databasename> -c <command to be executed>

•    I would recommend piping the output to a file for most of these queries

•    Run these queries at your own convenience/risk and note that not all these queries have been tested against each version of the TSPS database

 

Example for Windows:

Go to %TRUESIGHTPSERVER_HOME%\truesightpserver\modules\pgsql\bin\" then run the command below from the command prompt

psql -U <dbUser> -d truesight -c "select a.patrolagentid,a.policiesconsidered,b.hostname from patrolagent_pcfgtl a left outer join patrolagent_details b on a.patrolagentid = b.patrolagentid order by b.patrolagentid"

 

Example for Linux

Source .tmprofile in /usr/pw/pronto/bin cd to /opt/bmc/TrueSightPServer/truesightpserver/modules/pgsql/bin

./psql -U <dbUser> -d truesight -c "select a.patrolagentid,a.policiesconsidered,b.hostname from patrolagent_pcfgtl a left outer join patrolagent_details b on a.patrolagentid = b.patrolagentid order by b.patrolagentid"

 

 

Query to list which  policies are applied to which Agents

psql -U <dbUser> -d truesight -c "select a.patrolagentid,a.policiesconsidered,b.hostname from patrolagent_pcfgtl a left outer join patrolagent_details b on a.patrolagentid = b.patrolagentid order by b.patrolagentid"

 

Query to list active policies

psql -U <dbUser> -d truesight -c "select oname from pepolicy where lifecycleStage='production' and poltype_id='uuid:policyType:3' order by oname"

 

Query to list servers which use a particular policy

psql -U <dbUser> -d truesight -c "select hostname from patrolagent_details where lower(policiesapplied) like '%<POLICY_NAME>%' order by hostname"

Examples/Clarification of the command:

With “lower” enter the policy name in all lower case:

 

psql -U <dbUser> -d truesight -c "select hostname from patrolagent_details where lower(policiesapplied) like '%linuxosdefault%' order by hostname"

Or no “lower” and Policy name is case sensitive.

psql -U tspsuser -d truesight -c "select hostname from patrolagent_details where (policiesapplied) like '%LinuxOSDefault%' order by hostname"

 

 

Query to list  policy names of a certain type

psql -U <dbUser> -d truesight -c "select oname from pepolicy where poltype_id = 'uuid:policyType:3'"

 

- 'uuid:policyType:3' are Monitoring policies

- 'uuid:policyType:4' are Staging policies

- 'uuid:policyType:5' are Blackout policies

 

 

Query to list polices per Patrol Agent

psql -U <dbUpser> -d truesight -c  "select * from patrolagent_details" > /tmp/PA.txt - List of Policies per Patrol Agent

 

 

Query to pull monitored host data from the Agent

psql -U <dbUser> -d truesight -c "select dnsname from device where dnsname NOT IN (select trim(hostname) from patrolagent_details where hostname IS NOT NULL)" truesight

**Note: Make sure dnsname and hostname are both either short name or fqdn.

 

 

Query to view threshold details for a specific parameter or for the full table

----specific parameter.txt

psql -U <dbuser> -d truesight -c "select * from template_thresholds where appclass='SWAP' and paramname=' SWPSwapUsedPercent' and  severity='CRITICAL' AND thresholdtype='ABSOLUTE' AND comparator='GT' AND tenant='bmcrealm'"  > C:\specific.txt

 

----full_table.txt

psql -U <dbuser> -d truesight -c "select * from template_thresholds" > C:\full_table.txt

 

 

Query to view deployable packages

psql -U <dbuser> -d truesight -c "SELECT * from create_deployable_package_xml"

 

 

Query to get a list of all PATROL Agents with an ISN in a file on TSPS

psql -U <dbUser> -d <dbname> -c "select hostname, patrolagentport, proxyhostname from patrolagent_details pa, proxy_details proxy where pa.proxyid = proxy.proxyid) to <file_location_name> WITH Delimiter ','"

 

**Note <file_location_name> is the parameter to provide file having details of PATROL Agents with ISN . For e.g. "C:\tableOut.txt"

    <dbUser> is the DB user that you provided during TrueSight Presentation Server installation

 

Query to get a list of PATROL Agents in a file

psql -U <dbUser> -d <dbname> -c "select serverid, moinstanceid,hostname from patrolagent_details)" > PatrolagentWithInstanceId.txt

 

Query to show proxy details

psql -U <dbuser> -d truesight -c "select * from proxy_details"

                 

Query to show a list of devices

psql -U <dbuser> -d truesight -c "SELECT * FROM device"

 

Query to list user preferences

psql -U <dbUser> -d truesight -c "select * from user_preference" > c:\temp\user_preference.txt

 

Query to list Agents where policies failed to apply

psql -U <dbUser> -d <dbname> -c "select serverid, moinstanceid, hostname, policiesapplied,policieslastappliedtime,policiesfailedtoapply,policiesfailedtoapplytime from patrolagent_details"  > PatrolAgentDump.txt

 

Query to list group details

psql -U <dbUser> -d <dbname> -c "select * from device)" > 'c:\temp\devicecontents.txt'

 

Or -c "select * from groupdesc" > 'c:\temp\groupdesc.txt'

Or -c "select * from grouprelationship" > 'c:\temp\grouprelationship.txt'

Or -c "select * from groupcontents" > 'c:\temp\groupcontents.txt'     

 

 

AMIGO.jpg

 

TrueSight 11.3.01 is here!!!!!

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:

000162720  Event shows incorrect status in TSPS 11.3.01 console but when looking at the event details the correct status is shown

 

000162570 The 'Allow Infrastructure Management PATROL repository management' permission used in the Unified Administrator role does not work properly in TrueSight 10.7

 

000162567  Deployment of TrueSight Presentation server packages fail when using HTTP vs HTTPS

 

000163287  Can you change Patrol Agent passwords via TSPS?

 

000163086  How to sync all connected Patrol Agents en masse

 

000162923 How to obtain from the TSPS database a list of PATROL Agents that have a specific infrastructure policy applied

 

000162957 Incorrect calculation for the SLO in TrueSight for the last month

 

000163153  When configuring TrueSight Infrastructure Management email2event functionality, how many unique mailbox configurations are allowed

 

000163107  How does one change the RSSO hostname as configured in the TrueSight Presentation Server 11. x configuration screen

 

000162935 Unable to import the solutions/KMs into the TrueSight Presentation Server 10.x, 11.x repository - Java.io.IOException: Unable to delete file: /tmp/bmc_products/install.ctl seen in the session.stdout log

Share This:

Over time, as your TrueSight grows in your environment, this growth can lead to performance issues and extra events. TrueSight sends self-monitoring events to users when their environments are growing too large for the existing configuration. The effort is made to provide a TrueSight Administrator with the details of how many devices, monitors, instances, and events are being monitored. When TrueSight has reached 50% of the upper limit, a warning event is sent out and once TrueSight has reached 90% of the upper limit on the parameters being monitored, a self-monitoring event is sent out.

 

Users don’t want to see this event - self-monitoring event: "No. of instances is above 100% of max limit 250000 on Infrastructure Management Server." This means you have hit a limit within TrueSight and you must clean up the instances which may not be necessary. If they are all necessary, a second setup may be needed to manage the load. TrueSight uses the following thresholds to monitor the count of devices, monitors, and attributes. Once these thresholds have reached 50% of the upper limit then TrueSight will notify users via an event so that the TrueSight admin is aware of the issue.

 

These values are found in the pronet.conf under the TSIM/pw/pronto/conf folder

 

pronet.deployment.selfmonitor.device.threshold.min=50

pronet.deployment.selfmonitor.device.threshold.max=90

 

pronet.deployment.selfmonitor.instance.threshold.min=50

pronet.deployment.selfmonitor.instance.threshold.max=90

 

pronet.deployment.selfmonitor.attribute.threshold.min=50

pronet.deployment.selfmonitor.attribute.threshold.max=90

 

pronet.deployment.selfmonitor.event.threshold.min=50

pronet.deployment.selfmonitor.event.threshold.max=90

 

There is a property available to enable/disable this functionality using a True and False value.

pronet.deployment.selfmonitor.feature.enable=True
BMC does not recommend disabling this property as it is important to know when the application is reaching its limits. The details above represent the approach to enhance self-monitoring so an alarm is generated if the number of monitored instances or attributes is approaching the upper limit for the environment. Based on the size configuration setting in the TSIM Server

Small environment

Size of jserver default (2 GB)

Size of rate default (2 GB)

Size of agent controller default (2 GB)


Medium environment
Size of jserver default (4 GB)
Size of rate default (4 GB)
Size of agent controller default (4 GB)

 

Large environment

Size of jserver default (10 GB)

Size of rate default (6 GB)

Size of agent controller default (7 GB)

 

TrueSight will read the configuration setting from TSIM server and identify a Small, Medium, or Large deployment, then based on a scheduled task which runs hourly (configurable) TrueSight will validate the device, instance, and attribute counts and will trigger the events once it reaches 90%(configurable) of the max limit.

 

Note: The values above are not absolute, Support has had to tune environments specifically based on the components used, the number of items being monitored, and the hardware specifications. There are many times when Support will need to tune the values of the jserver, rate, or agent controller based on what the system is running already.

 

There are several documentation pages which reference the sizing and limitations within TrueSight. The values are presented for the TrueSight Administrator to know which size of environment is needed. During the start of a TrueSight rollout, it may start off as a small environment, but over time it may grow. The idea is that users should plan for the size they think they may grow into.  This is not always possible, so for that, we do have tuning options to take you from a small to medium sized environment or a medium to large environment, but once you reach the maximum on the large environment, you will need to look at what is being monitored and whether some of the instances are not needed. Think of it as a built-in housekeeping situation.

 

Many times, you want to monitor everything up front, you want to see the nice reports and the total number of instances and parameters which can be monitored, but over time, you learn more about your systems and their performance and perhaps some parameters or some instances are no longer needed.  When you run into the self-monitoring event, it is time to review the setup and see which instances stay and which can be let go.

 

There are sizing guidelines for each TrueSight Component, so it can get complicated at times, but the best thing to do is to size the Presentation server, and then size the Infrastructure Management server, the Integration Service server(s) and then take a look at the data and event sizing guidelines as well. It really is enough to make your head spin!

 

Here are details the documentation provides to help make sizing a bit easier:

TSPSScaling.png

These details are in the online documentation under the Presentation Server sizing section

 

The hardest part of sizing is on the TSIM server. There are many more considerations in TSIM to account for. Here is the quick link to the start of that documentation - Infrastructure Management Server general sizing guidelines

 

A single large BMC TrueSight Infrastructure Management Server host computer scales to support the following maximum values. The values include all processes and the event management cell.

Data for 1.7 Million performance parameters:

  • 20,000 devices
  • 250,000 monitored instance
  • 3 days of raw data
  • 3 months of rate data
  • 40,000 intelligent events per day
  • 350,000 external events per day


These values are all independent so if you reach one, not all, but one of these values, you will receive the self-monitoring event indicating a sizing issue. This sizing is for a 64-bit host with 8 CPUs and 32 GB of RAM. Do not try to exceed 250,000 monitor instances or 1,700,000 attributes on a single Infrastructure Management Server host. Additional CPU and memory do not help to scale beyond these values. You will see performance issues as well as odd, unexplained behavior because when a system is overloaded, nothing really works correctly. A restart may help momentarily, but once the monitoring limits are breached, all bets are off and performance tanks quickly.

 

For 11.3.01 in some environments, the Infrastructure Management database requires more storage space than previous versions. The data collection rate has been increased, data was collected every 5 minutes but now the data collected by the BMC PATROL Agent is streamed to the BMC TrueSight Infrastructure Management Server and many parameters are collected every minute.  This means you must give the database the space I needs to for the increased data stream. You must allocate 600 GB of storage (100 GB for the Infrastructure Management Server + 500 GB for the database) in a large implementation.

 

We also need to consider the various components and their sizing:

Sizing charts and guidelines for event and impact management

Sizing charts and guidelines for data and event management environments

Sizing chart and guidelines for the Cloud Lifecycle Management integration

Sizing the VMware vCloud Director integration

 

Let’s not forget about the Integration Service, the overlooked component when it comes to sizing. It is important to have it properly sized.

A single large Integration Service host scales to support the following maximum values. These values include the Integration Service and the event management cell.

    Data for 1.7 million performance parameters

  • 900 PATROL Agents
  • 50,000 monitored instances
  • 25 events per second

 

Again, these values are independent, it does not take all values to trigger a self-monitoring event, it just takes one. Therefore, TrueSight documentation offers the considerations below for sizing the Integration Service:

· A 64-bit Integration Service host machine with 2 CPUs and 2 GB RAM can scale up to 500 PATROL Agents.

· Allocate a separate Integration Service for each remote network.

· A 64-bit Integration Service host with 4 CPUs and 8 GB RAM can scale up to 900 PATROL Agents.

· Minimize the number of Integration Service that you use to collect data from BMC PATROL Agents.

· Ensure that the Infrastructure Management Central and Child Servers have user access to the Integration Service computers.

· Deploy an Integration Service on each network where BMC PATROL Agents are located, and distribute BMC PATROL Agents on the Integration Services so that the load on the service does not exceed the suggested values.

· The load can be distributed across one or more Integration Services by keeping the total load on the server constant as per the deployment type. You can configure a maximum of 25 Integration Services.

· You can configure a maximum of 500 PATROL Agents per Integration Service in a small deployment and 900 in medium and large deployments.

 

 

Some of the general tips for all types of deployments

· Install the BMC TrueSight Infrastructure Management Server and Integration Service on separate computers.

· Distribute event correlation, de-duplication, and normalization on Infrastructure Management remote cells.

· (SAP SQL Anywhere only) To improve I/O throughput, use separate disks for the operating systems on which the BMC TrueSight Infrastructure Management Server and the database are deployed. Ensure that each disk has its own disk controllers.

· Distribute data collection on Integration Services so that the server is dedicated to the primary server processes (analytical engine, object cache, and agent controller). The Self-Monitoring Service, which is automatically installed on the BMC TrueSight Infrastructure Management Server, collects metrics only about the performance of the BMC TrueSight Infrastructure Management Server.

· If you expect the total number of attributes for the environment to grow to 750,000 attributes, use a large-environment deployment so that the system can accommodate growth smoothly.

 

Overall, when you size the environment, Support recommends planning for growth. Support has seen many cases over the past year where the environment was originally configured for small or medium and by the end of the year, the TrueSight implementation is already over the large sized capacity and performance is at a standstill. Please do review the sizing and hardware requirements as they are important in an ever growing monitoring environment.

 

If you have any sizing or tuning concerns, please log a case with Support for further assistance.

 

 

Did you miss one of our TrueSight Webinars this year?

Check out past Webinar recordings!!! - TrueSight Best Practices Webinar Calendar

 

Do you have questions about the new TrueSight Smart Reporting option? Take a look at this FAQ to see if helps - TrueSight Smart Reporting details

 

AMIGO.jpg

 

 

 

TrueSight 11.3.01 is here!!!!!…

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:

 

000162392 How to auto-close event in TrueSight when the corresponding incident is resolved in Remedy

 

000162132 Slow response in creating or editing TSPS infrastructure policies

 

000161854 When creating a package to upgrade PATROL Agent servers what happens if you leave the Agent TAG and Integration Service fields blank?

 

000161739 Is it recommended to install ASSO and RSSO on the same server in a TrueSight environment?

 

000161592 "Cannot validate argument on parameter 'Group'" seen when attempting to run GenericService_SDIG.ps1

 

000161584 Unable to remove an ISN under Manage Devices in TSPS

 

000162410 Policy is not being applied against all PATROL Agents that are defined in the Agent Selection Criteria

 

000162243 During fail over to Disaster Recovery site the TrueSight Presentation Server in the DR remains in standby mode

 

000162162 Cross Launch From TSPS to Truesight Smart Reporting is Throwing Session Timeout error

 

000162040 Propagation policy does not work after being edited

 

000161956 The publishing server is not starting properly. The psstat returns "Connection initialization timeout expired. Please verify if the Publishing Server and JBoss jms service are up  and running."

 

 

 

 

 

 

 

 

Share This:

If you are using TrueSight version 11.0.00 we encourage you to update to Fix Pack 3 which was released earlier this month. There are a number of fixes for issues encountered after the previous fix packs. The good thing is that the fix packs are cumulative and will contain all the fixes from FP1 and FP2. We wanted to be sure to spread the word with possible freezes on installations before the end of the year, so we wanted to share the details of Fix Pack 3 in the Community!

 

 

NOTE:

Fix packs do not contain all of the files that are required for a complete product installation. Before you install the fix pack, you must have previously installed the base version of the product. Please ensure you have the base version 11.0.00 installed.

110FP3requirements.png

Fix Pack 3 bring us a few new enhancements to note:

 

 

Enhanced Presentation Server logging

 

TrueSight Presentation Server now supports the following commands:

 

    tssh logger debug on -n all

  tssh logger debug off -n all

 

This allows users to blanket the debug options, rather than enabling/disabling loggers individually.

For more information, see  Enabling logging of the Presentation Server

 

Enhanced KB migration while upgrading TrueSight Infrastructure Management

 

You can upgrade TrueSight Infrastructure Management even if you have not migrated your KB customization. You must ensure that the POMEnabled property in the mcell.conf file is set to Yes.

You would probably want to migrate the custom KB, so to do that, please use the following;

To migrate the KBs for custom cells, perform the following steps:

 

    Follow the instructions at Using the mmigrate utility.

    Compile and restart the custom cells. For more information, see Compiling a Knowledge Base - mccomp

See also -  Applying feature packs or fix packs on the Infrastructure Management server .

 

Enhanced device consolidation

 

Devices can now be consolidated by using aliases and short names.

If the same device is monitored and discovered by multiple PATROL Agents, then each PATROL Agent informs the InfrastructureManagement Server that it has discovered the device as shown in the following figure.

device_consolidation.png

However, the Infrastructure Management Server is able to detect that the same device has been discovered by various PATROL Agents. Therefore, in the All Devices page, If the same device has been discovered by multiple PATROL Agents, Infrastructure Management does not display the device each time it is discovered. Instead, it displays the device only once in the Device Name column. The Agent column uses the count mechanism to display the number of agents that have discovered the device.

 

You can click the count link to view all the agents that have discovered the device.

The new feature allows more flexibility in consolidation.

 

For more information, see Consolidating devices in the administrator console

 

New tssh command to reinitialize events in the Presentation Server

 

When you modify an existing custom event class definition in the Infrastructure Management server, you need to reinitialize the events on the Presentation Server so that it displays the latest modified events data from the connected Infrastructure Management server. you can run the tssh event reinitialize command on the Presentation Server to reinitialize the events data. When you run this command, latest events data as per the modified class definition is reloaded into the Presentation Server. For more information, see Reinitializing events in the Presentation Server.

 

 

New tssh and pw commands to create and import certificates

 

Many of you have seen the pain and struggle with the secure certificates. It is necessary, but also complicated and long. I posted about certificates some time ago, see post.

The Presentation Server and Infrastructure Management server provide a set of CLI commands to create, import, list, delete, and verify the certificates easily and quickly. You enter a few basic details and the certificate creation and import happen without any further user intervention. For more information, see Implementing certificate deployment in TrueSight Operations Management using scripts.

 

Configuring Self-health monitoring for the TrueSight Operations Management components

 

A new section for configuring self-monitoring for the following components is added to the documentation, this does not add any new functionality, but the team wanted to update the documentation to help make the setup of self monitoring a bit easier for these specific components:

 

    Set up self-monitoring for Remedy SSO and configuring the default PostgreSQL DB for self-monitoring

    Set up self-monitoring for the TrueSight Presentation Server and configuring the default PostgreSQL DB or Elasticsearch DB for self-monitoring

    Set up self-monitoring for the TrueSight Infrastructure Management server and configuring the default SQL Anywhere DB or the supported Oracle DB for self-monitoring

 

Selfmonitor.png

 

For more information, see Configuring Self-Health Monitoring capability for TrueSight Operations Management.

 

Setting up a load balancer for TrueSight Operations Management

 

The documentation now includes a topic on how to prepare and configure a load balancer for TrueSight Operations Management. There are details for the HA environment as well as where to place the load balancer in your TrueSight configuration. We even provided some Use Case information to help match your needs. For more information, see Guidelines for load balancers.

 

 

Known and Corrected Issues

The lists of the known and corrected issues are broken down by TrueSight component

TSPS details are listed here

TSIM details are listed here

Application Visibility details are listed here

 

There are many fixes and our listings cover the previous fixes from earlier fix packs so I would definitely recommend using our handy filter if you want to search for a specific issue or defect.

 

Details.png

 

Downloading the fix 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. Visit http:www.bmc.com/support and click Product Downloads to access the EPD site. There are different files for each component, so depending on your TrueSight Operations Management components, you may need to download 3 files (TSPS, TSIM, and App Vis)

 

- Warning - Please take a backup or snapshot

Before applying this fix 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.

 

Installation Steps

To install Fix Pack 3 for TrueSight Operations Management 11.0.00, follow the sequence at  Applying feature packs or fix packs.

We do see questions from time to time regarding the order of installation. Here is a quick flow of the order to install the fix pack components

 

When preparing for the installation there are several pre-installation tasks which need to be performed. They are important to the successful implementation of Fix Pack 3.

 

Step 1: Step through the preinstallation tasks. Several steps for each component used

TSPS

TSIM

App Visibility

 

Step 2: Install the Presentation Server fixes using the details representing your configuration below:

 

Standalone mode

High Availability

 

Step 3: Install the feature pack or fix pack on Infrastructure Management - consists of several phases

 

Phase A – Install on the Integration Service and Remote Cell using one of these options

Standalone mode

High-availability mode

 

Phase B – Install on the Infrastructure Management server using one of these options

Standalone mode

 

Application high-availability mode

 

High-availability OS cluster mode

 

Disaster recovery mode

 

Phase C – Set up the Infrastructure Management environment

Step 4: Install the feature pack or fix pack on App Visibility Manager

Phase A – Install on the App Visibility Manager server

 

Phase B – Install on the licensed agents

 

Task 1 – Install on the App Visibility agent

Task 2 – Install on the Synthetic TEA Agent

 

AMIGO.jpg

 

TrueSight 11.3.01 is here!!!!

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:

 

 

000161445 TSPS does not start on one node but runs fine on the other

 

000161169 Unable to login to TSIM with message:invalid user or password because of the certificate missing in TSIM server

 

000160936 Integration service fails to connect to TrueSight Infrastructure Management Server

 

000160570  "Child Server version is lower than Central Monitoring Administration version, please upgrade the child server" seen in the CMA console

 

000160462  Not seeing all devices from the child groups in the parent group in TSPS

 

000160418 Is it possible to change the hostname of Atrium/Remedy SSO, TrueSight Presentation and Infrastructure Management server after installaion?

 

000161054 After an upgrade of TSOM - Individual graphs in dashboards and device graphs are breaking intermittently

 

000160751  When configuring the ITDA component within TSPS 11.x, ITDA is displaying the following error "Registration Error - Component is unreachable on ITDA component"

 

000160661 The TSIM server can talk to the remote cell, but even launching the Admin Console from the TSIM server, it cannot connect to the remote cell

 

000160478 Publish fails with 'ERROR (120006): Instance not found' and additional 'Unexpected...' errors

Share This:

In this post originally posted by Sharad Srivastava we are going to talk about end to end integration of BMC TrueSight with Change Management.

 

The integration of BMC TrueSight with Change Management enables you to create an automated blackout policy and schedule downtime for a Configuration Item (CI) in BMC TrueSight

 

When BMC TrueSight receives a change or a task request for scheduled maintenance, the CI associated with it goes into blackout state, as a result preventing the generation of false alerts, alarms, and data for the CI.

 

There are many advantages of integrating BMC TrueSight with Change Management, some of which include

 

  • Enables BMC TrueSight to receive notifications of change requests configured on specific CIs from BMC Change Management.
  • Enables the BMC TrueSight Presentation Server console and TrueSight Operations Console to display the attributes of the change requests that are configured in BMC Change Management. You can view these attributes in the Details pane of the change event in the BMC TrueSight Presentation Server console and BMC TrueSight Operations Console.
  • Creates an automated blackout policy in the BMC TrueSight cell for the CI that you configure for maintenance in BMC Change Management. The Blackout policy make sure that no false alarms are generated for the CI that is scheduled for maintenance.

 

HOW DOES IT WORK

 

To understand how the integration works, consider the following scenario

Jim is a network operations Center (NOC) operator at a company that has multiple monitoring tools for its IT environment.

The monitoring tools generate events for all changes that occur in the environment.

Due to lack of communication between users who introduce these changes and the NOC operators, the NOC operators end up troubleshooting events generated by known change requests, wasting time and resources.

 

The integration of BMC TrueSight with BMC Change Management allows Jim to reduce the number of events generated by changes introduced in the environment.

The integration allows him to automatically block and notify users of any change including:

 

For example, Roger, the distributed server operations user, requests Rahul, the Change Coordinator, to schedule a security patch update for selected servers.

Jim has configured an automated CI blackout policy for change requests received through BMC Remedy ITSM.

This policy:

 

  • Marks all events occurring the in scheduled time period for that CI to blackout
  • Automatically schedules downtime of TSIM Schedule downtime in TSIM for change requests received through ITSM.
  • Stops data collection
  • Stops Alarms and abnormalities generation
  • Sets CI to maintenance mode

 

Becky, the Event and Impact Management – Service Model administrator, requests that the status of CIs changed to Scheduled Downtime in the Service Model.

For this use case, the following procedure is followed:

 

  • Roger contacts Rahul about scheduling maintenance of the selected group of servers to apply the latest security patches.
  • Rahul schedules the server for the maintenance 2 weeks from the date of the request for 5 hours.
  • Jim receives an event in the BMC TrueSight Presentation Server and TrueSight Infrastructure Management GUI notifying him of the upcoming maintenance. He also receives a notification that the Cell Blackout Policy and TSIM downtime schedule was created.
  • When the date of maintenance arrives, the event status is modified in the BMC TrueSight Presentation Server and BMC TrueSight Infrastructure Management GUI to notify him of that fact that now the designated servers are in down for scheduled maintenance. He also sees that all events received from the CIs that represent the servers that are now in maintenance, are set to blackout state.
  • Becky sees that the CIs status representing servers is changed to Blackout in the Service Model.
  • When at the end of the scheduled down period, the Change request is marked as completed, Jim observes that the event status is modified to Completed and validates that the Blackout Policy and TSIM Schedule downtime are removed. Events received for the CIs reflect the actual state of the CIs. Jim also receives Event Status Closed for the event that was originally generated from the change request.
  • Becky observes that CIs status is back to normal state in the Service Model

 

ARCHITECTURE

Communicating between BMC Change Management and Operations Management

BMC Change Management sends change and task requests to Operations Management through RESTful web services.

 

Architecture.png

 

Rest Webservice EventProvider component:

 

This component will receive the event notifications from the ITSM change management in JSON format over rest webservice, and this component convert this event notification into the  event and send it to Jserver (event processor component in TrueSight)

 

EventProcessor:

 

This component receives the event from the webservices Eventprovider component and do any pre-processing required on the event then send the event to cell.

 

Event Selector:

 

This Component comes into picture once event is received by Gateway Event handler, Event selector is a thread pool, its purpose is to receives the event from gatewayEvent handler and if this event is a Change Event or some other event of concern, event Selector will send this event to RuleConfigurator asynchronously.

 

RuleConfigurator:

 

This Component itself have two major components, RuleConfiguratorConsumer, and RuleConfiguratorWorker.

RuleConfiguratorConsumer's are controlled by RuleConfiguratorConsumerManager, which gets started while the initialization of JSERVER.

 

This RuleConfiguratorManager starts the different RuleConfiguratorConsumer's thread, which in itself feeds the data to RuleConfigurator's i.e PolicyConfigurator and ScheduleConfigurator. PolicyConfigurator and Scheduleconfigurator uses BlackOutPolicyCrud and ScheduleConfiguratorCrud API's to create policy and schedule down time respectively.

 

ITSM End

 

From ITSM end, The CAI RESTful plug-in establishes communication between the Change Management application and BMC TrueSight. It gets data from CAI and pushes data to a RESTful web service exposed by BMC TrueSight. This plug-in refers to the configuration data for communicating with RESTful web services.

 

Subscription call from True Sight

SubscriptionCall.png

Pre-requisite before activating the Change Management Integration with TrueSight.

 

  • Make sure that the required CMDB extensions are installed on box where the CMDB is installed. Perform following steps:
  • Perform search on SHARE:Application_Interface form where ‘Providing Application Name = BMC_PN: Class and Attribute Definitions for Service Impact Management’.
  • Make sure that the status of the chgbpm.jar file is set as Installed = 'Yes'
  • Make sure that forms starting PN: are present (e.g. PN:Published Data etc.).
  • Ensure ITSM Change management related properties are enabled in %BMC_TRUESIGHT_HOME%\pw\pronto\conf\.pronet.conf file

               -Ensure that the flag pronet.jserver.ruleconfigurator.enable in the pronet.conf file is enabled.

               -Ensure that the flag pronet.jserver.ruleconfigurator.eventcollectiondowntime.enable in the pronet.conf file isset to true.

               -Ensure that the flag pronet.jserver.ruleconfigurator.datacollectiondowntime.enable in the pronet.conf file is set to true.

  • Make sure BPPM/TSIM Server is properly integrated with CMDB

Verify  if BPPM/TSIM Server is properly integrated with CMDB. To verify this please check cmdbcorsslaunch.properties from %BMC_TRUESIGHT_HOME%\custom\conf\ for UDDI and CMDB details. File and data should exist in order to enable ITSM change integration.

 

Install ITSM change management application and verify the step 1 from above section to ensure the UDDI is configured.

 

ENABLING THE INTEGRATION

From the TrueSight Presentation Server select Administration --> Integrations

Under Change Management Integration, click the action menu and select Edit.

 

Integrations.png

 

Enter the CMDB and UDDI details.Select Activate Integration and click Save.

VALIDATING THE INTEGRATION ENABLED

 

Once the integration activated from TSPS console, Make sure that the integration is active on the box where ITSM is installed.

  • Go to Application Administration Console > Custom Configuration > Change Management > Advanced Options > Change CI Event Notification to BPPM > BPPM Subscription.
  • Click Test Connection to ensure connectivity between Change Management and     Operations Management.
  • Click Save.

 

ITSM.png

 

Flow from ITSM to TrueSight end to end

 

1-Submit the CRQ from Change Management System and status should be in Scheduled State

CRQ.png

 

 

2-ITSM will send notifications for the submitted change by the user and the entry will be created in Form - CHG:CHGBPM:Change Adapter and there are two escalations triggers INT:CHGBPM:SendEvent and INT:CHGBPM:ProcessEvent  to process this events from ITSM to TrueSight.

 

3-In order to check the Event has received from the ITSM, we can check the form CAI:Events.

 

Search for “Change_Out_CreateBPPMEvent”

 

The expectation here is the event should be process from here and event API call will land to TrueSight Server for creating event.

If the event remains in CAI:Events form then verify the return code

 

4-Once the event process from ITSM end, the Web Service API call will go to BMC TrueSight Presentation Sever and internally call will from TrueSight Presentation Sever to BMC TrueSight Infrastructure Management Server.

 

RestServiceAudit.log

 

INFO  09/18 22:01:51.264 [https-jsse-nio-443-exec-1] RestServiceAudit Target is: InvocationTarget [authRequired=false, httpMethod=POST, targetURI=/api/CI/OI-7DAC07EA4AAD4899B3B196270433D34C/event]

 

DEBUG 09/18 22:02:13.029 [Thread-115,EXECUTOR_POOL] RestServiceAudit Calling process request...

DEBUG 09/18 22:02:13.029 [Thread-115,EXECUTOR_POOL] RestServiceAudit About to process the event request...................

DEBUG 09/18 22:02:13.029 [Thread-115,EXECUTOR_POOL] RestServiceAudit  processRequest is requested for resource size 1

DEBUG 09/18 22:02:13.045 [Thread-115,EXECUTOR_POOL] RestServiceAudit done with create uri

DEBUG 09/18 22:02:13.045 [Thread-115,EXECUTOR_POOL] RestServiceAudit created execution units list

DEBUG 09/18 22:02:13.045 [Thread-115,EXECUTOR_POOL] RestServiceAudit about to add execution unit...................

 

uri:http://ab.yy.com:80/bppmws/api/CI/OI-7DAC07EA4AAD4899B3B196270433D34C/event

ngphost:ab.yy.com

 

5-Example Event created in TSPS

EventDetails.png

6-Status in Services Page on TSPS

Step6.png

 

7-Blackout Policy created in TSIM Admin Console. If we have submitted the CR for the Patrol Agent then Blackout Policy will be created in Infrastructure Policies under Configuration Page on TSPS

 

Step7.png

8-Sent an event during blackout period and event status are blackout

 

Step8.png

 

Step8a.png

9-Once the CR will go from Scheduled to Completed state, then events will be closed. After closing the CR the configured blackout will be deleted from TSIM Admin Console.

 

 

Troubleshooting Change Management Issues on TSPS/TSIM

1) Unable to register the TSPS instance

 

  • Check TrueSight.log about the error coming.
  • Check if AR Web service is publish and available with UDDI.

TS1.png

TS2.pngTS3.png

  • Make sure that following forms are available on AR side. if not, check if extension installation is proper.

 

A) CAI:Events

B) CAI:AdapterEventConfiguration

C) CAI:AdapterConfiguration

 

  • Make sure that default itsm change instance is also available.
  • If you face time-out issue, please check arerror.log
  • If you face key violation(unique index) issue, check if is there already any integration present. There is one-one relationship present. (1 ITSM to 1 TSIM)
  • Check CAI: Events form for the error you are getting.

 

2) Registration successful, but unable to see events in TSPS and thus to TSIM

 

A) If you do not see events pending there, check arjavaplugin.log from AR side.

 

B) If event is pending in the CAI:Events Form,there check the error you are receiving

  • For 401: PLease check if you have manually change the password of default user (csm_user)
  • You can change the password from CAI:AdapterConfiguration form.
  • For 400: Check arjavaplugin.log for detailed error. TSPS will not process the event if it found multiple entries of resource (CI) present.
  • For 404: Check if you have CI available on TSPS side.
  • Make sure that the TSIM to which the CI belongs is properly registered to TSPS and in connected state.

 

C) You can also check TrueSight.log and InfraApp.log for the error coming in TSPS if failure lands in TSPS side.

Files to check on TSIM : bppmws.debug.log, eventws.debug.log, TrueSight.log

 

3) Unable to see CMA policy on TSPS but Event is listed on UI.

  • Check if you have Automated Blackout Policy created on TSIM admin console.
  • Check the jserver.log (debug level) for any error coming on while sending message to CMA.
  • Check for the messages coming for RuleConfigurator.
  • You may need to check messaging logs from TSIM and TSPS side for "ITSM" Blackout message communication.

 

EventProvider (EventConverter)

Any Error which occurs in this component will be sent back to the Webservice component, which will map that error into some error code.

 

1> Invalid Data Error: This error will occur when some of the manadatory parameter would not be present or some data would be in invalid format.

2> Not Connected Error: This error will occur when cell will be down, and connection would not be possible with cell.

3> Processing Error: This error will occur while sending the event to cell or error occured at cell while creating the event.

 

Event Processor Component

Any Error which occurs in this component will be sent back to the Webservice component, which will map that error into some error code.

 

1> Invalid Data Error: This error will occur when some of the mandatory parameter would not be present or some data would be in invalid format.

2> Not Connected Error: This error will occur when cell will be down, and connection would not be possible with cell.

3>  Processing Error: This error will occur while sending the event to cell or error occured at cell while creating the event.

 

Rule Configurator Component

No error will be sent back to any component, only logged into the Jserver log file.

1> One of the rule configurator failed i.e policy creator or pnet scheduler. We will revert back the successful rule on the failure of other rule.

 

Some Use Cases:

 

Problem: Blackout policy and schedule downtime are not created for events that are received successfully

by BMCProactiveNet Performance Management

  • Ensure that the flag pronet.jserver.ruleconfigurator.enable in the pronet.conf file is enabled.
  • If a blackout policy is not created, check if the flag pronet.jserver.ruleconfigurator.eventcollectiondowntime.enable=true is

       set to true.

  • If schedule downtime is not created, check if the flag pronet.jserver.ruleconfigurator.datacollectiondowntime.enable=true is

       set to true.

  • If the problem persists even after the flags are set to true, check the JServer logs for any errors.

 

Some of the possible error conditions are:

- All mandatory slots are not getting propagated from the BMC ProactiveNet cell to the gatewayevent handler.

- Scheduled date and time entered in BMC Change Management are not valid.

- The CI does not exist.

 

 

Problem: Event is not created in the BMC ProactiveNet cell

  • Check the web services logs for any change notifications. If the change notification is present, check the web service logs for any error conditions.

 

Some of the possible error conditions are:

  - The event is invalid.

  - Some mandatory slots are missing.

  - Other internal error to the server.

 

  • If JServer receives the event, check the JServer logs if the event is available. If the event is available, check for any error.

    Some of the possible error conditions are:

    - The BMC ProactiveNet cell is not connected.

    - An exception has occurred in the BMC ProactiveNet cell, due to invalid data.

  • If the BMC ProactiveNet cell receives the event, check the cell logs for any errors.

 

Problem: Event Not received to TSPS/TSIM and no log entry in any of the TSPS/TSIM logs

Check Configuration on the ITSM change management :

 

  • Check if Change-BPPM integration is active. To verify, go to Application Administration Console > Custom Configuration > Change Management > Advanced Options > Change CI Event Notification to BPPM > BPPM Subscription. Status of BPPM instance should be active.
  • Click Test Connection button on same page. Check server, check user name password.
  • Check AR Java Plugin.log file, BPPM error logs for any errors.
  • Make sure the Escalations are enabled in AR Server Setting.

 

If Events are still not seen on the BPPM console, then perform following steps:

  • Check CAI:Events form for any Error out events. Check the error message code defined in this event, check the details mentioned in the BPPM error message guide and take appropriate actions.
  • The integration will only process the Events for SIEM Enabled CI's with all allowed relationships (Only "Impacted" relationship will not be processed for event generation). So check whether CI's related to the Change Request are SIEM enabled or not.

 

 

Sample Logging in the Jserver:

 

To Check Event reach the jserver, and to check the values of attributes, search for the following in the jserver log

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

com.proactivenet.api.aspen.ws.EventDelegate: createEvent: Attributes:

DEBUG 09/19 03:29:46 jserver [Thread-54,EXECUTOR_POOL] com.proactivenet.api.aspen.ws.EventDelegate: createEvent: NGPEvent: Event id: null, severity: null, date reception: null, status: null

INFO  09/19 03:29:46 jserver  [Thread-54,EXECUTOR_POOL] 302868 com.proactivenet.api.aspen.ws.EventDelegate: createEvent: Receieved event: Event id: null, severity: null, date reception: null, status: null, Attributes: {msg=Testing, requestedForName=Allen Allbrook, changeNotes=, ciAssociationType=Related to, riskLevel=Risk Level 5, changeModifiedDate=1537352956, ciAssociationDate=1537349970, mc_smc_id=OI-7DAC07EA4AAD4899B3B196270433D34C, changeId=CRQ000000000202, changeCoordinator=Mary Mann, scheduledEndDate=1537353000, requestedForCompanyId=Calbro Services, mc_owner=Mary Mann, mc_smc_alias=Sharad_Service, mc_host=clm-pun-030033.bmc.com, statusReason=, urgency=LOW, itsm_company=Calbro Services, mc_priority=PRIORITY_5, itsm_location=clm-pun-030033.bmc.com, severity=INFO, changeReason=, impact=MINOR_LOCALIZED, mc_host_address=, ciClass=BMC_BUSINESSSERVICE, changeLocationCompanyId=Calbro Services, scheduledStartDate=1537351200, changeCategory=Normal, dataSetId=BMC.ASSET, changePriority=Low, changeStatus=Implementation In Progress}

 

For the status of a send event check the following logs:

INFO  09/19 03:29:46 jserver  [Thread-54,EXECUTOR_POOL] 302868 com.bmc.sas.ngp.eventprocessor.util.EventSender: sendEvent: Sending Event succeed with handle: 40534

    com.bmc.sas.ngp.eventprocessor.util.EventSender: sendEvent: error: (Detail message)

 

When the Event gets propagated from the cell to the Jserver we can see the following details in the logs:

DEBUG 09/19 03:29:46 jserver  [EventSelectorWorker#5] com.bmc.sas.ngp.server.components.EventSelectorWorker: run: event id: mc.pncell_VW-PUN-APM-SP01.1ba21ebb.0, time for submmiting the event(millis): 1

INFO  09/19 03:29:46 jserver  [ChangeRuleConfiguratorConsumer] 302868 com.bmc.sas.ngp.ruleconfigurator.change.ChangeRuleConfiguratorQueue: poll: resuming from wait state

 

To Search any logs corresponding to blackout policy, refer to the thread below:

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

RuleConfiguratorWorker#PolicyConfigurator

 

To Search any logs corresponding to Scheduled downtime, refer to the thread below:

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

RuleConfiguratorWorker#ScheduleConfigurator

 

Log statement to confirm Schedule downtime is created successfully

INFO  09/19 03:29:46 jserver [RuleConfiguratorWorker#ScheduleConfigurator] 600002 com.bmc.sas.ngp.ruleconfigurator.change.ScheduleConfigurator: delegateConfigure: event id: mc.pncell_VW-PUN-APM-SP01.1ba21ebb.0, configuration is Successful: true, ruleConfigurator: ScheduleConfigurator

 

Log statement to confirm Blackout is created successfully

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

INFO  09/19 03:29:46 jserver [RuleConfiguratorWorker#PolicyConfigurator] 600002 com.bmc.sas.ngp.ruleconfigurator.change.PolicyConfigurator: delegateConfigure: event id: mc.pncell_VW-PUN-APM-SP01.1ba21ebb.0, configuration isSuccessful: true, ruleConfigurator: PolicyConfigurator

 

Logs to check the status of schedule and policy together:

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

INFO  09/19 03:29:46 jserver [ChangeRuleConfiguratorConsumer] 600002 com.bmc.sas.ngp.ruleconfigurator.AbstractRuleConfigurator: submit: event id: mc.pncell_VW-PUN-APM-SP01.1ba21ebb.0, All the rule configurator workers succeed: [PolicyConfigurator, ScheduleConfigurator]

 

INFO 09/19 03:29:46 jserver [ChangeRuleConfiguratorConsumer] 600002 com.bmc.sas.ngp.ruleconfigurator.AbstractRuleConfigurator: submit: event id: mc.pncell_VW-PUN-APM-SP01.1ba21ebb.0, Failed rule configurator workers:

 

In Case CI is not a BMC computer system, we skip scheduled down time.

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

jserver [RuleConfiguratorWorker#ScheduleConfigurator] com.bmc.sas.ngp.ruleconfigurator.scheduleddtcrud.ScheduledDownTimeCRUD: scheduledDTConfigure: Given CI is not a ComputerSystem CI, hence not configuring the schedule downtime

 

Known Issues and Fixes

1-Product defect SW00525875 - was raised for Atrium WebServices, where If customers want to have the WS published and facing the behaviour reported in the defect they need to publish the WS manually, that involves using scripts as a workaround.

 

This same workaround, is impacting the configuration of Change Management, in TrueSight Presentation Server, which is not being pushed to Application Administration Console > Custom Configuration > Change Management > Advanced Options > Change CI Event Notification to BPPM > BPPM Subscription.

Currently the defect will possibly be considered in 9.1SP4 release.

 

Workaround:

Force the registration, from TrueSight Presentation Server

a) Open the AR System Web Services Registry form in search mode.

b) In the Web Service drop-down menu, select CAI_ChangeManagementEventsSubscription_WS and click Search

c) Copy the End Point URL.

d) Go back to TrueSight Presentation Server, and open an Command Prompt window, type:

 

tssh properties set defaultItsmSoapWSURL <End Point URL>

This property should now be inserted, into the properties configuration.

 

Reload the properties

tssh properties reload

 

This properties should now be reloaded

Check if the property "defaultItsmSoapWSURL" can now be found in the configuration:

tssh properties list

 

e) Go back to Change Management Integration in TrueSight TSOM, and press Save, this should no longer fail.

f) The BPPM/TSOM integration should be active in ITSM.

 

Go to Application Administration Console > Custom Configuration > Change Management > Advanced Options > Change CI Event Notification to BPPM > BPPM Subscription.

The BPPM status should be Active.  

 

2-The integration between BPPM/Truesight and Remedy Change Management will not work if there is a colon character (:) in the summary of the Change Request.

Article:000136490

 

3-After successful integration with TrueSight (10.7) and Remedy Change Management (v9.x) was confirmed with successful publishing of CI from Remedy, there was no automatic blackout policy being created and no notifications being received, as expected with scheduling of a Change Request (CR) and relating the relevant CI.

Article:000144136

 

 

What Logs and Information To Send BMC Support

1. Version of TSPS,TSIM and ITSM

 

2. From the TrueSight Presentation Server below here is the list of important loggers to troubleshoot issues and the command to turn on/off debug

tssh logger debug on -n RestServiceAudit

tssh logger debug on -n ROOT

tssh logger debug on -n InfraApp

Logs folder from  %TRUESIGHTPSERVER_HOME%\truesightpserver

Note: Make sure you disable debug as soon as issue is reproduced

 

3.From the TrueSight Infrastructure Management Server important loggers to troubleshoot issue and the command to turn on/off debug

pw debug on -p jserver

pw debug off -p jserver

 

Logs folder from <BMC_TRUESIGHT_HOME>\pw\pronto\lpg

Note: Make sure you disable debug as soon as issue is reproduced

 

4-From ITSM Side.

Enable API/SQL/FILTER/ESCALATION debug with below steps.

In the AR User tool go to,

AR System Administration Console-> System -> General -> Server Information Logs Files tab

Select 'Filter Log', 'API Log', 'SQL Log' and modify the 'Name:' fields so they all write to the same file..

Click Apply > OK

 

Note: So be sure to enable debug, wait for the problem to be reproduced and collect the logs mentioned above immediately. Make sure you disable API/SQL/FILTER/ESCALATION debug as soon as issue is reproduced so the size of log file is minimum.

 

AMIGO.jpg

TrueSight 11.3.01 is here!!!!

 

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:

000160312 The RSSO Server goto statement in the URL is pointing to HTTP of the Load Balancer, but the LB is setup only for HTTPS. TSPS 11.3, RSSO, and Load Balancer are configured for SSL, so where is it picking up the HTTP in the goto statement?

 

000159347 Is it possible to setup an audible alarm when a critical alert comes into TSPS?

 

000160225 Does TrueSight Presentation Server support using Chrome?

 

000160190 Entuity events are not being received in TrueSight

 

000160085 After a user logs out, or times out, from TSPS the tenant user is not redirected to the login page

 

000159950 Unable to install TSIM CMDB extensions on secondary ARServer as admin operations are disabled

 

000160124 Unable to Trigger Incidents to Remedy from Secondary TSIM sever

 

000160333 After applying TLS when I restart TSIM, something is changing mcell.dir

 

000160418 How to change hostname of Atrium/Remedy SSO, TrueSight Presentation and Infrastructure Management server?

 

000159284 Are the credentials for the SNMPV3 snmptrad.conf encrypted?

 

 

Feedback.jpg

 

We want to hear from you. Please let us know what you would like to see more of in the blog postings.

Share This:

The buzz this past month seems to have centered around customization. We are seeing more requests to allow custom logos, color differentiated tabs to represent different environments, in addition to some other GUI customization to help make life easier. While we cannot do all that you want today, we want to hear from you to see which options you would like to customize in the future. Branding and labeling your enterprise applications is important to you so it is important to BMC.

 

We do allow some changes in the GUI, such as the logo and the product name, some changes are officially documented and others will be soon (currently in the knowledge base - see KAs below). We have had several requests come through Support to ask for many GUI changes to help make life easier.

 

For example, we have had requests, to make the event details Bold, to allow the row heights in TSPS to be adjustable to allow users to make them smaller to fix more on the screen, and even to change the icons for event management in TSPS. While we do not have this functionality today, we hear your requests, and we want to hear more about what type of customization would make your TrueSight experience even better.

 

Here are some links to our documented processes for changing logos and branding of the product.

TSIM

11.3 Customizing the logo and about information in the operator and slo consoles

11.0 Customizing the logo and about information in the operator and slo consoles

10.7 Customizing the logo and about information in the operator and slo consoles

10.5 Customizing the logo and about information in the operator and slo consoles

TSPS

11.3 Configuring branding settings

11.0 Configuring branding settings

Prior to 11.x customization was not officially supported or documented, but you can refer to this Communities post for more details. I would like to thank Bhuvaneswaran Ekanathan for all his assistance with this topic in the Community. We love to see activity out there.

Original post- Can We change the logo and theme color in TrueSight

 

Today, it is possible to change the product name and logo for the TSPS Console here is how to do it. It is quick and easy.

 

Take the backup of the following files:

en.json, zh.json, and de.json from the <truesightpserver_home>\modules\tomcat\webapps\ROOT\WEB-INF\classes folder.

company.svg from <truesightpserver_home>\modules\tomcat\webapps\ROOT\img\header folder.

 

Step 1 ::: Product name change

 

Go to <truesightpserver_home>\modules\tomcat\webapps\ROOT\WEB-INF\classes

Open the en.json file and search for

"productName": "TrueSight"

This TrueSight value is the display for Product Name. Users can customize the name based on requirements.

E.g: "productName": "TrueSight_Prod", "TrueSight_QA", "TrueSight_Dev"

 

Please follow the same steps to change the productName value in the two additional json files(zh.json and de.json).

Save the files as the changes are made

 

ProductNameChange.png

 

Step 2 ::: Logo change

In order to change the logo in TrueSight, you would need to go to the <truesightpserver_home>\modules\tomcat\webapps\ROOT\img\header folder.

Backup and then remove the company.svg image, place the svg custom image in the folder mentioned above and rename it as per your company name.

 

ProductNameChange_Logo.png

 

Step 3 ::: Restart TSPS

A restart of TSPS is needed for the changes to be rendered

tssh server stop

tssh server start

 

Step 4 ::: Launch the TSPS console and verify the changes.

 

NOTE: These custom logo and product name changes will be lost during an upgrade of TSPS from one major version to another so be sure to make these custom changes after each upgrade

 

Users can also change the background image of the TSPS login page - check out the video below for details on how it is done

 

 

If you dont see what you want in the application today, please do let us know or feel free to submit an Idea via the Community. This feedback helps us help you. Here are a few of the current Ideas which may need your vote. Click the link and vote up the Idea.

 

Request to support changing the background color in the TSPS console

Request to allow users to customize the event display options in the TSPS console

TSPS - Change column names in the event view

TSOM-Visual Difference of QA and Prod

 

video.png

Have you heard? TrueSight products now have their own YouTube channels

Subscribe today to see all the latest how-to videos and videos which explain some of the most commonly misunderstood features in TrueSight. We are adding new content regularly, so be sure to subscribe so you will be notified of any new additions.

 

•    TrueSight Server Automation

•    TrueSight Operations Managements

•    TrueSight Capacity Optimization

 

 

AMIGO.jpg

Do not forget, we offer a free AMIGO program to help you move up to the latest version.

 

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 Articles added over the last month:

 

000158141 Unable to login to TrueSight Presentation Server Console setup in HA via the load balanced URL

 

000158367 Attempts to import the TrueSight Base Repository fail with "Failed to load resource bundle-BuilderMessages"

 

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

 

000158519 Is it possible to disable the ASSO timeout for NOC view in TrueSight Presentation Server 10.x

 

000158659  Is it possible to change the Product Name and Logo on the TrueSight Presentation Server?

 

000158661 If I create a group in a Infrastructure policy called Windows and the policy uses tag for the Windows Servers How can I see them in 1 Windows Group in TSPS

 

000158871 When working in TSPS if we have two similar policies, should they

 

000158942 How to view Service Models in TrueSight consoles when top level CI is not a Business Service?

 

 

Feedback.jpg

 

We want your feedback. Let us know what you like to see in the blog posts in the future.

Share This:

TrueSight Operations Management users have the option to use https or http when working with the communication between the TrueSight Components. Depending on your environment and security needs, you may be able to go with our http option. This would help you avoid the dreaded secure certificate installation for each component. However, if it is not an option in your environment, you would have to stick with https and the ssl certificates.

 

There are some benefits to using http vs https, one being the certificate factor, which is costly and time consuming. Some users report that SSL may cause performance issues and slow things down depending on what you are accessing, however, the encryption used with https sometimes is required. Perhaps the best reason, beyond system load, is that it breaks name-based virtual hosting. With SSL, it's one site - one IP address which adds cost and makes administration a nightmare. So for those who run and will only run with https, my apologies, but this may not be the post for you. BMC wanted to give TrueSight users the options so we default to https, but there are instructions for switching to http.

 

We do have the option to set http mode for RSSO/ASSO, and TSPS components, these are considered core components, additional components may have the same option, but I will focus on these components mentioned. It really is not that hard to make the switch. The TSIM server is configured for both http and https by default.

 

Let's take a look at what is involved in the configuration of http mode for the Remedy Server and TrueSight Presentation Server. Since these components go hand in hand, if you switch one to http, you will need to switch the other to http as well.

 

 

To configure Remedy SSO to use HTTP

 

Do the following:

 

    1. Log in to the Remedy SSO host computer, and navigate to the following directory:

        (Windows): <installationDirectory>\rsso\tomcat\conf

        (Linux): <installationDirectory>/rsso/tomcat/conf

 

    2. Edit the web.xml file, and comment the following section of code and save the file:

 

    The commented code lines:

   <!--

    <security-constraint>

         <web-resource-collection>

            <web-resource-name>Secure context</web-resource-name>

            <url-pattern>/*</url-pattern>

         </web-resource-collection>

         <user-data-constraint>

             <transport-guarantee>CONFIDENTIAL</transport-guarantee>

         </user-data-constraint>

    </security-constraint>

    -->

  3.  Edit the server.xml file, delete the redirectPort parameter from the following code line, and save the file:

http_conversion.png

The code line after deleting the redirectPort parameter:<Connector connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="2048" port="8088" protocol="HTTP/1.1"/>

 

    4.   Navigate to the <Remedy SSO Installation Directory>\rsso\bin directory, and restart the Remedy SSO server by running the following command

    • (Windows) rsso.bat server start
    • (Linux) ./rsso server start

 

 

To configure TrueSight Presentation Server to enable HTTP mode

 

Do the following:

 

  1. Log in to the Presentation Server host computer, and navigate to the following directory:
    • (Windows): <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf
    • (Linux): <Presentation Server installation directory>/truesightpserver/modules/tomcat/conf
  2. In a text editor, edit the \web.xml file and comment out the security constraint section so that it reads as follows:

<!--

<security-constraint>

        <web-resource-collection>

            <web-resource-name>Secure context</web-resource-name>

            <url-pattern>/*</url-pattern>

            </web-resource-collection>

           

            <user-data-constraint>

            <transport-guarantee>CONFIDENTIAL</transport-guarantee>

            </user-data-constraint>

    </security-constraint>

-->

     3.  In a text editor, edit the <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf\server.xml file:

          a. Modify the following line:

<Connector connectionTimeout="20000" enableLookups="false" port="80" protocol="HTTP/1.1" redirectPort="443"/>

     Then, remove the redirectPort information so that it reads as follows:

<Connector connectionTimeout="20000" enableLookups="false" port="80" protocol="HTTP/1.1" />

Note: The default port for Windows is 80 and Linux is 8080. If you specified a custom port during installation, enter that port number instead

         b. Comment out the following line so that it reads as follows:

<!-- <Connector SSLEnabled="true" ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_SHA256,
TLS_ECDHE_RSA_WITH_AES_128_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_SHA,TLS_ECDHE_RSA_WITH_AES_256_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_256_SHA384,TLS_ECDHE_RSA_WITH_AES_256_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_SHA,
TLS_DHE_RSA_WITH_AES_128_SHA256,TLS_DHE_RSA_WITH_AES_128_SHA,TLS_DHE_DSS_WITH_AES_128_SHA256,
TLS_DHE_RSA_WITH_AES_256_SHA256,TLS_DHE_DSS_WITH_AES_256_SHA,TLS_DHE_RSA_WITH_AES_256_SHA"
clientAuth="false" compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json" compression="on" compressionMinSize="1024" keystoreFile="C:/Program Files/BMC Software/TrueSightPServer/truesightpserver/conf/secure/loginvault.ks" keystorePass="changeit" maxThreads="150" port="4435" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslProtocol="TLSv1.2" useServerCipherSuitesOrder="true"/>
-->

  4.  From the <Presentation Server installation directory>\truesightpserver\truesightpserver\bin folder, use a command prompt to run the following command:

tssh properties set tspsPreferredWebServiceProtocol http

  5.  If you want to use the TrueSight console to deploy and install packages on a PATROL Agent, from the <Presentation Server installation directory>\truesightpserver\truesightpserver\bin folder, use a command prompt to run the following command:

tssh properties set server.port.websrv.protocol http

  6.  (Fresh installation only) In a text editor, edit the <Presentation Server installation directory>\truesightpserver\conf\ha\ha.conf file and add the following line:

ha.server.protocol=http

  7.  Restart the TrueSight Presentation Server

  8.  On each Infrastructure Management server connected to the TrueSight Presentation Server, add the following property to the <Infrastructure Management installation directory>\pw\custom\conf\pronet.conf file:

tsps.tsim.http.enabled=true

  9.  Restart each Infrastructure Management server that you changed.

 

For your TSIM servers, the default protocol for this connection to the Operator Console is HTTP. To log on using a secure HTTPS connection, click the link Switch to Secure Mode on the logon page. If you use HTTPS, Infrastructure Management encrypts the information relay from the Web interface for additional security. Secure connection mode is indicated by the text You are using a secure connection now.

 

Since TSIM handles both and will accept http by default, the option to set communication to https exists for the TSIM server(s).

 

Configuring the Apache web server to accept HTTPS connection only

 

If your site does not need a HTTP connection, follow these steps to reconfigure Apache.

To configure the Apache web server to accept HTTPS connections

 

    Access the appropriate directory for your operating system:

        (Windows) \pw\Apache\conf

        (Solaris or Linux) /usr/pw/apache/conf

    Save a copy of the httpd.conf file.

    Edit the httpd.conf file to comment out the 'Listen 80' line, so the line reads as '#Listen 80'.

    Restart httpd by running the following command:

    pw process restart httpd

 

Note: Switching Apache server from HTTP to HTTPS mode requires restarting the system.

 

All these details are documented in our product documentation:

 

Configuring the Presentation Server for non-secure (HTTP) mode1

11.3.01

11.0

10.7

10.5

 

 

Configuring the Apache web server to accept HTTPS connection only

11.3.01

11.0

10.7

10.5

 

AMIGO.jpg

 

Have you upgraded to 11.3.01 yet? What are you waiting for?

 

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:  We strive to share our experiences in order to help others

 

000156330 How to set Patrol config variables automatically via CMA Policy

 

000156341 Running dataUpgrade.bat gives the error “Data upgrade failed! See the logs at DataUpgradeUtility/logs. Please contact BMC support!

 

000156343 Error 1001 occurred during processing of TSIM event <event_handle>: Evaluation of function tf_next_start(Production) failed

 

000156363 TSIM performance is very slow and jserver is consuming high levels of CPU when attempting to navigate through the GUI

 

000156512 TSPS 11.0 installation cannot connect to RSSO 18.05

 

000156725 Does TrueSight accept Rest API call credentials in plain text?

 

000156840 Messages from Global Thresholds do not have prop spacing

 

000156914 "java.rmi.server.ExportException: Port already in use: 0" seen in the TrueSight.log & the jserver process does not start

 

000157022 How can I turn off the 'Enable KPI' defaults in the Global Thresholds found under the Configuration options in the TrueSight Console?

 

000157171 Unable to add new Patrol Agent to BPPM Operation console, but it appears fine in the CMA console

 

Feedback.jpg

 

 

Looking for a previous blog posting? Find it here:  BMC TrueSight Pulse Blogs

Share This:

Thank you for participating in the TrueSight Infrastructure Management Community. To expand opportunities for collaboration, and simplify participation for members, this community will be consolidated with the TrueSight Operations Management (TSOM) community in the near future.

 

 

This enhancement will continue to allow you to share information with TrueSight Infrastructure Management customers, but will also expand your opportunities for collaboration by adding members of the TrueSight Operations Management community. You will still be able to share ideas and experiences about improving the end-to-end health and performance of your IT infrastructure through monitoring, event management, operational analytics, and the other capabilities of TSIM. In addition, you will be able to gain information about application performance management including a view from an end-user perspective, by being part of the TSOM community. 

 

Your support of this improvement is appreciated and we look forward to your continued and expanded collaboration in the future.

 

What does it mean for you?

You will be able to participate as in the past, on any content, the scope of the community will be broader and as a consequence increase knowledge sharing.

Is there something you need to do?

Yes, if you have not done it already, click follow on the TrueSight Operations Management Community:

Screen Shot 2018-07-27 at 09.07.51.png

For more information about the simplification of TrueSight communities read this post.

 

Any question? Comment below

Share This:

If you are using a 10.x version of TrueSight Infrastructure Management and you are seeing poor GUI performance and jserver is consuming high levels of CPU when attempting to navigate

through the GUI, we may have something to help.

 

Slowness can have many causes, so Support will likely ask you for your hardware specifications as well as load on the application, and if there are any other outside factors (patching,other applications on the box, network connectivity issues, etc). The goal is to get an overall view of your environment to help narrow down the focus of the search.

 

While there may be a variety of factors, one way to clear up slowness is to enable lazyloading. This is a property which can be set in order to allow more effective loading of objects in the

console.

 

Certain performance problems can be observed within the navigation tree of the Ops Console. Examples of this could be:

 

  •     Navigation tree does not load at all
  •     Navigation tree only partially loads
  •     Navigation tree takes a long time to load
  •     Operations Console becomes inaccessible and the number of https processes increases

 

Setting the lazy loading parameter to true can help to resolve these problems.

 

The performance problems seen in the navigation tree can be caused by a number of things such as:

 

  •     High number of events
  •     High number of dynamic collectors
  •     High number of CIs in the service model
  •     Depth of service model
  •     Large number of component folders
  •     Large number of event folders

 

The recommendation is for users to uncheck those items in the navigation tree preferences that they are not interested in. For example, if a user is interested in events only, then uncheck

the boxes related to service model and folders.

 

This is because of the way the navigation tree works, in that data is loaded in the order of top to down. So, it will be event collectors first, then groups, then service model CIs, then

component folders, then event folders. All of this can take time as they have to be loaded from various sources such as cell, jserver, backend database, and it can result in a bottleneck.

 

The lazyloading option says to load only the toplevel elements. Then as soon as a user wishes to expand that toplevel it will fetch the data at that point. That is why traversing from

toplevel down can seem slower, but it is greatly reducing the load on the jserver.

 

To turn the lazyloading option on, add the following property to pw/custom/conf/pronet.conf file:

    pronet.navtree.lazyloading=true

Then reload the jserver properties with command:

    pw jproperties reload

Then monitor the performance of the TSIM console.

 

If the performance continues to be an issue, there is another property to set in the 10.x versions which can also help with TSIM slowness, the nearcache property.

 

Please add the following properties to the pw/custom/conf/pronet.conf

pronet.hotrod.client.rate.custom.nearcache.enable=false

pronet.hotrod.client.jserver.custom.nearcache.enable=true

pronet.tsim.console.data.fetch.optimized=false

 

Then restart the TSIM server (pw system start). These properties will help to solve performance issues in the TSIM Operations Console and Administration Console and these properties are set by default in TrueSight 11.3.01

 

If the issue remains after enabling the properties above, collect the pw dump 1 output and send the details to Support for further assistance.

 

 

TSIM Component stuck in the “Initializing” state

 

Another issue we have seen recently with TSPS is the TSIM server component being stuck in the Initializing state for a long period of time. While there may be many factors involved in this

type of situation, it is always best to send the logs to Support to review them for other possible causes of the issue.

 

Due to the elastic search errors below the component was unable to communicate (sync) with TSPS which caused it to fail.

INFO 06/21 09:32:53.393 [EventMsg_28] TsimAudit Failed to insert events to ES

java.util.concurrent.ExecutionException: RemoteTransportException[[ZbkOM4q][127.0.0.1:9300][cluster:admin/ingest/pipeline/put]];

nested: ScriptException[compile error]; nested: IllegalArgumentException[Scripts may be no longer than 16384 characters. The passed in

script is 21057 characters. Consider using a plugin if a script longer than this length is a requirement.];

 

This issue with elastic search is fixed in TrueSight 11.3.01 and is tracked as Defect ID: DRTSO-43721. The recommendation is to upgrade to 11.3.01. A workaround is to delete the elastic

 

search data folder and restart TSPS. The elastic search folder can be found here: <TSPS_HOME>/modules/elasticsearch/

Delete the entire folder as it will be recreated upon restart of the TSPS server

 

If clearing the elastic search folder does not allow the TSIM component to initialize, please gather up the output of the tssh dump export command and send it to Support for further review.

 

These were just a couple of issues which we have seen with TrueSight 10.x so we took the time to fix them in 11.3.01 so you will not have to worry about these issues above.

AMIGO.jpg

 

TrueSight 11.3.01 is here!!!!!…

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:

 

000155850     When the TrueSight Agent deployment status is stuck "in progress" or has failed, what troubleshooting details are needed?

 

000156363     TSIM performance is very slow and jserver is consuming high levels of CPU when attempting to navigate through the GUI

 

000156303     If groups are created in the TSIM Admin Console are they exported to the Report Engine for use in Business Objects?

 

000156107     TSIM upgrade or installation hangs on "Configuring and Populating Database" screen on Linux environments

 

000156040     'tssh componenttype update' does not honor the skipResourceCheck


000156341     Running dataUpgrade.bat gives the error “Data upgrade failed! See the logs at DataUpgradeUtility/logs. Please contact BMC support!“

 

000155953     "Self-Monitoring: Server is disconnected from Operations Management Server on <TSPS host name>" events are seen

 

000155948     How can I configure TSIM's jserver process to use an http proxy, so that I can configure the BSR configuration, when a proxy is required to reach the midtier server?

 

000155433     Unable to remove polling interval when editing an existing policy in TSPS

 

000155643     ALARM class events do not appear in the TSPS events display

 

 

 

Looking for a previous blog posting? Find it here: BMC TrueSight Pulse Blogs

Filter Blog

By date:
By tag: