Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

RME Device Group Filters

Does anyone have any useful resources related to creating RME Device group filters?

I was thinking of starting a web site that had useful LMS info such as scripts and filter examples.

I encountered this issue when trying to create a number of device group filters to do various things and ended up just assigning devices manually.

Example of filters I want to create:

1) A filter to group all CatOS based hardware

2) A filter to group all IOS based hardware.

1 REPLY
Cisco Employee

Re: RME Device Group Filters

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 1.3.6.1.4.1.9.5). 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:

rtr-core-1.company.com

This is a router. All routers run IOS, so if the hostname of the device starts with rtr-, then this is an IOS device.

sw-core-1.company.com

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 1.3.6.1.4.1.9.1, 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 1.3.6.1.4.1.9.5, then this is a CatOS device.

Here's what our rulesets look like (created under Common Services Group Administration):

CatOS:

------

Device.HostName startswith "sw-" AND

Device.SystemObjectID startswith "1.3.6.1.4.1.9.5"

IOS:

----

Device.HostName startswith "rtr-" OR

( Device.HostName startswith "sw-" AND

Device.SystemObjectID startswith "1.3.6.1.4.1.9.1" )

Again, this relies on a consistent naming scheme. If that is not hostname, it could be something like sysContact or sysLocation, or you can use the User-Defined fields.

150
Views
0
Helpful
1
Replies
CreatePlease to create content