Skip to main content

Connectivity problems

Use this information to solve connectivity problems.

Table 1. Symptoms and user actions for connectivity problems.

Table with one spanned column at the top and two other columns with headers that provides information about symptoms and user actions to solve connectivity problems

  • Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
  • See Parts listing, System x3850 X6 and x3950 X6 Type 6241 to determine which components are customer replaceable units (CRU) and which components are field replaceable units (FRU).
  • If an action step is preceded by (Trained service technician only), that step must be performed only by a Trained service technician.
SymptomAction
The server cannot communicate with SAN.

Make sure that:

  1. The SAN device is powered on and is functional.
  2. All cables between the I/O adapter and the SAN device are properly connected and secure, and that the activity LEDs are lit on the appropriate ports.
  3. See the documentation that comes with the I/O adapter for additional information about troubleshooting SAN connectivity or network connectivity issues.
The server cannot connect to the data network (Ethernet).

If the server is unable to connect to the data network during initial setup, complete the following steps:

  1. Make sure that:
    1. The I/O adapter is powered on and the ports are enabled.
    2. All cables between the I/O adapter and the network device (switch or router) are connected correctly and secure, and that the activity LEDs are lit on the applicable ports.
  2. From the server operating system, verify the adapter network settings (IP address, subnet mask (if using IPv4), DHCP, and vLAN), to ensure that the settings match those of the network device (switch or router). See the documentation that comes with the operating system for information about checking network settings.
  3. Make sure that the proper device drivers are installed for the server network device.
  4. Check the Lenovo Support web site for any firmware updates or tips that might apply to this issue. You can view the release notes for a firmware update to determine the issues that are addressed by the update.
  5. Complete the following steps:
    1. Force the link/duplex speed.
    2. Remove the I/O adapter and install an identical, working I/O adapter in the same I/O slot.
    3. If the problem is solved, replace the I/O adapter that you removed.
    4. If problem persists, contact Lenovo Support.

If the server experiences a sudden loss of network connectivity, check the operating system and IMM event log and take the appropriate action.

The server cannot log into the IMM.
  1. Verify that the server has DC power.
  2. Make sure that you are using the correct log-in information. The fields are case sensitive.
  3. Check with the system administrator for the correct login parameters and if parameters can log-in to the IMM, then do the following:
    1. If the IMM is proven accessible (by system administrator), verify the login information.
    2. If the IMM is not accessible by system administrator, reset the IMM to defaults through the Setup utility.
    3. Retry the login. If IMM is still not accessible, replace the standard I/O book (seeRemoving the standard I/O book and Replacing the standard I/O book).
The server cannot ping the IMM on the management network.
  1. Verify that the server has DC power.
  2. Make sure that the server IMM has acquired an IP address in the Setup utility.
    Note
    If the IMM recently lost connection to the DCHP server, you must reset the IMM so that a new IP address can be acquired.
  3. Check the Lenovo Support web site for any firmware updates that might apply to this problem (see the Lenovo Data Center Support website). Read the release notes for the firmware update to determine the issues that the update addresses.