Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) modem speed discrepancy
// When a user connects using a 56k modem in windows 95, he gets a message that states that he is connected at 44k or 48k, but the detail log only shows that he is connected at 31.2K. What is the deal? Do I need to go to a higher version of Radius? Anyone have this problem?
Not sure, we've virtually no 56k modems in use by the customers yet.
What does the SNMP tell you? If you happen to have a UNIX/CMU SNMP/Perl combination handy, try this:
#!/usr/bin/perl
@Modems=`snmpwalk euro.thl public mdmMib.mdmMIBObjects.mdmLineTable.mdmLineEntry.mdmLineState`;
foreach (@Modems) {
/([0-9]+)\s=\s([a-zA-Z]+)/;
$State{$1}=$2;
}
@Modems=`snmpwalk euro.thl public mdmMib.mdmMIBObjects.mdmStatsTable.mdmStatsEntry.mdmStatsIncomingFailures`;
foreach (@Modems) {
/([0-9]+)\s=\s([0-9]+)/;
$Fail{$1}=$2;
}
@Modems=`snmpwalk euro.thl public mdmMib.mdmMIBObjects.mdmStatsTable.mdmStatsEntry.mdmStatsIncomingCompletions`;
foreach (@Modems) {
/([0-9]+)\s=\s([0-9]+)/;
$Comp{$1}=$2;
}
@Modems=`snmpwalk euro.thl public mdmMib.mdmMIBObjects.mdmSCTable.mdmSCEntry.mdmSCCurrentLineXmitRate`;
$TotalFail=$TotalComp=$Total=0;
foreach (@Modems) {
/([0-9]+)\s=\s([0-9]+)/;
$Xmit{$1}=$2;
print "Modem number $1 is $State{$1}";
print " at $Xmit{$1}" if($State{$1} eq 'connected');
if(($Fail{$1}+$Comp{$1})>0) {
print ". Failures $Fail{$1} out of ", $Fail{$1}+$Comp{$1}, ", ", (int(($Fail{$1}/($Fail{$1}+$Comp{$1}))*10000))/100, "%";
}
print "\n";
$Total++ if($State{$1} eq 'connected');
$TotalFail+=$Fail{$1};
$TotalComp+=$Comp{$1};
}
print "\nTotal connected: $Total\nFailures: $TotalFail of ",$TotalFail+$TotalComp,", ",((int($TotalFail*10000/($TotalFail+$TotalComp)))/100), "%\n\n";
# SCRIPT ENDS
While we're on the subject, that script used to tell me all about the 24 modems we have. Now it tells me about the 32 modems we don't have. We still have 24. There are only 24 in use:
Modem number 1 is onHook. Failures 6 out of 97, 6.18%
Modem number 2 is connected at 33600. Failures 3 out of 82, 3.65%
Modem number 3 is onHook. Failures 2 out of 91, 2.19%
Modem number 4 is onHook. Failures 5 out of 101, 4.95%
Modem number 5 is connected at 33600. Failures 6 out of 89, 6.74%
Modem number 6 is onHook. Failures 2 out of 95, 2.1%
Modem number 7 is connected at 33600. Failures 5 out of 93, 5.37%
Modem number 8 is onHook. Failures 5 out of 84, 5.95%
Modem number 9 is connected at 28800. Failures 4 out of 100, 4%
Modem number 10 is connected at 28800. Failures 5 out of 83, 6.02%
Modem number 11 is unknown
Modem number 12 is unknown
Modem number 13 is connected at 28800. Failures 4 out of 90, 4.44%
Modem number 14 is onHook. Failures 5 out of 97, 5.15%
Modem number 15 is unknown
Modem number 16 is unknown
Modem number 17 is connected at 33600. Failures 3 out of 88, 3.4%
Modem number 18 is onHook. Failures 5 out of 96, 5.2%
Modem number 19 is onHook. Failures 1 out of 89, 1.12%
Modem number 20 is connected at 31200. Failures 0 out of 107, 0%
Modem number 21 is onHook. Failures 3 out of 97, 3.09%
Modem number 22 is connected at 28800. Failures 0 out of 88, 0%
Modem number 23 is onHook. Failures 4 out of 92, 4.34%
Modem number 24 is onHook. Failures 4 out of 66, 6.06%
Modem number 25 is onHook. Failures 7 out of 97, 7.21%
Modem number 26 is onHook. Failures 3 out of 88, 3.4%
Modem number 27 is onHook
Modem number 28 is onHook
Modem number 29 is onHook. Failures 5 out of 75, 6.66%
Modem number 30 is onHook. Failures 5 out of 96, 5.2%
Modem number 31 is onHook
Modem number 32 is onHook
Total connected: 9
Failures: 92 of 2181, 4.21%
Originally, all of 11,12,15,16,27,28,31,32 were in state 'unknown'. I ran yet-another-ascend-SNMP-script on it for resetting modems, on the modems 27,28,31,32 - and as you can see, they're now in state onHook. But yet they've still not been selected for calls. Which is hardly surprising, to mee, because I don't think they exist. The absence of statistics on them is because they've not had any failures or connections (They are totalled to make the percentage figure - I have no idea if this is the right way, but it's consistent enough for me to try and spot the sick modems, if any).
There's been no noticeable results at all of resetting them. So I have this theory that the modems somehow don't exist. If there's a way of using these non-existant modems, then that'd be very useful, obviously, even if my alarm proglet has only gone off once ever to warn us that modem usage popped above 20.
If there's no modem there, then why are they showing up under SNMP?
Oh, show modems on the TServ now shows my reset modems, but not the unknown-state modems. They're numbered the same way, though.
Is anyone else getting this problem? And what's causing it, anyway? And is playing with it only going to make it worse, as my mother used to say?
(Oh - Sorry for hijacking your question a bit there, Dave :-)
Dave.
--
Dave Cridland -- Network Systems Administrator -- Cerbernet Ltd
Job/Employer information provided purely for interest. This is
not an official communication from Cerbernet Ltd, and any views
expressed herein are personal, as well as wrong and impolite...
++ 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:
References: