The current command to restart any of the FRR processes is:
```
[email protected]:~$ restart frr
Possible completions:
<Enter> Execute the current command
bfdd Restart Bidirectional Forwarding Detection daemon
bgpd Restart Border Gateway Protocol daemon
ospf6d Restart OSPFv3 daemon
ospfd Restart OSPFv2 daemon
ripd Restart Routing Information Protocol daemon
ripngd Restart RIPng daemon
staticd Restart Static Route daemon
zebra Restart IP routing manager daemon
```
From a real-life example:
Two engineers needed 5 minutes to figure its under frr ;) thats why I would line to drop the frr level.
Its less intuitive to have `restart frr ospfd` or `restart frr bgpd` compared to `restart ospf`` and `restart bgp` - we have the same for `restart ipsec` and not `restart strongswan ipsec` - we should drop the FRR product name - maybe it will be another ruting engine in another release (edited)
I would also drop the `d`aemon suffix so the commands align with the VyOS CLI, else there would a missunderstandinc from ospf6d to ospfv3.
As CLI changes are now still fairly easy before launch of VyOS 1.3.0-epa1 I'd implement this in `equuleus` branch first and then cherry-pick to `current`