🚀 go-pugleaf

In article <9207292005.AA07608@orville.nas.nasa.gov> PMW1@PSUVM.PSU.EDU ("Peter M. Weiss +1 814 863 1843") writes:
>(One of the) We at Penn State have run across a limitation of the
>PCF so that filtering on full IP addresses causes us to also add
>a static route for that address.  Because of our extensive filtering
>(and its concomitant ROUTE), we have approached the limit of the
>file system (30036 bytes of EEPROM) to store configuration statements.
>
>Has anyone run across this limitation, and if so, how did you bypass/
>resolve it?
>
>/Pete
>--
>Peter M. Weiss                     | not affiliated with psuvm.psu.edu|psuvm
>31 Shields Bldg -- Penn State Univ.| "Connectivity is more than a Connection"
>University Park, PA USA 16802-1202 | E. Michael Staman, _The Circuit_, Apr 92


This problem can be resolved fairly simply by adding another EEPROM to
the IP coprocessor board effectivly doubling the capacity.  You should 
contact your local NSC Customer Service Representative or NSC Sales
office to find out the details.  While I don't know exactly who your
Sales Rep. would be, the Customer Service District Manager for your
area is Mr. Stubbs in Media, PA.  The Phone number is  215/565-1935.  
He should be able to direct you in the proper direction.

I sure hope this is of benefit to you.
____________________
Bryan L. Duff
Network Engineer
Network Systems Corp.
email - bryand@cascade.ens.tek.com

--
Bryan Duff
Network Engineer
Network Systems Corp.