topic Re: Connectivity problems in MSA Storage

Connectivity problems

BR818263 — Wed, 31 Aug 2005 07:42:55 GMT

Hello,

I'm trying to connect up an MSL6030 tape library and a DL380 up to an existing SAN but am having real problems.

I've cabled the device and the server into the brocade 2800 switch. I've also set up a zone with the 2 new devices in. Sansurfer has been installed on the server but it can't find any attached devices. The driver for the HBA has been installed and I'm at a loss now as to what else to try.

Do I have to assign the MSL6030 to each server that needs to use it or should it just work? If it needs assigning how do I do this?

The existing servers/tape loader all work OK - its just these new ones. I'm also unable to attach the new tape loader to any of the older servers so guess I'm missing something pretty obvious.

Can anyone help?

Thanks
Dave

Re: Connectivity problems

Alastair Gray — Mon, 05 Sep 2005 03:49:05 GMT

Hi Dave,

Have you followed the following routine to check setup?

1. Can the devices be seen on the switch?
- are the relevant ports online for
both the tape system and the server?
- are the WWNs correct for both?

2. Are you sure that :
- the zoning created contains the correct
ports or WWNs (depending upon type
being used)
- the created zone has been added to
the correct config
- the config with the new zone has been
enabled.

Sorry if these are obvious questions, but past - personal - experience is usually that it's the simple things that have been missed!

Cheers,

- Alastair G

Re: Connectivity problems

meloni — Mon, 05 Sep 2005 04:33:38 GMT

Fist step is to create a Map in the NSR and the second is to assign a Map to the host WWN

If you do not make these steps, the tapes and robot will not appear to the server.

Re: Connectivity problems

BR818263 — Mon, 05 Sep 2005 05:27:29 GMT

Hi - thanks for all your help. It was caused by me saving the config but not enabling it!

Thanks
Dave

Re: Connectivity problems

CA1329001 — Mon, 26 Sep 2005 08:31:46 GMT

Hallo Dave , we experienced similar problems and it appeared to be the HBA driver which was automatically installed by Microsoft.
After we installed the known good driver from HP everything worked fine.