Our company is serving connectivity to dozen international sites. We do have one office that particularly likes to be 'powered down' without any notice due to the regional conflicts (Middle East). It leads to creating events in router, that are then logged to SNMP server and after that they are described in monitoring tool (Spectrum) as a WAN alarms. As a workaround, whole site was disabled in monitoring tool (which does not affect any router configuration), but our Router A in events of OSPF alarms triggers separate major alarm titled 'OSPF NEIGHBOUR CHANGE STATUS'.
What is causing router to trigger proper alarm is OSPF trap below:
log number: date/date %OSPF-5-ADJCHG: Process 1, Nbr 10.150.31.1 on Tunnel100 from FULL to DOWN, Neighbor Down: Dead timer expired
As you can see, OSPF relationship was broken between Router A and B located X miles away from HQ. What we would like to achieve is to disable sending above message to SNMP server. We do NOT want to disable ALL OSPF traps because this router is responsible for multiple international sites so we could avoid little disaster.
I've tried 'no snmp link-status' under port interface (remember, it's Tunnel type interface) but there is only option to choose '0 or 1' meaning - we can only disable events if interface goes down. Which is not the case, tunnels and associated subinterfeces are always up - only OSPF session is broken.
Is there a possibility to perform such tasks? If yes, it should be configured on router (client) or SNMP manager?
We would like to exclude triggering 'OSPF NEIGHBOUR CHANGE STATUS' alarm when Tunnel100 lost his OSPF adjacency.
Inviting all network professionals in operations! We'd like to understand what would be valuable for you in a mobile application. Your response will help Cisco improve a product feature that could benefit you. Thanks!
Click here to take the sur...
Cisco’s software-defined wide area network (SD-WAN) solution allows user to quickly and seamlessly establish an overlay fabric to connect an enterprise’s data centers, branch and campus locations, as well as colocation facilities in order to imp...
1. Log into CLI of DNAC:
ssh maglev@< DNAC appliance IP> -p 2222
2. Run this curl command to get token to get member id:
curl -X POST -u admin:<admin user password> -H -V https://<CLUSTER-IP>/api/system/v1/identitymgmt/token
Enterprise Switching Business Unit is glad to announce Beta release 16.12.2 for all Catalyst 9200/9300/9400/9500/9600 and Catalyst 3650/3850 Platforms. This release is made available to allow users to test, evaluate and share fee...
Purpose of the document
This document describes the general recommendations or best practices when designing and deploying the Cisco SD-Access technology. The document assumes that the reader has a general overview of Cisco's SD-Access for Distributed C...