1-I have remote sites and main branch connection between remote sites to main branch is MPLS
2-Connection between main branch to remote sites over 2 ISP
I need real time monitor with out enable GRE tunnel between main branch to remote site
If the router down in remote site from any ISP I need the router will be reed
I need this action in topology map
I don't need this action by mail or by syslog
DFM monitors all devices in a Known state. If the devices are healthy (e.g. they are reachable, and have no down interfaces) then you will not see any alert for them in AAD. DFM is still managing and monitor those devices, though.
AAD only shows alerts. Devices which have no faults will not be shown in AAD. You can get a list of all devices DFM is managing under DFM > Device Management > Device Status. Any device in a Known state is being properly managed by DFM.
AAD automatically refreshes every 30 seconds. This cannot be customized.
AAD = Alerts and Activities Display
You can filter the output on the fly by clicking on the filter button at the top of the AAD screen. You can create custom filter groups by going to DFM > Configuration > Other Configurations > Alerts and Activities Defaults, and creating groups there.
The AAD will show alerts for ALL devices. An alert will appear for each device having a fault. The AAD can be filtered on device type, device names, and alert IDs. DFM, unlike the rest of LMS, has limitations on the number of supported ports and interfaces. If you only wanted to manage the two serial interfaces on 1300 devices (i.e. 2600 interfaces), you could do that all with one instance of DFM.
The Alerts and Activities Display is designed to be monitored by operators. It automatically refreshes. The polling interval is customizable, but by default, it is four minutes.
I do not understand the second question.
It depends on the interface type, but in general DFM manages all interfaces by default. To confirm if your interfaces are managed, go to DFM > Device Management > Device Details, and bring up the Detailed Device View on your devices. Check to make sure the managed state of your interfaces is true. If not, set the state to true, then go to DFM > Configuration > Polling and Thresholds > Apply Changes to apply the changes.
After that, DFM will poll the interfaces to make sure they are up. If they go down, you will get an alert under DFM > Alerts and Activities > Alerts and Activities. Within the Alert you will have an OperationallyDown event pertaining to each down interface.
If a device becomes SNMP unreachable, then Campus will detect that on its next Data Collection or polling pass. Campus Manager is NOT a fault management application, and its map is not updated in real time.
By default, the polling interval is every two hours. Campus 5.0 and higher has a critical devices poller which runs every five minutes by default. After that update runs, you may have to manually refresh the topology map. The N-Hop portlet should update based on your refresh interval.
If you see devices not getting updated with their status, make sure that they are actually becoming SNMP unreachable when Campus runs its Data Collection or polling cycle. If so, enable frontend, framework, core, and corex debugging under Campus Manager > Admin > Debugging Options > Data Collection. Wait for a new polling cycle or Data Collection to run, then look at the ani.log for errors.
All that said, it would be better to use a more real-time fault management application like DFM, HPOV Network Node Manager, NetView, etc. to let you know when this branch site goes offline.