Date: May 1, 1987 Number: 179 Title: INFORMATION ON SELECTED ERROR MESSAGES FOUND IN NONDEDICATED NETWARE 286, SFT I, SFT II, AND TTS Version 2.0a Address change detected for SERVERNAME Occurs on: ND286, SFT I, SFT II, TTS. Meaning: The Internetwork Number (Network Address) for the file server named SERVERNAME has been changed. This message does not necessarily signal an error condition. It is only a notice to the system manager that an address change has been detected. This message is displayed on the system consoles of all file servers on the internetwork that detect the change. It is important to remember that the server's address is the address that LAN A is set to. Therefore, an internetwork number change in LAN B, C, or D will not generate this message. Cause: This message is generated on other file servers if all of the following steps are performed within about 15 minutes. The server is brought down, and either the network address for LAN A is changed on the server with the SCONFIG utility, or an operating system with a different LAN A network address is installed. The file server is then rebooted. This same message can be generated if the node address for the file server is changed either by changing the switches (if the node address is switch selectable), or by changing the LAN interface card. This message could also be generated if multiple servers on the same internetwork have the same name. These servers would appear to the rest of the internetwork as one server that was constantly changing its address. This would cause the internetwork to behave erratically. Solution: This is not necessarily an error and no action may be necessary. This message may be helpful in determining problems on the internetwork such as multiple file servers with the same name. All file servers on an internetwork must have a unique name. This message can also help diagnose erratic problems on the internetwork with file servers running NetWare versions prior to SFT 2.0a. Versions of NetWare prior to this release could get stuck in a tight loop, broadcasting routing information over the internet when the server discovered that another server's address had been changed. This would cause problems on the internetwork, such as not being able to see or login to various servers. This message displayed on a server on the internetwork would indicate the server that had changed its address. ERROR! Address collision with SERVERNAME Occurs on: ND286, SFT I, SFT II, TTS. Meaning: This error message is displayed on the console when the file server detects that the server named SERVERNAME has the same Internetwork Number (Network Address) as itself, and these two networks are not on the same wiring segment. It is important to remember that the server's internetwork number is that set for LAN A in the server. This is not a fatal error and will not halt the server, although this condition may prevent users from accessing the server. LAN E must also have a unique node address on a Nondedicated system. Cause: Two file servers within the same internetwork have the same Network Address but are not on the same network cabling segment. Each file server within the same internetwork must have a unique network address unless connected to the same cabling segment. On the same cable segment, both internetwork numbers MUST be the same or the network will behave erratically. The node addresses of the LAN interface cards must always be unique within the internetwork. This error could also be generated if a break had occurred in a wiring segment with at least one file server on each side of the break. If the file servers are both still connected to the internet, they would both appear to have separate cabling systems, but both would have the same network address. Solution: Use the SCONFIG utility on the GENOS-3 diskette to change the network address of either the file server that is named in the error message or the server that the message appears on. Type "SCONFIG" with no options to get help with the syntax for the command. This new network address should be unique from all other servers that are not on the same immediate cabling segment in the internetwork. If the file server that this message appears on and the file server that is named in the message are supposed to be on the same wiring segment, then check for a break in the cabling between the two servers. Non-dedicated Server not running on top of DOS. Occurs on: ND286 only. Meaning: As it was booting, Nondedicated NetWare 286 discovered that it had not been started in a DOS environment. This is a fatal error and will halt the file server. This message will then be continuously displayed. Cause: When Nondedicated Netware 286 starts to initialize and set up the file server, it checks to make sure that DOS has been loaded. The Non- dedicated operating system requires DOS in order for it to task switch between the NetWare file server (running in 286 protected mode) and the DOS workstation (running in 286 real mode). Solution: Boot the system with IBM compatible DOS before attempting to start up Nondedicated Netware 286. Do not attempt to use Nondedicated Netware 286 with any other operating system. Not enough memory above 640K to run the server (requires 384K). Occurs on: ND286 only. Meaning: Nondedicated NetWare 286 requires more memory than the file server hardware has. In the Nondedicated environment, the first 640KB of RAM is used for the DOS workstation. The next 384KB of address space is reserved for adaptor cards and the ROM BIOS. NetWare utilizes all RAM above 640KB (starting at the 1 megabyte boundary) for the file server. The file server requires at least 384KB above the 1 MB boundary in order to run. This must be extended memory. Therefore, Nondedicated NetWare 286 will only run on a system that has at least 1 MB of system RAM with at least 384KB mapped above the 1 MB boundary. This is considered a fatal error and the server will halt operation and continuously display this error message. Cause: The file server does not have enough memory installed in it. This error could also be generated as a result of a failure in high memory, which would cause the file server to think that it has less memory installed. Solution: First, check that the file server has at least 1 MB of system RAM correctly installed in it, with at least 384KB mapped above the 1 MB boundary. If the server has plenty of memory installed in it and it still fails, check to make sure that the memory is good. Out of non-dedicated work stacks. Occurs on: ND286 only. This is an Abend error. Meaning: Nondedicated NetWare 286 allocates four stacks in memory for storing real mode interrupt information. This error is displayed if all four stacks are still in use when another real mode interrupt occurs. Cause: This error could be caused by inefficient interrupt routines that take a lot of time and cause the interrupts to stack up. Cards in the I/O expansion slot that use interrupts can also cause this problem if they interrupt too often. Solution: Except for the network interface cards, cards in the I/O expansion slot of a nondedicated file server should not use interrupts. Interrupt driven hardware and software should not be used with Nondedicated NetWare 286. Real time application software should especially be avoided. SwitchToReal ran out of non-dedicated work stacks. Occurs on: ND286 only. This is an Abend error. Meaning: Nondedicated NetWare 286 allocates four stacks in memory for storing real mode interrupt information. This error is displayed if all four stacks are still in use when another real mode interrupt occurs. Cause: This error could be caused by inefficient interrupt routines that take a lot of time and cause the interrupts to stack up. Cards in the I/O expansion slot that use interrupts can also cause this problem if they interrupt too often. Solution: Except for the network interface cards, cards in the I/O expansion slot of a nondedicated file server should not use interrupts. Interrupt driven hardware and software should not be used with Nondedicated NetWare 286. Real time application software should especially be avoided. WARNING!!! MULTIPLE ROUTERS WITH SAME INTERNET ADDRESS! Occurs on: ND286, SFT I, SFT II, TTS. Meaning: This error message is displayed on the console when the router process in the file server detects that another router in the internetwork has the same Internetwork Number (Network Address) as itself. This is not a fatal error and will not halt the server. Cause: At least two networks have been set up with the same internetwork number. This error will occur if the duplicate network number is assigned to LAN B, C or D as well as LAN A in a file server. Each network within the same internetwork must have a unique network address unless they exist on the same cabling segment. This error could also be generated if a break had occurred in a wiring segment with at least one file server on each side of the break. If the file servers are both still connected to the internet, they would both appear to have separate cabling segments, but both would have routers with the same network address. Solution: Use the SCONFIG utility to find and change the duplicate network addresses. The new network addresses should be unique from all other networks in the internetwork. If the two conflicting networks are supposed to be part of the same large network, then check for a break in the cabling between the two servers.