DX Unified Infrastructure Management

  • Private Community
 View Only

  • 1.  usage_metering change in cdm probe value

    Posted Jan 07, 2021 10:00 AM
    Not sure anyone else noticed, but looking at our usage_metering reports for January or UIM Server pack license counts were double what they normally are.  Checking the details of the report, it looks like the cdm value was changed from .33 to .50 per host.  Not sure why this changed but seriously elevated our license usage.  We will be having a chat with Broadcom account reps on this, crazy that it would change like that without any notice, heads-up or explanation.


  • 2.  RE: usage_metering change in cdm probe value

    Broadcom Employee
    Posted Jan 11, 2021 03:07 AM
    Edited by Ravishu Arora Jan 11, 2021 03:08 AM
    Hi Dane,

    Sorry to hear that you are seeing the unexpected spike!

    Please reach out to the Support or Account Team to understand the usage report and the discrepancy.
    We make an effort to provide due heads-up to customers for any planned changes to usage metering, and there should not be one in your January report. However, I shall defer to the account team to investigate the specifics of the issue.

    ------------------------------
    Principal Product Manager
    ​AIOps and Observability | Enterprise Software
    Broadcom
    ------------------------------

    Original Message


  • 3.  RE: usage_metering change in cdm probe value

    Posted Jan 13, 2021 01:52 PM
    Opened a support case - appears so far that during the upgrade to 20.3.x the cs_id's were changed to new cs_id but the usage_metering probe is still picking up the old cs_id's even though there are not duplicates/old id's not tied to cm_computer_systems table.
    Original Message


  • 4.  RE: usage_metering change in cdm probe value

    Posted Jan 13, 2021 02:01 PM
    By design usage_metering retains a record of the high values for the month. In this case for the month there is both the old and new cs_id so both show up in the log. Question to be resolve via the case is if this is a defect with the expectation that the probe should know and filter out the dup, or is this the way it is intended to work. Perhaps the greater more concerning question is why the cs_ids changed, I am unaware of anything that happens during the UIM Server or OC upgrade that would touch a robot cs_id. Perhaps it was related to robot_update deployment. Regardless please let us know the outcome from the support case.

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------

    Original Message