- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: SAN DISK Identification process
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
тАО12-08-2005 02:58 AM
тАО12-08-2005 02:58 AM
Re: SAN DISK Identification process
That is the only thing I can think of that I know is an issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2007 03:12 AM
тАО03-27-2007 03:12 AM
Re: SAN DISK Identification process
thanks
david
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2007 05:37 AM
тАО03-27-2007 05:37 AM
Re: SAN DISK Identification process
$ mc sysman io scsi
$ mc sysman io auto/log
If I don't do the "io scsi_verify" before, sometimes it does not pick up the new devices. However, if I do, then as long as I have remembered to present a non-zero O/S unit id, then the above sequence works.
Did you do both (even though you didn't unpresent any devices)?
This was with EVA6000 with latest (as of Feb, 2007) firmware/CV software, and ES47 with VMS 8.3 Factory Installed AVMS83R1.
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-27-2007 05:42 AM
тАО03-27-2007 05:42 AM
Re: SAN DISK Identification process
Maybe a question you already know, but are all the areas on the switches open for the OpenVMS system to see the SAN ?
It looks like there is a breach somewere.
Are connections switched, are groups on the switch changed, is the systemname still the systemname (for the switch) ?
Are on the SAN the securitys correct ?
AvR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2008 04:38 AM
тАО09-05-2008 04:38 AM
Re: SAN DISK Identification process
Our 'old' storage is HP EMA12000 and each shelf of 14 drives is seen as a different SCSI channel. I wonder how EVA handles this as that was the second choice to the SVC based storage (DS4800 controllers).
Thanks,
Bill Brown
St Jude Children's Res Hospital
Memphis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2008 05:03 AM
тАО09-05-2008 05:03 AM
Re: SAN DISK Identification process
The EVA has a Fibre Channel Arbitrated Loop (FC_AL) back-end.
Every disk drive is dual-ported and connects to a loop pair. The EVA5000 + 8000 have two loop pairs - all others have one loop pair.
Depending on the size and age of the model, there is a 'loop switch' in the back-end so that the controllers and disk enclosures are connected in a 'star topology'.
The latest models even use small 'cut-through switches' (CTS) in their disk enclosures.
But this is nothing what the server sees. At the front-end, the EVA looks much like a HSG in SCSI-3 mode (controller device at LUN address 0), except that today's models run in (asymetrical) active/active mode.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2008 02:19 PM
тАО09-05-2008 02:19 PM
Re: SAN DISK Identification process
Thanks,
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2008 03:49 AM
тАО09-08-2008 03:49 AM
Re: SAN DISK Identification process
MCR SYS$ETC:FC$CP FGA 2 1 8
worked for me with ds20 vms v7.3-1 , v7 firmware and ibm svc and ds8000.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2008 03:50 AM
тАО09-08-2008 03:50 AM
Re: SAN DISK Identification process
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2008 05:13 AM
тАО09-08-2008 05:13 AM
Re: SAN DISK Identification process
try running this
MCR SYS$ETC:FC$CP FGA 2 1 8
worked for me with ds20 vms v7.3-1 , v7 firmware and ibm svc and ds8000.
Is that 2 space 1 space 8 ? Did not show up ver well in the answer on the forum. Looks more like that now since I pasted it in.
BTW, I booted one of our DR nodes in this development cluster Saturday night. At boot (probably after the INIT) and coming back up on VMS the system saw the disks past 0 - 15 LUN...but after that I still could not add more disks with IO Auto.
I then went to another single node cluster system on OpenVMS 8.3 and added LUN 23 without problem. Scanning the FC shows LUN 23 on this 8.3 system where the 7.3-2 system still tops out showing 0-15 even though additional disks are recognized above that after a boot.
We will be upgrading our systems to 8.3 over the next couple of months, but want to have the SVC storage in first :-).
Thanks all