Path: utzoo!attcan!uunet!husc6!think!bloom-beacon!mit-eddie!bbn!uwmcsd1!ig!agate!ucbvax!decwrl!pyramid!prls!philabs!lamont!rgb From: rgb@lamont.Columbia.edu (bob bookbinder) Newsgroups: comp.protocols.appletalk Subject: Re: KFPS-II's and KIP 6/88 Summary: Kboxes hanging Message-ID: <658@muddy.lamont.Columbia.edu> Date: 20 Jun 88 20:50:40 GMT References: <8806162128.AA12713@nrl-css.arpa> Organization: Lamont-Doherty Geological Observatory N.Y. Lines: 14 In article <8806162128.AA12713@nrl-css.arpa>, wicinski@NRL-CSS.ARPA (tim wicinski) writes: > > What happens is that the box will configure and work fine, then for > unknown reasons, totally disappear from the net. You can ping them from > ethernet, but running CheckNet from Farallon, or the CAP 'atlook' programs > shows nothing. The same thing happens here, but only on one Ethernet segment with three KFPSII's's. The other kboxes (four of them) each on other Ethernet segments seem to stay up for months. The segment that has trouble also has the most traffic and is running with 2+% collisions (occasionally higher). We are running patched CAP 4 and KIP with an October 1987 date. Sometimes the boxes will stay up for a few days and sometimes they will only live for hours. The only way out is a power cycle or a complete reload, but usually just a power cycle will fix it.