How to classify Brocade as a Storage Switch, Not IP Switch

[jdiegeliv]

I have a request that all Brocade devices be classified as cmdb_ci_storage_switch.  Currently they end up in cmdb_ci_switch.  I've modified the model to remove IP Switch but when I run Discovery it adds IP Switch back and the devices stay IP Switches. Any idea where I should be tweaking this?

[Rahul Priyadars · Accepted solution]

Check classification and it must be satisfying below classification criteria as i see there are 85 OID for brocade manufacturer and its simply trigerring n/w switch pattern.

For Storage Switch Classification is as below.

RegardsRP

[jdiegeliv]

Thank you.  This was exactly where I need to look.

[Saptarshi7]

Hi ,

Were you able to fix the issue via tweaking the Probe? I created a SNMP OID record, with table name as Storage Switch and Pattern as "Standard Network Router", the device was being classified in the Storage Switch space but later changed back to IP Switch. 

[Evan Miller]

In case this helps anyone, what Rahul posts is somewhat deceiving. The second image he posted is actually for storage classification which is done through an SMI-S classification, not through an SNMP classification. So you basically have two options:

1. You can use SMI-S/CIM as a discovery method instead of SNMP to properly discover the storage switches with all the out of the box stuff.
2. You can't simply change the table on the OID classification for the OIDs linked to storage switches to Storage Switch. I've tested this out, it doesn't work. This is because when the initial classification takes place during the classification phase of Discovery, it will show up as a storage switch. But as soon as the Network Switch pattern kicks in, it will shift it back to a Network Switch, because that is what table is configured on the pattern. So your second option would be to clone the Network Switch pattern and change the table over to Storage Switch in the pattern, and then fix all the references to fields that exist in Network Switches but not Storage Switches. Or you can create a custom pattern instead. You would then need to create a new SNMP Classifier to link that OID Classification and the pattern to (via a horizontal pattern trigger probe). It's really not a great path to go down. It's a lot of work for very little value.