11-21-2012 04:40 AM - edited 03-18-2019 12:10 AM
Good Morning
Just a quick question
We have a C20 here which was working fine until we plugged a suspected faulty camera into it to test it. Unsure if the camera may have caused the fault but the codec was fine before hand. After the camera upgrade the unit would boot and all we had was a flashing green LED on the front.
Initially, on a putty session I could see that there was 2 firmware images on the codec, and image 2 was active. I entered the selectsw image 1 command and the codec booted properly after about 20 minutes, but when I was stood near it I noticed that it rebooted on its own. I managed to serial into it again and logged in as root and using the 'selectsw' command, and then discovered that there is only one software image. (Image 2) Now the codec just keeps rebooting its self, and moments after the boot is complete the image becomes corrupt and the unit reboots again.
It will not stay up long enough for me to attempt a firmware upgrade.
Any ideas?
Also, please could you tell me how to do a software recovery using TFTP?
Many thanks
Luke
11-21-2012 05:20 AM
Hello,
you access the C20 via putty? Do you have admin access? If so, please enable root access too using following command :
sweet-brew-7:/home/dderidde # ssh admin@10.60.142.199
Password:
Welcome to dderidde.ex90.home
TANDBERG Codec Release TC5.1.5.297625
SW Release Date: 2012-11-16
OK
systemtools rootsettings on cisco
OK
Connection to 10.60.142.199 closed by remote host.
Connection to 10.60.142.199 closed.
sweet-brew-7:/home/dderidde #
The login as root before the codec reboots using password cisco :
sweet-brew-7:/home/dderidde # ssh root@10.60.142.199
Password:
[dderidde-ex90-home:~] $
[dderidde-ex90-home:~] $
[dderidde-ex90-home:~] $ touch /tmp/noboot
[dderidde-ex90-home:~] $
Do the command touch /tmp/noboot
If the codec crashes now, it will not reboot.
Now you can look at the logfiles, e.g. cat all the files to your screen to a file.
[dderidde-ex90-home:~] $ cat /var/log/eventlog/* /var/log
Now we should be able to see in these files why we are crashing.
From here, you can also upgrade using tftp. My tftp server is named drop.
[dderidde-ex90-home:~] $ tftp drop
tftp> status
Connected to drop.cisco.com.
Mode: netascii Verbose: off Tracing: off Literal: off
Rexmt-interval: 5 seconds, Max-timeout: 25 seconds>
tftp> bin
tftp> get s52000tc5_1_5_rc2.pkg /upgrade/pkg
Regards,
Danny.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide