Query on auto configured IP SLA operations

pratikmehta003

Hi All,

Have one query... Saw the below point in the admin guide:

Note: Modifying operations created with VNQM is possible only by using VNQM. If you modify an operation created by VNQM directly on the device, the changes will be overwritten by the IP SLA operation settings from VNQM.

Does this mean if network engineer makes changes on the device level then it will not automatically reflect in Orion??

foonly

I think it's a little more complicated than the manual suggests. I think this is a very important question.

In my experience, if you config via VNQM, it pushes commands to the devices only once. Assuming that the command push succeeds (and it does NOT tell you if it does not - you might only see a red operation when it does have the ability to login to the device, but the device IOS version does not support the operation you are attempting), you will see the commands in the device config.

If VNQM does indeed re-push the config, we need to know under what circumstances other than if we are using VNQM to edit the config - which I assume would indeed push new commands based on what VNQM has in its database - not what it sees on the device.

If you then edit the commands on the device manually, I don't think that VNQM detects it, nor does it re-push the commands. VNQM config will then not properly reflect what is configured on the device. The operations may or may not succeed, depending on what manual change you made.

If you want to manually edit the config on the device, I suggest doing the following:

1. Use VNQM to do the initial config, and make sure it works.
2. Download the config from the device(s), and copy the config lines into Notepad
3. Delete the operation(s) from VNQM
4. Download the config(s) again to make sure it deleted (I can't say for sure, but I think there's some situations where it might fail to remove all commands)
5. In Notepad, edit the command lines to remove the owner.
6. Change the operation number to something like a date/time - e.g. 2016020410 to create a fairly unique operation number.
7. Put the edited config(s) back on the device(s).
8. Discover the operations in VNQM
9. Make sure they work before you do any edits.
10. Every time you make an edit, do a rediscover.

It might be that you can edit the config that VNQM pushed, and do a rediscover, but I'm not sure. So I prefer to keep VNQM configured things with the owner stamp on them, and not edit them ever when that stamp exists. This lets me know who configured it, and to not touch it.

The problem is that Cisco is incredibly inconsistent from model to model and version to version with what operations they support, and what subcommands exist. I don't know of any feature matrix for this that would make SolarWinds or your job easier,

Anyone have other thoughts on this?

=seymour=