topic Re: OpenVMS and SMA1000 in Operating System - OpenVMS

OpenVMS and SMA1000

D Kobus — Thu, 06 Apr 2006 15:22:00 GMT

I have the following configuration;

DS-15 Alpha Server

OpenVMS 8.2
FCA 2684 (DS-A5132-AA - 2GB, 64-bit/133Mhz PCI-X) Native, FW 1.91a1

MSA1000
FW 4.48

4 LUN's presented to host

The issue is that if I reboot the DS15 I lose the LUN's and have to manually attach to them.

Shouldnt the system be able to find and mount these without intervention?

Thanks for any help,

Re: OpenVMS and SMA1000

Volker Halle — Fri, 07 Apr 2006 00:46:45 GMT

Hi,

welcome to the OpenVMS ITRC forum.

During normal OpenVMS startup, all devices will be autoconfigured automatically using SYSMAN IO AUTOCONFIG. This operation should find and configure devices on your MSA1000.

What exactly do you have done to 'manually attach them' ?

Autoconfiguration could have been prevented by STARTUP$AUTOCONFIGURE_ALL == 0 in SYS$MANAGER:SYCONFIG.COM and would also not happen, if STARTUP_P1 is set to anything but "" (minimum boot).

Volker.

Re: OpenVMS and SMA1000

Jeroen Bleeker_2 — Fri, 07 Apr 2006 01:58:27 GMT

In the console you have to define all the available paths for the boot device with " set bootdef_dev ,".
If that is the the problem you can get more information in the WWIDMGR Users Manual.

Jeroen Bleeker

Re: OpenVMS and SMA1000

Vladimir Fabecic — Fri, 07 Apr 2006 05:07:59 GMT

Can you, please post more details. Do you have problem with booting or after the boot process?

Re: OpenVMS and SMA1000

D Kobus — Fri, 07 Apr 2006 08:07:22 GMT

This is happening during the boot process.

I'm not on site with the engineer so I have to work as a medium.

If more information is needed please let me know what info would help resolve this.

The client has moved there windows servers from the MSA1000 to a EVA and this engineer Inherited the MSA for his VMS servers.

I support the ESSI East storage team and none of us have incountered this issue.

Re: OpenVMS and SMA1000

Volker Halle — Fri, 07 Apr 2006 08:11:32 GMT

Does the system (try to) boot from a MSA1000 drive and that fails (error message ?)

or does the system boot from a local disk and fails to configure the MSA1000 disk ($1$DGAx) ?

Volker.

Re: OpenVMS and SMA1000

Vladimir Fabecic — Fri, 07 Apr 2006 08:15:52 GMT

OK
I would be interesting for output of the following after shutdown:
Halt the machine to prevent autoboot
>>> init
>>> wwidmgr -show wwid -full

Also output of VMS command:
$ show dev/multi
$ product show history

Regards

Re: OpenVMS and SMA1000

D Kobus — Fri, 07 Apr 2006 08:19:15 GMT

No boot from SAN, Boot from local disk and fails to mount the disks presented to the MSA1000,

I have verifed the MSA1000 configuration and the switches.

Info provided by the client;

The Alpha is able to see the drives at the >>>. But when the alpha is booted it can not see the drives or the controller. The alpha is a DS15. The fibre cards are in slot 3 & 4.

CLI> show version
Firmware version: 4.48 build 342
Hardware Revision: 7 [AutoRev: 0x010000]
Internal EMU Rev: 1.86 (USZ0416BGD)

CLI> show disks
box,bay bus,ID Size Speed Units
Disk101 1,01 0,00 36.4 GB 160 MB/s 0
Disk102 1,02 0,01 36.4 GB 160 MB/s 1
Disk103 1,03 0,02 36.4 GB 160 MB/s 1
Disk104 1,04 0,03 36.4 GB 160 MB/s 1
Disk111 1,11 1,03 36.4 GB 160 MB/s 1
Disk112 1,12 1,04 36.4 GB 160 MB/s 1
Disk113 1,13 1,05 36.4 GB 160 MB/s 1 (spare)
Disk114 1,14 1,08 36.4 GB 160 MB/s 0

Notes:
The speed is the currently negotiated speed to the disk. This may
be less than the maximum speed supported by the device due to bus
faults, loss of signal integrity, etc.

CLI> showunits
Invalid CLI command.

CLI> show units

Unit 0:
In PDLA mode, Unit 0 is Lun 1; In VSA mode, Unit 0 is Lun 0.
Unit Identifier : ops
Device Identifier : 600805F3-000DDFB0-571A9D01-706E000E
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Mirror Init Status: waiting for first write
2 Data Disk(s) used by lun 0:
Disk101: Box 1, Bay 01, (SCSI bus 0, SCSI id 0)
Disk114: Box 1, Bay 14, (SCSI bus 1, SCSI id 8)
Spare Disk(s) used by lun 0:
No spare drive is designated.
Logical Volume Raid Level: MIRROR FAULT TOLERANCE (Raid 1)
stripe_size=128kB
Logical Volume Capacity : 34,726MB

Unit 1:
In PDLA mode, Unit 1 is Lun 2; In VSA mode, Unit 1 is Lun 1.
Unit Identifier : Data
Device Identifier : 600805F3-000DDFB0-5B73234C-8663000F
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Parity Init Status: waiting for first write
5 Data Disk(s) used by lun 1:
Disk102: Box 1, Bay 02, (SCSI bus 0, SCSI id 1)
Disk103: Box 1, Bay 03, (SCSI bus 0, SCSI id 2)
Disk104: Box 1, Bay 04, (SCSI bus 0, SCSI id 3)
Disk111: Box 1, Bay 11, (SCSI bus 1, SCSI id 3)
Disk112: Box 1, Bay 12, (SCSI bus 1, SCSI id 4)
Spare Disk(s) used by lun 1:
Disk113: Box 1, Bay 13, (SCSI bus 1, SCSI id 5)
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5)
stripe_size=16kB
Logical Volume Capacity : 138,921MB

CLI> show connections

Connection Name: botpga
Host WWNN = 20000000-C94AA842
Host WWPN = 10000000-C94AA842
Profile Name = OpenVMS
Unit Offset = 0
Controller 2 Port 1 Status = Online

Connection Name: toppga
Host WWNN = 20000000-C94AA839
Host WWPN = 10000000-C94AA839
Profile Name = OpenVMS
Unit Offset = 0
Controller 2 Port 1 Status = Online

Connection Name: botpgb
Host WWNN = 20000000-C94AA834
Host WWPN = 10000000-C94AA834
Profile Name = OpenVMS
Unit Offset = 0
Controller 1 Port 1 Status = Online

Connection Name: toppgb
Host WWNN = 20000000-C94AAAAB
Host WWPN = 10000000-C94AAAAB
Profile Name = OpenVMS
Unit Offset = 0
Controller 1 Port 1 Status = Online
show oster_controller
Invalid CLI command.

CLI> show other_controller
Controller:
MSA1000(c) Compaq P56350FX3PZ04W Software 4.48 Build 342 Hardware 7
Controller Identifier:
NODE_ID = 500805F3-000DDFB0
SCSI_VERSION = SCSI-3
Supported Redundancy Mode: Active/Standby
Current Redundancy Mode: Active/Standby
Current Role: Active
Device Port SCSI address 6
Terminal speed for the CLI is set to 19200.
Host Port_1:
REPORTED PORT_ID 500805F3-000DDFB1
PORT_1_TOPOLOGY = F_Port
Cache:
128 megabyte read cache 128 megabyte write cache Version 2
Cache is GOOD, and Cache is enabled.
No unflushed data in cache
Battery:
Module #1 is fully charged and turned off.
Controller Up Time:
3 Days 20 Hours 31 Minutes 17 Seconds

CLI> show other_controller_id
Invalid CLI command.

Re: OpenVMS and SMA1000

Volker Halle — Fri, 07 Apr 2006 08:36:41 GMT

The Unit Identifier seems to be the problem. OpenVMS required decimal numbers and it looks like this MSA1000 uses strings.

See http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=878721

CLI> set unit_id 0 101
Device identifier 101 created.

This will result in device $1$DGA101: on OpenVMS.

Volker.