DX Unified Infrastructure Management

  • 1.  Probes errors on PVS servers

    Posted Dec 20, 2017 09:16 AM

    Hi ,

     

    We have nimsoft robot running on all PVS servers(200 servers) for monitoring and after server restart, all the probes except controller goes to "probe validation" state.It is because these servera are imaged from master server after every restart. Do we have any solution/Idea to eradicate the probe error validation issue.



  • 2.  Re: Probes errors on PVS servers

    Posted Jan 08, 2018 11:15 AM

    (converted this from a discussion to a question)

    community, can anyone help answer this question please.  



  • 3.  Re: Probes errors on PVS servers

    Posted Jan 08, 2018 11:16 AM


  • 4.  Re: Probes errors on PVS servers

    Broadcom Employee
    Posted Jan 09, 2018 08:33 PM

    Hi, Martin.

    Hostname and IP are the same after restart ?



  • 5.  Re: Probes errors on PVS servers

    Posted Jan 10, 2018 08:19 AM

    Yes, they remains same



  • 6.  Re: Probes errors on PVS servers
    Best Answer

    Broadcom Employee
    Posted Jan 10, 2018 11:03 AM

    You can do it, but I am thinking the implementation is wrong.  On the PVS image, you need to do a Cloud Robot Install set to a reboot of 1.  Then put a request.cfg file in to download a SuperPackage with probes and configs or use MCS to redeploy the probes and configs.

     

    Each robot needs a unique id, once a robot has checked into a hub, now that is stored in niscache and the DB.  You can't do that to an image.  I suspect there are issues with the inventory and QOS linkage for those devices now.

     

    Been there done that. 

     

    Note they need to be careful when they open that image for updates, they need to reinstall the Robot or make a backup copy of the Nimsoft folders after install then when the "seal" the image they delete the Nimsoft folder and copy the backup of the Cloud Robot install back in.



  • 7.  Re: Probes errors on PVS servers

    Posted Jan 10, 2018 05:00 PM

    Jay has the correct answer. Make sure the Cloud robot is reinstalled anytime the image is cracked open.