Discovery of Brocade SAN Switches

[Peter Nowak]

Hi,

we want to discover Brocade SAN Switch DCX8510-8 (IBM System Storage SAN768B-2 Backbone
(2499-816).
We want to use the SSH connection, but Shazzam identified the switch as a UNIX System and therefore the discovery run failed.

Then we tried SNMP. But snmpv1 and also snmpv3 failed. Every time the Shazzam identified the switch as UNIX and no further data came out of the switch.

We don't want to use CIM, as CIM use the BNA, and BNA will not be used in future. Other CIM server isn't available.

So, how it is possible to discover a Brocade Switch.

Thx for any answer.

BR, Peter

[Vivektietsood]

this has me confused too :). Can you check IRE (Identification and Reconciliation Rules) for switches and Linux servers ? And paste the screenshots here. 

[Alikutty A]

Hi Joachim,

From the ECC queue, the Identification phase is going into the credentialess discovery pattern which is not expected. Can you disable credententialess discovery inside your mid server and try this again?

Ideally it should call the Network switch pattern for the right device discovery.

Thanks!

[Joachim Fink]

Hi Alikutty,

I disabled credententialess discovery inside our mid server - now the device doesn't get classified at all - discovery ends after SNMP classify which found 348 OIDs :

"SNMP - Classify: 348 OIDs"

Thank you once again!

[Vivektietsood]

okay, another thought - are you able to discover any SNMP device like printers or any other switch / router if not then this may indicate a problem with the pattern, maybe pattern needs to be installed again. If yes then sometimes network engineers create custom ports, it may be possible that the switch in question is not configured to listen on port 161, and is using some other custom port. 

[Vivektietsood]

This might be useful too, taken from the following thread:

https://community.servicenow.com/community?id=community_question&sys_id=b12d89b2db0af3804abd5583ca96...

The Linux SNMP classifier, by default, is inactive and typically wouldn't be used. Enabling the classifier tends to collect a lot more things as Linux Servers then you'd actually want it to. It's likely your device has a lot of routing capabilities, which is why Discovery is classifying it as such.

If the device is running a Linux OS and you can use SSH, I'd recommend trying that route first. However, most appliances are running a hardened version that you might not be able to query everything by default.

In the end, you may have to come up with your own Discovery SNMP pattern to create your CI properly in the table you want and with the right attributes that are specific to the manufacturer/model. I'd recommend watching Doug's video on creating SNMP patterns to help you out.

https://community.servicenow.com/community?id=community_article&sys_id=dfd86535db172300f21f5583ca961...