Known issues and limitations for
Lenovo XClarity Mobile app v2.4.0
These are known issues and workaround tips for the Lenovo XClarity Mobile app version 2.4.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 v1.3 or later. Future versions of the XClarity Mobile app will require upgrade to Lenovo XClarity Administrator v1.4 or later.
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: A user can navigate to the Hardware tab for each active connection and use the search feature there.
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: The data is present, however, a user may wish to look at the XClarity Administrator view if they prefer that format. 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: The file is successfully downloaded from the XCC to the "Downloads" directory, so a user can navigate to that location on the phone and use the email capability provided on that screen.
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: If possible, clear the logs on the XClarity Administrator. However, an upcoming firmware fix to the mobile app will alleviate this issue. 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 is not yet available, but will be utilized in an upcoming mobile release. Workaround: 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. 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: If possible, ensure all connection information, requirements and the environment are correct when initially setting up the mobile app.
USB-attached utilization graphs may render incorrectly (ref. 149475) Description: When USB-attached to a Lenovo ThinkSystem server, the utilization graphs may render incorrect x-axis
timestamp information. Root Cause: During certain periods when the XCC is initializing or collecting utilization data, the Redfish REST API provides
invalid data. Workaround: If possible, re-try at a later time or use the XCC web interface to view utilization data.
Help links do not work on XClarity mobile app when using a Moto Z device (ref. 149131) Description: The help links under the mobile app Settings->About->Help screen will not launch when using a Moto Z device. Root Cause: The browser launch API is failing on this device due to an interaciton between the device and the Android
operating system for this particular device. Workaround: If possible, use another device or the help is available from the XClarity Administrator top toolbar Admin->Help link.
An attempt to update network information on a USB-attached Flex server fails (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 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 push notification packet from the XClarity Administrator to the
Apple push service. This communication is SSL secured with a certificate that expires yearly. The current expiration date is
August 8, 2018 and the following patch must be applied to the XClarity Administrator to update the certificate for version 2.1.0
or earlier. 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 avoiding the "pull to refresh" operation.
RESOLVED: The chassis map view on the mobile app does not match the same view on the Lenovo XClarity Administrator (ref. 136106) Description: When comparing the chassis map views of the Lenovo XClarity mobile app and Administrator, the SN850 and SN550 Flex blades front panel views are slightly different. The front drive configuration and corporate logo do not match. Root Cause: The mobile app must use SVG images while the Administrator uses simpler PNG images. As such, there are rare cases where the mobile and Administrator front panel images do not match perfectly. Workaround: The device can be tapped to bring up correct inventory information that will clarify the manufacturer and drive information. Corrected images are being created for this issue.
Lenovo XClarity Mobile app Android push notifications stopped working
Description: Due to a security enhancement that has been implemented by Google for its Google Cloud Messaging (GCM) service, the XClarity Mobile application push notification service has stopped working for Android phones.
Customers using the push notification feature of the XClarity Mobile application on an Android phone may have experienced this problem. The symptom of the issue is an error message in the Status column of the push notification subscription table of the XClarity Administrator web under the Monitoring->EventForwarding->Push Services->Android Service.
Workaround: The following XClarity Administrator v1.4.0 fix should be applied to XClarity Administrator systems running v1.4.0 to resume push notification services.
XClarity Administrator v1.4.0 GAFIX now available
- Update the certificate for communication between XClarity Administrator
and Google Push Service
The following XClarity Administrator v2.0.0 fix should be applied to XClarity Administrator systems running v2.0.0 to resume push notification services.
XClarity Administrator v2.0.0 GAFIX now available
- Update the certificate for communication between XClarity Administrator
and Google Push Service
Status of some jobs might not display (ref. 117029)
Description: When a complex set of jobs with subtasks is running on a connected Lenovo XClarity Administrator, the mobile app might not show all subtasks in the jobs view.
Root cause: Limitation on app ability to interpret jobs data from XClarity Administrator.
Workaround: In such situations, use the Lenovo XClarity Web interface to monitor jobs.
Displayed severity of alert might be incorrect (ref. 118405)
Description: On some devices, a received push notification alert for a critical-severity error might display the icon for an informational message. This issue is rare and limited to devices running iOS 11.
Root cause: Missed or misinterpreted data in push notification.
Workaround: Alerts are received and displayed. When running iOS11, carefully read alert content to assure that you understand the severity level. Alternatively, use the Lenovo XClarity Administrator Web interface or alternative Call Home paths.
Device counts might be inaccurate for Lenovo SD530 chassis (ref. 119547)
Description: When viewing inventory information for a Lenovo SD530 chassis, the number of devices shown on the app might differ from the actual number.
Root cause: The Lenovo XClarity Mobile app misinterprets inventory data for this device type.
Workaround: None. This inaccuracy may be disregarded, as all detailed inventory information is correct. If accurate device counts are required, you may use the Lenovo XClarity Administrator Web interface to obtain this information.
Local USB-attached management of ThinkSystem servers may not be possible with certain Android mobile phones (ref. 113275, 113947)
Description: When using the Lenovo XClarity Mobile app USB-attachment to a Lenovo ThinkSystem server, the connection and discovery steps might fail intermittently with certain Android phone models running Android 6.0 OS.
Root Cause: This is a limitation in the way certain implementations of the Android OS on particular phones communicate over the USB connection. Currently, the following devices are known to exhibit this behavior: Huawei NXT-AL10, Huawei Mate 8, LG G6.
Workaround: Resetting the XCC management controller on the managed server might alleviate the condition. Also, using another Android phone model or an Apple iPhone might avoid the issue. Depending the network connectivity, the main Lenovo XClarity Mobile app function or the XClarity Administrator can be used to perform the desired actions.
Immediately after device boot order is changed, viewing boot order on Mobile App may give error message (ref. 118013)
Description: If a system boot order is changed locally (e.g. using UEFI), then the boot order is viewed on the App, an error message may be seen.
Root Cause: This is a bug in the information received from the managed device.
Workaround: Wait a few moments and then retry action on App; correct information should appear.
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 <b>) 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.