DX Infrastructure Manager

Expand all | Collapse all

Change robot name with qos_processor

  • 1.  Change robot name with qos_processor

    Posted 04-10-2019 10:35 PM

    Hello all,

     

    I could change the robot name using qos_processor ruby script. The problem is S_QOS_DATA.ci_metric_id is created but it does not exist.

    I saw in CM_CONFIGURATION_ITEM_METRIC and there is no relation with ci_id. So, why is ci_metric_id is beeing created if no relation with device and ci_metric_type?

     

    Regards



  • 2.  Re: Change robot name with qos_processor

    Posted 04-11-2019 09:50 AM

    Why not via controller > configure > setup > nimsoft > Robot name: Set specific name?



  • 3.  Re: Change robot name with qos_processor

    Posted 04-11-2019 10:17 AM

    Hello David, because we need only this QOS been change. So, we can not change the others, that´s because we are trying to use qos_processor scripts.



  • 4.  Re: Change robot name with qos_processor

    Posted 04-11-2019 10:35 AM

    What qos?

    robot name is not a qos, it's an attribute of the robot.

    Better than guessing and going back and forth, provide all the relevant details.



  • 5.  Re: Change robot name with qos_processor

    Posted 04-11-2019 11:29 AM

    Hello David,

     

    Thank you for your time helping us about this situation.

    So, we have 2 robots. Robot1 and Robot2.

    The situation is:

    Robot1 get some informations from Robot2 and generate QOS using , but we need this QOS metric been associate to Robot2 not Robot1 because we need that QOS information shows in USM for Robot2, using this method of changing robot is not working.

     

    Regards



  • 6.  Re: Change robot name with qos_processor

    Posted 04-11-2019 11:42 AM


  • 7.  Re: Change robot name with qos_processor

    Posted 04-11-2019 02:58 PM

    Robot1 get some informations from Robot2 and generate QOS using

    this sounds like robot1 has a probe doing remote monitoring of robot2, and many of the probes that do remote monitoring have an option to use the profile name for the qos source. So this need may be able to be fulfilled via the probe configuration.

     

    See, if the details would have been supplied instead of vague 'get some info.' then specific advice could have been supplied.