show rep topology detail error

[ajackson79]

The 'show rep topology detail' parser fails when a device name includes a dash. (-)

Example of a device name that fails:

TEST-TEST

The error is:

python/site-packages/genie/libs/parser/iosxe/show_platform.py", line 9513, in cli
intf_dict['role'] = group['role']
UnboundLocalError: local variable 'intf_dict' referenced before assignment

[abvasudha]

Hi ajackson79,

Could you please share the raw output for 'show rep topology detail'.

Regards,
Vasudha

[ajackson79]

This output fails with the error above.

REP Segment 170
BOI-AIR-AGG-1, Te0/0/26 (Primary Edge No-Neighbor)
Open Port, all vlans forwarding
Bridge MAC: 00ea.bd0a.243f
Port Number: 021
Port Priority: 000
Effective Port Priority: 00002100EABD0A243F
Neighbor Number: 1 / [-4]
BOI-AIR-AGG-1, Te0/0/27 (Intermediate)
Alternate Port, some vlans blocked
Bridge MAC: 00ea.bd0a.243f
Port Number: 022
Port Priority: 040
Effective Port Priority: 04002200EABD0A243F
Neighbor Number: 2 / [-3]
BOI-AIR-AGG-2, Te0/0/26 (Intermediate)
Open Port, all vlans forwarding
Bridge MAC: 00ea.bd0a.1dbf
Port Number: 021
Port Priority: 000
Effective Port Priority: 00002100EABD0A1DBF
Neighbor Number: 3 / [-2]
BOI-AIR-AGG-2, Te0/0/27 (Secondary Edge No-Neighbor)
Open Port, all vlans forwarding
Bridge MAC: 00ea.bd0a.1dbf
Port Number: 022
Port Priority: 000
Effective Port Priority: 00002200EABD0A1DBF
Neighbor Number: 4 / [-1]

I fixed my local version by changing the regex on line 9467 of the file show_platform.py

original:

p2 = re.compile(r'^(?P[\w\d]+), (?P[a-z|A-Z]+\d+/\d+(/\d+)?) ((?P.+))$')

my change:

p2 = re.compile(r'^(?P[\w\d-]+), (?P[a-z|A-Z]+\d+/\d+(/\d+)?) ((?P.+))$')

Now mine no longer errors. It would be nice to get the main branch edited though so updates don't break things on my side.

[sanjaydilli]

Hi @ajackson79 could please you mention which image the parser is failing IOSXE or IOSXR ?

[ajackson79]

python/site-packages/genie/libs/parser/iosxe/show_platform.py", line 9513, in cli

iosxe

[sanjaydilli]

Hi @ajackson79, the above issue has been resolved and will take effect in the next release. Please continue contributing, and I will proceed with closing this ticket. Thank you