26 Mar
2016
26 Mar
'16
12:49 p.m.
Perhaps consider ways that RIP44 could be updated:
- to bootstrap one another in the case of a failure of
AMPRGW (election
of a master to send RIP44 announcements, participation in elections
disabled by default)
- allow possibility for addition of routes while
'acting AMPRGW' is
offline (re-elections with time-stamping/flagging)?
- ability to resume normal operations (AMPRGW is
automatically
elected/flagged/timestamps-recognized as master/signals send end of
elections)
Ideas?
This is all completely unnecessary.
The only thing you need to do to have redundancy in the RIP announcements
is setup another RIP announcer that gets the same database information and
sends the same announcements.
Currently they are sent at 5 minute intervals, an efficient solution would
be to modify the existing announce to use 10 minute intervals and setup a
second one to use 10 minute intervals with a 5 minute offset from the first.
When both are up, the users see no change. When one is down, the update
interval halves but everything remains running.
Rob