A good solution however should care about all of them. I may as well be interested in graphing certain dial-on-demand customer links. > The routine around here is: Max resets (pick a reason). Tech finds what T1 > profiles moved where and tells our SNMP bandwidth graphing app about it. > Repeat. > > Gets old. And is not really necessary. I would state here: 1) Ascends way of profile oriented setup vs. other vendors interface oriented setup is IMHO a progress. It makes a lot things easier and is the key to manage a larger NAS without extreme overhead. I would by no means request them to change _this_. This even includes the ifIndex jumping. The problem is not exactly with the ifIndex jumping but with the NMS which a) blindly adhere to Link == Interface philosophy b) cannot ask the Ascend box indirectly which ifIndex to use where b) is also an Ascend problem because the MIB for a long time was not capable of providing a trivial way for the NMS to do this. 2) Starting with 5.0A it is possible to automate the above. I've posted an example here on the list that marriages Ascend leased lines with MRTG. I will adapt this to the WAN MIB ASAP (6.0b site is already loaded ;) and will implement MPP bundles then as well (and if it is not too hard also dialed connections). It is a bit of overhead but could as well be implemented within MRTG itself like Target[uplink]: ascend-profile%isp-link:public@ourmax but I'm not the perl freak to do this (is Dave still around here ?). 3) I could imagine that leased lines get assigned to the first ifIndexes in profile order during startup. I could as well imagine specifying that I want them to have static ifIndexes in certain profiles. But IMHO a short and flexible way to crossref between profile name, IP address of the destination, slot/port and ifIndex is by far the best solution even if it requires some additional code on the NMS side. 4) The IETF has no clear concept. One ifIndex per VC is stupid. It allows old (stupid) NMS software to deal with an NAS as with a 2 fixed interface router, but at what price... -- Kanther-Line: PGP SSH IDEA MD5 GOST RIPE-MD160 3DES RSA FEAL32 RC4 +-o-+--------------------------------------------------------+-o-+ | o | \\\- Brain Inside -/// | o | | o | ^^^^^^^^^^^^^^ | o | | o | Andre' Beck (ABPSoft) beck@ibh-dd.de XLink PoP Dresden | o | +-o-+--------------------------------------------------------+-o-+ ++ 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="msg11081.html">(ASCEND) Re: SNMP Interface representation</A></STRONG></LI> <UL> <LI><EM>From</EM>: Peter Lalor <plalor@infoasis.com></LI> </UL> </UL> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg11433.html">(ASCEND) Is the list having a problem?</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg11432.html">(ASCEND) 5.0ap36 comments</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg11107.html">Re: (ASCEND) Re: SNMP Interface representation</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg11480.html">Re: (ASCEND) Re: SNMP Interface representation</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail2.html#11434"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd255.html#11434"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>