Probing Timeout Error on booting DS15 & ES40

[Ken USA]

Hi all:

We just got a new MSA-1000 with
Firmware Ver 4.48 Build 342
Hardware Rev 7 [AutoRev: 0x010000]
Internal EMU Rev 1.86

Was able to connect MSA-1000 to a console to enter CLI commands. Commands like "show units" and "show disks" work fine. Was able to add a unit with a disk #.

Example:
CLI> add unit 0 raid_level=0 data=DISK101
CLI> set unit_id 0 100

We have fiber optics wires connected from back our DS-15 to MSA-1000.

On DS-15 boot prompt, got the details (WWN etc) for the fiber card and added a connection to MSA-1000.

Example:
P00>>> show dev pgb0
pgb0.0.0.17.0 PGB0 WWN 1000-0000-C92C-1C60

CLI> add connection APGB WWPN=10000000-C29C1C60 profile=OpenVMS

P00>>> init
P00>>> wwidmgr -show wwid
Probing timeout.pgb0.0.0.17.0

We get the above "Probing Timeout" error. Can't figure out what we have missed in setting this up.

Noticed that doing "show connection APGB" at the CLI prompt does not give details like controller #, port # or status. here's what we get.

CLI> show connection APGB
Connection Name: APGB
Host-WWNN: 10000000-C92C1C60
Host-WWPN: 10000000-C92C1C60
Profile: OpenVMS
Unit Offset: 0


Using ES-40 & MSA-1000 gives same error.

Any help will be highly appreciated.

Thank you.
-Ken

[The Brit]

Hi Ken,
Can you attach the output from "show dev" (at the P00> prompt), and you didn't mention whether the MSA replied with an acknowledgement when you entered the "add connection" command. I think it should respond with something like

Connection XXXX has been added successfully.

Also, I think the "add connection" command is only used if the host is not yet connected to the MSA, but the WWN is known.

I think that normally the connection is automatically detected when the physical (fiber) connection is made, and should show up with a "show connection" command.

If there are more than one paths to a host, each one will show up as a separate connection, however assuming you have only one, then it should show up easily enough with a "show connection" command. All you have to do then is modify the connection name and/or profile using the "set connection" command.

The connections which are detected automatically are normally given a generic name, (I dont remember exactly, but it is something like "conn001") so to modify it enter;

set {if necessary}
rename


Dave

[Robert Atkinson · Accepted solution]

Ken, are there any switches with zoning involved?

[Ken USA]

Dave & Robert:

Yes, the MSA did respond back that

*** Connection APGB added successfully ***

The out from "sh dev" shows:

P00>>> show device

dka0.0.0.16.0 DKA0 COMPAQ BD018734a4
dqa0.0.0.13.0 DQA0 COMPAQ CDR-8435
dqb0.0.1.13.0 DQB0 Maxtor 5 3073H4
ewa0.0.0.9.0 EWA0 08-00-2B-86-2D-D0
ewb0.0.0.11.0 EWB0 08-00-2B-86-2E-69
pga0.0.0.14.0 PGA0 WWN 1000-0000-c921-9975
pgb0.0.0.17.0 PGB0 WWN 1000-0000-c92c-1c60
pka0.7.0.16.0 PKA0 SCSI Bus 1D 7
pkb0.7.0.116.0 PKB0 SCSI Bus ID 7

No, there are no switches or zoning involved.

Just FYI, the DS-15 is running OpenVMS 7.3-2. ES-40 has OpenVMS 8.2. I get the same "probing timeout" for both. I currently have DS-15 (7.3-2) connecetd to MSA-1000.

Thanks,
-Ken

[Robert Atkinson]

How have you managed to connect 2 nodes without a switch?

Can you do the CLI> SHOW CONNECTION as well.

[Ken USA]

The nodes aren't connected yet. That we will do later. We will have a cluster of 3 nodes - two ES-40s and one DS-25 - and MSA-1000 connected to a switch. But that will be done next week (as we await for a fiber card for one of the ES-40s).

Here's the output from "show connections" at CLI prompt. The first CPGA is for the first ES-40 we tried. When that gave "probing timeout" error, we disconnected it from MSA-1000 and connected DS-15 to MSA-1000. Connection APGB is from the DS-15 which is still connected to the MSA-1000.

CLI> show connections
Connection Name: CPGA
Host WWNN = 20000000-C9497036
Host WWPN = 10000000-C9497036
Profile Name = OpenVMS
Unit Offset = 0

Connection Name: APGB
Host WWNN = 10000000-C92C1C60
Host WWPN = 10000000-C92C1C60
Profile Name = OpenVMS
Unit offset = 0

(Not sure why but we don't see controller, port & status for these connections).

Thanks,
-Ken

[Robert Atkinson]

From the controller, you should be able to do a SHOW CONN, without having to pre-load it. It will come up as something like NEW-CONNECTION, but showing the WWID of the DS15.

If this is not the case, then I'd look at card compatability, cables, speeds, etc. This can be found at http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00868010/c00868010.pdf

To be honest, this would be much easier with a switch, as it's a lot easier to see what's happening on the port.

[Robert Atkinson]

Might be worth doing a SHOW ACL as well, just to make sure it hasn't been limited already - perhaps it was bought 2nd hand?

Rob.

[Ken USA]

Hi Robert:

Thanks, will check it out.

I have another question and thought will just ask here instead of opening a new thread.

On our old MSA-1000, we had four HP Ultra-32 (15k) SCSI 72.8GB combined as one volume (as follows):

CLI> add unit 1 RAID_LEVEL=0 Data=DISK102-105
CLI> set unit id 1 200

On our old DS-25 that was connected to old MSA-1000, we did the following:

>>> wwidmgr -show wwid
>>> wwidmgr -quickset -udid 200
>>> init
(After booting DS-25, we did the following).
$ INIT/SYSTEM $1$DGA200: USR1-ODS5
$ MOUNT $1$DGA200: USR1-ODS5 CORP_DGA200
$ SET VOLUME/STRUCTURE_LEVEL=5 $1$DGA200:
$ DISMOUNT $1$DGA200:
$!
$ MOUNT/SYSTEM/NOASSIST $1$DGA200: USR1-ODS5 CORP_DGA200

Is there a way to mount these disks on the new ES-40 (it has 6 open slots for disks) so that we can copy our data on to the existing disk (DKA0) on ES-40.

I tried once by inserting all four disks and when the system came up the disks were there with device name DKA200, DKA300, DKA400 & DKA500. Tried mounting and ran into a "Files-11" problem. Did not want to try anything in more in fear of losing the contents.

So, the question is:

How do we mount a set of disks that were mount on a MSA-1000 as one unit on a ES-40 to restore data?

Thanks,
-Ken

[Robert Atkinson]

Ken - according to Step 3 on http://h18000.www1.hp.com/products/quickspecs/11621_na/11621_na.html direct connect isn't supported for dual-redundant configurations.

Again, could be the reason. It's also a good guide on how to connect up your Alpha's.

Rob.

[Robert Atkinson]

> How do we mount a set of disks that were mount on a MSA-1000

This is very much dependent on the Meta Data on the physical disks.

I don't know about the MSA1000, but some SAN's will store the SAN serial number, so if you move disks around, it will refuse the disk without initializing it with the correct SAN serial number first.

The best way to tell is have a look at what the MSA1000 thinks about each unit. If it shows them as configured, without having to override any warnings, then it _should_ present them out without any problems.

On the other hand, if it refuses to use them with initialising first, or complains when you manually configure the units, then it's quite likely that it's unable to access the data.

Although the volume label may be in the correct VBN on the disk, it doesn't necessarily mean the data is also where it should be.

Rob.

[Ken USA]

Hi Rob:

Thanks for all your help and suggestions.

CLI> show acl
ACL is disabled. To enable ACL use 'add acl'.

We are going to use McData (Spheron 4500) fiber switch.

Thanks,
-Ken

[Ken USA]

Hi Robert:

Have both DS-15 and MSA-1000 connected to a McData Fiber Switch.

>>> wwidmgr -show wwid
just returns with
>>>

It does not give "probing timeout" error but then it does nothing too.

Thanks,
-Ken

[Robert Atkinson]

I'm not familiar with that switch, but I'll assume it works like a Brocade.

Log onto it and make sure there's no zoning in place.

Check the port status for each connection, and make sure the switch can see each card.

Once you're happy the switch can see everything, repeat the SHOW CONNECTION from the controller and see if you can see the new WWID's.

Robert.

[EdgarZamora]

On the Alpha console do a wwidmgr -show adapter and make sure your topology is set to fabric.

[Ken USA]

Hi all:

Sorry for replying late as our IT Network expert was out few days.

We now have MSA1000, ES-40 and DS-15 all connected to a McData fibre switch.

Will post another entry here with an update later today.

Thanks.
-Ken

[Ken USA]

Hi all:

It's all working fine now. Our network guru was here. He reset the password for fibre switch and we have MSA1000 and both alphaservers ES-40 and DS-15 connected to the switch.

Was able to "wwidmgr" from alpha.

(Robert - that was it. The Switch!!! Thx).

Thank you all for your help and suggestions.

Will assign points and close the thread.

Thanks.
-Ken

[Ken USA]

The alphaserver and MSA-1000 needed to be connected through a switch. Was trying for a direct connection and it was failing. Appreciate all the help from participants who took time out of their busy schedule to read and reply.

Thanks,
-Ken