HPE EVA Storage
1832650 Members
2902 Online
110043 Solutions
New Discussion

Connecting W2K3 Servers to MSA3000

 
WCzar
Frequent Advisor

Connecting W2K3 Servers to MSA3000

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?
47 REPLIES 47
Steven Clementi
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

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
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

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
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

"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
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

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
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

"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
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

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
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

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

Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

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
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

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
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

So it appears the serial port was manually locked or disabled. There is no reset button on the switch exterior either. Is there a switch inside the case or a battery that can be removed to initiate a reset?
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

As a long shot we tried a serial cable from a Brocade 3200 switch - it WORKS! Looks like the HP switch is a re-branded Brocade. We now get a serial connection. and need to see if any zoning was previously set up - if not to add zoning so our Window servers can see the SAN disk assigned to them. Should we reset the switch to the original config (including password and default IP)?
Uwe Zessin
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

The SANswitch 2 has some parameters set to non-standard values when it comes from HP. There is a download file on the support pages in case somebody does a factory reset.
.
Steven Clementi
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

Yes, HP does not make any SAn Switches, they license and re-brand from Brocade and Cisco... and previously McData.

If you have a serial connection to the switch, than you should not need to reset the switch... especially if it is already running in a production environment.

some useful commands...

ipaddrshow - show IP configuration
ipaddrset - set IP configuration
password - reset passwords (might be passwd, I have not done it in a while)
switchshow - show switch info (port logins, wwid's, etc)
cfgshow/zoneshow - show the current zone configuration(s).

After you set the IP, you should be able to than use Webtools from a browser.


Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

Thanks for the information, Steven.

We were able to get the password and IP. We can hyperterminal in - webtools works as well. There are several zones already set up, but are not used. We were able to create a host and virtual disk in EVA Command View and present the disk. We got the WWN for the HBA (Emulex 9802)in the W2K3 physical server from HP Insight Manager. It has a green receive led and amber transmit. When we go to the W2K3 server we assigned the storage to we still don't see the disk. We issued a rescan from Disk Administrator and tried rebooting as well. Also tried presenting another virtual disk previously set up to the W2K3 server - it still doesn't see it. We must be close to getting this thing running. Anything else we can check?
Rob Leadbeater
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

Hi,

> ... We got the WWN for the HBA ...

This implies that you manually entered the WWN of the HBA into Command View EVA, rather than it being automatically detected.

If it wasn't detected, then my guess will be that the zoning isn't correct - the HBA doesn't have access to the EVA.

Cheers,

Rob
Steven Clementi
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

Can you post the output of the zoneshow/cfgshow commands? also switchshow.

Or, if you go to webtools and hit the admin page, there is a "report" button that will open a web page with all the info in it. Zip it up and post it or copy/paste to wordpad..

Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

Steven, attached is the report from WebTools\Admin. We are looking at how zoning was set up before we inherited the box. Looks like we probably have to create a new zone and alias for our test server. Let us know if you need more information.
Steven Clementi
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

Yep. beofre the EVA will "see" the WWID's from the HBA's in the new servers, you will need to create, at the very least... a new zone and add it to the zone configuration.

This is easily done through the webtools gui in the Zone Administration applet.

So, following the naming convention already laid out...

1. Create an alias for the server and add the HBA's port WWID to it.
2. Create a zone for the new server, include the alias for the new server and the 2 aliases for the EVA.
3. Add the new zone to the zone configuration and "enable".


Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

Created the alias and then the zone. Saved the config and enabled it. W2K3 server still does not see the SAN storage. Ran DiskProbe utility from MS it shows only drive 00 (local disk). Installed the latest Emulex 9802 StorPort drivers and HBAnyWhere software (should we have used the HBA drivers instead?). HBAnyWhere diagnostic local testing is OK. Attached is the latest switch report.
Rob Leadbeater
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

Hi,

Did you add the new zone into the config ?

It's quite easy to miss this step. I know I have done more than once...

Cheers,

Rob
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

There is only 1 config file at this time. We used the WebTools (ZoneAdmin) to create the new alias and zone and then saved the config and enabled it from the main memu bar.
Steven Clementi
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

Ok... but did you add the new zone to the configuration?


On the last tab, in the left window pane, there will be "available zones" that you can "add" to the configuration.


Can you post the output for...

cfgshow
zoneshow


Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
WCzar
Frequent Advisor

Re: Connecting W2K3 Servers to MSA3000

Posted the cfgshow and zoneshow as 1 document.
Steven Clementi
Honored Contributor

Re: Connecting W2K3 Servers to MSA3000

Did you check the host configuration on the EVA?

Originally, you must have typed in the WWID of the hba, check to make sure you typed it correctly... and/or select it no from the drop down box in the "Add Port" wizard under ports.


The zoning looks ok as far as I can tell.
Is "a_HPSANSRV" the new server? You can take out the 2000xxxxxxxxxxxx entry fro mthe alias. You should only use the Port WWID in the alias.. not the Node WWID.


Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)