HP Matrix 7.2 KVM Private Cloud Getting Started Guide

7 Troubleshooting
When an operation does not process as expected, the troubleshooting tasks in this section can be
used to help pinpoint the problem. If these troubleshooting tasks do not resolve the problem, see
“HP Support services” (page 46).
IMPORTANT: Should the appliance fail such that it must be reinstalled to work properly, contact
HP technical support services for assistance.
• “Troubleshooting appliance settings” (page 36)
• “Troubleshooting security settings” (page 37)
• “Troubleshooting user settings” (page 38)
• “Troubleshooting IP addresses” (page 38)
• “Troubleshooting images” (page 39)
• “Troubleshooting virtual machine instances” (page 41)
• “Troubleshooting virtual machine hosts” (page 43)
Troubleshooting appliance settings
These sections describe a behavior you might encounter and provide suggested actions you can
take.
You cannot log in
Apply the recommendations that pertain to your situation.
Possible cause and recommendationSymptom
Appliance not yet started or browser not behaving correctly
There is no login
screen.
1. Wait for the appliance to start completely.
2. Refresh your browser and try again.
3. Open a new browser and try again.
4. As Infrastructure Administrator, restart the appliance and try again.
Invalid authentication
There is a login
screen, but the
1. Retype your login name and password in case you made an error.
appliance rejects your
login.
2. Verify your login name and your group and role settings with the Infrastructure Administrator.
If the appliance was reset to its original factory settings, the Infrastructure Administrator
might need to reinstate you.
3. As Infrastructure Administrator, restart the appliance and try again.
Appliance cannot access the network
Possible cause and recommendationSymptom
Appliance network not properly configured
Appliance cannot
access network
1. Minimum required privileges: Infrastructure Administrator
2. Verify that the IP address assignment is correct.
3. Verify that the DNS IP address is correct.
4. Verify that the DNS server is up.
36 Troubleshooting