%XDR-3-XDROOS: Received an out of sequence IPC message

joan.luque · ‎03-10-2014

Hi all

From some days ago we experimenting some management problems on C2960X stack. I see these strange messages on log:

Mar 10 12:30:31.808 UTC: %XDR-3-XDROOS: Received an out of sequence IPC message. Expected 0 but got 4 from slot 2. -Traceback= 42D90Cz 1C51C04z 7F858z D0A098z D0B6C0z D0EE00z D0FB48z D10350z D10AC8z 2122C40z 2069DB4z 206C468z 20521D4z 2049924z 20498CCz 20523B8z Mar 10 12:30:31.812 UTC: %XDR-3-XDROOS: Received an out of sequence IPC message. Expected 0 but got 4 from slot 2. -Traceback= 42D90Cz 1C51C04z 7F858z D0A098z D0B6C0z D0EE00z D0FB48z D10350z D10AC8z 2122C40z 2069DB4z 206C468z 20521D4z 2049924z 20498CCz 20523B8z Mar 10 12:30:31.815 UTC: %XDR-3-XDROOS: Received an out of sequence IPC message. Expected 0 but got 4 from slot 2. -Traceback= 42D90Cz 1C51C04z 7F858z D0A098z D0B6C0z D0EE00z D0FB48z D10350z D10AC8z 2122C40z 2069DB4z 206C468z 20521D4z 2049924z 20498CCz 20523B8z Mar 10 12:30:31.819 UTC: %XDR-3-XDROOS: Received an out of sequence IPC message. Expected 0 but got 4 from slot 2. -Traceback= 42D90Cz 1C51C04z 7F858z D0A098z D0B6C0z D0EE00z D0FB48z D10350z D10AC8z 2122C40z 2069DB4z 206C468z 20521D4z 2049924z 20498CCz 20523B8z Mar 10 12:30:31.822 UTC: %XDR-3-XDROOS: Received an out of sequence IPC message. Expected 0 but got 4 from slot 2. -Traceback= 42D90Cz 1C51C04z 7F858z D0A098z D0B6C0z D0EE00z D0FB48z D10350z D10AC8z 2122C40z 2069DB4z 206C468z 20521D4z

All the switches are the same model and have the same IOS release:

Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 52 WS-C2960X-48TD-L 15.0(2)EX1 C2960X-UNIVERSALK9-M
2 52 WS-C2960X-48TD-L 15.0(2)EX C2960X-UNIVERSALK9-M
3 52 WS-C2960X-48TD-L 15.0(2)EX1 C2960X-UNIVERSALK9-M
4 52 WS-C2960X-48TD-L 15.0(2)EX C2960X-UNIVERSALK9-M

I found a bug that could explain this but indicated IOS versions do not match ours CSCek28110

Has anyone encountered this problem before? We have multiple switches with the same configuration but this problem only happens in one of them.

Any suggestion or workarround to solve this?

Regards,

Jose Solano · ‎03-10-2014

Hi,

There are a few bugs out there that may be the cause of the problem as well as issues like stackports flapping, however I would say that the best option will be to open a TAC case in order to decode those traceback messages and get the proper interpretation of the same.

Hope this helps.

joan.luque · ‎03-11-2014

Hi,

After upgrade the switch stack from 15.0(2)EX1 to 15.0(2)EX2 the issue seems to have resolved.

Regards,