HP LH4r Installation and configuration of the HP NetRAID, NetRAID-1 and NetRAI - Page 134

Common Problems

Get HP LH4r - NetServer - 256 MB RAM PDF manuals and user guides View all HP LH4r manuals
Add to My Manuals
Save this manual to your list of manuals

Page 134 highlights

Chapter 11 Troubleshooting Common Problems Without NetRAID Assistant, the client(s) and server(s) connect normally, but the NetRAID Assistant cannot connect to any servers For NetRAID Assistant to connect to a server, it must resolve the server via TCP/IP. Ping the server by name from the client or server that will run HP NetRAID Assistant. If this is unsuccessful, then the client or server that will run HP NetRAID Assistant cannot resolve the server using TCP/IP. Confirm the following conditions: • The IP addresses are unique. • The subnet mask is not causing a group resolution problem. • The hosts file contains correct names and IP addresses for all servers with HP NetRAID Series adapters to be managed. No response when connecting to a server; may get Server Not Responding message after several minutes The server is likely to be down and the connection attempt/timeout may take two minutes before a message is generated. Be sure the selected server is up. NOTE If the server is still not up when the timeout message is displayed, HP NetRAID Assistant will exit. Can't unload raidserv.nlm If the adapter in a NetWare server is being accessed by a configuration utility (HP NetRAID Assistant in Full Access mode or HP NetRAID Config), the raidserv.nlm module cannot be unloaded until the adapter is no longer being accessed. This prevents a critical operation in the adapter, such as a disk rebuild, from being interrupted. HP NetRAID Assistant does not list any servers when started (other than "local") When HP NetRAID Assistant starts, the Main Screen only lists "(Local)" in the pull-down list of servers. The Registration Server may be down, or no servers may have checked in with it. Be sure that the Registration Server is working and that it started before the other servers. Servers can only log into the Registration Server when the access server (NT) or raidserv.nlm (NetWare) executes. 126

  • 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
Chapter 11
Troubleshooting
126
Common Problems
Without NetRAID Assistant, the client(s) and server(s) connect normally, but the
NetRAID Assistant cannot connect to any servers
For NetRAID Assistant to connect to a server, it must resolve the server via
TCP/IP. Ping the server by name from the client or server that will run HP
NetRAID Assistant. If this is unsuccessful, then the client or server that will run
HP NetRAID Assistant cannot resolve the server using TCP/IP. Confirm the
following conditions:
•
The IP addresses are unique.
•
The subnet mask is not causing a group resolution problem.
•
The
hosts
file contains correct names and IP addresses for all servers with
HP NetRAID Series adapters to be managed.
No response when connecting to a server; may get Server Not Responding
message after several minutes
The server is likely to be down and the connection attempt/timeout may take two
minutes before a message is generated. Be sure the selected server is up.
NOTE
If the server is still not up when the timeout message is
displayed, HP NetRAID Assistant will exit.
Can't unload raidserv.nlm
If the adapter in a NetWare server is being accessed by a configuration utility (HP
NetRAID Assistant in Full Access mode or HP NetRAID Config), the
raidserv.nlm
module cannot be unloaded until the adapter is no longer being
accessed. This prevents a critical operation in the adapter, such as a disk rebuild,
from being interrupted.
HP NetRAID Assistant does not list any servers when started (other than "local")
When HP NetRAID Assistant starts, the Main Screen only lists
"<clientname>(Local)" in the pull-down list of servers. The Registration Server
may be down, or no servers may have checked in with it.
Be sure that the Registration Server is working and that it started before the other
servers. Servers can only log into the Registration Server when the access server
(NT) or raidserv.nlm (NetWare) executes.