>No the Max does not send a trap with each session. That is a Cisco thing. >We send a start and stop record via Radius or Tacacs+. Alternately, we >record each event in an Event MIB. A trap is not the proper mechanism - >it was not intended to be used in such a high volume environment. Ok, thanks. I do not want to implement something `outside the specs' :-) Christian Vogel Buergernetz Neumarkt * <A HREF="http://www.bene.baynet.de">http://www.bene.baynet.de</A> Consider yourself disclaimed! ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <HR> <STRONG>References</STRONG>: <UL> <LI><STRONG><A HREF="msg10829.html">RE: (ASCEND) SNMP-Traps for Session Up/Down</A></STRONG></LI> <UL> <LI><EM>From</EM>: Ken Packert <kpackert@ascend.com></LI> </UL> </UL> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg10873.html">Re: (ASCEND) linux snmp recommendations?</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg10874.html">Re: (ASCEND) 5.0Ap33 woes ....</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg10836.html">RE: (ASCEND) SNMP-Traps for Session Up/Down</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg10835.html">RE: (ASCEND) SNMP-Traps for Session Up/Down</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail2.html#10872"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd246.html#10872"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>