Start a Conversation

Unsolved

This post is more than 5 years old

8812

February 26th, 2013 06:00

VNX and SMI-S Provider

​Hi,​

​I have a set-up with one VMAX and one VNX. I am sometimes controlling VMAX with a piece of software called Solutions Enabler. To do so, I attach to Solutions Enabler a gatekeeper from VMAX. This gatekeeper allows Solutions Enabler to communicate with VMAX using SMI-S protocol.​

​I have just read that a similar configuration can be deployed with VNX. In this case, the software is not called Solutions Enabler but SMI-S Provider. However, in VNX there is nothing like a gatekeper so I wonder how the communication is performed. Does SMI-S provider connect to the VNX IP (either SPA or SPB)?​

​Thanks​

8.6K Posts

February 26th, 2013 07:00

The block SMI-S provider is off-array – it runs on a management server and AFAIK it uses Solutions Enabler to communicate with the VNX SP’s

Take a look at the support site for downloads and documentation

8.6K Posts

February 26th, 2013 07:00

Solution Enabler should work just as well with VNX block or Clariion

AFAIK it talks to the SP’s via IP like navicli does

53 Posts

February 26th, 2013 07:00

Hi Baif,

Actually I am more looking into ProSphere and I saw that to connect to VNX SMI provider is needed. I was wondering how the communication goes in VNX

February 26th, 2013 07:00

Not sure about SMI-S for VNX OE Block

I think there is SMI-S for VNX OE File

If you're looking for VASA connection agent for VMware, it's embeded in both SPs of VNX OE Block.

53 Posts

February 26th, 2013 08:00

Hi, I cannot find anything useful apart from realse notes. I have just read:

◆ In-band discovery. This is conceptually the same as the Symmetrix SMI-S

Provider-based discovery. If the correct information is in place, SMI-S Provider can

automatically discover a CLARiiON array or VNX storage system during its startup

But does it use gatekeepers? I cannot see anything similar in VNX GUI. If not, how can I know the port which is being used for the SMI-S communication?

Thanks

8.6K Posts

February 26th, 2013 11:00

AFAIK there are no gatekeepers in VNX / Clariion

53 Posts

February 27th, 2013 01:00

Ok, but then how you define which iSCSI paths to use for the inline communicaiton? Or does it use broadcast?

53 Posts

February 27th, 2013 03:00

Hi Rainer

Thanks for the support. In that case, what is the difference between out of band communication and inband communication. I think you are referring to inline communicaiton.

8.6K Posts

February 27th, 2013 03:00

It is not using ISCSI – just TCP/IP like navicli does

TCP port 443 I think

4.5K Posts

February 27th, 2013 14:00

In-Line or In-Band is down the iSCSI connection - where you send SCSI commands to the array. Out-of-band is the IP ports on the array - SPA and SPB Management Ports. The host communicates some information over the IP network to the SP Management Ports. For example, when you connect a new host to an array (using Fiber channel for this example), the WWN is send to the array in-band - down the fiber - when you look on the array in Connectivity Status, you will see a new entry with only the WWN listed. If you have the EMC Host Agent installed and you have IP connectivity between the host and the array over the LAN side, the host agent will send additional information to the array - the host's LAN IP, the host name and other information.

glen

53 Posts

February 28th, 2013 02:00

Hi Glen,

Thanks. Imagine I use the in-band connectivity and I have 4 iSCSI paths from SMI-S Provider to VNX. Which path will be used? All using round robin? all doing a broadcast?

4.5K Posts

March 1st, 2013 13:00

iSCSI must be separate from LAN traffic - you must use a different subnet from the address for the SP Management Ports. SMI-S and other software running on hosts would use the SP Management ports and not the iSCSI ports. iSCSI should only be used for data traffic.

Not real sure what you mean by "I have 4 iSCSI paths from SMI-S Provider to VNX. Which path will be used? All using round robin? all doing a broadcast?". The iSCSI ports on the array should connect directly to either a switch or a host.

On support.emc.com - search for Suuport Solution emc245445 - this lists all support articles for iSCSI on the VNX and CLARiiON.

I also believe that to use SMI-S, you must also have Solutions Provider.

glen

53 Posts

March 4th, 2013 02:00

Hi,

I found the answer to my question. VNX does not use "real" inband communication. SMI-S provider can only communicate to VNX using IP connectivity, unlike VMAX which can communicate using iSCSI, FCoE or FC.

Hope I can help someone

11 Posts

March 8th, 2013 06:00

I'm using SMI-S in our ProSphere environment and it was easy to setup using the ECOM Deployment and Configuration Guide

Basic setup is create a text file with the SP IP's or hostnames,

run symcfg add authorization -username -password -host

run symcfg discover -clariion -file

Restart the ECOM service and your all set.

2 Posts

August 19th, 2014 00:00

Hi,

I would like to know where I can download the latest smi-s provider which can be installed on host, in order to communicate with VNX. Also, is there something like smi-s versions which can only be used?

Appreciate if you can get this info. Please do the needful.

No Events found!

Top