Smarts NPM/SAM: False OSPF Link Alarms received in Smarts SAM; Both sides of the link seem operational on a device that generates OSPF Link Down alarms
search cancel

Smarts NPM/SAM: False OSPF Link Alarms received in Smarts SAM; Both sides of the link seem operational on a device that generates OSPF Link Down alarms

book

Article ID: 304084

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:




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

Environment

VMware Smart Assurance - SMARTS

Cause

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.

Resolution

To resolve this issue, you can change the SNMP polling timeout for the endpoints as follows:

  1. Run the following command from the Smarts command line:

    ./sm_gui -c admin

     
  2. Enter the Smarts broker for the environment.
  3. Select the OSPF domain and connect to the domain.
  4. In the admin interface, click the Polling and Thresholds button.
  5. From the Polling and Thresholds window, expand the domain tree and expand OSPF Polling Groups.
  6. Click OSPF > OSPF SNMP Setting.
  7. 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).
  8. Click the Apply button to apply the SNMP configuration change in the application.
  9. Click the Reconfigure button to deploy the SNMP configuration change in the system.