Page 1 of 1
MASTERCOPY failed
Posted: 13 Jul 2006 14:27
by doddykartiwa
Please... HELP...
We just upgraded a system from R4.1.1 to R6.2.
Everything works fine in the upgrading process, but then when we tried to do a MASTERCOPY using swinst, the operation always timed out when copying accounting files.
Can anybody help? Thanks
Posted: 13 Jul 2006 22:40
by frank
While you do the mastercopy, use another session to telnet into the main cpu, and check the incvisu live. Also, reboot both cpus before the master copy
MASTERCOPY failed
Posted: 14 Jul 2006 10:07
by sadim
1. check the account files. If there are to many, try to delete the out of date using accereset
2. what kind of link are you using for the mastercopy (C1, eth)
3. if eth is there any incident of cpu ethernet disable ?
4. if you are using eth are the straps of the cpu on the good position
Posted: 18 Jul 2006 04:43
by doddykartiwa
1. there is a lot of accounting files in the database. we'll try to delete the out of date
2. there is no option on the link used. But the RUNTEL of the slave CPU was not started, so I assume it is ethernet that was used.
3. there is no cpu ethernet disable. when the message timeout appeared, i try to see if there is any incidents in the main CPU, but there wasn't any
3. which straps should we look at? the only difference is the boot strap in the middle of the CPU. the main does not have the strap, while the slave has that strap
MASTERCOPY failed
Posted: 18 Jul 2006 05:10
by sadim
Concerning the straps, only the CPU5_2, CPU5_S3 or CPU6 are concerned, and the strap is for instance in case of CPU5_3 the XB01 (Embedded Ethernet). Please take a look to TC0403
Posted: 18 Jul 2006 09:10
by wizzy
Are the hard drives in good condition ????
I had this problem when one of the hard drives ha reading failure..
Try to log on from console