Archive for the ‘Hewlett Packard’ Category

Validating the BSM EUM Model


The following steps will navigate you to the EUM model validation JMX bean:

  1. Login to gateway server jmx console http://<Gateway>:8080/jmx-console/
  2. Under Topaz, Click “service=EUM Administration Service” then find “validateEumModel()”

Enter the following:

  • customer id: 1
  • Eum Model: ALL
  • Full Model Scan: "yes"
  • Fix Model If Needed: "yes" ;

Why is my CMDB NOT Accurate!?

Many times CMDB projects encounter a situation where the CI's contained in the CMDB become unreliable, and thus the value is lost.  Typically this occurs after a period of time has elapsed from the initial deployment.

The Configuration Librarian.

The Configuration Librarian's responsibility is "…maintaining up-to-date (and historical) records of configuration items.." There is a lot of work implied between the lines in that  description. Regardless, without at least one dedicated Librarian, the CMDB will never be accurate. My experience is CMDB customers usually expect the entire CMDB scope to be automatic. And no matter what your Sales Rep tells you, its simply not true.

And that makes perfect sense. What other Enterprise solution maintains itself without administration? CMDB is no different and requires at the least a nominal investment in time and resources. Honestly, I'd say its much lighter in this regard than most other Enterprise solutions out there. Further, I would suggest a point of contact be made available from every organization involved in the scope (servers, networks, databases, apps, etc).

What separates the HP uCMDB from competitors is the high level of customization available to meet the needs of a unique Enterprise. If OTB discovery and enrichments are not sufficient, the capability is certainly there to expand those functionalities, based upon your own needs. However, this requires knowledgable resources… which comes back to the original point above; time and resources are required (just like any other Enterprise Solution).

Here is a breakdown of the Librarians' Key Activities:

  • Assist "ABC" in planning for Configuration Management databases and activities
  • Identify Configuration Items under "ABC" management
  • Control Configuration Item information
  • Perform status accounting
  • Perform verification and audit of Configuration Management databases
  • Provide management information about Configuration Management quality and operations
  • Maintain quality of CI information entered into "ABC" CI Databases
  • Collect information about the current state of CIs
  • Receive and obtain announcements of significant changes in the state or condition of CIs
  • Respond to requests for CI changes and updates from Change Management
  • Provide CI information upon request

With at least one dedicated Librarian, depending on scale, you are on the right path to having an accurate CMDB.  Can you spot the gap in your deployment above?

Integrating Sitescope to HP Operations Manager (BSM)

  1. Stop Sitescope Service on host
  2. Launch Configuration Tool from Start Menu (run as administrator)
  3. Install the Operations Agent
  4. On the SiteScope server (where the OM agent is running):

    1. Execute "ovconfget sec.core CORE_ID" from command line. Copy the results.
  5. On the BSM DPS machine: (<coreid> is output of step A)

    1. Execute "ovcert -exporttrusted -file \dps" from command line
    2. Execute "ovcm -issue -file \sitescope00 -name:  <sitescope_server_FQDN> -coreid <coreid>" from command line
    3. Copy the created files from DPS to SiteScope server
  6. On SiteScope server:

    1. Execute "ovcert -importtrusted -file \dps" from command line.
    2. Execute "ovcert -importcert -file \sitescope00" from command line.

Note: One reason you might perform this kind of manual integration is if port 383 is not open between the SiS and DPS servers.

Custom RHEL Memory Monitor – Part II

In the last post I described how to create a custom memory monitor using a Script Monitor.  The Script Monitor, while functional, may not be desirable as the "Value" returned does not fit into default Threshold/Alert configurations.  Which basically means the monitor can run, but cannot be Alerted upon.

Instead, by editing RedHatEnterpriseLinux.config, located on the SiS host (E:\SiteScope\templates.os dir), we can define the command being executed to determine the REAL "Physical memory used %" for RHEL systems.


  • Open the RedHatEnterpriseLinux.config file, locate the following:

command=/usr/bin/free -b

  • Replace that with the following:

command=echo `free | grep - | awk '{ print $4 }'`" "`free | grep Mem
|awk '{ print $2 }'`

  • Restart SiteScope Server

This monitor will now show the correct Physical memory used % for RHEL systems.

Custom SiteScope Memory Monitor – Part 1

In certain environments, a custom memory monitor may be required to monitor Unix based hosts.  Why? A Unix System Admin might describe it as follows:

Unix/Linux will fill any free memory with disk buffers and caching, but that should not be counted as “used” memory, because if an application needs it, the kernel will give it up. The proper way to calculate memory usage is to pull the total used and subtract whatever amount of cache and buffers are being used.

echo 'free | grep - | awk '{ print $4 }''/'free | grep Mem |awk '{print $2 }'' *100 | bc -l

On the SiteScope host, create a '' file in /SiteScope_Root/remote.script/ directory. This can be done using Notepad.

Insert the script above into your .sh file and save it.

In the SiteScope interface, create a Script Monitor directed at your Unix host with the following settings:

  • Script: USE COMMAND
  • Match expressions: /[0-9]{2}.[0-9]{2}/
  • Remote script Command File: (select your .sh file from dropdown)

From here you can adjust the Thresholds to Alert on the Status of the monitor (which is a 0-100 percentage of the actual Free Memory available).


See Also: Custom Memory Monitor Part 2

Return top