I have selected DNA as a replacement of CISCO Prime for several reasons. The first one is that Cisco Prime is a death path, and it will not receive upgrades and new features in the future. Additionally, I need to address the three use cases already mentioned and it seems that CISCO Prime is able to properly answer these questions:
- Treatment of messages/alarms/events caused by a scheduled preventive task on a network device (e.g. a switch). Is it possible to tag as “maintenance” the messages/alarms/events raised by a network device when the device is subject to a scheduled preventive task?. If not, at least, can we filter the messages received from a network device under a maintenance task so that those messages are not displayed to the user.
- If a network device is continuously generating communication errors, is it possible to switch off the device, either, automatically by defining a matching rule (e.g. after 20/30 messages of the same type originated from the same device, switch the device off), or by hand, by the user on demand from the network management appliance, in this case DNA ?.
- Concurrent changes on a network device from the local console and from the network management appliance (DNA9. If a technical manager connects locally to the console port of a device, and at the same time the device is being managed from the network management appliance, how can we control concurrent access ?. Can the local user block the network device while he/she is making some changes, avoiding that another user can perform changes using the network management appliance?. Can the user, who is working with the network management appliance, block the network device while he/she is making some changes, avoiding that another user can perform changes via the device console port ?.
