You can also change a parameter in NMMGR to essentially not allow the SQE
heartbeat losses to be recorded on the 3000.

Bill Lancaster

At 10:39 AM 5/13/98 -0700, Sletten Kenneth W wrote:
>John after Shawn:
>
>>> We've noticed an odd trend lately, there is a number of
>>> system processes that are taking a rather large amount of
>>> CPU.
>
>> I noticed this same thing when I updated to PP3. It seemed to
>> be the SQE switch on transceivers to DTC's was not on.
>
>Not only CPU activity:  If the SQE heartbeat on the 10BaseT
>transceiver is not on, believe you will also get a high level of disc
>I/O, because the system wants to log each of these "events".
>When we first switched from 10Base2 to 10BaseT and hooked
>up a DTC, we immediately started seeing a continuous 70-80
>I/O's per second.  Eventually got around to doing a
>
>LINKCONTROL @; STATUS = ALL
>
>and noticed we had millions of heartbeat losses recorded since
>last reset.  Turned on transceiver SQE heartbeat and all was well..
>
>Ken Sletten
>
>