Cannot connect to the advanced management module

Use this procedure to troubleshoot the advanced management module if you cannot establish network connectivity to the module at all (through Telnet, SSH, ping, or the Web browser).

Problem

You are unable to establish any network connectivity to the advanced management module.

Investigation

Perform these steps to resolve the problem:
  1. Connect a laptop (that can log in to other advanced management modules) to the advanced management module. Make sure that the IP configuration on the laptop puts it in the same subnet as the advanced management module and that the laptop is not running a local firewall.
  2. Try to connect to the advanced management module:
    • If you can ping the advanced management module and connect to it using a Web browser and Telnet, the problem is either in the network or in the other workstation used to access the advanced management module.
    • If you can ping the advanced management module, but you cannot connect using a Web browser or Telnet, see Can ping the advanced management module but cannot access it.
    • Connect to the serial port on the advanced management module and attempt to access the advanced management module from the command-line interface. If you can log in:
      1. Use the ifconfig command to check the network configuration of the advanced management module. For example,
                                            ifconfig -T system:mm[1] -eth0
                                         
      2. Use the ports command to ensure that all interfaces are enabled and the TCP ports are correct. For example,
                                            ports -T system:mm[1]
                                         

        For information about using these commands, see the Advanced Management Module Command-Line Interface Reference Guide.

      3. If you cannot access the advanced management module at all:
        1. Clear the Address Resolution Protocol (ARP) cache on the laptop. On Microsoft Windows, you can clear ARP cache with the command arp -d. See the documentation that comes with the operating system that you are using to determine how to clear the cache.
        2. Reseat the advanced management module:
          1. Remove the advanced management module from the BladeCenter S chassis. The fan modules will begin to run at full speed, which is clearly audible.
          2. Install the advanced management module. The fans will return to their normal level (in speed and noise) after the advanced management module has completed its POST process.
          3. Look at the LEDs for the advanced management module. If, after installing the advanced management module and connecting an Ethernet cable, the amber Error LED is lit, there is a fault in the advanced management module.
        3. Reset the advanced management module to the default configuration, which will restore the default user ID and password:
          Important: Resetting the advanced management module will shut down the external ports for all I/O modules, which will disrupt all network and fibre connectivity. After the advanced management module resets with the default configuration, it will attempt to obtain a DHCP address for two minutes before using the default IP address (192.168.70.125) and subnet mask (255.255.255.0). Remove the Ethernet cable from the advanced management module if you do not want it to attempt to obtain a DHCP address.

          If you previously saved your configuration, you will be able to restore it after resolving the problem with the advanced management module. For more information about restoring a previously saved configuration, see the Advanced Management Module User's Guide .

          1. Insert a paper clip into the pin hole on the back of the advanced management module.
          2. Push the paper clip in all the way and hold it for approximately 10 seconds. The advanced management module will reset and the fans will run at full speed, which is clearly audible.
          3. Remove the paper clip from the pin hole.
        4. Contact IBM support for assistance.