Thus spake Paul Farber
Anyone figure out why ALL modem failure reasons are always 0?
enterprises.usr.nas.mdm.mdmCs.mdmCsTable.mdmCsEntry.mdmCsConnectFailReason.1 = 0,
Well...not sure exactly what you're getting at here, but keep in mind that the mdmCs tree is for the current or last call. Basically, these values are reset at the beginning of each call, so if there is a call currently connected, the connectfailreason will be none because the current call didn't fail to connect. If the modem is idle, the connectfailreason will be none if the last call did successfully connect, but will be something different if the last call was a failed call. (Note...I haven't experienced this personally...going on my understanding of how the mib trees function within the TC equipment)
The reference chp 24 "Modem Disconnect and Fail to Connect Reasons" starts at drtDrop(1) and is only for the Quad modems????
Not sure what you mean by "is only for the Quad modems." I believe at least the 1.2.43 code has an off-by-error in it for these values...you have to subtract one from the value being reported via snmp to get the actual value from DSP's. I *think* the quads report it correctly (ie, not off-by-one) -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.