Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) ok, color me perplexed
> mdmLineCapabilitiesBell208 OBJECT IDENTIFIER ::= { mdmLineCapabilities 29 }
> -- "Bell 208"
>
> Now I'd LOVE to assume that someone didn't bother to document the 56kFlex
> protocol in the mib but... a snmpwalk of my maxen leads me to believe its
> not there either:
I am not a SNMP guru, but I am not surprised that there is no "56K" defined.
The piece of the MIB you are examining is part of RFC 1696 "Modem Management
Information Base", not a vendor MIB and thus it should not be changed in a
vendor specific way that would be incompatible with other vendor's equipment.
And there is not "56K" in RFC 1696.
It is my understanding that Ascend would need to add something to the vendor
MIB - but maybe the Ascend SNMP experts can say something about the right way
to get to this information. [Yo! Ken Packert!]
I should point out that it seems to me like the information is available in
other ways. If you want to see what the speed is then check the SNMP Object
"mdmSCCurrentLineXmitRate". You can check the capabilities using "slotType"
to see what type of card you are using.
> Is it that Ascend has got their SNMP all *&*&^^&%ed up again (recount how
> many times this has happened) or perhaps their design is incapable of
> distinguishing higher connect rates
The Ascend MAX is certainly capable of distinguishing the values. Check
your RADIUS accounting logs for the "Ascend-Xmit-Rate" attribute. Since
56K technology is [currently] only fast downstream, the maximum value for
"Ascend-Data-Rate" has not changed. You can also check the information
reported with the Term Serv "show users" command. You can also check the
SNMP mdmSCCurrentLineXmitRate.
++ 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: