vseassist Troubleshooting Utility

Limitations

• vseassist does not provide Managed Node Configuration checks for Linux managed systems. (vseassist does provide CMS to Managed Node Communication checks however.)

• vseassist is not localized, so all text displayed by the tool will be in English. The vseassist(1M) manpage installed on the system is also only provided in English.

  	NOTE: The help for VSE is localized. A localized version of the vseassist(1M) manpage can be found by selecting the “VSE Management Software - Command Reference” topic. Then click on the link labeled “vseassist(1M) (PDF)” to view a PDF version of the localized manpage.

Minor Issues

• When running vseassist communication checks between the CMS and managed system, the License check should look for VCEM licenses for ProLiant blades, but it does not. A Proliant blade is considered to be licensed for VCEM if the enclosure in which it is contained is licensed for VCEM.

  To see if a blade is licensed for VCEM, access the DeployLicense Manager menu. Select Virtual Connect Enterprise Manager in the product license information table. Then click the Licensed Systems button to see the enclosures that are licensed for VCEM. If the enclosure containing the blade you are interested in is shown, then it is licensed correctly.

• If you run CMS to Managed Node Communication Checks for the CMS (as a managed node), the WBEM authentication check for it will always fail.

• When you run vseassist -a from the command line, vseassist attempts to run checks for all of the systems in the “All VSE Resources” collection. However, if a system is not a server (for example, an enclosure, rack, etc.), then the checks are skipped because they do not make sense. Currently, vseassist -a displays both an error message and a note for these non-server systems that are being skipped. The error message should not be displayed, but the note is correct.

• If you run CMS to Managed Node Communication Checks (vseassist -l) or Managed Node Configuration Checks (vseassist -r) from the command line for a non-server system (for example, enclosure, rack, etc.), usage information is erroneously displayed when the arguments are all correct. A note will also be displayed indicating that the system is not a server, and so checks cannot be run for it. This is correct.

• If you run Managed Node Configuration Checks (vseassist -r) from the command line for a system without SSH, you will get blank results. In this case, vseassist should display an error message indicating that the system doesn't have SSH installed.

• The vseassist command checks that use the Win32 API are not logging API and exit code details to the logfile.

  The status (PASS, FAIL, or WARN) of these checks is still logged. And if the check fails, vseassist logs the Issue and Resolution messages for the failure. However, vseassist does not log the details of the APIs that were called and their results.

• When running vseassist Managed Node Configuration checks for a 64-bit Windows managed system, the following message will be displayed in stderr:

  ´chcp´ is not recognized as an internal or external command, operable program or batch file.

  This is an issue with the remote command execution facility (DTF) of SIM, and the message can be ignored.