Discovery of Brocade SAN Switches
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2020 07:54 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2020 05:32 AM
Hi Alikutty,
thank you very much first. We did your suggestion. The discovery ran much more faster. However, the result is no different from the previous one. I think it is because of the snmp configuration of the switch.
Maybe you or anyone else has some tips.
BR, Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2020 07:10 AM
What is the current error in your discovery log? Where does it stops in the ECC queue?
If it is failing during Shazzam then Port 161 should be opened.
If it is failing during Classification, then your SNMP credentials are not working.
If it is failing during Identification, then your SNMP OID entry is missing in the instance.
Please clarify?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2020 07:25 AM
It's not failing, but discovered as a "linux server" device without any details in the tabs.
Port 161 is open
SNMP credentials working SNMPv1 and also SNMPv3, we tried both.
Peter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2020 07:42 AM
So it is scanning on port 22. This should not happen if you setup the behavior correctly. Did you setup SNMP behavior and update it on your discocery schedule? Behavior may not work in quick discovery.
Please show a screenshot of your ECC queue and discovery schedule configuration.
Sample

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2020 09:31 AM
Hi Alikutty,
many thanks for your help so far - we really appreciate it 😉
I will provide you with detailed information regarding the discovery set up by choosing the just freshly established "SNMP only Discovery" behavior:
That's what is in the ECC queue:
Finally this SAN switch was classified as "linux server":
Any helpful suggestions are highly welcome!
Thank you in advance.
Sincerely,
Joachim