- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- New vdisks on EVA4100 not seen by OpenVMS
Disk Enclosures
1748019
Members
4643
Online
108757
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО08-01-2008 11:43 AM
тАО08-01-2008 11:43 AM
New vdisks on EVA4100 not seen by OpenVMS
We just installed & configured new drives on our EVA4100. Before we did this, the vdisks were presented to some Linux machines running VMware.
We've added more disks, created a new group and created new vdisks. We are trying to present some of these vdisks to a OpenVMS machine running on a bl860c blade. We created a VMS Host area on the EVA and added a new host with the FC Adapter Port WWN number being that of the Fibre device(s) on VMS.
After presenting the vdisks, I can't see them on VMS. How should I diagnose this problem?
The FC switch we're using is not zoned.
Ken
We've added more disks, created a new group and created new vdisks. We are trying to present some of these vdisks to a OpenVMS machine running on a bl860c blade. We created a VMS Host area on the EVA and added a new host with the FC Adapter Port WWN number being that of the Fibre device(s) on VMS.
After presenting the vdisks, I can't see them on VMS. How should I diagnose this problem?
The FC switch we're using is not zoned.
Ken
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2008 08:14 PM
тАО08-01-2008 08:14 PM
Re: New vdisks on EVA4100 not seen by OpenVMS
The surest way of knowing that your EVA disk presentation will work is to select the WWID's from the pick list, and not type them, when you create the host entry on the EVA (there are very few cases where you have to type them in). Aside from avoiding a typo, it also insures that the EVA can see the host in question via the zoning (or lack thereof) you have in place, or that you had a back cable someplace.
Assuming you got that far, for OpenVMS you need to make sure you had specfied a unique unit number as part of the presentation step (in addition to the LUN), the host type was specified as OpenVMS (if not, might work anyway), and on the vms side you did the "sysman io autoc" command.
I know there was something about Itanium OpenVMS 8.3 that keeps you from seeeing SAN drives if you are booted locally (or vice versa) that the -1H1 variant fixes. And although it might be a far shot, not having your switch zoned sometimes causes conflicts between hosts of different O/S's- you never go wrong with having a zone for each EVA/array port pair.
good luck.
Assuming you got that far, for OpenVMS you need to make sure you had specfied a unique unit number as part of the presentation step (in addition to the LUN), the host type was specified as OpenVMS (if not, might work anyway), and on the vms side you did the "sysman io autoc" command.
I know there was something about Itanium OpenVMS 8.3 that keeps you from seeeing SAN drives if you are booted locally (or vice versa) that the -1H1 variant fixes. And although it might be a far shot, not having your switch zoned sometimes causes conflicts between hosts of different O/S's- you never go wrong with having a zone for each EVA/array port pair.
good luck.
check out evamgt.wetpaint.com and evamgt google group
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-02-2008 10:49 AM
тАО08-02-2008 10:49 AM
Re: New vdisks on EVA4100 not seen by OpenVMS
> specfied a unique unit number
In Command View EVA, this is the field labelled "OS unit ID:", not the 'LUN address' which is used for individual presentation to a host.
Select a value between 1 and 9999 to get a device name from $1$DGA1: to $1$DGA9999: - of course, it must be unique across all storage arrays that this host has access to.
In Command View EVA, this is the field labelled "OS unit ID:", not the 'LUN address' which is used for individual presentation to a host.
Select a value between 1 and 9999 to get a device name from $1$DGA1: to $1$DGA9999: - of course, it must be unique across all storage arrays that this host has access to.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-06-2008 12:38 PM
тАО08-06-2008 12:38 PM
Re: New vdisks on EVA4100 not seen by OpenVMS
It turned out that the switches were already zoned. Once we remembered the passwords to the switches and were able to start up the Fabric Manager, we were able to add a zone on each switch for the VMS Blade. Once the zones were activated, I was able to see the new vdrives on VMS, initialize them, and mount them.
Ken
Ken
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP