nanog mailing list archives
Re: Whats so difficult about ISSU
From: Mikael Abrahamsson <swmike () swm pp se>
Date: Mon, 12 Nov 2012 08:29:59 +0100 (CET)
On Mon, 12 Nov 2012, Bryan Fields wrote:
And they only have to process maybe 2mbit/s of control traffic during busy hour. The rest is handled by dedicated hardware/ASIC's. Each one has a fully redundant hardware circuit pack and a bunch of monitoring to switch over in case one fails.
I'd imagine it's also because some are written in a language especially designed for the task.
http://en.wikipedia.org/wiki/Erlang_(programming_language)"... It supports hot swapping, so that code can be changed without stopping a system.[2]"
I've been told some people are doing routing control plane implementations in erlang just because of these features, but I'd imagine there is a hurdle getting enough programmers who are experienced in the language.
-- Mikael Abrahamsson email: swmike () swm pp se
Current thread:
- Re: Whats so difficult about ISSU, (continued)
- Re: Whats so difficult about ISSU Phil Regnauld (Nov 11)
- Re: Whats so difficult about ISSU Joe Greco (Nov 11)
- Re: Whats so difficult about ISSU Felipe Zanchet Grazziotin (Nov 11)
- Re: Whats so difficult about ISSU Gary Buhrmaster (Nov 11)
- Re: Whats so difficult about ISSU Gary Buhrmaster (Nov 11)
- Re: Whats so difficult about ISSU Miquel van Smoorenburg (Nov 11)
- Re: Whats so difficult about ISSU Jimmy Hess (Nov 11)
- Re: Whats so difficult about ISSU Kasper Adel (Nov 11)
- Re: Whats so difficult about ISSU Bryan Fields (Nov 11)
- Re: Whats so difficult about ISSU Mikael Abrahamsson (Nov 11)
- Re: Whats so difficult about ISSU Tim Jackson (Nov 12)
- RE: Whats so difficult about ISSU Frank Bulk (Nov 12)