Ethernet Teaming Messages - IBM eServer 200 xSeries User Reference Manual

Type 8479
Hide thumbs Also See for eServer 200 xSeries:
Table of Contents

Advertisement

Table 14. NDIS (Windows NT) driver messages for the Ethernet controller.
Error code (hex)
0x10
Explanation: Did not find any Ethernet controllers.
Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled.
0x11
Explanation: Multiple Ethernet controllers found, but none matched the required ID.
Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled.
0x13
Explanation: Did not find any Ethernet controllers that matched the required subven/subdev.
Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled.
0x16
Explanation: Single adapter found, but multiple instances tried to load.
Action: Using the Configuration/Setup Utility program, make sure that Ethernet is enabled, and that
the slot containing the IBM xSeries 200 10/100 Ethernet Adapter or the IBM 10/100 Etherjet PCI
adapter is enabled.
0x17
Explanation: Slot parameter not specified in the registry.
Action: Remove the adapter driver and reinstall it. If the problem persists, call for service.
All other 4-
Action: Call for service.
character
hexadecimal
codes

Ethernet teaming messages

This section describes the messages associated with Ethernet teaming.
Table 15. NDIS (Windows NT) driver teaming messages for the Ethernet controller.
Event ID
01
Error
02
Error
03
Error
04
Error
05
Error
06
Informational
88
IBM xSeries 200: User's Reference
Type
Explanation: Team name and physical adapter name are the same. This is
an invalid configuration.
Action: Reconfigure the adapter team by double-clicking the PROSet icon in
the control panel.
Explanation: Unable to allocate required resources.
Action: Free some memory resources and restart.
Explanation: Unable to read required registry parameters.
Action: Reconfigure the adapter team by double-clicking the PROSet icon in
the control panel.
Explanation: Unable to bind to physical adapter.
Action: Reconfigure the adapter team by double-clicking the PROSet icon in
the control panel.
Explanation: Unable to initialize an adapter team.
Action: Reconfigure the adapter team by double-clicking the PROSet icon in
the control panel.
Explanation: Team nn. Primary adapter is initialized.
Action: None.
Description
Description

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents