Hp Matrix Operating Environment Software Manuale Utente Pagina 179
- Pagina / 209
- Indice
- RISOLUZIONE PROBLEMI
- SEGNALIBRI
Valutato. / 5. Basato su recensioni clienti
HP Matrix infrastructure orchestration service may not start automatically after a system restart with
error Unable to retrieve database password from mxpassword
HP Matrix infrastructure orchestration service may not start automatically after a system restart. The
following error is displayed: Unable to retrieve HPIO's database password from
mxpassword.
Issue
When the CMS is under a high usage (mostly during services startup), the Systems Insight Manager
mxpassword command can take more than one minute to return, causing a failure during
infrastructure orchestration startup pre-conditions checking.
Possible cause
Perform one of the following actions.Action
• Manually start the HP Matrix infrastructure orchestration service after other services have
completed startup.
• Increase the timeout and the number of attempts performed by IO to retrieve the required
information. Increase the following properties in ..\Matrix infrastructure
orchestration\conf\hpio.properties
◦ launcher.mxpasswd.retry.count
Number of times that IO executes the mxpassword command if it fails. Default is 6.
◦ launcher.mxpasswd.retry.timeout
Time, in seconds, between each attempt. Default is 30 seconds.
CMS crash recovery
Create Service request does not complete successfully after CMS crash recovery
Create Service request does not complete successfully when resumed after CMS is recovered from
a crash. Manual steps recommended by IO are inadequate to recover the logical server and re-issue
the request successfully.
Issue
VCEM and Virtual Connect Manager (VCM) are out of sync due to a CMS crash that occurred
while assigning a server profile.
Possible cause
Action
• Perform VC Domain maintenance. See HP Virtual Connect Enterprise Manager User Guide for
more information.
• Delete the clean-me-<LS>logical server for any that are listed.
• Move the blade from Maintenance to another server pool which frees up the server IP address
and marks the blade as available.
• Re-issue the infrastructure orchestration Create Service request.
Deactivate physical server does not complete successfully after CMS crash recovery
Deactivate physical server does not complete successfully when resumed after CMS is recovered
from a crash. Manual steps recommended by IO are inadequate to recover the logical server and
re-issue the request successfully.
Issue
VCEM and VCM are out of sync due to a CMS crash that occurred while unassigning a server
profile.
Possible cause
Action
• Perform maintenance of the VC Domain Group in VCEM, which unassigns the server profile.
See HP Virtual Connect Enterprise Manager User Guide for more information.
• Move the logical server from Maintenance to another server pool. This frees up the server IP
address and marks the blade as available.
• Activate the server from logical server management.
• Re-issue the infrastructure orchestration Deactivate request.
Miscellaneous issues 179
- Abstract 1
- Contents 3
- 4 Contents 4
- Contents 5 5
- 6 Contents 6
- Contents 7 7
- 8 Contents 8
- Contents 9 9
- 1 Introduction 10
- 12 Introduction 12
- API and CLI support 13
- Configuring a federation 19
- Configuring Ignite-UX 33
- Default memory setting 35
- VMware cluster considerations 51
- Verifying VC domain groups 52
- ◦ Hyper-V: virtual switches 54
- Trunk and VLAN networks 56
- Configuring pools 62
- Creating a pool 64
- <ooServers> 69
- Designer interface overview 76
- Accessing the console 77
- Console interface overview 77
- Enabling telnet for Firefox 79
- Create service operation 85
- Delete service operation 86
- Add server to group operation 86
- To add a data disk 87
- To activate servers 88
- To deactivate servers 88
- Power on servers 89
- Power off servers 89
- Power cycle servers 89
- Change lease operation 90
- Creating a service request 113
- Managing new logical servers 118
- Automated allocation 119
- Billing code for services 121
- ◦ SPM is not configured 125
- Manual storage provisioning 126
- Dynamic SAN volume automation 126
- Creating storage tags 130
- Physical storage provisioning 136
- Virtual storage provisioning 138
- Overview 141
- ◦ Service provider architect 142
- ◦ Service provider user 142
- Access to resources 142
- Information security 143
- Creating an organization 144
- 4. Click Save 147
- 7 Troubleshooting 148
- Service creation 150
- Completed – Inoperable” 153
- Virtual service creation 158
- Service deletion 165
- A delete request failed 166
- Adding servers to services 167
- Console operations 168
- Designer operations 174
- Miscellaneous issues 177
- Operations Orchestration 178
- CMS crash recovery 179
- Log files 180
- Corrective procedures 181
- 182 Troubleshooting 182
- Corrective procedures 183 183
- 184 Troubleshooting 184
- Corrective procedures 185 185
- Correcting a checksum error 186
- Corrective procedures 187 187
- 188 Troubleshooting 188
- Corrective procedures 189 189
- 190 Troubleshooting 190
- 8 Support and other resources 191
- HP authorized resellers 192
- Documentation feedback 192
- Related information 193
- Glossary 194
- 196 Glossary 196
- Customizing existing rules 199
- Writing a new rule file 200
- Deploying rules 201
- 206 Index 206
- 208 Index 208
Prodotti e manuali riguardandi Software Hp Matrix Operating Environment Software
Software Hp ROM-Based Setup Utility Manuale Utente
(221 pagine)
(221 pagine)
Software Hp Smart Update Manager Manuale Utente
(77 pagine)
(77 pagine)
(125 pagine)
Software Hp Smart Update Manager Manuale Utente
(103 pagine)
(103 pagine)
© 2020, manymanuals.it. Tutti i diritti riservati | 0.028 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commenti su questo manuale