Filter
Top Products
v Any system that is accessing this system remotely must have the port
number changed to match the value you type. On the remote system, you
can change this value in the Add Remote System window.
v Any system that contains this system in its Notification list must change the
port number to the new port number. On the remote system, you can change
the port number in the Notification Manager by clicking Modify system .
No controllers were found in this system.
Explanation:
The ServeRAID Manager did not detect any controllers in the system.
Action:
If you know there are controllers in the system, the ServeRAID Manager might not
identify the controllers because of the following:
v The device driver is not loaded.
v (Linux, UnixWare, and OpenServer only) You are not running the ServeRAID
Manager as ″root.″ The ServeRAID Manager cannot access the device driver
unless it is run with root authority. Without access to the device driver, the
ServeRAID Manager cannot identify any controllers.
If
the problem persists, contact your service representative.
Host name [ID] is unknown or the network is down
Explanation:
The ServeRAID Manager could not access the remote system.
Action:
Verify the following:
1. The remote system is on.
2. Both the local and remote systems are connected to the network.
3. TCP/IP networking support is configured on both the local and remote
systems.
4. The network is functioning. Verify that you can ping the remote system.
Failed to connect to host name [ID] due to incompatible versions
[Local=number Remote=number]
Explanation:
The local and remote versions of the ServeRAID Manager are incompatible
versions.
Action:
Upgrade the older version of the ServeRAID Manager to the newer version.
Chapter 5. Troubleshooting ServeRAID Manager 227