Re: Again... ComOS 3.5

Jacob Suter (jsuter@intrastar.net)
Thu, 1 May 1997 21:20:28 -0500

> >Other info... running Radius 2.0
> >
> >Is there a beta out that I may need to try?
> >
> >Along the same lines can I downgrade back to 3.3.3 safely?
> >
> >Thanks, David
>
> Probably ran out of RAM. If you are using the WAN port on PM2ER/30 and
have
> many of the ports going I would recommend upgrading to 4 or 16MB of RAM.
> Use standard 30pin 72NS/30pin simms. All simms must be the same ie 4MB=
> 4-1MB, 16MB=4-4MB. This will allow you to use OSPF which makes life much,
> much easier.

We've got a PM2ER-10 and a 56K on the W1 port and all 10 lines have been
running ppp and the 56K going flat out and have had no problems except for
an intermittant CSU/DSU to NTU wiring problem (replaced the cable (with a
cat-3 cable) and all returned to normal)...

pm1-cro> ver
Livingston PortMaster PM-2 ComOS 3.5
System uptime is 19 days 11 hours 3 minutes
pm1-cro>

pm1-cro> sh mem
System memory 1048576 bytes - 786944 used, 261632 available
64:0 1152:0 640:0 2048:4 144:5 128:3 48:3 80:3 96:1 160:3 16:117 32:8
System nbufs 1400 - 89 used, 1311 available
pm1-cro>

Radius 2.0, NO OSPF, NO SNMP (we leave pmconsole loaded all the time on the
server)...

Works like a charm... now if my upstream would upgrade their sicky little
2501's IOS crap I could run VJ header compression and get that extra 2% of
bandwidth :)

JS