IT Operations Management (ITOM)
Showing results for 
Search instead for 
Do you mean 

Manage Dimensions in SHR you need ... Use you must .... Dimension Life Cycle Management

Guest Blogger (HPE-SW-Guest) on ‎05-19-2014 06:18 PM

 

So what was the need that we came up with Dimension Lifecycle management tool?

 

Many times we would have faced the situation where we always thought that how nice it would be if we could knock out a dimension from SHR data ware house. Also couple of similar asks in SHR forum recently like

 

  • From: *****************

Sent: Friday, May 16, 2014 9:47 PM

Subject: resynchronize operations agents list with SHR

 

"I would like to resynchronize the list of operations with SHR and delete the one which collections has failed. Actually I changed the primary DNS name in each of the operations agents in RTSM and now I have duplicate nodes in SHR with different DNS names, the ones with the old DNS name does not work and I would like to remove them."

 

Any idea, how to do that?

 

  • From: **************

Sent: Tuesday, March 04, 2014 2:01 AM

Subject: Deleting node in SHR database due to duplicate nodes imported from RTSM sync

 

"I’m seeing an issue where some nodes in RTSM are duplicated (i.e. one with CI Type as Windows, another as UNIX).   These duplicates were unfortunately imported into SHR and as a result there are duplicate server names in SHR’s table.   

We were able delete some of the duplicate entries in RTSM.  When SHR syncs topology with RTSM, will the duplicates in SHR be cleaned up (deleted from the table)?  Or, is there a way to delete the entries? "

 

  • From: ****************

Sent: Tuesday, January 28, 2014 9:24 PM

Subject: New CI ID for PA agent node 

 

"I am facing an issue with one of the PA agent node where CIID of the node has changed. Topology information of this node was pulled from RTSM few days back. But agent was not working (CODA was not logging data) till today and no data collection was happening from SHR. OM team reinstalled the agent today to fix the issue. Now when data collection started today, data is coming with a new CIID. Now there are two entries for this node"

 

As an answer to all these queries SHR 9.31 was released with Dimension Life Cycle Management Tool.

 

Scenarios where the tool proves its worth

 

  1. Dimension no longer exists in the deployment: Node is decommissioned from customer environment and there is no need of any report on this dimension in SHR. Following are the steps to delete such dimensions from SHR data ware house. 
  1. The tool identifies and lists the dimensions that do not have fact data for a given period and/or dimensions that are not available in data source but available in SHR (Output in CSV format). 

Command: Dimensionmanager -inactive_dim_list -caption K_CI_SYSTEM -inactive 30 -output_dir C:\DLC

 

 

  1. The user has to verify the CSV and remove the dimension entry from CSV which has to be retained in SHR.
  2. The modified CSV file is then given as input to the tool for deletion operation. 

Command: Dimensionmanager -inactive_dim_delete -caption K_CI_SYSTEM -file C:\DLC\K_CI_SYSYEM_1234.csv  -mode test

 

Please Note: This command runs the deletion in test mode and is to validate the result of deletion. In order to delete permanently the CIs from the warehouse, the command has to be run in "commit" mode

 

 

 

  1. Duplicate entries in SHR data warehouse: Multiple entries of the same CI may exist tin SHR data ware house due to various reasons of which some are as follows: 
  • Multiple entries are available in the topology source itself. For example, if a node is identified by a short name and long name and if RTSM reconciliation fails to reconcile this as a single node.
  • The business key (which is CIID in some cases) changes when the dimension is deleted and added again in the data source. 

Following are the steps to delete such duplicate dimensions from SHR data ware house:

 

  1. The tool identifies and lists the duplicate dimensions available in SHR /data source (Output in CSV format). 

Command: Dimensionmanager -duplicate_dim_list -caption K_CI_SYSTEM -output_dir C:\DLC

 

 

  1. The user has to verify the CSV and remove the dimension entry from CSV which has to be retained in SHR.
  2. The modified CSV file is then given as input to the tool for deletion operation. 

Command: Dimensionmanager -duplicate_dim_delete -caption K_CI_SYSTEM -file C:\DLC\K_CI_SYSYEM_1234.csv -mode test

 

Please Note: This command runs the deletion in test mode and is to validate the result of deletion. In order to delete permanently the CIs from the warehouse, the command has to be run in "commit" mode

 

 

 

  1. Renaming the natural key: In this use case, a dimension is deleted in customer environment and a new dimension is created with the same natural key. For example, a node is removed and a new VM is created with same node name.  Following is the command to rename the natural keys. 

Command: Dimensionmanager -rename -caption K_CI_SYSTEM -file C:\DLC\K_CI_SYSYEM_1234.csv

 

 

There are a few more commands available under dimension lifecycle management tool to manage the dimension for SHR data ware house. Following is the command to list down all the supported operations by “Dimension lifecycle management tool.

 

Command: Dimensionmanager -help 

 

 For further details regarding Dimension lifecycle tool and its limitation, kindly refer “HP Service Health Reporter Administration Guide.pdf" document shipped along with SHR 9.31.

0 Kudos
About the Author

HPE-SW-Guest

This account is for guest bloggers. The blog post will identify the blogger.

Events
June 6 - 8, 2017
Las Vegas, Nevada
Discover 2017 Las Vegas
Join us for HPE Discover 2017 in Las Vegas. The event will be held at the Venetian | Palazzo from June 6-8, 2017.
Read more
Apr 18, 2017
Houston, TX
HPE Tech Days - 2017
Follow a group of tech bloggers for a new HPE Tech Day, a full day of sessions about how to create a hybrid IT, from hyperconverged to Composable Infr...
Read more
View all
//Add this to "OnDomLoad" event