OSPF neighbor(s) down for Juniper




Indeni will alert if one or more OSPF neighbors isn't communicating well.

Remediation Steps

Review the cause for the neighbors being down.

1. Run the "show ospf neighbor" command to view the current state of OSPF neighbors.
2. Run the "show configuration protocol ospf" command to view OSPF configuration.
3. If no OSPF neighbor is shown, please check the following items:
a. physical and data link connectivity
b. mismatched IP subnet
c. subnet mask
d. area number
e. area type
f. authentication
g. hello and dead interval
i. network type
4. It's normal for DR-other neighbors to be stuck in two-way state.
5. If the OSPF neighbor is stuck in Exstart/Exchange State, check mismatched IP MTU.
6. Consider configuring traceoptions to track the OSPF operations.
7. Review the following articles on Juniper TechLibrary for more information:
a. Example: Configuring OSPF Trace Options
b. OSPF is in '2 Way' state with some neighbors and "Full" with others
8. If the problem persists, contact the Juniper Networks Technical Assistance Center (JTAC).

How does this work?

This script logs into the Juniper JUNOS-based device using SSH and retrieves the output of the "show ospf neighbor" command. The output includes the status of active OSPF neighbors (but not those that are missing).

Why is this important?

Due to the dynamic nature of OSPF, it should be closely monitored to verify that it is working correctly. Since routing is a vital part of any network, a failure or issues in dynamic routing can cause large disruptions.

Without Indeni how would you find this?

An administrator could login and manually run the command. SNMP traps and syslogs are also available to be aware of an OSPF issue.

View Source Code