Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts NPM: OSPFNeighborRelationship event triggered (359101)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3177Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

There are at least two reasons why this event would be triggered. This article aims to help you investigate and troubleshoot both reasons.

The two reasons are:
A: OSPFNeighborRelationship event triggered when device on one side of relationship no longer in OSPF topology
B: The OSPFNeighborRelationship event is triggered when there is a duplicate IP address seen using the dxa-topology-sync.asl Script.

Cause

The neighbor is not part of the OSPF areas or there is a duplicate IP address in the neighbor relationship.

Resolution

1: Configure OSPF neighbor correctly by removing device that is no longer on network from configuration of device remaining in repository. If correctly configured SMARTS OSPF domain will prune the Neighbor connection to a half link.

2: Remove the duplicate IP address.

Related Information

A: The neighbor is not part of the OSPF Areas.

Remove only the OSPF Device (e.g device1/81.144.19.216) remaining in SMARTS repository still configured to be the neighbor of device (10.1.1.1. This is an Example notification where 10.1.1.1 is no longer in OSPF SMARTS repository :

OSPF-NBR-device1/2 [Fa0/1] [81.144.19.216] [PoP LAN2 vcat2 port 6/14, CN1011]-81.144.19.216->10.1.1.1

To verify correct OSPF configuration on device:

1. If it's a Cisco device, check OSPF configuration using CLI by running "show ip ospf neighbors". Example output below may list device (e.g 10.1.1.1) no longer in repository configured as an OSPF Neighbor :

device1#show ip ospf neighbor

81.144.126.126 10 2WAY/DROTHER 00:00:14 10.1.1.1 FastEthernet0/1

81.144.126.127 10 2WAY/DROTHER 00:00:12 81.144.19.213 FastEthernet0/1

2. Carry out a sm_snmpwalk of the OSPF MIB on the device remaining in the repository (e.g 81.144.19.216) to verify if the device removed (e.g 10.1.1.1) from the repository is still present in the MIB, Example output below :

smarts1#sm_snmpwalk --oid=.1.3.6.1.2.1.14.4.1 smarts

SNMP version v2c is not supported; trying SNMP version v1 ...
Saving MIB walk to file(s) smarts.walk' 'smarts.mimic' 'smarts.snap' ...
End of MIB walk

smarts#more smarts.snap

.1.3.6.1.2.1.14.4.1.1.3.8.0.1.1.81.144.17.77.10.1.1.1 IP-ADDRESS 03080001
.1.3.6.1.2.1.14.4.1.1.3.8.0.1.1.81.144.17.78.81.144.17.78 IP-ADDRESS 03080001
.1.3.6.1.2.1.14.4.1.1.3.8.0.1.1.81.144.17.79.81.144.17.79 IP-ADDRESS 03080001
.1.3.6.1.2.1.14.4.1.1.3.8.0.1.1.81.144.17.80.81.144.17.80 IP-ADDRESS 03080001
.1.3.6.1.2.1.14.4.1.1.3.8.0.1.1.81.144.17.128.81.144.17.128 IP-ADDRESS 03080001
.1.3.6.1.2.1.14.4.1.1.3.8.0.1.1.81.144.17.129.81.144.17.129 IP-ADDRESS 03080001

B: A duplicate IP address in the neighbor relationship will cause this.
If you suspect this may be the case, you will see this type of message in your NPM domain log:

dxa-topology-sync.asl: [YYYY-ICR5] 'IP::IP-10.244.255.134' mapped to 'DuplicateIP::IP-10.244.255.134'
XXXX-OSPF_en_US_UTF-8.log(525595): June 16, 2016 10:08:07 AM GMT+00:00 +789ms 7088505 3635456320 WARN Discovery #3 DXA_MESSAGE-DXA_ECLASSMAPPED dxa-topology-sync.asl: [YYYY-ICR6] 'IP::IP-10.244.255.134' mapped to 'DuplicateIP::IP-10.244.255.134'
XXXXX-OSPF_en_US_UTF-8.log(619027): June 17, 2016 6:07:34 AM GMT+00:00 +539ms 8623133 3629152576 WARN Discovery #8 DXA_MESSAGE-DXA_ECLASSMAPPED dxa-topology-sync.asl: [AMER-ICR5] 'IP::IP-10.244.255.134' mapped to 'DuplicateIP::IP-10.244.255.134'

The resolution here is to speak with your network admin about having the duplicate device removed.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant