Can IPM report on IP SLA ops it didn't configure?

[yjdabear]

IP SLA monitors are configured via CLI manually or NetConfig, rather than through IPM itself, can it pick those up for reporting only?

[yjdabear]

All the ops have always been configured with "ip sla monitor schedule [#] start-time now". Shouldn't they be perpetual?

[Joe Clarke · Accepted solution]

Not unless you specify "life forever" as well. Else, it will only be active for 3600 seconds.

[yjdabear]

Another unexpected phenomenon: All the IP SLA configs have disappeared on the import source device. Were the configs removed as a result of the IPM importcollector process?

[Joe Clarke · Accepted solution]

Yes. By default, IPM does not push the collector configs to the running config. You can enable this by checking the "Copy IPSLA Configuration to running-config" box under IPM > Admin > Application Settings.

[yjdabear]

I'm not sure I follow. In this case, it's the reverse: NMSROOT/bin/ipm seemed to have removed every "ip sla *****" line from the running-config, after it's done importing. Would ticking a box in the GUI change the behavior of "ipm importcollector" as well, so it stops removing running-configs (or rather, remove anyway then put back)?

[Joe Clarke]

Yes, it should allow IPM to retain them in the running config once it assumes ownership.