# Help with IPPING diagnostic

**URL:** <https://forum.genieacs.com/t/help-with-ipping-diagnostic/5814>\
**Category:** Uncategorized\
**Created:** [August 5, 2024, 1:45pm UTC](https://forum.genieacs.com/t/help-with-ipping-diagnostic/5814 "2024-08-05T13:45:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![akcoder](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/akcoder/32/11_2.png) [@akcoder](https://forum.genieacs.com/u/akcoder)\
**Post date:** [August 5, 2024, 4:54pm UTC](https://forum.genieacs.com/t/help-with-ipping-diagnostic/5814/2 "2024-08-05T16:54:38Z")

</div>

There are two ways of accomplishing this.

Create a provision which blindly refreshes any of the diagnostic nodes you use in your environment (IPPing, UDPEcho, Download, Upload). Use a preset which listens for the `8 DIAGNOSTICS COMPLETE` event to kickoff the provision. This is the easiest route.

The better approach requires a lot more work. You need to create a [v-param to track which diagnostic test was initiated](https://forum.genieacs.com/t/virtualparameters-with-index-instances/2556/2). Then, in the provision script, use the value of your vparam to determine which parameter to refresh. This is the approach I use.

---

_[View the full topic](https://forum.genieacs.com/t/help-with-ipping-diagnostic/5814)._