-
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
Cisco IOS show cdp neighbors issue #727
Comments
Going thru the regex i think i found my issue
Fastpath/ICOS interfaces dont follow the pattern of Cisco for interfaces names https://regex101.com/r/utctz5/2 Even after getting full matches for either case i still cant get the full cdo nei.. output for devices with no domain.com |
Fast OS as in the Cisco 1900 switch last sold in 02? |
Nop :) Theseare relatively new devices.
Im currently working with them joined to Cisco routers on enterprise networks, also didnt see any apparent templates for them so i was thinking i could help on that front: EDIT: I created a workaround parsing raw data manually for now
|
Was able to match my cases with:
|
Thanks for looking into it. That does appear to solve your issue, but breaks existing raw data. |
@alepodj the fix is now in master. Thanks for reporting and providing data |
ISSUE TYPE
TEMPLATE USING
SAMPLE COMMAND OUTPUT
OUTPUT1:
OUTPUT2:
SUMMARY
STEPS TO REPRODUCE
When using show cdp neighbors on Router1(Output1) i get the expected output:
...but on Router2(Output2) i get:
Main differences i see is Router1 has Device ID value with the domain portion while Router2 doesnt and the Capabilities changes are
R
andS I
. Found the interface under PORT ID is also quite differentRunning a full
show cdp neighbors
without providing a filter interface, will only pick up the entries that include the domain.com part at the end of their IDs and ignore ones without it. I guess i could say thats the source of my issues.EXPECTED RESULTS
Both routers return a list of data as Router1 Output
ACTUAL RESULTS
Router2 is only displaying Device ID
The text was updated successfully, but these errors were encountered: