06-29-2011 10:01 PM - edited 03-17-2019 10:21 PM
Hi,
Tandberg MCU 4200 4.1(1.59) reboots every 3-5 minutes.
120357.916 SYSTEM : Warning : Product activation key required
EXIT 255
Jun 29 12:04:06 reboot: rebooted by root
syncing disks... done
rebooting
*** (C) Codian Ltd 2004-2005 ***
Resetting PCI
Calling Mpc107init
Mpc107init done
Testing SDRAM data lines ... ok
Testing SDRAM address lines ... ok
Relocating .text from FFF00000-FFF0B36E to 0E010000
Relocating .data from FFF0B380 to 0E01B380-0E01B7C8
Clearing .bss from 0E01B7C8-0E09EDA4
Initialising timebase regs
Calling main
L1 strap : built at Jul 7 2005 - 23:19:46
L2 found : image size 000362e4 version 2005:07:08 11:19
Starting L2
L2 Bootstrap
Relocating .text from FFF10000-FFF450B0 to 0E010000
Relocating .data from FFF450C0 to 0E0450C0-0E0462E4
Clearing .bss from 0E0462E4-0E0CA930
Calling main
Hello from l2_main
card detected in internal slot (EXCA_STATUS = 4c)
waiting until status ready ...ok!
mounting dos0
fatsize = 00010000
card detected in external slot (EXCA_STATUS = 6f)
waiting until status ready ...ok!
mounting dos1
fatsize = 0001f200
Product - MCU 4210
MAC address - XX:XX:XX:XX:XX:XX
Serial number - XXXXXXX
Motherboard serial number - яяяяяяяя
Slotmask : 00000028
03 - яяяяяяяяяяяяяяяя
05 - яяяяяяяяяяяяяяяя
Devmode : 00000000
Trying dos1:kupgrade
error opening source file dos1:kupgrade
Trying dos0:kupgrade
error opening source file dos0:kupgrade
Trying dos0:netbsd
copying dos0:netbsd to md0:00000000...................................... ......002bf13a bytes copied
Image version : 4.1(1.59)
fsck: Cannot open `/etc/fstab': No such file or directory
fsck: Cannot open `/etc/fstab': No such file or directory
** /dev/rwd0b
** Phase 1 - Read and Compare FATs
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
7 files, 60954 free (30477 clusters)
fsck: Cannot open `/etc/fstab': No such file or directory
fsck: Cannot open `/etc/fstab': No such file or directory
** /dev/rwd0d
** File system is clean; not checking
atactl: wd2: Device not configured
Can't read atactrl wd2 identify: Undefined error: 0
Hit Ctrl+C in the next 5 seconds to prevent mcu start
RUNNING MCU
/dev/rmd0c: 1.0MB (2048 sectors) block size 4096, fragment size 512
using 4 cylinder groups of 0.25MB, 64 blks, 96 inodes.
super-block backups (for fsck -b #) at:
32, 544, 1056, 1568,
cfev: driver loaded successfully - built at Dec 7 2004 12:46:29
Module loaded as ID 0
net.inet.ip.ifq.maxlen: 50 -> 500
net.inet.udp.checksum: 1 -> 0
ftrace_init done
user mbuf init
sendbatch_init
120518.342 SYSTEM : Info : Codian MCU 4210 4.1(1.59) (Build 6.16(1.59)) starting
120518.526 SYSTEM : Info : device configuration successfully loaded
120520.128 NETWORK : Info : SSL successfully initialised
DSP 00 state :
memory address zero onwards:
00000122 004002ea 00000362 dead0009 020003a2 c0fe0011 00000000 00000000
hsi_addr is 00000c30; this address onwards:
00000001 00000000 00000000 00000000 8000dd80 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
DSP 01 state :
memory address zero onwards:
00000180 004002ea 00000362 dead0009 020003a2 c0fe0011 00000000 00000000
hsi_addr is 00000c30; this address onwards:
00000001 00000001 00000001 00000000 8000dd80 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
DSP 02 state :
memory address zero onwards:
0029702a 004002ea 00000362 0000a35a 020003a2 00000000 00000000 00000000
hsi_addr is 00000c30; this address onwards:
00000001 00000002 00000002 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
DSP 03 IS DEAD!!! exit_msg_addr=40a2058b
exit msg :
*******
*******
*******
*******
DSP 03 state :
memory address zero onwards:
10488000 400240a1 2820008c 04a002a2 15980003 d1a0250a 0ec0a387 95288100
hsi_addr is 00000c30; this address onwards:
00088a0d 41821212 c000390a 1444002f 40a2058b 00043c8a 03688044 21026013
084a988a 20180468 0a310a40 40950aa0 178302c9 88796c42 c00400b0 9c1e0008
DSP 04 IS DEAD!!! exit_msg_addr=42c10160
exit msg :
*******
*******
*******
*******
DSP 04 state :
memory address zero onwards:
8c9a3082 818cc008 02110d42 18598401 0013910e 08081008 848101bc 115c9033
hsi_addr is 00000c30; this address onwards:
8b301a40 0485c603 49100343 01000002 42c10160 009531cc 41959102 008a0451
0b201a0c e0000010 0142c111 b3006101 aa20b013 200a7251 40220cc5 86dcb5a8
120824.644 SYSTEM : Warning : Product activation key required
PuTTYPuTTYEXIT 255
Jun 29 12:08:37 reboot: rebooted by root
syncing disks... done
rebooting
Full log is in the attached file.
Any ideas what can be done?
01-31-2012 02:14 AM
Hello osumbekov
Please try factory default
02-01-2012 05:26 AM
You can probably try the kupgrade process in reloading the SW via the flash card if you can:
Otherwise, I'd open a Support Case to see if there is anything else that can be done to revive your MCU.
02-21-2012 01:24 AM
Hi all,
I have the same problem. I managed to reset the unit to factory default. I also installed the latest version firmware with the aid of the above article. But the problem is still remain.
Please help.
02-21-2012 03:18 AM
HI Paym - Would suggest you open a TAC case for this issue as soon as possible. When opening your SR, can you hook the console port to a PC and log the session output to a text file for us to review? If you can, unplug the MCU and let it boot up. If its constantly rebooting on start, let it go through its cycle 2 to 3 times for us to see where its failing. Is this doable?
VR
Patrick
02-21-2012 04:11 AM
Hi Patrick,
I unplugged the network cable, and turned it on. It restarted 2 times, and then it is working. The Alarm LED turned green.
I plugged the network cable, and restarted the MCU, and it is working.
I captured the console port messages in the attached file. In the restarting phase it boots normally, but it starts to dump its memory to console port, and finally it restart.
02-21-2012 05:36 AM
Hi Payam - Your MCU could still have some various issues associated. I think its in your best interest, if you have maintanance on this device, to have it RMA'ed when you can.
02-21-2012 07:04 AM
Hi Patrick,
Do you think it is a hardware problem? Did you find anything from the console messages?
02-21-2012 07:33 AM
HI Payam. In your case, yes, I would suggest an RMA for your 4200 MCU based on what I'm seeing and confirmed by a colleague of mine as well. If any questions arise, you can refer them to me, and they should know how to find me.
VR
Patrick
04-13-2012 07:26 AM
Hi Payam
I am having the same problem with my MCU did you find a solution in the end or was it a RMA
Regards
Ash
04-13-2012 10:26 PM
Hi Ash,
I returned the unit to Cisco for RMA, and they changed the unit.
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