Re: Zebra & OSPF

[Paul Jakma]

On Thu, 8 Oct 2003, Kevin Benton wrote:

> Personally, my preference would be that all the daemons would
> handle their own configurations.

Yes, best for robustness. With the write config patch vtysh no 
longers interferes.

> If I'd had my wishes, zebra would have all the routing daemons
> embedded into it and run as one daemon instead of multiple
> independent daemons.

No. The multi-daemon aspect of Zebra is one of its greatest strengths 
IMO. It isolates problems. You can run an immature daemon to support 
$LATEST_ROUTING_PROTOCOL and crashes of said daemon will not affect 
your other daemons.

You can restart OSPF (eg after changing router id) without restarting 
the whole Zebra 'system'.

IMO it was an excellent design choice. (and other routing protocol 
suites have followed this approach, eg Bird and at least one other).

> That would make managing the system easier and help it really work
> more like a Cisco router.

Thats a seperate issue.

Try either Zebra with the write-config patch, or else (if Kunihiro 
will forgive me) Quagga (http://www.quagga.net) - for which there are 
RH9 RPMs available to download.

Note that for vty specific commands, eg 'line vty' and applying 
access-lists to vty, you still need to telnet to the daemon - vtysh 
wont handle that. However, thats something you need do only very 
rarely.

> For those that are working on their Cisco certifications, it would
> definitely make Zebra a tool to use to simulate another router.

try the write-config patch :)

regards,
-- 
Paul Jakma      address@hidden  address@hidden  Key ID: 64A2FF6A
        warning: do not ever send email to address@hidden
Fortune:
Any given program will expand to fill available memory.