Troubleshooting Q & A

In general, text fields throughout the Fabric Manager GUI provide real-time validation. If the type of information provided is not appropriate or left blank, the field is highlighted in light red with a red border as shown in the following example. Mouse-over the field to display a tool tip about how to provide the correct information.

Troubleshooting Example

Q1. Why does Fabric Manager GUI fail to connect to Fabric Manager?

A1. Diagnose the connection issue using the following steps.
  1. Check whether the FE is configured properly. You can use the “opafequery” tool from the 01org/opa-ff repository to do this.

    This tool is an easy way to diagnose the connectivity to the FE without using Fabric Manager GUI. You can run the tool on the same server as the Fabric Manager (and FE) is running.

  2. Check that the network is configured properly.

    If the opafequery test in Step 1 works properly, there are issues with the network connectivity.

    1. Check the firewall to ensure that the FE port is reachable.
    2. If Step a. passes, the issue may be more complicated.
      1. If you are using both ipv4 and ipv6, try to focus on ipv4 only.
      2. If you are using only ipv6, you might try looking at the Java system property “java.net.preferIPv4Stack” and see if it is set to “true”. Check on the machine running the FM GUI first, look at JAVA_TOOL_OPTIONS or_JAVA_OPTIONS settings. If not, perhaps your organization is enforcing this policy and you might try working with your system or network administrator to reach a resolution.

  3. If you have verified that the Fabric Manager GUI machine can communicate with the FE port, then you should send the fmgui log file to Intel Fabric Manager GUI support.

Q2. Why is the number of active nodes/ports wrong on the Home screen?

A2. It is possible that the Fabric Manager GUI is configured to connect to the wrong host. Double-check the hostname/IP address to confirm the connection to the expected host.

Q3. On the HOME page, why does the MASTER SM field show the name of a different host than the one I am connected to?

A3. On the HOME page, notice that the name of the host you are connected to is shown in a number of places:

If you have connected to a Standby SM, the name in the MASTER SM field will be different from the name in the title bar and Subnet: field.

Connected to a Master SM Connected to a Standby SM

Q4. The Fabric Manager GUI fails to connect to a subnet after a long time and then displays an error message. How can I fix this?

A4. There are many reasons why a remote subnet fails to connect. The Fabric Manager GUI repeatedly attempts to connect to a subnet through the failover process. By traversing the list of subnet hosts, provided in the Subnet Wizard, the Fabric Manager GUI attempts to obtain a response from the Subnet Manager (SM) and subsequently the Performance Manager (PM). During the connection process the following dialog is displayed:



If no response is received from the SM, or if the SM responds but the PM does not, then the failover process has failed and the following dialog is displayed:



If this happens, then it is necessary to determine the root cause of the problem. Here are a few things to look at:
  1. Check whether the host is reachable.

    Open an Ssh session using the CONSOLE feature under the ADMIN tab and then type the following command:

    ping <ip/hostname>

    If there is no response, determine the root cause and try again.

  2. Check whether the FE is running.

    For more information about configuring the Fabric Manager to initialize the FE, refer to the Intel® Omni-Path Fabric Suite Fabric Manager User Guide in the section titled "Controlling FM Startup."

Q5. When I try to connect to a subnet I get an error indicating that the connection was forcibly closed by the remote host. What can I do?



A5. This error is displayed when an attempt is made to connect to a secure fabric without providing the necessary security certificates to establish the connection.

  1. Follow the procedure in Section F.2.3 Import Certificates to Fabric Manager GUI Key Store and Trust Store in the Intel® Omni-Path Fabric Suite Fabric Manager User Guide.
  2. Open the SETUP WIZARD under the CONFIGURE menu. Select the subnet to be configured and click on the SECURE checkbox as shown in the following figure. Use the file browser icons to locate the Key and Trust Store files, click APPLY, and then RUN.

  3. Enter the password for the certificates on the new dialog to establish a connection to the remote host.

Q6. While trying to open an Ssh session to a remote host using the CONSOLE feature under the ADMIN tab, the following error was reported. Why?

SSH_MSG_DISCONNECT: 2 Too many authentication failures for invaliduser
A6. This error is displayed when:

Q7. While trying to open an Ssh session to a remote host using the CONSOLE feature under the ADMIN tab, the following error was reported:

Unable to connect to remote host phgppriv22: java.net.ConnectException: Connection refused: connect

A7. This error is displayed when the Ssh port is incorrect. By default the Ssh port number is 22 unless specifically reconfigured by the system administrator.

Q8. In the Preferences Wizard I put an email recipient in the list and clicked on the Test button, but no email was sent.

A8. To send emails, the SMTP server must be running on the remote host. Then the Fabric Manager GUI must be configured to point to the SMTP server. Under the configure menu, select Email Setup and enter the SMTP Host, Port #, and Sender’s email address.



Q9. On the LOGGING window under the CONFIGURATION menu, how can I get more information about filling out the OUTPUT FORMAT field?

A9. Click on the Help icon to the right of the OUTPUT FORMAT field to display the formatting help window, which provides detailed information about the formatting symbols.