Help and support

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

1. 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
   
   
2. 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.
   
   
3. 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 the Java entry from the list.
   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).
   
   
4. 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.
   
   
5. 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 (whollopeter@lenovo.com) if an LCRB review is needed.
   
   
6. 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.
   
   
7. 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.
   
   
8. 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.
   
   
9. 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.