Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) ok, color me perplexed
So I'm grabbing the latest release of the mibs from Release-970709 on
ftp.ascend.com and going through them looking for some data (so far we've
yet to be sure we've seen a 56k connect, in fact the only thing I've seen on
the ascends so far is a 33.6) and I start looking, I find the following
[ slightly long but I wanted them ALL to be there]
mdmLineCapabilitiesV21 OBJECT IDENTIFIER ::= { mdmLineCapabilities 1 }
-- "ITU V.21"
mdmLineCapabilitiesV22 OBJECT IDENTIFIER ::= { mdmLineCapabilities 2 }
-- "ITU V.22"
mdmLineCapabilitiesV22bis OBJECT IDENTIFIER ::= { mdmLineCapabilities 3 }
-- "ITU V.22bis"
mdmLineCapabilitiesV23CC OBJECT IDENTIFIER ::= { mdmLineCapabilities 4 }
-- "ITU V.23CC"
mdmLineCapabilitiesV23SC OBJECT IDENTIFIER ::= { mdmLineCapabilities 5 }
-- "ITU V.23SC"
mdmLineCapabilitiesV25bis OBJECT IDENTIFIER ::= { mdmLineCapabilities 6 }
-- "ITU V.25bis"
mdmLineCapabilitiesV26bis OBJECT IDENTIFIER ::= { mdmLineCapabilities 7 }
-- "ITU V.26bis"
mdmLineCapabilitiesV26ter OBJECT IDENTIFIER ::= { mdmLineCapabilities 8 }
-- "ITU V.26ter"
mdmLineCapabilitiesV27ter OBJECT IDENTIFIER ::= { mdmLineCapabilities 9 }
-- "ITU V.27ter"
mdmLineCapabilitiesV32 OBJECT IDENTIFIER ::= { mdmLineCapabilities 10 }
-- "ITU V.32"
mdmLineCapabilitiesV32bis OBJECT IDENTIFIER ::= { mdmLineCapabilities 11 }
-- "ITU V.32bis"
mdmLineCapabilitiesV32terbo OBJECT IDENTIFIER ::= { mdmLineCapabilities 12 }
-- "ITU V.32terbo"
mdmLineCapabilitiesVFC OBJECT IDENTIFIER ::= { mdmLineCapabilities 13 }
-- "ITU V.FC"
mdmLineCapabilitiesV34 OBJECT IDENTIFIER ::= { mdmLineCapabilities 14 }
-- "ITU V.34"
mdmLineCapabilitiesV42 OBJECT IDENTIFIER ::= { mdmLineCapabilities 15 }
-- "ITU V.42"
mdmLineCapabilitiesV42bis OBJECT IDENTIFIER ::= { mdmLineCapabilities 16 }
-- "ITU V.42bis"
mdmLineCapabilitiesMNP1 OBJECT IDENTIFIER ::= { mdmLineCapabilities 17 }
-- "MNP1"
mdmLineCapabilitiesMNP2 OBJECT IDENTIFIER ::= { mdmLineCapabilities 18 }
-- "MNP2"
mdmLineCapabilitiesMNP3 OBJECT IDENTIFIER ::= { mdmLineCapabilities 19 }
-- "MNP3"
mdmLineCapabilitiesMNP4 OBJECT IDENTIFIER ::= { mdmLineCapabilities 20 }
-- "MNP4"
mdmLineCapabilitiesMNP5 OBJECT IDENTIFIER ::= { mdmLineCapabilities 21 }
-- "MNP5"
mdmLineCapabilitiesMNP6 OBJECT IDENTIFIER ::= { mdmLineCapabilities 22 }
-- "MNP6"
mdmLineCapabilitiesMNP7 OBJECT IDENTIFIER ::= { mdmLineCapabilities 23 }
-- "MNP7"
mdmLineCapabilitiesMNP8 OBJECT IDENTIFIER ::= { mdmLineCapabilities 24 }
-- "MNP8"
mdmLineCapabilitiesMNP9 OBJECT IDENTIFIER ::= { mdmLineCapabilities 25 }
-- "MNP9"
mdmLineCapabilitiesMNP10 OBJECT IDENTIFIER ::= { mdmLineCapabilities 26 }
-- "MNP10"
mdmLineCapabilitiesV29 OBJECT IDENTIFIER ::= { mdmLineCapabilities 27 }
-- "ITU V.29"
mdmLineCapabilitiesV33 OBJECT IDENTIFIER ::= { mdmLineCapabilities 28 }
-- "ITU V.33"
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:
{sample]
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.1 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesV21
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.2 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesV22
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.3 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesV22bis
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.4 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesV32
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.5 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesV32bis
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.6 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesV34
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.7 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesV42
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.8 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesV42bis
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.9 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesMNP4
mdmMib.mdmMIBObjects.mdmLineCapabilitiesTable.mdmLineCapabilitiesEntry.mdmLineCapabilitiesID.1.10 = OID: mdmMib.mdmMIBObjects.mdmLineCapabilities.mdmLineCapabilitiesMNP5
so we go look at my max again, just to be sure
[cut & paste]
| >V42/MNP=Will ^| | 12345678901234 | | 12345678901234
|
| Max Baud=33600 | | *************s | | *************s
|
| MDM Trn Level=-13 | +--------------------+
+--------------------+
| MDM Modulation=K56 | |20-100 1234567890 | |00-100 Sys Option
|
ok, our MDM modulation is K56, so what exactly am I missing here? 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 (if so then I think I should send all 20 or so we have
back to ascend and tell em to call me when they're not peddling trash) or...
One person in our office who shall remain nameless brought up the concept
that the whole Kflex thing with ascend is a hoax and they've had one over
the lot of us. While I don't think Ascend is THAT pathethic, it surely
wouldn't suprise me anymore.
--
and the Number 1 Sign You've Hired the Wrong Clown for Your Child's Party...
All the balloon animals are ribbed and lubricated.
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>