Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'show ip ospf neighbors detail' really slow on switch with many ospf neigbors #747

Closed
frdaigle opened this issue Apr 5, 2023 · 5 comments · May be fixed by #780
Closed

'show ip ospf neighbors detail' really slow on switch with many ospf neigbors #747

frdaigle opened this issue Apr 5, 2023 · 5 comments · May be fixed by #780
Assignees

Comments

@frdaigle
Copy link

frdaigle commented Apr 5, 2023

Parsing the command will last about 14 minutes on a switch with about 230 ospf neigbors.

I had a look parser's code and a 'show run | section router ospf {instance}' is run for each neighbor to gather vrf data. I would be more efficient to run a 'show run | section router ospf' once and refer to the returned dictionary for all neighbors.

@sumitsehgal123
Copy link

sumitsehgal123 commented Apr 17, 2023

Thanks for reaching out piestack support team, I will be looking at your ticket and reviewing it .

@sumitsehgal123
Copy link

Hi frdaigle,
Please can you share the cli sample output for the "show run | section router ospf {instance}".

@sumitsehgal123
Copy link

Hi,
Ticket heading and problem statement both are different. Could you please clarify whether you are looking for the API for show run | section router ospf {instance?, and for Which OS / Device model ?

And , also would be good if you can share the reference logs (manual) to analyze further data to cross check. Are the system CPU/memory status only peaks when executing these cli`s ?

@sumitsehgal123
Copy link

closing the issue as no response was received.

@virrsa
Copy link
Contributor

virrsa commented Aug 18, 2023

Opened PR #780 to address this issue. Testing showed that the time it took to parse the command went from 14 minutes down to ~1 minute with the optimized parser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants