Solved: What is this error mean? %PLATFORM_IPC-3-COMMON: Unknown IPC message type - Page 2

Rudy R. · ‎12-02-2011

Errors started popping up on the console (making it difficult to even use console as they come in pretty frequently). I have never seen them before. I have no IPC configurations on this switch.

Info on IOS:

Cisco IOS Software, C3560E Software (C3560E-IPBASEK9-M), Version 15.0(1)SE, RELEASE SOFTWARE (fc1)

BOOTLDR: C3560E Boot Loader (C3560X-HBOOT-M) Version 12.2(53r)SE1, RELEASE SOFTWARE (fc1)

License Level: ipbase

cisco WS-C3560X-24 (PowerPC405) processor (revision A0) with 262144K bytes of memory.

Here are the errors:

Dec 2 16:27:52.793: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 1B2E650z 227DF8Cz 2289730z 220E69Cz 22179C8z 286A948z

Dec 2 16:27:56.559: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 1B23D08z 28653A0z 2862940z

Dec 2 16:27:59.042: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 2865750z 2865410z 2862940z

Dec 2 16:28:02.791: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 2864B14z 286492Cz 2866054z 2862940z

Dec 2 16:28:04.209: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 1B232F4z

Dec 2 16:28:08.084: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 2865300z 2864B80z 2862940z

Dec 2 16:28:11.053: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 1ACA310z

Dec 2 16:28:14.845: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 2862BA4z

Dec 2 16:28:18.401: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 1ACD2E0z 1ACD2D0z 28653A0z 2862940z

Dec 2 16:28:21.060: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 2708DE0z 22D6E24z 23D3D88z 1DF4250z 239BB18z 239BBE8z

Dec 2 16:28:25.347: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 1ACD320z 28653A0z 2862940z

Dec 2 16:28:28.761: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 286492Cz 286492Cz 286540Cz 2862940z

Dec 2 16:28:31.059: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 285EF44z

Dec 2 16:28:37.484: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 2865320z 2864B80z 2862940z

Dec 2 16:28:38.759: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 1B23328z

Dec 2 16:28:49.940: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 22DE160z 2398D20z 22D6E24z 23D3D7Cz 1DE1F30z 1DF21A4z

Dec 2 16:28:57.355: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 285EE1Cz

Dec 2 16:29:03.588: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 28652E0z 2864B80z 2862940z

Dec 2 16:29:08.033: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 58674 size 126

-Traceback= 5370E8z 21EF97Cz 23E20C0z 23E5A38z 23E5E1Cz 22D7E3Cz 22D7DE4z 22DDA0Cz 22DDF14z 22D7EECz 1B9F374z 286492Cz 107D0A8z 107F09Cz 107F834z 1919524z

Thanks for any pointers on how to debug this.

Rudy

Leo Laohoo · ‎01-28-2012

Also, the 12.x -> 15.0 upgrade was 30 minutes

Depends where you "came" from. Let me explain: If, for example, you have IOS version 12.2(46) and earlier and you upgrade to 12.2(58)SE or 15.0(1)SE then it'll take approximately 45 heart-stopping minutes because these new codes, 12.2(58)SE and /or 15.0(1)SE, will upgrade the microcode/bootstrap of your switch.

gene.uhl · ‎01-29-2012

I agree that would be horrific on a hot stack. I was offline creating this stack so I was ok but that is great info to know. If I knew this was going to happen I would have liked to see if it happened with the latest 12.x code instead of 15.x. Not sure if the 12.x code would work on the 3750x and recognize the 10g adapters with the twinax cables. Oh and that's another issue I'm fighting with Cisco. I have m cards in the nexus that will only recognize the active twinax cables but the must be version 2 not version 1 which I probably have but who has the different part numbers between the two as all I see is one part number. Even the comp matrix tells you that v2 is needed but the pn is the same as v1. Boy do I love Cisco

Sent from Cisco Technical Support iPhone App

Leo Laohoo · ‎01-29-2012

Not sure if the 12.x code would work on the 3750x and recognize the 10g adapters with the twinax cables.

If you are upgrading from 12.2(46)SE to either 12.2(58)SE or 15.0(1)SE microcodes are part of this package, however, this is a one-off affair. Once the microcode is upgraded it won't take that long after the next reboot.

I have m cards in the nexus that will only recognize the active twinax cables but the must be version 2 not version 1 which I probably have but who has the different part numbers between the two as all I see is one part number.

Try if you can RMA the cable. When you do, tell the TAC you want the v2.

Rudy R. · ‎01-30-2012

If you are upgrading from 12.2(46)SE to either 12.2(58)SE or 15.0(1)SE  microcodes are part of this package, however, this is a one-off affair.   Once the microcode is upgraded it won't take that long after the next  reboot.

There is a bug in the software... could be in the microcode. How are admins to know if the SE2 repairs a microcode bug causing the system to halt for 45 minutes? The upgrade procedure could give and ETA until the system will be back up and force the user to type 'Y' before the upgrade.

It may be a 'feature' to have the errors spitting out, but definately a bug to not have a knob to disable IPC messages.

ha! K.N.O.B. was censored.

Leo Laohoo · ‎01-27-2012

Version 15.0(1)SE

DO NOT, under any circumstances, use IOS versions 15.0(1)SE and 15.0(1)SE1. There are some critical CPU bugs. Try out the latest, 15.0(1)SE2 instead.

gene.uhl · ‎01-28-2012

Sorry to spoil the party but I am getting these errors and this is my config in the stack:

Switch Ports Model SW Version SW Image

------ ----- ----- ---------- ----------

* 1 30 WS-C3750X-24P 15.0(1)SE2 C3750E-UNIVERSALK9-M

2 28 WS-C3750G-24PS 15.0(1)SE2 C3750-IPSERVICESK9-M

3 28 WS-C3750G-24PS 15.0(1)SE2 C3750-IPSERVICESK9-M

4 30 WS-C3750X-24P 15.0(1)SE2 C3750E-UNIVERSALK9-M

So unfortunatley the answer is 15.0(1)SE2 didn't fix jack for me. I went from 12.x to this ver as the 3750's were pulled from standalone and the x's are brand new. I created this parallel stack to feed L3 10G to Nexus then I set up a L2 Etherchannel from this new stack to the old 3750 server stack which is L3 etherchannel to the old 6509 core. This wasy I can swing servers over when I feel like it. I use echannel and port channel in the same context here. The L2 was fine, as it should be. The L3 is what is giving me the issues. I asked to escalate yesterday AM and have not hear from them....I am going to press as this is BS It is not rocket science here and these are basic configurations, not like VPC's etc..

Gene

rtrees · ‎02-01-2012

This looks like this issue is reported as answered, what was the solution because I am seeing the same thing and am running 15.0(1)SE2 also.

Ron Arroyo · ‎02-01-2012

I dont know about the rest but I do not have an answer. Cisco TAC is still decoding my tracebacks. I was advised SE2 was not going to fix my errors and that the developers still need to evaluate my decodes. No answer on my side.

gene.uhl · ‎02-01-2012

Well this is the latest I have from TAC. They are saying my issue is different from the threads posted here, but I think not:

Here is what I have and waiting for a workaround:

BUG CSCtt42626 Unknown IPC messages seen on the console of a 3750x stack

Release-note:

Symptom:

Unknown IPC messages seen on the console of a 3750X stack

Conditions:

Currently seen on 3750X switches in a stack

Workaround:

None

Found in: 15.0(1)SE

To be fixed in: 15.0(2)SE

Take if for what it is worth......

Gene

rtrees · ‎02-01-2012

It's annoying to see this in the logs but is it actually affecting anything for you guys? I'm trying to track a network slowness issue and found these messages and I'm wondering if it is related or not.

gene.uhl · ‎02-01-2012

Didnt bother checking just yet, I disconnected as this is a parrallel stack that has a L2 portchannel to the main stack I am migrating from.

I can tell you that I do have a 3750X stack connected to my M card in the Nexus via 10G using the latest 12.x firmware and have zero issues for weeks. Also to a 3750X-48 non-stack with no issues either.

If they can't fix this, I am thinking of downgrading the stack to 12.2(55)SE3 (the latest the 3750G-12S can go to that is also in the the working 3750X stack that is working..

Gene

Ron Arroyo · ‎02-01-2012

I had issues before upgrading to SE1 of switches crashing in the stack but now on SE1 all seems stable and no impact other than the tracebacks logging. TAC advised SE2 would not resolve my issues so I am waiting. I really do not want to downgrade to 12.2. So far no impact on SE1 other than the annoying tracebacks. No slowness either. hope it helps.

Franziska Corradi · ‎04-21-2012

Hello, did anyone ever get a Reply from TAC to this? I updated a 3570X Stack Yesterday from 12.2.58SE2 to

Switch Ports Model SW Version SW Image

------ ----- ----- ---------- ----------

* 1 54 WS-C3750X-48 15.0(1)SE2 C3750E-UNIVERSALK9-M

2 54 WS-C3750X-48 15.0(1)SE2 C3750E-UNIVERSALK9-M

3 30 WS-C3750X-24 15.0(1)SE2 C3750E-UNIVERSALK9-M

Solved my Stack Power Problem, but now i have this message filling my Log

%PLATFORM_IPC-3-COMMON: Unknown IPC message type 2545 size 154

-Traceback= 545B9Cz 21DD084z 23CCA04z 23D037Cz 23D0760z 22C77A4z 22C774Cz 22CD380z 22CD888z 22C7854z 2130560z

and 32% CPU Load...

The C3KX-NM-10G runs as Uplink Module only, i cannot install the additional Software as i only have

Hardware Board Revision Number : 0x02

gene.uhl · ‎04-21-2012

Well TAC informed me that they will fix this bug in the next release circa July so the workaround is to downgrade to the latest 12.x code. I did this and the error went away. 6 weeks of working with them applying their debug code etc etc and this is what I got for all my troubles.

Gene

Sent from Cisco Technical Support iPhone App

Franziska Corradi · ‎04-21-2012

well i upgraded from 12.x to 15.x due to a Power Stack Issue...so thats not really an option for me.

what hardware version do you have? could it be a Problem with that?