...
These fields will need to be transitioned to the peer, and all areas of the code which use them will need to be modified.
Tracked under:
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Router Ping
Gateways are pinged on a configured interval. If the Gateway is dead, then there is another configuration parameter which governs the frequency of the ping to determine if gateway is back up.
...
- Use the discovery mechanism instead of keeping the ping handling code.
- This will reduce the complexity of the router code significantly. All the lnet_rc_data, mdh, event handling will simply go away.
- When a response is received to the ping, the discovery code can simply check if the peer is a router and if so call a routing function to further handle the response.
- This code will need to ensure that this gateway is viable for all the routes which use it.
Tracked under
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Router Aliveness and Health
...
Using this proposal the router and gateway requirements will continue to be achieved, while at the same time, getting rid of lots of code which is currently used to keep track of the aliveness of the peer NIs.
Tracked Under:
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|