At first blush, it may seem trivial to create such group rulesets. However, when actually getting down to it, especially with a diverse set of devices, it is not so easy. Creating a CatOS group may be the easier of the two, though. There are only so many sysObjectIDs for CatOS devices (all starting with 184.108.40.206.220.127.116.11). With IOS devices, you're not so lucky.
What we have seen customers do in the past is using hostname conventions in their network to distinguish device types. That along with sysObjectID mapping allows them to create such OS-based groups. For example:
This is a router. All routers run IOS, so if the hostname of the device starts with rtr-, then this is an IOS device.
This is a switch. Switches can run either CatOS or IOS. For IOS switches, we expand our IOS group to say that if the hostname starts with sw- and the sysObjectID starts with 18.104.22.168.22.214.171.124, then this is an IOS device.
For CatOS devices, we say that if the device's hostname starts with sw- and the sysObjectID starts with 126.96.36.199.188.8.131.52, then this is a CatOS device.
Here's what our rulesets look like (created under Common Services Group Administration):
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...