Warning 185 indicates that the Spyder ship posted an error (HDLC controller). This in itself does not cause a reset though...there may have been other causes for the reset. There were some resets with no Fatal Errors fixed in the 4.6B branch by 4.6Bp28....the latest version in that branch is 4.6Bp31. NOTE: the 4.6B branch does not include support for the new K56flex modems. Kevin Smith Updated Service and Support Ascend Communications Resources are now at: <A HREF="http://www.ascend.com/service">http://www.ascend.com/service</A> ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.shore.net/~dreaming/ascend-faq">http://www.shore.net/~dreaming/ascend-faq</A>> or <<A HREF="ftp://ftp.shore.net/members/dreaming/ascend-faq.txt">ftp://ftp.shore.net/members/dreaming/ascend-faq.txt</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <HR> <STRONG>References</STRONG>: <UL> <LI><STRONG><A HREF="msg00183.html">(ASCEND) MAX 4000 rebooting with fatalhistory reporting Index 185</A></STRONG></LI> <UL> <LI><EM>From</EM>: "Davar, Vikram" <vikram.davar@gs.com></LI> </UL> </UL> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg00290.html">Re[2]: (ASCEND) Disabling internal-NT1 on Ascend P50 UBRI</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg00288.html">RE: (ASCEND) Run-away debugging! (fwd)</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg00264.html">Re: (ASCEND) MAX 4000 rebooting with fatalhistory reporting Index 185</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg00184.html">(ASCEND) 5.0Ai10 breaks route table</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail2.html#00289"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd8.html#00289"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>