Log OSPF Adjacency Changes


Logging changes to the BGP peering relationships is recommended.


Any logged changes in a routing peer relationship will in the best case indicate a service issue due to standard operational issues (connectivity issues and so on) or in the worst case, could indicate malicious activity attempting to subvert the peering relationship and/or the routing table.


Errors on adjacency relationships are a common early warning message in attacks on routers. If successful, a malicious actor can advertise bogus routes to valid hosts or networks, allowing the interception and modification of traffic intended for those hosts or subnets.

For this reason it is important that OSPF endpoints alert on any interruptions in adjacency.


Enabling the logging of adjacencies is a single line in the OSPF process section. It is globally applied to all OSPF neighbors.

switch(config)# router ospf <Process tag>
switch(config-router)# log-adjacency-changes

Default Value:

By default changes in OSPF adjacencies are not logged.

See Also


Item Details


References: 800-53|CM-6, CSCv7|11

Plugin: Cisco

Control ID: 5f9d47414968ff185da9d6798de7b03fcdbd6881720cf318f444387dcda56f8b