Status: UP Framing: ESF Encoding: B8ZS PCM: u-law
Receive Level: -15dB to -22.5dB
Alarms Violations
----------------------------- -----------------------------
Blue 0 Bipolar 0
Yellow 0 CRC Errors 0
Receive Carrier Loss 0 Multiframe Sync 0
Loss of Sync 0
:-Þ
--Susan
Erik Power wrote:
>
> No problems here.
>
> an1> ver
> Livingston PortMaster PM-3 ComOS 3.8.2
> System uptime is 18 days 4 minutes
>
> an1> sh line0
> ---------------------- line0 - T1 Inband DS0 ---------------
>
> Status: UP Framing: ESF Encoding: B8ZS PCM: u-law
>
> Signaling: FXS loop start
>
> Receive Level: +2dB to -7.5dB
>
> Alarms Violations
> ----------------------------- -----------------------------
> Blue 0 Bipolar 0
> Yellow 0 CRC Errors 0
> Receive Carrier Loss 0 Multiframe Sync 0
> Loss of Sync 0
>
> an1> sh mem
> System memory 4194304 bytes - 3158652 used, 1035652 available
> 96:2 208:5 192:3 640:1 1168:1 112:5 176:6 240:5 144:6 2048:5 224:2 64:6
> 4240:3 592:2 32:12 2064:0 128:5 80:10 16:101 160:7 48:6
> System nbufs 2558 - 77 used, 2481 available
> System blocks 576 - 10 used, 566 available
>
> -----Original Message-----
> From: owner-portmaster-users@livingston.com
> [mailto:owner-portmaster-users@livingston.com]On Behalf Of jon-lists
> Sent: Monday, February 01, 1999 3:30 PM
> To: Tony Harris
> Cc: portmaster-users@livingston.com
> Subject: Re: (PM) An issue with 3.8.2 after 21 days?
>
> It stopped giving clients a network connection. I didn't go into it very
> far, but it appeared that PPP started not working for X number of ports
> after a few days (nowhere near 21 days... maybe 4).. as soon as I reflashed
> 3.8 into it the problem went away. I would just start seeing less ports in
> use for that specific time of day. The kicker was when a customer called
> having trouble, I had him try to connect 5 times in a row, then I rebooted
> and told him to try again and he got in no problem. Couple days later it
> started up again. This time I just reflashed 3.8 in there and rebooted and
> everything has been fine since. (month I would bargain)
>
> It's really a shame, since the 3.8.2 modem code appeared to be quite a bit
> better, I noticed some better connection rates in the early times after
> rebooting.
>
> memory usage looked normal when it started flaking out. I don't have a clue
> what the problem was, I had an idea of SNMP, but someone else had SNMP
> enabled and wasn't having a problem, if I remember correctly. *shrug*
>
> At 05:05 PM 2/1/99 -0600, you wrote:
> >Hello,
> >
> >Someone had mentioned that they had trouble with 3.8.2 after 21 days of
> use.
> >Could that person, or anyone else experiencing this PLEASE email me what
> the
> >symptoms were?
>
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
> Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
>
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
> Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>