Q: Why is the ServeRAID Manager starting in local mode only?
A: If your network is having trouble, ServeRAID Manager starts in local mode because the Manager cannot get an Internet address.
For example, if you have networking difficulties with your intranet, the Manager comes up in local mode only.
Q: (For Microsoft® Windows NT® 4.0 only) Why can't the ServeRAID Manager find the NFSTCPPR.DLL or NFSTJDLL.DLL?
A: You must start the ServeRAID Manager from the directory it was installed to (for example, the default of C:\Program Files\Netfinity\RaidMan). The installation utility creates a shortcut on the desktop that starts the Manager from the install directory. If you start the Manager from the command line, you should first change directory (that is, cd) to the install directory and then issue the command RaidMan.bat.
Q: (For Microsoft Windows NT 4.0 only) Why can't the ServeRAID Manager find the help HTML files?
A: You must start the ServeRAID Manager from the directory it was installed to (for example, the default of C:\Program Files\Netfinity\RaidMan). The installation utility creates a shortcut on the desktop that starts the Manager from the install directory. If you start the Manager from the command line, you should first change directory (that is, CD) to the install directory and then issue the command RaidMan.bat.
Q: (For Microsoft Windows NT 4.0 only) When I UN-install the ServeRAID Manager, I get the following message:
UN-install completed. Some elements could not be removed. You should manually remove items related to this application.
What happened, and what should I remove to complete the UN-install?
A: The files that UN-install did not remove are:
If you want to remove these files,
they reside in the installation directory (the default installation directory
is
C:\Program Files\Netfinity\RaidMan). The file names are:
These files are created the first time you run the ServeRAID Manager 3.50. Therefore, if you UN-install the Manager without having ever run it, you will not see the above message from UN-install
Q: Why didn't any controllers appear in the Tree view, even though I know I have controllers?
A:
Q: Why can't I log-in to a remote system?
A: Security is enabled by default.
Q: Why don't my drives blink when I use Identify drives?
Identify drives only works on controllers with a SAF-TE processor and the appropriate firmware. If a drive light or series of drives' lights do not blink, it is because all or part of the subsystem is not controlled by the processor or you do not have the correct firmware.
For example, if SCSI channel 1 has the processor, but SCSI channel 3 does not, and you select to identify the Physical drive, only SCSI channel 1 will blink.
As another example, if you created a logical drive across a physical drive that did not have the processor, then even if the other physical drives do have the processor, the logical drive will not blink.