View Only
  • 1.  Pulling historical performance data into CMC

    Posted Fri June 25, 2021 02:03 PM
    I am currently trialing the CMC software and was hoping this group might have some experience to help solve a couple of question.

    1. Is there a way to pull in historical performance data into CMC from the connected HMC's? The HMCScanner tool does this really well but it would be great to see it in CMC.
    2. under the patch planning inventory IBMi LPAR's are not shown with any TR level and the recommended one is always wrong. Anyone else had those issues?


    geoff king

  • 2.  RE: Pulling historical performance data into CMC

    Posted Mon June 28, 2021 07:57 AM
    i'm not familiar with that software, i use

    or maybe this would help.

    Bryan Dietz

  • 3.  RE: Pulling historical performance data into CMC

    Posted Tue June 29, 2021 09:23 AM
    i've been using lpar2rrd for 2 years now , it's very useful
    i have the agent installed on Ibm i as well as Linux and VIOS , 

    i decided to use lpar2rrd because PowerVP is not compatible with Power9 processors.

    Jean-Marc Gastal

  • 4.  RE: Pulling historical performance data into CMC

    Posted Wed September 01, 2021 02:28 PM
    Edited by Matt Geisler Wed September 01, 2021 02:33 PM
    If you login to the Cloud Management Console and go under "Capacity Monitoring" and then select "System Name" you can look at historical data for Systems/Frames like "Core Usage" "Memory Allocation" "Network Traffic" "Storage Traffic" and "Power Usage." Also if select the "Partitions" tab under "Capacity Monitoring" you can drill down in the systems performance at the LPAR level. It would be nice for them to add a bit more data like in LPAR2RRD. I hope Rocket Software keeps making improvements to it... My Patch Planning seems to lag on updating or doesn't always have the proper information either. 

    I run the following command as a cron job to update information on the HMC.

    hscroot@myhmc:~> for frame in `lssyscfg -r sys -Fname`; do lssyscfg -m $frame -r lpar --osrefresh -Fname; done

    From Support: The CMC relies on the HMC to tell it what OS level LPARS are running at. Although the HMC maintains an RMC connection with (most**) LAPRS, the information on OS level must be refreshed.