No Subject

Sure there is.  It's when the damn thing decides its *tired* of routing all
this data, and just stops until someone ELSE reboots it.  At least when
it's rebooting itself, its not requiring human intervention.

On that note, the OSPF failure would be a lot less annoying if there was
anyone have it monitored.  We have automatic monitors on every machine on
our network and know within 2 minutes if anything goes down, but when a MAX
stops routing, we don't know until a customer complains or we do a manual
check of each one.

Rob Wynne
Technical Coordinator
ISP Alliance, Inc.
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	&lt;<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>&gt;

</PRE>
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<HR>
<STRONG>Follow-Ups</STRONG>:
<UL>
<LI><STRONG><A HREF="msg03852.html">Re: (ASCEND) Re: Re: OSPF question</A></STRONG></LI>
<UL>
<LI><EM>From</EM>: "Alex.Bligh" &lt;amb@xara.net&gt;</LI>
</UL>
</UL>
<!--X-Follow-Ups-End-->
<!--X-References-->
<STRONG>References</STRONG>:
<UL>
<LI><STRONG><A HREF="msg03807.html">(ASCEND) Re: Re: OSPF question</A></STRONG></LI>
<UL>
<LI><EM>From</EM>: Peter Lalor &lt;plalor@infoasis.com&gt;</LI>
</UL>
</UL>
<!--X-References-End-->
<!--X-BotPNI-->
<HR>
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg03839.html">Re: (ASCEND) MAX4000: no trunk available</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg03838.html">Re: (ASCEND) Debug mode on MAX TNT</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg03809.html">(ASCEND) Re: OSPF question</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg03852.html">Re: (ASCEND) Re: Re: OSPF question</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="maillist.html#03840"><STRONG>Main</STRONG></A></LI>
<LI><A HREF="thrd148.html#03840"><STRONG>Thread</STRONG></A></LI>
</UL>
</LI>
</UL>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</BODY>
</HTML>