-
Notifications
You must be signed in to change notification settings - Fork 742
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
Juniper junos show system processes brief #1974
base: master
Are you sure you want to change the base?
Juniper junos show system processes brief #1974
Conversation
…ief.textfsm Co-authored-by: Michael Bear <38406045+mjbear@users.noreply.github.com>
Set this to draft status until it is verified by someone else. This does work when using output from both Junos Classic and EVO. I had to make a few adjustments to the template to make it work for both properly. I tested using the Nornir site and the output in the test files I provided. |
I did a double check for the |
ntc_templates/templates/juniper_junos_show_system_processes_brief.textfsm
Outdated
Show resolved
Hide resolved
Thank you for verifying. What I found does indicate the |
…ief.textfsm Co-authored-by: Michael Bear <38406045+mjbear@users.noreply.github.com>
I concur with that. Ansible on the other hand which can use textfsm templates, does not strip that out. |
…put from the router
The suggested fix of Output: I updated that line in the template to @mjbear Out of curiosity, when we are adding lines to the template like this that cover the line being there but don't actually capture anything, is there a rule of thumb as to how much of the line to add? |
Ooops on my part there. 😞
That's where I was headed. |
In this template I set the values that applied to me to variables and ignored the rest. After thinking about this a bit more, I am going to update this template and future ones to include all of the values listed in case those apply to someone else. That seems like the more complete way of doing this so others don't have to circle back later and "finish" the incomplete template I am contributing. |
…lue for parsed data in evo
I am going to make this PR ready for review. I don't think I can do anything else to it unless there is some bad syntax that someone points out. I skipped adding collection for the top uptime lines in both EVO and Classic. They were not quick and simple to get working and in reality that data has better methods of collection in Junos and other templates anyway. |
You don't have to capture all the data unless there's really value in capturing that data (reference). (Use your best judgement, hehe.) |
I understand and can see there may be value to others by adding the capture now. There just was not value in my particular use case so I never bothered capturing the data. Other than the top uptime lines, it was pretty quick and easy to add the other two lines to the template using the syntax we had already established in the work I had submitted. |
Updating juniper_junos_show_system_processes_brief.textfsm to support both Classic and EVO varieties of Junos.