Adj down isn't monitored by OSPF domain
search cancel

Adj down isn't monitored by OSPF domain

book

Article ID: 423890

calendar_today

Updated On:

Products

VMware Smart Assurance Network Observability

Issue/Introduction

  • Device is present is OSPF domain, but all adjacencies are not getting monitored.
  • OSPF Neighboring endpoints not getting created

Environment

All supported release of Smarts

Cause

The OSPF interface underlying IPs are unmanaged in environment and hence it did not pass through the DXA conf ( dxa-am.conf and dxa-am-v4v6.conf under <BASEDIR>/NPM/smarts/conf/ospf) we can see that there is a condition to import only managed devices. 

class   IP
in      TopologyCollection      ConsistsOf      OSPF-IP
peek    IsManaged    TRUE
attr    DisplayName
attr    SystemName              DeviceName
attr    Address
attr    Netmask
attr    Tag
rel     Underlying

Resolution

Once these IP's are managed, it should get imported to the OSPF domain and build the relationship.