Add cisco ios show spanning-tree root

[osmantitu]

Template for parsing output of show spanning-tree root cmd of Cisco ios devices.

[mjbear]

Hello @osmantitu

We also need test data included in this PR.

As long as you put the raw data in the correct spot, you can use helper scripts to generate the structured data (yaml).

The test data is necessary so that we can make sure the template is backwards compatible in the future when more changes are needed.

🎯 Please respond back if there are any questions. Thank you!

[osmantitu]

Hello @mjbear,
provided the raw data and parsed text in yaml format for testing.

Thank you

[mjbear]

Bringing this discussion out to the main part of the thread...

should this be 2 separate values? like ROOT_ID_INT and ROOT_ID_MAC?

Also a worthwhile point.

Maybe instead of ROOT_ID go with PRIORITY (the STP priority) and MAC_ADDRESS?

@osmantitu
What are your thoughts on splitting up the Root ID into two distinct values?

@itdependsnetworks
cisco_nxos has a similar template and this one is split up with numeric PRIORITY and ROOT_ID as the MAC address.
I suppose this is a reasonable path forward? 😀

• https://github.com/networktocode/ntc-templates/blob/master/ntc_templates/templates/cisco_nxos_show_spanning-tree_root.textfsm
• https://github.com/networktocode/ntc-templates/blob/352628b8ed079705d70d3153a5a767dbd15182f3/tests/cisco_nxos/show_spanning-tree_root/cisco_nxos_show_spanning-tree_root.yml

Update:
It just so happens right now the ntc-templates doesn't have a cisco_ios STP root template. That's fine and all. The closest thing is show spanning-tree for cisco_ios, which captures priorities, but not root bridge MAC addresses (another one of those "so be it" situations).

• https://github.com/networktocode/ntc-templates/blob/master/ntc_templates/templates/cisco_ios_show_spanning-tree.textfsm
• https://github.com/networktocode/ntc-templates/blob/master/tests/cisco_ios/show_spanning-tree/cisco_ios_show_spanning_tree.yml

[osmantitu]

@mjbear
It's a good idea to split ROOT_ID into PRIORITY and MAC_ADDRESS.

[mjbear]

@mjbear It's a good idea to split ROOT_ID into PRIORITY and MAC_ADDRESS.

So far I've split out the priority and root bridge/switch's MAC address, but that last capture group is still named ROOT_ID. This matches was is used in the cisco_nxos template for example.

Providing time for feedback from others before merging. Thank you!