HP Matrix Operating Environment Software - Manual (Page 77)

7 Troubleshooting
Verifying the CMS configuration
Insight Orchestration utilizes the vseassist tool and the Systems Insight Manager Diagnose menu
to help you identify and resolve any CMS configuration issues. The Check CMS Configuration
task performs configuration checks on the CMS. To run this task, from the Systems Insight
Manager menu, select Diagnose
→Troubleshoot VSE Management→Check CMS
Configuration . Additionally, when you install Insight Orchestration on the system, a set of
checks related to the Insight Orchestration configuration and resource availability execute to
help you identify any issues with the Insight Orchestration configuration.
IOAssist has its own command line interface. However, IOAssist is primarily used through
vseassist, either through the Systems Insight Manager interface or through the vseassist command
line interface (vseassist -c ). For more information on vseassist, see the vseassist(1M)
manpage and the HP Insight Dynamics help system.
Synopsis
ioassist [–f ] [–o ]
ioassist —g [–f ] [–o ]
ioassist —c [–d] [–f ] [–o ]
Where:
• [–f ] filters the output by levels. Valid entries are ALL, PASS, INFO, WARN, and
FAIL
.
• [–g ] executes checks on a specific group.
• [–d] forces the execution of whole dependency checks (used only with —c).
• [–c ] performs a verification of the check identified by the check identification
number provided.
• [–o ] displays output in a format, DEFAULT or XML.
• [–l ] list the available checks and groups, or checks available for a given group.
• [–h ] Displays help and exits.
Example: Running all checks in CLI
Response:
HP Insight Orchestration Assist tool.
Executing checks
Checking group all
-----------------------------------
Check: HPIO Database Responsiveness
Check: HPIO Database Responsiveness
Result: PASS
Actions:
-----------------------------------
Check: HP SIM Responsiveness
Result: PASS
Actions:
-----------------------------------
Check: HPIO User Groups Configured
Result: WARN
Actions: There are no users in HPIO_Architects group in the CMS. Create a user and assign to HPIO_Architects
group in the users and groups using Windows Computer Management.
(...)
Amount of checks executed: 19
Verifying the CMS configuration 77