Mani CPU winchester replacement
Posted: 20 Jan 2011 09:51
Hello,
There is an ACT system with duplicated CPU7.
There are 700 IP Touch set registered on site.
Now we had to replace the main CPU's winchester in case of disk errors.
We prepared the new winchester with the appropriate sw release, then we loaded CHO file and mao into it as well.
We used the 'mastercopy twincpu' comman on site to be synchronized the customer database and other parts of datas with CPU_b (StBy).
After restarted the CPU_a (as main) with the new winchester we recognized with 'ippstat' command there are a lot of IP touch phones
restarted and restarted again (we checked continuously number of working IP sets). As it seems some IP sets tried to download new binary (against the proper linux version
installation on both CPU).
Then we gave a 'bascul' command to became the former StBy CPU_b the main CPU.
In this situation (CPU_a is the StBy one) all the IP Touch Phones are working properly!
What could be the reason of this strange situation?
Best regards
There is an ACT system with duplicated CPU7.
There are 700 IP Touch set registered on site.
Now we had to replace the main CPU's winchester in case of disk errors.
We prepared the new winchester with the appropriate sw release, then we loaded CHO file and mao into it as well.
We used the 'mastercopy twincpu' comman on site to be synchronized the customer database and other parts of datas with CPU_b (StBy).
After restarted the CPU_a (as main) with the new winchester we recognized with 'ippstat' command there are a lot of IP touch phones
restarted and restarted again (we checked continuously number of working IP sets). As it seems some IP sets tried to download new binary (against the proper linux version
installation on both CPU).
Then we gave a 'bascul' command to became the former StBy CPU_b the main CPU.
In this situation (CPU_a is the StBy one) all the IP Touch Phones are working properly!
What could be the reason of this strange situation?
Best regards