Hp Matrix Operating Environment Software Manual de usuario Pagina 150
- Pagina / 209
- Tabla de contenidos
- SOLUCIÓN DE PROBLEMAS
- MARCADORES
Valorado. / 5. Basado en revisión del cliente
• FAIL—A serious configuration problem was found, which must be resolved for correct operation.
• WARN—A configuration problem was found. The problem may not necessarily prevent correct
operation, but it may limit or restrict operation of some features.
• N/A—Not Applicable: the check does not apply to this type of system.
IOAssist execution timeout
A check in ioassist failed to communicate with infrastructure orchestration, generating a
TimeoutException.
Issue
There was a delay in virtual machine management responding with VM Host details.
The default timeout value for each IOAssist check is two minutes. A timeout indicates that the verified
component (infrastructure orchestration, its subsystem or partner) either is not responding or is
unavailable, or is responding in an undesirable response time.
Possible cause
If IOAssist times out, assume that the component is not responding in the expected response time.
Do not assume that the component is unavailable. Any other conclusion is indicated by IOAssist
error messages.
Choose one of the following:Action
• In ..\Program Files\HP\Matrix infrastructure orchestration\conf\
ioassist.properties, set timeout.await to a value greater than 120 seconds.
• In a Windows Command Prompt, execute the ioassist command line.
Manually enabling federated CMS
A federated CMS environment contains one primary CMS running infrastructure orchestration, and
one or more secondary CMSs running Matrix OE.
Matrix infrastructure orchestration federated CMS is enabled by default during new installations.
At the end of a new installation, the Insight Management installer displays:
Issue
Warning — HP Matrix infrastructure orchestration was successfully installed but the federated CMS
feature was not enabled. Refer to the HP Matrix infrastructure orchestration User Guide for information
about how to enable federated CMS.
The CMS IP address cannot be correctly resolved to the CMS FQDN during installation, so the
Installer adds the CMS IP address to the managed_cms_list property. However, the
managed_cms_list must be configured with the CMS FQDN.
Possible cause
In a federated CMS environment, forward DNS lookups resolve CMS hostnames to IP addresses.
Additionally, on the primary CMS, forward and reverse DNS lookups must resolve for each secondary
CMS.
Action
1. Verify that all DNS lookups can be resolved using the FQDN of each system.
2. Enable federated CMS manually. See “Configuring a federated CMS environment” (page 18)
and the HP Matrix Operating Environment Federated CMS Overview white paper at Matrix
Operating Environment Information Library for detailed information.
Service creation
Physical service creation
Unable to allocate servers and networks in the same Virtual Connect Domain Group
Unable to allocate servers and networks in the same Virtual Connect
Domain Group. Either more available servers are required, or could not
Failure message
150 Troubleshooting
- 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
Relacionado con productos y manuales para Software Hp Matrix Operating Environment Software
Software Hp ROM-Based Setup Utility Manual de usuario
(221 paginas)
(221 paginas)
Software Hp Smart Update Manager Manual de usuario
(77 paginas)
(77 paginas)
(125 paginas)
Software Hp Smart Update Manager Manual de usuario
(103 paginas)
(103 paginas)
© 2020, manymanuals.es. Todos los derechos reservados | 0.061 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentarios a estos manuales