Top task "tipFdbAgeT" is high on Summit-200 switch
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-24-2016 05:38 PM
summit-200 switch has recently experienced a cpu spike causing latency through this switch. When running top I noticed the task "tipFdbAgeT" is running high which I haven't seen this task before.
could someone please explain what this task represents? I have tried searching online with no avail.
thanks,
Joey
could someone please explain what this task represents? I have tried searching online with no avail.
thanks,
Joey
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-24-2016 07:01 PM
Thank you for the responses, after further troubleshooting it was a FDB issue where a directly connected device was upgraded which corrupted the IP FDB table.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-24-2016 07:01 PM
Glad you got it sorted Joey.
Thanks for joining the Hub!
Thanks for joining the Hub!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-24-2016 06:03 PM
Hi Joey,
The task "tipFdbAgeT' refers to IP FDB Aging Timer on Extremeware switches. You can clear the FDB table on Summit-200 to see if the CPU spike clears out which is probably due to software/hardware mismatch.
For these End of Life products, there are not many troubleshooting tools available. So if clearing table does not help, rebooting the switch will be next step which can re-initialize all the processes and might help.
Thanks,
Ijaz
The task "tipFdbAgeT' refers to IP FDB Aging Timer on Extremeware switches. You can clear the FDB table on Summit-200 to see if the CPU spike clears out which is probably due to software/hardware mismatch.
For these End of Life products, there are not many troubleshooting tools available. So if clearing table does not help, rebooting the switch will be next step which can re-initialize all the processes and might help.
Thanks,
Ijaz
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-24-2016 06:01 PM
Hi Joey,
I guess that this task is related to iparp table aging process.
I would try clearing the fdb and iparp table and check if the process utilization normalizes.
I guess that this task is related to iparp table aging process.
I would try clearing the fdb and iparp table and check if the process utilization normalizes.
