BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/22/2024
Smart Assurance - SMARTS
No affected releases provided.
No fixed releases provided.
False Smarts NPM OSPF Link Alarms received in Smarts SAM OSPF Link Down alarms appear in Smarts SAM for a device where both sides of the link seem operational on the device
The OSPF Link Down alarm as described above can be caused when a NeighborState2 attribute is found to have a value 'DOWN'. This "DOWN" status will appear when there are timeouts received from the endpoints, and the neighbor state is perceived as DOWN as a result.
To resolve this issue, you can change the SNMP polling timeout for the endpoints as follows:Run the following command from the Smarts command line:./sm_gui -c admin Enter the Smarts broker for the environment.Select the OSPF domain and connect to the domain.In the admin interface, click the Polling and Thresholds button.From the Polling and Thresholds window, expand the domain tree and expand OSPF Polling Groups.Click OSPF > OSPF SNMP Setting.In the Timeout Value field on the right side of the OSPF SNMP Setting window, increase the timeout value to 1400 (the default value is 700).Click the Apply button to apply the SNMP configuration change in the application.Click the Reconfigure button to deploy the SNMP configuration change in the system.