- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Disk Numbering Changes - Reboot required ?
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
тАО10-26-2005 12:56 AM
тАО10-26-2005 12:56 AM
Example Case.
I have a shadow set as follows:
DSA1 = DGA100 + DGA300 + DGA400
The disk are HSG80 based disk.
I need to change the disk id for DGA300.
From DGA300 to DGA800.
1) Connect to OpenVMS (sign into System account).
$DISMOUNT $1$DGA400:/CLUSTER
Check removed from shadow set
$SHOW DEV DSA1
2) On HSG80
Find disk id (In this case say D100).
HSG>SHOW D100
HSG>SET D100 ID=800
HSG>SHOW D100
3) On OpenVMS.
From each node in cluster.
$MC SYSMAN IO AUTO
$SHOW DEV DGA800
4) Add back into shadow set ...
$MOUNT DSA1:/SYS/CLUSTER/CONFIRM/SHAD=$1$DGA800: label
....edit script files that reference disk..mountdisk etc..etc...
Will OpenVMS configure disk with a new id after the sysman io auto.
The disk already has a data structure under the old ID (DGA400). Will I get new one for the disk known as DGA800 ?
Or is it reboot time ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 01:07 AM
тАО10-26-2005 01:07 AM
Re: Disk Numbering Changes - Reboot required ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 01:37 AM
тАО10-26-2005 01:37 AM
SolutionI think a reboot sometime convenient would be cleaner, but AFAIK no need to hurry.
And the reboot may be executed as a 'rolling reboot'.
The ONE thing you definitely have to make REAL sure of, is NOT to re-use the old ID (DGA400) for another drive until ALL nodes of the cluster have rebooted!
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 04:20 AM
тАО10-26-2005 04:20 AM
Re: Disk Numbering Changes - Reboot required ?
After you change the ID for each node in the cluster you can delete the old path and reconfigure the new device.
$ MCR SYSMAN IO SCSI_PATH_VERIFY
$ MCR SYSMAN IO AUTOCONFIGURE
No need for a reboot, after all this is VMS.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2005 07:42 AM
тАО10-26-2005 07:42 AM
Re: Disk Numbering Changes - Reboot required ?
you can set the old devices
$SET DEVICE/NOERROR/NOAVAIL
to disable error loging and availability.
Mike