diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2021-10-13 12:40:35 -0400 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2021-10-13 12:40:35 -0400 |
| commit | 3766c36a209de3e33df05f71642664921d9cc6c5 (patch) | |
| tree | 231c0fff833517106fc6019bbc07cc690756bc78 /ospf6d/ospf6_interface.c | |
| parent | d7374bd3b1be5edfc20534ae5a301a0160c017bf (diff) | |
ospfd: Add `converged` and `role` json output for neighbor command
The `show ip ospf neighbor json` command was displaying
state:`Full\/DR`
Where state was both the role and whether or not the neigbhor
was converged. While from a OSPF perspective this is the state.
This state is a combination of two things.
This creates a problem in testing because we have no guarantee
that a particular ospf router will actually have a particular role
given how loaded our topotest systems are. So add a bit of json
output to display both the converged status as well as the
role this router is playing on this neighbor/interface.
The above becomes:
state:`Full\/DR`
converged:`Full`
role:`DR`
Tests can now be modified to look for `Full` and allow it to
continue. Most of the tests do not actually care if this
router is the DR or Backup.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'ospf6d/ospf6_interface.c')
0 files changed, 0 insertions, 0 deletions
