Netfinity 5000 - Ethernet Controller Messages

25.090 bytes

Parts Information

Document ID: DDSE-424SQN

Netfinity 5000 - Ethernet Controller Messages

Applicable to: World-Wide

Ethernet Controller Messages

The integrated Ethernet controller might display messages from the following drivers:
Novell NetWare or IntraNetWare Server ODI
NDIS Adapter for level 2.01 (OS/2)
NDIS Adapter for level 4.0 (Windows NT)
SCO UNIX LLI

Novell NetWare or IntraNetWare Server ODI Driver Messages:
The following error messages are for the Novell NetWare or IntraNetWare server ODI driver. The explanation and recommended action are included with each message.

Error Message

Explanation

Action

PCNTNW-NW-026 The MSM is unable to parse a required custom keyword.

The user entered an incorrect parameter keyword.

Reload the driver using the correct keyword.

PCNTNW-NW-054 The adapter did not respond to the initialization command.

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

Verify that the PCI Ethernet device type is set to the default (enabled) setting in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic
Test Programs to run the diagnostic utility.

PCNTNW-NW-058 The adapter did not respond to the initialization command.

The interrupt request (IRQ) setting might not be valid or the EEPROM information might be incorrect.

Make sure the IRQ settings are correct in the Configuration/Setup utility programs. See PCI Bus Control for information on setting the interrupt requests. If the IRQ settings are correct, replace the system board.

PCNTNW-NW-66 The cable might be disconnected from the adapter.

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

Verify that a cable is connected to the Ethernet port.

PCNTNW-NW-071 The matching virtual adapter could not be found.

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

If you installed an Ethernet adapter, such as an IBM Netfinity 10/100 Fault Tolerant Adapter, as part of Ethernet redundancy (failover), make sure that the adapter is seated correctly. If the adapter is seated correctly, replace the adapter.

PCNTNW-NW-072 A resource tag is unavailable.

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

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

PCNTNW-NW-073 Unable to allocate memory.

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

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

PCNTNW-NW-074 The hardware interrupt cannot be set.

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

Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). Make sure that the interrupt request numbers are set correctly. If you are using an ISA adapter, make sure resources are reserved as ISA Legacy in the Configuration/Setup utility programs (see Plug and Play.)

PCNTNW-NW-075 The Multiple Link Interface Driver (MLID) cannot be registered with the Link Support Layer (LSL).

An error occurred while the driver was trying to register with the LSL.

Check the version of the NetWare or IntraNetWare Operating System. Make sure that this driver is correct for the version of NetWare or IntraNetWare that you are using. Restart the server.

PCNTNW-NW-079 The Multiple Link Interface Driver (MLID) did not initialize MSMTx Free Count.

The MSMTx Free Count is not initialized correctly.

Restart the server.

PCNTNW-NW-086 The driver parameter block is too small.

The driver parameter block is too small.

Restart the server.

PCNTNW-NW-087 The media parameter block is too small.

The driver media parameter block is too small.

Restart the server.

PCNTNW-NW-091 The hardware configuration conflicts.

You tried to load a new frame type for the existing controller. The hardware assumptions made in doing so are incorrect. This error can also occur if you try to specify a mode (such as, redundancy) that conflicts with another specified mode.

Make sure that the hardware configuration matches the software settings. See PCI Bus Control for information on viewing and changing interrupt requests.

PCNTNW-NW-126 The group bit in the node address override was cleared.

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.

None.

PCNTNW-NW-127 The local bit in the node address override was set.

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.

None. Message is for information only.

PCNTNW-NW-164 The device was not found.

The driver cannot find an Ethernet controller in the server.

Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic Test Programs to run the diagnostic utility.

PCNTNW-NW-165 The device was not found at IOADDRESS.

The Ethernet controller cannot be found at the I/O address
specified.

The Ethernet controller does not require a parameter for the I/O
address. Remove the I/O address parameter.

PCNTNW-NW-167 PCI scan specified, device not found.

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

Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic Test Programs to run the diagnostic utility.

PCNTNW-NW-180 The DMA parameter is not necessary for PCI device.

The Ethernet controller does not require a DMA setting.

None necessary, message is for information only.

NDIS 2.01 (OS/2) Driver Messages: The following error messages are for the NDIS 2.01 (OS/2) drivers. The explanation and recommended action are included with each message.

Error Message

Explanation

Action

PCNTND-1 Unable to open the Protocol Manager.

The NDIS stack is not configured correctly.

Check and correct your configuration.

PCNTND-6 Out of memory while allocating buffers.

The driver could not allocate the requested buffers.

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

PCNTND-7 A Protocol Manager device error occurred.

The NDIS stack is not configured correctly.

Check and correct your configuration.

PCNTND-8 Bad status for the Protocol Manager.

The NDIS stack is not configured correctly in the PROTOCOL.INI file.

Check and correct your configuration.

PCNTND-9 Cannot find the PROTOCOL.INI entry.

The NDIS stack is not configured correctly in the PROTOCOL.INI file.

Check and correct your configuration.

PCNTND-10 The Protocol Manager Input Output Control (IOCTL) failed.

The NDIS stack is not configured correctly in the PROTOCOL.INI file.

Check and correct your configuration.

PCNTND-11 Protocol Manager registration failed.

The NDIS stack is not configured correctly.

Check and correct your configuration.

PCNTND-15 Device not found.

The driver cannot find an Ethernet controller in the server.

Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic Test Programs to run the diagnostic utility.

PCNTND-16 PCI scan specified, device not found.

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

Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic Test Programs to run the diagnostic utility.

PCNTND-21 The adapter failed the checksum test.

The driver cannot find an Ethernet controller.

Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic Test Programs to run the diagnostic utility.

PCNTND-23 WARNING: PCNET IRQ found = xx

The interrupt request (IRQ) setting ( xx) in the PROTOCOL.INI file does not match the hardware IRQ setting.

Remove the IRQ setting from the PROTOCOL.INI file or change the IRQ setting in the PROTOCOL.INI file to match the IRQ setting shown in the PCI Routing selection of the System Information menu in the Configuration/Setup Utility. (See PCI Routing.)

PCNTND-24 WARNING: PCNET IRQ does not match PROTOCOL.INI.

The interrupt request (IRQ) setting in the PROTOCOL.INI file does not match the hardware IRQ setting.

Remove the IRQ setting from the PROTOCOL.INI file or change the IRQ setting in the PROTOCOL.INI file to match the IRQ setting shown in the PCI Routing selection of the System Information menu in the Configuration/Setup Utility. (See PCI Routing.)

PCNTND-25 PCI scan specified, PCI bus not found

The driver cannot locate the PCI bus on your server.

Go to Diagnostic Test Programs to run the Diagnostic utility.

PCNTND-29 WARNING: DMA number is not necessary for PCI
device.

The Ethernet controller does not require a DMA setting.

Remove the DMA setting in the PROTOCOL.INI file.

PCNTND-33 PCNET device with specified IOBASE is already in use.

The specified I/O address number is already in use by another Ethernet controller or device.

Remove the I/O address setting in the PROTOCOL.INI file.

NDIS 4.0 (Windows NT) Driver Messages: The following error messages are for the NDIS 4.0 drivers. The explanation and recommended action are included with each message.

Error Message

Explanation

Action

PermaNet(tm) Server: No Secondary Adapter Found. Grouping Mode is disabled.

The failover option requires an adapter that is compatible with
the device driver of the Ethernet controller on the system board. No such
adapter was found.

Make sure the correct adapter is installed.

PermaNet(tm) Server: Problem Occurs on the Primary Adapter. Switching over to the Secondary Adapter.

The system detected a problem with the primary Ethernet connection and has transferred all network traffic to the secondary Ethernet controller.

Identify the cause of the failure on the primary Ethernet connection. Restoring the operational state of the primary connection will cause the network traffic to automatically transfer to the primary Ethernet controller.

PermaNet(tm) Server: Switching back to Primary Adapter.

The primary Ethernet connection is now operating correctly. Network traffic will automatically transfer to the primary Ethernet controller.

None needed, message is for information only.

UNIX Messages: The following error messages are for the SCO UNIX LLI driver.

Error Message

Explanation

Action

pnt0-2 PCI search specified, PCI device not found!

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

Run the NETCONFIG program to search for another Ethernet controller. Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the problem persists, go to Diagnostic Test Programs to run the diagnostic utility.

pnt0-6 Cannot allocate memory for the adapter during an interrupt. Please check your Streams parameters.

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

Use the CRASH utility to increase the number of Streams memory blocks. Modify the interrupt request (IRQ) settings in the Configuration/Setup utility programs, or run the NETCONFIG program to match the hardware settings.

pnt0-7 Cannot allocate memory for the adapter during reset. Please check your Streams parameters.

The system is out of Streams memory blocks.

Use the CRASH utility to increase the number of Streams memory blocks.

pnt0-11 Device not found!

The driver cannot find an Ethernet controller.

Run the NETCONFIG program to search for another Ethernet controller. Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the problem persists, go to Diagnostic Test Programs to run the diagnostic utility.

pnt0-12 Device failed checksum test!

The driver cannot find an Ethernet controller.

Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the problem persists, go to Diagnostic Test Programs to run the diagnostic utility.

pnt0-13 add_intr_handler failed! Interrupts already enabled.

The interrupt request (IRQ) that was specified, or the IRQ that was found, conflicts with other devices in the server.

Modify your hardware settings. Run the NETCONFIG program to match the hardware settings.

pnt0-14 Cannot locate hardware.

The SunSoft Solaris driver cannot find any Ethernet controller.

Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the problem persists, go to Diagnostic Test Programs to run the diagnostic utility.

pnt0-15 No more devices to open.

The SunSoft Solaris driver cannot find any more Ethernet controllers.

Verify that additional Ethernet adapters are present or replace the Ethernet adapter that fails to respond. If the problem persists, go to Diagnostic Test Programs to run the diagnostic utility.

pnt0-17 Device fault...Reset initiated!

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

Verify that additional Ethernet adapters are present or replace the Ethernet adapter that fails to respond. If the problem persists, go to Diagnostic Test Programs to run the diagnostic utility.

pnt0-19 IRQ found for PCnet hardware does not match space.c (or pnt.conf)!

This is a warning message referring to the interrupt request (IRQ) that the SunSoft Solaris driver found in the system.

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

pnt0-20 add_intr_handler failed! Unknown interrupt type.

The interrupt request (IRQ) that was specified, or the IRQ that was found, conflicts with other devices in the server.

Modify your hardware settings. Run the NETCONFIG program to search for another Ethernet controller.

pnt0-21 add_intr_handler failed! Out of range interrupt number.

The interrupt request (IRQ) that was specified, or the IRQ that was found, conflicts with other devices in the server.

Modify your hardware settings. Run the NETCONFIG program to search for another Ethernet controller.

pnt0-22 add_intr_handler failed! Out of range IPL.

The interrupt request (IRQ) that was specified, or the IRQ that was found, conflicts with other devices in the server.

Modify your hardware settings. Run the NETCONFIG program to search for another Ethernet controller.

pnt0-23 add_intr_handler failed! Vector already occupied.

The interrupt request (IRQ) that was specified, or the IRQ that was found, conflicts with other devices in the server.

Modify your hardware settings. Run the NETCONFIG program to search for another Ethernet controller.

pnt0-24 add_intr_handler failed! Vector already shared at different IPL.

The interrupt request (IRQ) that was specified, or the IRQ that was found, conflicts with other devices in the server.

Modify your hardware settings. Run the NETCONFIG program to search for another Ethernet controller.

pnt0-26 The DMA number is not necessary for PCI device.

The Ethernet adapter does not require a DMA setting.

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

pnt0-29 The IRQ number is already in use.

The specified I/O address is already in use.

Run the NETCONFIG program to modify your hardware settings.

pnt0-31 I/O address is not necessary for the PCI device.

The I/O address specified is not required.

Remove the assigned I/O address specified for the Ethernet controller.

Search Keywords

Document Category

Networking

Date Created

10-11-98

Last Updated

12-11-98

Revision Date

12-11-99

Brand

IBM PC Server

Product Family

Netfinity 5000

Machine Type

8659

Model

ALL

TypeModel

Retain Tip (if applicable)

Reverse Doclinks
and Admin Purposes

Error Message	Explanation	Action
PCNTNW-NW-026 The MSM is unable to parse a required custom keyword.	The user entered an incorrect parameter keyword.	Reload the driver using the correct keyword.
PCNTNW-NW-054 The adapter did not respond to the initialization command.	The board did not respond when the driver tried to initialize it.	Verify that the PCI Ethernet device type is set to the default (enabled) setting in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic Test Programs to run the diagnostic utility.
PCNTNW-NW-058 The adapter did not respond to the initialization command.	The interrupt request (IRQ) setting might not be valid or the EEPROM information might be incorrect.	Make sure the IRQ settings are correct in the Configuration/Setup utility programs. See PCI Bus Control for information on setting the interrupt requests. If the IRQ settings are correct, replace the system board.
PCNTNW-NW-66 The cable might be disconnected from the adapter.	The cable might be disconnected from the server's Ethernet port.	Verify that a cable is connected to the Ethernet port.
PCNTNW-NW-071 The matching virtual adapter could not be found.	You tried to load another instance of the driver with a different I/O address. This new adapter could not be found.	If you installed an Ethernet adapter, such as an IBM Netfinity 10/100 Fault Tolerant Adapter, as part of Ethernet redundancy (failover), make sure that the adapter is seated correctly. If the adapter is seated correctly, replace the adapter.
PCNTNW-NW-072 A resource tag is unavailable.	The driver tried to allocate some resources that were not available.	Add or free some memory in the server. Then, restart the server.
PCNTNW-NW-073 Unable to allocate memory.	The driver failed to allocate the memory needed for normal operation.	Add more memory, or free some memory resources in the server. Then, restart the server.
PCNTNW-NW-074 The hardware interrupt cannot be set.	An attempt was made to initialize a given hardware interrupt. The attempt was not successful.	Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). Make sure that the interrupt request numbers are set correctly. If you are using an ISA adapter, make sure resources are reserved as ISA Legacy in the Configuration/Setup utility programs (see Plug and Play.)
PCNTNW-NW-075 The Multiple Link Interface Driver (MLID) cannot be registered with the Link Support Layer (LSL).	An error occurred while the driver was trying to register with the LSL.	Check the version of the NetWare or IntraNetWare Operating System. Make sure that this driver is correct for the version of NetWare or IntraNetWare that you are using. Restart the server.
PCNTNW-NW-079 The Multiple Link Interface Driver (MLID) did not initialize MSMTx Free Count.	The MSMTx Free Count is not initialized correctly.	Restart the server.
PCNTNW-NW-086 The driver parameter block is too small.	The driver parameter block is too small.	Restart the server.
PCNTNW-NW-087 The media parameter block is too small.	The driver media parameter block is too small.	Restart the server.
PCNTNW-NW-091 The hardware configuration conflicts.	You tried to load a new frame type for the existing controller. The hardware assumptions made in doing so are incorrect. This error can also occur if you try to specify a mode (such as, redundancy) that conflicts with another specified mode.	Make sure that the hardware configuration matches the software settings. See PCI Bus Control for information on viewing and changing interrupt requests.
PCNTNW-NW-126 The group bit in the node address override was cleared.	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.	None.
PCNTNW-NW-127 The local bit in the node address override was set.	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.	None. Message is for information only.
PCNTNW-NW-164 The device was not found.	The driver cannot find an Ethernet controller in the server.	Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic Test Programs to run the diagnostic utility.
PCNTNW-NW-165 The device was not found at IOADDRESS.	The Ethernet controller cannot be found at the I/O address specified.	The Ethernet controller does not require a parameter for the I/O address. Remove the I/O address parameter.
PCNTNW-NW-167 PCI scan specified, device not found.	The driver cannot locate the Ethernet controller on the PCI bus.	Verify that the PCI Ethernet device type is set to the default (enabled) position in the Configuration/Setup utility programs (see PCI Bus Control). If the Ethernet adapter is enabled, go to Diagnostic Test Programs to run the diagnostic utility.
PCNTNW-NW-180 The DMA parameter is not necessary for PCI device.	The Ethernet controller does not require a DMA setting.	None necessary, message is for information only.

	Search Keywords
	Document Category	Networking
	Date Created	10-11-98
	Last Updated	12-11-98
	Revision Date	12-11-99
	Brand	IBM PC Server
	Product Family	Netfinity 5000
	Machine Type	8659
	Model	ALL
	TypeModel
	Retain Tip (if applicable)
	Reverse Doclinks and Admin Purposes