Print
login Account
Search
Unsupported Browser Detected: Dear user, the browser you’re currently using is not supported by this website. Please click here for more information about the browsers we support and how to obtain them.

ThinkServer EasyManage version 4.2.0 - Hints and Tips

The following is a list of tips associated with ThinkServer EasyManage v4.2.0.

1]  A memory leak occurs on Windows Server 2003 with Service Pack 1 and Windows Server 2003 R2 Non-Service Pack.

Cause

A memory leak occurs on Windows Server 2003 without Service Pack 2 or later.

Symptoms

When Lenovo ThinkServer EasyManage is installed on Windows Server 2003 (with Service Pack 1) or Windows Server 2003 R2 Non-Service Pack, the memory that is used for the ThinkServer EasyManage process increases.

Workaround

Apply Service Pack 2 or later for Windows Server 2003 Service Pack 1 or Windows Server 2003 R2 Non-Service Pack.

 

2] Failures might occur when logging in Linux by SSH.

Cause

SSH allows user to interrupt the session, which might cause some processing failures.

Symptoms

Logging on to a Linux node by SSH at the same time that messages are concurrently output to the login console (for example, background processing messages and user messages), might cause some processing failures. For example, problems might occur with the node discovery and with gathering node information.

If the discovery process fails to collect node information, then within the Monitoring module¡¯s Last Discovery Log, "Warning" is displayed in the Status column, and "No component information" is displayed in the Description column.

When you click the Warning entry, the following message displays in the detail area: "Although the SSH connection succeeded, this is an unsupported model."

Workaround

The failure doesn't happen frequently. If user wants to avoid it,try not to interrupt the session in the console when logging in by SSH.

 

3] An ESXi Server Installable Edition (the free version) that is a monitoring target might not show accurate status information, for exaple the disk/disk free space.

Cause

This issue depends on the VMware limitation. The following is the related information of VMWare:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1005704&sliceId=1&docTypeID=DT_KB_1_1&dialogID=305874685&stateId=1%200%20305878401
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1008167&sliceId=1&docTypeID=DT_KB_1_1&dialogID=305874701&stateId=1%200%20305878455

Symptoms

In the Monitoring module, when you reference the ESXi Server Installable Edition, the related component status might not be the most recent.

Workaround
  1. After the user creates or deletes a VM, he may find that the remaining disk space is not updated in real time. He needs to use VirtualCenter or Stage Manager to force a refresh function; and then he need wait for the next refresh cycle coming or click Recollection button in the top right of the monitoring page.
  2. If the user uses the Lab Manager or Stage Manager to manage VMWare, he may find that the remaining disk space is not updated in real time. He needs to use VirtualCenter to force a refresh function; and then he need wait for the next refresh cycle coming or click "Recollection button" in the top right of the monitoring page.

    Note: By default, the 15 minutes per one refresh cycle. But user can change this value. The operation step of changing the refresh cycle
    a) Enter the page of Settings -> Monitoring Interval -> Status monitoring,
    b) Update the value of Interval in the section of Status monitoring.

    Note: The value of Interval must be greater than the value of Max Duration.

 

4] The right side of the List of Changes - Detail report is not printed when using Internet Explorer 6.

Cause

This issue depends on using Internet Explorer 6.

Symptoms

In the Change section of the Reports module, the right side of the List of Changes - Detail option is not printed.

Workaround

Print the report using a supported browser other than Internet Explorer 6.

 

5] Fail to install EasyManage when there is double-byte character in installation package directory or  installation directory.

Cause

The EasyManage doesn't support double-byte character.

Symptoms

When the setup.exe file is launched from a folder name containing double-byte character codes, the installation will fail. When the program installation directory contains double-byte character codes, the installation will fail.

Workaround

User can use the default installation directory EasyManage provides. If the user-specified directory contains double-byte characters, he needs to modify the name of the directory to only contain the name of the single-byte characters.

 

6]  This service is not displayed when you change display name of specific service.

Cause

The page has not been updated.

Symptoms

In the Page of Setting -> Service Templates, if you change display name of specific service, this service is not displayed until the next refresh cycle or refresh it manually. The default refresh cycle is 15min, but user can modify this value.

Workaround

The either of the following both solutions can solve this problem.

  1. Click Recollection button in the top right of the monitoring page, then Services tab will be refreshed and all services can be displayed.
  2. Wait for the next refresh cycle coming.  By default, the 15 minutes per one refresh cycle. But user can change this value. The operation step of changing the refresh cycle:
    a) Enter the page of Settings -> Monitoring Interval -> Status monitoring,
    b) Update the value of Interval in the section of Status monitoring.

    Note: The value of Interval must be greater than the value of Max Duration.

  • Alias ID:
  • Document ID: HT077125
  • Last Updated :6/17/2014
  • (c) 2014 Lenovo