Correcting a No connection state for a managed system

The No connection state can occur when the HMC is not connected, or the handshake with the managed system failed.

Use this procedure for a system that was previously connected to the same HMC and is now in No connection state. If you have a new system, a new HMC, or have moved your system to a different HMC, refer to Correcting a connection problem between the HMC and a managed system.

Obtain the IP address for the managed system's service processor by performing the following steps.
1. On the HMC, right-click the desktop and select terminal > rshterm. The restricted shell command line interface displays.
2. At the terminal, issue the command: lssysconn -r all
  Information similar to the following appears:
```
resource_type=sys,type_model_serial_num=9117-570*100729E,sp=unavai
lable,ipaddr=10.0.0.247,alt_ipaddr=unavailable,state=No Connection,conne
ction_error_code=Connecting 0000-0000-00000000 
```
3. At the terminal, issue the ping command to the address of the failing system. In the example above you would type: ping 10.0.0.247.
Choose from the following options:
- If the ping is successful, go to step 3.
- If the ping is not successful, go to step 4.
If the ping test is successful, perform the following steps:
1. If your system is equipped with a control panel, ensure that there are no steady (that is, non-scrolling) reference codes displayed on the panel.
  Note: A steady reference code could indicate a hardware problem. Contact your next level of support or your hardware service provider.
2. Restart the HMC.
3. If restarting the HMC does not resolve the problem, contact your next level of support or your hardware service provider.
If the ping test is not successful, perform the following steps:
1. If your system is equipped with a control panel, ensure that there are no steady (that is, non-scrolling) reference codes displayed on the panel.
  Note: A steady reference code could indicate a hardware problem. Contact your next level of support or your hardware service provider.
2. If your system has a control panel, check to see if the power light is on.
3. Choose from the following options:
  - If there is power to the managed system, go to step 5.
  - If there is no power to the managed system, refer to Powering on a managed system. After the power is restored, wait 5 minutes for the service processor to re-IPL and the HMC to re-establish contact. If the system is equipped with redundant service processors, allow up to 20 minutes for this step.
Verify physical network connectivity:
1. Verify that the HMC and the service processor are correctly connected to your Ethernet network. For more information, see Cabling the HMC.
2. Verify that Ethernet link status is good on all network segments which exist between the HMC and the managed system.
3. If you think the network might be the problem, connect a cable from the HMC to the service processor and try pinging the failing system. Then choose from the following options:
  - If the ping is successful, put the cables back the way they were and correct the network problem. After the network problem is resolved, repeat this entire procedure.
  - If the ping is not successful, put the cables back the way they were and continue with step 5.d.
4. Reset the service processor. See Resetting the service processor.
If the problem is not resolved by any of the above steps, contact your next level of support or your hardware service provider.