cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
706
Views
0
Helpful
5
Replies

C90 fails to boot after SW upgrade

kfekete
Cisco Employee
Cisco Employee

Hello

Today I tried to update the TC software on a C90 codec. Previously it had TC 5.1.2, but now it has TC 6.3.0.

It has an U-boot version "U-Boot 2010.06-115 (Sep 26 2013 - 08:36:59) MPC83XX".

I used the usual "run pkgex" method to install the system to the flash (using console port), and it was successfull.

Unfortunately, after the boot complete, it stucks in "maintenance mode", and I could not use itself in fully functional mode.

I issued a factory reset, but it did not solve the mentoned problem.

Can you please advice what should I try next to eliminate the mentioned?

Thanks

Krisztián

5 Replies 5

amehla
Cisco Employee
Cisco Employee

Hi Krisztian,

was  factory reset successful ? did it erased IP information from unit ?

if it is still accessible over IP, then access it through putty and login as admin

then use the command selectsw and select non active image to revert back to TC 5.1.2 and check if it recovers.

Hi Amit,

There is no configuration remained in the unit. Using the serial connection to the board, we can see the following messages:

***

tipc: Resetting link <1.1.1:eth1-1.1.10:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.10:eth0> on network plane A
tipc: Lost contact with <1.1.10>
tipc: Resetting link <1.1.1:eth1-1.1.15:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.15:eth0> on network plane A
tipc: Lost contact with <1.1.15>
tipc: Resetting link <1.1.1:eth1-1.1.16:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.16:eth0> on network plane A
tipc: Lost contact with <1.1.16>
tipc: Resetting link <1.1.1:eth1-1.1.11:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.11:eth0> on network plane A
tipc: Lost contact with <1.1.11>
tipc: Resetting link <1.1.1:eth1-1.1.18:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.18:eth0> on network plane A
tipc: Lost contact with <1.1.18>
tipc: Resetting link <1.1.1:eth1-1.1.12:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.12:eth0> on network plane A
tipc: Lost contact with <1.1.12>
tipc: Resetting link <1.1.1:eth1-1.1.17:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.17:eth0> on network plane A
tipc: Lost contact with <1.1.17>
tipc: Resetting link <1.1.1:eth1-1.1.19:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.19:eth0> on network plane A
tipc: Lost contact with <1.1.19>
tipc: Resetting link <1.1.1:eth1-1.1.13:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.13:eth0> on network plane A
tipc: Lost contact with <1.1.13>
tipc: Resetting link <1.1.1:eth1-1.1.14:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.14:eth0> on network plane A
tipc: Lost contact with <1.1.14>
tipc: Established link <1.1.1:eth1-1.1.12:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.14:eth0> on network plane A
tipc: Resetting link <1.1.1:eth1-1.1.12:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.12:eth0> on network plane A
tipc: Lost contact with <1.1.12>
tipc: Resetting link <1.1.1:eth1-1.1.14:eth0>, peer not responding
tipc: Lost link <1.1.1:eth1-1.1.14:eth0> on network plane A
tipc: Lost contact with <1.1.14>

tipc: Established link <1.1.1:eth1-1.1.16:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.11:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.18:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.10:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.12:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.15:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.19:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.17:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.14:eth0> on network plane A
tipc: Established link <1.1.1:eth1-1.1.13:eth0> on network plane A
***

I assume this is some internal communication.

For sure I can revert back to TC 5.1.2 without any problem. Today I'm going to try out the TC 7, maybe there is a fixation in that revision.

Thanks in advance, and best regards!

Krisztián

Hi Krisztian,

i will recommeded to go in steps like from TC 5.1.2 to TC 5.1.8 and then to TC 6 version

if everything works fine then you can go to TC 7 version.

Hi Amit,

Today I flashed back the TC5.1.2, and unfortunately it acts like the same with the higher versions (TC 6.3.0).

At this point, I don't really know how should I solve this issue, can you please advice?

By the way, in the near past I upgraded an EX90 from TC5.1.2 to TC6.3.0 and it was good, there was not any issue,

why is that so different with the C90?

Thanks in advance, and best regards!

Krisztián

Hi Krisztian,

yes, you can move direclty from TC 5.1.2 to TC 6.3 but since in this case your device is falling in maintenance mode evertime you go from TC 5.1.2 to TC 6.3, try in above steps process and let us know the outcome.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: