Connecting W2K3 Servers to MSA3000

[WCzar]

We have an MSA3000 SAN, which is carved up into three separate array groups. We can use the EVA software to create new hosts and create\assign virtual disk. Currently the appliance server used to manage the SAN and one additional test server are connected to the fabric via HBA (Emulex 9802). The two HSTNM-N001 fiber switches are not connected to ethernet. Not sure how to get the W2K3 test server to see the SAN disk. We're looking at the mountvol command or do we need to install the iSCSI connector on the W2K3 box?

[Steven Clementi]

Ok.. assumin you mean an EVA 3000...

Connectivity to an EVA3000 is not over Ethernet. You test server has HBA's in it, thats the first thing you need.

The next thing you need is probably to create some zones on your fabric switches so that the server can talk to the EVA.

After you do that, you can create the host on the EVA and present sotrage to it.


Before that, We would need more information on your SAN Switches. You say NSTNM-N001, is that a network name that has been given to them? Do they have any other identifying marks? Model number? maybe you can take a picture of them and post it?


Steven

[WCzar]

Thanks for the reply Steven.

Yes, you are correct it's an EVA 3000.

Both switches in the cabinet are labeled HP Storage Works SAN Switch 2/16, series HSTNM-N001. They each have 1 ethernet port - we only want to connect using fiber.

Our test server has an Emulex HBA, connected to one of the SAN switches and has link lights.

Both SP controllers display a storage system name, which we see in the EVA management app. We can create hosts and vdisks and do the present under that.

Is there anything on the test server side we need to do to access the assigned SAN storage?

[Steven Clementi]

"Is there anything on the test server side we need to do to access the assigned SAN storage?"

Did you load the latest Emulex drivers yet for the HBA's?

Did you load up the proper multipath software for the EVA?

Look in Command View. What VCS version is running on the EVA?

Click on the HOSTS folder and click Add Host. Click on the drop down box to see if there are any WWID's listed.

Are there? if not, you will need to log into the switches and create some zoning.

This will entail using the console connection, or connecting the switches to your LAN.


Steven

[WCzar]

In Command View, under storage system properties .... Type: = HSV100, Version: = 4007.

For adding a host... the WWN port list pull down displays "port list is unavailable". Although we can manually enter a WWN port name (the Emulex 9802 in the test server).
Not following your reference to zoning in the switches.

The virtual disk status condition in Command View is Green.

On the test server.....

Installed cp007109 (HP Stor Port FC Driver ver 5-1.20a7.

Installed EVA 3000\5000 MPIO Full DSM VCS 4.xxx Disk Arrays v3.00.00.

Did a rescan and later a reboot.

Device manager shows Emulex as "working" - we have link lights on the card.

[Steven Clementi]

"Not following your reference to zoning in the switches."


Zoning is a way to segragate traffic between devices on the SAN. For instance. I have 1 Linux host, 1 Windows Host and 1 EVA3000. My zoning would look something like this:

Zone1:
Windows Initiator (HBA)
Storage Target1 (EVA3000 Controller A Port 1)
Storage Target2 (EVA3000 Controller B Port 1)

Zone2:
Linux Initiator (HBA)
Storage Target1 (EVA3000 Controller A Port 1)
Storage Target2 (EVA3000 Controller B Port 1)

Zoneset:
Zone1; Zone2

This would allow both servers to talk to the EVA... while not being able to see the traffic of the other server to the EVA or the other device at all.


From the sounds of it, you probably already have 1 zone configured... for the management server. You will need to log into the SAN Switches and add additional zones.

There are 3 ways to accomplish this.


1. Using a Console cable plugged into the SAN Switch and a terminal program.

2. Telnet to the switch (after you plug it into the network)

3. Browse the Switch Web interface (after you plug it into the network)

When you get to this point, let me know and I, or someone, can take you further.



Steven

[WCzar]

Trying to make a serial connection to either switch via HyperTerminal doesn't work. Start with switch powered off - then start HyperTerminal configured for 9600, 8 databits, no parity, 1 stop bit and flow control = to none. Then power up the switch - nothing displays. Tried hitting Enter 3 times, still nothing. Tried the other switch and a diferent laptop - same condition. Used a cable from another newer HP switch we're testing - still no good. I found a couple of forum threads mentioning serial cable must be pins 2,3 and 5 straight-thru. Is there a special serial cable required?

Have not tried Telnet or Web Interface - rather go with HyperTerminal if possible.

[Steven Clementi]

The cable you need is not a standard serial cable.

You might be betteroff with a network connection.

If the IP is still the default.. it is 10.77.77.77

uname: admin
pword: password (default)


Steven

[WCzar]

We inherited all of the StorageWorks equipment from one of our remote offices. There was no documentation - I wish there was.
We still cannot make a serial connection to either of the 2/16 switches. Hyperterminal session says connected, but we don't see any login prompt or post messages when the switch is powered up.
Made a new serial cable with only pinouts 2,3 and 5 straight thru - doesn't work. Got a serial cable from our local vendor they had used to configure an EVA3000 - that doesn't work and when I tested the pinouts found they are not 2,3&5.
Working on the ethernet connection, but don't know the IP address or if the password was changed. Man, bad news!
Is there any way to manually reset the initial config so we can use 10.77.77.77 admin\password?

[Rob Leadbeater]

Hi,

> Is there any way to manually reset the
> initial config so we can use 10.77.77.77
> admin\password?

No. You will have to get the serial connection working in order to do anything useful. Even then, be prepared for some pain if the username/passwords have been changed from there defaults. Getting these SAN switches back to a default config isn't trivial...

Good luck,

Rob