Technical article 101292

When configuring IPX/SPX protocol, I get: "Fatal error: floating-point value too large to represent."

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

The Network Configuration Manager can fail  when attempting to add
or modify an IPX/SPX protocol stack. The following error message
occurs:

Fatal error: floating-point value too large to represent. Error Information logged to: /tmp/tclerror.<no>.log. Press Enter to continue

Cause

This problem is seen when an IPX/SPX network number (internal or external) similar to the following is used:

1e1000
This is due to the Network Configuration Manager interpreting the
network number as a floating point number.  This is caused by the
letter 'e' or 'E' within the number.  The number should be seen as
a valid hexadecimal number.  Numbers containing the letters 'a',
'b', 'c', 'd', and 'f' do not cause this problem.

Solution

When configuring the IPX/SPX protocol with the Network Configuration Manager, specify an IPX/SPX network number that does not contain the letter 'e'.

It is then possible to edit the following file manually to replace the selected network number with the required network number containing the letter 'e':

/etc/ipx.d/NPSConfig

An example of the fields which may need editing are:

internal_network = "1e10000"    # The Internal Network Number
lan_1_network = "1e20000"       # The External Network Number

If the IPX/SPX stack has been newly configured before editing NPSConfig, the kernel will need to be relinked and the system rebooted.

If an existing IPX/SPX stack has been modified by making a change to NPSConfig, the IPX/SPX protocol will only need to be restarted.

See also

netconfig(ADM); ipx(PADM)

From the Xinuos technical article database, record 101292. Reproduced with permission. The original is at www.sco.com/ta/101292, 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.