•Soon
after giving synchronization command from active IOP, synchronization
getting aborted
Verify the HDL cable (IOP to IOP) or AP to IOP HDL cable connected
properly and check the cable connectivity.
•Synchronization getting failure
at the time of step 1
Proper shut down and boot not carried out
•Sync abort in step 3
Most unpopular step where in sync should not fail.
In this step ‘ED’ (exchange data) files are transferred.
Verify in which file the the Sync aborted by going through the sync_log
file.Contact the C-DOT control room.
Mostly copying of ED and part-init to system to be given for solving
this problem.
•Sync abort in step 4
• If cre-space file utility is run properly this step will not
fail.
• *.log & res* & heal* file are to be deleted.
• find /u -name *.log -print
• rm abc*.log
• rm res* file in $TEMP directory
• rm heal* in $FDTDIR directory
•Sync Abort in step 5
• Traffic and billing data files are transferred.
• This is the most popular step in which sync fails due to huge
volume of traffic & bc files.
• Traffic file and ‘bc’ file are to be deleted regularly.
• Then repeat the sync process.
•IOPs were in hanging status
By mistake init-iop 5:1; command might be executed from both the IOP
or controller card may be giving problem. If not reset and boot and
then sync.
•IOP goes OOS-SYS when ED/BD/BC backup is taken
Cartridge or cartridge drive may be faulty
•Both the IOPs are working alright when it is in simplex mode.During
synchronization get aborted.
Delete BC, BD, TF, IOH files and try again for synchronization.