This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

NCM Alert Action on different device

FormerMember
FormerMember

I am monitoring an IPSec tunnel where the alert is triggered on high latency to the other side. What I am trying to do is setup a NCM alert action that will run traceroute on the router on our side of the link every time a latency threshold is passed.

Now I can do the alert and the traceroute command, etc, but cannot specify the device on which to run the script. It looks like NCM tries to execute it on the remote device over which we have no control.

Can anyone suggest how this can be achieved.

 

Thanks

George

  • Is this an NCM alert or an NPM alert? You're monitoring for interface latency, right?

  • FormerMember
    0 FormerMember in reply to mrxinu

    This is an NPM alert and I am actually monitoring device latency as I do not have SNMP access to the remote device (ie, just pinging the external IP of the other side)

    I have used a workaround at the moment, where I launch an external program (powershell script) that will ssh into the router execute the commands required and e-mail the results.

    Ideally I would like to be able to do it through an NCM action as that returns the results in the ${Notes} variable and can be progressed through the normal alert escalation process.

     

    Thanks

    George

  • Have you looked at the NCM action options in the Advanced Alert Manager?

  • FormerMember
    0 FormerMember in reply to mrxinu

    There is not a whole lot of options under the NCM action unless I am missing something here. I select an NCM action, select to execute a config script and put in the commands but that doesn't allow me to specify the device on which I want to execute the script.

    Now, I've looked through the documentation but there is nothing there that allows you to select a device. I presume the NCM action will get executed against the device that raised the alert which is not what I am trying to achieve here.

    Thanks

    George

  • Ah, I see what you're saying. The workaround you're using sounds like the way you need to go. Maybe post the scenario in the feature request section and see if they'll come back with some more flexibility.

  • This ability to choose which device to perform the NCM action sounded obvious to me when i first heard about this NPM integration. We need it and we'll be looking forward to see this important improvement on the next versions.