The modem should not "forget" and if it did start doing that my thoughts
would be RMA.
>
> Drop DTR, pause, raise DTR, pause
> Send control-Q, CR
> Send modem init string
>
>The ^Q was because some modems can get locked in command mode when they
>get a ^S, and totally freeze until they're told to continue. Note that
>this is often true even when the modem is set for hardware flow control,
>since command mode is a special case.
>
>Actually, Kitten would reset all unused modems once an hour, just on
>general principle. It made sure the modems didn't fall asleep. It worked
>well enough that some time back I wrote a cron task for the server that
>sends resets to the Portmaster for all unused lines once an hour. I'm
>sure this is why we get such good results from El Cheapo modems.
What model "El Cheapo" are you running there?
With the new Session Terminations being logged, I did stats on the first
week's log and use that to help determine if a modem needs attention. VERY
helpful.
It turns out that 2 Sportsters were throwing the whole curve off. After
finishing up some work on getting the termination info and going home I was
rapidly dropped 4 times in a row. What? Hunt sheet, go up higher in the
hunt and telnet in to see what port(s) I was hitting. Check out the edited
stats.
Reason Total S0 S1 S2 S3 S4 S5 S6
Admin Reset 10 0 0 0 1 0 0 0
Idle Timeout 524 10 15 15 8 10 2 13
Lost Carrier 6246 73 75 78 79 87 1535 243
NAS Error - PPP Unknown State 96 0 1 1 2 0 7 2
No Event Identified 176 8 3 3 2 4 16 3
Port Error - PPP Loop Detect 12 0 0 0 1 0 0 0
Service Unavailable - PPP No Protocol 23 0 0 0 0 0 4 1
Session Timeout 172 5 3 3 6 5 1 3
User Request - PPP Term Req 7402 147 132 136 138 145 184 156
Ze Total 15396 260 238 250 246 258 1780 437
Looks like the major cause for people calling in or mailing me about being
disconnected. There are a total of 99 ports in use. Nothing was logged for
ports without modems. All other ports are within a reasonable deviation
except S5 and S6 and the stats are from the first PM, so the modems were at
the beginning of the hunt.
A bit off the subject, but that is how I determine if a modem is
"absent-minded" and needs to be checked. Now that I have weeded most of the
bad ones out, act up and RMA you go.
There are entries in the modem table, but I only use them to reset the
templates. The ports were set for a period of time to their respective
modem, but I wasn't pleased with the results. When or if a modem is a
problem I have never found it to be "forgetful" and usually it will not work
regardless of what I try, which is why 7 Sportsters were sent to USR and 4
Supras were also RMA'd. The reasons for the Supras were minor compared to
the USR's and were easier to determine (LED's on one, no answer, won't
handshake, and a dropper - Sportsers opted for the "multiple-answer" or all
of the above). I've come to expect problems from about 1 in 8 for
Sportsters.... or should I say did.
May have to set up a cron like you did. A good idea for the infrequent
modem hang, which accordingly with Murphy will happen when I sleep or am
away for a few hours. 8^)
------------
Jeff Mountin
sysop@mixcom.com
MIX Communications
Serving the Internet since 1990
Sure my business card says "Senior Network Administrator"
They still make me do just about anything.