Once upon a time Jon Lewis shaped the electrons to say...
>
>I've seen the following on several occasions now where all of a sudden
>ISDN users can't connect even though nothing has been changed in their
>config. (note, I'm not just taking their word for it...at least not in
>all cases.)
>
>[044:01:10:43:55] S10 (5:1) Confirming Connect - 64Kbps / Data (b1 ref:1)
>[044:01:10:43:65] S10 (5:1) DISCONNECT_ACK inavlid state 3
>[044:01:10:43:65] S10 (5:1) DISCONNECT_ACK
>[044:01:10:43:65] S10 (5:1) CALL_CLEAR
>[044:01:10:43:70] S11 (5:2) REGISTER_ACK
>
>What's invalid state 3 mean? Is this a telco issue, or is the PM2
>weirding out on me? It's running 3.7.2, and still occasionally leaks
>memory.
>
>Command> sh mem
>System memory 4194304 bytes - 1591620 used, 2602684 available
>112:0 2832:2 2048:7 144:8 64:1 1152:1 128:9 640:1 80:6930 96:28 272:50
>176:2 16:121 160:7 32:80 48:8
>System nbufs 1400 - 67 used, 1333 available
>Command> ver
>Livingston PortMaster PM-2e ComOS 3.7.2
>System uptime is 44 days 1 hours 13 minutes
>
>On fresh bootup, it uses less than 1mb. Sometimes when a B channel or two
>hoses and goes into NO-SERVICE, it will leak memory until the
>corresponding D channel is reset. This is a bug that's existed in the
>past several versions of ComOS. Any idea when/if this might get fixed?
>
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/message.
Florida Digital Turnpike |
______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.