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

[IOS-XE] [Help Wanted] show rep topology detail when ring is broken and the ring has failed ports parser is empty #927

Open
ajackson79 opened this issue Feb 7, 2025 · 0 comments

Comments

@ajackson79
Copy link

ajackson79 commented Feb 7, 2025

So if I run the parser when the rep ring is in a broken state because of a fiber cut, instead of returning what data it could I get a SchemaMissingKeyError and no data at all is returned. I know the data that would be returned will be incomplete, but is there a way to handle that error and have it return what data it can collect and ignore the missing keys?

Example output from a failed interface:

DEVICE_NAME, Te0/0/6 (Intermediate)
Failed Port, Reason: Physical link down
Bridge MAC: 7488.bb58.39bf
Port Number: 00C
Port Priority: 800
Effective Port Priority: 80000C7488BB5839BF
Neighbor Number: Not available

@ajackson79 ajackson79 changed the title [IOS-XE] show rep topology detail when ring is broken [IOS-XE] [Help] show rep topology detail when ring is broken and the ring has failed ports Feb 7, 2025
@ajackson79 ajackson79 changed the title [IOS-XE] [Help] show rep topology detail when ring is broken and the ring has failed ports [IOS-XE] [Help Wanted] show rep topology detail when ring is broken and the ring has failed ports Feb 7, 2025
@ajackson79 ajackson79 changed the title [IOS-XE] [Help Wanted] show rep topology detail when ring is broken and the ring has failed ports [IOS-XE] [Help Wanted] show rep topology detail when ring is broken and the ring has failed ports parser is empty Feb 7, 2025
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

No branches or pull requests

1 participant