MSA1500 unit not recognized by VMS

Warren Landrum — Thu, 18 Jan 2007 13:35:10 GMT

All,

I've got 3 rx4640's running VMS 8.3. Two MSA1500 pairs, currently in ACTIVE/PASSIVE (fw version 5.10 b414) until I upgrade for ACTIVE/ACTIVE. Servers and Controllers connected to a pair of 4/16 SAN Switches.

I set added unit 0 on 1 of the controllers (controller ID 400) and set the unit id to 0 as follows:

CLI> set unit_id 0 0

and it worked fine.

But then when I went over to VMS and did a

$ MC SYSMAN IO AUTOCONFIG/LOG, it came back and recognized the 4 MSA1500's but told me no identifier was defined for unit D1 as follows. I did not even try to set up a unit D1.

$ mc sysman io autoconfig/log

%SYSMAN-I-OUTPUT, command execution on node PHXIN2
%CALIC-W-MSG, Thu Jan 18 11:24:45 2007 - Computer Associates Licensing -1IXA- Co
mponent not licensed. Please run the appropriate license program to properly lic
ense your product. LRF=1IXA,0000F81B0CC3,DEC_AlphaServer.4100.5/600.8MB_4_*,PHXA
X7,0EN-I-SCSIPOLL, scanning for devices through SCSI port PKA0
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKB0
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port FGA0
%IOGEN-I-CONFIGURED, configured device GGA501
%IOGEN-I-CONFIGURED, configured device GGA401
%IOGEN-E-NODEVID, no identifier defined for device unit D1
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port FGB0
%IOGEN-I-CONFIGURED, configured device GGA500
%IOGEN-I-CONFIGURED, configured device GGA400
%IOGEN-E-NODEVID, no identifier defined for device unit D1
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKC0
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKD0
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port FGC0
%IOGEN-I-CONFIGURED, configured device GGA501
%IOGEN-I-CONFIGURED, configured device GGA401
%IOGEN-E-NODEVID, no identifier defined for device unit D1
%IOGEN-I-FIBREPOLL, scanning for devices through FIBRE port FGD0
%IOGEN-I-CONFIGURED, configured device GGA500
%IOGEN-I-CONFIGURED, configured device GGA400
%IOGEN-E-NODEVID, no identifier defined for device unit D1

Any ideas what I need to do to get the unit recognized as a device by VMS?

Thx,

Warren

ps - What's up with that Computer Associates licensing message? I've got their products installed on the AlphaServer 4100 cluster that I am migrating off of, but that cluster has no physical connectivity to this new Integrity cluster I amsetting up. - w

Re: MSA1500 unit not recognized by VMS

Ian Miller. — Thu, 18 Jan 2007 13:41:25 GMT

RE CA message then see
http://www.openvms.org/stories.php?story=06/12/22/6877349

[was also mentioned in latest newsletter]

Re: MSA1500 unit not recognized by VMS

Uwe Zessin — Fri, 19 Jan 2007 00:49:14 GMT

> CLI> set unit_id 0 0

ID 0 means "no ID". You need to enter a non-zero value.

Re: MSA1500 unit not recognized by VMS

Kris Clippeleyr — Fri, 19 Jan 2007 01:41:14 GMT

Hi,
Having no experience with the MSA1500, but having a number of MSA1000 at hand, I concur with Uwe that a unit with id 0 (zero) is not recognized by VMS. So change it to a non-zero value.
Kris (aka Qkcl)

Re: MSA1500 unit not recognized by VMS

Warren Landrum — Fri, 19 Jan 2007 11:57:04 GMT

Changed unit id to 2. That did it.

Thx,

w

topic Re: MSA1500 unit not recognized by VMS in Operating System - OpenVMS

MSA1500 unit not recognized by VMS

Re: MSA1500 unit not recognized by VMS

Re: MSA1500 unit not recognized by VMS

Re: MSA1500 unit not recognized by VMS

Re: MSA1500 unit not recognized by VMS