SMI-S or SNMP

Hello,

This is Subir Das from Network Appliance.

I would like to implement a tool which will retrieve san switch
configuration data. This tool would be collecting data from Brocade,
McData, Cisco and Qlogic switches.

Q1. Should I use SMI-S interface or SNMP technology to retrieve switch
configuration data? Which support is better in san switches.

Q2. I need to collect following data using these tool. Which technique
(SMI-S or SNMP) has better support to collect following data.

Firmware version, Switch Name, Switch WWN, Domain ID, ISL Data, Name
Server, Trunkinfo, Port data, Zone data, Name server, License Data,
VSAN/LSAN

Thank you,

Subir

On 30 Aug., 18:16, wrote:
Hello,

This is Subir Das from Network Appliance.

I would like to implement a tool which will retrieve san switch
configuration data. This tool would be collecting data from Brocade,
McData, Cisco and Qlogic switches.

Q1. Should I use SMI-S interface or SNMP technology to retrieve switch
configuration data? Which support is better in san switches.

Q2. I need to collect following data using these tool. Which technique
(SMI-S or SNMP) has better support to collect following data.

Firmware version, Switch Name, Switch WWN, Domain ID, ISL Data, Name
Server, Trunkinfo, Port data, Zone data, Name server, License Data,
VSAN/LSAN

Thank you,

Subir

Hi Subir,

i recommend using SMI-S. All vendors support SMI-S - and you can get
all data that you're looking for. Major advantage is that you need
only one API - instead of reading the different MIBs, dealing with the
SNMP authorities etc. You would also ensure that you are compatible
with future versions of the switch OS. Some vendors e.g. Brocade
require you to install a proxy smi-s.

regards

sarguid