• 0
  • 1
  • Problem
  • Updated 3 years ago
  • Solved
Getting  SOFTWARE FAILURE HAS BEEN DETECTED IN THE SYSTEM error while login into the Alpine Switch
Photo of surender lakra

surender lakra

  • 110 Points 100 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of Raymond van Dijk

Raymond van Dijk, Employee

  • 470 Points 250 badge 2x thumb
Hi Surender,

This message is seen when there is a software task crash on the system.

you can check which task,by using the TOP command and look for a task that is in suspended mode.

The only way to recover from a task crash is to reboot the system.


Raymond van Dijk
Photo of surender lakra

surender lakra

  • 110 Points 100 badge 2x thumb
Its showing only one task tFdbSyncTa as suspended. However, when check below link, it says Under normal operation, only two tasks have status of “SUSPEND”, tShell and tFdbSyncTask.

Total number of tasks: 86
Task Name       Task Id         Task PC         Status   % CPU Max % util
   tBGTask      873ef730        80d3c008        READY        98   98
  tExcTask      821368c0        80d4d37c        PEND          0    0
  tLogTask      82121cb0        80d4d37c        PEND          0    0
tSlowTimer      82186980        80d4d37c        PEND          0    1
tFastTimer      821b8c40        80d4d37c        PEND          0    0
  tTimeout      821bcf00        80d4d37c        PEND          0    0
tEMSOutput      8213e980        80d4d37c        PEND          0    0
tEMSFilter      82143980        80d4d37c        PEND+T        0    1
  tlogpoll      82147090        80d3c1d4        DELAY         0    0
tledPollTa      8214e920        80d4d37c        PEND          0    0
tFdbAgeTas      8386b780        80d4d37c        PEND          0    0
tFdbMacLoc      8386fa40        80d4d37c        PEND          0    0
tipFdbAgeT      83873d00        80d4d37c        PEND          0    0
tipsubFdbA      83877fc0        80d4d37c        PEND          0    0
tFdbSyncTa      8387d0a0        80d3ba10        SUSPEND       0    0
tFdbScanTa      822dc9d0        80d4d37c        PEND          0    0
tTrxdiagTa      822e09d0        80d4d37c        PEND          0    0
tAsyncSave      83896060        80d4d37c        PEND          0    0
 tpifstate      84a3d550        80d4d37c        PEND          0    0
  tbgpTask      857d4840        80d00d34        PEND+T        0    0
Press 'h' for help
Photo of Drew C.

Drew C., Community Manager

  • 39,442 Points 20k badge 2x thumb
Hi Surender,
In addition to Raymond's recommendations, you may also find the crash information in the log.

If a reboot doesn't help, you may want to attempt to clear the error from the system using these commands:
clear log diag-status
clear log static
clear log messages memory-buffer
clear log messages nvram

This will clear ALL log messages in the system.  If the problem persists after another reboot, I would suggest running diagnostics to determine if you're experiencing a hardware failure.

Also of note, this hardware is nearing End-of-Life and will no longer be supported by GTAC nor stocked in the RMA depots.  Some specific cards have already gone EOL, with the remainder ending on 6/30.
The full list can be found here:
Photo of surender lakra

surender lakra

  • 110 Points 100 badge 2x thumb
Thanks Drew for information..

Is there any possibility to check what wrong with switch software or hardware without reboot. Because in case will reboot the switch then unable to find RCA for the problem.

Photo of Drew C.

Drew C., Community Manager

  • 39,376 Points 20k badge 2x thumb
If a process has failed, you'll have to reboot the switch to recover it.  Is there any impact to your users?
Before rebooting, you may want to collect a show tech from the switch so that you'll have the information to analyze.
Photo of EtherMan


  • 606 Points 500 badge 2x thumb
We have had lots of hands on with Extreme since the beginning in 1998 ... all product lines... Here is what I would do if I had this one still in service.  If it is a 3808 with stand alone MSM then you can run diagnostics extended on individual slots and your impact may not be as great as a complete reboot.  If it is not and one of the smaller Alpines the msm is built into chassis and if it fails diagnostics then you will be dead with no way to get it back. 

I would make sure you have a current configuration in hand via downloading it to the tftp server or doing a show config and capturing the complete configuration in your telnet session.

A reboot could fix this or it could also cause the switch to not come back depending on problem.

Odds are you have a failing switch and it needs to be replaced but I would not do anything till you get it's replacement ready and standing by. 

The show tech Drew mentioned will show a lot more than the configuration but it does display the configuration...  It all depends on how responsive this unit is now.  I would guess you may have some services being impacted and just not know it yet.

Good luck... 
Photo of surender lakra

surender lakra

  • 110 Points 100 badge 2x thumb
Thanks Robert for sharing information..