Help and support

Help resources and support for the System x and Cluster Solutions configurator (x-config)

Tab navigation

x-config enhancements for current and previous quarter (up to 300KB)

Archive of x-config enhancements, back to 26 July 2011 (up to 2MB)

Limitations and workarounds

If you run into an issue that you do not see listed below, please send a note to the Solutions Center of Competency notes ID

  1. Components disappearing when using Java versions newer than version 7.x

    Limitation: x-config users with Java version 8 are experiencing components disappearing.

    Workaround: x-config is not supported by Java version 8.x. Uninstall version 8.x and reinstall Java version 6.x or version 7.x.

  2. Cyprus should not include Lenovo Storage products in configurations until 1 March 2015

    Limitation: Configurations for Cyprus that contain Lenovo Storage products will fail in the order process until 1 March 2015. This limitation is caused by delays in transitioning this country to the Lenovo order process. When Cyprus is transitioned to the Lenovo process (1 March 2015), the Lenovo Storage products will become orderable.

    Workaround - Options include:
    • Delay orders containing Lenovo Storage products until the transition is complete.
    • Create separate orders for the x86 products and the Lenovo Storage products. Process the x86 order now, and the Lenovo Storage order when the transition is complete.

  3. Group IDs are not assigned automatically in scalable node configurations

    Limitation: When building a scalable node configuration in x-config, the Group IDs are not assigned automatically.

    Workaround: Each node will need to be created individually as the Group ID needs to be unique. You cannot create four copies of the same node. When creating the four nodes, select the Group IDs by increments of ten for each node. For example:
    • For the first node, select Group ID 01
    • For the second node, select Group ID 11
    • For the third node, select Group ID 21
    • For the fourth node, select Group ID 31

  4. 3837 MT maximum values for components
    Limitation: The AC1 (4U) and AC2 (8U) models of the 3837 MT (and their derivatives) have different maximum values for components such as processors, memory DIMMs, PCIe cards and power supplies. However, due to framework limitations the maximum values seen on the screen correspond to the 8U models. If you choose a 4U model and select a value over the actual maximum for that model x-config will display an error message to inform you of the correct maximum for the chosen model.

    Workaround: There is no workaround available for this limitation.

  5. Missing x-config icon after update/install from x-config website (Windows OS only)
    Limitation: After installing an application update via the x-config website (Windows OS only), it has been reported that the x-config application icon does not appear on the user's desktop. Users that reported this behavior also reported that it happened after a recent java version update on their local machine. To date, this behavior has been seen by only a few users and it cannot be replicated by the x-config application support team.

    Workaround: Users who encounter this issue in Windows 7 should follow the steps below:
    1. On your local machine, click the "Start" button and then launch the "Control Panel".
    2. Select "View by: Small icons" in upper right area of Control Panel window.
    3. Select "Java"
    4. On the Java Control Panel window, in the "General" tab, locate the "Temporary Internet Files" section
    5. Click the "View" button to display the "Java(TM) Cache Viewer".
    6. Remove all "System x and Cluster Solutions Configurator (x-config)" items by right-clicking them and selecting "delete", or by selecting the item(s) and clicking the red "X" on the toolbar.
    7. Close the "Java(TM) Cache Viewer" window.
    8. Close the Java control panel window ("OK", "Cancel" or "Close" - any one will work).
    9. Close the Control Panel window.
    10. Go back to the x-config website and update/install x-config (once the update/install completes, the x-config icon will appear on your desktop).

  6. Missing desktop icon for Open SUSE v12, KDE 4.x
    Limitation: After installing the x-config application via x-config website, it has been reported that the x-config application icon does not appear on the user's desktop. Users reported that it happened using IBM Java 1.6 and earlier.

    Workaround: Users who encounter this issue in Open SUSE v12, KDE 4.x should update to Oracle version 7:
    1. On your local machine, uninstall any versions of IBM Java 1.6.x (using Windows Control Panel, "Uninstall or change a program").
    2. Install Oracle SDN Java SE Runtime Environment 7 on your local machine.

  7. Switch limitations when including NeXtScale chassis in configuration
    Limitation: Due to conflicting racking rule requirements, switching support is limited when allowed in the same rack as a NeXtScale chassis (MT 5456).

    Workaround: There is no workaround available.

    Details on limited support: The functionality to design high-speed, low-latency networks such as Infiniband and 10GbE is now available in x-config with caveats. These network types now accommodate oPSE (opposite Port-Side Exhaust) or cold-aisle facing switches in Enterprise racks. What is new is the concept of "building blocks". Since NeXtScale is cabled in the front, there is limited room to cable and manage thick bundles so exact cable lengths and proper chassis and switch locations have been calculated. This calculation has been done for several common Infiniband and 10GbE networks and the result is a new concept in x-config termed "building blocks." The NeXtScale building blocks listed below allow for optimal rack placement of switches and NeXtScale gear in Enterprise racks.
    • 10Gb Dual Ethernet building block 1
    • 10Gb Dual Ethernet building block 2
    • 10Gb Single Ethernet building block 1
    • 10Gb Single Ethernet building block 2
    • 50% Blocking IB building block 1
    • 50% Blocking IB building block 2
    • 50% Blocking IB building block 3
    • Non-Blocking IB building block 1
    • Non-Blocking IB building block 2

    Important note: Non-Building Block NeXtScale solutions that require high-speed networks will continue to be addressed through the Large Cluster Review Board (LCRB). Please contact Bill Hollopeter ( if an LCRB review is needed.

  8. 2498 MT Linecord Product Support
    Limitation: The following MT 2498 linecord feature codes are supported, but are missing their associated HVEC option part numbers. Support in non-Xccelerator countries is pending identification of a suitable requirements source.

    Workaround: Use the included jumper cable for rack installations.

  9. e-Pricer (*.csv) files only in English

    Limitation: x-config creates non-English e-Pricer (*.csv) export files that cannot be used as input to e-Pricer.

    Workaround: Ensure that your exported e-Pricer (*.csv) configuration file is in English if you intend for it to be used as input to e-Pricer. If you primarily use x-config with a language setting other than English: (1) Build the configuration in your native language and save as a *.cse file, (2) Exit x-config, (3) Restart x-config switching the language setting to English on the License screen, (4) Open the saved *.cse configuration file, and (5) Export the configuration as an e-Pricer (*csv) file.

  10. Update messages for Oracle Java users

    Limitation: x-config displays a message to inform users that "An optional update is available." When accessing x-config via Oracle Java, users are seeing this message display again after the new version is downloaded. The second time the message displays it is no longer true, and the update is not downloaded.

    Workaround: This is an Oracle JVM bug that cannot be fixed by Lenovo developers. Users should click OK and disregard the second message.

  11. QSFP+ DAC Break Out Cables

    Limitation: The IBM QSFP+ DAC Break Out Cables (listed below) will not currently be automatically included in the Point-to-Point cabling for switches that support them.

    1m IBM QSFP+ DAC Break Out Cable ( FC A1DL, 49Y7886 )
    3m IBM QSFP+ DAC Break Out Cable ( FC A1DM, 49Y7887 )
    5m IBM QSFP+ DAC Break Out Cable ( FC A1DN, 49Y7888 )

    Workaround: The user may manually install the IBM QSFP+ DAC Break Out Cables by turning off the "Network Component Restrictions" rule from the Rules menu. This will allow the cables to be manually selectable when editing the switch that supports them.

  12. Tyco Patch Panel

    Limitation: Effective May 18, 2010 (with 10A 1350 BOM release): In network configurations that contain the Tyco Patch Panel (0564-HC3, FC2706), x-config cannot update or cable these devices with Networking Rules turned on.

    Workaround: In such scenarios, users will need to turn off all Networking rules, manually place these devices and select the appropriate cables. Due to low attach rates, the brand does not plan to request that this function be automated.

  13. iDataPlex MT 6391

    Limitation: When including the Westmere iDataPlex MT 6391 in configurations users will be able to select the "dual power" supply with Y power cables in the x-config user interface. However, x-config will NOT be able to completely perform the Point2Point cabling automatically because the existing code will attempt to connect both ends of the Y power cable to both inlets on the chassis. In such scenarios users will need to perform the Point2Point cabling manually, and in some cases, such as dual power domain, perform manual PDU selection since power figures will be based on routing to a single PDU.

    Workaround: There is a partial solution in place to automatically cable the "dual power" supply using Y power cables. The Y cables properly connect to adjacent chassis' power supplies. This provides a more appropriate PDU and cabling configuration in some scenarios. If, however, an odd number of chassis in columns A and C exist using this power configuration, there will likely be Y power cables connecting across the columns or connecting only a single chassis with no adjacent chassis with which to link. To achieve an ideal configuration as specified in the iDataPlex Configuration Specification, the user will have to manually replace the remaining odd chassis with an identical configuration using the straight jumper power cable instead of the Y power cable.

    Important notes about leaving an odd number of chassis in the rack:
    • There may be one chassis with only one end of each Y power cable connected or two chassis being connected across columns A and C in the rack.
    • x-config is unable to automatically replace the Y power cables with the appropriate quantity of straight jumper power cables because the current x-config power cabling model is based on the selection of the power cables the user has made and is not able to change it at this time.

  14. Qlogic QDR 360

    Limitation: When configuring a Qlogic QDR 360 and adding the optional Power supplies, x-config may not add the needed PDUs.

    Workaround: Turn the PDU update rules off and manually add PDUs and specify the cabling.

  15. IB switch in iDataplex rack

    Limitation: When you have an iDataplex rack and the U1 to U10 locations are occupied by other machines the large switch will not be mounted on the same rack. Instead, it will be mounted on a new iDataPlex rack. You can move the large switch back to the original rack by turning off Automated Switching Update and making sure you make space for the switch at the bottom of the rack.

    Workaround: As of August 9, 2012, we are not able to confirm this limitation and test this workaround because currently there are no IB switches that occupy three or more U locations in an iDataPlex rack. Most large switches now are not compatible with iDataPlex racks. You can manually move the switch by turning the update rule off. It is still suggested that you make sure the switch goes near the bottom of the rack with no servers beneath it.

    To do so, click and drag the switch to move to another position in the same rack - OR - right-click the switch and select the "Move To" option to move it to another existing rack (there must be enough free space to move it)

    Remember to not install servers directly beneath large switches (3U or more).