-
Notifications
You must be signed in to change notification settings - Fork 739
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
New Template for Cisco IOS: show ip cef [detail] #695
New Template for Cisco IOS: show ip cef [detail] #695
Conversation
Initial commit with template, modified index file and tests
Please do not merge yet. I have found one issue. Will let you know once I've committed all changes. Regards |
Ok. Good to merge now. I've re-run all tests on ~500 devices. |
I added a PR into your fork/branch. We do not generally treat multiple outputs as a single command. There is a fine line in when this applies, but a good rule of thumb would be if the output is modified by additional parameters, then a new template is required. If the output is filtered, we generally can reuse the same template. PR into Yakuza branch: Yakuza-UA#1 |
- Added few more comments - Adjusted INDEX file to make sure templates are only used when applicable - Templates are no longer compatible with 'show ip cef 1.1.1.1', or 'show ip cef Vlan100'. Usage of 'detail' keyword is mandatory, such as 'show ip cef 1.1.1.1 detail'
This template produces output similar to cisco_ios_show_ip_cef.textfsm Additional flags are no longer supported (not parsed) Type is no longer supported, this is captured as nexthop Nexthop's value is literally identical to what you get from show ip cef (brief list) Template still mandates the use of 'detail' keyword (due to index file restrictions)
Ok. I had to review my template from scratch to make sure it complies with all requirements |
ISSUE TYPE
COMPONENT
cisco_ios_show_ip_cef.textfsm
cisco_ios_show_ip_cef_detail.textfsm
Cisco IOS: show ip cef [vrf NAME]
Cisco IOS: show ip cef [vrf NAME] [PREFIX | INTERFACE] detail
SUMMARY
There are two templates, one understands brief list of CEF entries and can only parse
show ip cef
, orshow ip cef vrf NAME
Other template can parse
show ip cef detail
,show ip cef vrf NAME detail
, orshow ip cef INTERFACE detail
, etc as long as keyworddetail
is present. Otherwise there will be no match in index file.I have tested this template in live environment and executed it in on 500 devices, including Catalyst 3750, 3850, 9300 and 9500, ISR 2800, 2900, 3800, 3900, 4300, 4400, as well as VG204, VG224, etc