×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

ASIC chip failing in Cat3750?

Unanswered Question
Jun 6th, 2012
User Badges:

Hi,


I've just noticed an error I've never seen before in our switch logs.  We have a stack of 6 Cat3750G-48TS-E switches.  The first two in the stack have been up for just over a year and I've only just noticed this error.  Thus far, I haven't noticed any symptoms - I just stumbled upon this error while checking for something else.


As far as I can tell, this has only popped up once and it was 2 days ago.  Unfortunately, thanks to an incorrect firewall rule, our syslogs were not getting to our syslog server so I don't have any historical logs to check against, but it hasn't happened since.


The error I've seen is as follows:-


Jun  5 17:04:03.288: * ManagementInterfaceInitialized exception in port-asic 0 (N16FujitsuSwitch.com.au-2)

Jun  5 17:04:03.288: *********************************************************** (N16FujitsuSwitch.com.au-2)

Jun  5 17:04:03.288: * ManagementInterfaceInitialized exception in port-asic 1 (N16FujitsuSwitch.com.au-2)

Jun  5 17:04:03.288: *********************************************************** (N16FujitsuSwitch.com.au-2)


Jun  5 17:04:03.288: * ManagementInterfaceInitialized exception in port-asic 2 (N16FujitsuSwitch.com.au-2)

Jun  5 17:04:03.288: *********************************************************** (N16FujitsuSwitch.com.au-2)

etc. Up to port-asic 7.  All errors are showing N16FujitsuSwitch.com.au-2 (ie the 2nd switch in the stack).


Otherwise, everything seems to be functioning normally.  In searching for this, the only thing I saw was another user who had this problem (coincidentally only a week ago) who contacted Cisco TAC and was told the ASIC chip was failing.  He had symptoms whereby normal switch traffic seemed to be functioning fine but he was losing IP connectivity to the switch.  The difference here is that he appeared to have a single switch - no stack, and in my stack, switch 1 is the current master.  I am having no connectivity issues to the stack.


I'm obviously thinking that the safe thing to do is to replace this switch in the stack.  Has anyone seen or heard of this issue?


Regards,

Mark Johnson

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Leo Laohoo Wed, 06/06/2012 - 18:42
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 LAN, Wireless

ManagementInterfaceInitialized exception in port-asi

Never seen this before.


I'd get this unit RMA-ed.

HANOH CHA Wed, 03/20/2013 - 16:54
User Badges:

I have a some problem for this log.


what did you do it? did you replace it or not?


if i have a this log, what am i planning to do?



Mar 20 21:53:30.124: %SUPERVISOR-3-FATAL: MIC exception error 20 EDF80760 0 0
-Traceback= 1755A04 1758EB4 16B6578 16B6520 16B8288 16B85A0 16B6628 293660C
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 0
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 1
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 2
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 3
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 4
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 5
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 6
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 7
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 8
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 9
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 10
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 11
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: ***********************************************************
Mar 20 21:53:30.124: * ManagementInterfaceInitialized exception in port-asic 12
Mar 20 21:53:30.124: ***********************************************************


thank you.

paolo bevilacqua Thu, 03/21/2013 - 02:02
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

As indicated above.


Contact Cisco for replacement.

HANOH CHA Thu, 03/21/2013 - 02:34
User Badges:

Thank you for anwsering.

Let me know what is problem?

Sent from Cisco Technical Support iPhone App

paolo bevilacqua Thu, 03/21/2013 - 09:48
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Problem: Hardware failure.

Solution: Read above.

Actions

This Discussion

Related Content