- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: MSA1000 on VMS
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2005 11:19 PM
тАО04-25-2005 11:19 PM
Cheers
Chris Smith
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2005 12:48 AM
тАО04-26-2005 12:48 AM
Re: MSA1000 on VMS
first thing I would check is whether the Connection profile is set to OpenVMS:
CLI> show connections
Connection Name: xyz_PGA0
___Host WWNN = 20000000-C9382xyz
___Host WWPN = 10000000-C9382xyz
___Profile Name = OpenVMS
___Unit Offset = 0
___Controller 1 Port 1 Status = Online
::one line
CLI> add connection abc_PGB0 WWPN=10000000-C9380abc profile=openvms
::one line
Connection has been added successfully.
Profile openvms is set for the new connection.
CLI>
You're right that you only configure a console device with WWIDMGR for boot and dump purpose, but not for all disks (there isn't even enough space to configure more than 4 LUNs...).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2005 03:40 AM
тАО04-26-2005 03:40 AM
Re: MSA1000 on VMS
I have been told that the boot device must be dga0: otherwise the 2nd drive will not be visible. Is that the case?
Cheers, Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2005 04:06 AM
тАО04-26-2005 04:06 AM
SolutionIs there a chance that the second logical disk is larger than 1 TeraByte
(>= 2^31 blocks)? Unfortunately, that doesn't work on OpenVMS :-(
Otherwise, you really need a certain patch level on OpenVMS so that it works with the latest firmware revision on the MSA1000.
And no, you have been told wrong. I have implemented several OpenVMS systems that boot from devices other than DGA0: (one is a cluster that boots from DGA101:) and they happily detect the remaining devices.
You might have to assign identifiers to the controllers, too - the documentation in this area I have seen so far is conflicting. Some says you need it - some says not needed.
If I recall correctly, the command is:
CLI> set this_controller_id 201
CLI> set other_controller_id 202
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2005 04:29 AM
тАО04-26-2005 04:29 AM
Re: MSA1000 on VMS
OK, so I don't have to reconfigure the boot drive to DGA0: Thanks. But, yes the other drive is 7 * 300GB in RAID 5 so approx 6 * 300GB or 1.8TB. Someone else suggested that as the drive had not be written to by the time I issued the init command, the actual initialisation of the RAID set would take quite a long time and that if I was to try it again now it could be completed and I wouldn't see the problem. I can't get along to the site until Thursday morning so I can't test that theory very easily.
Likewise your thoughts on controller ids.
I'll look out the patches. I've already had to apply 4 patches for the fibre HBA
vms732_pcsi-v0100
vms732_update-v0300
vms732_sys-v0700
vms732_fibre_scsi-v0400
(in that order) with rebbots after the 2nd, 3rd & 4th patches.
I will report back any progress after my site visit on Thursday.
Cheers
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2005 04:38 AM
тАО04-26-2005 04:38 AM
Re: MSA1000 on VMS
as Uwe expected and you confirmed: the RAID set is simply to big. NO way to get it working!
You will _HAVE_ to split it up into units of < 1 T.
Yes, it is about time for Engeneering to find some clever way to lift another never-expected limit!
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2005 04:39 AM
тАО04-26-2005 04:39 AM
Re: MSA1000 on VMS
Yes, that's too large for OpenVMS. You can, however, keep the disk array and create _two_ logical disks on those 7 physical disks, each about 900 GigaBytes. Then you could create a multivolume set on OpenVMS. The parity initialization should not affect the ability to write on the logical disk. It is rather the opposite: the MSA1000 is waiting for a first write from the host before it starts the initialization!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2005 02:57 PM
тАО04-26-2005 02:57 PM
Re: MSA1000 on VMS
Yes, it is about time for Engeneering to find some clever way to lift another never-expected limit!
It's not likely to happen unless a fair number of customer complain, and state *why* they must have logical volumes larger than 1TB.
It would be a very big project, and it's not clear to product management that it's a worthwhile thing to do -- there are a lot of interesting projects, and don't have the staffing to do everything. As of now, the feeling is that 1TB is sufficient.
If you disagree, please make an official plea to your support centres! Posting notes in public fora like here and comp.os.vms does not help; these places are not viewed with
any regularity by product management.
Your voices on this matter count more than ours!
-- Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2005 09:26 PM
тАО04-26-2005 09:26 PM
Re: MSA1000 on VMS
thanks for your explanation.
From my (our) perspective, the 1 T is not now a problem, since we do not, and do not intend, to bind disks into big RAID sets.
But, looking at the real world around us with some extrapolation into the future should also be done sometimes by Engeneering.
Look at the figures for the biggest available _SINGLE_ disks in recent years. And place your bet at the date when THAT number will pass 1 T...
By that time, it would be very desirable for the whole VMS community if those devices were not ruled out!
Proost.
Have one ion me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2005 11:12 PM
тАО04-27-2005 11:12 PM
Re: MSA1000 on VMS
Thanks again & cheers,
Chris