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]

Please try running discovery with SNMP as priority 1 or order 1 credentials and Unix order 2 (or even take out Unix credentials if possible)

Reason for your error:

Credentials can be assigned an order value in the Credentials Form, which forces the application to try all the credentials at their disposal in a certain sequence. If you do not specify an order value, the application tries the credentials in the Credentials [discovery_credential] table randomly, until it finds one that works. 

Once the discovery is successful, susequent runs should be easier, because:

After identifying the credentials for a device, Discovery and Orchestration create an affinity between the credentials and the device using the Credential Affinity [dscy_credentials_affinity] table. All subsequent discoveries or Orchestration activities attempt to match the credentials in this table with a device for which an affinity exists. If credentials for a device change, Discovery and Orchestration try all available credentials again until they create a new affinity.

Other Info on Credential Order

Order (sequence) in which Discovery tries this credential as it attempts to log on to devices. The smaller the number, the higher in the list this credential appears. Establish credential order when using large numbers of credentials or when security locks out users after three failed login attempts. If all the credentials have the same order number (or none), the instance tries the credentials in a random order.

Please like or accept solution so that it helps others too.

[Peter Nowak]

Thx for answer.

We'll try this. I'll get in touch.

BR, Peter

[Peter Nowak]

Hi,

we implemented the tip. Unfortunately this did not lead to the desired success. As before, no data can be extracted from the switch.

Also the behavior of the discovery run itself has also remained the same ...

Any other tip ?

BR, Peter

[Alikutty A]

Hi Peter,

You will need to use a behavior and scan the device in a separate schedule using the SNMP protocol only.

Steps to follow:

1. Create a new behavior with SNMP only port

2. Create a new schedule and add your device IP in it, Select the mid server selection method as Use Behavior and add yours in it.

3. Run the discovery

When you scan the device, Shazzam will only use the SNMP port and if you have valid credential/firewall access (161) then the device should get discovered. You can do this approach for all SNMP devices which have the SSH ports opened in it.

Note: Do not change the classification priority as it is global change.

Reference: https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/task/create...