Difference between revisions of "Configure HMC Consoles for take-over or recovery"
(Created page with "==Background== If you work in an environment where your System-I servers are not physically close by, you might have run into the problem where the Hardware Management Console (...") |
(→Some good news) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Background== | ==Background== | ||
| − | If you work in an environment where your System-I servers are not physically close by, you might have run into the problem where the Hardware Management Console (HMC) drops your connections to the console after a while. The is a major pain if you are in the middle of a 6 hour system save, and has to start all over again if the console drop. Or if a Reclaim Storage (RCLSTG) is running, and the console drop, which may cost you dearly. | + | If you work in an environment where your System-I servers are not physically close by, you might have run into the problem where the Hardware Management Console (HMC) drops your connections to the 5250 remote console after a while. The is a major pain if you are in the middle of a 6 hour system save, and has to start all over again if the console drop. Or if a Reclaim Storage (RCLSTG) is running, and the console drop, which may cost you dearly. |
==Some good news== | ==Some good news== | ||
| − | From V5R3, there is a setting in SST that will allow you to recover the console, or take it over. What essentially happens is that the console stays active on DSP01 (or whatever your console device is), even if the connectivity to the HMC has dropped. See the link at the end of this wiki article on how to enable it. | + | From V5R3, there is a setting in SST that will allow you to recover the console, or take it over. What essentially happens is that the console stays active on DSP01 (or whatever your console device is), even if the connectivity to the HMC has dropped. See the link at the end of this wiki article on how to enable it. You can enable it without doing an IPL, and immediately recover or take over the 5250 console remotely. |
| − | |||
== External links == | == External links == | ||
| − | * [http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/index.jsp?topic=%2Frzajr%2Frzajrconsoletakeoverandrecover. | + | * [http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/index.jsp?topic=%2Frzajr%2Frzajrconsoletakeoverandrecover.htm IBM HMC Recovery Configuration] |
[[Category:Configuration]] | [[Category:Configuration]] | ||
Latest revision as of 14:11, 16 May 2011
Background
If you work in an environment where your System-I servers are not physically close by, you might have run into the problem where the Hardware Management Console (HMC) drops your connections to the 5250 remote console after a while. The is a major pain if you are in the middle of a 6 hour system save, and has to start all over again if the console drop. Or if a Reclaim Storage (RCLSTG) is running, and the console drop, which may cost you dearly.
Some good news
From V5R3, there is a setting in SST that will allow you to recover the console, or take it over. What essentially happens is that the console stays active on DSP01 (or whatever your console device is), even if the connectivity to the HMC has dropped. See the link at the end of this wiki article on how to enable it. You can enable it without doing an IPL, and immediately recover or take over the 5250 console remotely.
