- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Hsv100 lun are not accessable openvms
Disk Enclosures
1753735
Members
4503
Online
108799
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
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
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
02-03-2005 07:37 PM
02-03-2005 07:37 PM
Hsv100 lun are not accessable openvms
Hi ,
I have hsv100 controller in SAN which i can access through command view eva software.one Open vms box is attached to this SAN. Through Command veiw i have creted one Vdisk and presented to VMS host. (os Id is also set uniqly).
On VMS host i ran mc sysman io auto/log
on $ prompt i can see $1$DGAn(n=os id).
till here i didn't face any promblem.
Now when i am trying to mount this device its telling not in file-11 formate . I tried to init this device this is also not happening coming out with "operation incomplete. or volume software is not enable".
let me know if anybody have any clue on it..
Regards
Deepak
I have hsv100 controller in SAN which i can access through command view eva software.one Open vms box is attached to this SAN. Through Command veiw i have creted one Vdisk and presented to VMS host. (os Id is also set uniqly).
On VMS host i ran mc sysman io auto/log
on $ prompt i can see $1$DGAn(n=os id).
till here i didn't face any promblem.
Now when i am trying to mount this device its telling not in file-11 formate . I tried to init this device this is also not happening coming out with "operation incomplete. or volume software is not enable".
let me know if anybody have any clue on it..
Regards
Deepak
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2005 06:17 AM
02-06-2005 06:17 AM
Re: Hsv100 lun are not accessable openvms
Hi,
did you also set the console lun id ?
Thats from the OVMs Platform Kit Install Guide.
The Command View EVA software displays a field for the Console LUN ID on the Initialized
Storage System Properties page.
It is very important that you set the Console LUN ID to a number other than zero. If the
Console LUN ID is not set or is set to zero, the OpenVMS host will not see the controller pair.
After the Console LUN ID is set for a controller pair, you do not have to concern yourself with
it until another controller pair is introduced in the SAN (see Table 2 for an example of how the
Console LUN ID displays).
The Command View EVA software displays a field for the OS Unit ID. This field is required
for OpenVMS host machines.
This is a settable ID field on the virtual disk properties page. The default setting is 0, which
disables the settable ID. To enable the settable ID, you must specify a value between 1 and
32767.
WARNING: It is possible to enter a duplicate Console LUN ID or OS Unit ID number. You
must ensure that the Console LUN ID and OS Unit ID number you enter does not duplicate
one already in use. A duplicate Console LUN ID or OS Unit ID number could allow the
OpenVMS hosts to corrupt data through confusion about LUN identity as well as have the
host not see the controllers.
You need to make the Console LUN ID and OS Unit IDs for OpenVMS hosts uniqueYou need to make the Console LUN ID and OS Unit IDs for OpenVMS hosts unique
throughout the entire SAN, not just the controller subsystem.
Best Regards
Roland
did you also set the console lun id ?
Thats from the OVMs Platform Kit Install Guide.
The Command View EVA software displays a field for the Console LUN ID on the Initialized
Storage System Properties page.
It is very important that you set the Console LUN ID to a number other than zero. If the
Console LUN ID is not set or is set to zero, the OpenVMS host will not see the controller pair.
After the Console LUN ID is set for a controller pair, you do not have to concern yourself with
it until another controller pair is introduced in the SAN (see Table 2 for an example of how the
Console LUN ID displays).
The Command View EVA software displays a field for the OS Unit ID. This field is required
for OpenVMS host machines.
This is a settable ID field on the virtual disk properties page. The default setting is 0, which
disables the settable ID. To enable the settable ID, you must specify a value between 1 and
32767.
WARNING: It is possible to enter a duplicate Console LUN ID or OS Unit ID number. You
must ensure that the Console LUN ID and OS Unit ID number you enter does not duplicate
one already in use. A duplicate Console LUN ID or OS Unit ID number could allow the
OpenVMS hosts to corrupt data through confusion about LUN identity as well as have the
host not see the controllers.
You need to make the Console LUN ID and OS Unit IDs for OpenVMS hosts uniqueYou need to make the Console LUN ID and OS Unit IDs for OpenVMS hosts unique
throughout the entire SAN, not just the controller subsystem.
Best Regards
Roland
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