Thanks Nikolay.
I should have stated that I already use include and categories when I can , I'm just wondering if there's a way to condense the config into something similar to the commands someone would actually enter.
For example, I'm on a stack of two X460-48t switches and someone entered:
create qosprofile QP2
create qosprofile QP5
create qosprofile QP6[/code]Those three commands resulted in 350 lines being added to the running configuration with each line being for a specific QP for a specific port:
...
configure qosprofile QP2 minbw 0 maxbw 100 ports 1:1
configure qosprofile QP2 minbw 0 maxbw 100 ports 1:2
configure qosprofile QP2 minbw 0 maxbw 100 ports 1:3
configure qosprofile QP2 minbw 0 maxbw 100 ports 1:4
configure qosprofile QP2 minbw 0 maxbw 100 ports 1:5
...[/code]Whereas most vendors would condense this down into:
configure qosprofile QP2 minbw 0 maxbw 100 ports 1:1-1:58
configure qosprofile QP2 minbw 0 maxbw 100 ports 2:1-2:58[/code]For most vendors showing the running config is considered to be the go-to command when trying to figure out how a switch has been configured. Configuration categories and the include command are useful if I already know what I'm looking for but I'm finding that's the case less and less often the more I work :)