ospf_interfaces
Inspect OSPF interface settings and diagnose down links or missing adjacencies via mismatched MTU, timers, network type, area, cost, authentication, and neighbor states.
Instructions
Starts with wrong: what is wrong, for OSPF and interfaces, each with a text line (an interface down, an OSPF interface that faces a neighbor and has no adjacency with the values both ends must share and do not, a Full adjacency whose ends still differ); empty when nothing is. Then mismatches and hints (below), then the OSPF interface values per router as collected: MTU, hello and dead intervals, network type, area, cost, DR/BDR role, priority, passive, authentication (none / simple / md5) and neighbor counts. For a link it also gives the other end and mismatches: one line per value that must be equal for an adjacency but is not, e.g. "r1 eth1 MTU 1500 ⇔ r2 eth1 MTU 1400". mismatch_details has the same lines as fields, with odd_end: the router whose value differs from its own other OSPF interfaces while the other end matches its own (an inference, with a note; null when that does not decide it, and for area). A value the router did not report is null and is not compared; each interface also has the neighbor state there, and hints names a link stuck in ExStart / Exchange whose MTU was not reported. All routers, or one with router. Read-only.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "ospf_interfaces"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Same input as lab_state (optional here: the server was started with /app/demo/bgp-lp/frameB.json) | |
| router | No | Only this router, e.g. r1 (default: all routers) |