Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Re: OSPF question
> Since we've started using OSPF in our Maxen the following symptoms have
> cropped up:
>
> 1. Random reboots once every two weeks or so. Sometimes only a day,
> sometimes as long as three weeks.
>
> 2. OSPF dies with a memory allocation error, stopping OSPF. This error
> causes routing to stop working altogether, resulting in a MAX that
> takes calls and leaves the customer with a "dead" connection.
>
> #1 is painful but only irritating.
>
> #2 is simply unacceptable.
>
Yep, we see this too. Except our MTBF on #1 is a couple of days.
Ascend have now managed to duplicate the problem in their labs,
allegedly. Whether or not this means they'll deign to fix it is,
of course, another matter. Allegedly due to "duplicate routes"
(which I presume is a reference to a memory leak if your network
has more than one feasible route to any given destination).
If you are really lucky you can get it to do #3 (crash without
dumping core).
> Conversely, the PM3's we have don't seem to exhibit these symptoms at all.
Mmmm... If we find a bug is Cisco code like this, it gets fixed
or a workaround given within days. Ascend have had this
one plus instructions on how to repeat it for months. I don't
have much experience in bug reporting / fixing to USR,
but to be frank it couldn't be much worse and from what
I hear, it's a lot better. And yes, Ascend,
we have escalated it and escalated it and escalated it.
Once a week this results in a nice conference call where
they say "we're working on it". All very well, but the
fact they've been working on it so long without a fix
despite so many complaints does rather make one question
both their engineering resource and their attitude to
fixing customer problems.
Alex Bligh
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: