IBM 8478 Hardware Maintenance Manual - Page 37

Table, NetWare, driver, messages, Ethernet, controller, continued

Get IBM 8478 - Eserver xSeries 200 PDF manuals and user guides
UPC - 087944650553
View all IBM 8478 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 37 highlights

Table 4. NetWare driver messages for the Ethernet controller (continued) Message Description 'xxx' is not supported for AFT team. Explanation: A bind command has been issued for adapters not supported by AFT.NLM. Action: Make sure that you attempt to bind only adapters supported by AFT.NLM. Primary and Secondary adapters do not match. AFT group is not created. Explanation: A bind command was entered for an adapter team that is a combination of server and client adapters. An AFT team must be a grouping of the same classification of adapter. Action: Verify that all the adapters bound in a team are of the same classification. Requested number of Secondary cards are not found. Explanation: The number of adapters specified in the bind command could not be located. Action: Verify the numbers and slot locations of the adapters to be bound. If the problem persists, contact your network supplier. Failed to create AFT group. Make sure that the drivers for supported adapters are loaded, primary adapter is bound to protocols, and secondary adapter is not bound to any protocols. Explanation: Binding of protocol failed. Protocol is either not bound to any adapter or is bound to more than one adapter in the group. Action: Ensure that the protocol is bound to only adapter in an AFT team. Error identifying slot numbers for the specified board names. Explanation: The mapping between the board name entered and the slot number for an adapter could not be established. Action: Check the board name for the adapter before issuing the bind command. If the problem persists, contact your network supplier. Can't unbind Explanation: The number entered in the specified slot from unbind command was not the primary AFT group. Make adapter in an AFT group. Action: Reissue sure that the slot you the unbind command and specify the slot specified is for the number for the primary adapter. primary adapter in an AFT group. LAN adapter at slot nnnn (Port 0xaa) failed to reset. Check the state of the adapter. Explanation: The adapter that you specified could not be initialized. Action: 1. Load the driver for the supported adapter. 2. Check that the adapter is seated properly in the slot and try loading the AFT module again. If the problem persists, contact your network supplier. Chapter 3. Diagnostics 27

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
Table
4.
NetWare
driver
messages
for
the
Ethernet
controller
(continued)
Message
Description
’
xxx
’
is
not
supported
for
AFT
team.
Explanation:
A
bind
command
has
been
issued
for
adapters
not
supported
by
AFT.NLM.
Action:
Make
sure
that
you
attempt
to
bind
only
adapters
supported
by
AFT.NLM.
Primary
and
Secondary
adapters
do
not
match.
AFT
group
is
not
created.
Explanation:
A
bind
command
was
entered
for
an
adapter
team
that
is
a
combination
of
server
and
client
adapters.
An
AFT
team
must
be
a
grouping
of
the
same
classification
of
adapter.
Action:
Verify
that
all
the
adapters
bound
in
a
team
are
of
the
same
classification.
Requested
number
of
Secondary
cards
are
not
found.
Explanation:
The
number
of
adapters
specified
in
the
bind
command
could
not
be
located.
Action:
Verify
the
numbers
and
slot
locations
of
the
adapters
to
be
bound.
If
the
problem
persists,
contact
your
network
supplier.
Failed
to
create
AFT
group.
Make
sure
that
the
drivers
for
supported
adapters
are
loaded,
primary
adapter
is
bound
to
protocols,
and
secondary
adapter
is
not
bound
to
any
protocols.
Explanation:
Binding
of
protocol
failed.
Protocol
is
either
not
bound
to
any
adapter
or
is
bound
to
more
than
one
adapter
in
the
group.
Action:
Ensure
that
the
protocol
is
bound
to
only
adapter
in
an
AFT
team.
Error
identifying
slot
numbers
for
the
specified
board
names.
Explanation:
The
mapping
between
the
board
name
entered
and
the
slot
number
for
an
adapter
could
not
be
established.
Action:
Check
the
board
name
for
the
adapter
before
issuing
the
bind
command.
If
the
problem
persists,
contact
your
network
supplier.
Can’t
unbind
specified
slot
from
AFT
group.
Make
sure
that
the
slot
you
specified
is
for
the
primary
adapter
in
an
AFT
group.
Explanation:
The
number
entered
in
the
unbind
command
was
not
the
primary
adapter
in
an
AFT
group.
Action:
Reissue
the
unbind
command
and
specify
the
slot
number
for
the
primary
adapter.
LAN
adapter
at
slot
nnnn
(Port
0x
aa
)
failed
to
reset.
Check
the
state
of
the
adapter.
Explanation:
The
adapter
that
you
specified
could
not
be
initialized.
Action:
1.
Load
the
driver
for
the
supported
adapter.
2.
Check
that
the
adapter
is
seated
properly
in
the
slot
and
try
loading
the
AFT
module
again.
If
the
problem
persists,
contact
your
network
supplier.
Chapter
3.
Diagnostics
27