Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) 6.1.7 SNMP callStatusGroup woes
> I thought the variable to give was .1.3.6.1.4.1.529.11.5 but, after much
> frustration, found that it's actually .1.3.6.1.4.1.529.11.5.0
> Did I miss something somewhere, or did Ascend change something?
> ----------------------------8<-----------------------------
> # /usr/local/bin/snmpget -v 1 max-name community .1.3.6.1.4.1.529.11.5
> Error in packet.
> Reason: There is no such variable name in this MIB.
> This name doesn't exist:
> enterprises.ascend.callStatusGroup.callCurrentAnalogIncoming
> ----------------------------8<-----------------------------
It is normal for an object to have more than one instance; therefore,
you need to use the index number (in the above case, "0"). If you want
to find all possible instances, use snmpwalk to examine the whole list.
For example:
# snmpwalk -v 1 max community .1.3.6.1.4.1.529.11.5
You would use the same approach throughout MIB 1 and MIB 2.
t.
---------------------------------------------------------------------
Tony Porczyk * tony@infobound.com * www.infobound.com * San Jose, Ca.
GIT/ED d++(!d) s++:++ a? C++++ USB++++$ P+ E- W(--) N++ !k w--- M- V?
PS+++ PE++ Y+ PGP-- t+@ 5++ X-- R* b- D---- e* V-- h* r+++(*)+++(*)>?
---------------------------------------------------------------------
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: