Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Q: Status of OSPF in 5.0Ap36
> A definite plus if you are just making config changes,
> and it certainly couldn't hurt in other situations.
> The two most common ways I see OSPF fail are:
> 1> crash and reboot the max
> 2> crash and just stop
>
> right now #2 requires a reboot, if they can correct that,
> or even have a watchdog that restarts OSPF automagicly,
> were at least 50% better off, but I won't even guess how difficult
> it would be to make sure all OSPF memory is dealocated,
> all processes get killed, etc., in order to restart it.
If it's any consolation, first indications would seem to show Ascend
have fixed 1 & 2 in the code that went into Ap42. We were really
suffering from this. However I don't know whether they have fixed the
other bizaro ones like a route getting stuck in OSPF inserted from
something misconfigured which you can't get rid of without clearing
the box. Having worked with Ascend (Global Internet that is) on getting
the bugs fixed on Ap42, I'd certainly vote for a "restart routing process"
function (and no switching OSPF off and on doesn't seem to cure it,
or at least didn't pre Ap42).
--
Alex Bligh
GX Networks (formerly Xara Networks)
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: