Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies replies
    3
  • Subscribers subscribers
    177
  • Views views
    460
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Exclusively agent driven flow - how to change probe names?

Tim Macaleese

Test upgrade of data flow probe, changed probe name.

Some existing discovery status of scan files from Inventory of scan file job start reporting errors "cannot find probe 'oldProbeName' Task for TriggerCI will not be created". I searched and found an old post talking about IPs and running discovery jobs to update IPs but ours is exclusively UDA agent driven flow (uploading scan files), no other discovery jobs.

Is there a way to tell discovery that the new probe name is taking over for the old probe name?

Parents

  • Verified Answer

    +1  

    There are two tasks that you would need to do if you change the name of a probe

    Before the change

    • The agent needs to know the name of the new probe it communicates with

    After the change

    • Delete the scan_file CIs whose LastDiscoveredByProbe is equal to "old-probe-name".  This is afe since the proper sca_file CIs would be created using the new probe

Reply

  • Verified Answer

    +1  

    There are two tasks that you would need to do if you change the name of a probe

    Before the change

    • The agent needs to know the name of the new probe it communicates with

    After the change

    • Delete the scan_file CIs whose LastDiscoveredByProbe is equal to "old-probe-name".  This is afe since the proper sca_file CIs would be created using the new probe

Children
  • 0 in reply to   

    Thank you for this information, Bill. Am I to understand, then, that in a scenario where a probe is decommissioned and deployed UDAs configs updated to point to new probe DNS/IP, or a probe is renamed but keeps the same DNS/IP, that the only way to resolve the errors is to delete the affected scan file CIs? Also, is there a way to delete the scan file CIs through the HTML5 CMS UI standalone interface, or is this still requiring the use of the Java client?

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.