Technical article 101290

Can IPX/SPX keep-alive packets be modified or disabled in SCO OpenServer 5.0.0?

OpenServer 5.0.0

Written · Last revised

Problem

How can I disable the keep-alive packets that are sent out on the network by the IPX/SPX protocols?

Solution

Within the IPX/SPX protocol suite, keep-alive packets are only sent out by NVT and SPX.

Keep-alives and SPX:

To disable the keep-alive packets in SPX, edit the file:

/etc/conf/pack.d/spx/spx_tune.h
and set the value of the SPX_WATCHEMU_INTERVAL parameter to 0.
SPX_WATCHEMU_INTERVAL specifies the interval in minutes that
the SPX watchdog runs.  The SPX watchdog ensures that the kernel
resources allocated to SPX are kept to a minimum and that all
dead connections are closed.

NOTE: The SCO servers on both ends of an SPX connection send keep-alive packets, so these must be disabled on both machines.

Instead of disabling the SPX keep-alives, increase the time between
keep-alive packets in SPX by modifying the SPX_WATCHEMU_INTERVAL
parameter in the same file.  The value of this parameter is in
minutes.

When the changes have been made, the kernel will need to be relinked and rebooted in order for the changes to take effect.

Keep-alives and NVT:

Keep-alive packets cannot be completely disabled in NVT, but the time interval between them can be increased. In order to increase this time, edit the file:

/etc/conf/pack.d/nvt/nvt_tune.h
and modify the value of the NVT_KEEP_ALIVE_INTERVAL_TIME
parameter.  This value is in clock ticks (there are 100 ticks
per second).  NVT_KEEP_ALIVE_INTERVAL_TIME specifies how long
NVT should wait before checking on inactive connections.  It
determines when the first watchdog packet is sent to an inactive
connection.  Increase the value of this parameter if NVT is used
on a large network with slow routers between the client and the
host.  Decreasing this value allows the host to detect downed
clients in a more timely manner.

When the changes have been made, relink and reboot the kernel in order for the changes to take effect.

See also

TA101288, "What are the different protocols for NetWare, and which ones does SCO support?"

From the Xinuos technical article database, record 101290. Reproduced with permission. The original is at www.sco.com/ta/101290, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.