English Community

Datacenter Systems ManagementLenovo XClarity Knowledge Base

XClarity Mobile: known issues and top Tips

Known issues and limitations for Lenovo XClarity Mobile app v2.5.0

 

These are known issues and workaround tips for the Lenovo XClarity Mobile app version 2.5.0 . Ensure that you are running the latest version to obtain the best results.

 

General compatibility information:  Use the Lenovo XClarity Mobile app with Lenovo XClarity Administrator v2.3 or later.  The app is supported on Android 7.0-10 and iOS 10 and later.  

 

App version 2.6 (or later) will be required for USB communication with model SE350 at later code levels (ref. 187325)

Description: When using the Lenovo XClarity Mobile app USB-attached to a Lenovo model SE350 edge server at XCC versions 2.6.1 or later, some functions are broken when using XClarity Mobile app version 2.5 or earlier ThinkSystem Flex server.

Root Cause: The Redfish REST communication method used in updated versions of the server XCC and the earlier version of the mobile app are incompatible, resulting in incomplete data transfer to the App. 

Workaround: Use a version of the Mobile App that is compatible with the version of XCC on the SE350.  For SE350 XCC version 2.6, App version 2.5 is compatible.  For SE350 XCC versions 2.6.1 or later, App version 2.6 or later (expected release late November 2019) will be compatible.  

 

Updating network information on a USB-attached Flex server may fail (ref. 147862)

Description: When using the Lenovo XClarity Mobile app USB-attached to a Lenovo ThinkSystem Flex server, the XCC network information cannot be updated using older levels of XCC firmware. The TEI322Q level of XCC firmware exhibits this issue.

Root Cause: The Redfish REST interface between the mobile app and XCC are incompatible, resulting in the XCC rejecting the update command.

Workaround: Update the Server XCC firmware to the latest level or use the XCC web interface to modify network parameters.

 

Lenovo XClarity Administrator certificate update required for XClarity mobile app iOS push notification operation

Description: The push notification feature for Apple iOS devices operates by sending a packet from the XClarity Administrator to the Apple push service. This communication is SSL secured with a certificate that expires yearly. The certificate for XClarity Administrator expired in September 2019 and the following patch must be applied to the XClarity Administrator to update the certificate for continued push notification function. Lenovo support link: https://support.lenovo.com/us/en/solutions/ht504654.

Root Cause: The SSL certificate required for communication to the Apple push service expires yearly and must be updated on the XClarity Administrator.

Workaround: None - certificate must be updated.

 

An attempt to "pull to refresh" on iPhone X leaves screen in incorrect location (ref. 138465)

Description: When using the Lenovo XClarity Mobile app USB-attached to a Lenovo ThinkSystem server, the network information screen may experience problems when executing a "pull to refresh" action. This is known to only happen on the iPhone X.

Root Cause: The basic action of sliding the screen up or down to view the content works fine, but an attempt to perform a "pull to refresh" action leaves the screen stuck momentarily in an incorrect position. However, it can be moved after that.

Workaround: Use another phone type or avoid the "pull to refresh" operation.

 

 In some languages formatting characters might not be correctly interpreted and might be shown in messages (ref. 94388)

Description: When using the Lenovo XClarity Mobile app in certain language modes, some unprocessed formatting tags (such as ) might be included in messages.

Root cause: Unexpected formatting information is received from Lenovo XClarity Administrator. This is a permanent limitation.

Workaround: None; Ignore these characters. All required information is present in the message.

 

The mobile search capability accepts only English text input  (ref. 73451, 75456)

Description: When using the search function in the Lenovo XClarity Mobile app, the search terms must be input in English.

Root cause: This is a permanent limitation of the program environment.

Workaround: Use English to input search terms.

 

 

RESOLVED: Newsfeed search may not work properly when multiple XClarity Adminiatrator connections are present (ref. 170919)

Description: When more than one XClarity Administrator connection is defined, a device may not be found if it is managed by an XClarity Administrator that is not the active connection.

Root Cause: The mobile logic is not collecting the device search data from all of the XClarity Administrators, just the active connection.

Workaround:This issue is fixed with XClarity Mobile app v2.5.0 or later. Users at earlier versions can navigate to the Hardware tab for each active connection and use the search feature there.

 

RESOLVED: Mobile app log contents may not match XClarity Administrator log contents (ref. 165762, 164776)

Description: When viewing the logs using the mobile app, at times, the number of log entries may not exactly match the data the XClarity Administrator provides.

Root Cause: For most device types this is not an issue, however, for the Flex "chassis" view and "CMM" view, the XClarity Administrator shows chassis and CMM oriented logs in both views, whereas, the mobile app only shows chassis hardware logs under the chassis view and CMM hardware logs under the CMM view.

Workaround: This issue is fixed with XClarity Mobile app v2.5.0 or later. Users at earlier versions will find that the data is present, however, a user may wish to look at the XClarity Administrator view if they prefer that format.

 

RESOLVED: USB-attached download of XCC service data and event log cannot be emailed using Android mobile app (ref. 163562, 163558)

Description: When USB-attached to a Lenovo ThinkSystem server, there are actions to download the XCC service data and event log to the mobile device. The download is successful, however, the prompt allowing you to email the file is not working for the Android mobile app.

Root Cause: The third party plugin code used to provide this "social sharing" feature has a code problem that is being addressed in an upcoming release of their software.

Workaround: This issue is fixed with XClarity Mobile app v2.5.0 or later. Users at earlier versions will find that the file is successfully downloaded from the XCC to the "Downloads" directory, so a user can navigate to that location on the mobile device and use the email capability provided on that screen.

 

RESOLVED: Large data sets do not render properly on iOS mobile app (ref. 166893, 165995)

Description:When the mobile app is receiving large data sets from one or more XClarity Administrators, the long lists of devices or logs may not scroll smoothly.

Root Cause: When the XClarity Administrator is managing a very large number of devices, the inventory and log data sent to the mobile app can not be handled by the current rendering engine of the iOS app.

Workaround:This issue is fixed with XClarity Mobile app v2.5.0 or later. For users of earlier versions: If possible, clear the logs on the XClarity Administrator. Alternatively logs may be viewed using XClarity Administrator.

 

RESOLVED: Face ID authentication is not supported on iOS mobile app (ref. 171324)

Description: When Apple introduced the iPhone X and newer models, they removed the front button which also acted as the fingerprint reader. The direction was to use the new Face ID feature.

Root Cause: The third party plugin required to support this feature was not available for versions before v2.5.

Workaround: This issue is fixed with XClarity Mobile app v2.5.0 or later. For users of earlier versions: This optional authentication is at the "app" level, which also still provides a 4 digit pincode that can be enabled. In addition, the Face ID feature is still available at the "phone" level, along with another pin code.

 

RESOLVED: Long mobile app wait times experienced when no connectivity to XClarity Administrator (ref. 166895)

Description: When connectivity is unavailable to the XClarity Administrator (no Internet or cell service, incorrect IP address or hostname, disabled VPN, certificate not installed or expired, etc), the app may experience long periods of wait time showing the progress spinner.

Root Cause: The mobile app must wait for a network timeout when trying to contact the XClarity administrator.

Workaround: This issue is fixed with XClarity Mobile app v2.5.0 or later. For users of earlier versions: If possible, ensure all connection information, requirements and the environment are correct when initially setting up the mobile app.

 

Was this information helpful?

Yes No

Comments

X

Delete