[DISPATCH-147] Failure to re-sync routes after processes suspended and resumed

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Backlog
• Component/s: Routing Engine
• Assignee: Unassigned
• Reporter: Ted Ross
• Created: 24/Jun/15 16:05
• Updated: 03/Apr/18 17:37

Description

Seen once.
I ran the 6-node scenario for a demonstration on my laptop. After suspending the laptop and reopening it later, the processes were all running but one node (node Y in the test topology) wasn't getting its link state to remote, non-neighbor, routers. This erroneous state was stable and did not recover.