-
Notifications
You must be signed in to change notification settings - Fork 723
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
template request: show ip bgp neighbors x.x.x.x advertised-routes #639
Comments
Do you mind providing more information for this? OS, raw output, etc? This may just need to be updated in an existing template, but not much information to go off of to address it. |
Hi @FragmentedPacket something like this. the blue marker is a network address like: 192.168.11.0/24 it was the prefix advertised to your bgp neighbor. Thanks |
Dummy Router#show ip bgp neighbors 172.17.55.13 advertised-routes
*> 113.55.45.0/24 0.0.0.0 32768 i Total number of prefixes 7 |
Do you get structured data parsing this with |
Ok no problem. I'll have to take a look at some point to see what the differences are and whether it's worth another template or adding any use cases that don't already exist in that template. |
@FragmentedPacket Again, Thank you for the efforts and for making all of the templates. |
@asoltes I submitted a new PR for this. So i'll have Jacob review it and if everything looks good we'll merge it. |
@FragmentedPacket I saw that the templates is now merged and I am able to update/download the new template but I am not able to parse the data.
/ntc-templates/templates/cisco_ios_show_ip_bgp_neighbors_advertised_routes.textfsm |
@FragmentedPacket woah that was awesome. I am now able to get the parsed data. Thank you, It will help us a lot in automating our network. stay safe and have a good day :) |
@asoltes I didn't catch that the tests weren't passing. I had to make some changes to the template names and index file as well. Do you mind testing again and letting me know? I will merge it once tested and be cutting a new release hopefully this week. |
ISSUE TYPE
The text was updated successfully, but these errors were encountered: