![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
StorageExpress(TM) system: StorageExpress Hardware Symptoms/Solutions
Contents:
"BACKUP FAILS WITH ERROR: FAILED TO CONNECT TO TARGET SERVICE AGENT: FFFFFFC6"
Description
There are some documented problems with the TSA (v3.11) that ships with
the current version of NetWare 3.11. When this version of the TSA is
loaded on the target server and a backup begins, the error "Failed to
connect to Target Service Agent: ffffffc6" will occur and the SMS logic
will be bypassed even though the TSA is loaded.
The TSA that ships with StorageExpress (v3.11b) has fixed many of these
problems. We recommend copying the TSA from StorageExpress to the
target servers running the TSA. See the steps below for accomplishing
this task.
Note: At the server colon prompt, type the console command MODULES
to check the version of NLMs that are currently loaded.
Note: If you are running Central Console v1.40 or greater, the
TSA-311.NLM file name was changed to TSA311.NLM with a 4.00a version.
If the version of the TSA is the new one and this error is still
occuring, check the concurrent connection setting in SYSCON for the user
used in the StorageExpress Association (usually Supervisor). Be sure
this is set to at least 2.
Copying the TSA v3.11b from StorageExpress
Copying the TSA v3.11b from the StorageExpress server disk to the target
servers will eliminate the problems created by the earlier version of
the TSA. To accomplish this task the following steps should be taken:
1. Unload the TSA NLM on the target server.
2. Map a drive (F:) to the SYS:SYSTEM directory on the target server.
3. Create a new directory under SYS:SYSTEM called TSA:
F:\SYSTEM>MD TSA
4. On the target server, flag the TSA.NLM file Normal:
F:\SYSTEM>Flag TSA.NLM N
5. Map a drive to the StorageExpress Unit, logging in as supervisor
and giving the supervisor password.
MAP G:=StorageExpress_Server_Name\SYS:SYSTEM
6. Copy the TSA files from the StorageExpress server to the target
server. There are 2 files that make up the TSA.NLM: TSA-311.NLM
and TSA.NLM. The TSA.NLM is located in the SYS:SYSTEM directory.
The TSA-311.NLM is located in the SYS:SYSTEM\TSA Directory. The
new TSA version looks for the TSA-311.NLM in the SYS:SYSTEM
Directory, but also needs a copy of the file in a SYS:SYSTEM/TSA
directory. The commands to accomplish this are:
COPY G:TSA.NLM F:
COPY G:TSA\TSA-311.NLM F:
COPY G:TSA\TSA-311.NLM F:TSA
Where G: is mapped to StorageExpress_Server_Name\SYS:SYSTEM and
F: is mapped to Target_Server_Name\SYS:SYSTEM
7. Logout of the StorageExpress server:
LOGOUT StorageExpress_Server_Name
8. TSA.NLM and TSA_311.NLM should be dated 04-03-92.
9. Reload the TSA NLM on the Target server and try the backup
again.:"STORAG4.DEF">
STORAGEEXPRESS WILL NOT ACCEPT A TAPE DURING BACKUP OR RESTORE
Symptom:
The StorageExpress system is set to backup or restore files. It will
not accept a tape during the session.
Solution:
* Check the name of the tape. The StorageExpress system will look
either for specific tape names during the backup or restore
operation or a blank tape (Quick erase will blank a tape).
* Check that the tape heads have been cleaned with the cleaning tape
that came with the StorageExpress, according to the recommended
schedule.
* Make sure the tape is not a cleaning tape or an image tape of the
StorageExpress system.
CPU UNIT HANGS AT "DETERMINING LOCAL NETWORK NUMBER...XXX" OR NAME UNIQUENESS
Symptom:
CPU unit is attempting to connect to the Network and the server is not
answering to any of the addresses.
Solution:
* Check that there is a server running on the same ring or segment
and that REPLY GET NEAREST SERVER=ON.
* Check the physical network cable connection to the CPU unit. Be
sure this connection is working.
* Check that the frame type or source routing options match the
network settings.
CPU UNIT HANGS AT "ACTIVITY LOGGER STARTED" AND OTHER SYMPTOMS
Symptom:
The StorageExpress system cannot communicate with the Tape drive in the
peripheral unit. The StorageExpress system attempts to communicate with
the Tape unit(s) during initialization and hangs at the "Activity Logger
Started" screen. Other symptoms include:
* A StorageExpress system with four tape drives in four separate
groups (parallel) will have the SCSI IDs 3 and 4 timeout while
attempting a self-restore. The self-restore may take 20 to 30
minutes and completes successfully even though it appears to have
failed. Possible error messages:
* "Tape driver at SCSI id 3 may not have been initialized".
* "Tape driver at SCSI id 4 may not have been initialized".
* CPU unit LCD indicates drive 1 or 2 error.
* Central Console configuration screen does not allow "parallel"
drive with 2 tape drives.
Description:
These symptoms are caused when the CPU unit is unable to attach to the
peripheral unit. The symptoms during or after a self-restore are caused
by a problem in the way the LDENGINE.NLM is loading the drivers for the
self-restore.
Solution:
Upgrade your StorageExpress system software to v1.30.A.E.
Check the Peripheral Unit I/O Cable.
Verify that the SCSI switches on the back of the peripheral unit are
correctly set for your tape drive type.
Check the internal tape drive cabling in the peripheral unit.
Check the SCSI ID switch. Information on the switch settings is in
document 6763.
CPU UNIT HANGS AT "SELF TEST" AFTER POWER UP
Symptom:
When the StorageExpress unit is powered up, it hangs at the "Self test"
screen.
Description:
Usually the main causes of this symptom include:
* Hardware configuration errors.
* Hardware failures.
* Improperly connected cables.
Solution:
If this installation includes the Token Ring Option, verify the switch
settings and EPROM location on the adapter board. Document 6724
contains Token Ring Option instructions.
Power the system off and re-seat the external and internal SCSI cables
as well as the External SCSI terminator. Power the system back on.
TOKEN RING ADAPTER IN THE STORAGEEXPRESS SYSTEM IS NOT MAKING CONNECTION TO THE NETWORK
Symptom:
The Token Ring Option has been added to the StorageExpress system. It
is not making a connection to the network.
Description:
This symptom may be caused by:
The Token Ring adapter card settings are not correct .
Solution:
Check the switch settings on the Token Ring adapter card and the
position and orientation of the special socketed EPROM.
Switch Settings:
x x x x OFF
x x x x x x x x ON
1 2 3 4 5 6 7 8 9 10 11 12
1 = RPL Enabled
2-6 = RPL EPROM Address
7-8 = Interrupt (IRQ) 2
9-10 = I/O Address A20-A23, A30-A3F
11-12 = DMA Channel 5
Boot ROM
This is located in the center of the card in a 32 position socket. The
Boot ROM is labeled:
306628-001
INTEL
CORPORATION
The notch on the ROM aligns with the notch on the scoket. The socket
has four unfilled positions when the ROM is installed correctly. The
ROM should be installed so the four unfilled positions are located on
the notched side of the socket.
Notch--> ) ) Boot ROM
STORAGEEXPRESS CPU BOX FAILS POST TEST, (BEEP ERRORS ON BOOT)
Symptom:
When the StorageExpress CPU box is powered up, it starts beeping almost
immediately. The series of beeps can be deciphered by referring to the
StorageExpress POST beep codes.
Description:
CMOS has become corrupted, the POST test cannot execute correctly.
Solution:
Clear the CMOS on the StorageExpress CPU box:
1. Facing the front of the system with the cover removed, (the power
supply is to the right of the motherboard), locate jumper block J21
on the motherboard, (far left hand edge, approximately 5 inches
from the front edge). There should be four jacketed jumpers on
this block, jumping 1 & 3, 4 & 6, 10 & 12, 11 & 13.
2. Move the jumper from pins 11 & 13, to pins 9 & 11.
3. Replace the cover and power up the system.
4. Then power down the system and remove the cover.
5. On jumper block 21 move the jumper from pins 9 & 11, to pins 11 &
13.
The CMOS has now been cleared "STORAG8.DEF">
Trademark information