PC Server 315 - 100/10 Ethernet Adapter Information

61.051 bytes

Parts Information

Document ID: DDSE-44ZTF8

PC Server 315 - 100/10 Ethernet Adapter Information

Applicable to: World-Wide

100/10 ETHERNET ADAPTER CONFIGURATION

Some PC Server 315 models come with an Ethernet adapter preinstalled as a standard feature. The adapter contains three LEDs visible from the back of the server that show the status of the connection, monitor read and write activity, and indicate a 100 Mbps connection. Refer to "100/10 Ethernet Adapter Troubleshooting" for more information about the LEDs.

During POST, the server automatically configures the Ethernet adapter.

The Ethernet Configuration and Drivers program automatically installs necessary Novell NetWare 4.0 drivers, tests the adapter, and displays a help file with installation instructions for unsupported network operating-system drivers.

NOTE:
You must use Category 5 cabling when operating the Ethernet adapter at 100 Mbps.

The Ethernet Configuration and Drivers program supports Windows NT Server 4.0.

Installing Multiple Adapters

Use the Ethernet Configuration and Drivers program each time you install an adapter. You can also use the program to isolate problems during troubleshooting.

Repeat the configuration procedures for each adapter that you want to install. Even though the Ethernet Configuration and Drivers program can detect all the PCI adapters in the server, you must perform the installation process before you can use the adapter.

Configuring for Windows NT Server 4.0

To configure the Ethernet adapter for the Windows NT Server 4.0 operating system:

1. Double-click on the Network icon on the Control Panel.
2. Click on the ADAPTERS button; click on the ADD button; then, click on the HAVE DISK button.
3. Insert the Ethernet Configuration and Drivers diskette 1 of 2 in drive A. Then, click on OK.
4. When the Select OEM Option screen appears, highlight the IBM 100/10 PCI Ethernet Adapter. Then, click on OK.

The Ethernet Configuration and Drivers program automatically scans server resources and determines which resources were assigned to the adapter. This may take a few seconds.

If a message appears stating The system has not enabled busmastering on the device you are installing, the device driver will attempt to enable mastering when it loads. Run the adapter diagnostics to see if busmastering is allowed in the slot selected.

5. Click on TEST.

NOTES:
- When testing a newly configured adapter, the network device driver will not be active. The diagnostic will test only the adapter and its connection to the network.
- When testing a previously configured adapter, the network device driver will be active. The diagnostic will test the adapter, its connection to the network, and the device driver. The test will also track the actual network activity of the device driver.

6. When testing completes, click on OK to accept the configuration. Then, click on OK again.
7. Under Network Adapter, select the IBM 100/10 PCI Ethernet Adapter. Then, click on CLOSE.

NOTE:
If you have other LAN protocols installed, such as TCP/IP, additional screens will appear requesting configuration information. If this occurs, follow the instructions on the screen.

8. Remove the Ethernet Configuration and Driver diskette from drive A.
9. Click on YES in the Network Settings dialog box to restart Windows NT Server Version 4.0.

TROUBLESHOOTING

- Make sure that you are using the device drivers that come with this adapter.
- Make sure that the device driver is loaded and the protocols are bound. See the Network Bindings dialog box in Windows NT Server 4.0 to verify this.
- Make sure that you are using Category 5 cabling when operating the Ethernet adapter at 100 Mbps.
- Test the adapter using the instructions in "Configuring for Windows NT Server 4.0."
- Check with the LAN administrator.

100/10 ETHERNET ADAPTER TROUBLESHOOTING

The following information is for troubleshooting problems that might occur when the 100/10 PCI Ethernet Adapter is installed in the server.

Network Connection Problems

If the adapter cannot connect to the network, check the following:

- Make sure the cable is installed correctly.

The network cable must be securely attached at all connections. If the cable is attached but the problem persists, try a different cable.

If you set the Ethernet adapter to operate at 100 Mbps you must use Category 5 cabling. Refer to the HARDWARE SPECIFICATIONS AND CABLING INFORMATION section in the help file for a list of recommended cables and
information on how to install cabling.

If you directly connect two workstations (no hub), use a crossover cable. Refer to the HARDWARE SPECIFICATIONS AND CABLING INFORMATION section in the help file.

- Check the LEDs on the rear of the Ethernet adapter.

The Ethernet adapter has three diagnostic LEDs beside the cable connector. These lights help indicate whether a problem exists with the connector, cable, or hub.
1) The LNK LED illuminates when the adapter receives a LNK pulse from the hub. If the LED is OFF, there might be a bad connector or cable, or a problem with the hub. The LNK LED is also OFF when you run the diagnostic tests in the Setup program.
2) The ACT LED illuminates when the adapter detects read or write activity on the network, even when there is no activity on the adapter. If the ACT LED is not on, make sure that the hub and network are operating and that the correct drivers are loaded.
3) The 100 LED illuminates when a 100 Mbps connection is established.

- Make sure that you are using the correct drivers.

- Check for operating system-specific causes for the problem.

- Test the adapter.

Select TEST ADAPTER from the Main Menu on the Ethernet adapter Configuration and Drivers diskette. How you test the adapter depends on which operating system you are using.

100/10 ETHERNET CONTROLLER

The Ethernet controller on the system board provides an efficient, high-speed interface to a 10-Mbps Ethernet network, with automatic configuration.

The controller provides full-duplex (FDX) operation.

The controller also provides an automatic sensing function. The server automatically detects which of the two Ethernet ports is connected to the network, and then uses that port for communication. This function, always active, eliminates the need for a media type parameter and facilitates changing from one media type to another.

NOTE:
Before installing an IBM PC Ethernet adapter, be sure to run the Ethernet diagnostics and record the server's Ethernet configuration information.

100/10 ETHERNET CONTROLLER MESSAGES

The integrated Ethernet controller might display messages from the following drivers:

- Novell NetWare Server ODI
- Novell NetWare Server DOS ODI
- Novell NetWare Server OS/2 ODI
- NDIS Adapter for level 2.01
- NDIS Adapter for level 3.0
- Packet Driver
- SCO UNIX LLI, UnixWare DLPI, and SunSoft Solaris

Novell NetWare Server ODI Driver Messages

This following error messages are for the Novell NetWare server ODI driver. The explanation and recommended action are included with each message.

PCNTNW-NW-026 THE MSM IS UNABLE TO PARSE A REQUIRED CUSTOM KEYWORD.

EXPLANATION: The user entered an incorrect parameter keyword.

ACTION: Enter the keyword correctly. Then, reload the driver.

PCNTNW-NW-054 THE BOARD DID NOT RESPOND TO THE INITIALIZATION COMMAND.

EXPLANATION: The board did not respond when the driver tried to initialize it.

ACTION: Do the following:

1. Verify that the Ethernet jumper on the system board is set to the default, enabled position.
2. Go to "General Checkout."

PCNTNW-NW-58 THE BOARD DID NOT RESPOND TO THE INITIALIZATION COMMAND.

EXPLANATION: The IRQ setting might be incorrect with the hardware setting, or the EEPROM might be corrupted.

ACTION: Do the following:

1. Verify that the IRQ settings in the NET.CFG file match the configuration settings in the configuration programs. See "Resolving Hardware Configuration Conflicts" for information on setting the interrupt requests.
2. Verify that the EEPROM on the system board is programmed correctly.

PCNTNW-NW-66 THE CABLE MIGHT BE DISCONNECTED FROM THE BOARD.

EXPLANATION: The cable might be disconnected from the server's Ethernet port.

ACTION: Verify that a cable is connected to the AUI port or the 10BASE-T port.

PCNTNW-NW-071 THE MATCHING VIRTUAL ADAPTER COULD NOT BE FOUND.

EXPLANATION: You tried to load another instance of the driver with a different I/O address. This new board could not be found.

ACTION: If an IBM Ethernet adapter was installed, make sure the adapter is seated properly. Also, check the I/O settings of the board with the settings supplied to the drive.

PCNTNW-NW-072 A RESOURCE TAG IS UNAVAILABLE.

EXPLANATION: The driver tried to allocate some resources that were not available.

ACTION: Add or free some memory in the server. Then, restart the server.

PCNTNW-NW-073 UNABLE TO ALLOCATE MEMORY.

EXPLANATION: The driver failed to allocate the memory needed for normal operation.

ACTION: Add more memory, or free some memory resources in the server. Then, restart the server.

PCNTNW-NW-074 THE HARDWARE INTERRUPT CANNOT BE SET.

EXPLANATION: An attempt was made to initialize a given hardware interrupt. The attempt was not successful.

ACTION: Do the following:

1. Verify that the Ethernet jumper on the system board is set to the default, enabled position.
2. Make sure that the interrupt request numbers are set correctly, and that no other devices are using the interrupt. See "Resolving Hardware Configuration Conflicts" for more information.

PCNTNW-NW-075 THE MLID CANNOT BE REGISTERED WITH THE LSL.

EXPLANATION: An error occurred while the driver was trying to register with Link Support Layer.

ACTION: Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware installed. Restart the server.

PCNTNW-NW-076 THE POLLING PROCEDURE CANNOT BE ADDED.

EXPLANATION: An error occurred while the driver was adding a polling procedure to the Netware Operating System polling routines.

ACTION: Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware installed. Restart the server.

PCNTNW-NW-077 THE EVENT NOTIFICATION CANNOT BE REGISTERED.

EXPLANATION: The driver failed to register its event notification routines with the Netware Operating System.

ACTION: Check the version of Netware Operating System. Make sure that this driver is correct for the version of Netware installed. Restart the server.

PCNTNW-NW-078 THE FIRMWARE FILE CANNOT BE READ.

EXPLANATION: The driver to read a firmware file. The read process failed.

ACTION: Make sure that the support files that were shipped with the driver are present. Restart the server.

PCNTNW-NW-079 THE MLID DID NOT INITIALIZE MSMTX FREE COUNT.

EXPLANATION: The MSMTx Free Count is not initialized properly.

ACTION: Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-084 UNABLE TO ALLOCATE MEMORY BELOW THE 16 MEGABYTE BOUNDARY.

EXPLANATION: A request was made to allocate memory below 16 megabytes. The request did not complete successfully.

ACTION: Free some memory below 16 megabytes, or add more memory below the 16 megabyte boundary.

PCNTNW-NW-086 THE DRIVER PARAMETER BLOCK IS TOO SMALL.

EXPLANATION: The driver parameter block is too small.

ACTION: Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-087 THE MEDIA PARAMETER BLOCK IS TOO SMALL.

EXPLANATION: The driver media parameter block is too small.

ACTION: Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-091 THE HARDWARE CONFIGURATION CONFLICTS.

EXPLANATION: You tried to load a new frame type for the existing adapter. The hardware assumptions made in doing so are incorrect.

ACTION: Make sure that the hardware configuration matches the software settings. See "Resolving Hardware Configuration Conflicts" for information on viewing and changing interrupt requests.

PCNTNW-NW-092 CANNOT SCHEDULE AES WITHOUT AN HSM ROUTINE.

EXPLANATION: The Netware Operating System needs a Hardware Support Module routine before it schedules an AES event.

ACTION: Restart the server. If the error is still present, replace the system board.

PCNTNW-NW-093 CANNOT SCHEDULE INTERRUPT TIME CALL BACK WITHOUT AN HSM ROUTINE.

EXPLANATION: The driver needs a Hardware Support Module routine before it can schedule an interrupt time call back.

ACTION: Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-094 CANNOT SET HARDWARE INTERRUPT WITHOUT AN HSM ROUTINE.

EXPLANATION: The driver needs a hardware interrupt call back routine before it sets the interrupt.

ACTION: Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-095 CANNOT ADD POLLING WITHOUT AN HSM ROUTINE.

EXPLANATION: The driver needs an HSM polling routine before it can start the polling process.

ACTION: Restart the server. If the error recurs, replace the system board.

PCNTNW-NW-126 THE GROUP BIT IN THE NODE ADDRESS OVERRIDE WAS CLEARED.

EXPLANATION: The IEEE address has a group bit indicating that an address belongs to a group of stations. This bit is used only as a destination address; it cannot be used as a source address. You tried to enter a source address with this bit set. The driver cleared the group bit of the source address.

ACTION: None.

PCNTNW-NW-127 THE LOCAL BIT IN THE NODE ADDRESS OVERRIDE WAS SET.

EXPLANATION: The local bit in the IEEE address format indicates that the addresses are being managed locally. If you use the node address override capabilities of this driver to enter a new address, the local bit should be set. You entered an address without the local bit set. The driver has set the local bit.

ACTION: None.

PCNTNW-NW-164 THE DEVICE WAS NOT FOUND.

EXPLANATION: The driver cannot find an Ethernet controller in the server.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout."

PCNTNW-NW-164 DEVICE NOT FOUND AT IOADDRESS.

EXPLANATION: The Ethernet controller cannot be found at the IO address specified in the NET.CFG file.

ACTION: Verify that the IO Address in the NET.CFG file matches with the board. Otherwise, remove the PORT keyword from the NET.CFG file.

PCNTNW-NW-167 PCI SCAN SPECIFIED, DEVICE NOT FOUND.

EXPLANATION: The driver cannot locate the Ethernet controller on the PCI bus.

ACTION: Perform the following steps:

1. Verify that the Ethernet jumper on the system board is set to the default, enable position.
2. Edit the NET.CFG file to change the BUSTYPE keyword to PCI1.
3. If the problem persists, go to "General Checkout" on page 2.

PCNTNW-NW-180 THE DMA PARAMETER IS NOT NECESSARY FOR PCI DEVICE.

EXPLANATION: The Ethernet controller does not require a DMA setting.

ACTION: Delete the DMA parameter from the NET.CFG file.

Novell NetWare DOS ODI Driver Messages

The following error messages are for the Novell NetWare DOS ODI device driver. The explanation and recommended action are included with each message.

PCNTW-DOS-1 THE LSL IS NOT LOADED.

EXPLANATION: The Link Support module (LSL.COM) is not loaded.

ACTION: Load LSL.COM; then, load the device driver.

PCNTW-DOS-2 THE LSL HAS NO MORE ROOM FOR A BOARD USING FRAME <STRING>.

EXPLANATION: The maximum number of adapters, whether virtual or physical, has been registered with the Link Support Layer. In the PC Server 315 - Type 8638, the DOS ODI LSL can support up to five PCI Ethernet adapters, plus
the Ethernet controller in the system board.

ACTION: Reduce the number of active adapters in the systems by removing an adapter, or by decreasing the number of frame types activated by Multiple Link Interface Driver (MLID).

PCNTW-DOS-3 COULD NOT FIND PCNTNW MLID TO UNLOAD.

EXPLANATION: A request was made to unload PCNTNW MLID, but the MLID is not loaded.

ACTION: None.

PCNTW-DOS-4 A TSR IS LOADED ABOVE THE PCNTNW MLID.

EXPLANATION: You tried to unload the PCNTNW MLID from memory, but the PCNTNW MLID detected another Terminate and Stay Resident (TSR) program loaded above the MLID. For the PCNTNW MLID to unload safely, you must first unload any TSR programs that were loaded after you loaded the MLID.

ACTION: Either unload the other TSR program before loading the PCNTNW MLID, or unload the TSR program before attempting this operation.

PCNTW-DOS-5 PCNTNW MLID COULD NOT BE UNLOADED; THE OPERATION WAS ABORTED.

EXPLANATION: The PCNTNW MLID attempted to remove the resident PCNTNW MLID from memory, and failed. A hardware error has probably occurred.

ACTION: Run the Ethernet diagnostic.

PCNTW-DOS-6 THE ADAPTER DID NOT INITIALIZE. PCNTNW DID NOT UNLOAD.

EXPLANATION: The hardware did not initialize correctly. The PCNTNW driver did not load.

ACTION: Check the hardware. Make sure that the board's hardware setting matches its settings in the NET.CFG file.

PCNTW-DOS-7 YOU NEED ANOTHER PCNTNW MLID SECTION HEADING IN THE NET.CFG FILE IN ORDER TO LOAD THE MLID AGAIN.

EXPLANATION: You tried to load the PCNTNW MLID a second time. Normally, you would do this so that you could use two or more Ethernet controllers in the server. When two or more of the same type of Ethernet controllers are installed in the server, an associated PCNTNW MLID section heading must be specified in the NET.CFG file.

ACTION: Create a NET.CFG file and add the commands for both PCNTNW MLID boards to the file. Then, restart the server.

PCNTNW-DOS-8 A NET.CFG IS REQUIRED TO LOAD THE MLID AGAIN.

ACTION: Create a NET.CFG file and add the commands for both PCNTNW MLID boards to the file. Then, restart the server.

PCNTNW-DOS-9 THE NET.CFG ENTRY HAS BEEN IGNORED.

EXPLANATION: The PCNTNW ignored the NET.CFG entry.

ACTION: Verify that the entries in the NET.CFG file are correct.

THE PCNTNW MLID HAS BEEN SUCCESSFULLY REMOVED.

EXPLANATION: A request was made to unload a PCNTNW MLID. The PCNTNW MLID has been removed from memory.

ACTION: None.

PCNTNW-DOS-11 THE MLID DOES NOT SUPPORT FRAME <STRING:>. THE PROTOCOL KEYWORD HAS BEEN IGNORED.

EXPLANATION: The NET.CFG files specified the PROTOCOL option for a PCNTNW MLID. The specified frame type is not supported by the PCNTNW MLID.

ACTION: Check the PROTOCOL line in the NET.CFG file for possible omissions of required dashes and underscores or any misspellings.

PCNTNW-DOS-12 THE PROTOCOL KEYWORD MUST HAVE A FRAME TYPE. ENTRY IGNORED.

EXPLANATION: The PROTOCOL option was specified in the NET.CFG file for a PCNTNW MLID. The entry failed to specify the associated frame type for the protocol ID addition. An entry in the NET.CFG file for the PROTOCOL option
should use the following format:

LINK DRIVER PCNTNW
PROTOCOL IPX 8137 ETHERNET_II

ACTION: Specify a frame with the PROTOCOL option.

PCNTNW-DOS-13 THE MLID COULD NOT REGISTER PROTOCOL ID <STRING> FOR PROTOCOL STACK <STRING> FOR FRAME TYPE.

EXPLANATION: The PCNTNW MLID could not register the specified Protocol ID.

ACTION: Verify the protocol information in the NET.CFG file.

PCNTNW-DOS-14 THIS VERSION OF LSL IS NOT SUPPORTED.

EXPLANATION: The PCNTNW MLID cannot run successfully using this version of the LSL.

ACTION: Update the LSL.COM to a newer version.

PCNTNW-DOS-15 THE FRAME TYPE IS ALREADY ACTIVATED FOR FRAME <STRING>. THE NET.CFG ENTRY HAS BEEN IGNORED.

EXPLANATION: Two FRAME keywords under the same main section heading specified the same frame type. A specified frame type can be specified only once per driver.

ACTION: Remove the duplicate FRAME keyword entry.

PCNTNW-DOS-16 THE NODE ADDRESS WAS INCORRECTLY SPECIFIED IN NET.CFG.

EXPLANATION: You used the NODE ADDRESS option in the NET.CFG file to override the node address on the network board. The number specified was not a valid Ethernet address. An Ethernet address is six bytes in length. This error occurs if Bit 0 of the first address byte is a 1. This bit must always be 0. For example, if the first byte has the following address, an invalid Ethernet address is generated.

FIRST BYTE
7 6 5 4 3 2 1 0
_______________
0 0 0 0 0 0 0 1

This byte will produce node addresses in the 0100 0000 0000 to 01FF FFFF FFFF range (in hexadecimal), all of which will be invalid.

ACTION: Specify a valid node address in the NET.CFG file.

PCNTNW-DOS-17 AN INVALID KEYWORD WAS SPECIFIED IN NET.CFG ON LINE xx.

EXPLANATION: The keyword specified in the NET.CFG file is incorrect.

ACTION: Check the keyword in question. Make sure that the keyword is correctly spelled.

PCNTNW-DOS-18 THE FRAME TYPE SPECIFIED IN THE NET.CFG FILE IS NOT SUPPORTED.

EXPLANATION: The NET.CFG file specified the PROTOCOL option for a PCNTNW MLID. The specified frame type is not supported by the PCNTNW MLID.

ACTION: Check the PROTOCOL line in the NET.CFG file for possible omissions of required dashes and underscores, or any misspellings. Check the PCNTNW MLID documentation for supported frame types.

PCNTNW-DOS-19 AN INVALID ETHERNET NODE ADDRESS IS SPECIFIED IN NET.CFG. THE MLID MODIFIED THE INCORRECT ADDRESS BITS.

EXPLANATION: The NET.CFG file has an invalid node address. The PCNTNW MLID modified and corrected the address.

ACTION: Verify the node address entries in the NET.CFG file.

PCNTNW-DOS-50 THE BOARD CANNOT BE FOUND.

EXPLANATION: The Ethernet controller is either not configured correctly or is disabled.

ACTION: Perform the following steps:

1. Verify that the Ethernet jumper on the system board is set to the default, enabled position.
2. Check the settings for the Ethernet controller (for example, the I/O and interrupt request settings) against the settings in the NET.CFG. See "Resolving Hardware Configuration Conflicts" for information on setting the interrupt requests.
3. If the problem persists, go to "General Checkout."

PCNTNW-DOS-54 THE BOARD DID NOT RESPOND TO THE INITIALIZATION COMMAND.

EXPLANATION: The Ethernet controller initialization failed.

ACTION: Verify that the Ethernet jumper on the system board is set to the default, enabled position. Go to "General Checkout."

PCNTNW-DOS-58 THE BOARD DID NOT RESPOND TO THE INITIALIZATION COMMAND.

EXPLANATION: The IRQ setting might be incorrect with the hardware setting, or the EEPROM might be corrupted.

ACTION: Verify that the IRQ settings in the NET.CFG file match the configuration settings in the configuration programs. See "Resolving Hardware Configuration Conflicts" for information on setting the interrupt requests. Verify that the EEPROM on the system board is programmed correctly.

PCNTNW-DOS-61 PCI DEVICE IRQ NUMBER MISMATCH.

EXPLANATION: The IRQ number specified in the NET.CFG file does not match with the IRQ number assigned in the configuration programs.

ACTION: Remove the IRQ number in the NET.CFG file.

PCNTNW-DOS-64 THE DEVICE WAS NOT FOUND.

EXPLANATION: The driver cannot find any PCnet device in the server.

ACTION: Verify that the Ethernet enable jumper is set to the default (enable) position. Go to "100/10 Ethernet Diagnostics" to run the diagnostic utility.

PCNTNW-DOS-65 DEVICE NOT FOUND AT IOADDRESS.

EXPLANATION: The device was not found at the IO address specified in the NET.CFG file. The driver cannot find an Ethernet controller in the server.

ACTION: Verify that the IO address in the NET.CFG file matches with the with the board. Otherwise, remove the PORT keyword from the NET.CFG file.

PCNTNW-DOS-67 PCI SCAN SPECIFIED, DEVICE NOT FOUND.

EXPLANATION: The driver cannot locate the Ethernet controller on the PCI bus.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Use the BUSTYPE keyword to specify a value of PCI1.
3. If the problem persists, go to "100/10 Ethernet Diagnostics" to run the Ethernet diagnostics.

PCNTNW-DOS-75 UNSUPPORTED BUS ID SPECIFIED.

EXPLANATION: The bus ID number specified in the NET.CFG file is not supported by Novell.

ACTION: Correct the bus ID number in the NET.CFG file.

PCNTNW-DOS-76 WRONG BUS ID SPECIFIED.

EXPLANATION: The bus ID number specified in the NET.CFG file is different from the bus type found in the server.

ACTION: Correct the bus ID number in the NET.CFG.

PCNTNW-DOS-80 THE DMA PARAMETER IS NOT NECESSARY FOR PCI DEVICE.

EXPLANATION: The board does not require a DMA setting.

ACTION: Edit the NET.CFG file to delete the DMA parameter.

Novell NetWare OS/2 ODI Driver Messages

The following error messages are the for the NetWare OS/2 ODI driver. The explanation and recommended action is included with each message.

PCNTNW-OS2-1 THE LSL IS NOT LOADED.

EXPLANATION: The Link Support Layer module (LSL.SYS) is not loaded.

ACTION: Load LSL.SYS before loading the driver.

PCNTNW-OS2-21 COULD NOT ADD THE MLID PROTOCOL ID.

EXPLANATION: The PCNTNW MLID could not register the specified Protocol ID.

ACTION: Edit the NET.CFG file and correct the protocol information.

PCNTNW-OS2-22 COULD NOT ALLOCATE MEMORY. THE VIRTUAL BOARD DID NOT LOAD.

EXPLANATION: The driver could not allocate memory for the virtual adapter.

ACTION: Check the system configuration.

PCNTNW-OS2-54 THE BOARD DID NOT RESPOND TO THE INITIALIZATION COMMAND.

EXPLANATION: The board initialization failed.

ACTION: Verify that the Ethernet enable jumper is set to the default (enable) position. Go to "General Checkout."

PCNTNW-OS2-56 THIS INTERRUPT IS ALREADY USED AND CANNOT BE SHARED.

EXPLANATION: The interrupt is already used by another device and cannot be shared.

ACTION: Assign a different IRQ in the configuration programs. See "Resolving Hardware Configuration Conflicts" for information on setting the interrupt requests.

PCNTNW-OS2-58 THE BOARD DID NOT RESPOND TO THE INITIALIZATION COMMAND.

EXPLANATION: The IRQ setting might be incorrect with the hardware setting, or the EEPROM might be corrupted.

PCNTNW-OS2-61 PCI DEVICE IRQ NUMBER MISMATCH.

EXPLANATION: The IRQ number specified in the NET.CFG file does not match with the IRQ number assigned in the configuration programs. The IRQ numbers might be assigned automatically, or you might have manually assigned the IRQ
number.

ACTION: Remove the IRQ number in the NET.CFG file. Or, see "Resolving Hardware Configuration Conflicts" for information on setting the interrupt requests.

PCNTNW-OS2-64 THE DEVICE WAS NOT FOUND.

EXPLANATION: The driver cannot find the Ethernet controller in the server.

ACTION: Verify that the Ethernet enable jumper is set to the default (enable) position. Go to "General Checkout" on page 2.

PCNTNW-OS2-65 DEVICE NOT FOUND AT IOADDRESS.

EXPLANATION: The Ethernet controller cannot be found at the IO address specified in the NET.CFG file.

ACTION: Verify that the IO address in NET.CFG matches with the board. Otherwise, remove the PORT keyword from the NET.CFG file.

PCNTNW-OS2-67 PCI SCAN SPECIFIED, DEVICE NOT FOUND.

EXPLANATION: The driver cannot locate the Ethernet controller on the PCI bus.

ACTION: Do the following:

PCNTNW-OS2-73 UNABLE TO ALLOCATE MEMORY.

EXPLANATION: The driver could not allocate memory for the virtual board.

ACTION: Check the system configuration.

PCNTNW-OS2-80 THE DMA PARAMETER IS NOT NECESSARY TO PCI DEVICE.

EXPLANATION: The Ethernet controller does not require a DMA setting. This parameter is not a valid driver parameter.

ACTION: Edit the NET.CFG file to delete the DMA parameter.

NDIS 2.01 Driver Messages

The following error messages are for the NDIS 2.01 drivers. The explanation and recommended action are included with each message.

PCNTND-DOS-1 UNABLE TO OPEN THE PROTOCOL MANAGER.

EXPLANATION: The NDIS stack is not configured properly.

ACTION: Check and correct the configuration.

PCNTND-DOS-6 OUT OF MEMORY WHILE ALLOCATING BUFFERS.

EXPLANATION: The driver could not allocate the requested buffers.

ACTION: Check the system configuration. Edit the PROTOCOL.INI file to reduce the number of Txbuffers and Rxbuffers specified for the driver.

PCNTND-DOS-7 PROTOCOL MANAGER DEVICE ERROR.

EXPLANATION: The NDIS stack is not configured properly.

ACTION: Check and correct the configuration.

PCNTND-DOS-8 BAD STATUS FOR PROTOCOL MANAGER.

EXPLANATION: The NDIS stack is not configured correctly.

ACTION: Check and correct the configuration.

PCNTND-DOS-9 CANNOT FIND PROTOCOL.INI ENTRY.

EXPLANATION: The NDIS stack is not configured properly in the PROTOCOL.INI file.

ACTION: Check and correct the configuration.

PCNTND-DOS-10 THE PROTOCOL MANAGER IOCTL FAILED.

EXPLANATION: The NDIS stack is not configured properly in the PROTOCOL.INI file.

ACTION: Check and correct the configuration.

PCNTND-DOS-11 PROTOCOL MANAGER REGISTRATION FAILED.

EXPLANATION: The NDIS stack is not configured properly.

ACTION: Check and correct the configuration.

PCNTND-DOS-15 DEVICE NOT FOUND.

EXPLANATION: The driver cannot find an Ethernet controller in the server.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout."
3. Replace the system board.

PCNTND-DOS-16 PCI SCAN SPECIFIED, DEVICE NOT FOUND.

EXPLANATION: The driver cannot locate the Ethernet controller on the PCI bus.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout."
3. Replace the system board.

PCNTND-DOS-21 BOARD FAILED CHECKSUM TEST. PLEASE RUN CONFIGURATION UTILITY.

EXPLANATION: The driver cannot find an Ethernet controller.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout."

PCNTND-DOS-23 WARNING: PCNET IRQ FOUND =

EXPLANATION: The IRQ setting in PROTOCOL.INI does not match the hardware IRQ setting.

ACTION: Remove the IRQ setting from PROTOCOL.INI (or match the IRQ setting in PROTOCOL.INI with the configuration settings in the configuration programs. See "Resolving Hardware Configuration Conflicts" for information on setting the interrupt requests.)

PCNTNW-DOS-24 WARNING: PCNET IRQ DOESN'T MATCH PROTOCOL.INI.

EXPLANATION: The IRQ setting in PROTOCOL.INI does not match the hardware IRQ setting.

ACTION: Remove the IRQ setting from PROTOCOL.INI or match the IRQ setting in PROTOCOL.INI with the hardware jumper setting.

PCNTNW-DOS-25 PCI SCAN SPECIFIED, PCI BUS NOT FOUND!

EXPLANATION: The driver cannot locate the Ethernet controller on the PCI bus.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout."

PCNTNW-DOS-29 WARNING: DMA NUMBER IS NOT NECESSARY FOR PCI DEVICE.

EXPLANATION: The Ethernet controller does not require a DMA setting.

ACTION: Remove the DMA setting in PROTOCOL.INI.

PCNTNW-DOS-32 IRQ NUMBER IS ALREADY IN USE BY ANOTHER PCNET DEVICE.

EXPLANATION: The specified IRQ number is already in use by another Ethernet controller or device.

ACTION: Modify the IRQ setting in the PROTOCOL.INI file, or modify the IRQ settings in the configuration programs. See "Resolving Hardware Configuration Conflicts" for information on setting the interrupt requests in the configuration programs.

PCNTNW-DOS-33 PCNET DEVICE WITH SPECIFIED IOBASE IS ALREADY IN USE.

EXPLANATION: The specified IO address number is already in use by another Ethernet controller or device.

ACTION: Modify the IO address setting on the hardware, or modify the IO address setting in the PROTOCOL.INI file.

NDIS 3.0 Driver Messages

Windows NT error messages are logged into a log file. You can view the file with the Event Viewer. Error messages appear with the "PCNTN3" prefix followed by a "Missing Configuration Parameter" message and several hex numbers. The hex numbers must be converted to decimal values so that they correspond to the error numbers used in this manual.

PCNTN3-9 IO BASE ADDRESS IS ALREADY IN USE BY ANOTHER PCNET DEVICE.

EXPLANATION: The specified IO address number is already in use by another device.

ACTION: Modify the IO address setting on the hardware or modify the IO Address setting in the setup dialog box.

PCNTN3-13 IRQ AND/OR DMA NUMBER IS ALREADY IN USE BY ANOTHER DEVICE.

EXPLANATION: The specified IRQ is specified by another device.

ACTION: Modify the IRQ setting in the setup dialog box.

PCNTN3-18 PCI SCAN SPECIFIED, DEVICE NOT FOUND.

EXPLANATION: The driver cannot locate the Ethernet controller on the PCI bus.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default ENABLE position.
2. If the problem persists, go to "General Checkout."

PCNTN3-19 LANCEOPENADAPTER FAILED.

EXPLANATION: The configuration is set up incorrectly.

ACTION: Rerun the setup program.

PCNTN3-20 DEVICE AT SPECIFIED IO BASE ADDRESS NOT FOUND.

EXPLANATION: The Ethernet controller cannot be found at the specified IO address.

ACTION: Verify that the IO address matches with the board. Otherwise, remove the IO Address specification from the setup.

PCNTN3-21 DEVICE NOT FOUND.

EXPLANATION: The driver cannot find any PCnet device.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default ENABLE position.
2. Go to "General Checkout."

Packet Driver Messages

The following error messages are for the packet driver. The explanation and recommended action are included with each message.

PCNTPK-DOS-1 THE COMMAND SYNTAX IS PCNTPK [-N] [-D] [-W]
<INT=PACKET_INT_NO>
[IRQ=INT_NO] [IOADDR=IO_ADDR] [DMA=DMA_NO] [BUSTYPE=BUS]
[DMAROTATE] [TP] [LED0=XX] [BUSTYPE=BUS] [LED0=XX]
[LED2=XX] [LED3=XX]

EXPLANATION: The driver command was not entered correctly.

ACTION: If you entered the command from the command line, enter the command with the correct syntax. If the command is in the AUTOEXEC.NET file, edit the file to correct the syntax. The only parameters that should be included are PCNTPK and BUSTYPE=PCI1.

PCNTPK-DOS-2 UNABLE TO RESET THE PCNET DEVICE.

EXPLANATION: The software could not reset the Ethernet controller.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout."

PCNTPK-DOS-3 UNABLE TO INITIALIZE THE PCNET DEVICE.

EXPLANATION: The software could not initialize the Ethernet controller.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Check the interrupt settings in the configuration programs. For more information, go to "Resolving Hardware Configuration Conflicts."
3. If the problem persists, go to "General Checkout."

PCNTPK-DOS-5 THERE IS ALREADY A PACKET DRIVER AT XXXX.

EXPLANATION: The driver is already loaded at this memory location. It cannot be loaded a second time at the same location.

ACTION: Do not load the driver again. If you want to load the driver at a different memory location, specify another software interrupt address on the INT parameter.

PCNTPK-DOS-6 <IRQ=INT_NO> SHOULD BE BETWEEN 0 AND 15 INCLUSIVE.

EXPLANATION: The specified IRQ is out of range for the Ethernet controller.

ACTION: Use valid IRQ values.

PCNTPK-DOS-7 PACKET DRIVER FAILED TO INITIALIZE THE BOARD.

EXPLANATION: The board initialization failed.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout."

PCNTPK-DOS-8 <INT=PACKET_INT_NO> SHOULD BE IN THE RANGE 0X60 TO 0X80.

EXPLANATION: The specified software interrupt number is out of the allowable range.

ACTION: Specify a valid value for the INT parameter.

PCNTPK-DOS-12 PCI DEVICE IRQ NUMBER MISMATCH.

EXPLANATION: The specified IRQ number does not match with the IRQ number assigned by the PCI BIOS.

ACTION: Remove the IRQ setting.

PCNTPK-15 THE DEVICE WAS NOT FOUND.

EXPLANATION: The driver cannot find an Ethernet controller.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout."

PCNTPK-DOS-18 PCI SCAN SPECIFIED, DEVICE NOT FOUND.

EXPLANATION: The driver cannot locate the Ethernet controller on the PCI bus.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. If the problem persists, go to "General Checkout."

PACKET DRIVER IS AT SEGMENT XXXX.

EXPLANATION: The memory address where the packet driver is loaded is xxxx.

ACTION: None.

PACKET INTERRUPT NUMBER XXXX.

EXPLANATION: The interrupt number used by the packet driver is xxxx.

ACTION: None.

MY ETHERNET ADDRESS IS XXXXXXXXXXXX.

EXPLANATION: The Ethernet address of this station is xxxxxxxxxxxx.

ACTION: None.

MY ARCNET ADDRESS IS XXXX.

EXPLANATION: The ARCnet address of this station is xxxx.

ACTION: None.

UNIX Messages

The following error messages are for the following UNIX drivers:

- SCO UNIX LLI
- UnixWare DPLI
- SunSoft Solaris

PNT0-2 PCI SEARCH SPECIFIED, PCI DEVICE NOT FOUND!

EXPLANATION: The driver cannot locate the Ethernet controller on the PCI bus.

ACTION: Do the following:

1. Run netconfig to search for another Ethernet controller.
2. Verify that the Ethernet enable jumper is set to the default (enable) position.
3. If the problem persists, go to "General Checkout."

PNT0-6 CANNOT ALLOCATE MEMORY FOR THE ADAPTER DURING AN INTERRUPT. PLEASE CHECK THE STREAMS PARAMETERS.

EXPLANATION: The system is out of Streams memory blocks.

ACTION: Perform the following steps:

1. Use the CRASH utility to increase the number of Streams memory blocks for the failing size.
2. Modify the IRQ settings in the configuration programs, or run netconfig to match the hardware settings.

PNT0-6 CANNOT ALLOCATE MEMORY FOR THE ADAPTER DURING AN INTERRUPT! PLEASE CHECK THE STREAMS PARAMETERS.

EXPLANATION: On a SunSoft Solaris system, this message indicates that the system is out of Streams memory blocks.

ACTION: Use the CRASH utility to increase the number of Streams memory blocks for the failing size.

PNT0-7 CANNOT ALLOCATE MEMORY FOR THE ADAPTER DURING RESET! PLEASE CHECK YOUR STREAMS PARAMETERS.

EXPLANATION: The system is out of Streams memory blocks.

ACTION: Use the CRASH utility to increase the number of Streams memory blocks for the failing size.

PNT0-11 DEVICE NOT FOUND!

EXPLANATION: The driver cannot find an Ethernet controller.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout."

PNT0-12 DEVICE FAILED CHECKSUM TEST!

EXPLANATION: The driver cannot find an Ethernet controller.

ACTION: Do the following:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout."

PNT0-13 ADD_INTR_HANDLER FAILED! INTERRUPTS ALREADY ENABLED.

EXPLANATION: The IRQ specified or found conflicts with other devices in the system.

ACTION: Do the following:

1. Modify the hardware settings.
2. Run netconfig to match the hardware settings.

PNT0-14 CANNOT LOCATE HARDWARE.

EXPLANATION: The SunSoft Solaris driver cannot find any Ethernet controller.

ACTION: Perform the following steps:

1. Verify that the Ethernet enable jumper is set to the default (enable) position.
2. Go to "General Checkout."

PNT0-15 NO MORE DEVICES TO OPEN.

EXPLANATION: The SunSoft Solaris driver cannot find any more Ethernet controllers.

ACTION: Do the following:

1. Verify that additional IBM PCI Ethernet adapters are present or replace the Ethernet adapter that fails to respond.

2. Go to "General Checkout."

PNT0-17 DEVICE FAULT... RESET INITIATED!

EXPLANATION: The SunSoft Solaris driver has been reset due to device fault.

ACTION: Do the following:

1. Verify that additional IBM PCI Ethernet adapters are present or replace the PCnet card that fails to respond.
2. Go to "General Checkout."

PNT0-19 IRQ FOUND FOR PCNET HARDWARE DOES NOT MATCH SPACE.C!

EXPLANATION: This is a warning message referring to the IRQ found in the system.

ACTION: Ignore this message if you are sure that this is what you want to do. Otherwise, run netconfig to match the hardware settings.

PNT0-19 IRQ FOUND FOR PCNET HARDWARE DOES NOT MATCH PNT.CONF!

EXPLANATION: This is a warning message referring to the IRQ that the SunSoft Solaris driver found in the system.

ACTION: Ignore this message if you are sure that this is what you want to do. Otherwise, run netconfig to match the hardware settings.

PNT0-20 ADD_INTR_HANDLER FAILED! UNKNOWN INTERRUPT TYPE.

EXPLANATION: The IRQ specified or found conflicts with other devices in the system.

ACTION: Do the following:

1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

PNT0-21 ADD_INTR_HANDLER FAILED! OUT OF RANGE INTERRUPT NUMBER.

EXPLANATION: The IRQ specified or found conflicts with other devices in the system.

ACTION: Do the following:

1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

PNT0-22 ADD_INTR_HANDLER FAILED! OUT OF RANGE IPL.

EXPLANATION: The IRQ specified or found conflicts with other devices in the system.

ACTION: Do the following:

1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

PNT0-23 ADD_INTR_HANDLER FAILED! VECTOR ALREADY OCCUPIED.

EXPLANATION: The IRQ specified or found conflicts with other devices in the system.

ACTION: Do the following:

1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

PNT0-24 ADD_INTR_HANDLER FAILED! VECTOR ALREADY SHARED AT DIFFERENT IPL.

EXPLANATION: The IRQ specified or found conflicts with other devices in the system.

ACTION: Do the following:

1. Modify the hardware settings.
2. Run netconfig to search for another Ethernet controller.

PNT0-26 THE DMA NUMBER IS NOT NECESSARY FOR PCI DEVICE.

EXPLANATION: The IBM PCI Ethernet adapter does not require a DMA setting.

ACTION: Edit the SPACE.C file to delete the DMA parameter.

PNT0-29 THE IRQ NUMBER IS ALREADY IN USE BY ANOTHER

EXPLANATION: The IBM PCI Ethernet adapter

EXPLANATION: The specified IO address is already in use.

PNT0-31 IO ADDRESS IS NOT NECESSARY FOR THE PCI DEVICE.

EXPLANATION: The I/O address specified is not required.

ACTION: Remove the assigned IO address specified for the Ethernet controller.

100/10 ETHERNET DEVICE DRIVERS

The following is a list of Ethernet device derivers and the directory/path in which they are located for the operating systems supported by the PC Server 315 - Type 8638. The device drivers are located on three diskettes labeled 1, 2, and 3. These diskettes are supplied with the server.

NOTE:
The device driver names are in BOLD type.

Disk 1
- NDIS 2.0.1 Driver (DOS, OS/2)
A:\MSLANMAN.DOS\DRIVERS\ETHERNET\PCNTND\ PCNTND.DOS
A:\MSLANMAN.OS2\DRIVERS\ETHERNET\PCNTND\ PCNTND.OS2
A:\LANSRVR\PCNTND.OS2

- ODI Driver (DOS, OS/2, Server)
A:\NOVELL\SERVER\3.1X\PCNTNW.LAN
A:\NOVELL\SERVER\4.X\PCNTNW.LAN

- Novell Support files
A:\NOVELL\WKSTN\DOSODI\PCNTNW.COM
A:\NOVELL\WKSTN\OS2ODI\PCNTNW.OS2

- ODI LAPP Driver (DOS)
A:\LAPP\DOSODI\PCLAPP.COM

- NDIS 3.x for Windows NT 3.51
A:\WINNT351\AMDPCN.SYS

- SCO UNIX Open Server 5.0 MDI driver
Driver support is built into SCO UNIX 5.0.

- Unixware 2.0 DLPI driver
Driver support is built into UNIXWARE 2.x.

Disk 2
- DOS Client for IBM LAN Server
A:\IBMADOS\PCNTND.DOS
A:\IBMLSP\PCNTND.DOS

- Packet Driver
A:\PKTDRVR\PCNTPK.COM

Disk 3
- Sun Solaris Driver (for v2.4)
This diskette is Unix PkgAdd format. the driver's name extension is pcnt.

100/10 ETHERNET DIAGNOSTICS

You must use the Ethernet Diagnostic Diskette to perform diagnostic tests on the integrated Ethernet controller. This diagnostic diskette includes the LANAID utility program.

Backing Up the Ethernet Diagnostic Diskette

Use an operating system command, such as the DOS DISKCOPY command, to make a complete backup copy of the IBM PC Server PCI Ethernet diagnostic diskette.

Using the backup copy can prevent damage to the original diskette. The operating system documentation provides information on backing up diskettes.

Starting the Ethernet Diagnostics

To start the Ethernet Diagnostic Diskette:

1. Insert the backup copy of the Ethernet diagnostic diskette into the diskette drive.
2. Power-on the server, or if it is already on, shut down the operating system and restart the server.
3. Type /DIAGS; then, press ENTER.
4. Follow the instructions on the screen.
5. When the diagnostic tests are complete, remove the diskette from the diskette drive; then, restart the server.

100/10 ETHERNET PORTS

The PC Server 315 Type 8638 has Ethernet connectors for 10Base-T or Attachment Unit Interface (AUI) devices. The controller automatically detects which port is connected to the network, and then uses that port for communication.

NOTES:
- If the server comes with an Ethernet interface cable, it must be installed to comply with FCC requirements.
- The cables used in a 10BASE-T link segment do not require grounding. However, all of the devices connected to the cables must be grounded.

To connect the 10Base-T port to a 10Base-T port on a repeater, use an unshielded twisted-pair (UTP) cable with RJ-45 connectors at both ends. Use a straight-through UTP cable when connecting to a crossover port (also called MDI-X port), and use crossover cables to connect to a repeater that is not a crossover port (also known as a MDI port).

To connect the AUI port to a 10Base-5, 10Base-2, or 10Base-F segment, use an AUI cable.

Search Keywords

Document Category

Networking

Date Created

11-02-99

Last Updated

11-02-99

Revision Date

11-02-2000

Brand

IBM PC Server

Product Family

PC Server 315

Machine Type

8638

Model

TypeModel

Retain Tip (if applicable)

Reverse Doclinks
and Admin Purposes

	Search Keywords
	Document Category	Networking
	Date Created	11-02-99
	Last Updated	11-02-99
	Revision Date	11-02-2000
	Brand	IBM PC Server
	Product Family	PC Server 315
	Machine Type	8638
	Model
	TypeModel
	Retain Tip (if applicable)
	Reverse Doclinks and Admin Purposes