Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
VSE Management Software Version 4.0 Getting Started Guide > Chapter 6 Command Reference

vseassist(1M)

Version A.01.01.00
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

NAME

vseassist — Help Resolve VSE Management Software Configuration Problems

SYNOPSIS

Path (HP-UX): /opt/vse/bin/vseassist

Path (Windows): install-path\bin\vseassist.exe

vseassist -a [-q] [ -n nodename -g collectionname ]...

vseassist -c [-q]

vseassist { -l -r } [-q] { -n nodename -g collectionname }...

vseassist -s [-q] -h cms

DESCRIPTION

The vseassist command performs a number of checks to identify configuration problems in the Virtual Server Environment (VSE) Management Software. The VSE Management Software runs under HP Systems Insight Manager (SIM). This command checks the software configuration on the HP SIM Central Management Server (CMS), the communication between the CMS and managed systems, and the configuration of the software on managed systems. A summary of results is displayed, and detailed results are written to a log file, along with recommendations for resolving any problems found.

You can execute vseassist from the HP SIM graphical user interface, from the command line on the CMS, or from the command line on a managed system. HP recommends the following diagnostic procedure:

  1. If you have root access to the CMS, execute the following command from the command line:

    # vseassist -a

    This will check the VSE Management Software configuration of the CMS, communication with all systems in the All VSE Resources collection, and the VSE Management Software configuration on those systems. Refer to the summary output and examine the log file for any problems. Follow the resolution steps in the log file to fix any problems that were found.

    Fix problems in the CMS configuration first. You can verify that you have fixed those problems by executing the following command from the CMS command line:

    # vseassist -c

    You can also run this command directly from the HP SIM user interface. From the Diagnose menu, select Troubleshoot VSE Management, then select Check VSE CMS Configuration.

  2. After you have resolved all problems with the CMS configuration, check to see if there are any remaining communication issues with the managed systems. From the CMS command line, specify the HP SIM nodenames or system collection names of your managed systems using the following command:

    # vseassist -l { -n nodename | -g collectionname ...}

    Or, from the HP SIM user interface, select the managed systems, then from the Diagnose menu, select Troubleshoot VSE Management, then select Check VSE CMS to Managed Node Communication.

  3. After you have resolved the communication issues between the CMS and your managed systems, check the VSE Management Software configuration on those systems. From the CMS command line, specify the HP SIM nodenames or system collection names of your managed systems using the following command:

    # vseassist -r { -n nodename | -g collectionname ...}

    Or, from the HP SIM user interface, select the managed systems, then from the Diagnose menu, select Troubleshoot VSE Management, then select Check VSE Managed Node Configuration.

  4. If you are unable to resolve issues with one of your managed systems, you can install or copy vseassist to the managed system and run it from the command line there. In the following command, replace cms with the short hostname or fully qualified domain name of the CMS:

    # vseassist -s -h cms

Options

If no options are specified, the command syntax is displayed and the command exits with return code 3.

The vseassist command recognizes the following options. For each option, a mnemonic is shown in parentheses to help you remember the option letter.

Title not available (Options)

-a

(All) Perform all checks:

  1. Check the VSE Management Software configuration of the CMS (as with the -c option).

  2. Check the communication between the CMS and the specified managed systems (as with the -l option). If no managed systems are specified, then perform this check on all systems in the All VSE Resources collection.

  3. Check the VSE Management Software configuration of the specified managed systems (as with the -r option). If no managed systems are specified, then perform this check on all HP-UX and Microsoft® Windows® systems in the All VSE Resources collection.

-c

(CMS) Check the VSE Management Software configuration of the CMS.

-l

(Link) From the CMS, check the communication between the CMS and the managed systems specified by the -n and -g options. Some of the problems detected with this option include expired licenses, no open WBEM ports, and improperly configured SSH authentication. These checks will verify if the CMS can communicate with the managed systems to perform VSE management functions.

This option requires one or more -n or -g options.

-r

(Remote) From the CMS, check the VSE Management Software configuration of the HP-UX or Windows managed systems specified by the -n and -g options. This option uses mxexec to copy the vseassist command to the managed systems, where it is executed with the -s option.

For the -r option to succeed, the CMS must be able to communicate with the managed systems (as checked by the -l option).

This option requires one or more -n or -g options.

Note: Remote operation is only possible for managed systems running HP-UX or Windows.

-n nodename

(Node) Specifies the name of a VSE managed system, using the node name by which the system is known to the CMS (as reported by mxnode(1M)). Multiple -n and -g options can be used to specify multiple systems.

Note: This command is not designed to diagnose problems with non-VSE resources. Specifying non-VSE resources using -n or -g options will not produce useful results.

-g collectionname

(Group) Specifies the name of a collection of systems known to the CMS. The specified checks will be performed for each of the managed systems in the collection. Multiple -n and -g options can be used to specify multiple systems.

Note: System or collection names that include spaces must be enclosed in quotes.

See mxquery(1M) for more information about collections under HP SIM.

-q

(Quiet) No output will be generated on stdout or stderr. The results will still be logged to the vseassist.log file.

-s

(System) This option is used when running vseassist directly on managed systems. Some of the problems detected with this option include missing WBEM providers, stalled WBEM process, and missing required patches.

When you use vseassist with the -r option on the CMS, mxexec will remotely execute vseassist on the managed systems using the -s option.

-h cms

(Host) Specifies the short hostname or fully qualified domain name of the CMS that is managing the system. This option is passed to the remote execution of vseassist when you use the -r option on the CMS.

Installation

Beginning with VSE Management Software Version A.03.00.00, vseassist is installed on the CMS when the VSE Management Software is installed. For information about updates, known issues, and workarounds, see the HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes and the VSE Management website at http://docs.hp.com/en/vsemgmt/.

RETURN VALUES

Title not available (RETURN VALUES)

0

The command completed successfully and no FAIL results were found.

1

The command completed successfully and one or more FAIL results were found.

2

Warnings, but no FAIL results were found.

3

Incorrect options were specified; the command syntax is displayed.

4

An unexpected internal error occurred. Contact your HP Support Representative, your HP Services Representative, or your authorized HP reseller for assistance.

EXAMPLES

The specific checks performed may vary by operating system and system type of the CMS and managed systems. The following examples show the kind of output that is produced, but the details may be different in your environment.

Check the configuration of a CMS named vsecms:

# vseassist -c
Version: A.04.00.07
+--------------------------------------------------------------+
|         Performing CMS configuration verification            |
+--------------------------------------------------------------+

  vsecms:
    HP SIM running........................................[PASS]
    HP SIM memory configuration...........................[PASS]
    VSE Management software running.......................[PASS]
    Localhost name resolution.............................[PASS]
    VSE manageable systems discovered in HP SIM...........[PASS]
    Application Discovery server running..................[PASS]
    File system free space................................[PASS]
    Java JRE installed....................................[PASS]
    Virtual Machine Management runnning...................[PASS]
    VMM responsive........................................[PASS]
    Virtual Connect Enterprise Manager responsive.........[N/A ]
    Check Logical Server Automation installed.............[PASS]

Result Summary:
   11 verification check(s) performed on 1 system(s)
   11 check(s) passed
    0 check(s) failed
    0 check(s) warned
    1 check(s) not applicable

See log for details:
   C:\Program Files\HP\vse\logs\vseassist.log

Check the communication from the CMS to the managed systems named uxsys and winsys:

# vseassist -l -n uxsys -n winsys
Version: A.04.00.07
+--------------------------------------------------------------+
|Performing link verification of managed system(s) from the CMS|
+--------------------------------------------------------------+

  uxsys.dom.com:
    Managed system hostname resolution....................[PASS]
    WBEM port open........................................[PASS]
    WBEM authentication...................................[PASS]
    SSH port open.........................................[PASS]
    SSH authentication....................................[PASS]
    SNMP server accessibility.............................[PASS]
    Trial or permanent license applied....................[FAIL]
 ISSUE: This system does not have a permanent license (LTU) or
        all of the trial licenses have expired for the following
        products:
          - Virtual Machine Management 
          - Insight Power Manager 
 RESOLUTION: Purchase and apply a permanent LTU for the system
             in order to manage it with the VSE Management
             software.  See the "VSE Management Software Getting
             Started Guide" for information about installing and
             configuring VSE licenses. 
    VMM agent compatibility...............................[N/A ]

  winsys.dom.com:
    Managed system hostname resolution....................[PASS]
    WBEM port open........................................[PASS]
    WBEM authentication...................................[FAIL]
 ISSUE: Unable to either access WBEM credentials in HP SIM for
        winsys.dom.com, or failed to use these credentials to
        make a successful WBEM request to this system.
 RESOLUTION: Make sure valid WBEM credentials have been entered
             in HP SIM for this system, and that the WBEM server
             is running on winsys.dom.com.  Additional
             information about the specific failure is available
             in the vseassist log file.
    SSH port open.........................................[PASS]
    SSH authentication....................................[FAIL]
 ISSUE: The winsys.dom.com node doesn't have the Operating 
        System information available in HP-SIM, which may
        indicate a discovery problem in this node. 
 RESOLUTION: Verify if the WBEM credentials as well as the the
        SSH credentials are properly configured for this node.
        To configure the system credentials go to HP-SIM:
        Options -> Protocol Settings -> System Protocol Settings
    SNMP server accessibility.............................[PASS]
    Trial or permanent license applied....................[PASS]
    VMM agent compatibility...............................[PASS]

Result Summary:
   15 verification check(s) performed on 2 system(s)
   12 check(s) passed
    3 check(s) failed
    0 check(s) warned
    1 check(s) not applicable

System Summary:
  winsys.dom.com: 6 passed, 2 failed, 0 warned, 0 not applicable
  uxsys.dom.com: 6 passed, 1 failed, 0 warned, 1 not applicable

See log for details: C:\Program Files\HP\vse\logs\vseassist.log

Check the configuration of the managed system named uxsys from the CMS:

# vseassist -r -n uxsys
Version: A.04.00.07

+--------------------------------------------------------------+
|       Performing remote managed system(s) verification       |
+--------------------------------------------------------------+

**** Start of output from remote execution of vseassist on
                                           uxsys.dom.com ****
Running tool Execute Remote Vseassist Command with job id 1775.
Task Name       :defRunNowTaskId_1202673463625_9
Job ID          :1775
Tool Name       :Execute Remote Vseassist Command
Job State       :Complete
User Name       :vsecms\Administrator
Execute As User :root
Start Time      :Sunday, February 10, 2008 12:57:43 PM MST
End Time        :Sunday, February 10, 2008 12:58:20 PM MST
Elapsed Time    :36 seconds 656 milliseconds
Node            :uxsys.dom.com
Status          :Complete
Exit Code       :1
Files copied    :2/2
Source          :vsecms.dom.com:
                           C:\Program Files\HP\vse\bin\vseassist
Destination     :uxsys.dom.com:/var/adm/vseassist
Source          :vsecms.dom.com:
                 C:\Program Files\HP\vse\lbin\run_va_and_cleanup
Destination     :uxsys.dom.com:/var/adm/run_va_and_cleanup
STDOUT          :

Version: A.04.00.07
Performing configuration verification of managed system

  uxsys:
    CMS hostname resolution...............................[FAIL]
 ISSUE:    The hostname of the CMS cannot be resolved from this 
           system. 
 RESOLUTION: Verify that your name resolution service is
             configured properly. 
    WBEM running..........................................[PASS]
    WBEM responsive.......................................[PASS]
    System type matches HP SIM system type................[PASS]
    Virtual machine WBEM provider validation..............[PASS]
    nPartition WBEM provider validation...................[PASS]
    Virtual partition WBEM provider validation............[N/A ]
    Utilization Provider validation.......................[PASS]
    Complex name valid....................................[PASS]
    Virtual partition naming conflicts....................[N/A ]
    nPartition name valid.................................[PASS]
    LDAP/WBEM compatibility...............................[PASS]
    Compare CMS and managed system nslookup...............[PASS]
    SSH configuration validation..........................[PASS]
    Application Discovery agent running...................[PASS]
    Managed system required patches installed.............[PASS]
    File system free space................................[PASS]
    Java JRE bundle installed.............................[PASS]
    Fair-Share Scheduler installed........................[PASS]
    Processor Sets installed..............................[PASS]
    gWLM agent configuration..............................[WARN]

  WARNING: This system has the following gWLM agent issue(s):
        -  The gWLM agent bundle is installed but the gWLM agent 
           LTU bundle is not installed.  This is required to use 
           gWLM when the trial license expires. 
 RESOLUTION: Take the following steps to correct these issue(s): 
         -  Install the gWLM agent LTU ('T2762A' bundle) if you 
            plan to manage this system with gWLM.  The latest 
            installation instructions ("VSE Management Software 
            Installation and Update Guide") can be found at 
            http://docs.hp.com/en/vse.html. 
    iCap status...........................................[N/A ]

Result Summary:
   19 verification check(s) performed on 2 system(s)
   17 check(s) passed
    1 check(s) failed
    1 check(s) warned
    3 check(s) not applicable

System Summary:
  : 0 passed, 0 failed, 0 warned, 1 not applicable
  uxsys: 17 passed, 1 failed, 1 warned, 2 not applicable

See log for details: /var/adm/syslog/vseassist.log

**** End of output from remote execution of vseassist on
                                           uxsys.dom.com ****

See log for details: C:\Program Files\HP\vse\logs\vseassist.log

AUTHORS

vseassist was developed by Hewlett-Packard Company.

FILES

Detailed results of the checks performed by vseassist are written to the log file. Examine the log file for recommended steps to resolve any problems found. Note: The log file is not automatically pruned.

HP-UX:

/var/adm/syslog/vseassist.log

Windows:

install-path\logs\vseassist.log

SEE ALSO

VSE Management Software online help

VSE Management manuals from http://docs.hp.com/en/vse.html:

VSE Management Software Version 4.0 Getting Started Guide, VSE Management Software Version 4.0 Installation and Update Guide for HP-UX.

Related manpages:

capcollect(1M), mxexec(1M), mxnode(1M), mxquery(1M), vseinitconfig(1M), vselicense(1M)

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2006-2008 Hewlett-Packard Development Company, L.P.