Configure Traps for OSPF Neighbor Change on a XOS Switch

[Alexander_Bauer]

Hello,

how can i configure a trap for an ospf neighbor change?
Mib-View is added:
#configure snmpv3 add mib-view "All" subtree 1.0/00 type included

Other traps were reached by Netsight.

Thanks,
Alex

[Keith9 · Accepted solution]

It worked!
The command:
Enable snmp traps ospf all
on the switch paired with the netsight alarms configuration in my last posts screen shots did work. Around 1:12 am last night there was a small interruption in one of our WAN providers, which does happen from time to time in those AM overnight maintenance windows. I received 4 emails from Netsight stating ospf neighbor state change along with the IP endpoints, all of which are on that provider. Now I remoted in and traceroutes look normal so it must have been a quick maintenance item done by the ISP.

[Keith9]

I'm attaching two screen shots to visualize in netsight what I'm looking at. In the lower right corner there are colored blocks by severity. I would expect the OSPF messages to end up in here like other messages do.

I would also expect the events to email me as a test due to the alarm configuration. I know that when we first migrated to X690's in the core, our consultant helped setup so if a power supply or fan goes, we do get alerted. That works as we tested pulling a fan or power supply briefly to check the logs and alerts.

This is on the switch side and the netsight server is in fact 10.1.0.110.

enable cli-config-logging
configure syslog add 10.1.0.110:514 vr VR-Default local0
configure log target syslog 10.1.0.110:514 vr VR-Default local0 from 10.1.0.251
enable log target syslog 10.1.0.110:514 vr VR-Default local0
configure log target syslog 10.1.0.110:514 vr VR-Default local0 filter DefaultFilter severity Debug-Data
configure log target syslog 10.1.0.110:514 vr VR-Default local0 match Any
configure log target syslog 10.1.0.110:514 vr VR-Default local0 format timestamp seconds date Mmm-dd event-name none process-slot priority tag-id tag-name

One thing I chedked in sh configuration | i snmp, I see this line:
enable snmp traps configuration save

So I'm wondering what other traps there are. I did enable snmp traps ? and I see ospf is an option so I pick that and the options are all or trap-map. So I'm going to test this:
enable snmp traps ospf all

I don't know if that is the "missing link" that I need to complete this configuration but I hope its just that simple. I do not know how the hardware alerts are getting through because there is no enable snmp traps for hardware. Also we do get port up/down messages and I do not see enable snmp traps port-up-down in our config at all.

All assistance is greatly appreciated!

[PeterK]

Hi Keith,
were do you have checked for that messages in netsight? Only on Traps or even on Syslog?
show log & Netsight Syslog (not Traps) should have same entries, then severity level an so is configured same for logging sylog-server and local

[Keith9]

I have this configured in netsight to email me, but after hours yesterday I intentianally broke a link to generate a log to see if I would be alerted. The log generated on the X690 switch as seen in the sh log command, but in Netsight in the warning, info, error or critical sections that are notated and accessed from the lower right of the screen did not show anything excpet for common port up and port down messages for various things. Plus I was not emailed.

Here's some examples of what I cut and paste from the sh log command during my testing.

1/08/2019 17:27:53.18 Slot-1: Changing the state of neighbor rtid 192.168.255.4 ipa 192.168.100.2 to state = FULL due to Loading done.
01/08/2019 17:27:53.18 Slot-1: Changing the state of neighbor rtid 192.168.255.4 ipa 192.168.100.2 to state = LOADING due to exchange done event.
01/08/2019 17:27:53.13 Slot-1: Changing the state of neighbor rtid 192.168.255.4 ipa 192.168.100.2 to state = EXCHANGE due to negotiation done event.
01/08/2019 17:27:52.18 Slot-1: Changing the state of neighbor rtid 192.168.255.4 ipa 192.168.100.2 to state = EX_START due to AdjOK event.
01/08/2019 17:27:52.18 Slot-1: Changing the state of neighbor rtid 192.168.255.3 ipa 192.168.100.1 to state = DOWN due to inactivity timer expiry.
01/08/2019 17:27:52.18 Slot-1: Changing the state of neighbor rtid 192.168.255.3 ipa 192.168.102.1 to state = DOWN due to inactivity timer expiry.


And then coming back online:
01/08/2019 17:32:42.41 Slot-1: Changing the state of neighbor rtid 192.168.255.3 ipa 192.168.102.1 to state = 2WAY due to two way event.
01/08/2019 17:32:42.33 Slot-1: Changing the state of neighbor rtid 192.168.255.3 ipa 192.168.100.1 to state = 2WAY due to two way event.
01/08/2019 17:32:32.58 Slot-1: Changing the state of neighbor rtid 192.168.255.3 ipa 192.168.102.1 to state = INIT due to hello received.
01/08/2019 17:32:32.58 Slot-1: Changing the state of neighbor rtid 192.168.255.3 ipa 0.0.0.0 to state = DOWN due to new neighbor.
01/08/2019 17:32:32.58 Slot-1: Changing the state of neighbor rtid 192.168.255.3 ipa 192.168.100.1 to state = INIT due to hello received.
01/08/2019 17:32:32.58 Slot-1: Changing the state of neighbor rtid 192.168.255.3 ipa 0.0.0.0 to state = DOWN due to new neighbor.