test

Solstice X.25 9.2 Administration Guide

Appendix C Error Messages and Error Codes

Error Messages are generated by the Solstice X.25 software, and tell you that there may be a mistake in the configuration. Error Codes are generated by your communication service and may indicate a problem with the remote host.

Note -

The information given below does not contain an exhaustive list of all the messages that can appear while using Solstice X.25, since many of the messages are self-explanatory. If you receive a message which is not listed here and is not self-explanatory, contact your authorized service provider for assistance.

Error Messages


Invalid Address Extension

Check and re-enter the extension.


Invalid Characters or Invalid Length in Address Extension

Check and re-enter the extension.


Missing Address Extension

Enter the address extension.


Invalid Character in Called Address or in Calling Address

Check and re-enter the address.


Invalid Character in Calling Address

Check and re-enter the address.


Invalid Address Local SAP

Check and re-enter the local SAP.


Invalid Address Loop SAP

Check and re-enter the loop SAP.


Invalid Character in Call User Data

Check and re-enter the Call User Data.


Specify the HTML browser before starting Help

To use on-line help with x25tool, you must first specify the browser you want to use (Netscape, Hot Java, Mosaic).


Invalid DNIC

Check and re-enter the DNIC


Cannot allocate memory

Free up memory and try again.


Cannot load file <file_name> : <cause>

The cause displayed with this message should give you some indication of the problem. Correct the problem and try again.


The file does not exist, or is in the wrong format

Check that the file exists and is in the right format.


Error loading file for link# <link id>

The file may be in the wrong format.


Cannot open lapb device

The X.25 network must be up before the lapb device can be opened.


Cannot open x25 device

The X.25 network must be up before the x25 device can be opened.


NO IXE file

The file is missing.


Error opening directory %s

The directory may not exist.


Error opening file %s

The file may not exist.

Error Messages Related to Read and Write Permission

The following error messages can occur if you do not have read and write permission. If you receive one of the messages listed below, log in as root or become superuser, and try again.


Cannot add dynamically this IP interface


Cannot add dynamically this link


Cannot load dynamic parameters for link <link>


Cannot load dynamic parameters for NUI


Cannot load dynamic parameters for Route


Cannot remove dynamically this IP interface


Cannot remove dynamically this link


Cannot reset this link


Cannot save dynamically IP Interface Parameters


Cannot save dynamically IP Map Parameters


Cannot save dynamically LAPB Parameters


Cannot save dynamically LLC2 Parameters


Cannot save dynamically MLP Parameters


Cannot save dynamically NUI Parameters


Cannot save dynamically Pad Daemon Parameters


Cannot save dynamically PAD Printer Parameters


Cannot save dynamically PVC


Cannot save dynamically Routing Parameters


Cannot save dynamically X25 Security Parameters


Cannot save dynamically WAN Parameters


Cannot save dynamically this Link


Cannot get running links list


Error creating backup of boardconf file


Error creating backup of ipconf file


Error creating backup of ixemapconf file


Error creating backup of pvcmapconf file


Error creating backup of nuimapconf file


Error creating backup of paddconf file


Error creating backup of padmapconf file


Error creating backup of routes file


Error creating backup of x25secuconf file


Error creating backup of x25secupid file


Cannot create a symbolic link from <source file> to <destination file> <causes>


Error creating backup of x29profile file


Error creating backup of xhosts file


Error creating backup of xtpmapconf file


Unable to Execute Command


Unable to Execute Command <command name>


File <filename> is read-only Change the permissions and re-do


Cannot remove symbolic link <symbolic_link>


Error writing boardconf file


Cannot write in Directory <directory_name>


Error writing ipconf file


Error writing ixemapconf file


Error writing pvcmapconf file


Error writing nuimapconf file


Error writing paddconf file


Error writing padmapconf file


Error writing routes file


Error writing x25secuconf file


Error writing x25secupid file


Error writing x29profile file


Error writing xhosts file


Error writing xtpmapconf file

Error Messages Relating to File Format Problems

The following messages indicate a problem with the format of the file. This type of problem can be avoided by using x25tool whenever possible, instead of directly editing files.


nuimapconf: Bad facility: non-digit locdefpktsize


nuimapconf: Bad facility: overlong locdefpktsize


nuimapconf: Bad facility: non-digit locdefthclass


nuimapconf: Bad facility: overlong locdefthclass


nuimapconf: Bad facility: non-digit locdefwsize


nuimapconf: Bad facility: overlong locdefwsize


nuimapconf: Bad facility: non-digit remdefpktsize


nuimapconf: Bad facility: overlong remdefpktsize


nuimapconf: Bad facility: non-digit remdefthclass


nuimapconf: Bad facility: overlong remdefthclass


nuimapconf: Bad facility: non-digit remdefwsize


nuimapconf: Bad facility: overlong remdefwsize


nuimapconf: Unexpected character in facility string


xtpmapconf: invalid address <address> for device xtp<device>


xtpmapconf: invalid cud <cud> for device xtp<device>


xtpmapconf: incorrect device


xtpmapconf: incomplete line in config file


xtpmapconf: invalid link number : <link_number> for device xtp<device>


xtpmapconf: invalid opt <opt> for device xtp<number>


xtpmapconf: invalid printer name <printername> for device xtp<number>


route file: AEF already set: <aef>


route file: bad type of AEF: <aef>


route file: AEF must be in Hexa : <aef>


route file: source_aef not supported, skipped


route file: too long AEF: <aef>


route file: bad source_aef entry


route file: bad link number


route file: bad right-hand part of aef entry


route file: bad tag <tag> at line <line_number>


route file: Mac address already set <mac_address>


route file: bad 802 address <address>


route file: mismatched quotes at line <line_number>


route file: unknown keyword on line <line_number>


route file: parse error at line <line_number>, truncated file?


route file: Pid already set <pid>


route file: bad Pid <pid>


route file: Pid must be hexa <pid>


route file: Odd length pid <pid>


route file: Pid too long <pid>


route file: PSTN number already set <PSTN_number>


route file: PSTN missing <PSTN_number>


route file: PSTN number must not exceed 16 digits <PSTN_number>


route file: too many items on line <line_number>


route file: X.121 address already set <x121_address>


route file: bad X.121 <x121_address>


route file: bad X.121 <x121_address>


route file: bad right-hand part of X.121


route file: too long X.121 <x121_address>


x25secuconf, line <line_number> :Bad address


x25secuconf, line <line_number> : No more than 15 digits in X121 address


x25secuconf, line <line_number> : Invalid character in address


x25secuconf, line <line_number> :Bad date


x25secuconf, line <line_number> :Bad day number


x25secuconf, line <line_number> :Bad link id


x25secuconf, line <line_number> :Bad month


x25secuconf, line <line_number> : Invalid repetition period


x25secuconf, line <line_number> :Bad time


x25secuconf, line <line_number> :Bad year number


x25secupid, line <line_number> : Error in reading pid


x25secuconf, line <line_number> :error in get_service_name


x25secupid, line <line_number> : No * after 128 digits in pid


x25secupid, line <line_number> : pid len must be even


Missing service name <service_name> in x25secuconf file


x25secuconf, line <line_number> :Service name too long


x25secupid, line <line_number> : Invalid Character in pid


x25secupid, line <line_number> :character not authorized in service name


Unexpected Hold-Down Timer value <timer_value> Assumed to be X.25 mode from V8 config file


Unexpected 'Unconfigured Host' value on line <line_number> Assumed to be Reset Action from V8 config file


Unrecognized option at line <line_number>, processing PAD Daemon file


Invalid Characters or Invalid Length in PID


x25secupid, line <line_number> :error in read_service_name


x25secupid, line <line_number> :Service name too long

Error Codes

A problem with an X.25 application might be a result of a problem communicating with the PSDN or a problem with the remote host. When a problem causes your call to be cleared, you receive a diagnostic code in the form of two pairs of digits. The first pair indicates why the call was cleared; the second pair gives additional diagnostic information. The tables on the following pages specify the meanings for these numeric codes. Table C-1 specifies reasons for call-clearing. Table C-2 specifies diagnostic information in addition to the call-clearing cause.

In many instances, if you receive any of these error codes, you will need to contact your service provider. However, in some instances the error code may indicate a configuration problem that you can correct yourself.

A zero (00) call-clearing code indicates that the call-clearing request originated in the remote host. A non-zero call-clearing code indicates the call-clearing request originated in the PSDN.

For example, your call is cleared with a code 03 42. As specified in Table C-1, 03 indicates an invalid facility request. Table C-2 tells you that 42 (hex) means that a facility parameter (that you used) is not allowed. This combination of messages tells you that:

  1. The problem was detected by the PSDN, not by the remote host.

  2. One or more parameter settings that you made in x25tool are unacceptable to the PSDN.

Often, a diagnostic gives only a general clue as to the source of a problem. For example, your call might be cleared with the code 00 42, indicating an invalid facility parameter setting. You might, in fact, have a facility parameter set to a value outside of the range of what you subscribed to. However, you can also receive this message if the maximum I-frame size is set to a size lower than the PSDN expects. Solstice X.25 clears the call rather than allow it to start and possibly fail later.

If you receive error code 00 42 and are not subscribing to any facilities, or are confident that your facilities parameters settings are correct, confirm that you and your PSDN agree on the maximum I-frame size. Remember that any adjustment of the maximum I-frame size, a LAPB parameter, might also require a change to the default packet size parameter, at the X.25 Packet Layer. Use x25tool to modify your link configuration as necessary.

In Table C-1 note the four categories of codes, separated by the double horizontal lines:

Codes in the fourth category (hexadecimal codes 05 through 15) indicate problems within the PSDN. Table C-1 lists the fourth category causes for call clearing codes:

Table C-1 Causes for Call Clearing

Hexadecimal Code 

Decimal Code 

Meaning 

00

00

Originated by remote DTE 

01

01

Number busy 

09

09

Out of order  

11

17

Remote procedure error 

19

25

Reverse charging acceptance not subscribed 

21

33

Incompatible destination 

29

41

Fast select acceptance not subscribed  

03

03

Invalid facility request 

0B

0B

Access barred 

13

19

Local procedure error 

05

05

Network congestion 

0D

13

Not obtainable 

15

21

RPOA out of order 

Table C-2 lists the X.25 diagnostic codes.

Table C-2 X.25 Diagnostic Codes

Hexadecimal Code 

Decimal Code 

Meaning 

00

00

No additional information  

01

01

Invalid P(S) (send-packet sequence number) 

02

02

Invalid P(R) (receive-packet sequence number) 

10-1F

16-31

Invalid packet type 

20

32

Packet not allowed 

21

33

Unidentifiable packet 

22

34

Call on one-way logical channel 

23

35

Invalid packet type on a permanent virtual circuit 

24

36

Packet on an unassigned logical channel 

25

37

Reject not subscribed to 

26

38

Packet too short 

27

39

Packet too long 

28

40

Invalid general format identifier 

29

41

Restart with nonzero in bits 1-4, 9-16  

2A

42

Packet type not compatible with facility 

2B

43

Unauthorized interrupt confirmation 

2C

44

Unauthorized interrupt 

30

48

Timer expired 

31

49

For incoming call 

32

50

For clear indication 

33

51

For reset indication 

34

52

For restart indication 

40

64

Call setup problem 

41

65

Facility code not allowed 

42 

66 

Facility parameter not allowed 

43 

67 

Invalid called address 

44 

68 

Invalid calling address 

Note in the table above that hexadecimal codes 0, 20, 30, and 40 (decimal 0, 32, 48, and 64) stand for general messages that include the specific conditions indicated by the codes that follow them. Your PSDN might return only the codes that stand for the general messages.

Table C-3 lists X.25 diagnostic codes that you might receive when you are running Solstice X.25 over the Connection-Oriented Network Service (CONS).

Table C-3 CONS Diagnostic Codes

Hexadecimal Code 

Decimal Code 

Meaning 

Sent by CONS 

E0

224

Unspecified 

E1

225

Disconnect--transient 

E2

226

Disconnect--permanent 

E3

227

Reject--transient 

E4

228

Reject--permanent 

E5

229

QOS not available--transient 

E6

230

QOS not available--permanent 

E7

231

NSAP unreachable--transient 

E8

232

NSAP unreachable--permanent 

E9

233

Unspecified Reset 

EA

234

Reset due to congestion 

EB

235

Unknown NSAP 

Sent by CONS user (TP0/TP2) 

F0

240

Unspecified 

F1

241

Normal disconnect 

F2

242

Abnormal disconnect 

F4

244

Reject--transient 

F5

245

Reject--permanent 

F6

246

No QOS--transient 

F7

247

No QOS--permanent  

F8

248

Incompatible NS user data 

FA

250

User Reset 

Note that you receive the reset codes, hexadecimal numbers E9, EA, and FA, in Reset Request/Indication packets. You receive the remaining codes in Clear Request/Indication packets.