Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Ap33 Warnings
Unless, of course, they are immediately follwed by route loss? Win95
problems. Pakcets go in, but they never come out!(Ticket #158733) Only
happens on on the 4048s...
On Tue, 4 Nov 1997, Kevin Smith wrote:
> At 07:23 AM 10/31/97 -0500, Chris A. Epler wrote:
> >
> >WARNING: Index: 179 Load: tik.m40 Revision: 5.0Ap33
> > Date: 10/30/1997. Time: 19:57:22
> > Location: b00cc998 b00c7ed4 b007abe8 00000000 00000000 00000000
> >...
> >
> >WARNING: Index: 179 Load: tik.m40 Revision: 5.0Ap33
> > Date: 10/31/1997. Time: 02:50:10
> > Location: b00cc998 b00c7ed4 b007abe8 00000000 00000000 00000000
>
> The notes for this release are being modified to say something to the effect:
>
> Note: This warning provides additional information that can be safely
> ignored unless it is followed immediately by a MAX reset (e.g. FE 1).
>
>
> Kevin
>
>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
>
++ 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: