(ASCEND) MRTG with BSTDX-8/9000

[Michael Ferioli <mferioli@isdnet.net>]

I am having great difficulty getting MRTG to query CERTAIN MIB
variables on my Cascade/Ascend BSTDX's.  And, of course, the 
most important MIB variables (cktInOctets, etc.) are the ones 
I can't get.

But I *CAN* get others.  For example, I can get the following:

1.3.6.1.4.1.277.1.3.22.0
1.3.6.1.4.1.277.1.3.24.0
1.3.6.1.4.1.277.1.4.2.1.16.slot.port (InOcttes for a physical port)
1.3.6.1.4.1.277.1.4.2.1.20.slot.port (Outoctes for a physical port)

I CANNOT get:

1.3.6.1.2.1.10.32.2.1.9.if.dlci  (InOctets for a PVC)
1.3.6.1.2.1.10.32.2.1.7.if.dlci  (OutOctets for a PVC)

I have hacked away at the MRTG code and have realized that the
Cascade is sending a NULL reply to these queries.  In other
words, there is a timing loops with a fallback routine.  It
only goes through the loop once, receives a NULL response and
exits.  I'm not sure if this is normal behaviour when a box
does not understand an snmpget.

Anyone offer any help?

Mike
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

Follow-Ups:

• Re: (ASCEND) MRTG with BSTDX-8/9000
• From: Jason Ackley <jason@viaccess.net>

---

• Prev by Date: Re: (ASCEND) dns server negotiation?
• Next by Date: Re: (ASCEND) Max flooding our ethernet backbone
• Prev by thread: (ASCEND) Need Help on OSFP for MAX400
• Next by thread: Re: (ASCEND) MRTG with BSTDX-8/9000
• Index(es):
  • Main
  • Thread