- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: can I exclude DGA devices from SYSMAN IO AUTO?
Operating System - OpenVMS
1753876
Members
7490
Online
108809
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
Go to solution
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
04-11-2007 05:54 AM
04-11-2007 05:54 AM
Re: can I exclude DGA devices from SYSMAN IO AUTO?
@Jon:
> Can a laptop with a terminal emulator be included in the "spare"
> setup? If so, key parts of the node-specific cookbook can be
> there to cut'n paste into the SRM console, but also it would be
> possible to connect to the HSG80 consoles and change the
> presentations to the "spares" WWID. Then the spare would see
> only the disks that the original systems saw.
We discussed this option, but fiddling with the HSG80 configuration was deemed too dangerous in emergency situations.
> You will still have a good bit of work making your startup
> smart enough to adapt to different device names, etc, and make
> sure you use logical names for things like tape devices, etc.
We already achieved this with minor modifications of the existing systems (e.g. putting a SCSI adapter into a different PCI slot or swapping a DE500 for a DE602 to make device names match) and making the spare system sort of a "superset" of the individual configurations, especially with respect to network cards.
> Alternatively [...] the spare system [...] could communicate
> with the HSG80 then that system could have a script that could
> configure the HSG80's presentations, [...]
This sounds like a creative solution as no manual intervention is involved regarding the HSG80s, but it also sounds like *much* more work than setting the unwanted devices to /NOAVAIL. However, I'll keep it in mind...
> [...] it should be easy to have the spare system always set
> all $1$DGA devices that weren't in it's "range" to /noavailable
> in the system startup, before any accidents could occur.
This will be the final setup, probably. Each system "knows" which devices it needs, and as the spare system boots from the system disk of the system it is replacing, setting the rest /NOAVAILABLE should be straight forward.
Thanks for your ideas,
Hans.
> Can a laptop with a terminal emulator be included in the "spare"
> setup? If so, key parts of the node-specific cookbook can be
> there to cut'n paste into the SRM console, but also it would be
> possible to connect to the HSG80 consoles and change the
> presentations to the "spares" WWID. Then the spare would see
> only the disks that the original systems saw.
We discussed this option, but fiddling with the HSG80 configuration was deemed too dangerous in emergency situations.
> You will still have a good bit of work making your startup
> smart enough to adapt to different device names, etc, and make
> sure you use logical names for things like tape devices, etc.
We already achieved this with minor modifications of the existing systems (e.g. putting a SCSI adapter into a different PCI slot or swapping a DE500 for a DE602 to make device names match) and making the spare system sort of a "superset" of the individual configurations, especially with respect to network cards.
> Alternatively [...] the spare system [...] could communicate
> with the HSG80 then that system could have a script that could
> configure the HSG80's presentations, [...]
This sounds like a creative solution as no manual intervention is involved regarding the HSG80s, but it also sounds like *much* more work than setting the unwanted devices to /NOAVAIL. However, I'll keep it in mind...
> [...] it should be easy to have the spare system always set
> all $1$DGA devices that weren't in it's "range" to /noavailable
> in the system startup, before any accidents could occur.
This will be the final setup, probably. Each system "knows" which devices it needs, and as the spare system boots from the system disk of the system it is replacing, setting the rest /NOAVAILABLE should be straight forward.
Thanks for your ideas,
Hans.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2007 05:57 AM
04-11-2007 05:57 AM
Re: can I exclude DGA devices from SYSMAN IO AUTO?
Thanks for the confirmation that DGA devices can't be excluded from SYSMAN IO AUTO in any way. I'll follow plan B and set the unneeded devices to /NOAVAILABLE.
Hans.
Hans.
- « Previous
-
- 1
- 2
- Next »
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