HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: CPU Migration
Operating System - OpenVMS
1829936
Members
2808
Online
109998
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
Forums
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
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
07-27-2009 08:32 PM
07-27-2009 08:32 PM
CPU Migration
Hi,
I have a ES47 server with Openvms 7.3-2 it has 1 hard partion and 2 soft partitions. I tried to migrate a cpu from 1 partion to another partion using SET CPU/MIGRATE command and the cpu leaves from the soruce to destn but it goes to "Timeout" state in the dstn system hence its is not usable. Later when I power off both partions followed by a reboot it comes to RUN state in original partition without any issues. Is there any way to overcome this situvation or is there any way to migrate the CPU from 1 soft partion to another soft partion from MBM if yes please let me know the steps.
I have a ES47 server with Openvms 7.3-2 it has 1 hard partion and 2 soft partitions. I tried to migrate a cpu from 1 partion to another partion using SET CPU/MIGRATE command and the cpu leaves from the soruce to destn but it goes to "Timeout" state in the dstn system hence its is not usable. Later when I power off both partions followed by a reboot it comes to RUN state in original partition without any issues. Is there any way to overcome this situvation or is there any way to migrate the CPU from 1 soft partion to another soft partion from MBM if yes please let me know the steps.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2009 08:36 AM
07-28-2009 08:36 AM
Re: CPU Migration
What are your licensed units for each instance?
2.4 OpenVMS Galaxy License Enforcement
In an OpenVMS Galaxy computing environment, the OPENVMS-GALAXY license units are checked during system startup and whenever a CPU reassignment between instances occurs.
If you attempt to start a CPU and there are insufficient OPENVMS-GALAXY license units to support it, the CPU will remain in the instance's configured set but it will be stopped. You can subsequently load the appropriate license units and start the stopped CPU while the system is running. This is true of one or more CPUs.
Steps are in here:
http://h71000.www7.hp.com/doc/732final/aa-rezqe-te/aa-rezqe-te.pdf
hth
2.4 OpenVMS Galaxy License Enforcement
In an OpenVMS Galaxy computing environment, the OPENVMS-GALAXY license units are checked during system startup and whenever a CPU reassignment between instances occurs.
If you attempt to start a CPU and there are insufficient OPENVMS-GALAXY license units to support it, the CPU will remain in the instance's configured set but it will be stopped. You can subsequently load the appropriate license units and start the stopped CPU while the system is running. This is true of one or more CPUs.
Steps are in here:
http://h71000.www7.hp.com/doc/732final/aa-rezqe-te/aa-rezqe-te.pdf
hth
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP